Verify the Fix Before You Pack Up

Why this matters

The five minutes between "I think it is fixed" and "I packed my tools" is where callbacks are won or lost. A repair that is electrically or mechanically correct can still fail under real load, or the customer's original complaint may not even be the thing you fixed. Verifying before you pack up is the cheapest quality control there is. It turns "it worked when I left" into "I watched it work, and so did the customer."

"Powered up" is not "verified"

The most common verification failure is mistaking a sign of life for proof of function. A unit that energizes, a light that comes on, a motor that spins for a second: none of that proves the system does its job under the conditions that made the customer call. Verification means the system performs the function the customer needs, at real operating load, observed by you. A furnace that lights is not a furnace that heats the house to setpoint and shuts off cleanly. Make the system do the actual job before you believe it.

Verify against the original complaint

You can fix a real problem and still leave the customer's problem in place, because you fixed something else. Always close the loop back to what they reported.

• Re-read the complaint in their words. "It leaks when the dishwasher runs," not "there was a leak."
• Reproduce the original trigger. Run the dishwasher, draw the load, cycle the thermostat, open the affected fixture.
• Confirm the symptom they described is gone under that exact trigger, not just that the part you touched now works.

If you cannot reproduce the original complaint at all, say so plainly and document it. An intermittent fault you could not reproduce is a real outcome, but the customer must know that is what happened.

Build a verification habit, every job

1. Restore everything to normal operating state. Covers on, power and supply restored, settings returned to where the customer keeps them. Verify the system as it will actually run, not in a half-disassembled test state.
2. Run a full cycle under real load. Not a tap of the switch. Let it complete a real operation start to finish.
3. Reproduce the original trigger and confirm the complaint is resolved.
4. Check your readings against spec. Where a measurable value exists (pressure, temperature, current, voltage, flow), confirm it lands in the expected range, not just that the unit runs. A unit running out of range is a future failure you can catch now.
5. Look for new problems you may have caused. Leaks at joints you opened, noises that were not there, anything you disturbed. (See the collateral-damage article.)
6. Watch it settle. Let it run long enough for a fault to reappear if it is going to. The fault that comes back two minutes in is one you want to see now, not on a return trip.

Test at real conditions, not bench conditions

A fault that only shows under heat, pressure, full flow, or a complete cycle will pass a quick poke test and fail in service. Push the system to the conditions where the complaint lives. If the problem was "no cooling on a hot afternoon," a thirty-second run in a mild morning proves little. Load it, heat it, fill it, or run it long enough to recreate the stress that exposed the fault. Verification under the wrong conditions is not verification.

Bring the customer into the verification

A demonstration the customer watches does two things. It proves the work, and it converts an anxious customer into a confident one. Show them the system doing its job. Briefly explain what you found and what you did. This heads off the nervous "I think it is still wrong" call that comes when a customer is left unsure, and it gives them a clear before-and-after in their own memory.

Document what you verified

Record the readings you took, the cycle you ran, and the fact that the original complaint was reproduced and resolved (or could not be reproduced). This protects you if the issue returns for a different reason, gives the next tech a baseline, and turns the verification into a permanent part of the job record. (In Manuall, the job notes and equipment record are the place for these readings.)

Common mistakes

• Calling "it turned on" a passing test.
• Verifying the part you replaced instead of the complaint the customer reported.
• Testing in mild conditions a fault that only appears under load.
• Packing up before the system has run long enough to resurface an intermittent fault.
• Leaving without showing the customer it works.

References

• Manufacturer commissioning and startup documentation, which defines the post-repair checks and target readings for the equipment.
• Trade-standard practice for functional testing and closeout.
• See related: Universal, The Operational Test After a Repair; Universal, Did I Fix It or Just Mask It.