What discharge monitoring records must be submitted to CIWQS under California Water Code § 13160?

CIWQS — California's Integrated Water Quality System — is the primary online platform where NPDES permittees submit discharge monitoring reports and self-monitoring compliance data to Regional Water Quality Control Boards. For environmental consultants preparing these submittals, the system generates a record of each filing. Understanding what that record must contain, and what happens when CIWQS submissions are disputed, is core compliance knowledge.

The authority is Cal. Water Code § 13160. The specific implementation lives in individual NPDES permit conditions and SWRCB program guidance.

What information must a CIWQS discharge monitoring report contain?

A discharge monitoring report (DMR) submitted through CIWQS must include:

Monitoring period: The start and end dates of the monitoring period covered by the report. If a permittee submits late or covers the wrong period, the error may not be caught until a Regional Board compliance review.

Parameter-by-parameter sampling results: Each monitored parameter identified in the permit — effluent limits for pH, TSS, BOD, metals, bacteria, or other constituents — must be reported for each required monitoring event. Missing data must be flagged with an explanation (e.g., no discharge occurred, equipment malfunction, lab error).

Permit exceedances: Any exceedance of a permit limit must be identified and accompanied by an explanation and, in many cases, a corrective action description. Self-reporting of exceedances is required — and failing to report a known exceedance can be treated as a separate violation.

Certification signature: The DMR must be certified and signed by a responsible corporate officer, principal executive officer, or authorized signatory as defined by the permit. Electronic signatures through CIWQS satisfy this requirement when the permit authorizes electronic submission.

What does CIWQS generate as a submission record?

When a DMR is submitted through CIWQS, the system assigns a submission identification number and records a timestamp. The submitter can access a printable confirmation of the filing from their CIWQS account.

This confirmation record matters. A Regional Board audit or enforcement proceeding may rely on CIWQS records to establish whether a DMR was filed by the permit deadline. If a consultant submits a DMR on behalf of a discharger, both the submission itself and the CIWQS confirmation record should be retained in the project file — see DTSC submittal tracking for how the same principle applies to agency submittals outside portal systems.

What happens if a CIWQS report has errors or is submitted late?

Late DMR submissions are tracked in CIWQS. Regional Boards generate compliance reports from CIWQS data — late or missing DMRs flag automatically and may trigger a notice of violation or compliance inspection. The system's timestamp is the authoritative record of when a submission was received.

For DMRs with data errors, CIWQS allows amended submissions. The amended report supplements the original — the original submission record remains. Consultants amending a previously filed DMR should document the reason for the amendment and ensure the discharger's file retains both the original submission confirmation and the amended version.

What are the retention requirements for discharge monitoring records?

NPDES permit conditions typically require five years of DMR data and supporting monitoring records. Supporting records include:

• Laboratory analytical reports with chain-of-custody records
• Field sampling logs and calibration records for in-situ monitoring equipment
• Flow measurement records
• Any calculations used to convert raw monitoring data to reported values

These records must be available for production if a Regional Board requests them during a compliance inspection or in response to a records request. Consultants who maintain monitoring records on behalf of clients should build a clear handoff process into project closeout so records are transferred — not left in the consultant's file when the project ends.

How does CIWQS connect to enforcement proceedings?

Regional Board enforcement actions — Administrative Civil Liability orders, Cease and Desist Orders, and cleanup and abatement orders — typically rely on CIWQS data as a primary evidence source. A discharger's CIWQS filing history is reviewed to establish whether violations were reported, how consistently the permittee submitted DMRs, and whether reported exceedances were accompanied by required corrective actions.

Consultants who prepare DMRs should treat CIWQS submissions as formal regulatory records, not routine data entry. The submission is a legal certification of the data it contains. Errors in CIWQS can create enforcement exposure even when the underlying monitoring data is accurate. Confirm current CIWQS submission requirements and any permit-specific electronic reporting conditions with the Regional Board.

For environmental consulting firms, enforcement proceedings against a client also delay project closeout and invoice collection. The same delivery confirmation record that establishes timely submission also closes the billing loop — see why environmental consulting firms wait 75+ days to get paid.

What are the common failure modes in CIWQS discharge monitoring submissions?

DMR submitted on time but confirmation not retained. A monthly DMR was submitted through CIWQS before the permit deadline. The consultant did not retain the CIWQS confirmation email or print the confirmation PDF. Six months later, the Regional Board's compliance review flags the submission as missing for that period. CIWQS's record is the authoritative timestamp — and the consultant has no independent evidence to corroborate it.

Amendment filed without retaining the original submission record. A DMR was submitted with an error in a parameter result. The consultant caught the error and filed an amendment through CIWQS. The original submission confirmation was not retained before the amendment was filed. In an enforcement proceeding, the Regional Board's record shows an amended submission and the question becomes when the original was filed and whether it was timely. The consultant cannot reconstruct the original submission timestamp from the amended record alone.

Consulting engagement ends; monitoring records stay in the consultant's file. A multi-year NPDES compliance engagement concludes. The consultant's file contains five years of DMR data, sampling records, and CIWQS confirmations. Those records are transferred to the client at closeout — or they are not, and the client later faces a Regional Board records request with no underlying documentation. The handoff process is the gap.

Mainstay timestamps and preserves each submission record at the file level — so the CIWQS confirmation, the specific DMR version, and the delivery timestamp are all on record in a form that survives staff turnover, platform migrations, and engagement closeouts.

---

Mainstay coordinates the work; it is not a compliance advisor and makes no regulatory determination. Always confirm requirements with the relevant agency.