The Professional Escalation Handover
Where you are: Module 13 — Escalation, Communication and Documentation · Lesson 13.2 · Based on Chapter 13 (§13.3) of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What you'll be able to do
- List the six parts of a complete escalation handover in the book's order.
- Write a handover that lets the next technician continue instead of starting again.
- Explain, using an example, how a complete record shortens the time to resolution at the next tier.
Watch: The Professional Escalation Handover
The video follows a simulated incident: a sales team that suddenly cannot open its shared folder. You see the Tier 1 technician's tests, the handover record they write, and how a server specialist uses that record to find the cause in minutes. As you watch, ask yourself:
- Which part of the handover stops the specialist from repeating work?
- What would have happened if the handover had said only "shared drive broken"?
- Which of the seven steps does the specialist start from, and why not Step 1?
Why the handover matters
When a problem moves from one person to another, knowledge can be lost at the boundary. The user has to explain everything again; the next technician repeats checks that were already done; evidence such as an error message disappears when someone restarts the device. Chapter 13 states the purpose of a good handover: it lets the next person continue from where the previous one stopped, instead of starting again.
That makes the handover the most practical expression of the seventh principle from Chapter 2, write it down. If you have kept notes throughout the seven steps, the handover is mostly already written.
The six parts of a complete handover
The book lists six things a handover should include. Keep them in this order:
The problem statement
One or two sentences built with the Chapter 4 template: since when, who, cannot what, on where, how often, the most recent change, and the exact error.
Exact evidence
Error messages word for word, plus screenshots and photographs, including any error codes.
Start time and changes
When the problem started and what changed beforehand: updates, moves, new staff, power cuts, configuration work.
Every action and its result
Each test or change you made and what happened, including the ones that did not help.
Urgency and scale
How urgent it is and how many users are affected, so the next tier can prioritise.
Contacts and availability
How to reach the user and you, and when each of you is available.
Part 4 is the one most often skimped, and it is the one that saves the most time. A rejected theory is valuable information: it tells the next person where not to look. Recording "restarted the laptop: no change" is just as important as recording a success.
Never put passwords in a handover, and never ask a user to tell you theirs so you can pass it on. If the next tier needs access, they use the organisation's approved process. Treat screenshots carefully too: crop out personal or confidential information that the next technician does not need.
Weak and complete handovers compared
| Weak note | Complete handover |
|---|---|
| "Shared drive broken, please fix." | A problem statement with time, scope, location and exact error |
| No evidence attached | Screenshot of the error message |
| No history | The start time and the change that happened shortly before |
| Nothing about what was tried | Three theories, each with its test and result |
| No sense of urgency | Six users affected, quote deadline this afternoon |
| "Call me" | User and technician extensions, with times available |
With the weak note, the next technician must phone the user, rebuild the history and re-run every basic check before doing anything new. With the complete handover they can go straight to the next untested theory.
Worked example
(Fictional scenario.) At 10:15 on a Tuesday, a member of the sales team reports that they cannot open the shared Sales folder on the file server. The Tier 1 technician works through the method.
Identify. Six sales staff are affected; the rest of the company can open their own shared folders. The error is Access is denied. The technician asks what changed and learns that the server team carried out planned maintenance on the file server at 10:00.
Theory and test (the Step 2–3 loop).
| Theory | Test | Result |
|---|---|---|
| A problem with one user's account | Ask a second sales user to try | Also denied: rejected |
| The network or drive mapping | Open another folder on the same server | Opens normally: rejected |
| The folder's permissions were changed | Needs administrator access to the server | Cannot test at Tier 1: escalate |
The third theory is beyond Tier 1's authority and access, so the technician escalates to a Tier 3 server specialist with this handover:
- Problem statement: Since 10:15 today, the six members of the sales team cannot open the Sales shared folder on the file server. It happens every time they try. The most recent change was planned maintenance on the server at 10:00. The error shown is "Access is denied."
- Evidence: screenshot of the error, taken on two different sales laptops.
- Started and changed: first report 10:15; server maintenance 10:00.
- Actions and results: second user tested, also denied; another folder on the same server opens normally; no changes made by Tier 1.
- Urgency and scale: six users, all of the sales team; a customer quote is due at 15:00.
- Contacts: reporting user on extension 2141 until 17:00; Tier 1 technician on extension 2007.
How the specialist continues. The specialist reads the record at 11:05. Because Part 4 shows that accounts and the network have already been ruled out, they do not re-test them. Because Part 3 mentions the maintenance, they check the change record and see that a permissions clean-up was made on the Sales folder. Within minutes they confirm that the sales team's group is no longer listed on the folder's permissions. That is theory 3, confirmed.
The specialist plans the fix (restore the group's previous permission, which is recorded in the change record), implements it, and asks two sales users to verify that the folder opens. Both confirm, and the ticket is documented with the cause and fix. As a preventive measure, the server team adds "check access for affected groups" to their maintenance checklist.
Total time from escalation to fix: under half an hour, because nobody started again.
Try it
Use a paper or simulated scenario only: do not change permissions or settings on a real system.
Take this situation (fictional): since 14:00, a user's laptop shows No internet on Wi-Fi in the library, while their phone works on the same network. You have restarted the laptop (no change), forgotten and rejoined the network (no change) and run ipconfig, which shows an address beginning 169.254. Your shift ends at 16:00.
Write a six-part handover to Tier 2.
Completion criteria: all six parts present and in order; the problem statement follows the Chapter 4 template; every action has a result; no password appears anywhere; a classmate could start work from your handover without asking you a single question.
Knowledge check
Which handover part most directly stops the next technician repeating tests you already ran?
According to Chapter 13, what is the main purpose of a good handover?
In the worked example, why did the specialist check the server's change record first?
A user offers to tell you their password so that Tier 2 can log in as them. What should you do?
Answers explained
- b — Recorded actions and results show what has been ruled out; urgency, contacts and start time are needed but do not prevent repeated tests.
- c — The book defines the purpose as continuation, not proof of effort or a transfer that lets someone close the ticket.
- a — The recorded change pointed straight at the likely cause; checking change history is good practice, but here it was the handover that directed the specialist.
- d — Passwords are never shared during troubleshooting (Chapter 10); every other option still exposes the credential.
Key takeaways
- A handover exists so that the next person continues instead of starting again.
- Six parts, in order: problem statement, exact evidence, start time and changes, every action and result, urgency and scale, contacts and availability.
- Rejected theories are evidence: record them.
- A complete record lets the next tier begin at the next untested theory, which is why handovers save time and money.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §2.2, §4.6, §10.4, §12.4, §13.3
