A Prior Patch Is Masking the Symptom: Decision Tree

Why this matters

A patch that suppresses a symptom lets a fault keep growing in the dark. The equipment "works," so nobody worries, while the real problem advances toward a bigger failure. When you arrive on a system that runs but you suspect a patch, your job is to expose the masked fault and measure how far it has already progressed, before it fails on its own terms and takes more with it. This tree walks the exposure in order, safest and simplest first.

Start here: could exposing the fault release a hazard?

Before you remove or defeat a patch to see what is behind it, ask what the patch is holding back.

If removing the patch could release stored energy, pressure, water onto live electrical, or fuel gas - a capped relief, a clamped high-pressure line, a bypass on a fuel or electrical safety - stop and control it first: isolate and lock out the energy source, close the upstream shutoff and relieve pressure, or shut and cap the fuel before you disturb the patch. Do not "just crack it and watch." A masked fault at full strength is exactly what the patch was hiding, and it can come out fast.

If exposure is low-hazard, proceed to expose and measure.

Identify the patch and what signal it suppresses

Find the compensation and name the signal it is eating:

• A booster, assist, or override suppresses a low-output signal.
• A cap, clamp, or plug suppresses a leak or a pressure symptom.
• A defeated sensor or jumper suppresses an alarm or a lockout.

You cannot measure a fault whose signal is being eaten. First, know what is being eaten.

Restore the true signal, then measure the fault

Now get a real reading of the masked fault:

• Where safe, take the patch out of the loop (turn off the booster, remove the override, restore the sensor) and let the system show its true behavior.
• Measure how far the fault has progressed. A leak that was clamped for a season may have corroded the surrounding metal. A compressor that was assist-started for a year is likely weaker now than when the assist went on. The patch bought time, and that time has a cost you need to quantify.

Decide: expose now, or stabilize and schedule

Not every masked fault gets torn into on the spot.

• Expose and fix now if the fault is advancing fast, is a safety issue, or the patch is failing.
• Stabilize and schedule if the system is safely holding on the patch and the customer needs time to approve the real repair, but only after you have measured the fault and told them plainly what the clock looks like. Leaving a patch in place is a decision you make with the customer, in writing, not a default you fall into.

Never re-mask. Replacing a crude suppression with a cleaner one, without measuring or disclosing the fault, just resets the same trap for the next tech.

Recap the order

1. Safety first. If exposing the fault could release a hazard, isolate, depressurize, or shut off fuel before disturbing the patch.
2. Identify the patch and the signal it suppresses.
3. Restore the true signal and measure how far the fault has progressed.
4. Decide with the customer: fix now, or stabilize and schedule, in writing.
5. Never simply re-mask.

A masked symptom is a fault on a delay timer. Expose it, measure it, and put a real decision in front of the customer before it goes off.

References

• OSHA control of hazardous energy (29 CFR 1910.147); relieve pressure and de-energize before disturbing a patched safety
• Trade-standard practice on quantifying progressive damage from a deferred repair
• See related: Seeing Past a Stopgap to the Underlying Problem; The Temporary Fix Someone Left in Place