How to Amend a SWPPP Mid-Project (Amendment Process)

You amend a SWPPP by revising the affected sections, recording the change in the amendment log with a date and rationale, and getting sign-off from the credentialed preparer. Under California's Construction General Permit (Order 2022-0057-DWQ — confirm the current version at the SMARTS portal), most amendments stay on-site — you don't resubmit to the Regional Water Board. What you cannot skip is documentation: the record of what changed, when, and why is what an inspector actually asks for.

When do I actually have to amend a SWPPP?

The permit requires amendment whenever a change in construction or operations could materially affect the discharge of pollutants. In practice that means:

• A change in grading, phasing, or site layout that moves or resizes disturbed area
• New or relocated BMPs — swapping fiber rolls for a gravel bag berm, adding a concrete washout
• A change in the QSD or QSP of record
• Corrective actions after an inspection finding or a numeric action level exceedance
• A Risk Level reclassification (e.g., a project that crosses into Risk Level 2 after a sediment risk recalculation)

You do not need to amend for routine BMP maintenance or for a change already contemplated in the original plan. The test is whether the change alters the pollutant-discharge picture the SWPPP describes.

Do I have to resubmit the amended SWPPP to the Water Board?

For most sites, no. The CGP treats the SWPPP as a living site document. Amendments are made and retained on-site and produced during inspection. You update your project record in SMARTS (the State Water Board's Stormwater Multiple Application and Report Tracking System) when the change affects information the permit requires you to certify — a new Legally Responsible Person, a change in disturbed acreage that shifts your risk level, or a change to the QSD/QSP.

Where firms get burned is assuming "no resubmittal" means "no record." It doesn't. If the Regional Board requests your SWPPP during an audit and the on-site version doesn't match the conditions in the field — or the amendment log has a gap — that's the finding.

What does a defensible amendment log look like?

Every amendment entry should carry, at minimum:

• Amendment number (sequential — 1, 2, 3)
• Date the change was made
• Description of what changed and which SWPPP section/sheet it affects
• Reason (inspection finding, phase change, agency request)
• Name and credential of the person authorizing — the QSD when the amendment affects plan design, the QSP for field-level corrective actions
• Reference to any related inspection report or REAP

The failure mode isn't the amendment — it's proving the sequence held together. When a change happens in the field, the QSP notes it, the QSD updates the plan, and the client's PM signs off, and each of those moves usually lives in a different inbox. Weeks later nobody can produce a clean chain showing the field change and the revised sheet in the right sequence. This is the specific gap Mainstay closes: every send — the marked-up sheet, the revised SWPPP, the sign-off request — carries a tamper-proof timestamp, so the amendment log and the delivery record line up when someone asks for both.

How do I keep the field version and the office version in sync?

Two rules that survive audits:

1. One controlled copy. The SWPPP on-site is the copy of record. If your team edits a PDF in the office while the binder in the trailer says something else, you have two SWPPPs and neither is defensible. Distribute the amended version with a dated transmittal and confirm it landed.

2. Amend before the field changes, not after. When a phase change is planned, amend the SWPPP so the BMPs are in place before ground moves. Retroactive amendments — dated after the disturbance they describe — are exactly what inspectors flag as backdating.

When can I bill for amendment work?

Amendments are often out-of-scope revisions triggered by client-side changes or agency requests — real billable work that gets written off because nobody can point to the moment it was delivered. Tie the invoice to the delivery event: when the revised SWPPP and amendment log go out with a timestamped record, the billing trigger is the delivery itself, not a monthly guess at hours. That's the difference between recovering amendment work and eating it.

---

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

• Construction Stormwater Program — State Water Resources Control Board
• Stormwater Multiple Application and Report Tracking System (SMARTS)
• State Water Resources Control Board
• California Stormwater Quality Association (CASQA)
• U.S. EPA National Pollutant Discharge Elimination System (NPDES) Stormwater Program

---

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.