Every fleet director eventually stands in front of a budget committee and says a version of the same sentence: "this vehicle needs to go." The ones who get funded aren't the ones who feel it most — they're the ones who show up with a score, not a story. This walks through the scoring framework, the break-even math, and the one-page report that actually moves a council vote. For the cost data behind it, see the full vehicle lifecycle management checklist or how total cost of ownership is actually calculated.
Turn "it's getting old" into a number council can't argue with
Replacement requests built on a documented score get funded. Requests built on frustration get deferred another budget cycle — while the vehicle keeps costing you.
The 5-criterion scorecard that holds up in a budget hearing
Councils push back on capital requests by default. A score built from five documented criteria turns "this truck feels old" into a recommendation nobody can wave away with a single question.
The break-even math behind "repair or replace"
Depreciation is steepest in a vehicle's first three years, then flattens. Maintenance does the opposite — low early, then climbing fast once a vehicle passes the seven-to-eight-year mark. The right replacement point is where those two curves cross.
Two thresholds worth flagging on their own
A single repair estimate above roughly 50% of the vehicle's current residual value, or annual maintenance spend crossing 25–50% of original purchase price, is generally where the financial case for replacement stands on its own — independent of the full five-point score.
See your fleet's scores before the next budget cycle
A short walkthrough shows this scorecard and TCO math built from your own maintenance history.
What waiting actually costs
One municipal fleet ran this exact scoring model across its aging units, flagged 34 vehicles, and cycled 22 of them on schedule instead of waiting for failures. The result, one budget year later:
None of that came from buying more vehicles — it came from replacing the right ones, on a documented schedule, before they became emergency repairs.
The one-pager council actually reads
Every replacement request that survives a vote fits on one page: the vehicle, its score, its cost trajectory, and a plain recommendation. Nothing else gets read before the vote.
Government vehicles run an average of 7.4 years in service against roughly 3.9 years in the private sector, and procurement alone can take 18 to 36 months — which is exactly why the score needs to be ready before the budget window opens, not after.
Frequently asked questions
What's a reasonable point system to start with?
Many municipalities use a simple additive model — one point per fifth of a vehicle's target age, target mileage, and target maintenance cost — with points uncapped so chronically expensive units keep rising to the top of the list.
Does a high score mean the vehicle must be replaced?
No — it means the case is strong enough to bring to council. Department needs, funding timing, and safety findings can still justify moving a request up or holding it, but the score keeps that conversation grounded in data.
How is the maintenance cost ratio actually calculated?
Cumulative parts, labor, and outside repair costs divided by the vehicle's original purchase price. A vehicle that's consumed 30% of its purchase price in repairs is generally an early warning; 50% is a serious review point.
Can this scoring model run across mixed asset classes?
Yes — each class (police, fire, refuse, parks, admin) gets its own age, mileage, and cost benchmarks, so a patrol sedan and a snowplow are never scored against the same target.
How does FleetRabbit help build this report?
It tracks maintenance history, mileage, and downtime per vehicle automatically, then rolls that data into the cost-per-vehicle and lifecycle reports fleet teams bring to council and budget hearings.
Build your next replacement case on data, not frustration
Get the scorecard and lifecycle reports ready before your next budget cycle opens.
