
Capstone 2: Root Cause and Professional Handover
Where you are: Module 14 — Case Studies and Final Assessment · Capstone 2: Root Cause and Professional Handover · Draws on Chapters 4, 5, 6, 12 and 13 of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What this capstone asks you to do
Capstone 1 asked you to solve one incident. This capstone asks a harder, more professional question: why does the same incident keep coming back, and what will stop it? You will analyse a history of recurring occurrences, find the root cause with the 5 Whys and a fishbone diagram, choose preventive measures, decide what must be escalated, write a complete handover for the people who will carry out the work, and explain it all to the people affected.
By the end you will have shown that you can:
- find a pattern in a log of recurring occurrences, and separate workarounds from fixes;
- apply the 5 Whys and the fishbone (Ishikawa) diagram, and write a precise root cause statement;
- select and justify preventive measures that act on the root cause;
- decide when and to whom to escalate, and prepare a six-part handover that lets the next person continue without starting again;
- communicate clearly, honestly and without jargon or blame.
Allow 4 to 6 hours.
The situation
(Fictional scenario.) Rosemount Veterinary Clinic is a small practice with two vets, three nurses and two receptionists. Reception and the nurses use six Windows laptops to run the clinic's practice management system, a cloud web application reached through a secure (HTTPS) website, for appointments, records and payments.
You are a support technician at the IT provider that holds the clinic's support contract. Your remit covers Tier 1 and Tier 2 work. The provider's workstation engineering team (Tier 3) owns the clinic's standard laptop configuration (the settings applied to every laptop when it is set up). Opening laptops and replacing internal parts is done only by the provider's authorised hardware technician or by the manufacturer under warranty. Anything affecting the building's electrical fittings belongs to the clinic's facilities contractor and needs the practice manager's approval.
On Monday 16 November 2026 the practice manager, Mr Haddad, logs ticket TCK-2530: "The reception laptops have failed AGAIN this morning. Clients were kept waiting for twenty minutes. This is the seventh time since September. I want it fixed properly, not patched." The ticket is assigned to you.
Evidence packet
E1. Occurrence history
Compiled by you from the ticketing system, the receptionists' notebook and staff interviews. Three occurrences were never logged as tickets.
| # | Date and time | Laptops affected | What users saw | What was done | Recorded as |
|---|---|---|---|---|---|
| 1 | Mon 07/09/2026 07:55 | VET-L01, VET-L03 | Practice system would not load: "Your connection isn't private", code NET::ERR_CERT_DATE_INVALID | Receptionist noticed the clock showed 2019 and set the date and time by hand | Not logged (notebook) |
| 2 | Mon 14/09/2026 08:02 | VET-L01, VET-L02, VET-L04 | Same error; clocks showed 01/01/2019 | Help desk connected remotely and set the clocks by hand | TCK-2291 "Clock wrong — fixed" |
| 3 | Mon 28/09/2026 08:10 | VET-L03 | "Wi-Fi not working" (secure sites failing) | Help desk restarted the clinic router (no change), then set the clock by hand | TCK-2350, category Network |
| 4 | Mon 12/10/2026 07:50 | VET-L01, L02, L03, L04 | Same error on all four | Clocks set by hand; one set to 19:50 instead of 07:50, so three appointments were saved with the wrong time | TCK-2417 "Clocks — user error" |
| 5 | Wed 21/10/2026 09:15 | VET-L02 | Same error | Laptop had been left unplugged in the storeroom since Sunday; clock set by hand | Not logged (notebook) |
| 6 | Mon 02/11/2026 08:05 | VET-L01, VET-L04 | Same error | Clocks set by hand | TCK-2488 "Recurring — user advised to set clock" |
| 7 | Mon 16/11/2026 07:58 | VET-L01, L02, L03, L04 | Same error; 20-minute delay at reception | Clocks set by hand | TCK-2530 (this ticket) |
E2. Staff interview notes
| Who | What they said |
|---|---|
| Receptionist (Leah) | "On Monday mornings the laptops sometimes show a black screen with a message about the clock losing power. I press F1 like it says and carry on. Then the clinic system won't open until I fix the time." |
| Receptionist (Tom) | "It's never the vets' laptops. Theirs are newer and they keep them plugged in at their desks." |
| Head nurse | "The laptops live in the charging trolley in the back office overnight and at weekends." |
| Practice manager | "Facilities put the back office sockets on timers at the start of September to save electricity over weekends. I don't think that affects IT." |
E3. Asset register (extract)
| Asset | Model year | Purchased | Warranty | Usual location |
|---|---|---|---|---|
| VET-L01 to VET-L04 | 2019 | August 2019 | Expired August 2022 | Reception and nurses; charging trolley overnight |
| VET-L05, VET-L06 | 2023 | March 2023 | Manufacturer on-site warranty until March 2027 | Vets' consulting rooms; plugged in at desks |
E4. Standard laptop configuration, version 2023.1 (extract)
| Setting | Value | Note |
|---|---|---|
| Time zone | (UTC+00:00) Dublin, Edinburgh, Lisbon, London | |
| Set time automatically | Off | No reason recorded |
| Power: sleep when plugged in | Never | |
| Setup checklist items | 14 items, covering accounts, security software, printers and the practice system shortcut | No item covers date, time or time synchronisation |
E5. Facilities note
Charging trolley and back-office sockets connected to a seven-day timer from Friday 04/09/2026. Power off Friday 19:00 to Monday 07:00, and overnight 22:00 to 06:00 on weekdays.
E6. Tests already carried out by a colleague
| Date | Test | Result |
|---|---|---|
| 13/11/2026 | VET-L01 started after its main battery had been allowed to run completely flat; firmware set-up screen opened before Windows | Firmware shows date 01/01/2019 00:02 and the message "Real-time clock lost power. Date and time reset. Press F1 to continue." |
| Weekend 07–09/11/2026 | VET-L05 (2023 model, same standard configuration) placed in the charging trolley over the weekend; trolley power off as normal | Monday 09/11: main battery flat; after charging, clock correct to the minute; no firmware message |
| 16/11/2026 | On VET-L03, Set time automatically switched On temporarily after the clock reset (with the practice manager's agreement) | Clock corrected within a minute; practice system loaded normally. Setting returned to Off afterwards, pending a decision |
Background for this capstone. A computer keeps its date and time while switched off using a small real-time clock (RTC) circuit powered by its own small battery, often called the CMOS battery. When that battery is exhausted and all other power is removed, the clock resets to a default date. Secure (HTTPS) websites check certificates against the computer's date, so a clock that is years wrong makes valid certificates appear invalid. The book makes the same point in Chapter 5: incorrect clocks break logins and secure websites.
Your tasks
Part A — Analyse the history
- Identify the pattern in E1. Consider days of the week, which laptops are affected, which are never affected, the start date, and the one occurrence that breaks the Monday pattern. What does occurrence 5 tell you?
- Classify each action in the "What was done" column as a workaround, a fix or a root-cause fix (Module 12), and explain why the problem has kept returning.
- Identify every change in the evidence that happened shortly before the first occurrence, and explain how it relates to the pattern.
- Explain what the test with VET-L05 (E6) proves, using the language of the isolation techniques (Module 6). Why was it necessary, given that VET-L05 and VET-L01 differ in more than one way?
- Identify two process failures in how the earlier occurrences were handled, with reference to the book (for example, how tickets were categorised and when the problem should have been escalated).
Part B — Root cause analysis
- Apply the 5 Whys, starting from: "Reception cannot open the practice management system on Monday mornings." Continue until you reach a cause that can be acted on to prevent recurrence. Show each question and answer.
- Draw a fishbone (Ishikawa) diagram (a neat table or text layout is acceptable) with the problem at the head and at least five categories from people, process, technology, network, environment and measurement. Place at least two possible causes under each category, then mark which causes the evidence confirms, which it rules out and which are contributing.
- Write a root cause statement of no more than three sentences. It must name the deepest correctable cause, the trigger, and why the fault was never corrected automatically or by process.
Use this layout for the 5 Whys:
| # | Why? | Because | Evidence |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | |||
| 4 | |||
| 5 | |||
| Corrective action |
Part C — Prevention
- Propose at least four preventive measures. For each, state what it prevents, who would carry it out, how it would be verified, and whether it addresses the root cause, the trigger or the detection of the problem. Draw on the preventive measures table in Module 12.
- Recommend what should happen immediately (this week) and what should follow (within a month). Justify the order.
- Identify one tempting measure you would not recommend and explain why.
Preventive measures layout:
| Measure | Prevents | Owner | How verified | Root cause / trigger / detection |
|---|---|---|---|---|
Part D — Escalation decision
- Using the escalation triggers from Module 13, state which apply to this problem and which do not. Explain why the problem should have been escalated before the seventh occurrence.
- Decide who receives each part of the work, using the tiered support model (Tier 0 self-help, Tier 1 help desk, Tier 2 technical support, Tier 3 specialists, Tier 4 vendor or external), and the clinic's own responsibilities (facilities, practice manager). State the urgency of each.
- State clearly what you will not do yourself, and why.
Part E — Professional handover
-
Write a complete escalation handover to the workstation engineering team, using the book's six parts in order:
- the problem statement (Module 4 template);
- exact error messages, screenshots and photographs;
- when the problem started and what changed beforehand;
- every action taken and the result of each;
- the urgency and the number of users affected;
- contact details and availability of the user and of the person escalating.
Use realistic but fictional contact details. Do not include any password or ask anyone for one.
Part F — Communication and documentation
- Write an email to Mr Haddad (150 to 250 words) that acknowledges the impact on the clinic, explains the cause in plain language without jargon or blame, sets out what happens next and when, and states what the clinic needs to approve.
- Write a short guide for reception staff (no more than 120 words) that tells them what to do if the problem appears again before the permanent fix is complete, including when to stop and call support.
- List the documentation updates you will make so the organisation learns from this incident (for example, the ticket, the knowledge base and the standard configuration notes).
Deliverables
| # | Deliverable | Linked tasks |
|---|---|---|
| 1 | Pattern analysis, classification of past actions and process failures | 1–5 |
| 2 | Completed 5 Whys table | 6 |
| 3 | Fishbone diagram with confirmed, ruled-out and contributing causes marked | 7 |
| 4 | Root cause statement | 8 |
| 5 | Preventive measures table, immediate and follow-up actions, and the measure you rejected | 9–11 |
| 6 | Escalation decision with tiers and urgency | 12–14 |
| 7 | Six-part handover | 15 |
| 8 | Email to the practice manager, staff guide and documentation updates | 16–18 |
Recommended length: 2,000 to 3,000 words, plus tables and diagram.
Assessment rubric
| Criterion (weight) | Excellent (4) | Proficient (3) | Developing (2) | Beginning (1) |
|---|---|---|---|---|
| 1. Pattern analysis (15) | Pattern fully described, including the Wednesday exception and the unaffected laptops; past actions correctly classified; the change in September linked to the start date; the VET-L05 test correctly interpreted as isolating one variable; two genuine process failures identified | Pattern and classification largely correct; minor gaps | Partial pattern; some actions misclassified; test not interpreted | Occurrences described individually with no pattern |
| 2. 5 Whys and root cause statement (20) | Each why follows from evidence; chain reaches a correctable process or configuration cause, not a person; statement names cause, trigger and why it was never corrected, in three sentences or fewer | Logical chain; statement mostly precise | Chain stops at a symptom or a part, or jumps without evidence | Blames users or restates the symptom |
| 3. Fishbone diagram (15) | Five or more relevant categories, two or more causes each; evidence used to mark confirmed, ruled-out and contributing causes; distinguishes this from the single chain of the 5 Whys | Adequate categories and causes; some marking | Few causes or no use of evidence | Diagram missing or irrelevant |
| 4. Prevention (15) | Four or more measures acting on root cause, trigger and detection, each with owner and verification; sensible immediate and follow-up order; a rejected measure with a convincing reason | Sound measures with minor gaps in ownership or verification | Measures generic or mainly workarounds | No meaningful prevention |
| 5. Escalation and handover (20) | Correct triggers identified; work assigned to the right tier or party with urgency; limits of authority respected; handover contains all six parts in order, precise enough for a stranger to continue | Handover complete with minor omissions; escalation decisions sound | Handover missing parts; escalation partly wrong | No usable handover; unsafe or unauthorised actions proposed |
| 6. Communication and documentation (15) | Email acknowledges impact, plain language, no blame, clear next steps and approvals; staff guide short, safe and practical; documentation updates turn the incident into shared knowledge | Clear communication with minor lapses in tone or completeness | Jargon, blame or vague commitments | Communication missing or inappropriate |
Scoring: for each criterion, multiply the level (1–4) by the weight and divide by 4. A total of 70 or above indicates professional-standard work.
Submission checklist
| ✓ | Check |
|---|---|
| ☐ | I have described the pattern, including the occurrence that breaks it |
| ☐ | I have classified every past action as workaround, fix or root-cause fix |
| ☐ | My 5 Whys uses evidence at every step and ends at a correctable cause |
| ☐ | My fishbone has at least five categories and marks what the evidence confirms or rules out |
| ☐ | My root cause statement is three sentences or fewer and does not blame individuals |
| ☐ | Each preventive measure has an owner and a way to verify it |
| ☐ | I have named the escalation triggers that apply and the tier or party for each piece of work |
| ☐ | My handover has all six parts, in the book's order |
| ☐ | My email and staff guide are in plain language, with no jargon or blame |
| ☐ | I have not asked for or included any password |
| ☐ | I have not proposed opening any laptop myself or changing the building's electrical fittings |
Safety and authority reminder. Replacing an internal battery means opening the laptop: it must be done by an authorised technician or the manufacturer, following manufacturer guidance, with the device shut down and disconnected and with anti-static protection. Do not open equipment under warranty without authorisation. Timer sockets and other electrical fittings belong to the facilities contractor.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026): §4.1, §4.4, §4.6 (5W1H, intermittent faults and occurrence logs, problem statement), §5.4 and §5.6 (date and time; workarounds), §6.2–6.3, §6.6 (substitution, comparison, rollback), §8.6 Safety First, §12.1–12.4 (root cause analysis and prevention), §13.1–13.5 (escalation, tiers, handover, communication, documentation)
