Wastewater Discharge Sampling Log Template — NPDES tracking made clear

Overview

The Wastewater Discharge Sampling Log is a structured workplace form for recording one sampling event from the field through laboratory review. It organizes the details that matter for NPDES recordkeeping: when and where the sample was taken, what type of sample it was, how it was preserved, whether holding times were verified, who handled custody, and what the lab reported back.

Use this template when your team needs a repeatable record for routine discharge monitoring, resampling after an upset, or documenting a suspected permit exceedance. The form is especially useful when multiple people touch the sample, because it keeps the chain of custody and transfer timestamps in one place. It also helps reviewers confirm that the sample condition, preservation method, and transport method match the parameter requirements.

Do not use this as a general incident report or a broad environmental log. It is not meant to capture unrelated site issues, long narrative investigations, or every operational detail at the facility. If your program needs weather data, flow measurements, duplicate samples, or field calibration values, add those as optional fields with clear validation and progressive disclosure rather than crowding the core record. The goal is a clean, auditable sampling log that supports compliance review without collecting unnecessary PII or extra data.

Standards & compliance context

This template supports NPDES recordkeeping by documenting the sampling event, custody chain, and laboratory results in a single auditable record.
The form structure helps maintain data integrity by separating field collection details from lab analysis results and follow-up actions.
Use only the fields needed for the sampling program to align with GDPR data minimization and the minimum-necessary principle when no personal data is required.
If the form is exposed to external users or contractors, keep the interface accessible and readable in line with WCAG 2.1 AA expectations.
Avoid collecting unnecessary PII in collector or reviewer fields beyond what is needed for accountability and traceability.

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

Sampling Event Details

This section identifies the exact discharge event so the sample can be tied to the correct date, time, facility, permit, and outfall.

Sampling Date (required)
Date the sample was collected.
Sampling Time (required)
Time the sample was collected.
Facility Name (required)
Name of the facility associated with the discharge point.
NPDES Permit Number (required)
Permit identifier associated with this discharge location.
Discharge Outfall / Sampling Point (required)
Identifier for the outfall or sampling location.
Sampling Event Type (required)
Select the reason for the sampling event.

Sample Collection Details

This section documents how the sample was taken and preserved, which is critical for sample integrity and defensible results.

Sample Type (required)
Select the sample collection method.
Collection Method (required)
Method used to collect the sample.
Number of Sample Containers (required)
Total number of containers collected for this event.
Preservation Method (required)
Select all preservation methods applied to the sample.
Field Temperature (°C)
Measured sample temperature at collection, if applicable.
Sample Condition / Observations
Note any visible issues, odors, color, turbidity, or unusual field conditions.

Parameters and Holding Requirements

This section shows what was monitored and whether the sample met timing and custody requirements before analysis.

Parameters Monitored (required)
Select all parameters included in this sampling event.
Parameter Notes
Add any permit-specific notes, method references, or parameter exceptions.
Holding Time Verified (required)
Confirm that sample handling and transport met applicable holding-time requirements.
Custody Seals Intact on Transfer
Check if custody seals were used and remained intact during transfer.

Chain of Custody

This section creates the audit trail from collector to laboratory so the sample’s handling can be verified later.

Sample Collector Name (required)
Name of the person who collected the sample. Avoid collecting unnecessary PII.
Collector Title / Role
Job title or role of the sample collector.
Custody Transferred To (required)
Name or organization receiving custody of the sample.
Custody Transfer Date and Time (required)
Date and time when custody was transferred.
Transport Method (required)
Method used to transport the sample to the laboratory.
Chain-of-Custody Notes
Document any custody exceptions, delays, temperature excursions, or seal issues.

Laboratory Analysis Results

This section captures the lab’s reported findings and the supporting QA/QC notes needed to interpret them.

Laboratory Name (required)
Name of the laboratory that performed the analysis.
Laboratory Sample ID (required)
Unique identifier assigned by the laboratory.
Sample Received Date
Date the laboratory received the sample.
Results Summary (required)
Summarize analytical results, including units, qualifiers, and any exceedances.
QA/QC Notes
Include method deviations, blanks, duplicates, qualifiers, or other quality notes.
Laboratory Report Attached (required)
Confirm that the laboratory report or certificate of analysis is attached.

Compliance Review and Follow-Up

This section records whether the results triggered a permit issue and what action was taken next.

Permit Exceedance Observed? (required)
Indicate whether any result exceeded permit limits.
Exceedance Parameters
Select the parameters that exceeded permit limits.
Corrective Action / Follow-Up
Describe notifications, investigations, resampling, or corrective actions taken.
Reviewer Name
Name of the person reviewing the sampling record for completeness.

How to use this template

Enter the sampling event details first, including the date, time, facility name, permit number, outfall, and whether the sample was routine, follow-up, or another event type.
Record the sample collection details immediately after collection, using the correct sample type, collection method, container count, preservation method, field temperature, and observed sample condition.
List the monitored parameters and verify any holding-time or custody-seal requirements before the sample leaves the site.
Document the chain of custody by naming the collector, the person receiving the sample, the transfer time, and the transport method used to reach the laboratory.
Attach or reference the laboratory results, then note any QA/QC comments, report receipt date, and whether the results report is attached to the record.
Complete the compliance review section by marking any permit exceedance, naming the affected parameters, and recording the corrective action and reviewer.

Best practices

Use a date picker for sampling dates and a time field for collection and transfer timestamps so the record is consistent and easy to audit.
Mark required fields only where the information is truly necessary for compliance, and keep optional site-specific fields behind conditional logic.
Record the sample condition at the time of collection, not after the sample has been transported or stored.
Verify holding times before the sample leaves the site and document that verification in the log rather than relying on memory.
Capture the exact outfall and permit number for every event so results cannot be misattributed to the wrong discharge point.
Attach the lab report and chain-of-custody record to the same entry so reviewers do not have to search across systems.
If a permit exceedance occurs, document the corrective action in the same record as the result to preserve the audit trail.

What this template typically catches

Issues teams running this template most often surface in practice:

The sampling time is missing or entered inconsistently, which makes the event hard to verify against holding-time requirements.

The wrong outfall or permit number is recorded, causing the lab result to be linked to the wrong discharge point.

Preservation method or sample condition is left blank, weakening the chain-of-custody record.

Custody transfer details are incomplete, especially the transfer_datetime or custody_transferred_to field.

Holding time is assumed rather than explicitly verified before shipment.

The lab report is referenced in notes but not actually attached to the record.

A permit exceedance is noted without naming the affected parameters or documenting corrective action.

Common use cases

Municipal WWTP compliance sampling

A wastewater treatment plant uses the log to document routine effluent samples at a permitted outfall, including custody transfer to the contract lab and any review of exceedances. The structured fields make it easier for operators and compliance staff to reconcile field notes with lab results.

Food processor discharge follow-up

An environmental manager records a follow-up sample after a high-strength discharge event to show what was collected, how it was preserved, and whether the lab confirmed compliance. The corrective_action field captures the response in the same record.

Industrial lab chain-of-custody

A plant technician uses the template to document sample handoff from the field to the courier and then to the laboratory. This is useful when multiple people handle the sample and the audit trail must show each transfer.

Stormwater-related discharge review

A facility with intermittent discharge uses the log for event-based sampling when a storm or process upset triggers collection. The sampling_event_type field helps distinguish these records from routine monitoring.

Frequently asked questions

What is this template used for?

This template records a single wastewater discharge sampling event from collection through laboratory reporting. It captures the sampling date and time, outfall, sample handling details, chain of custody, and any permit exceedance follow-up. Use it when you need a consistent record for NPDES compliance review and internal audit trail.

Is this for every routine sample or only special events?

It works for both routine monitoring and event-based sampling, such as a scheduled compliance sample, a resample after a process upset, or a confirmation sample after a suspected exceedance. The sampling_event_type field helps distinguish the context without changing the core record structure. If your site uses separate logs for grab, composite, or storm-related events, this template can still be adapted with conditional logic.

Who should complete the log?

The person who collects the sample should complete the field collection and chain-of-custody sections, and a supervisor or compliance reviewer should complete the follow-up section. In many facilities, environmental staff or EHS personnel own the log, while operators provide supporting details. The key is that each field is filled by someone who can verify the facts, not by guesswork after the fact.

What compliance issues does this help with?

It supports NPDES recordkeeping by documenting sample identity, preservation, custody transfer, and lab receipt details. It also helps show that holding times were verified and custody seals remained intact, which are common audit questions. If a permit limit is exceeded, the corrective_action and reviewer_name fields create a clear record of response.

What are the most common mistakes when using a sampling log like this?

Common mistakes include leaving out the exact sampling time, using free-text where a controlled field would be clearer, and forgetting to record custody transfer details. Another frequent issue is documenting results without linking them back to the correct outfall or permit number. This template reduces those gaps by separating event details, custody, lab results, and review actions.

Can this be customized for grab samples, composite samples, or field screening?

Yes. The sample_type, collection_method, and sampling_event_type fields are designed for customization, and you can add conditional logic for site-specific parameters or field screening notes. If your program needs additional fields such as flow conditions, weather, or duplicate samples, those can be added without changing the core compliance record.

How does this compare with an ad-hoc spreadsheet or notebook?

An ad-hoc log often misses one of the details needed to prove sample integrity, such as preservation method, transfer time, or lab sample ID. This template keeps the workflow in one structured form so the record is easier to review, audit, and hand off. It also makes it simpler to standardize data entry across multiple sampling events and staff members.

What should be attached or linked to the record?

Attach the lab report, chain-of-custody form, and any supporting field notes or calibration records if your process requires them. The results_report_attached field helps confirm that the analytical report is part of the record, not stored elsewhere with no link. If your organization uses an LIMS or document system, this template can be paired with those records for a complete audit trail.

Related templates

Forms

Employee Onboarding Form

Employee Onboarding Form for collecting new hire details, tax references, direct deposit, emergen...

Forms

Workplace Incident Report

A Workplace Incident Report template for documenting injuries, illnesses, and near-misses with th...

Inspections

Forklift Daily Pre-Shift Inspection

Forklift Daily Pre-Shift Inspection template for recording pre-use checks, defects, and out-of-se...

Sop

Fire Evacuation Procedure

A fire evacuation procedure that tells each role exactly what to do from alarm to accountability....

Hr Policy

Anti-Harassment & Anti-Discrimination Policy

Anti-Harassment & Anti-Discrimination Policy template for defining prohibited conduct, reporting ...

Workspace

Accounts Receivable Collections Workspace

An accounts receivable collections workspace for aging review, dispute tracking, escalation, and ...

Ready to use this template?

Get started with MangoApps and use Wastewater Discharge Sampling Log with your team — pricing built for small business.

Get Started Customize with AI