Found a Prior Tech's Error: Fix vs Flag vs Document Decision Tree

Why this matters

Discovering that someone before you did the work wrong puts you in a delicate position where the right move protects the customer, your company, and even the prior tech from a worse outcome, while the wrong move creates liability and burns trust. Quietly fixing a serious prior error can erase the evidence that the customer needs to recover from whoever caused it, and may put your name on a problem you did not create. Loudly trashing the prior work makes you look unprofessional and can be defamatory if you are wrong about what you are seeing. Saying nothing about a genuine safety hazard is the most dangerous choice of all, because a discovered hazard you ignore becomes your liability the moment you walk away from it. The decision among fix, flag, and document turns on severity, who owns the prior work, and above all whether the error is a safety hazard that you cannot in good conscience leave.

The situation

While working a job you find that prior work, whether by another company, a previous owner's handyman, or possibly your own company on an earlier visit, was done incorrectly. You have to decide whether to correct it, flag it to the customer for a separate decision, or simply document it, and how to communicate it without either alarming the customer unnecessarily or downplaying a real problem.

What is at stake

The stakes are safety, liability, and reputation. A real hazard left in place can injure people and will be traced to the last competent person who saw it, which is now you. Taking on a fix outside your scope without authorization can leave you owning the prior problem and unpaid for it. Speaking carelessly about a competitor's or another trade's work can expose you to a defamation claim if you mischaracterize it. There is also a relationship stake, because how you handle bad news the customer did not expect to hear strongly shapes whether they trust you. A measured fix-flag-document approach manages all of these.

Decision factors

• Severity and safety. Is the error a genuine hazard, a code violation, a reliability problem, or merely a stylistic difference you happen to disagree with.
• Scope and authorization. Is correcting it within the work you were hired and paid to do, or a separate job that needs the customer's approval and a quote.
• Who owns the prior work. Your own company, another contractor, an unknown party; this affects warranty recovery and how you communicate.
• Certainty. Are you sure it is wrong, or could there be context (a deliberate temporary measure, a code-compliant alternative) you are not seeing.
• Customer's ability to act. Whether the customer can pursue the prior party and what evidence they need to do so.
• Your competence and licensing for the correction. Whether the trade or scope of the fix is one you are licensed and equipped to perform, since correcting work outside your trade can replace one prior error with a new one that is now yours.

Options and when each wins

Fix it when correcting the error is within your authorized scope and necessary to complete your job correctly, or when it is a safety hazard that must be made safe immediately; in the hazard case you stabilize first and explain after. Fix-now wins when leaving the error would compromise your own work or endanger people. Flag it when the error is real and material but outside your scope, requiring the customer to decide on a separate repair; you present it factually, show the customer what you see, explain the risk and the options, and let them choose, often with a quote. Flagging wins for non-emergency problems that belong to a separate job or a separate party. Document it in all cases, and document-only is the right standalone choice when the issue is minor, debatable, or arguably acceptable and you simply want a record that you noted it. Across every path, describe what you observe factually rather than characterizing the prior tech's competence, both to stay professional and to avoid a defamation exposure. When the prior work is your own company's, escalate internally so the warranty and goodwill response is handled correctly rather than improvised on site.

What to document

Photograph the condition before you touch it, especially for a hazard, because that evidence is what lets the customer recover from the responsible party and protects you from being blamed. Record the specific defect in factual terms, the severity and any safety classification, what you did (fixed, flagged with a quote, or documented), and exactly what you told the customer. For a hazard, document the written notification and any make-safe action. If the prior work was your company's, note the internal escalation. Keep the language descriptive and evidence-based, never a verdict on the prior tech. The reason factual language matters beyond professionalism is legal: a written statement that another company's work was incompetent or dangerous, if it turns out you misread the situation, can expose you to a defamation or disparagement claim, whereas a description of exactly what you observed and measured is defensible regardless of who did the work. Describe the condition; let the customer and the facts assign the blame.

References

• Occupational Safety and Health Administration, 29 CFR 1910 and 1926, and the General Duty Clause, 29 U.S.C. 654(a)(1) (duty to address recognized hazards)
• International Residential Code (IRC) and applicable trade codes (NEC, IPC, IMC) for determining whether prior work is an actual code violation
• State contractor-licensing and consumer-protection statutes governing defective-work disclosure (varies by state; cite the applicable act)
• National Association of the Remodeling Industry (NARI), guidance on documenting and disclosing pre-existing defects