Measure Detailing Revenue per Labor Hour Without Misleading Yourself

What the Metric Actually Measures

Revenue per labor hour is simply job revenue divided by total worker-hours consumed. If a full detail bills at $250 and two technicians each spend two hours on it, the job consumed four worker-hours, not two. Dividing $250 by four gives $62.50 per labor hour. Dividing by two gives $125, which sounds better but is wrong and will mislead every decision you make with it.

The number measures how efficiently you convert worker time into billed dollars. It does not measure profit. A ceramic coating job with a $150 product cost and a $400 invoice may post lower revenue per labor hour than a quick wash, yet leave you more money after materials. Keep that distinction in mind before using the metric to cut services.

Elapsed Time Versus Worker-Hours: A Critical Distinction

Elapsed time is how long a job occupies your calendar from start to finish. Worker-hours are the sum of each person's active time on that job. For a solo operator these are often the same. The moment a second person touches the car they diverge. A two-hour detail with two technicians working in parallel is two elapsed hours but four worker-hours.

Using elapsed time on team jobs understates your labor input and inflates the metric. Using worker-hours keeps the denominator honest across solo and team jobs so you can compare them fairly. Whichever definition you choose, apply it consistently across every job in a reporting period or the averages are meaningless.

Why Your Timer Data Needs a Missing-Timer Rule

A process timer is useful only when technicians actually start and stop it on every job. In practice, timers get forgotten on busy days, skipped on familiar repeat jobs or stopped after cleanup but before the final walk-around. Any job without a recorded time creates a gap in your data.

You need a written rule before you calculate averages. The simplest options are: exclude any job with no timer record from the calculation and note how many were excluded; use a standard estimated duration for that service type as a fallback, labeled clearly as estimated; or record both actual and estimated and run separate averages to see whether the gap matters. Whichever you pick, document it so the same rule applies next month. A metric built on inconsistent inclusions will drift without explanation.

Match Your Job Population Before You Average

Averaging revenue per labor hour across all service types in the same period can hide more than it reveals. A full paint correction and a basic wash have fundamentally different price structures and labor inputs. If you ran more washes this month than last, your average will drop even if your pricing and efficiency are identical.

Before drawing conclusions, filter to a matched population: same service tier, same period length, same team size. Compare interior details against interior details from last quarter, not against ceramic coatings from this quarter. If you only have one service type, the comparison is straightforward. If you have several, track each separately and look at the mix shift as its own question.

Worksheet: Revenue per Labor Hour by Service Type

Use this worksheet at the end of any period you choose, weekly or monthly. Fill it in from your job records and timer logs. The final column tells you which services are carrying their weight and which need a price or time review.

The tradeoffs show up in that last column. A service with high revenue per labor hour but few jobs may not be worth optimizing. A service with low revenue per labor hour but high volume is your biggest lever. Fix the volume problem first.

REVENUE PER LABOR HOUR WORKSHEET
Period: _______________
Timer rule applied (circle one): ACTUAL ONLY / ESTIMATED FALLBACK / EXCLUDED

For each service type:
1. List all completed jobs in the period.
2. Record invoice total (before tips, after any discounts).
3. Record total worker-hours per job (sum all technicians' active time).
4. Sum invoice totals for the service type.
5. Sum worker-hours for the service type.
6. Divide total revenue by total worker-hours.
7. Note how many jobs had no timer record and whether they were included.

Service Type	Jobs Completed	Jobs w/ Timer	Jobs Excluded or Estimated	Total Revenue ($)	Total Worker-Hours	Revenue per Worker-Hour ($)
Basic Wash
Interior Detail
Full Detail
Paint Correction
Ceramic Coating
TOTALS

Hypothetical Worked Scenario

This example is entirely hypothetical. Imagine a two-person mobile operation tracking one month of full details only. They complete eight jobs. Six have timer records. Two do not because the timer app was not opened on back-to-back days. Their rule is to exclude timer-missing jobs from the calculation and note the gap.

The six recorded jobs show invoice totals of $280, $310, $265, $295, $280 and $320, for a total of $1,750. Worker-hours across those six jobs are 4.0, 5.0, 3.5, 4.5, 4.0 and 5.5, totaling 26.5 worker-hours. Revenue per labor hour equals $1,750 divided by 26.5, which is approximately $66 per worker-hour. The two excluded jobs had invoice totals of $290 and $275. The owner notes that excluding them represents roughly 24 percent of jobs and flags the timer discipline issue before relying on the $66 figure for any pricing decision. If the excluded jobs had similar ratios, the number likely holds. If those were unusually fast or slow jobs, the average could shift meaningfully, which is exactly why the exclusion note matters.

Tradeoffs and Failure Cases to Expect

The most common failure is comparing periods with different team compositions. If you worked solo in March and with a helper in April, your revenue per labor hour will drop in April even if you booked more total revenue. That is not a sign of inefficiency; it is a math artifact of adding worker-hours to the denominator. Segment solo jobs and team jobs separately before comparing trend lines.

A second failure is using the metric as the only reason to cut a service. High revenue per labor hour sounds good but does not account for materials, travel time or setup. A job that looks efficient on this metric might eat your margin on product costs. Use revenue per labor hour alongside, not instead of, a per-job margin review. A third failure is chasing a higher number by selecting only fast, high-ticket jobs and letting lower-ticket volume work dry up. That narrows your client base and makes scheduling fragile.

Tracking and Acting on the Number

Record the metric consistently at the same interval, monthly works for most solo and small-team operators, and look for directional changes rather than a single month's reading. A three-month average smooths out slow weeks and gives you a more reliable baseline. When the number drops, ask whether the service mix shifted, whether timer discipline slipped, or whether a new service type with different labor demands entered the mix before assuming your pricing is wrong.

If your CRM tracks appointment records and you use a process timer, keeping job revenue and worker-hours in connected records makes this calculation straightforward at the end of any period. Weavr's optional process timer and appointment-linked records can support this kind of per-job data collection without requiring a separate spreadsheet system, though you still need to decide and document your missing-timer rule. The action to take today is simple: pick one service type, pull the last four weeks of completed jobs, apply a consistent timer rule and calculate the number. One real calculation beats a year of planning to calculate.

The practical takeaway

Sum worker-hours across every technician, not elapsed time. Apply a written rule for timer-missing jobs before you average. Compare matched service populations across matched periods, then use the number alongside margin data, not instead of it.

Explore the relevant WeavrCRM workflow · Review integrations and requirements