How to Stop Eating Callbacks (and Prove You Weren't at Fault)

A callback is a tax on doing business — except you're paying it even when you did nothing wrong. A homeowner points at a stain, a crack, or a leak and assumes it's on you. Without proof, you either argue (and lose the relationship) or eat the cost (and lose the money). Usually you eat it.

Here's the uncomfortable truth: a large share of callbacks aren't workmanship failures at all. They're pre-existing conditions, customer misuse, or unrelated issues that get pinned on you because you can't prove otherwise. The fix isn't better work — it's better proof.

The callback usually isn't your fault

The stain was there before you started. The crack came from settling. The 'leak' is condensation. You know this — but knowing it and proving it are different things. When the only record is your memory versus the customer's memory, the customer wins, because you want the referral more than you want to be right.

Document the pre-existing condition

The 'before' photo is the entire game. A wide shot of the work area before you touch anything, time- and location-stamped, captures the exact condition you inherited. Six months later, when a homeowner blames you for a mark that was already there, you send one photo and the conversation ends.

Make it impossible to skip

This only works if it happens on every job, automatically. That means the 'before' set is part of the crew's routine, the photos are stamped and filed without anyone thinking about it, and you can pull up any past job from your phone the moment a callback call comes in.

Turn proof into a policy

The best contractors make documentation a stated part of how they work — and they tell customers about it. 'We photograph everything before, during, and after' does two things: it reassures honest customers, and it quietly warns the few who'd have tried to blame you for a pre-existing problem.