Common SWPPP Violations and How to Avoid Them

Stormwater inspectors rarely cite something exotic. The findings that show up on inspection reports and in federal enforcement actions are almost always the same handful of failures, repeated across thousands of construction sites. Knowing which ones get cited most often — and the practical habit that prevents each — is the difference between a routine inspection and a stop-work order.

This guide walks through the construction stormwater violations that come up again and again under the EPA's Construction General Permit (CGP) and equivalent state permits, the fix for each, and what real enforcement looks like when these problems are left unaddressed.

Why these violations matter

Land disturbance during construction exposes bare soil to rain and runoff. Sediment, concrete slurry, fuel, and other pollutants wash off the site into storm drains, ditches, and streams. The Clean Water Act regulates these discharges, and the Stormwater Pollution Prevention Plan (SWPPP) is the document that proves you are managing them.

When a SWPPP is missing, ignored, or out of date, the site is operating without a defensible compliance record. Inspectors — whether from the EPA, a state agency, or a municipal stormwater program — look first at the paperwork, then at the dirt. Gaps in either one are where citations come from.

The most-cited construction stormwater violations

1. No SWPPP available on site

The first thing an inspector asks for is the SWPPP itself. The permit requires that a current copy be kept at the construction site (or a nearby field office) and made available on request. A plan sitting on a server back at headquarters, or a version that predates the current site conditions, counts as not having one.

The fix:

• Keep a complete, current copy on site at all times — a printed binder, a tablet, or both.
• Make sure the version on site reflects the work actually happening, including any phase changes and added controls.
• Tell field staff where it lives so anyone can produce it when an inspector arrives unannounced.

2. Missing or late inspections

Most permits require routine site inspections on a set cadence — commonly every seven or fourteen days, plus after qualifying rain events. Skipped inspections, or inspections that happened but were never written up, are among the most frequently cited problems because the gap is obvious in the record.

The fix:

1. Lock the required cadence into a recurring schedule, not someone's memory.
2. Assign a trained, qualified inspector and a clear backup for vacations and turnover.
3. Document every inspection — date, conditions, findings, and corrective actions — and do it at the time, not from recollection weeks later.
4. Track rain events so post-storm inspections actually get triggered and logged.

3. Failed or unmaintained BMPs

Best Management Practices (BMPs) are the physical controls — silt fence, inlet protection, wattles, check dams — that keep sediment on site. Installing them is not enough. Inspectors routinely cite controls that have failed and were never repaired.

Two classic examples:

• Undermined silt fence. Fence that was never trenched in, or that water has scoured a channel beneath, lets runoff pass straight through. The fence is technically present but doing nothing.
• Unprotected inlets. Storm drain inlets without working protection send sediment directly into the system, exactly what the SWPPP is supposed to prevent.

The fix:

• Install BMPs the right way the first time — silt fence trenched and keyed into the soil, inlet protection sized and seated correctly.
• Treat every routine inspection as a maintenance trigger: note damaged or undermined controls and repair them promptly, before the next storm.
• Replace controls that are at the end of their useful life rather than patching them indefinitely.

4. Sediment tracking onto public roads

Tires and equipment carry mud off the site and deposit it on adjacent streets, where the next rain washes it into storm drains. Track-out is highly visible, easy for an inspector or a neighbor to spot, and a common source of complaints and citations.

The fix:

• Install and maintain a stabilized construction entrance — rock pads sized to knock mud off tires.
• Inspect the entrance regularly; once it clogs with fines it stops working.
• Sweep or clean tracked sediment off public roads promptly, and never simply hose it into the gutter.

5. Unstabilized soil left past deadlines

Permits set deadlines for stabilizing disturbed areas once work pauses or finishes in a given spot — typically requiring that stabilization begin within a set number of days of activity stopping. Bare slopes and stockpiles left open past those deadlines are a frequent finding, especially on sites that go quiet between phases.

The fix:

• Stabilize disturbed areas as soon as work in them stops, using seeding, mulch, blankets, or other temporary cover.
• Pay special attention to slopes and stockpiles, which erode fastest.
• Build stabilization into the schedule so it is not an afterthought when a phase wraps or weather rolls in.

6. Uncontained concrete washout

Washing out concrete trucks, pumps, and tools produces a highly alkaline, sediment-laden slurry. Letting it run onto the ground or into a drain is a discharge violation, and it is one inspectors look for specifically because it is so damaging and so easily prevented.

The fix:

• Provide a designated, contained washout area — a lined pit or a manufactured washout container.
• Make sure every crew and subcontractor knows where it is and uses it; one driver washing out at the curb undoes the whole system.
• Maintain the washout so it does not overflow, and dispose of the hardened material properly.

7. Failure to file the Notice of Intent

Before disturbing soil, the operator generally must obtain permit coverage by filing a Notice of Intent (NOI) and waiting for coverage to take effect. Starting earthwork without that coverage means discharging without a permit — a foundational violation that can taint the entire project from day one.

The fix:

• File the NOI and confirm coverage is in place before any land-disturbing activity begins.
• Track which permit (federal CGP or the applicable state permit) governs the site, since requirements and the operative agency vary.
• Keep proof of coverage with the SWPPP so it is ready to show on request, and file the Notice of Termination when the project closes out.

What enforcement actually costs

It is tempting to treat these as paperwork problems. Enforcement records say otherwise.

The EPA and authorized state agencies bring Clean Water Act enforcement actions against construction operators for exactly the failures above — discharging without permit coverage, missing or inadequate controls, and incomplete records. Resolutions can include civil penalties, mandated corrective work, and ongoing compliance obligations that follow a company across its future projects.

A widely cited example comes from the utility-scale solar sector. Swinerton Renewable Energy, a major solar contractor, reached a Clean Water Act settlement in which the company agreed to pay $2.3 million over stormwater violations at large solar construction sites. The Swinerton case is notable precisely because it involved a sophisticated, experienced builder — not a fly-by-night operation — and still resulted in a $2.3M resolution tied to construction stormwater compliance. That figure underscores a point worth internalizing: the cost of getting stormwater wrong is measured in millions, not in the price of a few rolls of silt fence.

Beyond the headline number, enforcement carries costs that do not show up as a single line item:

• Stop-work orders that idle crews and equipment while problems are corrected.
• Schedule slip as deadlines blow past while a site sits halted.
• Reputational damage that follows a contractor into the next bid and the next permit application.
• Heightened scrutiny on subsequent projects once a company is on a regulator's radar.

Against those numbers, the controls and habits that prevent violations are inexpensive. The trouble is rarely that operators do not know what to do — it is that the discipline slips when a site gets busy.

How disciplined recordkeeping prevents penalties

A striking feature of stormwater enforcement is how much of it turns on documentation. Many citations are not about a control that was missing in the field — they are about an inspection that was never recorded, a corrective action that was taken but never logged, or a plan that no longer matched the site.

Good records do two things. They keep the site compliant in real time, because a written inspection routine forces someone to actually walk the site and look. And they give you a defensible position if a regulator ever questions the project, because you can show the cadence was met, the failures were caught, and the fixes were made.

Recordkeeping that holds up shares a few traits:

• Contemporaneous. Entries are made at the time of inspection, not reconstructed later.
• Complete. Every routine and post-storm inspection is captured, including the ones where nothing was wrong.
• Specific. Findings name the control, the location, the problem, and the corrective action with dates.
• Current. The SWPPP is updated when conditions, phases, or controls change, so the plan on site always matches the dirt.
• Retrievable. Anyone on site can produce the plan and the inspection history on request.

Sites that maintain records this way rarely face the surprise findings that lead to penalties, because the problems get caught and fixed on their own schedule rather than an inspector's.

A practical checklist

Before your next inspection, confirm:

1. A current SWPPP is on site and matches actual conditions.
2. The NOI is filed and proof of coverage is on hand.
3. Inspections are happening on the required cadence and after rain events — and are documented.
4. BMPs are installed correctly, intact, and maintained, with inlets and silt fence given particular attention.
5. The construction entrance is working and roads are kept clear of track-out.
6. Disturbed areas are stabilized within the permit's deadlines.
7. Concrete washout is contained and used by every crew.

Run that list often enough and the common violations simply do not have room to develop.

Keeping ahead of it

The pattern across every item here is the same: the requirements are knowable and the fixes are cheap, but staying compliant takes a current plan and a steady routine that survive a busy schedule.

Siltworks generates an inspection-ready SWPPP built around your site and the permit that governs it, so the plan on site is current, the required controls and inspection cadence are spelled out, and the recordkeeping that protects you is in place from day one. It is a straightforward way to keep a project clear of the violations that lead to stop-work orders and settlements — and to stay ready whenever an inspector shows up.