Water Quality Reporting Software: Samples, Limits, and Reports the Public Can Read

What the project is

A utility samples its water at defined points: at the treatment plant, in the distribution network, and at customer taps for specific parameters such as lead and copper. Samples go to a laboratory, results return with values, units, and detection limits, and each result is checked against its regulatory limit. The reporting system holds the schedule, the results, the limit checks, and the follow-up actions, and generates two kinds of output: the compliance filing for the regulator, and the public report for customers.

The public report, often called a consumer confidence report, summarises what was tested, what was found, and whether standards were met, in language a non-expert can follow. The gap between a lab spreadsheet and that report is where trust is won or lost. A utility that publishes clear results, including bad ones with an explanation and a fix, keeps more trust than one that publishes only reassurance.

Core features

Limit checking and follow-up tracking are the features that matter. A result that exceeds a limit and sits unnoticed in a spreadsheet is the failure this software exists to prevent.

• Sampling schedules by point, parameter, and frequency, derived from regulatory requirements, with overdue alerts.
• Lab result import with units, detection limits, and qualifier flags, validated on import rather than trusted blindly.
• Automatic limit checks with exceedance flags, routed to the responsible staff member with a due date.
• Violation and follow-up workflow: resampling, investigation, corrective action, and closure, each recorded.
• Consumer confidence report generation from the same results, with plain-language explanations per parameter.
• Public disclosure tools: publishing reports online, notifying customers when a notice is required, and archiving past reports.
• Trend views per point and parameter, so a rising value is visible before it becomes an exceedance.

How it is built

Start from the regulatory schedule, not the public report. If the sampling and limit-checking core is wrong, the public report will be wrong too, in public.

1. Requirements study: list every sampling duty, parameter, limit, and report for the system, from its current permits and rules.
2. Schedule and import build: sampling schedules, lab result import with validation, and limit checks, tested on a year of real results.
3. Follow-up workflow: exceedance routing, resampling, and corrective actions, with closure tracking.
4. Public reporting: consumer confidence report generation and disclosure tools, reviewed by communications staff before launch.
5. Launch and audit: run one full reporting cycle in parallel with the old process, and reconcile every number before switching over.

Tech considerations

The technical priorities are result validation, limit logic that can be audited, and a public report that cannot drift from the underlying results.

• Lab result import supporting common lab formats, with validation for units, detection limits, and missing qualifiers.
• Limit rules as configuration per parameter and point, with change history, so a limit change does not rewrite history.
• Report generation from the same result records used for compliance, so public and regulator versions cannot disagree.
• Role-based access separating samplers, lab staff, compliance staff, and public publishers.
• Retention handling matched to the regulatory record period, with archived reports retrievable by year.

Challenges to plan for

Quality reporting fails on lab data quality and on the temptation to soften bad news. Both are trust problems with regulatory consequences.

• Lab format variation: laboratories report in different formats and units, and import errors silently corrupt results if validation is weak.
• Detection limit confusion: a result reported as below detection is not zero, and the report must handle it honestly.
• Exceedance handling: a result over a limit needs a defined response within a defined time, or it becomes a violation on top of a violation.
• Public language: a report that hides behind jargon will be distrusted, and one that oversimplifies will be challenged by anyone who reads the lab data.

Who it is for, and honest limits

This fits municipal and private water suppliers with sampling and public reporting duties, and the laboratories and consultants that serve them. It fits less well for a tiny system with a handful of annual samples, where a schedule and a spreadsheet may honestly be enough.

It does not make water safe or interpret results beyond the limits. It makes sampling complete, results checked, and reporting honest. When a result is bad, the software's job is to surface it fast and track the fix, not to soften the message.

Frequently asked questions