What documentation do Regional Water Quality Control Boards require for NPDES compliance reports?

Regional Water Quality Control Board compliance documentation is not one thing. It is nine things — one for each Regional Board — and within each region, it varies by permit type, permit conditions, and discharger category. What environmental consultants need to know is not a universal checklist. It is what their client's specific permit requires, and what constitutes a defensible record that the permit conditions were met.

Cal. Water Code § 13260 establishes the general obligation to file reports of waste discharge. Everything specific flows from there — and from the permit itself.

What types of reports do RWQCB permits require?

NPDES permit compliance reporting falls into several categories:

Discharge Monitoring Reports (DMRs): The primary periodic compliance filing for most NPDES permittees. DMRs include monitoring data — effluent concentrations, flow rates, mass loading calculations — submitted on a schedule set by the permit (monthly, quarterly, or annually depending on permit conditions). Each DMR must be signed by a responsible corporate officer or authorized representative under penalty of law.

Annual compliance reports and certifications: Many individual NPDES permits require an annual summary of compliance status, including any permit exceedances, corrective actions taken, and a certification that the discharger is in compliance with all permit conditions. The exact format varies by permit and region.

Stormwater compliance reports: Under the Construction General Permit (CGP), construction site operators file reports through SMARTS, SWRCB's online tracking system. Rain event action plans (REAPs), post-rain-event reports, and annual reports are submitted electronically with SMARTS generating confirmation records.

Special studies and compliance schedules: Permits that include a compliance schedule for meeting future limits may require periodic progress reports. These have independent deadlines and delivery requirements.

How does SMARTS work for construction stormwater compliance?

The Construction General Permit is administered via SMARTS, the Stormwater Multiple Application and Report Tracking System. Project operators (LRPs and operators) file electronically — SMARTS generates a submission confirmation with a timestamp and record number. For construction stormwater work, the SMARTS confirmation is the primary delivery record.

Consultants preparing REAP submittals, annual reports, or inspection reports on behalf of construction clients should retain SMARTS confirmation records for each submission. If a question arises about whether a REAP was filed before a qualifying rain event, the SMARTS timestamp is the evidence.

What constitutes a defensible compliance record for RWQCB submittals outside SMARTS?

Not all RWQCB submittals route through a portal with automatic confirmation. Individual NPDES permittees often submit DMRs and compliance reports by email to a named permit compliance contact at the Regional Board. Municipal separate storm sewer system (MS4) permittees submit annual reports that may go by email or hard copy depending on the permit.

For submittals outside SMARTS, the documentation gap is real. A Regional Board staff contact who leaves their position may not transfer receipt records to the next staff member. Email confirmations are informal and file-specific acknowledgment is not guaranteed. Consultants who need to prove a compliance report was submitted by the permit's deadline — and that the specific file submitted was the final version — need a delivery record beyond an email in a Sent folder.

What do permit conditions typically specify about delivery method and timing?

Check current permit conditions — they govern. Some NPDES permits specify that reports are due by a date certain and must be postmarked or received by that date. Others treat electronic submission as of the date transmitted. The distinction matters if a deadline dispute arises.

A common failure mode: a report is emailed on the due date to a regional staff contact who is on leave. The report sits unread. The permit's deadline passes. Whether the submission was timely depends on whether the permit conditions measure "submitted" by transmittal or by receipt — and the consultant has a Sent folder record but no confirmation the report landed. Consultants should document both the transmittal and, when possible, confirmation of receipt. That confirmation gap — delivery documented but receipt unconfirmed — is also what delays invoicing; see why environmental consulting firms wait 75+ days to get paid.

How long must RWQCB compliance records be retained?

Retention requirements vary by permit. Many NPDES permits require five years of DMR data and supporting records. The Construction General Permit requires retention of records for three years after the Notice of Termination is filed. Confirm the specific retention requirement in the permit conditions — and build record retention into the project closeout process, not as an afterthought.

What are the common failure modes in RWQCB compliance report documentation?

Report delivered to a staff contact who has since left the agency. The consultant emailed a compliance report to the named permit compliance contact. That contact left the Regional Board six months later. The replacement staff member has no record of the submission. The consultant's Sent folder shows the email. Without a delivery confirmation tied to the specific file, the submission record depends on the Regional Board's internal email retention — which is not guaranteed.

SMARTS confirmation not retained after portal submission. The construction site annual report was submitted through SMARTS on time. The consultant's project file has a screenshot of the submission screen but not the system-generated confirmation email or PDF. SMARTS interface changes two years later make the screenshot ambiguous. The Regional Board's record is the authoritative timestamp; the consultant cannot independently corroborate it.

Final version not the version confirmed received. A DMR was submitted with a data entry error. The consultant corrected the error and resubmitted. The original submission confirmation was not retained. In a Regional Board compliance review, the record shows an amended submission — and the timeline of corrections becomes the subject of inquiry rather than the data itself.

Mainstay logs the delivery event and generates a SHA-256 receipt tied to the specific file submitted — so the file version and the confirmed receipt timestamp are both on record, independent of whether the receiving staff contact is still in their role two years later.

---

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