In Part 4, we pulled production hours out of the clock-in to clock-out total. That gets you the right kind of hour. It doesn't tell you how many people it took to produce them.
Crew size is the variable most benchmarks quietly inherit. If last year's routes ran four people where three would do, last year's hours already carry that extra person.
Build a target on that history and the incentive pays crews for matching an old staffing habit. That's not performance. It's margin you gave away, coming back as a bonus.
Crew size changes nothing about base pay. Every person on a crew is paid the full base hourly wage for every hour worked, and the performance incentive sits on top of that wage. This post is about which history the benchmark is built on, and who decides how many people go out on a truck.
Why crew size hides in the numbers
Most job reports show hours per job, not people per job. A 32-hour day reads the same whether it was four people for eight hours or three people for ten and a half.
Revenue doesn't flag it either. The job bills the same. Margin slips a little on every visit, and nobody sees it until the season is over.
"An extra person can buy you an hour of daylight. Over a season, it can also cost you the margin on the route."
Two ways a staffing mismatch breaks an incentive
Overstaffed history inflates the target
If the benchmark comes from routes that ran heavy, the target has slack built in. Crews beat it just by running normal staffing.
The program then pays out on savings that were never real. It's the same overpay trap from Part 3 — coming in through headcount instead of the estimate.
Fixed crew sizes punish the crew for an office decision
Now flip it. The benchmark is built right, but dispatch still sends four people where three would do. The crew misses the target for a call they didn't make.
Like travel time in Part 4, the number is measuring a decision, not performance. Crews notice fast, and trust in the program goes with it.
What we look at before setting a target
This is the part of the readiness work where we read crew size out of your time data. Four questions shape how the benchmark gets built.
How many people actually work each job type?
We pull crew size per visit from clock events, not from the org chart. Planned and real crews often differ — a fourth person added "for the busy season" who never came off.
What does output per person-hour look like by crew size?
On the same job type, we compare production per person-hour across crew sizes. There's usually a sweet spot. Below it, quality and safety slip. Above it, people wait on each other.
Who decides crew size today?
If the crew lead controls who rides along, staffing can live inside the incentive — a right-sized crew that hits quality earns more. If dispatch decides, the benchmark has to account for crew size, or staffing becomes its own office metric.
Is the budget priced in person-hours or crew-days?
An estimate for "one crew, one day" and a report in person-hours will never agree. As with travel in Part 4, the benchmark has to use the same unit it's judged against.
Understaffing is the other failure. A crew running short to chase a bonus cuts corners, and callbacks follow. That's why quality standards and safety disqualifiers sit right next to the schedule benchmark — a short-handed shortcut shouldn't pay.
What this looks like in a real operation
A composite from our readiness work: a commercial maintenance company planned to launch performance pay on its routes. On paper, every route looked healthy. Revenue targets were met and margins held.
When we pulled crew size per visit, most routes had drifted from three people to four over two seasons. Each time, the reason made sense: a new account, a sick day, a trainee. None of the extra seats came back off.
Built on that history, the benchmark would have paid crews for returning to three-person staffing. That's money for savings the company had quietly given away and was now buying back.
So staffing was reset by job type first, and the benchmark was built on the reset history. Crew leads got a say in who rides, with the same quality and safety standards no matter the headcount.
Where Protiv fits
This analysis is part of the readiness work our team runs with you before launch, using the time and job data you already sync. Today it's a team-led process with growing platform support, and more of it moves into the product on a regular basis.
Once you're live, the bonus pool on each job splits the way your company sets it, and the crew's share can be distributed by equal rate, equal weight, or crew-lead weighting. A right-sized crew shares what it earned.
Where this leads next
Five questions in, you have an honest baseline, budgets you trust, the right hours, and the right crew sizes. One question is left: what would the program have actually paid?
That's Part 6 — the ledger test. Last year's jobs, run through this year's rules, before a single dollar goes out.
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 right-sizing a crew mean someone loses hours?
Not necessarily. Right-sizing is a scheduling decision, and it often means moving a person to work that needs them rather than cutting hours. Whatever the schedule, every hour anyone works is paid at the full base wage.
Won't crews run short-handed to earn more?
Some will try, which is why the schedule benchmark never stands alone. Quality standards, safety disqualifiers, and callback holdbacks make sure a rushed, short-handed job doesn't pay out.
How should trainees be handled?
Trainees add hours without adding full production. Many operations leave trainee hours out of the benchmark for a set period, or budget them separately, so a crew isn't penalized for teaching.
How does this connect to Part 4?
Part 4 decides which hours count toward the benchmark. This step asks how many people produced them. Both have to be right, or the target ends up measuring routing or staffing instead of the crew.
Want to see what your crew sizes are costing you?
A 30-minute conversation with our team walks through staffing by job type in your own data — before any incentive goes live.