Tying a Bonus to Quality, Not Just Speed

Why this matters

A bonus built around jobs-per-day or revenue-per-tech rewards exactly one thing: going fast. Techs are smart, and they will optimize for whatever you actually pay them on, not for whatever you hoped they would optimize for. Pay purely for volume and you will get volume, along with a rise in comebacks, a drop in documentation quality, and a slow erosion of the workmanship that got your shop its reputation in the first place. A bonus that survives contact with reality has to measure quality alongside speed, or it will quietly train your best people to cut the corners that are hardest to see until the customer calls back.

Speed-only metrics and how they get gamed

Any single metric that measures output alone, jobs completed, revenue billed, tickets closed per week, can be satisfied without doing good work. A tech chasing a jobs-per-day number can skip a step in a checklist, under-diagnose a job to get in and out, decline to test the fix before leaving, or recommend the fast repair over the correct one. None of this requires bad intent. It is simply what happens when the only number on the scoreboard is speed. The fix is not to abandon speed as a factor, a shop does need efficient techs, it is to make sure speed never stands alone.

Build the quality gate first, then add the speed incentive

The order matters. Decide what "quality" means in measurable terms before you build any bonus around volume:

• Callback and comeback rate, the percentage of jobs that require an unpaid return visit within a defined short window. This is the single strongest signal that speed came at the cost of correctness.
• Checklist and documentation completion. If your shop uses standardized checklists or requires photos, readings, or notes, a bonus-eligible job should mean a fully documented one, not a fast one with blanks left on the form.
• Customer satisfaction or survey score tied to the specific job, when you collect it. A tech who is fast but leaves customers cold is optimizing for the wrong outcome even if the callback rate looks fine.
• Warranty claim rate on that tech's work, if your shop tracks warranty issues by originating technician. A pattern of claims traces back to a quality problem the raw job count would never surface.

Only once these are defined do you layer in a volume or speed component, and only as a multiplier or a gate on top of the quality baseline, never as the entire bonus on its own.

Structures that work

• Gate, then reward. A tech must be under a maximum callback rate and meet documentation standards to be eligible for the speed or volume bonus at all that period. Miss the gate and the volume bonus does not pay out, no matter how many jobs got done. This is the simplest structure and the easiest for a crew to understand.
• Blended score. Combine a quality score and a volume score into one number, weighted so quality carries genuine weight, not just a token ten percent. A common trap is weighting quality so lightly that it barely moves the outcome; if the blended score barely changes whether callbacks were high or low, the plan is speed-only in disguise.
• Team-level quality pool. Pay an individual speed bonus, but hold back a portion of a team-wide bonus pool tied to the whole crew's combined callback rate. This nudges techs to look out for each other's workmanship, not just their own numbers, and dampens the temptation to win at a teammate's expense.

Watch for the metric that hides the problem

A callback rate can be gamed too, if the definition is loose. A tech who talks a customer out of a legitimate complaint, or convinces them to call a manager instead of logging an official callback, can post a clean callback number while the underlying quality problem is real. Keep the definition of a countable callback out of the hands of the person being measured; it should come from the same intake or dispatch process every job goes through, not from a tech's self-report.

Introducing this to a crew already used to a volume-only bonus

Changing an existing bonus structure is a trust event, not just a math event; see the related article on changing pay structure without losing your best people for the rollout mechanics. The short version specific to quality gates: announce the change before it takes effect, explain the "why" in terms of protecting the shop's reputation and the team's earning long-term, and give the crew a full cycle to see their actual numbers under the new structure before it affects a real paycheck. A quality gate introduced as a surprise deduction reads as a pay cut. The same gate introduced as "here's what protects your bonus going forward, and here's your current number so you know where you stand" reads as fair.

References

• Society for Human Resource Management (SHRM), pay-for-performance and quality-metric design guidance
• U.S. Department of Labor, Wage and Hour Division, non-discretionary bonus guidance under the Fair Labor Standards Act
• See related: Commission Structures That Don't Encourage Overselling
• See related: Change the Pay Structure Without Losing Your Best People: Decision Tree