What do I do about techs who won't clock into jobs properly?
Short answer
Make clocking in the job the same physical action as picking up the ticket, and treat unclocked time as lost data you have to chase every single time it happens.
Most of the time it's friction, not defiance
Techs skip clocking into a job because it's an extra step that interrupts getting their hands dirty, not usually because they're trying to hide something. If your system requires walking to a terminal, logging in, and searching for the right RO, plenty of techs will just skip it on quick jobs.
Fix the friction before you write a policy
Put a tablet or terminal at each bay if you can, or make the paper ticket itself double as the clock in slip that a tech hands to the advisor the moment they start. The fewer steps between picking up a job and having it logged, the more compliance you'll get without a single conversation.
If it's flat rate pay, tie their own paycheck accuracy to clocking in properly. Once a tech realizes unclocked time is unpaid time on their own check, most fix the habit fast.
For the ones who still won't do it
After you've fixed the system friction, treat repeated non-compliance as a direct performance conversation, not a shrug. Unclocked time wrecks your effective labor rate, your job costing, and your ability to know which techs are actually productive.
Talking to a tech who keeps skipping clock-ins
You
“I noticed three jobs this week you worked on that never got clocked in. What's going on there?”
Tech
“I just get busy, I forget sometimes.”
You
“I get it, that's why we moved the tablet right to your bay. But I need every job clocked, it's how I know we're profitable and it's how your flat rate hours get counted right. Can you commit to clocking in before you touch the car, every time, starting today?”
Fixing the system before blaming the tech
- 1.Put a clock-in terminal or tablet within arm's reach of every bay
- 2.Make the repair order itself the trigger, no separate login step if possible
- 3.Review unclocked time weekly and ask about it the same day you see it, not a month later
- 4.Tie flat rate pay accuracy directly to clock-in data so techs feel the cost of skipping it
Where owners get this wrong
- Writing a strict policy before checking whether your own system creates the friction.
- Letting unclocked time slide for months before saying anything.
- Assuming it's always dishonesty when it's usually just an annoying extra step.
Ask your version of this question
This is one business owner-tested take. Your shop size, trade, and team change the answer. Ask the exact version inside Ask a Shop Owner and get a response grounded in how owners like you actually handled it.
Now run it against your numbers.
This answer is written for shops in general. Inside Ask a Shop Owner it becomes your answer: your revenue, your crew, your market, your history. Ask "What do I do about techs who won't clock into jobs properly" and get the version that accounts for what you already told us.
Was this helpful?
One click. It tells us which answers to deepen and which questions we still owe you.
Not ready for a trial? Take the scripts with you.
Leave your email and we send three short notes over the next week showing how owners used answers like this one on a real decision. No newsletter, no drip forever.
Three emails, then it stops. Unsubscribe in one click. We never sell your email address.
Answered for these owners
Built for shops like yours