How do you design a flat-rate (piece-rate) pay plan for techs?

Flat-rate pay is pay for the task, not for the time.

Your book assigns every common job a set number of hours — a capacitor swap, a drain clear, a condenser changeout — and the tech earns those hours at their pay rate no matter how long the work actually takes.

Finish ahead of the book and the earnings per clock hour rise; run behind and the paycheck shows the same task hours, with no extra book time for the overrun.

The one thing that never changes underneath is that every clock hour still counts as hours worked, which is where the wage-and-hour rules in the third section below attach.

Federal wage law knows this structure well: the Department of Labor's overtime rules treat job-rate and day-rate pay as their own category, with a specific formula for computing overtime under 29 CFR 778.112.

Flat rate is also how many plumbing shops pay per fixture, per setting or per install — in wage law that is piece-rate pay, and it lands under the same formula.

So the design question is never whether flat rate is allowed; it is whether your version of it survives the arithmetic.

Keep it separate from flat-rate pricing.

Pricing is the customer-side decision: the menu price a homeowner pays per task.

Pay is the technician-side decision: how the tech's wage is computed from task hours.

Shops often feed both from one book, but they are two different dials with two different risks.

A price change is a margin call; a change to the hours a task pays is a paycheck change your techs will read within a day.

This page is about the pay side only.

The task book is the plan.

Every task a truck commonly performs needs a set of hours, and you have two honest ways to source them: published flat-rate labor guides, or your own measured completion times.

Whichever you start from, the book is only credible if it survives contact with your trucks — so calibrate it.

Pull real jobs, compare book hours to actual completion times task by task, and fix the lines where the book is wrong.

Your techs already know which tasks pay badly under the current book; a design process that never asks them will ship a grievance list dressed up as a pay plan.

Set the rate underneath the hours.

Book hours turn into a paycheck only through a rate — a dollar-per-book-hour figure, or a per-task price you build from it.

Two design rules keep the structure sane.

First, keep the math simple enough that a tech can predict a paycheck before the week starts; complexity reads as discretion, and discretion reads as favoritism.

Second, separate the diagnostic line from the repair lines in the book so each is priced on its own — a book that buries diagnosis inside a bundled task price will pay the careful tech and the careless one identically, which is exactly the wrong signal for callback rates.

Write the mechanics down and date them: how task hours are recorded and approved, when the book gets reviewed, and how a tech challenges a task time they believe is wrong.

Task times drift — equipment changes, product mixes change, a task that took an hour in 2024 takes forty minutes now.

A book nobody has re-checked in two years is quietly re-pricing every tech's day.

If you are still weighing flat rate against hourly or commission, start with our HVAC technician pay plan comparison; the rest of this page assumes you have chosen flat rate and are building it.

The Fair Labor Standards Act (FLSA), enforced by the U.S. Department of Labor, applies to flat-rate techs the same as hourly ones — the plan changes the arithmetic, not the duty.

Flat-rate pay does not remove overtime.

For job-rate and day-rate workers, the regular rate is the total job pay for the week divided by the hours actually worked, plus an extra half-time at that rate for each hour over 40 in a workweek (29 CFR 778.112).

Piece-rate techs follow the same method: all piece earnings plus any other pay for the week, divided by all hours worked, with an extra half of that rate for every hour over 40 (29 CFR 778.111).

A worked example shows how little is added when the plan already paid straight time for every hour: a tech who earned $523 across 50 hours has a regular rate of $10.46, and because straight time is already covered for all 50 hours, only the extra half-time is owed — 10 overtime hours add $52.30.

The discipline is in the divisor: every hour actually worked goes in, including windshield time, bench time between calls and any waiting time — not just the hours the book paid for.

Compliance is tested workweek by workweek: under the FLSA's own rules there is a violation of the Act in any workweek when something — the regulation names employee-paid tool costs as its example — cuts into the minimum wage or overtime wages required to be paid for that week (29 CFR 531.35).

Flat rate makes that weekly test a live calculation, and the number to watch is the week's total flat-rate earnings divided by the week's total hours actually worked, against the minimum wage.

A week heavy on slow tasks, long diagnostics or drive time can drag that figure below the floor even when the book was followed to the letter — and in that workweek, the shortfall below the required wages is owed.

Run the division every week; it is the federal backstop and the single calculation that most often breaks a young flat-rate plan.

If the plan layers commission or bonuses on top of flat-rate tasks, the regular rate absorbs them — with one defined exception.

Commissions are pay for hours worked and count in the regular rate whether or not they are the tech's only pay.

Bonuses count too, unless they fit one of the FLSA's listed exclusions, and the exclusion people reach for is narrow: a bonus is truly discretionary — and left out of the math — only when the employer decides both whether to pay and how much at or near the end of the period, with no prior promise.

An announced spiff or bonus plan is not discretionary, and neither are production, quality or attendance bonuses, or bonuses announced to make techs work faster or stay with the company — those all go into the regular rate.

The FLSA's own arithmetic shows how a bonus folds in: an hourly tech paid $12 an hour for 46 hours with a $46 production bonus has a $13 regular rate, so overtime is owed at $19.50 an hour, not $18.

The one narrow path around FLSA overtime, the section 7(i) exemption, demands that every test hold at once: the employer must qualify as a retail or service establishment, meaning 75% of annual dollar sales of goods or services is not for resale and the business is recognized as retail in its industry; the employee's regular rate must exceed 1.5 times the minimum wage; and more than half of the employee's pay over a representative period of at least one month must be commissions.

On the retail question, assume nothing for an HVAC or plumbing service company: in May 2020 the Department of Labor withdrew the old regulation that courts had read as carving air-conditioning contractors out of the exemption's definition, and whether a service company qualifies now is decided case by case.

One more floor: federally funded work.

The Davis-Bacon and Related Acts apply to contractors and subcontractors on federally funded or assisted contracts over $2,000 for construction, alteration or repair of public buildings or public works, and they require at least locally prevailing wages and fringe benefits.

A slow flat-rate week can fall through that floor on a prevailing-wage job, so the plan needs a check against the job's wage determination before you bid the work.

Compliance here is fact-specific to your pay mix and your state. Put the finished plan in front of an employment attorney or the Department of Labor's Wage and Hour Division before it goes live — retroactive overtime is the most expensive way to learn the math.

The callback is where flat-rate plans quietly break.

The task's book hours were already paid once, so the return visit earns no new book hours unless your plan says otherwise — and a plan that says nothing pays for speed over accuracy, because the tech who rushed the first visit loses nothing on the second.

Decide the policy before the first callback, write it down, and make sure every tech can recite it.

You have three levers, and shops combine them.

Re-pay the task: the callback's task hours pay again at book, which costs you double but keeps the tech whole for rework that was not their fault.

Pay callback time hourly: return visits ride an hourly rate instead of the book, which costs less and keeps the book clean.

Split by cause: the plan pays fully when the callback traces to the part, the installation conditions or the shop — and differently when the diagnosis or workmanship fell short.

Whatever you choose, one rule outranks the policy: a callback is hours actually worked.

Even where the plan pays no task hours for the return visit, the time still counts in the weekly division — unpaid callback hours drag the effective regular rate down, and a callback-heavy week can push it below the minimum-wage floor from the section above.

Separate warranty from rework in the same written policy.

A repeat visit for a failed manufacturer part, a warranty-covered component or a customer-damaged item is a different event from a callback on your own work, and techs should never be guessing which one a dispatch is.

Name the categories, name who approves each, and name what each pays.

Then track it.

Callback rate per tech against your own baseline is the health metric of a flat-rate plan — no industry benchmark needed, just your own numbers trending.

If callbacks climb after a book revision, the revision underpriced the careful work.

That is a book problem, and it gets fixed in the book, not in the paycheck of whoever drew the short tasks that week.

For the wider system the plan lives in — sourcing, screening, keeping techs — see our guide to hiring HVAC and plumbing techs.

Everything in the overtime section above is federal law, so it applies to a California shop the same as any other — but it is a floor, not a ceiling, and states add wage-and-hour rules on top of it.

California is the state where flat-rate and piece-rate pay plans meet the most additional law, and you should not design one there from federal sources alone.

One caution from our own research: the California-specific piece-rate rules — including how rest periods and other non-productive time must be paid under a piece-rate plan — were not confirmed in the sources we read for this page, so we will not restate them secondhand.

Before you run flat-rate techs in California, put the plan in front of the California Labor Commissioner's Office, which enforces the state's wage-and-hour rules, or an employment attorney who works in them — and ask specifically how your plan must treat rest periods, travel between jobs and other paid-but-not-on-a-task time.

Ask the same question about the weekly earnings-per-hour check in the overtime section: that weekly test is the federal backstop, and our research — which covered the federal rules only — did not confirm whether California accepts a weekly test for flat-rate and piece-rate pay.

Treat it as the federal floor, not as settled for California, and put the question directly to the Labor Commissioner's Office.

The answer changes the arithmetic of every task rate in your book.

One California rule our research did confirm: employers with 15 or more employees must include the pay scale for a position in any job posting, and must give applicants the pay scale on reasonable request (Labor Code 432.3).

A flat-rate plan is a pay scale — the rate structure your posting advertises is the one the law will ask about — so the task rates and how they compute into earnings belong in your California job ads, not just in your handbook.

This page is employer career and business information, not legal advice. Pay-plan rules are fact-specific and state-specific — confirm the plan with the California Labor Commissioner's Office, the U.S. Department of Labor's Wage and Hour Division, or an employment attorney before it goes live.