Two numbers on every line, not one
Picture a four-bay independent shop at the end of a busy month. The service writer sold plenty of labor. The technicians feel like they worked every minute. Yet the owner looks at the numbers and cannot tell which jobs made money and which ones quietly ate an afternoon. One brake job paid two hours and took four because a seized caliper bolt snapped. A diagnostic paid one hour and took three because the problem was intermittent. Nobody wrote any of that down in a place the owner could find.
That scene is an original illustration, not a TwoQM client and not a measured result. It describes a common gap: shops track the hours they bill, but not the hours the work actually took, and not why the two numbers were different.
This article walks through a simple way to record both numbers on every repair order, so job costing stops being a guess. It is about operations and records, not about how you pay your technicians. Pay plans, flat-rate rules, and wage questions belong with your accountant or employment advisor.
Most shop systems already store the labor hours charged on each repair order line. That is the "flagged" or billed number. What is often missing is the actual time a technician spent on that same line.
Keep both numbers side by side, on the line, not in a separate spreadsheet:
Billed hours: what the customer is charged for that labor line.
Actual hours: clock-on and clock-off time for that technician on that line.
Technician: who did the work. If two people touched the line, each gets their own time entry.
Variance reason: a short pick list, filled in only when actual time is well over or well under billed time.
When the numbers live on the same line, you can answer "did this job make money?" without opening three programs.
Clocking on and off without slowing the bay
Technicians will not use a time clock that costs them time. Keep it to two taps from a tablet or phone in the bay: pick the repair order line, start; pick it again, stop. If a technician switches to another car to wait for a part, they stop the first line and start the next one.
Set a few house rules and write them down:
Diagnostic time is clocked on the diagnostic line, not folded into the repair line.
Waiting for parts or customer approval is not working time on the line. Stop the clock and note why.
Comebacks and redo work are clocked on their own line, linked to the original repair order.
If someone forgets to clock, a service manager can correct the entry, and the system keeps both the original and the correction.
A short list of variance reasons
Free-text notes are hard to add up. A short pick list is easy:
Seized, rusted, or broken fastener
Intermittent or hard-to-reproduce problem
Wrong or missing part
Added work found during the job
Learning a new procedure or vehicle
Comeback from an earlier repair
Allow one optional note for details. Ask for a reason only when the gap is large enough to matter in your shop, a threshold you choose, so technicians are not filling in forms on every oil change.
What the owner reviews each week
With both numbers on every line, a weekly review gets practical:
Which job types run over their billed time again and again?
Which variance reasons show up most, and are they fixable (parts ordering, tools, training) or just the reality of older vehicles?
Which repair orders had comebacks, and how much unbilled time did they take?
Are diagnostic hours being charged, or given away?
None of these questions need an exact answer to be useful. They show where to look. Maybe your labor guide time for a certain job is unrealistic for the vehicles you see. Maybe parts delays are costing more bay time than anyone assumed.
If your shop already uses customer approval thresholds on the repair order and special-order parts status, the same record ties it together: approved work, the parts it waited on, and the time it really took. The article on HVAC job costing and change orders covers the same idea for field trades.
Bilingual bays
Many shops in the Rio Grande Valley run in English and Spanish. Put the clock screens and the variance pick list in both languages, stored as the same codes underneath. A technician picks "Pieza equivocada o faltante" and the owner's report reads "Wrong or missing part" for the same line. Nobody translates notes after the fact.
Where TwoQM fits
Many shop management systems handle repair orders well but leave actual time and variance reasons out, or bury them. Custom software can add a simple bay clock and variance screen tied to your repair orders. Connected systems can pull repair order lines from the tools you already use so nobody retypes them, and business automation can flag lines that ran far over billed time for the service manager to review. What fits your setup is confirmed during scoping. See how TwoQM supports auto repair shops.
Where AI helps, and where it stops
AI can summarize a week of variance reasons, group similar notes, and draft a short list of job types worth a closer look.
AI does not change billed hours, adjust a customer's invoice, decide anyone's pay, or judge a technician's performance. A person on your team does.
Where to start this week
Pick one job type you do often, such as front brakes or a check-engine diagnostic. For the next two weeks, record billed and actual time on every one of those lines, with a variance reason when the gap is large. Then look at the list together with your service writer and lead technician.
TwoQM builds custom software, automation, and connected systems for small businesses in the Rio Grande Valley and beyond. Pricing explains how business apps, systems, and custom software are scoped.
Describe Your Repair Order Time Tracking · Explore TwoQM Custom Software