How to Verify the Complaint Before You Start Work

Why this matters

The complaint on the work order was written by someone at a desk, from a phone call, hours or days ago. It may be vague, it may be wrong, it may have changed, and sometimes there is nothing wrong at all by the time you arrive. A tech who starts diagnosing the booked complaint without confirming it is real chases phantoms, replaces working parts, and generates the worst kind of callback: the one where nothing was ever broken. Verifying the complaint takes a few minutes and saves you from solving a problem that does not exist.

Step 1: Get the complaint in the customer's own words

The booked description is a translation. Get the original. Ask the customer to describe what is happening in their own words, and listen for the gap between what they say and what got written down. "No cooling" on the order can turn into "it cools, but one room stays warm," which is a completely different job. Do not diagnose the sentence on the work order. Diagnose what the customer actually experiences.

Step 2: Make it happen in front of you

A complaint you have not witnessed is a rumor. Reproduce it, or have the customer reproduce it while you watch:

• Ask them to show you, do the thing that triggers it, run the cycle that fails.
• Watch and listen for the actual symptom, not a description of it.
• If it hazards a real danger on reproduction, safety leads: at the first sign of a burning smell, sparking, gas odor, or water at a live circuit, stop the reproduction, make the hazard safe, and treat it as a hazard call before you go further.

Witnessing the failure yourself is the single most valuable thing you do before diagnosis. It tells you the symptom is real and shows you its exact shape.

Step 3: Rule out the non-failures

A large share of complaints are not equipment faults. Before you open anything, clear the cheap explanations:

• User error or a setting. A control in the wrong mode, a switch off, a schedule the customer forgot they set.
• A safety that did its job. A tripped device or a locked-out system may be protecting against a real fault, not failing. Do not just reset it and leave; find why it tripped.
• Already resolved. Intermittent problems sometimes clear before you arrive. That does not mean fixed; it means not currently reproducible.

Naming a non-failure honestly is not a lost job. It is the trust that brings them back.

Step 4: Confirm it is one complaint, not several

Customers stack problems into one call. "It's acting up" can be three separate issues wearing one description. Separate them now:

• Is the noise, the leak, and the poor performance one fault or three?
• Which one actually prompted the call, and which are they mentioning because you are here?

Sorting this before you start keeps you from fixing the minor issue and missing the one they care about.

Step 5: Pin the conditions

Nail down when and how the symptom shows, because that shapes your whole diagnosis:

• When did it start, and did anything change around then (weather, a prior repair, a new appliance)?
• Is it constant or intermittent? Intermittent means you are buying diagnosis time, and the customer should hear that now, not at the invoice.
• Does it depend on load, temperature, time of day, or a specific cycle?

Step 6: If you cannot reproduce it, say so and set the plan

Sometimes the fault will not show on your visit. Do not paper over that by replacing a likely suspect and calling it fixed, which is guessing dressed up as work. Tell the customer plainly: you could not reproduce it today, here is what you inspected, and here is the plan, whether that is monitoring, a data-logging step, or a return when it acts up. An honest "not reproducible, here is the next step" beats a confident repair of a fault you never confirmed.

The judgment to bank

You cannot fix what you have not confirmed. Verify the complaint is real, is what they said, and is currently present before you spend an hour and a part on it. The few minutes of verification are the cheapest insurance against a no-fault-found callback.

References

• Trade-standard diagnostic practice (confirm the symptom before component testing)
• OSHA guidance on recognizing hazards during equipment inspection (29 CFR 1910)
• See related: How to Diagnose Methodically Instead of Guessing; Recreating the Conditions to Find the Fault
• See related: How to Do a Walkthrough Before You Touch Anything