Water and wastewater compliance reporting and operations data

Reference article · 5 min read

A water or wastewater utility produces two kinds of data at once. Operations data comes off instruments and controls continuously: flows, levels, pressures, runtimes, turbidity, chlorine residual. Compliance data is a much smaller set of values a permit or rule requires, reported on a fixed schedule and signed by someone legally responsible for its accuracy. The systems holding the first are usually not the systems producing the second, and that gap is where most compliance reporting work happens.

In many utilities the bridge is manual: a historian trend exported to a spreadsheet, a laboratory PDF, values retyped into a state portal at month end. That holds until staff turn over, a digit is transposed, or an inspector asks how a value was derived.

What regulators expect to receive

The permit is the specification. Two facilities in the same state can owe different parameters, sample types, and frequencies, so start from the permit text.

• Discharge monitoring reports. Clean Water Act discharge permits, issued by EPA or an authorized state agency, set effluent limits and monitoring requirements. Results are reported periodically, commonly monthly.
• Drinking water monitoring. Safe Drinking Water Act requirements are administered by a state primacy agency in most states. Systems file monthly operating reports plus scheduled sampling results for microbial, disinfection byproduct, and lead and copper parameters.
• Event reports. Overflows, bypasses, treatment technique violations, and public notification triggers carry their own forms and deadlines.
• Annual reports. Consumer confidence, pretreatment, and biosolids reports, depending on the utility.

SCADA, historians, and the line between operations and compliance

A historian records tag values at high frequency. A reported value is usually an aggregate: a daily average, a daily maximum, a monthly geometric mean. That aggregation has to match the permit definition, including whether an average is time weighted or arithmetic, how rounding is handled, and how out of service hours are treated.

• Keep a registry of compliance tags. Which tags feed a reported value, in what unit, from which instrument, with calibration records attached: inspectors ask when a meter was last calibrated.
• Preserve raw data. Aggregates should be derived and reproducible, never written back over the source.
• Document substitution rules. Gaps, failed sensors, and manual readings need a written rule applied consistently.
• Move data off the control network safely. Reporting should read from a replica or one way feed, not a path that lets business systems reach controls.

Laboratory results, sampling schedules, and chain of custody

A laboratory information management system, or the laboratory module of an operations system, should build the sampling schedule from permit requirements, not a technician's memory. The schedule drives bottle preparation, collection, preservation, holding times, and analysis.

• Track sample events. Location, parameter, method, collector, date and time, and the permit requirement each satisfies, with chain of custody recorded from collection to the bench.
• Confirm certification and methods. Analyses generally must use approved methods and, for many programs, a certified laboratory. Requirements differ by program and state, so confirm with the permitting or primacy agency.
• Require electronic data deliverables. Contract laboratories should return results in a defined electronic format that loads into your system. PDFs force retyping, which is where errors enter.
• Handle qualifiers deliberately. Non-detects, detection limits, and reruns need consistent treatment, because they change the reported number.

Electronic submission, signatures, and records

Federal rules have moved discharge monitoring reporting to electronic submission, generally through EPA's NetDMR or an equivalent state system, and drinking water reporting usually runs through a state portal. Electronic reporting under authorized programs is subject to EPA's cross media electronic reporting requirements, which is why identity proofing, signature agreements, and a durable copy of record matter. Permits name a responsible official and allow written delegation, so keep that authority current: submissions stall when the named person leaves. The portal's copy of record is itself a record, worth keeping in your own systems for the retention period the permit sets.

Overflows, bypasses, and violation reporting

Event reporting runs on short clocks. Many programs expect verbal or electronic notice within a day of discovery and a written report shortly after, with exact windows set by the permit and state rules.

• Mobile capture of start and stop time, estimated volume and how it was estimated, cause, receiving water, and corrective actions.
• Asset identification from GIS, so the location is a manhole or outfall, not a text description, plus a link to the work order so repair and regulatory records agree.
• A queue showing which notifications are still open against their deadline.

Annual reports to customers

Community water systems prepare an annual consumer confidence report covering detected contaminants, sources, violations, and required language, delivered to customers and certified to the primacy agency. The rule has been revised in recent years, so confirm current content, format, and timing with that agency. Build it from the same result store used for regulatory submission, so the two cannot diverge, and plan for plain language and an accessible web version.

What to ask vendors and require in the contract

1. How historian and laboratory data are exported, in what formats, and whether export is self service.
2. Whether aggregation logic for reported values is configurable and visible, not hidden in vendor code.
3. What the audit trail captures: who changed a result, when, and why, with no silent edits.
4. Whether the product supports your state's submission format, demonstrated against your permit.
5. Where the system runs and how it connects to control system networks.

In the contract, require export in open formats at any time and at exit without added fees, retention of audit trails, support during reporting windows, and agency ownership of data and configuration.

HQT builds and integrates data systems for state and local agencies, including work connecting operational data to reporting and analytics.

Frequently asked questions