Evidence-Driven Municipal Maintenance: From Calendar to Condition
I stood on a street in Malmö last winter, ankle-deep in slush, staring at a pavement that had been "inspected" three months earlier and declared fine. It was now a mosaic of cracks wide enough to swallow a bicycle wheel. The maintenance crew? They were across town, resurfacing a road that looked perfectly drivable to me. Why? Because the calendar said so.
This is the madness municipalities live with. Thousands of assets — roads, lights, drains, signs, green spaces — and a budget that would not cover a decent dinner party. The traditional answer? A calendar. Inspect annually. Maintain on rotation. React to complaints when they pile high enough to attract media attention. Resources smeared thin across everything, prioritised by neither urgency nor reality.
Evidence-driven maintenance throws the calendar out the window. You maintain what observation shows needs maintaining — and you can prove it.
The problem with calendar maintenance
Calendar-based schedules have two fatal flaws, and I have seen both up close:
Over-maintenance. Assets in good condition get attention because the schedule demands it. Crews resurface roads that do not need it while the actual disasters fester. The waste is invisible in the budget — it looks like efficient execution. It is not.
Under-maintenance. Assets that deteriorate faster than the schedule assumes fail between inspections. Emergency repairs. Higher costs. Public outrage. This too hides in the budget as "unavoidable emergency spend." It is entirely avoidable.
Neither problem gets questioned because neither is measured against actual condition. The calendar is the oracle, and the calendar does not care what is really happening on the ground.
What evidence-driven maintenance looks like
An evidence-driven system has three parts, and they are brutally simple:
Continuous observation. Not once a year by a survey team with clipboards. Regular observation by a distributed network. Condition, location, timestamp, photographic proof. No trust, just evidence.
Condition scoring. Every asset gets a number. A pavement rated 62 can be decomposed to show exactly which defects contributed. The score is transparent. Arguable. Actionable.
Priority-based scheduling. Maintain by condition score and deterioration trend, not by calendar position. A rapidly declining asset jumps the queue over a stable one, even if the stable one is "due" first. The data decides. Not the date.
The political benefit: provable need
Here is where it gets interesting. Evidence-driven maintenance changes the entire political game around funding.
A maintenance director who asks for more budget because "we think things are getting worse" gets scepticism. Politicians have heard that song before. But the same director who walks into a council meeting with a condition map — exact assets, exact deterioration, exact consequences — makes a case that is hard to refuse. The evidence does the talking.
It also protects against arbitrary cuts. When someone proposes slashing the maintenance budget, the condition data shows precisely what will be deferred and what the risk is. You cannot argue with a photograph of a crack widening into a chasm.
From reactive to predictive
The endgame is not just better scheduling. It is prediction. A trend of deterioration, observed continuously, can be extrapolated to estimate when an asset crosses the failure threshold. The municipality schedules intervention before failure — at lower cost, with less disruption, and with the evidence to justify the timing.
I have seen this work. I have also seen what happens when it does not. The difference is not technology. The difference is whether someone had the courage to trust what the ground was telling them.
Request a pilot →