How Callbacks and Warranty Work Affect Your Pay

Why this matters

Every tech has gone back to a job. Sometimes it was your loose wire. Sometimes the new part failed in a week, or the customer's kid stuffed a toy in the return, or another tech misdiagnosed it and you got sent to clean up. On hourly pay, all of those cost you nothing but pride. On flat rate or commission, the recall policy decides whether that trip pays normally, pays nothing, or actually takes back money you already earned. Shops write these policies very differently, some fair and some not, and the legal floor underneath them is narrower than most owners think and wider than most techs know.

Four kinds of return trip, and why the label matters

Shops use these words loosely. Pin down which your pay plan means, because the label usually decides the pay.

• Recall (or comeback): a return to fix work you did, because of how you did it. Most flat-rate plans pay this at zero flag hours, on the theory that you were already paid to do it right.
• Callback: a return to a past customer for a new or unrelated problem. This is a new job and should flag normally.
• Manufacturer warranty work: a part failed inside the manufacturer's warranty, and the manufacturer reimburses the shop a set labor allowance, often less than the shop's own flat-rate book time. Plans commonly flag these at the allowance, or at a reduced shop rate.
• Shop workmanship warranty: the shop's own guarantee on its labor, for example one year. A return under it is free to the customer; whether it is free to you depends on whether it was your workmanship.

The fight is almost always over a trip coded as a recall that was really one of the other three.

The common policies, side by side

None of these is illegal on its face. What makes a policy fair or unfair is mostly how "recall" gets decided.

What a fair recall policy looks like

There is no legal standard for fairness here, so these are the tests experienced techs use when judging a shop's plan or negotiating one:

Cause, not just return. Zero-flag should apply to returns caused by your workmanship: a loose connection, a missed step, a callback for something you should have caught. A part that failed on its own is a warranty event, a customer-caused problem is a callback, and a return caused by another tech's diagnosis belongs to that tech or to the shop. A plan that zeroes every return trip regardless of cause makes you the shop's insurer.

A time window. Thirty days from the original visit is a common starting point for repairs, often longer for installations. A furnace you serviced eight months ago that now has a cracked igniter is not a recall.

Someone who decides, and a way to dispute it. The service manager, not the dispatcher who booked it, should code a return as a recall, and you should be able to say "that was a defective part" and have it looked at.

Warranty money flows to the work. If the shop collects a labor allowance from the manufacturer for a warranty repair, a plan that pays you zero on it is keeping the whole reimbursement. Flagging warranty jobs at the allowance, or at the shop's reduced rate, is the usual fair compromise.

No double penalty. Charging back the original job's flag hours on top of a zero-flag recall makes one mistake cost twice. Plans that do this tend to be the ones techs leave.

The floor that still applies

Two legal rules sit under every policy, whatever it says.

Recall time is hours worked. A recall that flags zero still puts clock hours on your week, and for a nonexempt tech those hours count when the minimum-wage and overtime floors are checked. Under federal law the minimum-wage test averages total pay over the workweek; California and some other states do not allow that averaging. See related: How Flat-Rate Pay Works From the Tech's Side for that arithmetic. A shop that keeps recall time off the timecard because "it pays nothing anyway" is shrinking the hours the floor is measured against.

Deductions for faulty work have limits, and the state layer is often stricter. Under the FLSA, wages must be paid "free and clear" (29 CFR 531.35, which the Department of Labor applies to deductions for losses), so a deduction for the employer's loss, such as a charge-back for bad work, may not reduce your pay for the workweek below the minimum wage or cut into the overtime premium you are owed. That is the federal floor. Several states go much further. California's wage orders allow a deduction for breakage or loss only when it was caused by a dishonest or willful act or gross negligence, so an ordinary workmanship mistake cannot be charged to you there at all. New York Labor Law 193 bars wage deductions except for listed categories. Many other states require your written authorization for any deduction. A commission reversal is treated differently from a deduction in many states, because it can be part of how the commission is earned in the first place, which is why the written plan matters; California requires commission plans to be in writing and signed (Labor Code 2751).

Whether a particular charge-back is lawful in your state is a question for the state labor agency, and this is not legal advice.

Worked example: one month, three policies

A tech on flag rate F per flag hour books 150 flag hours in a four-week month on regular work, over 180 clock hours. Four return trips added 6.0 more clock hours:

• Trip 1: the tech's own loose connection, day 9, 1.5 clock hours. The original job had flagged 3.0 hours.
• Trip 2: a new capacitor failed on day 10, 1.0 clock hour. Book time for the replacement is 1.0 flag hour.
• Trip 3: another tech misdiagnosed a no-heat; this tech went back and found the real fault, 2.5 clock hours. Book time for the diagnosis and repair is 2.0 flag hours.
• Trip 4: a drain line clogged by debris on day 45 after an install, 1.0 clock hour. Book time 1.0 flag hour.

All three versions below run on the same 186 clock hours (180 plus 6.0).

Policy A, every return flags zero. Pay is 150 F. Per clock hour, 150 F divided by 186 is 0.81 F.

The fair version (zero only for own workmanship inside 30 days). Trip 1 flags zero. Trip 2 is warranty and flags its 1.0 hour, Trip 3 flags its 2.0 hours, and Trip 4 was customer-caused (and outside the window anyway), so it flags its 1.0 hour as a callback. Pay is 150 plus 4.0, or 154 F, which is 0.83 F per clock hour. The difference from Policy A is 4 F, about 2.7 percent of the month's 150 F of regular pay.

Policy A plus charge-back. Everything zeroes as in A, and Trip 1's original 3.0 flag hours are taken back. Pay is 150 minus 3.0, or 147 F, which is 0.79 F per clock hour, and the tech is now 7 F behind the fair version on the same month of work: the 4 F of trips that flagged zero plus the 3 F taken back.

Where the floor bites. Trip 1 and Trip 3 both landed in week 3, a slow week: 44 clock hours and 18 flag hours. Say, for illustration, that the higher of the federal and state minimum wage where this tech works is 0.40 F per hour, so the flag rate is two and a half times the minimum. Before the charge-back, week 3 pays 18 F over 44 hours, 0.41 F per hour, just above the floor of 44 times 0.40, which is 17.6 F. Take the full 3.0 F charge-back in that week and pay drops to 15 F, or 0.34 F per hour, below the floor. Under the federal rule, only 18 F minus 17.6 F, or 0.4 F, of the charge-back can come out of that week, and the overtime premium on the week's 4 hours past 40 is owed on top regardless. Under California's rules none of the 3.0 F could be charged for an ordinary workmanship error, and the no-averaging rule would have to be checked hour by hour.

What the month shows. The policy label moved pay by up to 7 F, about 4.7 percent of 150 F, on six clock hours of return trips. That is small in one month and large over a year, and nearly all of it came from how Trips 2, 3 and 4 were coded, not from Trip 1, which was genuinely the tech's own mistake.

What to ask before you sign on, or before you dispute

• Who decides a return is a recall, and can I dispute it?
• What is the window, for repairs and for installs?
• How are manufacturer warranty jobs flagged?
• Is anything ever charged back, and if so, is it in writing with my signature?
• Does recall time go on the timecard? It should, every time.

Keep your own record of each return trip with its cause, the original ticket number and your clock time. See related: Tracking Your Own Hours and Pay. When a trip gets coded wrong, that record is what turns "that wasn't my fault" into a correction. See related: Raising a Paycheck Error.

References

• 29 CFR 531.35 (wages paid free and clear; limits on deductions) and the U.S. Department of Labor Wage and Hour Division guidance on deductions for losses
• California Industrial Welfare Commission wage orders, section 8 (deductions for shortage, breakage or loss); California Labor Code 2751 (written commission agreements)
• New York Labor Law section 193 (deductions from wages)
• See related: How Flat-Rate Pay Works From the Tech's Side; Commission and Spiff Math a Tech Should Check; The Flat-Rate Tech Who Made Less in a Busy Month