
Module 13 Checkpoint and Lab: Write the Handover
Where you are: Module 13 — Escalation, Communication and Documentation · Checkpoint · Based on Chapter 13 of Dr. Tahseen Al Doori's Troubleshooting Essentials.
Recap
Knowing when to stop is a troubleshooting skill. Escalate when safety, data or security is at risk (acting first to make things safe, stop using the device, or isolate and report), when the fix is beyond your authority or access, when the equipment is under warranty or contract, when theories are exhausted or the time limit has passed, and when many users or critical services are affected. Support is organised in tiers: Tier 0 self-help, Tier 1 help desk, Tier 2 technical support, Tier 3 specialists, Tier 4 vendors and providers. A complete handover has six parts so that the next person continues instead of starting again. Communicate in plain language, keep users informed and confirm the fix with them; record every incident with a consistent template so that records become a knowledge base.
Knowledge check
Which of these is NOT one of the escalation triggers listed in Chapter 13?
A user reports clicking a link in an email that asked them to confirm their password, and now sees unknown logins on their account. Which trigger applies, and where does it go?
Put the first three parts of the book's handover in order.
Who in the tiered model typically handles password resets, quick-win checks and logging tickets?
Ten tickets in two months record the same root cause in the same words. Which benefit of documentation does this show?
Answers explained
- b — Impatience calls for good communication, not escalation; warranty, scale and time limit are all on the book's list.
- c — Phishing and unknown logins are a security trigger; waiting, restoring data yourself or calling a manufacturer would all delay the people who need to act.
- d — The book's order is problem statement, exact evidence, start time and changes, then actions and results, urgency and scale, and contacts.
- c — Figure 13.1 lists those tasks for Tier 1; Tier 0 is self-help, Tier 2 deeper diagnosis, Tier 3 specialists.
- a — Consistent records reveal patterns; the other options contradict the book's guidance.
Lab: Write the Handover
This lab adapts the book's Chapter 13 review question 3: write a complete escalation handover for a printer that has failed after all basic checks.
Goal. Produce a handover that a Tier 2 technician could act on without contacting you, plus the user communication and the log entry that go with it.
Safe setup. This is a paper or simulated exercise. Do not open a printer, change printer or network settings, or touch shared equipment. If you have access to a training lab, your instructor may set up a real printer fault; otherwise use the scenario below.
Scenario (fictional). The second-floor network printer in an accounts office has printed nothing since about 09:40 today. Twelve staff use it, and month-end invoices must be posted by 16:00. The printer's display shows Service error. Call for service. You have carried out the Chapter 11 printer checks and the Chapter 5 quick wins:
| Action | Result |
|---|---|
| Checked power, paper, toner and jams | Power on, paper loaded, toner 60%, no jam |
| Restarted the printer | Same error returns after start-up |
| Cleared the print queue and restarted one PC | No change |
| Tried to print the printer's own test page | Fails with the same error |
| Asked what changed | The cleaners moved the printer to a different wall socket last night |
Steps.
- Decide which escalation trigger(s) apply and which tier should receive the problem. Note whether the printer is under a maintenance contract (state your assumption).
- Write the problem statement using the Chapter 4 template.
- Complete all six parts of the handover in the book's order.
- Write the message to the users (no more than four sentences) using the five communication principles.
- Fill in the Appendix B problem log fields that are known at the moment of escalation; mark the others "pending".
- Swap handovers with a classmate. Each of you lists every question you would still need to ask. The ideal number is zero.
What to record. The trigger and tier with a one-line justification; the handover; the user message; the partially completed log; your classmate's list of remaining questions.
Completion criteria.
- All six handover parts are present, in order, with every action paired with its result.
- The failed test page is recognised as evidence that the fault is in the printer itself, not the PCs or network (Chapter 11).
- The change (the move to a different socket) appears in the handover.
- No password or personal data appears anywhere.
- The user message sets a realistic expectation and contains no jargon or blame.
Safety. An error that tells you to call for service is a reason to stop. Do not open the printer: internal parts can be hot or electrically hazardous, and opening equipment under a maintenance contract may breach it.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §4.6, §5, §11.1, §13.1–13.5, Figure 13.1, Appendix B, Chapter 13 review questions
