What Your Crew Saw (That Never Made It to the Report)

July 1, 2026

When a permit renewal asks for documented inspection history, or FEMA needs evidence of pre-storm maintenance, the crew work is rarely what’s in question. The documentation trail is field notes in a notebook, photos on a personal device, maintenance history spread across systems, assembled at a desk days after the crew was on site.

What makes a field observation a usable record?

In practice, a usable field record has to hold up on four counts: you can find it by asset and date without hunting, you can trace it to a specific person and location, you can show the specific structure it came from, and you can pull it into a report without asking anyone to reconstruct what they saw. A record that fails on any of those isn’t just incomplete. When reporting season arrives or a resident files a complaint, it might as well not exist.

Where the documentation chain breaks

The break happens in the same place across most departments. A crew goes out, conditions get noted, photos get taken: some to a shared folder, some to a personal device, some through a text thread. In departments that have already moved to digital tools, the pieces are often still scattered: work orders in one system, GIS in another, inspection history in a third. The record stays unofficial until someone reconciles it at a desk, sometimes days later.

The stakes show up differently depending on where you sit. Stormwater programs run into it at permit renewals. NPDES requirements ask for inspection evidence tied to specific assets and dates, not a general attestation that the program ran. Public works departments hit it when a resident challenges a flooding complaint or FEMA asks for pre-storm maintenance records. Either way, the same question: was this documented at the asset when it happened, or pieced together afterward?

What this looks like in practice

Across departments that have adopted Forerunner, the pattern looks similar: inspection data moves from personal devices and disconnected channels onto a system tied to each individual asset, captured in the field with no desk-reconciliation step afterward. What the crew recorded on Tuesday is the official record, not something assembled at the end of the week.

In Madeira Beach, Florida, field data used to live in manual spreadsheets and texts. Crew members shared site photos informally, and at the end of each month, administrative staff had to track down each crew member to pull together what was needed for reporting. Public Works Director Megan Wepfer calls it a constant chase: not because the crew wasn’t doing the work, but because documentation quality depended entirely on manual, disconnected processes.

See how Madeira Beach, FL tracks every storm drain on a monthly inspection rotation → Read the case study

When a resident reported a flooding drain after the transition to Forerunner, Wepfer had an immediate answer:

“I could go back and say, ‘We were there on X date; there were no issues with the pipe.’ It’s way easier to track.”

That response used to require a phone call and a folder search. Now it’s one lookup — every inspection is stored on the asset record, accessible by date and location. The department tracks every storm drain on a monthly inspection rotation, something Wepfer describes as “previously impossible to track on paper.”

Closing the gap between the field and the file

The gap closes when the record is created at the moment of observation, attached to the specific asset, with no transcription step in between.

For Ami Pierce and the Town of Ponce Inlet, that shift started with moving inspection data off personal devices and disconnected channels into Forerunner. When a crew member arrives at a site now, the full history for that location is already there: last inspection date, condition at last visit, open maintenance items, prior photos. What comes back from the field that day goes directly onto the same record. Reporting that used to require tracking down crew members and piecing together folders is now a targeted pull. “It saves time when you don’t have a lot and makes you more efficient,” Pierce noted. The team reclaimed more than 10 hours of staff time per week and goes into every permit renewal with data that’s already organized.

See how Ponce Inlet, FL reclaimed 10+ hours/week on compliance documentation → Read the case study

In practice, that means field data captured once, stored on the asset record, with nothing to reconstruct. Key capabilities for public works and stormwater programs:

Offline-capable mobile inspections: Records are captured in the field and sync when connectivity returns.
Asset-tied records: Every inspection is stored on the asset it came from, with full history accessible by date and location.
Live Mode: Crews can capture live video with AI anomaly detection during inspections, including conditions that are hard to describe in a notes field get documented as they’re observed.
MS4 reporting: An AI assistant lets your team draft the annual report narrative or pull full inspection history in plain language, without touching a spreadsheet.
Integrations: For departments already running GIS or asset management platforms, Forerunner connects to those systems rather than replacing them.

When the inspection record and the asset record live in the same system, you start to see what fragmented data never shows — which assets keep coming up, where maintenance frequency has dropped off, what condition your infrastructure was in the week before the storm. Every month’s work is already organized. The next time a storm comes, a permit renewal lands, or council asks what the maintenance budget accomplished — the record is ready.