In Part 3, we separated two problems that look identical on a report: a budget that was wrong from the start, and a crew that fell behind on a budget that was right. Fixing that gets you an honest target. It doesn't yet get you an honest comparison — because the hours you hold up against that target usually aren't one kind of hour.
Most timesheets in the trades run clock-in to clock-out. Somewhere inside that span is the work the job was actually priced on. Also inside it: the drive to the first stop, the load-out at the yard, the forty minutes waiting on a supplier, the callback on last month's job that nobody budgeted for. All of it lands in one total. And when a performance benchmark gets set against that total, the program starts measuring things the crew doesn't control.
Nothing in this post changes how hours are paid. Drive time, yard time, and non-billable time are paid at the full base hourly wage, every hour, no exceptions. A performance incentive sits on top of that wage and is never a substitute for it. The question here is narrower: which hours should a crew's schedule benchmark be built on, so the incentive rewards the work the crew actually controls?
One total, four kinds of hours
When we work through an operation's labor data before a launch, the first thing we do is try to split the total into the categories below. Not every business can split all four on day one — and that's useful to know, too.
| Hour type | What it looks like | Who mostly controls it |
|---|---|---|
| Production | On-site time spent doing the scoped, priced work | The crew |
| Travel | Yard to first stop, between stops, and back | Routing, dispatch, and the customer map |
| Yard & load-out | Loading, fueling, equipment prep, end-of-day unload | Shared — process, equipment, and crew habits |
| Non-billable on-site | Callbacks, warranty work, waiting on materials or access | Mixed — and worth tracking separately |
The right-hand column is the one that matters for incentive design. A schedule benchmark is fair when the crew can move the number by doing better work. It stops being fair when the number moves because of where the jobs happen to sit on the map or how the day got dispatched.
Why the blended number breaks a performance target
Here's a composite example of what we see when two crews are compared on total hours. Same scope of work, same week, same job types. The only real difference is route geography.
That flip is the whole problem in one picture. If the incentive is tied to total hours, Crew B earns it for having a shorter drive, and Crew A misses it while doing slightly better work. Nobody on Crew A will believe the program is fair after that — and they'd be right.
"If your benchmark can't tell a slow crew from a long drive, it isn't measuring performance. It's measuring the map."
The blend causes a second, quieter problem: it points pressure at the wrong places. When travel and yard time count against the crew's number, the easiest hours to "save" are the ones that shouldn't be rushed — the pre-trip equipment check, the careful load-out, the drive itself. A well-built program aims pressure at production quality and pace, and leaves everything else to the people who actually control it.
What we look at before setting a target
This is the part of the readiness work where we sit with an operation's time and job data and answer four questions. Each one tells us something different about how the benchmark should be built.
Can the hours be separated at all?
Some operations already capture job-level clock events, so travel and on-site time fall out naturally. Others only have a daily total per employee. That's not disqualifying, but it changes what's measurable — the same question we raised in Part 2 about whether your baseline reflects reality. If the split isn't possible yet, the first move is usually fixing how time gets captured, not launching the incentive.
What share of total hours is production — by crew and by job type?
A company-wide production share hides the same way a blended labor percentage does. We look at it per crew, per route, and per job type. A wide spread between crews doing similar work is almost always a routing or dispatch story before it's a performance story.
Is the budget built on the same hours it's compared against?
This mismatch is more common than you'd expect. An estimate prices production hours, but the variance report compares it to total clocked hours — so every job looks over budget by roughly the travel share. Or the reverse: travel is baked into the budget for some job types and not others. Either way, the benchmark has to be built on the same slice of time it's judged against.
Who owns the non-production hours?
Travel and dispatch are usually office decisions. Callbacks may trace back to a specific crew, or to the estimate, or to the customer. Waiting on materials is a purchasing problem. Each of those can be tracked and improved — often with its own metric and its own owner — but folding them into a crew's schedule benchmark makes the crew pay for decisions they didn't make.
If the crew can't change it by working better, it doesn't belong in the crew's schedule benchmark. Track it, assign it to whoever does control it, and keep it out of the incentive math.
What this looks like in a real operation
A composite from the kind of engagement we run: a multi-branch maintenance company was preparing to launch performance pay and had already flagged one branch as the weak link. On total hours per route, that branch trailed the others every month. The working assumption was a crew problem.
When the hours were split, the picture changed. That branch's production pace was in line with the rest of the company. What was different was travel — a large new contract had stretched its routes well beyond the others, and its travel share was roughly double the company average. The crews weren't slow. The map had changed and the routes hadn't.
The fix had two parts, and neither touched a pay rate. Routes were rebuilt around the new contract, which recovered a meaningful share of the lost time. And the schedule benchmark for every branch was rebuilt on production hours, with travel tracked separately as a dispatch metric. When the program launched, the "weak" branch was competitive from the first month — and the crews there had no reason to doubt the scoreboard.
Where Protiv fits
This analysis is part of the readiness work our team runs with you before an incentive goes live, using the time and job data you already sync rather than a spreadsheet reconstruction of it. Today it's a team-led process with growing platform support — we're adding more of it to the product in automated form on a regular basis, so more of this becomes something you can pull up yourself rather than something we run for you. If your time data can't support the split yet, we'll tell you, and help you fix capture first.
Where this leads next
Once production hours are separated out, a new question comes into focus: how many people were on the job to produce them. A route can hit its production benchmark and still lose money if it's carrying an extra person every day. That's Part 5 — staffing ratios, and what they reveal about jobs that look profitable on paper.
Frequently asked questions
Is this a piece-rate pay model?
No. The base hourly wage is always paid in full for every hour worked, regardless of job outcome. The performance incentive is a bonus layered on top, earned only when a crew hits a quality standard and a schedule benchmark built from real job data. Nothing in this analysis changes or reduces base pay.
Does excluding travel from the benchmark mean travel time isn't paid?
No. Travel, yard, and non-billable hours are paid at the full base hourly wage like any other hour. Leaving them out of the schedule benchmark only means the incentive isn't won or lost because of a long drive or a dispatch decision the crew didn't make.
What if our timesheets don't separate travel from on-site time?
That's common, and it's worth knowing before launch rather than after. The usual first step is improving how time is captured at the job level. Launching an incentive on blended hours tends to reward route geography instead of performance, which erodes trust in the program quickly.
Should travel time ever be part of an incentive?
Only where the crew genuinely controls it. In most operations, routing and dispatch decide travel, so it's better tracked as its own metric owned by the office. If a crew does set its own route order, it can be worth discussing — but it should still be measured separately from production pace.
How does this connect to job budget variance?
Part 3 asks whether the budget is right. This step asks whether the hours you compare against it are the right hours. A budget priced on production time and compared against total clocked time will look wrong on every job, even when it isn't.
Want to see where your hours actually go?
A 30-minute conversation with our team walks through how we separate production time from everything else in your data — before any incentive goes live.