There is nothing wrong with starting in Excel. The problem is that spreadsheets fail quietly — you do not notice the cost until a decision goes wrong.
1. There is more than one version of the truth
The moment the engineer, the supervisor and the finance office each maintain a copy, the numbers stop matching and every meeting starts with reconciling them.
2. Nobody can produce a map
Infrastructure decisions are spatial. If answering 'which streets in Ward 3 are below fair condition' requires a filter, a join and a GIS request, the data is not usable at the speed decisions are made.
3. Condition history is overwritten, not recorded
Spreadsheets tend to hold the current score. Overwrite it and you have destroyed the time series that deterioration modeling depends on — the single most valuable dataset an agency owns.
4. Reporting is a multi-day project
If the annual condition report takes a week of copy-paste, it will be produced once a year, which means decisions the rest of the year run on memory.
5. You cannot answer 'what if'
When council asks what happens under flat funding for five years, a spreadsheet cannot answer without a model. That question is where budget increases are won or lost.
Frequently asked questions
- Can we import our spreadsheet into AtlasView?
- Yes. Spreadsheet imports are a standard part of onboarding, and migration support is included in every plan.
- Is dedicated software worth it for a small network?
- The threshold is usually decision complexity rather than network size. If you are making multi-year funding decisions, modeling pays for itself quickly.