Pay plans for technicians: hourly pays for slowness, commission pays for selling

Compliance is not optional and does not care what you call it

This deserves its own section because it is where well-intentioned owners create expensive problems.

Calling someone a flat-rate technician, or paying by percentage, does not remove wage-and-hour obligations for a non-exempt employee. Minimum wage and overtime requirements generally still apply, and overtime calculations on incentive pay are more complicated than on straight hourly — the incentive typically has to be factored into the regular rate for the period. Deducting callbacks or damage from pay is restricted in many places. And classifying technicians as independent contractors to avoid all of this is one of the most consistently penalized arrangements in the service trades.

Rules vary by state and change, and the cost of getting this wrong is retroactive. If you are moving to any incentive-based structure, have it reviewed by someone who does employment law in your state before the first pay period, not after the first complaint.

The three levers

A durable plan pays on three things, not one.

Lever 1 — production. Revenue generated, billable hours, or jobs completed. This is the base and the largest component, and it is what most plans get right.

Lever 2 — quality. Callback rate, customer review scores, first-time fix rate, inspection results. This is what stops production from being pursued at the customer's expense. It works best as a multiplier or a gate rather than a small bonus: a technician whose callback rate exceeds a threshold does not earn the production bonus at all, which is a far stronger signal than deducting a hundred dollars.

Lever 3 — growth. Memberships sold, training completed, apprentices mentored, certifications earned. This is the lever almost nobody uses, and it is what turns a good technician into someone who makes the whole crew better rather than hoarding what they know.

The proportions matter less than the presence of all three. A plan with only lever one will eventually produce a callback problem; a plan with only levers one and two will produce technicians who never teach anyone anything — which is how a company ends up with one irreplaceable veteran and a permanent hiring problem underneath him.

There is a fourth consideration that is not a lever but shapes all three: the threshold. Production bonuses usually begin above a floor that represents the revenue a technician must generate to cover their own cost. Setting that floor honestly — using loaded labor cost, vehicle, tools, insurance and a share of overhead rather than just the wage — is what keeps a generous-looking plan from paying out on work that lost money. Set too low, the plan rewards mediocrity; set too high, it reads as unreachable and nobody engages with it at all.

Design rules that hold up

• A technician must be able to calculate their own pay in their head. If it requires a spreadsheet, it will not change behavior, because nobody optimizes for a number they cannot see coming.
• Do not cap it. A cap tells your best performer that effort stops mattering above a line, and it is remembered long after the cap is removed.
• Pay on collected revenue, not billed revenue, when the technician has any influence over collection. Otherwise you are paying commission on receivables you may never see.
• Publish the plan in writing, with worked examples at three earning levels. Verbal pay plans generate disputes and turnover.
• Review it annually and change it rarely. Frequent adjustment reads as a moving target and destroys the trust the plan depends on.

Changing a pay plan without losing your crew

The transition is riskier than the design. Technicians hear "new pay plan" as "pay cut" by default, and the good ones have options.

Four steps make it survivable. Model it first against the last twelve months of real data, technician by technician, so you know exactly who would have earned more and who less — and if your best people would earn less, the plan is wrong, not them. Guarantee current earnings for a defined transition period, commonly ninety days, so nobody is financially at risk while learning the new structure. Explain it individually rather than in a group meeting, showing each person their own numbers under the new plan. And publish the calculation with every paycheck, so the plan is verifiable rather than trusted.

Eighteen months, measured

An HVAC and plumbing company with nine technicians, roughly $4.2 million in revenue.

Starting point. All technicians hourly, ranging from $26 to $38, with occasional discretionary bonuses. Average revenue per technician-day $1,180. Callback rate 9.4%. Membership sales averaging 1.2 per technician per month. Turnover of three technicians in the prior year.

What changed. The company moved experienced technicians to a base hourly rate plus a production percentage on collected revenue above a threshold, gated by a callback rate under 5% and a review average above 4.6. It added fixed spiffs for memberships and for completed certifications, and a mentoring bonus paid when an apprentice reached defined competency. Apprentices stayed hourly. Everything was modeled against twelve months of history first, and current earnings were guaranteed for ninety days.

Eighteen months later. Revenue per technician-day rose to $1,610. The callback rate fell to 3.8%, because the gate made it the single most expensive thing a technician could do. Membership sales rose to 4.7 per technician per month. Average technician earnings rose 22%, and the two highest performers rose 41%.

Turnover was zero over the period. The owner's read was that the retention effect came less from the money than from the transparency: technicians could see exactly how the number was built, and stopped suspecting that bonuses were arbitrary.

The plan is only half of it — dispatch is the other half

There is a problem that appears in every company that moves technicians to production-based pay, and it has nothing to do with the plan's design. Once earnings depend on the work performed, who gets assigned which job becomes a compensation decision.

Two technicians on the same plan can earn very differently because one was sent to three replacement estimates and the other to three warranty callbacks. If dispatch is informal — the dispatcher sends the easy work to the technician who complains least, or the lucrative work to the owner's favorite — the pay plan will be blamed for an unfairness that lives somewhere else entirely.

Four practices keep it clean. Rotate high-value opportunities on a documented basis rather than by judgment. Compensate separately for the work nobody wants — warranty callbacks, unpaid diagnostics, jobs that exist to protect a relationship — so that taking one is not a financial penalty. Make the assignment log visible, so a technician who suspects unfairness can check rather than stew. And watch the earnings spread for patterns that track dispatch rather than performance.

This is the most common reason a well-designed plan generates resentment, and owners almost always look at the formula first. The formula is usually fine. The dispatch board is where the problem is.

Five mistakes in technician pay plans

• Paying on revenue alone. It produces exactly the upselling reputation the trade is trying to shed.
• Building a plan nobody can calculate. Complexity does not change behavior; visible arithmetic does.
• Ignoring overtime and wage rules on incentive pay. The label on the plan does not change the obligation.
• Launching without modeling against real history. You find out who loses money after they have already handed in notice.
• Capping earnings. It is a small saving and a large message.

The numbers to watch

Five metrics tell you whether the plan is doing its job. Revenue per technician-day, which is the production signal and the reason the plan exists. Callback rate by technician, which is the quality signal and the one that must be visible to everyone, including the technicians. Labor cost as a percentage of revenue, which should stay stable or improve — if it rises sharply, the plan is paying for volume you were getting anyway. Earnings spread between your best and weakest technician, which reveals whether the plan actually differentiates. And voluntary turnover, measured over a full year after implementation, because a pay plan that raises production while quietly driving out experienced people has not improved anything.

Frequently asked questions

Should service technicians be paid hourly or on commission?

Neither in pure form, because each has a predictable failure mode. Straight hourly pays for time, which means it pays for slowness: the technician who takes five hours on a three-hour job earns more than the one who is quick and careful, and nothing in the structure rewards efficiency or selling the work that genuinely needs doing. Straight commission pays for revenue, which means it pays for selling — including selling things the customer did not need, and this does not require dishonest technicians to produce dishonest outcomes, only an incentive pointed in one direction and enough pressure. A workable plan pays for production while making quality and honesty measurably part of the compensation. The test for any plan is to ask what a technician would do if they optimized purely for their own paycheck: if the answer includes anything you would be uncomfortable explaining to a customer, the plan needs another lever.

What are the three levers a technician pay plan should pay on?

Production, quality and growth. Production means revenue generated, billable hours or jobs completed — this is the base and the largest component, and it is what most plans get right. Quality means callback rate, review scores, first-time fix rate and inspection results, and it is what stops production from being pursued at the customer's expense; it works best as a multiplier or a gate rather than a small bonus, so that a technician whose callback rate exceeds a threshold does not earn the production bonus at all, which is a far stronger signal than deducting a hundred dollars. Growth means memberships sold, training completed, apprentices mentored and certifications earned — the lever almost nobody uses, and the one that turns a good technician into someone who makes the whole crew better rather than hoarding what they know. The proportions matter less than the presence of all three.

Is flat rate or commission pay legal for service technicians?

It can be, but calling someone a flat-rate technician or paying by percentage does not remove wage-and-hour obligations for a non-exempt employee. Minimum wage and overtime requirements generally still apply, and overtime calculations on incentive pay are more complicated than on straight hourly, because the incentive typically has to be factored into the regular rate for the period. Deducting callbacks or damage from pay is restricted in many places. And classifying technicians as independent contractors to avoid all of this is one of the most consistently penalized arrangements in the service trades. Rules vary by state and change over time, and the cost of getting this wrong is retroactive. If you are moving to any incentive-based structure, have it reviewed by someone who practices employment law in your state before the first pay period, not after the first complaint.

How do you change a technician pay plan without losing people?

The transition is riskier than the design, because technicians hear new pay plan as pay cut by default and the good ones have options. Four steps make it survivable. Model it first against the last twelve months of real data, technician by technician, so you know exactly who would have earned more and who less — and if your best people would earn less, the plan is wrong, not them. Guarantee current earnings for a defined transition period, commonly ninety days, so nobody is financially at risk while learning the structure. Explain it individually rather than in a group meeting, showing each person their own numbers under the new plan. And publish the calculation with every paycheck so the plan is verifiable rather than trusted. The signal that a plan is designed correctly is that your best technician earns noticeably more and your weakest earns less.

Why do technicians think a pay plan is unfair even when it is well designed?

Usually because of dispatch, not the formula. Once earnings depend on the work performed, who gets assigned which job becomes a compensation decision — two technicians on the same plan can earn very differently because one was sent to three replacement estimates and the other to three warranty callbacks. If dispatch is informal, with easy work going to whoever complains least or lucrative work to a favorite, the pay plan gets blamed for unfairness that lives somewhere else. Four practices keep it clean: rotate high-value opportunities on a documented basis rather than by judgment; compensate separately for the work nobody wants, so taking a warranty callback is not a financial penalty; make the assignment log visible so a technician can check rather than stew; and watch the earnings spread for patterns that track dispatch rather than performance.