The goal is the engine of a performance pay program. Set it right and workers engage, push harder, and earn more. Set it wrong in either direction — too easy or too hard — and the program quietly fails. Workers either coast to the bonus without any behavior change, or conclude the goal is unreachable and mentally opt out.
Finding the right goal is less art than it is a four-step process. Here's how the contractors who get it right actually approach it.
The ideal performance goal is one where 60–70% of crews hit it on a normal, well-run day — meaning it requires genuine effort but isn't out of reach. Goals where 90%+ of crews hit them are too easy. Goals where fewer than 30% hit them are too hard, and will be abandoned within weeks.
The Goldilocks problem with performance goals
Most contractors set goals based on what they need — what margin they want the job to produce. This is understandable but backwards. A goal needs to be set based on what's achievable for a motivated, well-organized crew — and then the business model needs to work within that constraint.
If your budgets are built on assumptions that can only be hit by the top 10% of your crews on their best days, you don't have a goal-setting problem. You have a bidding problem. Performance pay can't fix margin issues that exist because jobs are systematically underbid.
Start with real job data — not optimistic estimates
Pull the actual hours from similar jobs over the past six to twelve months. Not the estimated hours — the actual hours it took to complete. What's the median? What's the best performance you've seen on that job type with a competent crew?
Your baseline should be close to the median. Your goal — the performance threshold that earns a bonus — should be somewhere between the median and the best. Not the best plus 10%. The best is the ceiling, not the floor.
Validate with the crew before you set it
Ask an experienced foreman: "On a good day — not a perfect day, a good day — how many hours does this job type take?" Their answer, combined with your historical data, gives you a goal that has real-world credibility.
Workers who were consulted in setting the goal are far more likely to believe it's achievable than workers who received the goal from management. The process of asking is itself a form of buy-in.
Build in the right stretch — specific to the job type
A goal that's exactly equal to the average takes no special effort to hit. A goal that's 20% below average requires optimization to hit. The right stretch for most job types is somewhere between 5% and 12% below the current median performance.
New to performance pay? Start at 5%. After the first six months, revisit the data. If 80% or more of crews are hitting the goal comfortably, tighten it. If fewer than 40% are hitting it, loosen it. Let the actual data tell you where the line belongs.
Make progress visible — not just at the end
A goal that workers can't track in real time isn't really a goal — it's a judgment. The Protiv app shows workers their current pace against the job goal throughout the day, so they can see whether they're on track and adjust their behavior accordingly.
This visibility is the mechanism. Workers who find out at the end of the week that they missed the goal by two hours can't do anything about it. Workers who see at noon that they're an hour behind can. Goal-setting without real-time tracking is like telling someone they're late without showing them a clock.
"The right goal is the one where a crew looks at the number in the morning and thinks: 'We can hit that if we're focused.' Not easy. Not impossible. Achievable with real effort."
After the first 30 days of a new program, review the attainment rate across all qualifying jobs. If you're in the 60–70% range, your goals are calibrated correctly. If you're outside that range, adjust — and adjust transparently, explaining to the crew why the target changed and how it was recalculated.
See Protiv in action
A 30-minute demo shows you exactly how to set up performance pay for your specific job types and crew structure.