A Mistake Is Discovered Months After the Job: A Decision Tree

Why this matters

The call comes in long after the job left your mind: a customer found a problem that traces back to work you did months ago. Time changes everything about this conversation. Evidence has degraded, other things may have happened to the system since, and the customer's memory of what was said and agreed has softened into their own version. Handling this well protects a real relationship and a fair claim; handling it badly either lets a genuine mistake go unfixed for a customer who trusted you, or hands out a free redo for a problem you never caused.

Start here: can you still verify what actually happened

Before deciding fault or a resolution, pull everything your business kept from the original visit: the invoice, job notes, photos, the signed estimate or scope, any follow-up communication. This record is your anchor against a memory, on both sides, that has had months to drift.

• Your records are detailed enough to reconstruct the visit. Go to "Comparing the record to the current problem."
• Your records are thin or missing (no photos, vague notes, nothing beyond an invoice line). You are working with limited information, which changes how confidently you can assign fault either way. Go to "When your own record is incomplete."

Comparing the record to the current problem

1. Does the failure match something your original scope actually touched? A problem in a system or component you never worked on is a different conversation than a failure in the exact part you installed or repaired.
2. Is the timeline plausible for this to be your original work failing, versus normal wear, a separate incident, or something that happened after your visit (another contractor's work, a modification, an unrelated event)? Ask the customer directly and without accusation: "Has anyone else worked on this since we were out, or has anything changed?"
3. Does the failure mode match a known failure pattern for the original work, or does it look like a new and different problem that happens to be in the same area?

If the match is clear and the failure traces convincingly to your original work, treat it as a genuine mistake (see below). If the match is unclear or points elsewhere, treat it as a legitimate dispute rather than an assumed fault (see "When the connection is genuinely unclear").

When it is a genuine mistake, discovered late

• Own it the same way you would if it surfaced the next day. Time passing does not change whether you were wrong; it only changes how the conversation feels for the customer, who has been living with a problem while assuming it was unrelated to your work.
• Acknowledge the delay explicitly. "I'm sorry this has been going on for months without us catching it, let's get it corrected." This costs nothing and matters more than it seems, because the customer has been carrying this longer than a same-week miss.
• Decide the resolution against your actual warranty or workmanship terms, not against guilt. If your stated terms have already lapsed, you can still choose to honor the spirit of the original commitment as a goodwill call; that decision belongs to whoever owns pricing and policy, not to guessing under pressure on the phone.

When your own record is incomplete

• Do not let a thin record become an automatic denial or an automatic concession. Both are overcorrections. A missing photo does not prove you did the work correctly, and it does not prove you did not.
• Ask the customer for anything they have: photos they may have taken since, other contractors' notes, dates they remember. Build the timeline together rather than defending a gap in your own file.
• Where genuine ambiguity remains after a good-faith look, lean toward a resolution proportionate to the size of the actual problem, not the size of the accusation. A modest goodwill gesture on an unclear case usually costs less than the relationship and reputation risk of a flat refusal.

When the connection is genuinely unclear

• Say so honestly, without sounding like a denial dressed up as diplomacy. "Based on what I can see, this doesn't look connected to what we did, here's why," followed by the specific reasoning, holds up far better than "that's not on us."
• Offer to take a fresh look in person before finalizing a position by phone. A problem that looks unrelated on a phone description sometimes turns out otherwise once someone is standing in front of it, and vice versa.
• If, after inspection, it genuinely is unrelated, you can decline responsibility for the original claim while still offering a fair quote to address the current problem. Those are two separate transactions and should be framed that way: "This looks like a separate issue from the original work, here's what I'd recommend to fix it now."

What to watch for on both sides

• A customer who has clearly had other work done since, and is bundling all of it into one claim against your original job, deserves a careful, specific walkthrough of what your scope actually covered.
• A business that reflexively assumes any late claim is opportunistic misses the real callbacks that simply took months to surface, which is common and not evidence of bad faith.

The judgment to keep

Time does not decide fault. The record and the failure pattern do. A late discovery deserves the same honesty as an immediate one, just with more legwork to reconstruct what actually happened before anyone commits to a resolution.

References

• Trade-standard warranty and workmanship-guarantee practice.
• Better Business Bureau guidance on resolving delayed consumer complaints.
• See related: A Fair Complaint vs an Unreasonable One; Apologizing Without Admitting Liability.