SWPPP Deficiency Notices in California Construction General Permit Reviews

SWPPP deficiency notices in California follow a handful of predictable patterns: gaps in what the plan document contains, mismatches between what the plan says and what is built on-site, and missed procedural deadlines inside the state's reporting system. Understanding which of these three categories a notice falls into is the fastest way to prevent one, and the fastest way to answer one correctly once it arrives.

What the California Construction General Permit requires from a SWPPP

The 2022 Construction General Permit, Order 2022-0057-DWQ, took effect on September 1, 2023, and it sets the baseline that every Stormwater Pollution Prevention Plan in California now has to meet. A deficiency notice is simply the state's way of saying a plan, or its execution, falls short of that baseline. Coverage applies to any project disturbing one acre or more, and it also applies to smaller lots that are part of a larger common plan of development, a rule that catches contractors who assume a half-acre parcel puts them under the threshold when the whole subdivision phase does not.

The permit requires a site-specific SWPPP, prepared and certified by a Qualified SWPPP Developer, and carried out on-site by a Qualified SWPPP Practitioner. Those two roles are not interchangeable, and the permit treats them as distinct functions with distinct responsibilities. The SWPPP itself has to include a site map showing drainage patterns, slopes, storm drain inlets, the property perimeter, and BMP locations; a risk-level determination that sorts the site into Risk Level 1, 2, or 3 based on sediment risk and the sensitivity of the receiving water; a set of Best Management Practices covering erosion control, sediment control, and general housekeeping; a Rain Event Action Plan for any site rated Risk Level 2 or 3; and the names and credentials of the responsible parties, including the Legally Responsible Person named on the permit.

None of this is static. The SWPPP is meant to change as the site changes, and the 2022 permit sets specific deadlines for amendments depending on whether the change is minor or major. Enrollment itself runs through SMARTS, the state's Stormwater Multiple Application and Report Tracking System, where the Notice of Intent gets filed, the Permit Registration Documents get uploaded, and a WDID number gets issued before any ground-disturbing work can start.

SWPPP Review and Deficiency Notices from the State and Regional Boards

A deficiency notice can come from either of two separate channels, and a project can clear one while failing the other. The first channel is document review inside SMARTS, where the State Water Board and the Regional Water Quality Control Boards look over the uploaded Permit Registration Documents, the SWPPP itself, inspection reports, and sampling data, checking for completeness and for internal consistency across the file. A plan can generate an administrative deficiency this way before an inspector has ever set foot on the property.

The second channel is physical inspection, carried out at the local level. Under Provision C.6 of the Municipal Regional Permit, Contra Costa municipalities and similar local permittees have to inspect construction projects directly, run an Enforcement Response Plan, and demand timely correction when something is found non-compliant. This local layer runs alongside the state CGP rather than replacing it, and the training behind it continues: the Contra Costa Clean Water Program held its C.6 Construction Stormwater Inspection Workshop on February 5, 2026, covering inspection protocols and enforcement response for the people who do this work in the field.

The Legally Responsible Person named on the permit carries the accountability for a deficiency notice and for any penalties that follow it. Regulators do not default to treating the QSD or the QSP as the liable party; the name on the permit is the name on the hook. Penalties can run into tens of thousands of dollars per violation, and each day a violation continues counts as a separate one. Inspectors can also issue a stop-work order independent of any fine, and for most contractors the delay that causes does more damage to the schedule and the budget than the penalty itself.

The documentation gaps that most commonly trigger deficiency notices

Most deficiency notices that could have been avoided trace back to what the SWPPP document contains or leaves out, not to anything failing on the ground. A site map that doesn't show drainage patterns, BMP locations, discharge points, and slopes in enough detail is one of the most common findings a reviewer flags, and a surprising number of these maps turn out to be recycled from an earlier project. Because the SWPPP has to be site-specific, a reused map is a deficiency on its face.

Risk-level determination is another frequent failure point. A site that actually qualifies as Risk Level 2 or 3 but gets filed as Risk Level 1 ends up missing the Rain Event Action Plan and the higher-frequency inspection schedule that the higher risk levels require, and that gap gets caught both during document review and later in the field, when the missing elements simply aren't there. Related to this is the REAP itself: Risk Level 2 and 3 sites have to include one, and submitting a plan without it, or with a REAP that doesn't speak to the site's actual discharge points and forecast thresholds, is one of the more routine citations regulators issue.

Credential documentation causes its own share of notices before anyone even evaluates the substance of the plan. The permit requires the QSD's name and certification, the QSP's name and certification, and the Legally Responsible Person's information, and leaving any one of these out generates an administrative deficiency on its own. Because the SWPPP is a living document, failing to amend it when conditions change, grading wraps up, new activity areas open, drainage patterns shift, is treated by inspectors the same way as any other non-compliant plan: an outdated SWPPP is a non-compliant SWPPP, full stop on the comparison to any other standard. Sites that drain into impaired waterways carry one more layer: a SWPPP has to address any applicable Total Maximum Daily Loads, and ignoring that requirement makes a plan deficient no matter how well it handles the standard erosion and sediment controls.

BMP selection and implementation failures that inspectors flag in the field

A SWPPP can be flawless on paper and still earn a field deficiency notice the moment what's installed on-site doesn't match what the plan describes, or doesn't perform the way the plan says it will. The CASQA BMPs Handbook lays out the standard practices inspectors are trained against, and workshops like Contra Costa's cover the same ground from the enforcement side, so the categories that generate notices in the field are well understood on both sides of the inspection.

Erosion control problems tend to center on bare soil left exposed past the permit's allowed window without mulch, hydroseeding, or erosion control blankets, and on stabilization measures that were installed correctly at first but haven't been maintained, torn blankets, fiber rolls knocked loose, mulch that's thinned out to nothing. Inspectors treat a degraded control the same as a missing one. Sediment control issues follow a similar pattern: silt fences and fiber rolls that have been overtopped or buried without repair, storm drain inlets that the SWPPP's own site map shows as protected but that have no protection installed, a direct contradiction between the plan and the ground that inspectors catch quickly, and sediment basins that were never built before grading started on the area that drains into them.

Good housekeeping failures round out the field category, and concrete washout is a specific enforcement priority in California: an absent washout area, one that's full, or one placed where discharge can reach a storm drain is a common citation. Fuel, paint, and chemical storage without secondary containment or spill kits nearby is another. The 2022 CGP also permits passive treatment technologies, but only when they're correctly designed and their performance is documented, so a passive system installed without proper design or without performance records creates both a field problem and a paperwork problem at once. The logic inspectors apply across all of this is consistent: any BMP that the SWPPP lists but that's missing, poorly installed, or unmaintained in the field is evidence not just of one bad control, but of a SWPPP that isn't being implemented as written, which turns a single BMP failure into a broader permit-implementation violation.

Inspection and monitoring reporting failures that generate notices independent of site conditions

A deficiency notice can land even when every BMP on the site works exactly as designed, because the permit's inspection and reporting obligations run on their own calendar, no matter what's happening in the field. The 2022 CGP requires weekly inspections at all risk levels in California, but the federal CGP allows a biweekly schedule paired with post-storm inspections. Beyond the routine weekly check, the permit requires a pre-event inspection within a defined window ahead of any forecast carrying a 50 percent or greater probability of precipitation and a quantitative precipitation forecast of 0.5 inches or more within 24 hours, what the permit calls a Qualifying Precipitation Event. That pre-event window runs 72 hours out under a standard forecast, but it extends to 120 hours when the forecast reaches further out. During-event and post-event inspections attach to the same qualifying storms. Skipping any one of these inspection types, regardless of whether the site itself is in good shape, is its own standalone violation.

Timing matters just as much on the submission side. Inspection reports, sampling results, and annual reports all carry their own deadlines for upload into SMARTS, and a late or missing submission is visible to reviewers without anyone having to visit the property. That visibility alone generates an administrative notice. Inspection logs also have to stay on-site and accessible at all times; an inspector who shows up and can't get to current logs can cite the project even if every control is working. Training records round out this category: the permit requires documentation that stormwater team members have received training, and subcontractors need documented training only if they're the ones conducting inspections. Missing training files appear repeatedly in routine inspector visits, and this finding doesn't need a storm or a failed BMP to surface.

SMARTS submission errors that create or compound deficiency notices

SMARTS is the single record the State Water Board works from, so an error inside the system becomes an official deficiency no matter how complete or accurate the paper file sitting in a project trailer happens to be. Permit Registration Documents get uploaded incomplete, unsigned, or citing the superseded 2009 permit order, 2009-0009-DWQ, instead of the current 2022 order, and reviewers read an outdated citation as a sign that the compliance process behind the document was never actually updated. A SWPPP sometimes doesn't match the risk-level classification filed in the Notice of Intent, and that kind of internal inconsistency between SMARTS records is one of the most reliable deficiency triggers there is, because the system makes the mismatch visible without any judgment call required.

Operators also miss the Notice of Termination once construction wraps up, which leaves the permit open and keeps generating annual-report obligations and fees for a project that's already finished. Annual reports themselves go missing or arrive late often enough that they show up in the system simply flagged as overdue, citable without anyone visiting the site. The WDID number that SMARTS issues carries weight beyond the state permit, too: many cities require it before they'll release a grading permit, so a SMARTS error that delays the WDID can stall a project at the local permitting counter before the state has issued any notice.

Responding to a Deficiency Notice and the Correction Timeline

A deficiency notice is a request for correction, not a penalty in itself, and it stays that way as long as the response is prompt, documented, and sent through the right channel. The first step is figuring out where the notice actually came from: a SMARTS document review, a Regional Water Board enforcement action, and a local MRP Provision C.6 inspection each route to a different responding authority and a different correction process. The notice itself will specify the deficiency and the corrective action required, along with a deadline, so the next step is simply reading it closely enough to know what's being asked.

If the deficiency is a documentation gap, the correction runs through the QSD, who has to prepare and certify an amendment and upload it to SMARTS. The 2022 CGP sets a single 30-calendar-day deadline for uploading any SWPPP amendment, and submitting the wrong amendment tier can draw its own citation on top of the original one. If the deficiency is a BMP installation or maintenance problem out in the field, the QSP corrects the condition, documents it with dated photographs and an updated inspection log, and uploads that record to SMARTS inside the notice's own deadline. A notice stemming from a Numeric Action Level exceedance, for pH or turbidity, calls for a different sequence entirely: investigating the source of the exceedance, adjusting the BMPs responsible, resampling, and filing a report with the Regional Water Board, with each of those steps carrying its own documentation requirement.

Practices that prevent most deficiency notices before the first inspector arrives

Because deficiency notices follow such a small number of repeating patterns, a disciplined routine before and during construction eliminates most of the exposure before a regulator ever opens the file. Before ground is broken, confirm whether the project triggers CGP coverage under the one-acre threshold or the common-plan-of-development rule, and bring a QSD in early enough to finish the risk-level determination, write the SWPPP, and file the Notice of Intent through SMARTS, since SMARTS timestamps don't leave room for argument later. Check that the SWPPP cites Order 2022-0057-DWQ rather than the superseded 2009 order, and confirm the WDID number is in hand before the grading permit gets pulled.

Once construction starts, match every BMP installation to the SWPPP's site map before grading begins, because every location the map shows has to be installed and working at the right phase of work. Treat the inspection schedule as a calendar obligation rather than a judgment call: weekly, pre-event within the required window, during-event, and post-event, each one logged and uploaded to SMARTS on time. Amend the SWPPP the moment site conditions, phasing, or activities change, and treat that amendment deadline as fixed, not flexible.

Firms running several permitted sites at once carry the highest exposure to exactly this kind of mechanical failure: a missed amendment deadline, a late SMARTS upload, a gap in the inspection log that nobody noticed until an inspector asked for it. Workflow tools that track a project's obligations against the permit's own calendar, flagging an amendment due in two weeks or a report due after the next storm, address this category directly. Their value isn't in replacing what a QSD or a QSP decides on-site; it's in making sure the obligations that don't require judgment at all, filing on day 14, uploading a log after a storm, don't fall through the gap between the people responsible for them.