How Flat-Rate Pay Works From the Tech's Side

Why this matters

Flat-rate pay sounds simple: every job carries a set number of hours, and you get paid those hours whether the job takes you less time or more. A fast, well-stocked tech on a full board can earn well past what the same tech would make hourly. The same tech in a slow week, or stuck on a recall, or waiting two hours on a parts run, can earn less than the minimum wage would have paid, at which point federal law makes the employer top it up. Most techs on flat rate know the first half of that sentence and not the second. Knowing both lets you judge an offer, read your stub, and spot the week the floor should have kicked in.

This is not personal financial or legal advice. It explains the mechanics so you can check your own numbers and ask the right question.

Flag hours, clock hours and the gap between them

Flag hours (also called billed, booked or sold hours) are the hours the pay plan assigns to a job, usually straight from the shop's flat-rate price book. A capacitor replacement might flag at 1.0 hour whether you finish it in 25 minutes or 90.

Clock hours are the hours you actually worked: from the start of your first task to the end of your last, minus a bona fide meal break, under federal rules. They include more than wrench time. Time spent traveling between job sites during the workday is hours worked (29 CFR 785.38). So is time you are required to spend waiting at a job or the shop when you are "engaged to wait" (29 CFR 785.15), shop meetings, loading the truck at the shop, and required training. Your normal commute from home to the first job generally is not, under the Portal-to-Portal Act, though driving a company vehicle with required duties attached can change that.

Flat-rate pay is a piece-rate system. You are paid per unit (the flag hour), not per hour of time. That matters because the FLSA has specific rules for piece-rate pay, and they run on clock hours, not flag hours.

Efficiency: the number your paycheck is really riding on

Efficiency is flag hours divided by clock hours, as a percentage. Flag 44 hours in a 40-hour week and you ran 110 percent. Flag 30 and you ran 75 percent.

On flat rate, efficiency is your effective raise or pay cut against an hourly tech at the same rate. What drives it is mostly outside the job itself:

• Board density. Gaps between calls are clock hours with no flag hours attached.
• Drive distance. A spread-out territory burns clock time that pays nothing on flat rate.
• Parts availability. A supply-house run in the middle of a job is pure clock time.
• Job mix. Some jobs flag generously against how long they really take and some flag tight. Who gets which calls is a dispatch decision, and on flat rate it is a pay decision too.
• Recalls. Going back to fix your own work usually flags at zero.

The last one deserves its own line. A recall (also called a comeback) is a return trip to fix work you did; most flat-rate plans pay no flag time for it. A callback in many shops means a new problem at a past customer, which is paid normally. Plans differ, so read yours. How a recall policy should work is its own subject; see related: How Callbacks and Warranty Work Affect Your Pay.

The floor the employer still has to meet

Flat rate does not suspend federal wage law. For a nonexempt tech, two FLSA rules still apply every workweek; the Department of Labor summarizes them in Fact Sheet 22 (hours worked) and Fact Sheet 23 (overtime).

Minimum wage, averaged over the workweek. Under the FLSA the test is total pay for the workweek divided by total hours worked in it, and the result must be at least the minimum wage (29 CFR 776.4 and 778.104 treat the workweek as the unit). If it falls short, the employer owes the difference. This averaging is a federal rule, and states can override it. California does not let an employer average: each hour must be paid at least the minimum wage, and its Labor Code 226.2 requires piece-rate workers to be paid separately for rest and recovery periods and for other nonproductive time. Several states also set minimum wages well above the federal floor, so the floor you check against is the higher of the two.

Overtime on the piece-rate method. For hours over 40 in a workweek, the regular rate is your total piece-rate earnings for the week (plus any spiffs or bonuses) divided by total hours worked. You are then owed an extra half of that regular rate for each overtime hour, because the piece earnings already paid the straight time for every hour, overtime hours included (29 CFR 778.111). An alternative is allowed if agreed in advance: paying one and a half times the piece rate for pieces done during overtime hours (29 CFR 778.418). Either way, paying flag hours with no overtime line in a 50-hour week is not compliant for a nonexempt tech, unless a specific exemption applies, such as the FLSA section 7(i) exemption for some commissioned employees of retail or service establishments, which has its own conditions about how much of your pay is commission. State law adds layers here too: California owes daily overtime after 8 hours in a workday, and a flag-only week there fails on rest-period pay before overtime is even reached.

If your employer has a reason why one of these rules does not apply to you, they should be able to name it. That is the point at which to talk to your state labor department or an employment attorney, with your own hour log and your stubs in hand.

Worked example: one tech, three weeks

Same tech, same flag rate, written F (pay per flag hour), so the math holds at any pay level. Assume, for illustration, that the higher of the federal and state minimum wage where this tech works is 0.40 F per hour, meaning the flag rate is two and a half times the minimum. The tech's state uses the federal workweek-averaging rule. Each step below is the calculation payroll should be doing.

Week A, a full summer board. 48 clock hours, 52 flag hours. Efficiency is 52 over 48, or 108 percent.

• Piece earnings: 52 flag hours at F is 52.00 F.
• Regular rate: 52.00 F divided by 48 clock hours is 1.083 F per hour.
• Minimum-wage check: 1.083 F is above 0.40 F. Pass.
• Overtime: 48 minus 40 is 8 overtime hours. Half the regular rate is 0.542 F, times 8 hours, is 4.33 F.
• Total pay: 52.00 F plus 4.33 F is 56.33 F. Per clock hour, 56.33 F over 48 is 1.17 F.

Week B, a mild week in the shoulder season. 45 clock hours, 22 flag hours. Efficiency is 22 over 45, or 49 percent.

• Piece earnings: 22.00 F.
• Regular rate: 22.00 F divided by 45 hours is 0.489 F.
• Minimum-wage check: 0.489 F is above 0.40 F. Pass, narrowly.
• Overtime: 5 hours at half of 0.489 F, which is 0.244 F, comes to 1.22 F.
• Total: 22.00 F plus 1.22 F is 23.22 F.

Week C, slow, plus a recall. 45 clock hours, of which 3 were spent on a recall that flagged zero. Flag hours for the week: 16. Efficiency is 16 over 45, or 36 percent.

• Piece earnings: 16.00 F.
• Regular rate: 16.00 F divided by 45 hours is 0.356 F.
• Minimum-wage check: 0.356 F is below 0.40 F. Fail. The employer owes enough to bring straight-time pay to 45 hours at 0.40 F, which is 18.00 F, so the make-up is 18.00 F minus 16.00 F, or 2.00 F.
• Overtime: the regular rate is now the minimum wage, 0.40 F. Half of that is 0.20 F, times 5 hours, is 1.00 F.
• Total: 18.00 F plus 1.00 F is 19.00 F.

What the three weeks show. Week A paid 1.17 F per clock hour; Week C paid 19.00 F over 45 hours, or 0.42 F per clock hour. That is close to a threefold swing (1.17 divided by 0.42 is 2.8) in what an hour of this tech's life was worth, on the same pay plan. Notice also that the recall's 3 hours still counted: they pushed Week C's clock hours to 45, which is what created both the minimum-wage make-up and the overtime premium. A shop that leaves recall time off the clock because "it pays nothing anyway" is shrinking exactly the denominator the law protects. And notice Week B: it passed the floor, so nothing was owed beyond the overtime premium, and the tech still took home well under half of Week A's pay.

What would change the answer. In California, none of these weeks is computed correctly as shown: rest-period pay and nonproductive time (the drive and parts time) must be paid on top of piece earnings, every hour must clear minimum wage without averaging, and any day over 8 hours earns daily overtime. If this tech were commission-paid under a valid section 7(i) exemption, the overtime lines in all three weeks could legitimately be zero, but Week C's minimum-wage make-up still would not be, and 7(i) requires the regular rate to exceed one and a half times the minimum wage, which Week C fails. If the shop instead paid one and a half times the flag rate for jobs done after hour 40 under a prior agreement, Week A's overtime would be computed on the flag hours booked in those last 8 clock hours instead.

Judging a flat-rate offer

The flag rate alone tells you almost nothing. Ask:

• What efficiency do techs here actually average, by season? A high flag rate at 70 percent efficiency can pay less than a lower rate at 110 percent.
• How are recalls, parts runs, drive time, meetings and training paid? Each is clock time. Unpaid on flat rate, they lower your efficiency; the floor catches only the worst weeks.
• Is there a guaranteed hourly floor above minimum wage? Many shops pay the greater of flag earnings or a set hourly rate per week. That is a real benefit; get it in writing.
• How is overtime computed and shown on the stub? You want to see clock hours and an overtime premium line, not just flag hours.
• Who assigns the calls? On flat rate, dispatch is a pay lever.

A busy month can still pay less than a slow one when the busy work is long, tight-flagging installs and the slow month was short, generous service calls; see related: The Flat-Rate Tech Who Made Less in a Busy Month.

Keeping your own count

Track clock hours and flag hours yourself, every day, with the jobs attached. At week's end, divide pay by clock hours and compare against the minimum wage where you work. Most weeks that check takes a minute and passes. The week it fails is the week your record turns a hunch into a number.

References

• U.S. Department of Labor, Fact Sheet 23 (overtime pay requirements) and Fact Sheet 22 (hours worked)
• 29 CFR 778.111 and 778.418 (piece-rate overtime); 29 CFR 785.15 and 785.38 (waiting and travel time)
• FLSA section 7(i), 29 U.S.C. 207(i), commissioned employees of retail or service establishments
• California Labor Code 226.2 (piece-rate compensation); your own state labor department's minimum wage page
• See related: Reading Your Pay Stub as a Technician, How Callbacks and Warranty Work Affect Your Pay, The Flat-Rate Tech Who Made Less in a Busy Month, Overtime Rights a Tech Should Know