You quoted two hours. The job took three. You billed two. Nobody wrote the third hour down — so nobody knows it happened. Multiply that by every technician, every week, and you have the single biggest leak in most repair shops.
The fix isn’t working harder or charging more across the board. It’s knowing, job by job, how long work actually takes. This guide shows a simple way to do that, how to read the numbers, and how to get your technicians to go along with it.
Why you should track time per job, not per day
Most shops already track time in one way: a payroll clock that records when someone arrived and left. That answers an important question — how many hours do I owe this person? — but it can’t answer the questions that actually decide whether your shop makes money:
- How long does a brake service really take in our shop?
- Are we quoting a full tune-up too low?
- Which jobs take longer than we charge for, and by how much?
- Is one technician slower on a certain kind of work, and why?
Those are job-level questions. To answer them, time has to be attached to the job (the work order), not to the person’s shift.
The three numbers every shop should know
For every job, keep three numbers side by side:
- Estimated time — what you expected the work to take when you wrote it up.
- Worked time — the hands-on time your technician actually spent on it.
- Billed time — the labor time you charged the customer for.
The most useful single figure is the difference between billed and worked time. If you billed 3 hours and the technician worked 3 hours 40 minutes, the difference is −40 minutes. A negative number means you gave time away. A positive number means you billed more than the clock shows, which is fine for flat-rate work, as long as you know it’s deliberate.
Here is an illustrative example (not real shop data):
| Job | Estimated | Worked | Billed | Billed − worked |
|---|---|---|---|---|
| Bike tune-up | 1h 30m | 1h 52m | 1h 30m | −0h 22m |
| Brake service | 3h 00m | 3h 40m | 3h 00m | −0h 40m |
| Chain & sprocket kit | 2h 00m | 1h 24m | 2h 00m | +0h 36m |
| Total | 6h 30m | 6h 56m | 6h 30m | −0h 26m |
Illustrative figures only.
■ Billed ■ Worked — the longer blue bar means time was given away.
Four ways shops track time (and where each one fails)
| Method | What goes wrong |
|---|---|
| Pencil on the paper ticket | Start and stop times get forgotten, rounded, or guessed at the end of the day. Tickets get lost or smudged. |
| Whiteboard or sticky notes | Great for “who’s on what”, but nobody records the hours, so there’s nothing to review later. |
| End-of-day recall in a spreadsheet | Technicians reconstruct their day from memory. Accuracy drops fast, and entering it is a chore nobody wants. |
| Payroll time clock | Accurate for attendance, but it tracks the person, not the job, so it can’t tell you what any job really cost. |
| Start / Stop on the job | Works when it takes one tap and sits where the technician already works. This is the method worth aiming for. |
How to set it up in six steps
- Decide what counts as “worked” time. A good rule: the timer runs while hands are on the vehicle, or the technician is actively diagnosing, ordering or documenting that specific job. Write it down so everyone uses the same definition.
- Allow one running timer per technician. A person can only work on one thing at a time. Starting a new job should automatically stop the previous one, which removes the most common source of double-counted time.
- Make it two taps. Start when you begin, Stop when you pause. If there are more steps than that, it won’t survive a busy Saturday.
- Stop the timer when you’re waiting. Waiting on parts, on a customer’s approval or on a delivery isn’t hands-on time. Flag the job instead (for example “Parts Hold”) so the board still shows why it’s sitting.
- Record an estimate on every job. Even a rough estimate gives you something to compare against, and a clear work order is the natural place to keep it (see what to put on a repair work order). Without it you can see how long a job took, but not whether that was normal.
- Review once a week for fifteen minutes. Look at the jobs where worked time and billed time differ most. That short, regular habit is where the value is.
What to do with the numbers
Once you have a few weeks of data, look for patterns rather than individual jobs:
One job type is always over
If every brake service runs 40 minutes longer than you billed, the problem is your quote, not your technicians. Raise the labor estimate for that service, or add a clearly priced line for what’s taking the extra time.
One technician is often over
That can mean a training gap, a missing tool, a poorly set-up bench, or simply that they take on the hardest jobs. Ask before you assume. The data tells you where to look, not who is at fault.
You’re always under
If you consistently bill more than the clock shows, either your technicians are very efficient or your quotes are padded. Check that customers aren’t noticing: quotes that are too generous cost you work.
Getting your technicians on board
- Explain the why. “We’re pricing jobs more accurately so we don’t keep underquoting you into long days” lands far better than “we need to track you”.
- Start with yourself. If owners and managers run timers on their own jobs first, it’s clearly a shop habit, not a spy tool.
- Keep it fast. Anything slower than a couple of taps will be skipped when it’s busy.
- Show people their own numbers. Technicians should be able to see their own hours and results, not just the boss.
- Celebrate the wins. When a job comes in faster than estimated, say so. It reinforces that accurate times help everyone.
Common mistakes
- Rounding everything to the nearest hour. You lose exactly the detail you’re trying to find.
- Tracking breaks and admin on the job. It muddies the numbers. Keep the timer for hands-on work only.
- Forgetting to stop. A timer left running overnight creates a ten-hour brake job. Build the habit of stopping at the end of the day, and review obvious outliers.
- Judging a single job. One long job is noise. A trend across twenty is information.
- Collecting data and never looking at it. The weekly fifteen-minute review matters more than the software you use.
A one-page checklist
- Every job has an estimate before work starts.
- Technicians start and stop a timer on the job, not just on their shift.
- Only one timer runs per person at a time.
- Waiting time is flagged, not clocked.
- Billed time is recorded on every closed job.
- You compare estimated, worked and billed time at least weekly.
- You adjust quotes, training or tools based on patterns, not single jobs.
How BayBoard handles this
This is exactly how we built time tracking in BayBoard. Technicians tap Start and Stop right on the job, and starting a new job stops the last one automatically. Reports show estimated, worked and billed time for each technician and each job, with the difference shown as a negative number when you’ve given hours away. Technicians see their own numbers, and owners and managers see the whole shop. There’s a one-click CSV export, and quick ranges for the last 7, 15 or 30 days.
If you’d like to see it with your own kind of jobs, book a free demo, or check pricing — BayBoard doesn’t charge per user.
Find the hours your shop is giving away.
Track time per job, compare it with what you billed, and fix your quotes with real numbers.
Frequently asked questions
How do you track technician time in a repair shop?
Track time per job rather than per shift. The technician starts a timer when they begin working on a job and stops it when they pause or finish, and you compare that worked time with the estimate and with what you billed the customer.
What is the difference between worked time and billed time?
Worked time is the hands-on time a technician actually spent on a job. Billed time is the labor you charged the customer for. The difference between them shows whether you gave time away or billed more than the clock shows.
What is technician efficiency?
Many shops divide billed time by worked time to get an efficiency percentage. Close to 100 percent means billed and worked time match. A figure well below 100 percent means hours are leaking out of your jobs.
Should technicians keep the timer running while waiting for parts?
No. Stop the timer while you are waiting on parts, approvals or deliveries so worked time reflects hands-on work, and flag the job instead so the board shows why it is waiting.
