Bring in a Third Opinion, or Decide Between Two: Decision Tree
Why this matters
When two techs are stuck between competing diagnoses, pulling in a third person feels like the safe move, and sometimes it is. But it costs time, it can read to the customer as the shop being unsure of itself, and a third opinion does not automatically settle anything if it just becomes a two-against-one vote rather than new evidence. Knowing when a third opinion actually adds information, versus when it just adds a person, is the skill worth having.
Start here: what would a third person actually add
Before calling anyone in, ask a concrete question: what specific thing does a third opinion bring that the first two don't already have? If the honest answer is "someone to break the tie," that is usually the wrong reason to escalate, because a tie broken by headcount is not more likely to be correct than a tie broken by seniority. If the honest answer is "different equipment, different experience with this specific fault type, or a fresh set of eyes on evidence we might be reading wrong," that is a real reason.
Decide using what's actually unresolved
| What's actually unresolved | Best move |
|---|---|
| Neither tech has run the specific test that would settle it | Run that test before calling anyone. This is not a disagreement yet, it's incomplete diagnosis |
| Both have run every test available in the truck and still disagree | A third opinion, ideally from someone with relevant specialty experience or better equipment, is now genuinely useful |
| The disagreement is really about repair-versus-replace judgment, not the fault itself | A third technical opinion won't help; this needs a business judgment call, often the customer's own choice with both options honestly presented |
| The fault type is rare or outside what either tech has seen before | A manufacturer technical line or a specialist is worth more than a third generalist opinion |
| One tech is clearly reasoning from confirmed evidence and the other from a hunch | This isn't actually a tie; weigh the evidence, don't escalate to break a false tie |
If you decide to bring in a third opinion
- Give the third person the evidence, not the argument. Hand over what was tested and found, not a summary of who thinks what. Let them form their own read before hearing either original opinion, so they are not anchored to an existing side.
- Ask for their reasoning, not just their verdict. "I think it's X" is less useful than "I think it's X because of this specific finding," because the reasoning is what lets the other two techs evaluate whether the third opinion actually resolves the open question or just adds a third guess.
- If the third opinion still doesn't clearly settle it, you likely need a different kind of input entirely (specialized equipment, manufacturer support, a longer observation period) rather than a fourth person's opinion.
If you decide two is enough and it's time to just decide
- Name explicitly which factor is deciding it: the stronger evidence, the theory that explains more of the symptoms, or a business judgment where the customer gets an honest choice. Do not let it default to seniority without saying so.
- Run the fix, but flag the discarded theory in the file in case the fix does not hold. See the related article on documenting competing diagnoses.
- If the fix doesn't hold, go back to the discarded theory first, not back to square one. The value of having weighed two theories originally is that you already have a second, evidence-informed place to look.
Recap
Ask what a third opinion would actually add before calling anyone in. If the open question is a specific untested possibility, test it first. If it's genuinely exhausted the available evidence, a relevant specialist beats a generic third opinion. If the disagreement is really about business judgment, not the fault, that's a customer decision, not a technical vote. Either way, decide out loud on a named reason and document the path not taken.
References
- Internal quality-control practice: structured escalation criteria for unresolved technical disputes
- Trade-standard practice for manufacturer technical support escalation
- See related: Escalating a Diagnostic Disagreement Without Damaging Morale; When Two Technicians Genuinely Disagree