Deciding Whether to Undo an Undocumented Modification or Work Around It

Why this matters

Once you've found and assessed an undocumented modification, you face a real decision with real consequences either way: restore the system to factory-documented configuration, or leave the modification in place and work around it. Undo the wrong one and you can reintroduce whatever problem the original installer was actually solving. Leave the wrong one in place and you can hand the customer a system that looks fixed today and fails again on a predictable timeline. This is the framework for making that call deliberately instead of by default.

The default should lean toward restoring documented configuration

Manufacturer-documented configuration exists because it was engineered, tested, and rated as a system. An undocumented field modification, even a clever one, was made by one person under field conditions without that same testing. All else equal, restoring the documented configuration is the safer default and the one that best protects you if anything goes wrong later, since you can point to following the manufacturer's design rather than defending someone else's improvisation.

When working around it (leaving it in place) is the better call

There are legitimate cases where undoing the modification is worse than living with it:

• The modification solves a real, still-present problem that the factory configuration does not account for. If undoing it would simply reintroduce the original failure (a genuine access constraint, an environmental condition the factory design didn't anticipate, a load or usage pattern the original design predates), removing it without also solving the underlying problem just restores the original complaint.
• The modification is structurally significant and undoing it introduces new risk. If reversing a modification means disturbing something load-bearing, pressurized, or otherwise risky to undo casually, and the modification itself is currently safe and functioning, the safer move can be to leave it and document it rather than create a new failure point trying to "fix" something that wasn't actively broken.
• The scope and cost of restoring it is disproportionate to the actual problem you were called for, and the modification is confirmed safe and unrelated to today's complaint. Forcing a full restoration as a condition of doing today's repair, when the modification is a stable, safe, unrelated finding, can be scope creep dressed up as thoroughness.

When undoing it is the right call, even if it's more work

• The modification is, or has become, the actual cause of the current complaint. Working around a modification that is the root cause just delays the same failure.
• The modification bypasses a safety or protective function. This is close to non-negotiable; see the safety-issue decision tree. A workaround here is not a workaround, it's leaving a hazard in place with your name on the visit.
• The modification will actively conflict with the repair you were called to do. If proceeding with the intended fix requires the factory configuration to function correctly, and the modification prevents that, you cannot genuinely "work around" it, you have to address it directly.

Present the decision to the customer as a choice, with the tradeoffs stated plainly

This is not purely a technical call, it often has a cost and scope dimension the customer should weigh in on, especially when either option is legitimate. State it plainly: "There's a modification here that isn't standard. I can leave it and work around it, here's what that means going forward, or I can restore it to factory spec, here's what that involves." Let them choose with the tradeoffs in front of them rather than deciding unilaterally on a borderline call.

Document whichever way you go

Whatever you decide, the same rule applies: write down what the modification was, what you found when assessing it, and which option you chose and why. This is the record that protects the next tech, the customer, and you, regardless of which direction the decision went.

References

• Manufacturer documentation for the equipment's rated, tested configuration
• Trade-standard practice for scope-of-repair documentation and customer authorization
• See related: Discovering an Undocumented Modification Mid-Diagnosis; The Modification Looks Like the Cause But You're Not Certain (decision tree)