A pending lawsuit gives a utility nothing to act on until the court does something, which is why it is worth writing down what each possible outcome would require before the docket moves. The Guardian reported on the new suit, which asks a federal judge to order action on "widespread pollution from the hormone-disrupting pesticide atrazine." The summary describes the complaint as alleging that EPA has failed, under the Clean Water Act, to address surface-water atrazine pollution for decades.
The filing is a request. It does not alter the federal drinking water standard for atrazine, which is 3 micrograms per liter, and it does not change the monitoring you run or the treatment you operate today. What it does is point at the source record. Atrazine reaches a surface-water intake through runoff, and the timing of that runoff depends on application, rainfall, and flow. A complaint about surface-water pollution therefore lands first on the records that describe the river, and only later, if at all, on the finished water.
Three outcomes, three different records
The first outcome is that the case stalls, is narrowed, or is dismissed. Nothing in your compliance obligations changes. The record to keep is the rationale for continuing current practice, dated and signed, so that a later reviewer can see why no capital decision followed the filing.
The second outcome is that the court orders the agency to respond, and the agency takes a position on a schedule. The record here is the schedule itself, together with any proposed criteria. Staff should identify early which kind of requirement a future action would produce. An ambient water quality criterion for aquatic life is a different instrument from a drinking water maximum contaminant level, and it can take years before either one binds a treatment plant. Mapping that distinction now prevents a future memo from treating a proposal as a limit.
The third outcome is a revised standard or a new monitoring requirement with a compliance date. This is the only case where the treatment and laboratory questions become binding. The record then needs the compliance date, any method requirements, the reporting format, and the detection limit the method must reach. If a revised limit were set below your current detection capability, the gap would be a laboratory question before it became a treatment question.
What to pre-stage now
Pull the atrazine results from the intake for the period you have on file, along with sample dates, method detection limits, and the laboratory that analyzed each sample. The purpose is to see whether your data would show a seasonal pattern. A quarterly or routine grab sample can miss a runoff pulse entirely, so the result describes the sampling schedule as much as the water. Note the frequency and whether any event-based sampling was done after heavy rain.
Next, document the treatment options on paper before anyone needs them. Powdered activated carbon is commonly applied for episodic events, since it can be dosed when a pulse arrives, while granular activated carbon works as a continuous filter bed. Adsorption capacity depends on contact time, water chemistry, and how much organic matter competes for the same sites, and a bed loaded by other compounds will break through sooner than the design suggests. Writing these mechanisms into the file lets a future decision rest on the tradeoffs rather than on a vendor summary.
Assign one person to watch the docket and the agency's public calendar, and give that person a short list of triggers that would prompt a review. A trigger might be a court order, a published proposal, or a state adoption of federal criteria. Each trigger should have a named response, such as updating the scenario register, asking the laboratory for a method check, or convening the operations group.
Write around the uncertainty
The suit has not been decided. Its outcome, timing, and scope are unknown, and any statement about what will happen would be speculation. The disciplined posture is to keep a range of outcomes, attach each one to a record and a trigger, and revisit the file when the docket changes. Building a capital plan on a complaint is premature. Building a file that can answer quickly when a ruling arrives is not.