We are here for you
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
.webp)
A regional carrier in Ohio kept repairing a 2016 Class 8 tractor for fourteen months past the point where replacing it would have been the cheaper decision. By the time anyone added it up, the fleet had spent $34,000 in cumulative repairs on a truck with a trade-in value of $18,000. Nobody made a bad call in the moment. Each repair, approved individually, looked reasonable on its own. What was missing was not judgment. It was the expense tracking per unit that would have shown the cost trajectory screaming "replace" from month nine onward, instead of a series of disconnected invoices that never got assembled into a decision.
That gap, not a lack of frameworks, is the actual reason most fleets get this decision wrong. The repair-versus-replace math is well established and not particularly complicated. What most 10 to 50 truck fleets are missing is not the formula. It is clean, per-unit cost history to run the formula against.
The most commonly cited decision rule in fleet replacement analysis is straightforward: when a single repair estimate reaches roughly 50% of a truck's current market value, the math favors replacement over continued repair. A 30% threshold on trailing annual maintenance cost relative to value serves as an earlier warning sign, and multiple fleet cost analyses document that once a truck's annual maintenance spend crosses that 30% mark, the trajectory typically doubles within twelve months and can triple within three years. This is often called the 50/30/20 rule, and it gives a fleet manager three reference points rather than one binary threshold: 20% of value is a signal to start watching closely, 30% is an active warning, and 50% on a single repair estimate is the point where the math clearly favors replacement.
Cost per mile is the more precise version of the same signal, because it captures the trend rather than a single data point. American Transportation Research Institute data documents a cost curve that stays relatively flat for the first several years of a truck's life, then rises steeply once the vehicle passes roughly the 6 to 10 year mark, moving from approximately $0.15 per mile in that earlier window toward $1.10 per mile or higher in the years beyond it. ATRI's broader fleet operating cost data places the average Class 8 replacement cycle at approximately 7.3 years, though that figure is an industry average, not a rule that applies uniformly to every truck regardless of its actual maintenance history.
The reason cost per mile matters more than age alone is that two trucks of identical age can be at completely different points on that curve. A truck that has been through consistent, documented preventive maintenance may still be well inside its economic life at year eight. A truck of the same age and mileage that has accumulated a pattern of reactive repairs may have already crossed the threshold at year five. Age is a starting guardrail. Actual per-unit cost data is what confirms or overrides it.
None of this framework is difficult to apply once the inputs exist. The problem for most fleets in the 10 to 50 truck range is that the inputs do not exist in a usable form.
Running the 50/30/20 rule or a cost-per-mile trend requires trailing twelve-month repair and maintenance spend for each individual truck, categorized consistently enough that the numbers can actually be compared against a current fair market or trade-in value. For a fleet routing trucks through whatever shop is convenient at the time, with invoices that vary in format from a detailed work order to a one-line total, that data simply does not exist as a coherent trail. The in-house versus outsourced cost analysis on this site covers a related version of this problem: fleets without a structured maintenance program are not just paying more per repair, they are also losing the data trail that would tell them which specific trucks are driving that excess cost.
This is precisely the situation the Ohio fleet was in. Fourteen months of individually-approved repairs on the same unit, each one authorized without anyone stepping back to view them as a trend, because nobody had assembled the twelve preceding invoices into a single per-truck cost line. A fleet manager reviewing a stack of unconnected repair bills sees fourteen separate, reasonable-looking decisions. The same fleet manager reviewing a single chart showing that truck's monthly cost climbing steadily past the 30% threshold sees a different, much more obvious decision.
The self-managed fleet maintenance tipping point article on this site identifies rising cost per mile as an early signal that can indicate either a maintenance process problem across the fleet or a specific vehicle approaching its replacement threshold. Distinguishing between those two causes is only possible with per-unit data. Without it, a fleet manager cannot tell whether a rising average cost per mile means one truck needs to be sold or the entire program needs restructuring.
Applying the repair-versus-replace framework correctly for a specific truck requires three data points assembled together, not separately.
The first is trailing twelve-month repair and maintenance cost for that specific unit, broken out from the fleet average. A fleet-wide average cost per mile can look acceptable while masking two or three specific trucks that are driving most of the excess spend, exactly the pattern the full maintenance plan comparison on this site describes when discussing per-unit expense tracking as a distinct capability from pooled fleet totals.
The second is a current trade-in or fair market value estimate, obtained close to the time of the decision rather than an outdated figure from when the truck was purchased. Values shift with market conditions, and a repair-versus-replace calculation run against a stale valuation produces a misleading threshold.
The third is the downtime cost associated with the truck's repair pattern, not just the invoice totals. A $2,500 repair that takes a revenue-generating truck out of service for four days at a meaningful daily contribution margin has a real cost well above $2,500 once the lost operating days are included. Fleet cost analyses commonly note that the invoice is not the full cost of a repair event, and a truck with a pattern of extended downtime per repair is a different economic case than one with the same invoice totals but faster turnaround.
A fleet manager with these three inputs assembled per truck can run the 50/30/20 comparison or track the cost-per-mile trend directly. A fleet manager without them is making the decision the way most fleets actually make it: on a rough mental estimate and a gut feeling about whether a particular truck has been reliable, which is right often enough to seem like a working method and wrong often enough to produce a $34,000 outcome on an $18,000 asset.
If your fleet's maintenance spend is currently scattered across shop invoices with no consistent per-unit categorization, building this data manually means pulling twelve months of repair history per truck and reconstructing the trend by hand, a task that takes real time across a fleet of any size and needs to be repeated every time the decision comes up again. A coordinated preventive maintenance program that tracks expense history per unit as a standard part of service produces this data continuously rather than requiring a one-time reconstruction project every time a truck's reliability becomes a question.
The repair-versus-replace framing implies two options, but fleet lifecycle analyses commonly identify a third path worth considering before either extreme: a mid-life rebuild or refurbishment on a truck whose chassis and structural condition remain sound even though specific major components, an engine or a transmission, have reached the point of requiring significant work. This option sits between full replacement and continued piecemeal repair, and it is only visible as an option when the underlying data, condition assessment alongside the cost trend, is available to evaluate it properly.
The right choice among the three options depends on where the specific truck sits on its cost curve, what condition its frame and structural components are in independent of the failing system, and what the fleet's near-term operating plans require. None of that evaluation is possible from invoice totals alone. It requires the same per-unit cost history and condition tracking that the core repair-versus-replace decision requires, which is the same data gap this entire framework runs into without structured tracking in place.
The math behind this decision is not the obstacle. Most fleet managers running 10 to 50 trucks could apply the 50/30/20 rule correctly if the inputs were sitting in front of them. The actual obstacle is that the inputs are scattered across a year of invoices from however many different shops the fleet used, in whatever format each shop happened to produce, with no per-unit trail connecting them into a trend anyone can act on before the decision becomes obvious in hindsight.
The fleet maintenance plans page covers how the coordination program tracks expense history per unit as part of the service itself, which means the data this decision requires is a byproduct of how the fleet's maintenance already gets managed, not a separate system to build or buy. If you want to understand what your fleet's current per-unit cost trends actually look like and whether any specific units are approaching their replacement threshold, reach out through the contact page with your fleet profile and recent repair history. That conversation is a lot more useful with real numbers in front of us than with an industry rule of thumb applied blind.
This article draws on the following sources:
