SWPPP Revision History: Why Version Control Matters

Track SWPPP revisions by logging every change with a date, the reason, the person who made it, and the version that resulted — and keep prior versions intact instead of overwriting them. The California Construction General Permit requires the SWPPP to be revised when site conditions or operations change, and inspectors expect the plan on site to match the conditions on the ground, backed by a history showing when and why each change occurred.

Why does the Construction General Permit care about revision history?

The CGP (Order 2009-0009-DWQ, amended by 2010-0014-DWQ and 2012-0006-DWQ) treats the SWPPP as a living document, not a binder produced once at NOI filing. The permit requires the SWPPP to be revised when there's a change in BMPs, site operations, or conditions that affects discharge, and to record those revisions — confirm the exact provisions and section references in the current permit at the SMARTS portal.

That last clause is what trips firms up. The Regional Water Quality Control Boards conducting inspections aren't only checking that you have the right BMPs. They're checking whether the plan was kept current as the site evolved from grading to vertical construction to stabilization. A SWPPP that shows a single version dated many months ago, on a site that's gone through several distinct phases, reads as a plan nobody maintained — regardless of how good the current BMPs are.

What does a regulator actually want to see in a revision log?

When a Regional Board inspector reviews revision history, they're generally looking for several things on each entry:

• Date of the revision — and whether it tracks logically against the construction schedule and weather events
• What changed — specific BMP additions, removals, or relocations, not "updated plan"
• Why it changed — the triggering condition (phase change, failed BMP, new disturbed acreage)
• Who authorized it — tying back to the QSP or environmental consultant of record

Vague entries undercut the whole record. "Revised per inspection 5/12" tells an inspector nothing they can verify. "Added fiber rolls along east perimeter following a measured rain event; relocated concrete washout from NW corner to staging area" is checkable against the site and the rain log.

How do I track SWPPP revisions for a client without losing the old versions?

The most common failure that environmental consulting firms run into is overwriting. A consultant opens the existing SWPPP file, edits it, saves it under the same name, and prints the new copy for the site binder. The prior version is gone. If a discharge or enforcement question arises about conditions months ago, there's no way to show what the plan said at that time.

A defensible workflow keeps each revision as a discrete, frozen version:

1. Never edit in place. Each revision produces a new dated file — ProjectName_SWPPP_v4_2026-04-18, not a re-saved SWPPP_final.
2. Maintain a revision table inside the document that lists every version, date, change summary, and author. This is the page an inspector flips to first.
3. Record when each version reached the site. A revision that exists in your office but never made it into the on-site binder doesn't help the client during an inspection.

That third point is where delivery and version control intersect. A revision only counts if the current version is the one actually on site — and if you can prove when it got there. Mainstay produces a tamper-proof record of every send, so when you transmit SWPPP v4 to the superintendent, there's a fixed timestamp showing the controlling version reached the field. If a later question arises about what the site should have had on April 18, the delivery record answers it.

How does revision tracking affect getting paid?

Revisions are billable work, but they're easy to lose track of when they happen reactively — a phone call after a failed BMP, a quick edit before a storm. Firms that treat each revision as an undocumented favor leave real fees on the table.

Tying billing to delivery closes that gap. When the revised SWPPP is transmitted to the client and that send is logged, the same event that protects you in an inspection also marks the work as delivered — which is the cleanest possible trigger for invoicing. The revision history becomes both your compliance record and your billing record, drawn from the same set of timestamped sends.

What's the minimum a small firm should run?

You don't need enterprise software. You need three habits applied consistently across every project: a never-overwrite file naming convention, an in-document revision table maintained at the moment of change, and a verifiable record of when each version was delivered to the field. Done together, those three keep the plan on site matching the conditions on the ground — which is the question every inspection ultimately asks.

---

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 General Permit (Construction Stormwater) — State Water Resources Control Board
• Stormwater Multiple Application and Report Tracking System (SMARTS)
• State Water Resources Control Board — Stormwater Program
• U.S. EPA — Stormwater Discharges from Construction Activities
• 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.