Gross per hour and gross per RO measure different things — and when they move in opposite directions for the same advisor, the combination is one of the most diagnostic signals a service manager can see. This post explains what it means and what to do about it.
Two Metrics, Two Different Questions
Gross per RO asks: how much did this advisor produce on each repair order? It reflects the depth of the ticket — the services presented, the value built before quoting price, the willingness to recommend what the vehicle actually needs.
Gross per hour asks: how much did this advisor produce per hour of shop capacity committed? It reflects how efficiently billed time is converting to gross profit, accounting for both labor and parts on each job.
Most service managers track G/RO because it's the most visible number in the DMS. But G/RO alone has a blind spot — it doesn't account for what type of work is being written. An oil change and a brake job can both land at the same G/RO if the oil change includes enough attached services, but the time commitment to each is entirely different.
That's where G/Hr fills the gap. And when the two metrics diverge for the same advisor, it's worth stopping and asking why before jumping to a coaching conversation.
What High G/Hr + Low G/RO Actually Means
There are three distinct scenarios where this pattern shows up — and they require three completely different responses.
The Efficient, High-Quality Advisor
This advisor is doing their job well. They're writing clean, efficient tickets — shorter jobs, but high-quality inspection and strong parts attachment on every one. Their G/RO looks modest because the work mix is weighted toward maintenance, not because they're underperforming. Action: none. Recognize the consistency and look at ticket mix before initiating a coaching conversation.
The Maintenance-Heavy Advisor
This advisor is making the most of every job they get — the problem is the jobs they're getting. They're over-indexed on oil changes, tire rotations, and scheduled maintenance. Fast jobs with limited repair opportunity. Their G/Hr is high because they present well on everything they write. Their G/RO is low because those tickets have a ceiling. Action: lineup adjustment, not coaching. Route more repair work and returning customers to this advisor.
The Advisor Who Needs More Depth
This advisor produces well on what they present — but they're not finding enough to present. Low HPRO alongside low G/RO and high G/Hr means the inspection isn't complete. They're closing what they recommend effectively, they're just not recommending everything the vehicle needs. Action: Inspection Depth coaching. Slow down per RO, complete the walkaround, present the full vehicle picture.
The HPRO Tells You Which Scenario You're In
When G/Hr is high and G/RO is low, look at HPRO next. That single number tells you whether you're looking at a routing issue or a coaching issue.
Why G/RO Alone Misleads You
A service manager looking only at G/RO can make two costly mistakes. They can initiate a coaching conversation with an advisor who doesn't need one — the efficient advisor who is simply writing maintenance-heavy work and doing it exceptionally well. And they can miss the depth problem on an advisor whose G/Hr masks the fact that they're leaving findings unmentioned on every ticket.
Neither mistake shows up when G/RO is the only lens. Both are immediately visible when G/Hr is in the picture alongside it.
Before any coaching conversation about G/RO, check G/Hr and HPRO together. If G/Hr is high and HPRO is normal, the advisor doesn't need coaching — they need different work. If G/Hr is high and HPRO is low, the coaching conversation is specific: finish the inspection, the closing skill is already there.
What This Means for How You Route Work
Scenario 2 — the maintenance-heavy advisor — is a management problem, not a performance problem. The fix is how new ROs get distributed on the drive, not how the advisor presents services.
Most service lanes assign customers to advisors in rotation — the next car in gets the next advisor in the queue. That system doesn't account for what type of work is coming in. A returning customer with $2,000 in deferred services from last visit is a different opportunity than a walk-in for a scheduled oil change, even if they arrive at the same time.
Pairing returning customers with the same advisor who wrote them last time, and routing higher-opportunity repair work to advisors who demonstrate the skills to close it, directly impacts G/RO without any change in advisor behavior. It's a lineup decision — and it's one of the highest-leverage moves a service manager can make.
The Bottom Line
G/Hr and G/RO are not the same metric. They're not even asking the same question. When they diverge for the same advisor, that combination is one of the most specific diagnostic signals you have — it narrows the field from "this advisor needs coaching" to a precise answer about what kind of coaching, if any, is actually needed.
That precision is the difference between a coaching conversation that changes behavior and one that wastes everyone's time.
See G/Hr and G/RO side by side for every advisor on your team
AdvisorLab surfaces both metrics on the SM heatmap — alongside HPRO, discount rate, and 6 coaching pillar scores — so you know exactly which conversation to have before you have it.
Book a Demo →