Describe your project, inspection cadence, and stormwater controls. Makeform turns the details into a site-ready checklist for documenting weather, discharge points, best management practices, deficiencies, photos, corrective actions, and inspector sign-off during routine visits.
Route inspection records to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose the inspection pattern closest to your project, customize the prompt, and send it to the Makeform builder. Each structure is an example to adapt to your SWPPP and permit conditions.
Prompt ready4 formats
Audience
Qualified inspectors walking an active construction site
Format
Mobile checklist organized by inspection area
Prompt size
603 chars
Brief qualitySends to builder
Example inspection structure
Mobile checklist organized by inspection area
Prompt exampleEditable in builder
Project, inspector, inspection date, and site phase
Short answerFirst ask
2
Weather and recent rainfall information
Number
3
Condition of each BMP and inspection area
Multiple choice
4
Photos and location of deficiencies
File upload
5
Corrective-action owner and due date
Date & time
6
Inspector certification and signature
Signature
Suggested routing tags
Suggested
No action needed
Corrective action open
Reinspection due
Ask for a photo and exact location whenever a control is marked damaged or ineffective; the condition alone is not enough for a crew to find and repair it.
Step 1
Prepare
project, weather, site phase, and inspection trigger
Step 2
Walk
inspect each BMP, activity area, and discharge point
Step 3
Assign
document deficiencies, owners, photos, and due dates
Step 4
Verify
follow up on repairs and retain the completed record
A clearer site walk
Turn stormwater observations into work crews can act on.
A useful inspection record connects every observation to a place, a control, and a next step. Structured responses help the inspector move consistently through the site without reducing the visit to a generic pass-or-fail sheet.
Checks matched to site areas
Group entrances, perimeter controls, inlets, slopes, storage areas, washouts, outlets, and other BMPs so the inspector can follow the site plan instead of hunting through one long list.
Follow-up only when needed
Conditional fields can request the location, photo, severity, immediate response, owner, and due date only after an item is marked deficient, damaged, missing, or ineffective.
A repair trail after the walk
Route open actions to the people responsible and use a focused verification form to record whether the repair was completed and the control is functioning as intended.
Adapt it to the project
One builder for four common inspection patterns.
Start with the workflow that matches the visit, then replace generic control names and thresholds with the requirements and BMP inventory documented for your project.
Routine recurring inspections
A consistent route through active work, stabilized areas, controls, material handling, waste, and discharge locations, with a complete header for each visit.
Rain-event observations
Storm timing, rainfall information, runoff status, visible discharge observations, overtopping, bypass, scour, and sediment accumulation documented while conditions are visible.
Linear and phased projects
Repeatable sections organized by station, segment, lot, building pad, or phase let one inspection cover changing locations without losing the map reference.
Repair verification visits
A compact reinspection captures the original finding, completion status, new photos, functional condition, remaining work, and the person who verified it.
Inspection workflow
Build the checklist around the way your inspector walks the site.
A short prompt can establish the structure. The important work is adding the project's actual inspection areas, BMPs, escalation rules, and follow-up responsibilities before publishing it to the field.
Tell Makeform whether the visit is routine, event-based, phase-specific, or a follow-up. Include project type, inspection areas, control categories, weather fields, and the people who handle findings.
02
Replace placeholders with project details
Edit the generated form to match the site's SWPPP: use actual BMP names, inspection locations, plan references, responsible subcontractors, rating options, and any project-specific timing instructions.
03
Test the deficient-item branch
Preview the form on a phone and deliberately mark a control unsatisfactory. Confirm that location, description, photo, immediate response, assigned owner, due date, and follow-up fields appear and are required.
04
Publish, route, and revisit open actions
Share the form with inspectors, send submissions to the project team, filter records by open action or due date, and use a follow-up submission to document the condition after repair.
Inspection record options
Choose a format that survives the walk and the follow-up.
The project's required records should drive the final form. The practical difference is whether an inspector can capture a complete observation at the location and whether the team can find open work afterward.
Approach
During the inspection
After the inspection
ApproachPaper checklist
During the inspectionEasy to carry, but photos, exact locations, and conditional detail sit elsewhere or get added later.
After the inspectionSomeone must scan, file, transcribe, and separately notify the crew about each deficiency.
ApproachGeneric spreadsheet or PDF
During the inspectionProvides repeatable rows, but can become cramped on a phone and may not enforce details for failed items.
After the inspectionUseful as a project record when completed carefully; action ownership and verification often need another tracker.
Approach
Generated online form
During the inspectionShows a mobile sequence, requires supporting details when conditions call for them, and accepts photos at the observation point.
After the inspectionCreates structured submissions that can be routed, searched, exported, and connected to a corrective-action follow-up.
Field guide
What a useful SWPPP inspection form should capture.
Use these six sections as a drafting guide, then compare the form against the project's current SWPPP, site map, permit conditions, inspection schedule, and recordkeeping process before field use.
Inspection identity
Anchor every record to one visit.
The header needs enough context to distinguish a routine inspection from a storm-event observation or repair check. Record the project, inspector, trigger, date, time, site phase, and plan revision or area references used during the walk.
Project name, location, tracking identifier, and current construction phase.
Inspector name and role, inspection date, start time, and end time.
Routine, storm-related, phase, complaint, discharge, or corrective-action follow-up trigger.
Weather & site conditions
Record the conditions behind the observations.
Weather provides context for what the inspector could see. Use separate fields for current conditions, recent rainfall information, runoff or discharge status, soil condition, and whether an inspection area was inaccessible rather than burying them in a general notes box.
Current weather, temperature if useful, and active precipitation status.
Storm timing and rainfall amount from the project's chosen source or gauge.
Runoff, ponding, frozen or saturated ground, and inaccessible-area explanation.
BMP condition checks
Inspect controls by location and function.
A control inventory is more useful than one question asking whether all BMPs are acceptable. Organize controls in the order encountered and provide clear ratings such as acceptable, maintenance needed, failed, not installed, not observed, or not applicable.
Entrances, perimeter barriers, inlet protection, slope and channel stabilization.
Sediment traps or basins, outlets, check structures, and discharge points.
Stockpiles, concrete washout, fueling, dewatering, waste, and material storage controls.
Observations & evidence
Make each finding locatable.
A photo without a label can be difficult to place later. Pair every problem with an area, station, plan callout, nearest landmark, or GPS reference; describe what was observed; and upload close and context views when they help the repair team.
Exact location, control identifier, receiving feature, and observed condition.
Evidence of erosion, sediment migration, track-out, leaks, spills, bypass, or damage.
Annotated or labeled photos showing both detail and surrounding site context.
Corrective actions
Turn a deficiency into an owned task.
The finding should say what happens next. Capture immediate measures taken during the visit, the permanent or additional work needed, priority, responsible company and person, target date, notification path, and whether a verification visit is required.
Immediate containment, cleanup, maintenance, stabilization, or access restriction.
Named owner or subcontractor, action description, priority, and target completion date.
Open, in progress, complete, or deferred status with reason and reinspection date.
Review & sign-off
Close the record without hiding exceptions.
Finish with an inspection summary that counts open findings and identifies areas not inspected. Let the inspector review required fields, note who was notified, add supporting documents, and sign the record using the statement selected by the project team.
Overall condition, open-action count, inaccessible areas, and unresolved observations.
Notification recipients, distribution date, attachments, and related inspection reference.
Inspector name, signature, completion date, and project-approved acknowledgment wording.
Related tools
Connect stormwater inspections to the wider site workflow.
Use separate forms when the audience, routing, or record structure changes: progress reporting, equipment checks, safety observations, incidents, work orders, and general maintenance requests.
Practical answers for inspectors, superintendents, environmental managers, and project teams building a repeatable field record.
What is a SWPPP inspection form?
A SWPPP inspection form is a structured record used during a construction-site stormwater inspection. It typically identifies the project and inspector, records weather and site conditions, walks through erosion and sediment controls and pollution-prevention practices, documents discharge observations and deficiencies, and assigns corrective actions. The exact content and inspection timing should come from the project's current SWPPP, permit conditions, and established procedures.
What fields should I include in a routine SWPPP inspection checklist?
Start with project, inspector, date, time, inspection type, current phase, weather, recent rainfall information, and runoff status. Add sections for each inspection area and BMP, including condition rating and location. For exceptions, require a description, photos, immediate response, additional work, responsible person, priority, due date, and reinspection status. Finish with inaccessible areas, overall notes, notifications, attachments, and inspector sign-off.
Can the form change for a post-storm inspection?
Yes. Create a post-storm version or use conditional sections that appear when the inspector selects a storm-event trigger. Ask for storm timing, rainfall information, active runoff or discharge, overtopping, bypass, sediment movement, erosion, scour, ponding, and the condition of controls after the event. Use the project's own trigger, timing, and observation requirements instead of assuming one universal threshold.
How should the form handle a failed or damaged BMP?
Use conditional logic so a deficient rating reveals required fields for exact location, control identifier, observed problem, close and context photos, any immediate measure taken, further action needed, responsible company or person, priority, and target date. Include a stable finding ID or reference so a later verification submission can be connected to the original observation without relying on free-text searching.
Can inspectors complete the checklist on a phone and attach photos?
Yes. Publish the form as a link that inspectors can open on a phone and add file-upload fields at the control or finding level. Keep choices short, group the checklist in the physical order of the site walk, and preview the deficient-item branch on a small screen. Label every photo with its area or finding so the image remains useful after it leaves the field.
How do I adapt the form for a linear or multi-phase project?
Use a repeatable location section keyed to station range, segment, lot, phase, or plan area. Within each location, ask about current activity, disturbed ground, nearby inlets or receiving features, controls present, condition ratings, photos, and actions. Maintain dropdown lists as work shifts, and preserve a free-text or GPS reference for locations that are not yet represented on the list.
Does a generated checklist guarantee that our inspection meets every requirement?
No. Generation provides an editable starting structure, not a determination that the checklist is sufficient for a particular project or jurisdiction. Before field use, the responsible project team should compare every section with the current SWPPP, applicable permit conditions, site map, BMP inventory, inspection schedule, corrective-action process, and required sign-off or retention wording, then keep the form updated as the project changes.
Is the SWPPP inspection form generator free?
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and use the inspection form without a response cap. A paid tier is available only for removing the Makeform badge. Review the generated first draft carefully and replace example fields with the project's actual inspection requirements before sharing it with inspectors.
Build the field record around your site.
Generate a SWPPP inspection form your team can inspect, assign, and revisit.
Unlimited free forms and responsesConditional deficiency detailsPhotos, owners, and due dates
