Suspected Prior DIY Work: Proceed vs Disclaim vs Decline Decision Tree

Why this matters

A tech opens up a job and finds prior work that was clearly not done by a professional: non-code wiring, improvised plumbing, a part rigged in, missing permits, hidden modifications. The question is immediate. Do you proceed and absorb whatever that prior work brings, proceed only after disclaiming responsibility for it in writing, or decline the job until the unsafe or non-conforming prior work is corrected? Get it wrong by proceeding silently and you may inherit liability for a condition you did not create. Decline reflexively on every imperfect prior job and you turn away most of the existing-home market. The branch depends on whether the prior work is unsafe, whether it is in your work path, and whether it blocks a code-compliant result.

The core risk is "you touched it last." Once you work on a system, a later failure can be attributed to you even if a prior DIY defect caused it. The decision tree manages that exposure: it routes genuinely dangerous conditions to decline-or-correct, isolates merely-ugly-but-safe conditions with a disclaimer, and lets you proceed cleanly where the prior work does not affect your scope.

The situation

During a job, a tech discovers prior work that appears to be unpermitted, non-code, or amateur. Before continuing, the tech and dispatcher decide whether to proceed, proceed with a written disclaimer, or decline pending correction. The decision must protect the company from inheriting liability while not abandoning a customer over cosmetic-only prior work.

Quick checks

• Is the prior work a present safety hazard? Energized, leaking, backfed, structurally compromised. If yes, the safety protocol runs first.
• Is the prior work in the path of your scope? Will you connect to it, build on it, or rely on it? Or is it elsewhere and untouched by your job?
• Does the prior work block a code-compliant or warrantable result for your work? Can you do your job correctly with that condition present, or does it force you to either bless the bad work or fail an inspection?

Decision tree

Start: Is the prior work an immediate safety hazard?

• Yes. Run the unsafe-condition protocol first (make safe, notify, document). Then: the job cannot proceed normally until the hazard is corrected. Quote the correction or refer it; do not conceal it. This collapses to a decline-pending-correction on the affected portion.

• No immediate hazard. Go to: Is the suspect prior work in the path of your scope?

  • No, it is unrelated and untouched by your work. Proceed with your scope. Document that you observed the prior work, photographed it, noted it is outside your scope, and are not responsible for it. You do not have to fix the world; you do have to record that you saw it and did not touch it, so a later problem there is not pinned on you.

  • Yes, your work connects to or relies on the prior work. Go to: Can you produce a code-compliant, warrantable result with the prior work in place?

    • Yes, the prior work is non-ideal but safe and does not prevent a compliant result for your scope. Proceed with a written disclaimer. Complete your work to code, and document explicitly that pre-existing conditions outside your scope exist, were disclosed to the customer, and are excluded from your warranty. Warrant your work, not theirs. Get the customer's acknowledgment of the disclaimer.

    • No, the prior work forces a non-compliant result, blocks inspection, or would make you appear to certify the bad work. Decline to proceed as-is. Present the customer two paths: correct the prior work first (quote it), then complete your scope on a sound base; or limit your scope to what can be done compliantly and exclude the rest in writing. Do not connect new work to a non-conforming base and call it done; that puts your name on the violation.

Confirming the right call

• The customer has been told, in plain language, what prior condition was found and what it means for the job.
• Photos of the prior work are on the record before you touched anything.
• If proceeding with a disclaimer, the disclaimer is specific (names the condition and the exclusion), not boilerplate, and is acknowledged.
• If declining or limiting scope, the alternative (correct-first or reduced-scope) is offered, not just a refusal.
• Nothing unsafe or non-conforming is left concealed behind your finished work.

Remediation: protecting the company while serving the customer

• Write disclaimers that name the specific pre-existing condition and the specific exclusion; generic "as-is" language is weak.
• Quote corrections separately so the customer sees the path to a fully sound result.
• Never re-cover, re-close, or finish over a hidden defect without disclosing it; concealment converts a prior party's defect into your liability.
• When a permit/inspection is involved, flag unpermitted prior work to the customer; you cannot certify what was never inspected.
• Tag the job so a future visit starts with the known prior-work condition.

References

• National Electrical Code (NFPA 70), International Plumbing Code, and International Residential Code provisions requiring that altered or extended work meet current code and that unsafe existing conditions affecting the work be addressed.
• Uniform Commercial Code Article 2, ss 2-316 (disclaimer of implied warranties) and common-law principles on liability for work performed on a defective existing system.
• OSHA General Duty Clause, 29 U.S.C. ss 654(a)(1), for the safety obligations triggered when prior work creates a recognized hazard.
• State contractor-licensing and permit statutes governing the obligation to disclose unpermitted prior work and the limits of working on non-conforming existing installations.