Surface Water Treatment Rule Monthly Operating Report
Track monthly SWTR operating data in one report with daily filter performance, disinfection monitoring, corrective actions, and certification fields ready for state submission.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Municipal Water Utilities · Public Water Systems · Water Treatment Operations · Environmental Compliance
Overview
This template is a monthly operating report for Surface Water Treatment Rule compliance. It brings together the facility identifiers, the month being reported, daily filter performance, disinfection monitoring, corrective actions, and final certification in one place so the report can be reviewed and submitted to the state primacy agency without stitching together separate files.
Use it when your plant needs a repeatable monthly summary of operating conditions, exceptions, and follow-up actions. The structure is especially useful when daily logs, SCADA exports, lab results, and operator notes need to be reconciled into a single record with a clear audit trail. The report also helps standardize who reviews the data, who certifies it, and what supporting documents are attached.
Do not use this template as a substitute for daily operational records, instrument calibration logs, or state-specific forms if your primacy agency requires a different format. It is also not the right fit for facilities that do not operate under SWTR reporting obligations. Keep the data minimal and relevant: collect only the fields needed to explain monthly performance, document exceptions, and support submission. If your process includes branching conditions, use conditional logic so you only show the exception detail fields when a filter or disinfection issue occurred.
Standards & compliance context
- This template supports SWTR reporting by organizing operating data, exceptions, and corrective actions into a clear monthly record for the primacy agency.
- The report structure helps maintain an audit trail by linking daily monitoring entries to exception details, supporting documents, and certification.
- Use data minimization when customizing the form so you collect only the PII or operational data needed for compliance and follow-up.
- If the report is shared electronically, ensure the submission process preserves integrity, access control, and a reviewable certification record.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Report Details
This section identifies the facility, reporting month, and contact person so the submission can be matched to the right plant and followed up without confusion.
- Facility Name
- Facility ID
-
Reporting Month
Select any date within the reporting month. The month and year will be used for the report period.
- Reporting Contact Name
- Contact Email
Plant Operating Summary
This section gives a month-level snapshot of how many days the plant operated and whether any unusual operating patterns need context.
- Days Operated This Month
- Days with Filter Runs
- Days with Disinfection in Service
-
Monthly Summary Notes
Use this field for brief operational context only. Do not include unnecessary PII.
Daily Filter Performance
This section captures the day-by-day filter record and makes it easy to flag performance exceptions that need explanation or corrective action.
- Daily Filter Log
- Filter Performance Exceptions
-
Filter Exception Details
Describe the exception, affected filter, duration, and corrective action taken.
Disinfection Monitoring
This section records the daily disinfection data and highlights any monitoring gaps or out-of-range conditions that require review.
- Daily Disinfection Log
- Disinfection Exceptions
-
Disinfection Exception Details
Describe any residual or contact time deviations and the corrective action taken.
Corrective Actions and Attachments
This section documents what was done in response to exceptions and preserves the supporting evidence needed for an audit trail.
-
Corrective Actions Taken
Summarize operational corrections, notifications, or follow-up actions taken during the month.
-
Supporting Documents
Upload lab sheets, SCADA exports, or other supporting records if required by your agency.
- Additional Notes
Certification and Submission
This section confirms that an authorized person reviewed the report, certified it as complete, and dated it for submission.
- I certify that this report is complete and accurate to the best of my knowledge.
- Certifier Name
- Certifier Title
- Certification Date
How to use this template
- Enter the facility name, facility ID, reporting month, and the contact person who can answer follow-up questions from the state.
- Summarize the month’s operating pattern by recording days operated, days with filter runs, days with disinfection, and any high-level notes that explain unusual conditions.
- Complete the daily filter performance section with one row or entry per operating day, then mark any exceptions and add the specific filter details that need review.
- Complete the daily disinfection monitoring section with the corresponding daily readings, then document any disinfection exceptions and the reason they occurred.
- List each corrective action taken, attach the supporting documents that verify the event or response, and add any remaining notes that help explain the report.
- Have the authorized certifier review the full report for completeness, then sign and date the certification before submission to the primacy agency.
Best practices
- Use date pickers for reporting dates and numeric inputs for counts so the report is easier to validate and less likely to contain formatting errors.
- Keep exception detail fields hidden until an exception is marked, using conditional logic to avoid forcing operators through unnecessary prompts.
- Record the source of each daily value, such as SCADA, operator rounds, or lab results, so the audit trail is easy to follow later.
- Describe corrective actions in plain operational language and tie each action to the specific filter run or disinfection event that triggered it.
- Attach source documents at the time the report is prepared rather than waiting until a regulator asks for them.
- Review the report against the plant logbook before certification to catch missing days, duplicate entries, or mismatched units.
- Keep the template focused on SWTR-relevant data and avoid adding fields that do not support reporting or follow-up.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this monthly operating report cover?
This template covers the core monthly data needed for Surface Water Treatment Rule reporting: facility details, operating summary, daily filter performance, disinfection monitoring, corrective actions, attachments, and certification. It is designed to compile the records you already collect during the month into a submission-ready format. Use it as the final reporting layer, not as a substitute for your daily logbooks or instrument records.
Who should complete and certify this report?
It is typically completed by the plant operator, compliance staff, or water quality manager who has access to the daily operating records. The certification fields are meant for the person authorized to attest that the report is complete and accurate. If your utility uses a review chain, the preparer and certifier can be different people.
How often should this template be used?
Use it once per reporting month, after the daily filter and disinfection logs are closed and any exceptions have been investigated. The monthly cadence helps you catch missing entries, reconcile corrective actions, and submit a clean record to the primacy agency. If your state requires a different deadline or supplemental schedule, add that as a workflow step.
What records should feed into the daily filter and disinfection sections?
Populate those sections from operator rounds, SCADA exports, lab results, and instrument readings that document filter performance and disinfection conditions each day. Use the template to summarize the daily record, then attach the source documents when needed for audit trail support. Keep field values aligned with your actual monitoring method and reporting units.
Does this template help with regulatory compliance?
Yes, it is structured for SWTR compliance reporting and for maintaining a clear audit trail of operating data, exceptions, and corrective actions. It does not replace your utility’s regulatory review or state-specific instructions, but it helps standardize what gets reported and how it is documented. Always confirm local primacy agency requirements before submission.
What are the most common mistakes when using this form?
Common issues include leaving required fields blank, entering narrative text where a date or numeric field is needed, and failing to explain exceptions in enough detail. Another frequent problem is listing a corrective action without linking it to the specific filter or disinfection event that triggered it. The template is most useful when every exception has a clear follow-up and supporting document.
Can this be customized for different plant setups or reporting systems?
Yes, you can tailor the daily log fields, exception prompts, and attachment list to match your plant’s treatment process and state reporting format. If your facility uses SCADA, lab software, or a document management system, add integration fields or links so the report pulls from the right source records. Keep the minimum-necessary principle in mind and avoid collecting data you will not use.
How does this compare with keeping SWTR data in ad hoc spreadsheets?
An ad hoc spreadsheet can store numbers, but it often misses validation, consistent field labels, and a reliable certification step. This template gives you a repeatable structure for monthly review, exception tracking, and submission, which makes it easier to spot gaps before filing. It also creates a clearer audit trail when regulators ask how the report was assembled.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
Compare 11 frontline hiring platforms on mobile apply, automated screening, and onboarding handoffs to find the right fit for hourly and shift-based workforces.
-
Disconnected cloud apps create friction and waste time. Learn why unified work platforms improve productivity and retention.
-
When scheduling tools lack leave and budget data, costly errors follow. See how integrated workforce management closes the context gap.
-
Integrated digital workplace task management tips to keep work moving, reduce stalls, and turn conversations into accountable action.
Ready to use this template?
Get started with MangoApps and use Surface Water Treatment Rule Monthly Operating Report with your team — pricing built for small business.
