Lesson 54 of 60 beginner

Ticket Quality, SLA & Shift Handover

What operations teams judge every day

Open interactive version (quiz + challenge)

Real-world analogy

A good handover is a relay baton that fits perfectly into the next runner’s hand. A bad handover is tossing the baton behind you and hoping.

What is it?

Ticket quality, SLA compliance, handovers, and KB updates are the ‘meta-skills’ of enterprise IT support. They’re unsexy. They’re exactly what gets you trusted with bigger things.

Real-world relevance

Night shift hands over 6 tickets: 2 high-priority incidents, 3 routine, 1 suspected security event. Clear next-action for each. Morning shift lead reads handover for 3 minutes, knows exactly where to start. No tickets stall at shift boundaries.

Key points

Severity vs priority (applied) — Severity from impact + urgency. A CEO’s critical issue may be high priority even at low technical severity. Match your response to the business pain, not only the technical symptom.
Ticket hygiene at close — Symptom (user words), Environment, Steps taken, Evidence, Root cause (or suspected), Action, Validation, Follow-up, Time. If a stranger reads it, they understand in 60 seconds.
Regular updates for open tickets — Even ‘no update yet’ is an update. SLAs often measure response, not resolution. Silence looks like neglect. Set a cadence and meet it.
Handover checklist — Open tickets with status, priority, and next action. Pending changes in progress. Active incidents with IC + contact. Systems currently under watch. Pending approvals. Known customer hotspots. Anything in flight during the window.
Knowledge base updates — After tricky resolutions, spend 10 minutes writing a KB entry. Link it from the ticket. Future you (and your replacement) pay dividends in saved hours.
Escalation discipline — Escalate with: current state, what you tried, what you ruled out, hypothesis, what you need, links to logs. ‘Please help’ is not an escalation.
CMDB hygiene (briefly) — If your org has a CMDB, keep asset/service relationships current. Changes, new systems, and retirements should update the CMDB. ‘We don’t know what depends on this’ is the worst thing to hear during an outage.
Personal metrics to track quietly — Your own: avg resolution time, % SLA met, first-time fix rate, number of KB articles written, mentorship moments. Be the kind of junior seniors notice.

Code example

// Shift handover template (one page)

Date/Time:      2026-04-20 06:00 local
Outgoing:       Alice (Tier 1), Bob (Tier 2)
Incoming:       Chen, Priya

Active incidents:
  - INC-1284 (Sev 2)  M365 sign-in issues in APAC
      IC: Senior-oncall; affected: ~500 users
      Next action: await Microsoft service update at 06:30
      Comms cadence: every 30 min; last update 05:50

Pending changes:
  - CHG-0423 patch window 22:00-02:00 tonight
      Owner: Server-team; rollback tested; comms done

Open high-priority tickets:
  - #4421  payroll batch failed; retry at 07:30 scheduled
  - #4432  exec laptop failing BitLocker PIN

Watch items (no alert yet):
  - DB01 CPU rising since 04:00
  - Branch SIT-03 intermittent Wi-Fi reports

Handovers closed:
  - INC-1278 DNS outage — resolved 04:15, KB-0076 updated
  - CHG-0419 firewall rule deployed, verified

Line-by-line walkthrough

1. Handover template
2. Date/time
3. Outgoing staff
4. Incoming staff
5. Active incidents section
6. Specific incident details
7. Pending changes section
8. Change details
9. Open high-priority tickets
10. Ticket lines
11. Watch items
12. Notable metric trends
13. Closed handovers
14. Resolved items and KB links

Spot the bug

Ticket closure note (actual): ‘User happy. Case closed.’

Need a hint?

What’s missing that a future coworker or auditor will need?

Show answer

Missing symptom, environment, steps taken, evidence, root cause/suspected, action, validation, and follow-up. One-line closures waste team time and destroy audit trails. Use a template.

Explain like I'm 5

Good support is 50% fixing things and 50% writing clearly about what you fixed — so the next person, the next shift, and the auditor can all understand you.

Fun fact

Many of the senior hires in enterprise IT teams were first noticed for one boring habit: they always wrote clear tickets and kept their handovers tidy. Technical skill opens the door; documentation habits walk you through it.

Hands-on challenge

Design your own shift-handover template and use it for a week of self-tracking (even a personal to-do list). Share it with a peer for feedback.

More resources

ITIL 4 service desk guidance (AXELOS)
Writing great tickets (YouTube search)
Shift-handover research (healthcare, IT adaptations) (Wikipedia)

Open interactive version (quiz + challenge) ← Back to course: IT Jobs Bootcamp