Repair spend is useful, but the total invoice value rarely tells the whole story. A vehicle with one large planned job can create less disruption than another with several smaller unplanned failures. A good small-fleet review therefore keeps cost, event frequency, downtime, and repeat problems visible together.

Define what “maintenance cost” means

Before comparing vehicles, publish a simple cost dictionary. Categories might include:

  • planned maintenance;
  • unplanned repair;
  • tires, if tracked separately;
  • tow or roadside cost;
  • diagnostic or inspection cost where billed separately;
  • recall or warranty events, with the fleet-paid amount separated from amounts covered by another party;
  • other defined maintenance.

Fuel, insurance, registration, finance, depreciation, tax, tolls, and accident costs may matter to whole-life economics, but they should not drift in and out of a maintenance measure without an explicit definition.

Consistency matters more than building a long chart of categories staff cannot apply reliably.

Keep cost periods aligned

A cost-per-mile calculation is meaningful only when the numerator and denominator describe the same period.

Maintenance cost per mile = defined maintenance spend during the period ÷ miles driven during the same period

Use trusted odometer readings close to the start and end of the analysis window. If the mileage window is weak, mark the result as low confidence rather than presenting false precision.

A large one-off event does not need to be removed. Give it context by showing the event count, planned versus unplanned split, and downtime alongside the total.

Define downtime before measuring it

Different “downtime” clocks answer different questions. Consider separating:

  • Technical out-of-service time - how long the vehicle could not be used because of a maintenance or repair condition;
  • Shop cycle time - handoff to return;
  • Business-impact time - how long the operation actually lacked needed vehicle capacity.

Those numbers can be very different. A vehicle may sit at a shop over a weekend while a spare prevents disruption. Another vehicle may be unavailable for only a few hours but cause a cancelled job.

Choose the definitions that support real decisions and use them consistently.

Look for repeat events without pretending the category is a diagnosis

A simple administrative repair taxonomy makes patterns easier to filter. Categories can cover areas such as brakes, tires, electrical, steering/suspension, HVAC, body, or scheduled service.

A repeat-event rule should mean review this history, not we have diagnosed the cause.

Two events in the same broad category may still be unrelated. Open the underlying service records before concluding that the vehicle has a recurring technical fault.

Compare a vehicle with itself and with genuinely comparable units

Mixed fleets can make simple league tables misleading. Compare like with like where possible: similar vehicle type, age, mileage, duty, analysis period, and cost definition.

Also look at a vehicle’s own trend. Rising unplanned events or downtime can deserve attention even when the total cost still looks ordinary compared with a larger or harder-working unit.

Useful monthly evidence can include:

  • overdue or due-soon maintenance;
  • open defects;
  • rolling maintenance cost;
  • planned versus unplanned spend;
  • unplanned event count;
  • downtime;
  • repeat-category flag;
  • data-confidence note.

Do not use a universal repair-versus-replace percentage

There is no honest single rule such as “replace the vehicle when repairs exceed X percent of value.” The decision depends on the vehicle’s mission, reliability, future cost exposure, capital, availability of replacements, market value, warranty or lease position, lead time, and other business constraints.

Instead, define internal review triggers. Examples include repeated unplanned events, material downtime, unusually high maintenance cost among comparable units, a major repair estimate on an aging vehicle, mission mismatch, parts-availability problems, or an approaching planning milestone.

A trigger means assemble the evidence, not sell the vehicle.

Build a repair-versus-replace evidence pack

Bring the decision into one place:

  • vehicle identity, age, mileage, and duty;
  • reliable 12- and 24-month maintenance history where available;
  • planned versus unplanned cost;
  • breakdown count and downtime;
  • repeat categories;
  • known open work and recommendations;
  • qualified condition information where needed;
  • current market or disposal evidence;
  • replacement options, cost, and lead time;
  • future mission requirements;
  • warranty, lease, finance, tax, and accounting inputs from the appropriate sources;
  • the cost and operational risk of keeping the current unit over the next decision horizon.

Then compare the forward choices rather than letting sunk cost or repair fatigue make the decision.

Record the decision and the next review trigger

If management chooses to repair and retain the vehicle, document why and specify what would cause the question to return. If replacement is chosen, preserve the evidence that supported it.

That small decision log prevents the same debate restarting from memory at the next meeting.

For the operating workflow behind the data, see the fleet defect and repair workflow and small fleet maintenance system guide.

Scope: Cost and replacement decisions may involve technical, finance, tax, accounting, safety, legal, warranty, and operational considerations. Use the appropriate current professional and official sources rather than treating a fleet spreadsheet as the final authority.

Working tools

Use the free due date and mileage calculator to check one verified requirement. The Small Fleet Maintenance System connects recurring rules, actions, completion evidence, costs and downtime across several vehicles.