Wastewater Discharge Monitoring Report Log
Track wastewater sampling results, flow data, exceedances, and corrective actions for each permitted outfall before NPDES DMR submission. Use it to keep reporting periods, lab results, and certification details in one place.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Manufacturing · Food Processing · Utilities · Chemical Processing · Municipal Wastewater
Overview
This Wastewater Discharge Monitoring Report Log template is built to capture the information that typically feeds an NPDES DMR submission for a permitted wastewater outfall. It organizes the reporting period, facility details, sampling event data, monitoring parameters, flow conditions, noncompliance notes, corrective actions, and final review so the reporting record stays in one place.
Use it when your team needs a repeatable way to document each sampling event and tie results back to a specific permit and outfall. It is especially useful when multiple people touch the workflow, such as field staff collecting samples, a lab issuing results, and a manager reviewing the record before submission. The template also helps preserve an audit trail by keeping the sample date, chain-of-custody reference, lab report number, and review fields together.
Do not use it as a substitute for the actual permit, DMR filing system, or a site-specific monitoring schedule. If your facility does not have permitted wastewater discharge, or if the record is for stormwater, drinking water, or a non-regulated internal process, this template is not the right fit. It is also not ideal for one-off incident notes unless you need them tied to a reporting period and formal compliance review. The value of the template is in structured, permit-linked documentation that supports accurate, timely submission.
Standards & compliance context
- This template supports NPDES DMR preparation by keeping permit-linked monitoring data organized for review and submission.
- Use data minimization when collecting names, contact details, or other PII, and only retain what is needed for compliance and audit trail purposes.
- If the log is used in a public-facing or shared workflow, apply access controls so sensitive compliance records and operational notes are not broadly exposed.
- The certification section should be completed by the authorized reviewer or certifier required by your permit and internal control process.
- For regulated records, preserve source documents such as lab reports and chain-of-custody forms so the logged values can be verified during inspection or audit.
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
Reporting Period and Facility Details
This section anchors the record to the correct permit, facility, and discharge point so the rest of the log can be tied to one reporting window.
- Reporting Period Start Date
- Reporting Period End Date
- Facility Name
- NPDES Permit Number
-
Outfall Identifier
Enter the permitted outfall ID exactly as listed in the permit or DMR instructions.
Sampling Event Details
This section captures how and when the sample was collected, which is essential for traceability and defensible reporting.
- Sample Date
- Sample Time
- Sample Type
- Collection Method
- Sample Collected By
-
Chain of Custody Reference
Optional reference number for internal tracking or laboratory chain of custody.
Monitoring Parameters and Results
This section holds the actual measured values and lab references that feed the DMR and support verification.
- Parameter Results
- Required Sampling Frequency
- Laboratory Name
- Laboratory Report Number
Flow and Operational Conditions
This section documents the operating context behind the discharge data, including flow values and any upset conditions that may affect interpretation.
- Average Daily Flow
- Peak Flow
- Flow Units
- Did a process upset or bypass occur?
- Process Upset / Bypass Description
Exceedances, Missing Data, and Corrective Actions
This section records noncompliance, data gaps, and the follow-up actions needed to show the issue was identified and addressed.
- Was any exceedance, missing data, or noncompliance observed?
- Type of Issue
- Corrective Action Description
- Corrective Action Date
Review, Certification, and Submission
This section confirms the log has been checked, marked ready, and prepared for authorized submission with an audit trail.
- Reviewed By
- Review Date
-
Ready for DMR Submission
Confirm that the record has been checked for completeness and is ready for regulatory submission.
-
Certification Statement
By submitting this form, you confirm the recorded information is complete and accurate to the best of your knowledge and is maintained for compliance recordkeeping.
How to use this template
- Enter the reporting period, facility name, permit number, and outfall identifier so every record is tied to the correct discharge point and filing window.
- Record each sampling event with the sample date, sample time, sample type, collection method, collector name, and chain-of-custody reference using the appropriate field types.
- Add the monitoring parameters, lab name, lab report number, sample frequency, and measured results exactly as reported, including units and any qualifiers.
- Document flow conditions and operational events such as average daily flow, peak flow, process upset status, and a brief upset description when applicable.
- Note any noncompliance, missing data, or exceedances, then assign corrective actions with a clear description and action date before review.
- Have the designated reviewer confirm completeness, mark the record submission-ready, and finalize the certification statement before the DMR is filed.
Best practices
- Use one record per reporting period and outfall so results do not get mixed across permits or discharge points.
- Match each parameter result to the exact lab report number and chain-of-custody reference to preserve traceability.
- Use conditional logic to show corrective action fields only when noncompliance or a process upset is recorded.
- Keep units consistent across flow and parameter fields, and do not rely on free-text notes for values that should be numeric or date-based.
- Record missing data explicitly instead of leaving blank fields, because blanks can be mistaken for an omitted entry rather than a true gap.
- Capture the review date and reviewer name after the data are complete, not while the sampling record is still being edited.
- Limit PII in the sample_collected_by and reviewed_by fields to what is necessary for accountability and internal audit trail purposes.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
This template records the data you need to prepare a wastewater Discharge Monitoring Report for a permitted outfall. It keeps the reporting period, sampling event details, lab results, flow data, noncompliance notes, and review status together in one log. That makes it easier to assemble a complete DMR package without hunting through lab emails and field notes.
Is this for every wastewater site or only permitted outfalls?
It is designed for permitted wastewater outfalls tied to an NPDES permit. If a facility has multiple outfalls, you can clone the template per outfall or add a clear outfall identifier for each record. It is not meant to replace a permit-specific monitoring schedule or the actual regulatory filing form.
How often should this log be completed?
Complete it each time a sampling event occurs and again when lab results, flow values, or corrective actions are available. Many teams also use a review step at the end of each reporting period to confirm that all required fields are filled before submission. The cadence should match the permit’s monitoring frequency and internal review process.
Who should fill it out and who should review it?
Field staff, operators, environmental coordinators, or lab coordinators can enter the sampling and result data, depending on your workflow. A supervisor, environmental manager, or designated certifier should review the log before submission. The review step is important because it creates a clear audit trail for what was checked and when.
What compliance issues does it help with?
It supports NPDES DMR preparation by organizing monitoring results, exceedances, missing data, and corrective actions in one place. It also helps document process upsets and noncompliance observations so the reporting record is easier to defend. The template should be customized to match the permit’s required parameters and any site-specific reporting rules.
What are the most common mistakes when using a discharge monitoring log?
Common mistakes include leaving out the reporting period, mixing data from different outfalls, and recording units inconsistently. Another frequent issue is documenting a lab result without the chain of custody or lab report number, which makes the record harder to verify. Teams also sometimes note an exceedance but forget the corrective action date or description.
Can this template be customized for different permits or facilities?
Yes. You can add or remove monitoring parameters, adjust the flow fields to match your permit units, and add conditional logic for site-specific upset or noncompliance questions. If your facility has multiple discharge points, separate logs or filtered views by outfall usually work better than one long shared record.
How does this compare with tracking wastewater data in spreadsheets or email?
A structured log reduces missed fields, inconsistent naming, and version confusion that often happen in ad hoc spreadsheets and email threads. It also makes review faster because the same fields appear in the same order for every reporting period. That consistency is especially useful when you need to show how a result was collected, reviewed, and prepared for submission.
What should I connect this log to in my workflow?
Many teams connect it to lab reports, chain-of-custody records, permit documents, corrective action trackers, and submission checklists. If your system supports it, link the log to document storage so reviewers can open the source report directly. Integrations are most useful when they reduce manual copying of results and help preserve an audit trail.
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...
-
Artificial intelligence in the workplace: boost productivity, streamline tasks, and empower employees with smarter, more meaningful work.
-
Discover 7 common intranet platform failures that exclude frontline workers—and the specific capabilities that close the gap for deskless teams.
-
Compare the top employee intranet platforms built for frontline, deskless, and shift-based workers in 2026, including MangoApps, Viva Connections, and more.
-
Internal communication helps employees respond faster in a crisis with clear alerts, preparation, and one trusted source for updates.
Ready to use this template?
Get started with MangoApps and use Wastewater Discharge Monitoring Report Log with your team — pricing built for small business.
