June 9, 2026

NPDES Permit Delivery Requirements California

California's NPDES permits, including the Construction General Permit (Order 2022-0057-DWQ), require SWPPPs and related records be submitted electronically through SMARTS and retained for a defined period — confirm the current retention term in the permit. The permit specifies who must certify documents, when uploads are due relative to construction phases, and that records remain available to the Water Boards on request. Delivery requirements are about timing, certification, and retention — not just sending a file.

California's NPDES permits don't say "email the SWPPP to the client." They require electronic submission through the State Water Board's SMARTS database, certification by a designated person, retention for a defined period, and availability to inspectors on request. For most construction-sector work, the governing document is the Construction General Permit (Order 2022-0057-DWQ), and its delivery language is more specific than firms tend to assume.

What does the Construction General Permit actually say about submission?

The current Construction General Permit (CGP) requires the legally responsible person (LRP) — usually the landowner or developer — to file Permit Registration Documents (PRDs) through SMARTS before construction begins; confirm the current effective date and version at the SMARTS portal. PRDs include the Notice of Intent, the risk assessment, the site map, and the SWPPP itself. These aren't delivered to a regional inspector by mail; they're uploaded to a state system that timestamps the submission and ties it to a WDID number.

The practitioner consequence: your SWPPP isn't "delivered" when you send the PDF to your client. It's delivered when the LRP certifies and submits it in SMARTS. If your client sits on it for two weeks, the regulatory clock — and your liability for the gap — keeps running.

Who is allowed to certify and submit the documents?

This is where firms get exposed. Under the CGP, the SWPPP must be developed by a Qualified SWPPP Developer, but the submission in SMARTS must be certified by the LRP or a Duly Authorized Representative they've formally designated in the system. Your firm can prepare and even upload, but the certification of accuracy is a named legal act by a specific person.

When a Water Board inquiry asks "who submitted this and when," the answer comes from SMARTS metadata, not your sent-mail folder. If there's a dispute about whether the consultant delivered a complete SWPPP to the client in time for the client to certify it, the email trail is the only record — and email trails are editable, deletable, and routinely lost in staff turnover.

What does the permit require for record retention?

The CGP requires that the SWPPP and all associated records — inspection reports, sampling data, rain event action plans, corrective actions — be retained and available for a defined period after the Notice of Termination is filed; confirm the current retention term in the permit at the SMARTS portal. The Water Boards can request these at any point in that window, and during an active enforcement action they will.

"Available" means retrievable on demand, with the version that was actually in effect on the date in question. A SWPPP gets amended as site conditions change. If an inspector asks for the SWPPP that governed work on March 14, you need that version — not the current one, not a reconstruction.

What happens when the delivery record is the dispute?

Most enforcement friction in small-firm consulting isn't about whether the work was good. It's about whether a document reached the responsible party in time, and whether anyone can prove it. A client says they never received the updated SWPPP before the rain event. The consultant says they sent it. Without a tamper-proof record of the send — recipient, timestamp, document version, and confirmation of receipt — the firm absorbs the risk by default.

This is the specific problem Mainstay addresses: it produces a tamper-proof record of every delivery, so the question "did the consultant deliver the SWPPP, and when" has a verifiable answer that doesn't depend on an inbox. The same delivery event can trigger billing, so the firm gets paid when the work is provably handed off rather than waiting on an invoice nobody disputes the work but everyone disputes the date.

How does this differ across permit types?

The CGP is the most common, but the principle holds across the NPDES landscape. Industrial General Permit (Order 2014-0057-DWQ) dischargers file Annual Reports and monitoring data through SMARTS on a fixed annual schedule — confirm the current reporting dates in the permit. Municipal MS4 permits carry their own reporting timelines and certification requirements. Individual NPDES permits issued by Regional Water Quality Control Boards may specify submission methods directly in the permit language.

In every case, "delivery" is defined by the permit — a submission channel, a certifying party, a deadline, and a retention period — not by whatever your firm has historically done. Read the actual order. Confirm the SMARTS workflow for your permit type. And keep a delivery record you can produce years from now without depending on a single person's memory.

Mainstay coordinates the delivery and documentation of environmental compliance work — it is not a compliance advisor and makes no regulatory determination. Always confirm requirements with the relevant agency.

Sources

This post is for general informational purposes only. Mainstay coordinates the delivery and documentation of environmental compliance work — it is not a compliance advisor and makes no regulatory determination. Regulatory requirements vary by permit type, jurisdiction, and project conditions. Always confirm applicable requirements with the relevant agency or a qualified professional.