Here’s a test. Pick any stormwater facility your organization owns and try to produce its last three inspection reports, with photos, in under ten minutes.
Most districts, municipalities, and HOAs I work with can’t do it. The inspections happened. Somebody walked the pond, took photos, maybe filled out a form. But the records are spread across a consultant’s files, a retired manager’s hard drive, three email threads, and a binder in a storage closet. The organization paid for the inspections and can’t use them.
This matters for two reasons. The practical one: inspection history is what tells you whether a facility is stable or deteriorating, and a single inspection without history is a snapshot with no trend line. The legal one: when a regulator, an auditor, or a downstream property owner’s attorney asks what you knew about a facility’s condition and when you knew it, your inspection records are the answer. Records you can’t produce don’t exist.
Why Records Scatter
Nobody decides to lose their inspection records. It happens structurally, for predictable reasons.
The records follow the person, not the asset. The inspector (staff or consultant) generates a report and stores it wherever they store things. When the person changes, the storage location changes. Five years and two consultants later, the history is in three places, none of them yours.
The report is a document, not data. A PDF inspection report answers the question it was written for. It can’t answer the questions that come later: which of our facilities is deteriorating fastest, what did this pond look like four years ago, which assets are overdue. To answer those, someone has to open every PDF and rebuild the history by hand.
Photos live apart from findings. The photos end up in a phone backup or a folder named something like IMG_2019. Without a date, a facility ID, and a location attached to each photo, they degrade from evidence into decoration.
What a Defensible Record Contains
Whatever system you use, each inspection record should carry: the facility identifier and location, the inspection date, who performed it, the condition rating against a consistent scale, specific findings tied to specific components (outlet, embankment, forebay, vegetation), photos with dates and locations, and the follow-up actions with their status.
That last item is the one that separates a paper program from a real one. An inspection that finds a problem and generates no tracked follow-up is worse than no inspection. It documents that you knew and didn’t act.
The Spreadsheet Stage, and Where It Breaks
Most organizations graduate from nothing to a spreadsheet, and honestly, a well-kept spreadsheet is a big step up. One row per facility, columns for last inspection date, condition, and open items. If your organization owns eight facilities and one dedicated person keeps the sheet current, it can work for years.
It breaks at predictable points. Photos never fit, so they stay orphaned somewhere else. History doesn’t fit either: a spreadsheet holds current status well and prior status poorly, so the trend line disappears. And the sheet depends entirely on the discipline of whoever maintains it. When that person leaves, the spreadsheet becomes one more record nobody can interpret.
The failure isn’t the spreadsheet. It’s that the spreadsheet holds a copy of the truth, maintained by hand, parallel to where the work actually happens. Every manual copy step is a place for records to fall through.
What Good Looks Like
The systems that survive staff turnover share one property: the inspection record is created once, in the field, attached to the asset, and everything downstream reads from it. No transcription. No parallel copies. No dependence on one person’s filing habits.
In practice that means the inspector stands at the facility with a phone, rates the condition, photographs the deficiencies (with GPS and date captured automatically), notes the findings, and saves. The asset’s history grows by one entry. The facility’s condition updates. Anything overdue gets flagged. When someone asks for the last three inspections with photos, it’s a filter, not an archaeology project.
This is the workflow we built into DistrictWorks. Field mode sorts your assets by inspection priority, walks the inspector through each one, and files the record against the asset the moment it’s saved. The condition history, the photos, and the capital forecast all stay attached to the facility, not to whoever happened to do the inspection that year.
If You Fix One Thing
Make the inspection record inseparable from the asset. Software does this well, but even without it, you can enforce the principle: every inspection gets filed by facility ID in one shared location your organization controls, not the inspector’s. Consultant contracts should require delivery of records in that structure, with photos labeled.
Your inspection program is only as good as your ability to produce its records. Ten minutes, any facility, last three inspections, with photos. If you can’t pass that test today, that’s the gap to close, and closing it costs far less than the first time you need those records and don’t have them.