SWPPP Rainfall Inspection Requirements: What Contractors Need to Know

If you manage construction sites with active Stormwater Pollution Prevention Plans, you already know the basics: disturbed earth, erosion controls, inspection schedules. But the part that creates the most practical difficulty isn't the routine work — it's the storm-triggered inspection requirement that sits on top of everything else.

This guide covers what counts as a qualifying rain event, what you're required to do after one, and where the most common gaps show up.

What counts as a qualifying rain event

Under the NPDES Construction General Permit (CGP), a qualifying rain event is generally defined as a rainfall accumulation of 0.5 inches or more within a 24-hour period. When that threshold is crossed at or near your site, it triggers a separate inspection requirement on top of your routine schedule.

The 0.5-inch threshold is the federal default under the CGP. Some state-issued permits use different thresholds — sometimes lower, occasionally higher, and some use intensity-based triggers instead of accumulation. Your specific SWPPP should reference the applicable threshold for your permit.

The 24-hour inspection window

Once a qualifying rain event occurs, most permits require a post-storm site inspection within 24 hours of the end of the rainfall event. This is not 24 hours from when you found out it rained — it's 24 hours from when the qualifying accumulation was recorded.

This creates a practical problem: if it rains overnight or over a weekend and nobody is tracking actual accumulation data, the 24-hour window may start — and potentially close — before anyone on your team even knows a qualifying event occurred.

What the inspection should cover

• All stormwater control measures — are they in place and functioning?
• Evidence of sediment discharge or erosion beyond controlled areas
• Effectiveness of existing BMPs (best management practices)
• Areas where additional controls may be needed
• Condition of stabilized areas and newly disturbed areas

How most teams handle rainfall tracking

Most construction firms handle rainfall tracking one of three ways:

1. Someone checks a weather app in the morning. This tells you what's forecast, not what actually accumulated. It doesn't give you NOAA station data, timestamps, or anything an auditor could verify.
2. Someone writes it down after the fact. Handwritten logs are common but hard to verify. If an auditor cross-references your entry against actual NOAA precipitation data and the numbers don't match, that's a documented discrepancy.
3. Rainfall isn't actively tracked. The inspection schedule runs on its routine cycle and storm events get addressed only if someone happened to notice it rained enough. This is the most common way qualifying events get missed.

The core issue is that weather awareness is not the same as precipitation monitoring. Knowing "it rained last night" is different from knowing the specific station recorded a specific accumulation that exceeded the specific threshold in your permit.

What regulators and auditors actually look at

During compliance reviews, regulators and auditors typically focus on a few specific things related to storm events:

• Did a qualifying event occur? They pull NOAA data for stations near your site. If the data shows a qualifying event, they expect to see a corresponding inspection record.
• Was the inspection conducted within the required window? The timestamp on your inspection needs to fall within 24 hours of the event. Approximate or backdated entries are straightforward to flag.
• Does the record include verifiable data? Best practice is to reference the specific NOAA station, the measured accumulation, and the event timestamp — not just "it rained."
• Is there a pattern of missed events? A single miss might draw a note. Multiple gaps across events suggest a gap in the tracking process, which typically draws additional scrutiny.

Common recordkeeping mistakes

• No rainfall source cited. The inspection log says "rain event" but doesn't reference any verifiable precipitation data.
• Inspection dates that don't align with events. The log shows an inspection two or three days after the qualifying event, well outside the 24-hour window.
• Missing events entirely. NOAA data shows qualifying rainfall, but there's no corresponding inspection record at all.
• Inconsistent thresholds. The log uses a different threshold than what's specified in the site's SWPPP or permit.
• No station identification. The record references "local weather data" without specifying which station, making verification impossible.

What should be documented after a storm event

A well-documented storm event inspection record should include:

• The NOAA station used for rainfall measurement (station ID, name, and approximate distance from the site)
• Measured 24-hour precipitation accumulation
• The applicable qualifying threshold from your permit
• Timestamp of when the threshold was exceeded
• Date and time of the post-storm inspection
• Findings from the inspection (BMP condition, any issues observed)
• Corrective actions taken or planned, if applicable

State and permit variability

While the NPDES Construction General Permit provides a federal baseline, many states operate under their own construction stormwater permits with different specific requirements. Common variations include:

• Different rainfall thresholds (some states use 0.25 inches, others use 0.5 inches or intensity-based triggers)
• Different inspection timing windows (24 hours is most common, but some permits specify different periods)
• Additional documentation requirements beyond the federal minimum
• Different definitions of what constitutes the "end" of a rainfall event

The practical takeaway

Storm-event inspection compliance comes down to three things: knowing when a qualifying event happened, inspecting within the required window, and having documentation that can be verified against actual NOAA data.

Most teams that end up with gaps in their records aren't cutting corners. They're just not set up to catch qualifying rainfall events reliably — especially overnight, on weekends, or across multiple active sites.

Any process that depends on someone manually checking the weather and deciding whether it qualifies has a built-in gap. Closing that gap is what reliable storm-event compliance looks like.