California CGP SWPPP Requirements: What Consultants Get Wrong

California's 2022 Construction General Permit (Order 2022-0057-DWQ, in effect since September 1, 2023) requires a site-specific SWPPP for any construction project disturbing one acre or more, developed by a certified QSD and uploaded to SMARTS before the Notice of Intent is filed. The plan has to carry a risk-level determination, site maps, risk-appropriate BMPs, and — for Risk Level 2 and 3 sites — a rain event action plan and sampling protocol. Most environmental consulting firms know this. The liability shows up in the gaps between "we did it" and "we can prove we did it."

Where does the risk-level determination actually go wrong?

The risk-level calculation combines a sediment risk score (based on the R-factor, K-factor, LS-factor, and cover) with a receiving-water risk score. Consultants get the sediment risk math right and then miss the receiving-water half — specifically whether the project discharges to a sediment-impaired 303(d)-listed water or one with a sediment TMDL.

That single input can push a site from Risk Level 1 to Risk Level 2, which triggers additional monitoring and reporting obligations, including a rain event action plan — confirm the exact requirements for each risk level in the current permit. If you determine Level 1 for a site that should have been Level 2 and a Regional Board inspector disagrees, you are not looking at a paperwork fix — you are looking at a period where required sampling never happened and can never be recreated. Pull the current 303(d) list before you finalize the score, not after.

Why do consultants lose SWPPP amendment battles?

The permit requires the SWPPP to be revised whenever there is a change in construction activity or BMPs that could affect discharge. In practice, projects change constantly — grading phases shift, a Risk Level 2 site adds a concrete washout, a subcontractor relocates the stabilized construction entrance.

The failure is almost never the amendment itself. It is the record of when the amendment was made and when the QSP or contractor received it. When a discharge event occurs and the Regional Board asks for the SWPPP that was in effect that day, "we emailed the update sometime that week" is not a defensible answer. You need the version, the timestamp, and proof it reached the site.

This is a delivery-record problem, not a document problem. Mainstay was built for exactly this — every send generates a tamper-proof record of what went out and when, so the SWPPP version in effect on a given date is provable rather than argued.

What gets missed on the Rain Event Action Plan?

For Risk Level 2 and 3 sites, a Rain Event Action Plan (REAP) must be developed in advance of a likely precipitation event, based on National Weather Service forecast probability — confirm the current triggering threshold and timing in the permit. The common gap is treating the REAP as an annual document instead of an event-triggered one.

Each qualifying storm needs its own REAP, prepared in advance, showing the specific BMP deployment for that event and the responsible personnel. Inspectors may check these against the actual NWS forecast history. A site that discharged during a qualifying forecast event with no corresponding REAP has a clear, dated deficiency that no retroactive plan can close.

How do sampling and reporting deadlines create exposure?

Risk Level 2 and 3 sites require monitoring during qualifying rain events, with results compared to numeric action levels (NALs) for parameters such as pH and turbidity — confirm the applicable sampling requirements and NALs in the current permit. NAL exceedances trigger reporting obligations in SMARTS, and the CGP sets an annual reporting deadline — confirm the current due date at the SMARTS portal.

The exposure here is timing. When sampling, analysis, and SMARTS entry pass through email threads and lab portals, the deadline slips quietly — and the firm carries the professional liability for the missed filing even when the delay started with a lab. Tying your invoice to confirmed delivery of the deliverable, rather than to a calendar date, keeps cash flow attached to the work actually leaving your office and reaching the client or the Board.

What documentation survives an audit?

The permit requires that SWPPP-related records be retained and available for a period following the Notice of Termination — confirm the current retention period in the permit. When a firm gets pulled into a third-party citizen suit under the Clean Water Act — which occurs in California — the discovery request is for dated delivery records, not just the plans themselves.

Firms that keep clean, timestamped proof of every SWPPP send, amendment, and report walk out of those disputes. Firms relying on reconstructed email chains do not. The plan being correct is table stakes; being able to prove what you delivered and when is the actual shield.

---

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

• California Construction Stormwater Program - State Water Resources Control Board
• Stormwater Multiple Application and Report Tracking System (SMARTS)
• California Integrated Report (Clean Water Act Sections 303(d) and 305(b))
• U.S. EPA National Pollutant Discharge Elimination System (NPDES) Stormwater Program
• California Stormwater Quality Association (CASQA)

---

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.