Scope a Repair vs Recommend Replacement Decision Tree

Why this matters

The repair-or-replace call is where a tech earns trust or burns it. Recommend a replacement on a unit with years of life left and you look like you are padding the ticket. Patch a piece of failing equipment and the customer pays you twice when it dies a month later, and the callback is on your reputation. This is a scoping decision, made before you write the price, not a sales pitch. The honest answer is sometimes the cheaper one, and saying so is exactly what earns the next job. Walk the diagnosis in order so the recommendation is defensible.

Start here: can it even be repaired safely and to code?

Some failures take the choice off the table.

• If the part is obsolete and unavailable, or the repair would leave the system out of current code, repair is not really on the menu. Replacement is the answer; explain why.
• If repairing it would be unsafe (a cracked heat exchanger, compromised structure, a corroded gas or pressure component), do not scope the repair at all. Document the safety reason.
• If it can be repaired safely and legally, continue down the tree.

Get this gate out of the way first. It prevents you from pricing a repair you should never offer.

Check the age against the expected service life

Every system has a rough expected service life. Compare where this unit sits on that curve.

• Early life, isolated failure: repair. A young system with one bad component is a repair almost every time.
• Past the typical service life: replacement moves to the front, especially if the failure is a major component rather than a wear item.
• In the gray middle: keep going; age alone does not decide it.

Know the rough life expectancy for the equipment you service. A repair that buys a year on something with one year left is a different recommendation than the same repair on something with ten years left.

Weigh the repair cost against replacement value

Compare what the fix costs against what a new unit costs and how long each buys.

• If the repair is a small fraction of replacement and restores full life, repair wins clearly.
• If the repair approaches a large share of replacement value and the rest of the unit is aging, replacement is usually the better spend for the customer even though it is the bigger ticket today.
• A repair that only buys a short stretch before the next predictable failure is often a poor value. Say so.

Frame it in payback, not just price: what each option costs and how long it lasts. That is the comparison the customer actually needs.

Read the failure pattern, not just the failed part

One repair is data. A pattern is a verdict.

• First failure, otherwise sound system: repair.
• Repeat failures, multiple components going, or one fix exposing the next weak link: the system is telling you it is at end of life. Stacking repairs on a failing unit is throwing good money after bad.
• Cascade risk, where this failure likely damaged or stressed other parts, pushes toward replacement.

If you have history on the unit, use it. Two service calls in a short window changes the recommendation.

Comparison: which way the factors point

When to give the customer both and let them choose

When the factors are genuinely mixed, do not decide for them. Scope both: a clean repair price and a replacement price, each with its honest payback and risk. Tell them what you would do and why, then let them choose. Document both options on the estimate so the decision and your advice are on record. The customer who picks the repair against your replacement advice has it in writing, and so do you.

References

• Manufacturer documentation: published service-life and repair-limitation guidance for the equipment class
• Trade-standard practice on repair-versus-replace thresholds and life-cycle costing
• Consumer-protection guidance on honest disclosure of repair options
• See related: Assessing an Old or Non-Standard System; The Second Look Before You Commit the Price