Reading the Prior Work: Good or Bad

Why this matters

Almost nothing you service is brand new and untouched. Someone worked on it before you, and how they worked on it tells you what you are walking into. Prior work that was done right makes your job predictable. Prior work that was done wrong hides problems, fails in the middle of your job, and gets blamed on you if you did not flag it first. Learning to read the previous hand is one of the fastest ways to scope accurately.

Why the previous work changes your scope

When you take over a system, structure, or installation, you inherit everything the last person did. If they cut a corner, that corner is now your problem the moment you touch it. If they did clean, code-compliant work, you can build on it with confidence. Either way, you need to read it before you price, because the condition of the prior work decides how much of your time goes to fixing their mistakes versus doing the job in front of you.

Signs of solid prior work

Good work has a look and a logic to it. Look for:

• Neat, consistent connections. Fasteners driven straight, joints sealed evenly, runs that go in clean lines rather than wandering.
• Correct materials for the job. The right gauge, rating, or grade for the application, not whatever was in the truck.
• Labeling and order. Things marked, organized, and accessible. Someone who labels expects another tradesperson to come behind them.
• Code-compliant choices. Proper supports, correct clearances, no obvious shortcuts around the rules.

When you see this, your scope gets simpler. You can trust the foundation and quote the actual task.

Signs of trouble you are about to inherit

Bad work also has tells. When you spot these, your scope grows because you cannot safely build on a broken base.

Each of these adds time, and time you do not see is the time that blows up your quote.

The "why is it like this" habit

When something looks wrong, ask why before you assume. Sometimes ugly work is a clever fix for a real constraint you have not noticed yet. Sometimes a strange choice was forced by the building. But more often, wrong work is just wrong, and it will fail in the middle of your job. Pause long enough to decide which one you are looking at. That judgment is the skill.

If the prior work defeated a safety device or violated code, that is not a judgment call. Flag it, document it, and tell the customer it has to be corrected. You do not want to be the last name on a system that someone tampered with.

How to put it in the quote

Reading prior work only protects you if it shows up in the scope. When you find bad work that affects the job:

• Name it specifically. "Existing connection is undersized and must be replaced before proceeding," not "things look rough."
• Separate it from the main scope. The customer should see the difference between the job they called about and the correction the prior work forced.
• Tie it to your conditions clause. "Assumes existing work is sound" plus a documented exception is how you avoid eating someone else's mistake.

A customer who hears "the last person who worked on this left a problem, here is what it will take to make it right" respects the honesty, especially when you can point at it and show them.

Protect yourself on the documentation

Photograph the prior condition before you touch anything. If you take over a system and it later fails at a spot the previous tradesperson worked, your photo proves the condition you inherited. Without it, the failure becomes your word against theirs, and the customer's memory will favor whoever is standing in front of them. The record is cheap. The blame for someone else's work is not.

References

• Trade-standard practice for assessing existing installations
• NFPA and applicable code references for identifying non-compliant prior work
• See related: Locate the Utilities and Shutoffs First
• See related: The Photo and Note Scope Record