How to Hand Off an Unsolved Intermittent to the Next Visit

Why this matters

An intermittent you could not catch this visit is not a failure unless you leave nothing behind. The real waste is arriving next time and starting the hunt over, re-interviewing the customer, re-running the same eliminations, re-arming the same monitors, because none of this visit's work was set up to carry forward. A clean handoff of an unsolved intermittent means the next visit, yours or another tech's, picks up mid-hunt with the traps already set, not from scratch.

This is not a solved-job handoff

A solved job hands off an answer. An unsolved intermittent hands off a hunt in progress: what you have eliminated, what you suspect, what is watching for the fault while nobody is there, and what event should trigger the return. Set those up before you leave, or the next visit inherits nothing but the symptom you started with.

Step 1: Leave the monitoring armed and documented

The single most valuable thing you leave behind is a running trap. Arm what fits the fault: a data logger on the suspect parameter, a min-max meter left connected, a customer log sheet taped where the fault happens. Write down exactly what is deployed, where, what it is capturing, and when it needs checking or its battery runs out. An armed monitor nobody knows how to read is a wasted monitor.

Step 2: Record what you ruled out, with evidence

List every suspect you cleared this visit and how you cleared it: "supply confirmed at the terminals under load," "capacitor within spec hot and cold," "filter new and clean." Without this, the next tech re-runs your eliminations on the clock. The ruled-out list is what makes the second visit shorter than the first instead of a repeat of it.

Step 3: State the trigger hypothesis and the catch-plan

Write where you landed even though it is unconfirmed: the condition you think brings the fault on, heat, load, a specific cycle, weather, and how the next visit should catch it. Be there at that time, force that condition, or read the logger after the next event. A hypothesis paired with a plan to catch it hands the next tech a move, not a mystery to solve from the beginning.

Step 4: Brief the customer on their part

The customer is your eyes between visits. Show them once how to log an occurrence: the time, what was running, the conditions, and what the fault did. Ask them to call the moment it happens if catching it live is what matters. Tell them plainly that a fault they do not record is one you cannot fix, so the logging is the job right now, not a favor.

Step 5: Set the return trigger, not just "we will be back"

Tie the next visit to a condition, not a vague promise. The return fires when the logger catches an event, when the customer reports the next occurrence, when the predicted weather hits, or after a set observation window closes. Tell dispatch the trigger so the visit gets booked against the right moment, instead of a random slot where the fault will not show and the trip is wasted again.

Step 6: Set expectations so it does not read as failure

An unsolved intermittent frustrates a customer who expected one and done. Frame it straight: intermittents hide, catching them takes being present when they happen, and the monitoring is how you get there. A customer who understands the plan stays patient. One who thinks you gave up starts shopping for another shop, even though the diagnosis is going exactly as it should.

References

• Trade-standard practice for multi-visit diagnostic continuity and fault monitoring
• Manufacturer documentation for data-logging and captured-reading interpretation
• See related: How to Log an Intermittent Fault Over Days; How to Stage a Diagnosis When You Only Get One Visit