Site Erosion Control Inspection

Use it on the schedule required by your permit or site plan, typically for routine weekly checks and after rain events that can move sediment. It is also useful after grading changes, utility trenching, or any work that exposes new soil. If the site has active runoff paths, steep slopes, or nearby storm drains, inspections should be more frequent. The template is built to capture conditions at the time of the walk-through, not after cleanup.

A competent person, erosion control lead, superintendent, or environmental inspector usually completes it, depending on how your project assigns responsibility. The person should understand the approved erosion and sediment control plan and be able to judge whether a control is functioning or failing. If your permit or local authority requires a specific role, use that role and document it in the inspection details. The template also works well when a field supervisor performs the inspection and routes findings to the responsible trade.

It covers perimeter controls like silt fence and wattles, inlet and drainage protection, stabilization of disturbed soil, stockpile protection, and housekeeping around tracked sediment. It also captures whether runoff is leaving the site with visible sediment and whether controls need repair or replacement. The structure follows the path an inspector would normally walk: perimeter, drainage points, exposed soil, then closeout and corrective actions. That makes it easier to spot deficiencies before they become a discharge issue.

This template supports field documentation for erosion and sediment control programs that are often tied to stormwater permit conditions, construction site plans, and local authority requirements. It is not a substitute for the approved SWPPP, permit, or jurisdiction-specific checklist, but it helps prove that controls were checked and maintained. In practice, teams use it alongside environmental compliance obligations and site safety procedures. If your AHJ or permit requires specific language, you can customize the findings and corrective action fields.

The biggest mistake is marking controls as present without checking whether they are actually functioning, such as a silt fence that is undercut or a wattle that has shifted downslope. Another common issue is failing to note sediment buildup at inlets before it reaches a failure point. Teams also miss discharge points, which can show the first visible sign of sediment-laden runoff leaving the site. This template is designed to force a real field observation, not a checkbox-only review.

Yes, it can be tailored for roadway work, vertical construction, utility projects, earthwork, or phased development sites. You can add site-specific controls such as check dams, sediment basins, construction entrances, or dewatering discharge checks if they are part of your plan. You can also adjust the inspection trigger to match weekly, post-storm, or post-disturbance requirements. The core sections stay the same because the inspection logic is consistent across most active sites.

Each deficiency should be assigned to a responsible party with a due date that reflects the risk and the site conditions. Critical issues, such as bypass flow, overtopping, or visible sediment leaving the site, should be escalated immediately rather than left for the next routine cycle. The template includes a corrective action field so the inspection does not stop at observation. That makes it easier to track closure and show follow-up if the site is reviewed by an owner, regulator, or third-party auditor.

Ad hoc notes and photos are useful, but they often miss repeatable coverage of the same controls and do not clearly show whether a deficiency was corrected. This template creates a consistent record of what was inspected, what failed, who owns the fix, and when it is due. It also helps different inspectors use the same criteria from week to week. That consistency is especially valuable when multiple crews, phases, or subcontractors are changing site conditions.