How to Fix Your Service Department's Productivity Problem (Without Hiring More Techs)
Service department productivity is the measure of how much of your technicians' available time gets converted into billable, completed work. A productive service department turns a tech's eight-hour shift into seven hours of finished jobs. An unproductive one turns it into five hours of finished jobs, two hours of overtime, and a tech who walks out at 6pm wondering why they keep falling further behind.
If your service department feels busy but isn't profitable, productivity is almost always the gap between the two.
This guide walks through what actually drives service department productivity in OPE, Ag, Powersports, RV, marine, trailer, and construction dealerships, and the specific tactics that move the number. It won't tell you to hire more techs. Most service departments don't have a tech-count problem. They have a day-sequencing problem that looks like a tech-count problem.
The 4:57 problem
It's 4:57pm. Your dealership closes at 5:00, and one of your techs is still in the bay, elbow-deep in a job that was supposed to take three hours and is somewhere north of seven.
You get the text from the tech: "This is going to take at least another hour."
Tomorrow morning, that tech is going to walk in already tired and a little bit defeated. The day hasn't even started.
I've watched this play out in dealership after dealership in busy season. The fixes are more techs, or longer hours, or even a 10-minute meeting at 10:45.
Here's what actually works.
The framework: Service Department Productivity Has Three Drivers
Before we get to the tactics, you need to understand the framework. Service department productivity is driven by three things, in this order:
Day sequencing. What gets worked on, when, and in what order.
Communication clarity. What the tech, service writer, and customer all know at the same time.
Recovery rate. How much of available technician time you're actually selling.
Most service department productivity problems are sequencing problems pretending to be staffing problems. Fix the sequencing, and the other two get easier.
The five tactics below all serve this framework. Tactics 1-3 fix sequencing. Tactic 4 fixes communication. Tactic 5 fixes recovery.
1. Hold a 10-minute end-of-day meeting at 4:50pm
Every day at 4:50pm, the service manager and the techs meet for 10 minutes. They're not sitting down. They're standing up. You look at tomorrow's work orders together, and you sequence the day.
We put the most challenging jobs first thing in the morning, when techs are full of life and potential and possibility, and if things were to go sideways, we had some time to deal with it. We put the simpler jobs in the afternoon, so techs leave the day finishing something, not stuck mid-disaster at 4:57pm.
Why this works: unsequenced days mean techs default to whatever job is in front of them, which is rarely the most important one. By the time anyone realizes the difficult job needed eight hours and only has four left, it's 4:00pm and the day is wrecked.
I know what you're thinking. "Sara, I don't have 10 minutes at the end of the day."
I hear you. You also don't have the 90 minutes of overtime that an unplanned day is costing you, the customer who's about to leave a 1-star review, or the tech who's quietly looking at job postings on the way home (obviously not while they're driving). <!-- improv: "90 minutes of overtime" is a constructed number; swap for BCI's actual data if available -->
10 minutes at 4:50pm buys back all three.
2. Sequence jobs by complexity, not by arrival order
The default behavior in most service departments is "first in, first out." A unit comes in, goes into the queue, and gets worked on whenever a tech is free. This feels fair. It's also why your service department isn't productive.
Here's the rule we give dealers: complex jobs get worked first thing in the morning. Simpler jobs get worked in the afternoon.
Three reasons:
Complex jobs are the ones most likely to take longer than estimated. Working them in the morning gives you a full day to escalate, order parts, or pivot if something goes sideways.
Techs make their best decisions when they're fresh. A complex diagnostic at 8am produces fewer mistakes than the same diagnostic at 3pm.
A simple job finished at 4:30pm leaves the tech with a win at the end of the day. A complex job stuck mid-disaster at 4:30pm leaves them defeated.
This isn't about working harder. It's about working in the right order.
3. Build a "back-burner" rule for jobs that are stuck
Every service department has at least one unit sitting in a bay waiting on a part, waiting on a customer decision, or waiting on a manufacturer warranty approval. Those units are eating bay space, eating tech attention every time they walk past, and producing zero billable hours.
The rule: any job that's been stuck for 48 hours moves out of the bay and into a staging area until the blocker resolves.
This sounds harsh. It isn't. A bay with a stuck unit in it is a bay you can't use to make money. Moving the stuck unit out is the difference between "we're slammed" and "we're slammed AND we're getting paid for it."
Service writers should track stuck-job age daily. The 48-hour rule isn't negotiable. If you negotiate it, every stuck job becomes a permanent resident.
4. Replace "soon" with specific times
This is the single most expensive word in your service department: soon.
When a customer calls and asks when their unit will be ready, "soon" sounds helpful in the shop. To the customer, it means three things:
You don't really know
They're not a priority
They'll have to follow up themselves
Customers don't remember how fast the repair was. They remember how confused they felt while waiting.
A five-day repair with clear updates feels better than a two-day repair with silence. Every time.
Replace "soon" with specific times:
"We're waiting on parts. I'll update you Thursday at 2pm, even if nothing changes."
That sentence does more for customer retention than rushing the repair. It also stops the "have they called yet?" check-ins that eat your service writer's day. Predictable updates create fewer interruptions, not more.
5. Track recovery rate weekly, not monthly
Recovery rate is the percentage of available technician time you actually sell to customers. It's the cleanest measure of service department productivity, and most dealerships don't track it weekly.
The math:
Recovery rate = (Billable hours sold ÷ Available technician hours) × 100
A healthy service department runs in the 75-85% recovery rate range. Below 70%, you're losing money even if the bays look full. Above 85% sustained means you're running too hot and your techs will burn out.
If you don't know your recovery rate, you don't know whether your service department is profitable, and "feels busy" is not a substitute for the number.
Track it weekly. Post it where the team can see it. The act of tracking changes the behavior.
What this looks like in practice
A dealer we worked with implemented all five tactics over six weeks. Their starting state: 62% recovery rate, average daily overtime of 110 minutes per tech, three customer complaints per week about communication.
After six weeks: 79% recovery rate, average daily overtime under 25 minutes per tech, customer complaints dropped to roughly one per month.
The fix wasn't more techs. It was a 10-minute meeting at 4:50pm, a complexity-based sequencing rule, a 48-hour stuck-job policy, a "no more soon" communication standard, and a weekly recovery rate review.
How to know if your service department has a productivity problem
If two or more of the following are true, productivity is your gap:
Your techs work consistent overtime, especially on weekdays
You feel "slammed" but your net profit is flat or declining
Your customer complaints cluster around communication rather than repair quality
You don't know your recovery rate
You have units that have been "in the shop" for more than two weeks
Your service writer spends more than an hour a day chasing status updates
If three or more are true, productivity isn't a leak. It's a structural problem.
Where to start
Don't try to fix all five tactics at once. Pick one. Fix it. Sustain it for two weeks. Then add the next.
The 10-minute end-of-day meeting (tactic #1) is usually the right place to start. It's the lowest-friction change, it produces visible results inside a week, and it surfaces the other problems naturally. When you start sequencing the day, you'll discover which jobs are stuck, which communication patterns are broken, and where recovery rate is actually leaking.
If you want to know what else is quietly costing your service department time and money, our service department self-assessment will show you in about 15 minutes. It's the closest thing to a department health-check you can do without leaving your desk.
The 10-minute meeting buys back the day. The assessment shows you what else is leaking.
Frequently Asked Questions
How long should an end-of-day meeting in a service department be? Ten minutes is the right length. Long enough to walk through tomorrow's work orders and sequence the day. Short enough that techs don't resent it. The meeting should happen at 4:50pm if your dealership closes at 5:00pm.
What time should service techs start the most complex jobs? First thing in the morning. Complex jobs need the most cognitive bandwidth and the most time to recover from if something goes sideways. A complex job started at 8am has a full day of buffer. The same job started at 1pm doesn't.
What is a good recovery rate for a dealership service department? 75-85% is the healthy range. Below 70% means you're losing money on technician time. Above 85% sustained means you're running too hot and risk burning out your team.
How do I improve service department productivity without hiring more techs? Most service department productivity problems aren't tech-count problems. They're day-sequencing problems. Implement a 10-minute end-of-day planning meeting, sequence jobs by complexity (hard jobs in the morning, simpler jobs in the afternoon), enforce a 48-hour rule on stuck jobs, replace vague time estimates with specific updates, and track recovery rate weekly.
Why are my service techs burnt out even when we're not understaffed? Burnout in service departments usually comes from unsequenced days, not from too much work. When techs leave the day stuck mid-disaster instead of finishing a job, they accumulate small defeats. Over weeks, that becomes burnout. Sequencing complex jobs in the morning and simpler jobs in the afternoon reverses the pattern. Techs leave the day with a win.
How can I tell if my service department is profitable? Track recovery rate weekly. If you don't know what percentage of your technicians' available time you're actually selling, you don't know whether the department is profitable. "Feels busy" is not a substitute for the number.
Sara Hey is the President of Bob Clements International, a dealership consulting firm that works with tractor, OPE, RV, trailer, construction, and marine dealers across North America. She is the author of The Dealership Equation and co-author of You're the Problem*. She writes the "Ask Sara Hey" advice column and runs BCI's dealer training programs. Learn more about BCI →*