The Brake Job the Contract Ate

Pull the last month of work orders for your biggest flat-rate account and read them line by line. Say it's a regional distributor's fleet, thirty trucks at $185 a truck a month, covering scheduled maintenance: oil and filters, chassis lube, brake adjustment, a DOT inspection on rotation. Unit 41 came through on the 9th for its PM. Line six of the work order reads: steer axle brake shoes at the wear line, replaced. Three and a half hours, $410 in parts. The work order closed to the contract, all six lines of it, because that's how work orders close on that account.

Nobody decided to eat a brake job. The service writer closed a PM ticket on a contract truck, which is what it was. The decision happened anyway. It just happened as a default.

Every line needs a payer

One ticket, one billable event. In a shop, the ticket is the work order, and the principle cuts finer than it does at a scale house. Every line on that work order is its own event, and every event has exactly one payer. The contract pays for what Exhibit B lists. The customer pays for repairs outside it. A vendor pays for warrantable parts. You pay for comebacks. Those are the only four answers, and a work order isn't really closed until each line has one.

A flat-rate contract quietly replaces that question with an account setting. The rate went into your billing system the week the deal was signed: thirty units, $185, invoice on the first. Exhibit B, the two pages that say what $185 actually buys, went into a folder. So the system knows what to charge and has no idea what the charge covers, and every line written against that account inherits the same answer: covered.

The brake job wasn't covered. Exhibit B says inspect and adjust; shoes and hardware are a repair, billable at time and materials per paragraph 9. Nobody looked, because looking is a separate act, and closing is one keystroke.

The default wins every argument it never has

Watch how the shop's own rhythm protects the default.

The tech does the right thing mechanically. The truck's on the lift, the wheels are off for the inspection the contract does cover, and shoes at the wear line are a now problem, not a next-visit problem. Writing the repair on the open work order is the honest record. Opening a second, billable repair order means a call to the fleet manager for approval, and the truck holds the lift while everyone waits. One work order keeps the day moving.

The service writer closes it at 5:40, eleven work orders deep. Adjudicating line six means pulling Exhibit B, deciding whether "brake adjustment" stretches to cover shoe replacement, and starting an $800 conversation with a customer who thinks his flat rate buys quiet months. Closing to contract means none of that. And the gray areas are real: is a leaking wheel seal found during a covered inspection a covered find or a billable repair? Reasonable people differ. But gray plus a deadline resolves to the default every time, and the default on a contract account is free.

Notice the one-way traffic. Put a covered item on an invoice and the fleet manager catches it by Friday; he has his own copy of Exhibit B and reads it whenever reading it saves him money. Absorb a repair into the flat rate and no one on either side will ever mention it. He may not even notice; his truck just got fixed. The errors that overcharge get corrected. The errors that undercharge get archived.

flowchart TD
  A["Work order line: brake shoes, 3.5 hrs, $410 parts"] --> B{"Who pays for this line?"}
  B -- "today: the default answers" --> C["Closed to contract"]
  C --> D["Absorbed into the $185 flat rate"]
  B -- "line checked against a scope table" --> E["No covered operation matches"]
  E --> F["Flagged as non-compliant that day"]
  F --> G["Bills at T&M on the monthly invoice"]

The leak that reads as bad pricing

Put illustrative numbers on it, yours to redo from your own rates. One absorbed repair a week on that thirty-truck account, at an average of $340 between labor and parts, is about $17,500 a year sliding under a contract worth $66,600. More than a quarter of the account's revenue, gone, with every invoice arithmetically perfect.

Here's the part that costs more than the $17,500. Your accounting can't see an absorbed repair as leakage; it sees contract work with terrible margins. So at renewal you conclude flat-rate work doesn't pay, and one of two things happens. You raise the rate 12 percent to cover costs the contract never owed, and the distributor takes his thirty trucks to the shop across town that bid it right. Or he accepts the increase, and now he's overpaying to subsidize your closing habits. Either way, the pricing took the blame for the paperwork. The rate was never the problem.

So here's the claim to argue about at the counter: a shop that won't adjudicate scope line by line makes more money on plain time and materials, and should stop selling flat rates entirely. Flat rates smooth your revenue and win fleet deals, sure. But a flat rate is a bet that you'll police the boundary of what it covers, and a shop that closes every contract ticket on one keystroke has already lost that bet. T&M at least bills what happened.

Make covered a verdict

A memo about diligence won't fix this. The fix is moving Exhibit B from the folder into the same system the rate lives in, so the question every line needs gets asked by structure instead of by a service writer at 5:40.

The scope is reference data: each contract's covered operations, covered parts classes, labor caps if you wrote them, effective dates. Your T&M door rate and parts markup are billing rules, along with whatever repair discount contract holders earned. Work orders get digitized as they close, line by line, and each line checks against the scope for its account. A line whose operation Exhibit B covers rides the flat rate, same as today. A line that matches nothing covered gets flagged as non-compliant that day, while the tech still remembers the shoes and the approval is a same-week phone call instead of a line-item argument in March.

Month end, the invoice assembles from what cleared: the flat line, plus every repair line that priced against a rule. That machinery, digitizing the tickets, flagging the ones that break scope, structuring the rules, holding the reference data, assembling the totals, is what Termco builds. Where the line between adjustment and repair sits stays your call. It just gets made once, in the scope table, instead of eleven times a night at the closing screen.

You can size the leak this week with a highlighter. Pull last month's work orders for your biggest flat-rate account and mark every line whose operation doesn't appear in Exhibit B. Price the marks at your posted door rate and your normal parts margin. That's one month, one account. Multiply by your contract count before you decide the flat-rate business is the problem.

If you'd rather have a second reader on the stack, send 10-20 sample tickets to hi@termco.ai, work orders from flat-rate accounts especially, and we'll send back what we find within 48 hours.