CGP Stormwater Inspector Qualification Preparation Course

What a Qualified Inspector Is Expected to Do

The permit expects inspections to be performed by someone qualified, and qualification is about capability rather than a card in a wallet. The person has to know the controls on that site, understand what each one does hydraulically, recognize when it has stopped doing it, and write that up in a form that survives review by somebody who was never there.

That is a considerably higher bar than walking a checklist. Anyone can confirm that a silt fence exists. A qualified inspector looks at where the flow is actually going, notices that a swale has cut a new path since the last storm, and understands that the fence is now irrelevant to the real problem even though it is intact and shown on the map.

The role carries authority in practice as well. An inspector who identifies a deficiency starts a clock under the permit, and the correction becomes the site's obligation from that moment. Writing a soft finding to avoid friction with a superintendent does not make the problem any smaller. It moves the failure into the record with no deadline attached to it.

The Inspection Report Is a Legal Record

Treat every report as a document that will be read by somebody hostile, years from now, with no memory of the site and no patience for explanation. Enforcement actions, third-party suits and owner disputes all run on these records. The report is frequently the only surviving description of what the site looked like on a particular day.

That has consequences for how you write. Vague findings age badly, because a reader in the future cannot tell whether the issue was trivial or serious, or whether it was ever resolved. Blank sections read as work not performed. A run of reports carrying identical wording week after week reads as a form filled out from the seat of a truck.

It also means good records are worth a great deal. A file showing deficiencies found, dated, corrected and photographed is the strongest available evidence that the operator was running a real program. Most sites have problems at some point. The ones that get punished are the sites where the record shows that nobody was looking for them.

Judgment on the Walk, Not a Checklist

Inspect in the direction the water moves. Start high, follow the flow down to the discharge points, and pay attention to where the paths have changed since you last walked it. Sites are dynamic. Yesterday's grading created today's drainage pattern, and the controls were designed for a version of the site that no longer exists on the ground.

Look hardest at the discharge points. What leaves the site is what the permit cares about, and the condition of the receiving ditch or the street tells you whether the controls upstream are performing. Sediment on the pavement, a plume at the outfall or a fan of silt below a pipe outlet is a result rather than an opinion, and it is hard to argue with.

Then check the boring things. Stabilization on areas that have gone idle, whether cover was established where the schedule says work finished, the state of the stockpiles, fuel storage, washout and the entrance. Those items generate a large share of findings precisely because they do not belong to any particular crew's daily task list.

Routine Inspections Versus Post-Rain Inspections

The permit sets a routine schedule and also requires inspection after qualifying rain, and the two are looking for different things. Routine inspections mostly catch maintenance drift. Controls degrading, work areas expanding beyond what the plan showed, stabilization falling behind the schedule. They are predictable and they can be planned around the work.

The post-rain inspection is where the site tells you the truth. Water has just demonstrated where it goes, what it undercut, what it overtopped and what it carried away. Scour lines, sediment deposits and a silt fence bowed with water standing behind it are evidence of performance under load, and that evidence disappears fast once the site dries out and gets graded again.

Which makes timing part of the job. Get out while the marks are still there, and record conditions during the event itself when it is safe to do so. The most common weakness in a stormwater file is a set of post-rain inspections that read exactly like the routine ones, which usually means nobody went out until it was convenient.

Writing Findings That Are Specific and Dated

A usable finding answers where, what, and what has to happen. "Silt fence needs repair" fails on all three counts. "Silt fence along the south property line, at the low point east of the equipment lay-down area, is undercut across a run of posts, sediment has passed onto the adjacent lot, requires re-trenching and backfill" can be found, fixed and verified by somebody who was not on the walk.

Photographs are evidence when they carry a location and a date, and decoration when they do not. Take a wide shot that establishes where you are standing and a close shot that shows the defect, then reference the photo in the finding itself. Take the closeout photo from the same position, because a before and after from one angle ends most arguments before they start.

Date everything, including the date the deficiency was observed and the date it was corrected. Those two dates are what a reviewer looks at first and compares against the permit. Leave the observation date off and the report cannot demonstrate that the deadline was met, even where the crew went out and fixed the thing that same afternoon.

Corrective Action as a Discipline

The permit gives deadlines for correcting deficiencies, and those are conditions of coverage rather than targets to aim at. Where a repair cannot be completed in time, the permit generally expects the reason and the plan to be documented and interim measures put in place. Silence is what turns an ordinary maintenance issue into a violation with a paper trail behind it.

Run corrective action as a tracked list rather than a note buried in a report. Each item needs an owner, a due date and a closeout with evidence attached. Items that carry forward untouched across several reports are the clearest signal available to a regulator that the program is paperwork, and they are easy to spot because the same sentence keeps repeating.

Some findings point at the plan instead of the site. If the same control fails in the same place after every storm, the design is wrong for the flow it receives, and the answer is a plan amendment rather than another repair. Recognizing that difference is one of the things that separates an inspector from somebody carrying a clipboard.

What This Course Covers and What It Cannot

This course prepares you for the inspector role. Reading the permit and the plan together, performing the walk in a defensible sequence, judging whether controls are performing, writing findings that hold up, running corrective action, and building a file that reads well under review. At $149 it is aimed at the people who sign reports rather than the people who install controls.

It cannot grant a state-specific qualification. Requirements vary, several states run their own certification with an exam and continuing education, and some permits name particular credentials. Check what your permit and your state require before assuming that any course satisfies it. This is preparation and knowledge, and where a separate credential is required you still have to go and obtain it.

It also cannot replace time on site with somebody experienced. Judgment about whether a control is performing comes from seeing failures and watching what they cost. Pair the course with several inspections alongside a seasoned inspector, ideally including one after a real storm, which teaches more in a morning than any amount of classroom material.

Who Should Take This Course

Anyone who signs a stormwater inspection report. That covers contractor safety and quality staff who inherited the role without asking for it, self-perform superintendents who inspect their own work, and environmental consultants early in their careers who are still learning to document rather than simply observe. If your name goes on the report, the report is your work product.

Owners' representatives and construction managers benefit as well, because they review these files and often have to judge whether a contractor's program is real or decorative. Knowing what a weak report looks like is a useful skill on a site you do not run day to day, and it is far easier to fix during construction than afterwards.

It also suits experienced field people moving into a compliance role. If you have spent years installing and repairing controls, you already understand how they fail and why. What this adds is documentation discipline, and a sense of how a file reads to a regulator who turns up long after the site has been closed out.

Frequently asked questions