Customer Undid My Prior Fix, Now Faults Decision Tree

Why this matters

You return to a site and find the system faulting. You also find that the work you did last visit has been altered: a setting changed, a part adjusted, a switch repositioned, a thermostat moved, a configuration overwritten. The customer says "we did not touch anything." The evidence says otherwise. This decision tree gives you a way to confirm whether the prior fix was undone, identify the scope of what changed, and decide how to handle the call commercially and technically.

This pattern is common across every trade. It is not a callback in the warranty sense. It is a new condition created by a change made after you left. Distinguishing the two protects your reputation, your callback statistics, and your time.

Symptom presentation

• Thermostat that was reprogrammed has reverted to factory settings or different programming
• A balancing damper you set to a specific position is in a different position
• A water heater dial moved from your set point
• A safety lockout reset (or jumpered) that you specifically warned against
• A breaker switched off then back on
• A panel cover replaced incorrectly so a safety microswitch no longer engages
• A control board parameter that you configured has different values
• A part you replaced has been replaced again with a different (often wrong) part

The fault may or may not be a direct result of the change. Establish both.

Quick checks

1. Compare current state to your documented state from the prior visit. If you did not document, you cannot prove the change. (Lesson for next time: photograph and write down what you leave the system in.)
2. Ask the customer who has had access since the last visit. Tenants, family members, cleaners, other service providers, building staff, alarm-system installers, internet techs. Often the customer is not lying; another party touched it.
3. Identify what specifically is different. A thermostat schedule that was changed is different from a thermostat that was replaced; both look "wrong" but the diagnostic implications are different.
4. Determine whether the change caused the current fault, or whether the fault is independent and the change is just an additional finding.
5. Read the panel for fault history. Fault timestamps may correlate with the change event.

Decision tree

Branch A: Change directly caused the current fault

Examples: thermostat is wired to wrong terminals after a DIY thermostat swap; balancing damper closed off blocking critical airflow; settings reverted such that anti-short-cycle is now disabled and compressor is short-cycling; safety device was bypassed and the protected fault has now occurred.

In this case: restore the prior configuration, verify operation, document what was found and what was restored. Discuss with the customer that the change caused the fault. This is a billable call, not a warranty callback. Be clear, calm, and factual about what you found.

Branch B: Change did not cause the current fault, but did create a separate problem

Example: prior fix is intact, but a different component has now failed independently. The change you found is unrelated to the current fault but should still be noted (and restored if appropriate).

In this case: handle the current fault on its merits, restore or note the change separately, document both. This is a new service call.

Branch C: Cannot determine whether change caused the fault

Example: settings have been altered, the unit is faulting, the relationship is unclear. The change might have triggered the fault, exposed an underlying condition, or be coincidental.

In this case: restore the prior configuration first, observe whether the fault clears. If it does, the change caused the fault. If it does not, the fault has another cause that you now have to diagnose with the system in a clean state.

Branch D: Documented warranty issue, the change did not cause it

If your prior repair has truly failed and the change is irrelevant, honor the work. Replacing a contactor that you installed two weeks ago and that has now failed is your work to make right regardless of whatever else the customer may have touched.

Confirming the determination

Photograph the current state before you change anything. The photograph is your record that the change was present when you arrived. Customers occasionally claim the technician created the change; the photograph forecloses that argument.

If you have access to the system's configuration log (most modern panels carry a parameter change log with timestamps and source), pull it. It will tell you when and from where the change was made. Local panel, network, mobile app, building automation system, each leaves a different trace.

Next steps

When you restore the prior configuration, write what you found and what you restored. Tell the customer what was changed and why it matters. If the customer disputes that they made the change, that does not change your work; document and proceed.

For commercial accounts, route the finding to the account manager or building owner if the changes were made by an unauthorized party. The owner has a right to know that another contractor or party has been altering their equipment.

Going forward: at every visit, leave a written tag, sticker, or service note on the equipment showing the date, the technician's initials, and any critical parameter (setpoint, position, switch state). The tag is a powerful deterrent against undocumented changes and a record if a change is made anyway.

References

• ISO 13379-1 Condition monitoring and diagnostics of machines, data interpretation
• NFPA 70B Recommended Practice for Electrical Equipment Maintenance, documentation requirements
• OSHA 29 CFR 1910.147 Control of hazardous energy (defeated safety device documentation)
• ACCA Standard 4 Maintenance of Residential HVAC Systems, service documentation
• NARI Member Code of Ethics, scope and documentation requirements for service work