A Different Tech From Your Shop Did the First Visit: Decision Tree

Why this matters

You pull up to a callback and the first visit was not yours, it was a coworker's. Now you are carrying their work and the customer is watching to see if the shop is one team or a bag of individuals. Handle this well and you protect the customer, the coworker, and the company's name at once. Handle it wrong, by trashing the last tech or by hiding a real mistake, and you damage all three. This tree keeps you fair to everyone while you fix the machine.

Safety first

If you arrive to a live hazard - gas smell, burning odor, water at an energized part, a scorched or arcing component - make it safe before anything else: clear people, shut off gas or water, de-energize and verify dead. A coworker's miss that left a hazard gets corrected immediately and documented plainly, not softened to protect a feeling. Safety outranks shop politics every time.

Start here: get the first-visit record before you touch anything

You cannot judge the first visit without knowing what it was. Pull the work order, notes, photos, and readings the first tech left.

If the notes are complete - what they found, what they did, what they left it reading - you can diagnose against a baseline. Go to "Diagnose against their baseline."

If the notes are thin or missing, do not guess what they did. Call the tech if you reasonably can, or treat the machine as an unknown and diagnose from scratch. Note the gap for the shop; missing documentation is the real problem to fix, separate from today's repair.

Diagnose against their baseline

Run the fault fresh, then compare to what the first tech recorded. You are looking for which of a few cases you are in.

• The repair was right but incomplete (a valve left half open, air not purged, a setting not restored). Finish it. This is a normal handoff gap, not a character flaw.
• The diagnosis was wrong (they replaced a good part, missed the real cause). Correct it, and capture what the actual cause was so the tech and the shop learn from it.
• A new or separate fault appeared. Confirm it is not tied to their work, then handle it as new work. See the related article on separating a failed repair from a new problem.
• You cannot beat their diagnosis either and the fault is genuinely hard. Loop the first tech in rather than flailing. Two heads on a stubborn fault beats ego.

Decide: proceed solo, or loop the first tech in

Not every coworker callback should be handled silently by whoever got dispatched.

• Proceed solo when the fix is clear, within your skill, and the notes give you what you need. Just fix it and report back cleanly.
• Call the first tech when the notes are unclear, when what you are finding contradicts theirs in a way you cannot explain, or when the fix touches something they set up deliberately. A thirty-second call prevents you from undoing a choice that had a reason.
• Escalate to a lead or owner when you find a pattern (this tech's callbacks keep landing on you) or a serious workmanship or safety issue. That is a management conversation, not a truck-to-truck one.

What to tell the customer about a coworker

The customer does not need to hear the shop's internal business, and they must not hear you throw a coworker under the truck.

• Present one shop, not two techs. "Let me see what we did last time and get this sorted" beats "wow, whoever was here before really missed this."
• Own it as the company. If it was a genuine miss, "we did not get this fully resolved last visit and we are going to make it right" carries the same accountability without naming and shaming.
• Never speculate about blame in front of them. You often do not have the full story, and a customer who hears you bad-mouth a coworker assumes you will bad-mouth them too.

Close the loop with the tech and the shop

The callback is not done when the machine runs. Feed back what you found so the first tech gets better and the shop catches patterns.

• Tell the tech directly and privately what you found, as information, not an ambush.
• Update the job record with the real cause and the corrected fix.
• Flag documentation gaps or recurring issues to whoever owns quality.

Ordered recap

1. Make any hazard safe first.
2. Pull the first tech's notes before diagnosing.
3. Diagnose fresh, compare to their baseline, name which case you are in.
4. Decide solo vs call the tech vs escalate.
5. Present one shop to the customer; never trash a coworker.
6. Feed the real cause back to the tech and the record.

References

• Trade-standard practice for team callbacks and workmanship review
• See related: Taking Over a Comeback on a Coworker's Work; Separating a Failed Repair From an Unrelated New Problem
• See related: The Conversation That Keeps a Comeback From Losing the Customer