I build software for stormwater asset management, so you’d expect this article to tell you spreadsheets are terrible. They’re not. A well-kept spreadsheet beats most of what I encounter in the field, which is usually nothing at all. Some organizations genuinely should stay on a spreadsheet for now.

What follows is the honest version of the comparison: where spreadsheets hold up, the specific points where they break, and how to tell which side of the line your organization is on.

Where a Spreadsheet Is Enough

A spreadsheet works when three conditions hold. You have few assets, roughly a dozen or fewer. One person owns the sheet, keeps it current, and isn’t leaving soon. And your reporting needs are simple: an occasional status summary, not a capital forecast or an audit response.

A small HOA with two ponds and an engaged manager fits this picture. Set up one row per facility with columns for type, location, install year, last inspection date, condition, and open items. Store inspection reports and photos in one shared folder, named by facility and date, in a location the organization owns (not the manager’s personal drive). Review it at one board meeting a year. That’s a functioning program, and it costs nothing but discipline.

If that describes you, stop reading and go set up the folder structure. It’s the discipline that matters, not the tool.

The Four Breaking Points

Spreadsheet programs don’t fail gradually. They fail at specific joints, and the failures look like this.

History. A spreadsheet holds current status well and past status badly. When you update the condition column, the old value is gone. Three years in, you can’t answer the question that actually matters for planning: is this pond stable, or has it dropped a condition grade every year since 2023? Trend is the whole game in asset management, and a spreadsheet structurally can’t hold it without someone maintaining a second sheet of snapshots, which nobody does for long.

Photos and evidence. Inspection records are only as defensible as their documentation, and photos never live in the sheet. They live in a parallel folder that drifts out of sync, or on someone’s phone. When you need to prove what a facility looked like in 2024, the photo exists somewhere. Somewhere isn’t a records program. We’ve covered this failure mode in detail in how to track inspections without losing your records.

The single maintainer. Every spreadsheet program has exactly one person who understands it. The sheet is really a UI over that person’s memory. When they leave (they always leave), the next person inherits a grid of numbers with no context, and usually starts over. The organization’s knowledge resets to zero on a personnel event. For a metro district board with statutory responsibilities and decades-long obligations, that’s a fragility problem, not an inconvenience.

Derived numbers. The valuable outputs of an asset program are computed: remaining life, replacement year, 20-year capital need, reserve drawdown. In a spreadsheet these are either absent or hand-entered guesses that go stale the day they’re typed. Nobody re-derives six facilities’ replacement forecasts by hand every time an inspection comes in. So the board sees numbers that were true once, presented as if they’re true now.

What Software Actually Buys You

Purpose-built software addresses exactly those four joints, and honestly, not much else. The inspection record is created once, in the field, attached to the asset, so history accumulates instead of overwriting. Photos ride with the record, dated and located. The system, not a person, is the keeper of context, so staff turnover stops resetting the program. And the derived numbers (remaining life, capital forecast, funding gap) recompute automatically from current condition, so the board is always looking at the live picture.

That’s the entire pitch. Software doesn’t inspect your ponds or fund your reserves. It makes the record-keeping and the math continuous instead of manual, which matters in proportion to how many assets you have and how much turnover you face.

A Word on the Enterprise Platforms

If you’ve searched this space, you’ve found the big municipal asset management platforms. They’re capable systems built for cities: GIS departments, work-order management, hundreds of users, implementation projects measured in months and budgets measured in tens of thousands per year. For a district with thirty stormwater assets and a part-time manager, that’s not overkill you grow into. It’s software you’ll pay for and never fully deploy. The honest options for small programs are a disciplined spreadsheet or purpose-built lightweight software, not a city platform at district scale.

That gap is why we built DistrictWorks: the four breaking points solved (field inspections, permanent history, automatic forecasts, board reporting) without the enterprise overhead, priced for organizations that count their assets in dozens. We’ll even load your existing spreadsheet as the starting inventory, so the years of discipline that went into it aren’t wasted.

The Test

Count your assets. Then answer two questions. Could you produce any facility’s full inspection history, with photos, in ten minutes? And does your board see a capital forecast that updates when conditions change, or a number someone typed two budget cycles ago?

Under a dozen assets, one committed maintainer, and honest yes answers: keep the spreadsheet, keep the discipline. More assets than that, a looming staff change, or two no answers: you’ve outgrown the sheet, whether it feels that way yet or not.