Auto-SWPPP
CGP requirement: develop a SWPPP before NOI submission and keep it current
1) SWPPP contents (what must be in the plan)
The Idaho CGP requires a SWPPP that identifies pollutant sources and describes controls to reduce pollutants in stormwater discharges. The permit’s minimum SWPPP content list is in CGP Section 7.2, with related requirements throughout the permit.
Operators + responsibilities
List all operators and identify who is responsible for implementing the SWPPP (CGP 7.2.1; operator eligibility/definition in CGP 1.1 + Appendix A).
Stormwater team + training
Identify the stormwater team and ensure team/inspectors meet training expectations (CGP 6.1–6.4; SWPPP content items in CGP 7.2).
Site description + receiving waters
Describe site conditions, runoff/run-on, discharge points, and receiving waters considerations (CGP 7.2; map + water features in CGP 7.2.2.4).
Site map (make it legible and useful)
Include boundaries, disturbance/phasing, slopes, stockpiles, discharge points, inlets, receiving waters, and key features (CGP 7.2.2.4).
BMPs (erosion/sediment + pollution prevention)
Describe what controls you will use, where they go, and how they will be maintained (CGP Part 2; SWPPP documentation in CGP 7.2).
Stabilization plan
Document temporary/permanent stabilization approach and how you track disturbed areas to stabilization (CGP Part 2 stabilization requirements + SWPPP documentation in CGP 7.2).
Inspections
Describe inspection procedures, schedule triggers, and documentation approach (CGP Part 4; SWPPP documentation in CGP 7.2).
Corrective action process
Define how issues are identified, fixed, documented, and closed out; maintain the corrective action log (CGP Part 5).
Post-authorization documents
After coverage, include NOI/coverage correspondence and a copy of the permit in the SWPPP package (CGP 7.2.10).
Template alignment: Your Auto-SWPPP template mirrors a practical structure (Sections 1–9): Contacts, Site Evaluation/Discharge Info,
ESA/Federal, Erosion & Sediment Controls, Pollution Prevention, Post-Construction, Inspections/Corrective, Training, Certification/Notification.
Template Sections 1–9 (quick reference)
Section 1
Contacts / responsible parties
Operators, contacts, signatories, stormwater team roles.
Section 2
Site evaluation & discharge info
Discharge points, receiving waters, site mapping, soils/slopes/drainage.
Section 3
ESA / other federal requirements
ESA criteria documentation and required attachments where applicable.
Section 4
Erosion & sediment controls (BMPs)
Perimeter, inlets, slopes, basins, track-out, sequencing.
Section 5
Pollution prevention (materials/waste)
Concrete washout, fueling, spill response, waste, equipment washing.
Section 6
Stabilization & post-construction BMPs
Temporary/permanent stabilization, final stabilization criteria.
Section 7
Inspections & corrective action
Inspection frequency, reporting, corrective action log closure.
Section 8
Training
Stormwater team/inspector training documentation.
Section 9
Certification & notification
SWPPP certification/signatures; NOI/coverage docs included.
CGP: keep permit/SWPPP available; post coverage notice
2) What to keep on-site and available
The CGP requires keeping a current SWPPP copy on-site (or easily accessible) so it can be made available at inspections or upon request, and posting notice of permit coverage. See CGP 7.3 (SWPPP availability) and CGP 1.5 (post notice).
Current SWPPP + maps
Maintain the most current SWPPP and applicable site maps/figures where field staff can access them quickly (CGP 7.3; team access in CGP 6.4).
NOI + DEQ coverage authorization
Keep the NOI and coverage/permit tracking correspondence in the SWPPP package (CGP 7.2.10).
Inspection records
Keep inspection documentation available (CGP Part 4 + SWPPP documentation expectations in CGP 7.2).
Corrective action log
Maintain a corrective action log and keep it immediately available at inspections (CGP 5.4).
Permit copy access
Keep a copy of the permit with the SWPPP package and ensure stormwater team access (CGP 7.2.10; CGP 6.4).
Posting / notice
Post the notice of coverage as required so inspectors can verify coverage (CGP 1.5).
Fast field check: If an inspector shows up, you should be able to produce: (1) current SWPPP + map, (2) NOI/coverage,
(3) inspection log, and (4) corrective action log — without hunting.
CGP Part 4: inspections and documentation
3) Inspections (set up your process so it’s easy to execute)
Inspections are one of the most common failure points because they’re recurring and documentation heavy. Your SWPPP should define: who inspects, when, what they check, and how issues are tracked to closure (CGP Part 4 + Part 5).
Assign qualified inspectors
Ensure inspectors meet training expectations and understand BMP intent, discharge points, and documentation requirements (CGP 6.3; SWPPP support in CGP 7.2).
Define your inspection scope
Include perimeter controls, inlets, stabilized entrances, stockpiles, discharge points, receiving waters near outfalls, and material management areas.
Document clearly
Write down what was observed, where, the date/time, and what was done. “Inspected – OK” is not helpful if something goes wrong later.
Trigger corrective actions
When conditions meet corrective action triggers, move immediately into Part 5 workflow (identify → fix → document closure).
Want the inspection page? See SWPPP inspections (Idaho) for inspection scheduling, common triggers, and field-ready checks.
CGP Part 5: corrective actions + log
4) Corrective actions (the close-out system matters)
Corrective actions are where many sites fail: issues are found but not closed out with dates and documentation. The CGP requires tracking corrective actions and retaining the log (CGP 5.4).
Identify and document the condition
When a corrective action condition is found, document what it is and when it was identified (CGP Part 5; log requirements in CGP 5.4).
Fix it within required timelines
Take action, then document what was done and when it was completed; note if SWPPP changes are needed (CGP Part 5.2 + 5.4).
Update SWPPP if needed
If corrective actions require changes to BMP selection, locations, sequencing, or procedures, update the SWPPP and map (CGP 7.2 + 7.4).
Keep the log available
Keep the corrective action log on-site or easily accessible for inspections (CGP 5.4).
Tip: Treat corrective actions like “tickets”: opened with a timestamp, assigned, fixed, verified, and closed with a completion date.
CGP: SWPPP must be kept up to date
5) SWPPP amendments (when you must update the plan)
The CGP requires the SWPPP be kept current throughout permit coverage (CGP 7.1) and modified when conditions change. Examples include ownership/operator changes, phasing/plan changes, inspection findings requiring changes, or changes to controls (CGP 7.4).
Plan/spec changes that affect stormwater
If the project changes in a way that affects drainage, discharge points, disturbed areas, or BMP needs, update the SWPPP and map (CGP 7.4).
Operator/control transfers
If operational control transfers (common on multi-operator sites), document it and reflect map/roles updates (CGP 7.4).
Inspection/corrective action-driven updates
If inspections or corrective actions show controls aren’t working as planned, update the SWPPP accordingly (CGP 5.x + 7.4).
Maintain a change record
Keep records showing dates of SWPPP modifications (CGP 7.4).
Bottom line: If the field reality changes, the SWPPP should reflect it. That alignment is what protects you during inspections and incidents.
Common gaps that create problems
- BMPs installed differently than shown, or not installed before disturbance
- Perimeter/inlet protection missing or bypassed by runoff routing changes
- Stabilization lagging behind activity (areas sit exposed too long)
- Corrective actions identified but not documented to closure
- Records exist but are not accessible at the site when requested
How Auto-SWPPP fits
- Before checkout: generate a narrative PDF preview to confirm scope, story, and assumptions
- After purchase: finalize and deliver the SWPPP PDF package aligned to Idaho CGP expectations
Straightforward projects often target ~24 hours; complex sites can take longer due to phasing, mapping, sensitive waters, and dewatering.