Photo and GPS evidence on stormwater inspections: what auditors actually want to see

State agency reviewers asking about a specific inspection tend to start with the same question. Show me the photo. When the program cannot, the inspection record reads as half-finished even when the work was done. The inspector was there, the conditions were observed, the finding was noted. The photo lives somewhere else, and the audit trail has a gap.

This post is about field evidence on stormwater inspections. What good photo and GPS documentation actually looks like, what the common failure patterns are, and how programs keep this from becoming the place where audit-defensibility quietly breaks down.

Why field evidence matters

A stormwater inspection record without field evidence is a narrative claim. The inspector says they were at the outfall, they say the discharge was clear, they say the catch basin sump was not yet at capacity. All of that may be true. None of it is verifiable.

Photo and GPS evidence change the record from a claim into something defensible. A timestamped photo of the outfall, with GPS metadata that puts the inspector at the outfall, produces an auditable record that does not depend on memory or trust. Five years later, when the inspector has moved on and the program is responding to a state-agency request for records, the photo carries the weight that the original narrative cannot.

The other reason field evidence matters: enforcement records depend on it. A notice of violation tied to an inspection finding needs the underlying photo and GPS evidence to survive any challenge. Programs that issue NOVs without photographic backing are setting themselves up for losses on appeal.

What auditors actually look for

State agency reviewers are not photo enthusiasts. They are looking for a small number of specific things:

The photo shows the thing the record says it shows. A finding of “sediment at 75 percent of sump capacity” with a photo of a parking lot does not match. A finding of “no observed discharge” with a photo of an empty outfall pipe does match.
The photo timestamp matches the inspection date. A photo taken three days after the inspection date looks like reconstructed evidence.
The GPS metadata puts the photographer at the location. A photo taken at coordinates two miles from the inspection site reads as a stock image dropped in.
The photo identifies the asset. Either the asset tag is visible in the frame, or the GPS coordinates resolve to that specific structure or site, or the photo composition is specific enough that a reviewer can see which asset it is.
Multiple photos show different angles or features when the inspection type calls for it. A BMP inspection that includes one photo of the inlet and one of the outlet is more complete than a single wide shot.

A program that captures this kind of evidence consistently does not need to argue with auditors about whether inspections happened. The record speaks for itself.

The metadata that actually matters

Most modern phones embed metadata in photos automatically. The metadata that matters for inspection records:

Capture timestamp in the photo’s EXIF data
GPS coordinates at the time of capture
Direction (compass bearing) when available
Altitude for sites where elevation matters (rare in stormwater, useful for some IDDE work)
Device identifier for chain-of-custody on enforcement-bound records

The inspector does not need to manage any of this manually if photos are captured through the inspection workflow. The metadata is automatic. The failure modes are about where the photo goes after capture, not about whether the metadata exists.

Photo composition by inspection type

Different inspection types call for different photos. Some practical patterns:

Outfall screening (MCM 3): A photo of the outfall structure showing flow conditions, a close shot of the discharge or pipe interior if dry, and a photo of any indicator (sheen, foam, color, debris) noted in the field record. Three photos minimum on any indication-positive screening.

Construction site inspection (MCM 4): Photos of erosion controls in their current condition, any deficient feature, and any active disturbance area. The photo set should support the findings in the inspection record. A finding of “perimeter silt fence inadequate” should have a photo of the inadequate fence.

Post-construction BMP inspection (MCM 5): Photos of the inlet, outlet, and treatment surface. Vegetation condition for bioretention. Surface condition for permeable pavement. Sediment accumulation if the inspection records sediment depth. The full BMP context in the post-construction BMP guide.

Catch basin and structure inspections: A photo of the structure from above (showing grate condition and any debris) and a photo of the sump or interior (showing sediment depth or any anomaly). For oil-water separators, a photo of the separator interior showing the oil layer.

IDDE incidents: Photo of the outfall or contributing point at first response, photos at each source-tracing step, and photos of any corrective action. The full IDDE workflow in the complaint-to-closure playbook.

Municipal facility inspections (MCM 6): Photos of fueling areas, vehicle washing areas, material storage, and any visible non-stormwater discharge or housekeeping issue.

The point of these patterns is not bureaucratic completeness. It is making the photo set match what the inspection record says. A reviewer reading the inspection narrative and looking at the photos should see the same story.

Where the field-evidence workflow tends to break

The single most common failure pattern: photos live on personal phones, never make it to the inspection record, and quietly disappear at staff transitions. Some specific patterns:

Photos on personal devices. The inspector takes photos in the field. The photos sit in the camera roll. At the end of the day, the inspector emails three of them to themselves and uploads those to the inspection. Five photos that were taken never get attached. A year later, the camera roll has been overwritten by family photos and vacation shots.

Photos in personal cloud accounts. The inspector uploads to their iCloud or Google Photos. Two years later, the inspector leaves the agency and their personal cloud goes with them. The inspection record has captions referencing photos that no longer exist.

Photos in shared drive folders, but not on the inspection record. The agency has a shared drive folder for inspection photos, organized by date. The folder is searchable but the inspection record itself does not link to specific photos. A reviewer has to cross-reference dates and locations to figure out which photos belong to which inspection.

Photos with stripped metadata. Some platforms strip EXIF metadata when photos are uploaded or attached. The photo survives, the timestamp and GPS do not. The photo loses most of its evidentiary value.

Photos taken in the wrong app. The inspector uses a different app to capture photos than to fill out the inspection. The photos go to the camera app’s storage and do not auto-attach to the inspection. The inspector has to manually upload them later, which sometimes happens and sometimes does not.

GPS verification and chain of custody

For routine inspections, GPS verification is a documentation upgrade. For inspections that may end up supporting enforcement, GPS verification is closer to chain of custody.

A chain-of-custody-grade record has:

The capture device identified
The inspector identified at capture time, not just at upload
A timestamp that comes from the device clock, not from the upload time
GPS coordinates captured by the device, not entered manually
A trail showing where the photo went between capture and the final record
An audit log of any changes to the photo (rotation, cropping, redaction)

Most stormwater inspections do not need this level of rigor. Construction enforcement, industrial discharge enforcement, and any inspection feeding a notice of violation probably do.

The practical implication: the system that holds inspection photos should not strip metadata, should not allow silent edits, and should preserve the original capture record alongside any annotations or markups.

Storage, retention, and exports

Some practical rules of thumb for stormwater inspection photo storage:

Retention should match the program’s broader records retention policy, typically five to seven years for inspection records, longer for some enforcement records.
Photos should export with their inspection record when the agency requests records for state submittals, public records requests, or program transitions.
Original photos should be preserved alongside any annotated or redacted versions.
Storage should not be on inspector personal devices, on shared drives that the program does not control, or in third-party cloud accounts tied to individual staff.

The exportability question matters most when a program transitions to a different system. If the next vendor cannot accept photo records with their original metadata, the program loses years of evidentiary value in the migration. Standard formats (JPEG with intact EXIF, PDF reports with embedded photos, CSV inspection logs with photo file references) protect against that.

How software fits

A purpose-built inspection workflow keeps the photo, the GPS coordinate, and the inspection record on the same record from the moment of capture. The inspector files the inspection through the same interface that captured the photos, the metadata stays attached, and the photos are findable from the inspection without searching a shared drive.

NPDESTracker captures field evidence this way. Photos taken through the inspection workflow attach directly to the record being filled out, GPS coordinates come from the device at capture time, and the inspection cannot be filed without a clean record of where the inspector was. The full mobile inspection workflow is on the inspections page, and the GIS-aware structure of inspections (where the same site or structure pinned on the map is one click from its inspection history) is on the GIS workspace page.

If your program is currently relying on inspector phones plus a shared drive plus manual uploads, the easiest way to see what an integrated capture workflow looks like is the interactive demo. Sample data, browse only, no signup.

The tool does not stop the inspector from forgetting to take a photo. What it does is keep the photos that are taken from going missing between the field and the record.