The Redo: Eat It vs Explain It Decision Tree
Why this matters
A job has to be done over. The question that decides your reputation and your margin is: do you eat the cost silently, or explain it and charge? Get it wrong in one direction and you bleed money eating redos that were never your fault, while training customers that your work is endlessly free to revisit. Get it wrong the other way and you nickel-and-dime a customer over your own mistake and lose them plus their referrals. The redo is a fork in the road, and the right turn depends on one thing: whose fault is it, honestly? Quality is cheaper than callbacks, so the cheapest redo is the one your standard prevented. But once you're here, sort it cleanly.
Start here: go look, then assign cause honestly
Don't decide over the phone and don't decide defensively. See the work, find the real root cause, and assign it without flinching in either direction. Then walk the tree.
Branch 1: Is the redo your fault?
If the work failed because of something you or your crew did or skipped (a bad connection, a missed test, a wrong part, a rushed step): you eat it. Fully, quickly, and without making the customer feel the cost. This is not generosity; it's the deal. You sold a result, the result failed, you make it right on your dime. The way you eat it matters as much as that you do:
- Don't visibly resent it. A grudging redo poisons the goodwill the redo was supposed to protect.
- Don't make the customer prove it or argue it. If you know it's yours, own it before they have to push.
- Move fast. Speed of recovery is what the customer remembers and repeats. A fast, gracious redo of your own mistake often earns more loyalty than a job that never failed.
Eating your own redo well is some of the best marketing you'll ever do.
Branch 2: Is the redo the customer's fault or choice?
If the work has to be redone because of something the customer did, decided, or changed, this is explain-and-charge, but the explanation determines whether the charge lands as fair or feels like a gouge. Cases:
- They changed their mind about scope, layout, or finish after you built what they asked for.
- They caused the failure (misuse, damage, ignoring your instructions).
- They declined the fix you recommended, and the thing you warned about is what failed.
In all three, you're entitled to charge for the redo. But you have to explain it like a teacher, not bill it like a stranger:
- Show them physically what happened and why it's not the original work failing.
- Connect it to the earlier decision honestly ("this is the part I flagged and you opted to leave").
- Name exactly what they're paying for, no mystery line.
Branch 3: The gray area (shared fault or unclear cause)
Plenty of redos aren't cleanly anyone's fault: ambiguous instructions, a part that failed but you installed it, a miscommunication on scope. Here the rule is: lean toward eating it, especially when the ambiguity is partly yours. The reasoning is pure economics. The cost of eating an occasional gray-area redo is small and one-time. The cost of a customer who believes you dodged a fair share of blame is a lost relationship plus the bad story they tell. When it's genuinely 50/50, the relationship is worth more than the ticket; absorb it or split it, don't fight to win it.
The two traps, named
| Trap | What it looks like | What it costs |
|---|---|---|
| Eating too much | Redoing customer-caused work for free to "keep the peace" | Bleeds margin, trains customers that nothing is final or theirs to maintain |
| Charging too much | Billing the customer for your own mistake, or itemizing blame on a gray-area call | Wins the ticket, loses the customer and the referrals |
The discipline is symmetric: eat what's yours fully and gracefully; charge what's genuinely theirs but explain it like you're teaching, not collecting; and in the gray, protect the relationship over the ticket.
Document either way
Whichever branch you land on, record it. If you ate it, note the root cause so it feeds your comeback rate and becomes a standard that prevents the next one. If you charged it, document why (the customer change, the declined recommendation, the misuse) so there's a record if memory gets convenient later. The redo you analyze is the callback you prevent next time, which is the only redo that's truly free.
References
- Trade-standard workmanship-warranty practice (what a shop stands behind vs what it bills).
- SBA guidance on customer-communication and dispute handling for service businesses.
- See related: The Warranty Callback, Track Your Comeback Rate, Building a Reputation for Quality.