How Should a Service Manager Handle Improving Hours-Per-RO in the Service Drive

Improving hours-per-RO starts with three moves: standardize your MPI process so every technician inspects the same way, implement a pre-labor approval workflow so advisors aren't writing $800 jobs at the desk, and track actual vs. estimated hours in real-time so you catch variance before it tanks your labor gross. Most dealerships see 0.3–0.5 hour gains per RO within 60 days by tightening these three levers.

Why Hours-Per-RO Matters to Your Bottom Line

Hours-per-RO is the metric that separates a 45% labor gross from a 52% labor gross. It's not glamorous, but it's where your fixed ops profit lives.

Think about it mathematically. If your shop is turning 80 ROs per month at an average labor rate of $145/hour, and your current hours-per-RO is 1.8, you're generating roughly $20,880 in monthly labor revenue. Bump that to 2.1 hours-per-RO—still conservative, still realistic—and you're at $24,360. That's $40,000+ a year without hiring another technician or changing your customer mix.

But here's the trap: most service managers assume hours-per-RO is a technician problem. It's not. It's a workflow problem. Technicians are efficient when they know exactly what they're diagnosing, when parts are staged, when the estimate is already approved by the customer, and when they're not stopping mid-job to hunt for a part number or wait for an advisor to call the customer.

The stores that nail this tend to have one thing in common: they've built a system where the customer's approval, the technician's workflow, and parts availability are all synchronized before the tech touches the vehicle.

Standardize Your MPI Process Across All Technicians

An MPI (multi-point inspection) is supposed to be a conversation between the technician and the service advisor about what the vehicle needs. Instead, most dealerships end up with seven different versions of the same MPI, depending on which tech you get.

Here's what standardization looks like:

Create a written checklist by vehicle class. SUVs, sedans, trucks, and luxury brands have different inspection priorities. A technician inspecting a 2019 Subaru Outback should follow the same 23-point checklist every time, not wing it based on mood or memory.
Assign a "lead tech" to train the rest. Pick your most consistent technician,not necessarily the fastest, but the one who follows the playbook,and have them own the MPI standard. They audit other techs' MPIs once a week and coach gaps.
Use photos or video cues. Instead of relying on written descriptions ("brakes look worn"), have your lead tech photograph typical wear states (25% pad remaining, 50%, 75%, "replace now") and post them in the shop. When a tech takes a photo of actual brakes and compares it to the standard, you eliminate guesswork.
Build the MPI into your DMS workflow. If your DMS has an MPI module, use it. If it doesn't (or if you're still using paper), create a simple form that asks the same questions in the same order every time. The format matters less than the consistency.
Track MPI attach rate by technician. This is your leading indicator for hours-per-RO. If Technician A's MPIs attach 3.2 hours on average and Technician B's attach 1.8 hours, B is either skipping items or not finding legitimate work. Either way, you have a coaching conversation to have.

A typical scenario: a customer drops off a 2017 Honda Pilot with 105,000 miles for an oil change. Your standard MPI flags transmission fluid, coolant, cabin air filter, and brake inspection. Tech finds that brakes are at 25% pad, coolant is discolored, and the air filter is clogged. That's a realistic $800–$1,200 attach to a $65 oil change. But only if every tech checks the same things. If your checklist is optional, some techs sell the work and some don't,and your hours-per-RO becomes a guessing game.

Implement Pre-Labor Approval to Stop Desk Delays

Here's where most dealerships leak hours-per-RO: the advisor writes the estimate, calls the customer, the customer asks questions, the advisor doesn't have answers, the advisor has to find the technician, the technician explains it, the customer still hesitates, the advisor promises a call-back, and the job sits in queue for 2–3 hours.

Pre-labor approval means the customer signs off on the work before the technician starts the job. Not after. Not pending approval. Before.

Here's the workflow:

Advisor writes the estimate with the technician present (or immediately after). The technician is there to explain what the work is and why it's needed. No surprises, no phone tag.
Advisor calls the customer with the tech standing by. If the customer has a question, the tech can answer it directly. "Why do you recommend a transmission flush?" "Because the fluid is dark and we're seeing higher shift temps than normal." Done. No call-back needed.
Customer approves or declines right then. Advisor notes approval in the RO. Job is either green-lit or removed from the queue. No limbo.
If approved, parts are ordered immediately and the job is scheduled into the tech's day. The tech knows the job is confirmed, parts are staged, and they can block out the time accurately.

This is the kind of workflow Dealer1 Solutions was built to handle,estimate line approval, parts staging, and tech scheduling all linked so there's no ambiguity about what's approved and what's waiting. But even with paper estimates, the principle holds: get approval before the work starts.

When you remove the 2-3 hour approval window from every RO, your hours-per-RO tightens immediately because you're measuring actual shop time, not desk time.

Stage Parts Before the Technician Starts the Job

A technician who stops mid-job to find a part number, check availability, or wait for parts to be picked loses focus and momentum. You can't measure that loss cleanly on a single RO, but it compounds across 20–30 jobs a month.

Parts staging is simple in theory: before the tech starts work, the parts coordinator pulls or orders every part the estimate calls for and has it waiting at the technician's station or in a bin with the RO number.

In practice, this requires:

Real-time parts availability checking. When the advisor writes the estimate, they (or the parts team) should check on-hand and in-transit inventory immediately. If a part is on backorder, the customer needs to know before approval, not after the job is halfway done.
A handoff protocol between advisors and parts. Once an estimate is approved, the advisor flags it as "ready for parts staging." Parts team pulls the job and stages everything at the tech's workstation with a printed RO.
A "parts ready" checkpoint before the job moves to the tech queue. Parts coordinator confirms all items are staged and ready. If something is missing, the advisor is notified and has a conversation with the customer about delay or substitution before the tech is assigned the work.
For longer lead times (3–5 days), schedule the job out. If a transmission cooler is on backorder for 4 days, don't assign the job to a tech today. Schedule it for Thursday when parts arrive. This keeps your daily queue realistic and prevents technicians from working around missing parts.

This is where a lot of shops lose 0.2–0.4 hours per RO. Technician is standing at the parts counter waiting for a filter or gasket that should have been staged 20 minutes earlier.

Track Actual vs. Estimated Hours Every Single Day

You can't improve what you don't measure. Most service managers look at hours-per-RO once a month in a report. By then, the variance is baked in and it's too late to coach.

Instead, build a daily review habit:

Pull a report of yesterday's closed ROs. Look at estimated hours vs. actual hours for each job. Flag outliers,jobs that ran 30+ minutes over estimate or under estimate.
For overages, ask three questions: Was the estimate wrong (scope creep, hidden damage)? Was the technician inefficient (wrong tool, rework, distraction)? Or was the job legitimately harder than expected (seized bolt, hidden rust)? Each answer gets a different response.
For underages, ask whether the tech is rushing (cutting corners, skipping steps) or whether the job was simpler than anticipated (good sign,you can use this data to refine future estimates).
Have a 5-minute stand-up with your lead technician or shop foreman. "Yesterday we had a $1,400 transmission flush on a 2015 Camry estimated at 2.0 hours, came in at 2.8. Was that normal for that job or did something go sideways?" Over time, you'll build a library of "typical" times that's specific to your shop and your techs.
Adjust your estimate guide quarterly. If your estimates for brake jobs are consistently running 15 minutes long, update your guide. Your estimates should reflect reality, not optimism.

Stores that run this daily standup see variance tighten within 30 days. You spot patterns (one tech is consistently slower on diagnostics, certain jobs always run long, parts delays are eating a specific job type) and you address them immediately instead of waiting for the month-end surprise.

Create Accountability Through Technician Metrics and Coaching

Hours-per-RO lives at the intersection of shop systems and individual technician performance. You need both.

Here's a practical approach:

Post daily hours-per-RO by technician on the shop board or in your team chat. Transparency drives accountability. Technicians know the metric matters when it's visible every day, not buried in a monthly report.
Set a target that's achievable but ambitious. If you're currently at 1.8 hours-per-RO, don't jump to 2.5 overnight. Target 1.95–2.0 in 30 days, then 2.1–2.2 in 60 days. Small gains are sustainable; big jumps invite cutting corners.
Recognize the techs who hit the target. (Yeah, I know, but sometimes the obvious stuff gets skipped.) A $25 gift card or a shout-out in the team chat costs nothing and reinforces the behavior you want to see.
Coach the outliers without blame. If a tech's hours-per-RO is 1.4 while the team average is 1.9, sit down with them. "I'm seeing your jobs come in faster than estimate. Walk me through your process,are you skipping steps, or are you just efficient?" Listen to the answer. They might have a shortcut you can teach everyone else, or they might be rushed and need support.
Pair newer techs with the lead tech for diagnostics. A tech who's fast but inaccurate will wreck your hours-per-RO (and your CSI). A tech who's slow but thorough can improve by watching how the lead tech diagnoses without cutting quality.

The goal isn't to squeeze techs. It's to build a culture where everyone understands that accurate estimates, clear communication, and efficient workflow make their jobs easier and the shop more profitable.

Audit Your Estimate Guide and Labor Times

Sometimes your hours-per-RO problem isn't a workflow problem or a technician problem. It's an estimate problem.

If you're estimating a typical brake job at 1.2 hours and your techs are consistently taking 1.6 hours, your estimate guide is wrong. It doesn't matter how efficient your workflow is,you're starting with an impossible number.

Here's how to audit:

Pull the last 20 closed ROs for a specific job type. Let's say front-brake-pad replacement on 2010–2018 sedans. Look at the estimated hours and the actual hours.
Calculate the average actual time. If 20 jobs averaged 1.55 hours actual, that's your reality.
Compare to your current estimate. If you're estimating 1.2, you have a gap of 0.35 hours per job.
Decide: do you want to update the estimate to 1.5 hours, or do you want to find out why techs are taking 0.35 hours longer than they should? Usually the answer is "both." Update the estimate and coach the process.
Repeat this for your top 10–15 labor operations (oil changes, tire rotations, brake jobs, transmission flushes, air-filter replacements, coolant flushes, etc.). These drive most of your ROs and most of your hours-per-RO variance.

This is the kind of detail work that doesn't feel urgent but moves the needle on hours-per-RO more reliably than anything else. Accurate estimates mean accurate hours-per-RO, which means your team knows what success looks like.

Frequently asked questions

What's a realistic hours-per-RO target for a typical dealership service department?

Most dealerships run 1.7–2.1 hours-per-RO depending on their customer mix, vehicle age, and service menu. Luxury and high-mileage vehicles trend higher (2.0–2.4); newer vehicles and quick-serve shops trend lower (1.5–1.8). A good benchmark is: measure your own department for 30 days, then set your target 5–8% above that baseline. Pushing for unrealistic gains usually means cutting quality or corners, which kills CSI and repeat business.

How do you handle hours-per-RO when a job has unexpected hidden damage?

When a technician finds hidden damage (seized bolts, hidden rust, broken studs), it's legitimate and shouldn't count against their efficiency. The key is flagging it in real-time so the advisor can call the customer and get approval for the extra time before the tech continues. This is where your pre-approval workflow shines,the tech stops, the advisor gets a "surprise" estimate, the customer approves, and the job continues. Document these in your daily variance review so you build a library of "normal surprises" for each job type. Over time, you'll get better at estimating for them upfront.

Should hours-per-RO targets be the same for all technicians?

No. A technician who specializes in diagnostics should have different expectations than someone focused on maintenance and basic repairs. A tech who handles mostly warranty and recall work (which is often slower because of documentation requirements) shouldn't be held to the same standard as a tech doing routine service. Set individual targets based on their actual work mix and skill level, then hold everyone to consistent quality and accuracy. The goal is improvement, not uniformity.

How does parts availability affect hours-per-RO, and how do you control for it?

Parts delays are invisible killers of hours-per-RO. A technician can't start work if parts aren't staged, and you can't hold them accountable for delays that aren't their fault. The control is simple: if a part is on backorder when the estimate is written, don't approve the job until parts are confirmed in stock or in-transit with an ETA. Schedule the work for the day parts arrive. For common items (filters, pads, fluid), maintain adequate stock so delays are rare. For specialty parts (transmission coolers, water pumps), check availability before you write the estimate and be transparent with the customer about lead time.

Can you improve hours-per-RO without a sophisticated DMS or workflow software?

Yes. The fundamentals,standardized MPI, pre-approval, parts staging, daily tracking,work with paper estimates and a whiteboard. What a good workflow system does is remove manual work and make the data automatic. But if you don't have that tool yet, you can still build discipline around these steps. The software accelerates the improvement, but the discipline is what sticks. Once you prove the concept with manual processes, investing in a platform that automates those workflows becomes an easy decision.

How long does it typically take to see improvement in hours-per-RO after making these changes?

Small improvements (0.1–0.2 hours-per-RO) show up within 2–3 weeks if you're consistent with daily tracking and pre-approval. Larger gains (0.3–0.5 hours-per-RO) take 45–90 days because they require estimate-guide updates, technician coaching, and habit formation. The dealerships that see the fastest gains are the ones that tackle all three levers at once (standardized MPI, pre-approval, parts staging, tracking) rather than trying one thing and waiting for results. Patience matters, but momentum matters more.

One More Thing: Pick Your Starting Move

If you're reading this and thinking "I need to fix all six of these things tomorrow," stop. You'll burn out and nothing will stick.

Pick one: standardize your MPI, implement pre-approval, or set up daily tracking. Pick the one that feels most broken in your shop right now. Spend 30 days making it routine, then layer in the next one. The three-move formula at the top of this post is real, but the path to it is sequential, not simultaneous.

By the time you've built those three habits,standard MPI, pre-approval, daily tracking,your hours-per-RO will already be up 0.3–0.4. The estimate-guide audit and parts staging will be obvious next steps because you'll have the data and the discipline to execute them cleanly.

Start Monday. Pick one move. Make it routine. Then move on.