How to Keep Inspection Records Complete Across Multiple Sites

At an operator with dozens or hundreds of active sites, the hard part isn't getting inspections done. It's knowing which deficiencies are still open and when the rest were closed. For a single site, answering that can mean digging through several places.

None of this looks like a problem until someone asks for the documentation. Then someone has to track the record down by hand. Until they find it, a missing record can turn into a finding when a state or EPA inspector reviews the site, and for contractors, it gives the owner reason to ask whether the work in the contract was actually done.

What does a site inspection record have to prove?

A site inspection record has to pass four tests. Pick one of your sites and check its record against each one: 

1. The record exists for every required inspection. Count the inspections the permit required at one site last month, including any triggered by a storm, and compare that with the records you can find. If the permit called for six and you can find five, the site fails this test.
2. The record is tied to a place and time you can verify without asking anyone. Open a few recent records and check whether the date and location come from the visit or from when someone entered the form. An inspection done on Tuesday but dated Friday, when it was entered, looks late on paper even though it was on time. If any record is dated when it was entered instead of when the inspection happened, the site fails this test.
3. The record shows what was found, whether it needed a corrective action, and when that action was closed out. Pick a few corrective actions from last month and check that each one shows the date it was closed. A silt fence repaired on site but never marked closed still counts as open. If any of them is missing a close-out date, the site fails this test.
4. The record can be pulled the day someone asks for it, without anyone piecing it together from several places. Try pulling one site's inspections and corrective actions from last quarter, photos included. If it takes more than a day, or you had to pull from more than one place, the site fails this test.

‍
These tests hold whether the requirement comes from a construction general permit, a multi-sector permit, a client contract or your own EHS standard.

What tools do multi-site operators use to document inspections?

If you run inspections across a lot of sites, you're probably using one of three kinds of tool:

• a forms app alongside a GIS
• an enterprise EHS suite that tracks what's due and when
• a field intelligence layer that works on top of both

What separates them is what the record is tied to. A forms app captures the answers, but the location lives in a separate map. An EHS suite files records by facility and permit, whether they come in through its mobile app or get entered later. A field intelligence layer ties each inspection to a mapped spot on the site and shows the inspector what's still open there before they start.

Where do multi-site inspection programs break down?

Programs tend to break down in four places:

• The same inspection gets done differently from site to site, depending on who's doing it.
• Crews work around the tool, and the inspection ends up somewhere other than the record, like a paper form or in a phone or text thread.
• The form doesn't match what the site's permit or contract requires. Most states issue their own stormwater permit, and some owners add requirements of their own, so one form rarely fits every site.
• Sites without cell service produce a late record, or none at all.

Each of these breakdowns costs staff time and adds compliance risk. Someone has to chase missing records, re-enter field notes and pull documentation together by hand every time an owner or inspector asks. Any record that can't be found, or doesn't hold up, can mean a re-inspection or a finding. Across two hundred sites, the cost and the risk compound.

The four tests are also a ten-minute checklist to see where records fall short for any site:

Download the multi-site inspection documentation checklist.

Who is asking for inspection records, and how often?

Owners, insurers and state or EPA inspectors can all ask for inspection records, and some of those requests come without warning. Since you can't plan around them, the records for every site have to be current every day, not just before a scheduled audit.

EPA's proposed 2027 Construction General Permit would go a step further and make some of that documentation part of the filing. Under proposed Part 1.4.1, an operator applying for permit coverage would submit one of three things: the complete stormwater pollution prevention plan (SWPPP), a link where it can be viewed, or the site map plus a signed certification. But a filed plan only shows the site on the day it was filed. The plan itself keeps changing as the work does, so the copy on file can soon stop matching the site. Anyone who looks at the filed copy, an inspector included, may see a plan the site no longer follows, and the operator is left explaining the gap or re-filing to close it.

What we asked the EPA for

In our public comment, we asked EPA not to require re-filing every time the plan changes. Instead, we recommended that the filed plan show when it was last revised, with a record of every revision behind it, and that any link to it stay current for the full three-year retention period. We also asked that operators who share one plan for a site, such as a general contractor and its subcontractors, be able to point to a single filing.

Whatever EPA adopts, it will help to have a revision history behind every plan you file.

What does a working inspection program look like?

When it's working, the record is finished before the inspector leaves the site.

For the person doing the inspection, the work is finished on site. They fill out the inspection form and upload photos offline. Nothing needs to be retyped back at the office, and the record syncs to the systems your team already uses.

For the program lead, answering a request from an owner or inspector means pulling up the site's record and sending it. The same view shows open corrective actions across every site, so it's clear which sites are falling behind and where to put staff or training. And because inspections are recorded the same way at every site, even when the permit requirements differ, a failed silt fence at one site can be compared with one at another.

A field intelligence layer is what makes this possible.

‍

How do multi-site operators close the documentation gap?

Forerunner is a field intelligence layer for inspections. Crews use the Forerunner mobile app to complete inspections on site, with or without cell service. Before they start, the app shows them the site's requirements, previous inspections and open items. When they finish, the record is written into the systems the business already uses.

Here's what that looks like day to day:

1. The record is written in the field. The observation, the photo, the location and the time are saved to the site's record during the inspection itself. Nobody has to move a form response afterward or go back in to update a status.
2. The inspector sees the history before they start. Previous inspections, open corrective actions, the site map and the requirements for that site are all there before the visit begins, so when someone finds the same problem twice, it shows up as the same problem.
3. It works offline. Cell service is usually the first thing to go on a remote site. The whole inspection, photos and location included, is captured on the device and syncs to the site record when service comes back. Nobody types it in a second time.
4. The record goes where the business already keeps its records. For most operators that is not only a GIS or an EHS platform. It is the project management system, the CRM or the document repository the rest of the company works out of, and the inspection record shows up there without someone having to carry it over.
5. Every inspector works from the same requirements. The permit, the SWPPP and the standards that apply to a site are attached to its inspection record, and Forerunner's AI Assistant draws on those documents when it helps an inspector complete the form, citing the passage it relied on. Photos and voice notes taken on site are turned into field values the same way at every site, so the record reflects the site's requirements rather than the habits of whoever is holding the device.