On-Call Handoff English: Phrases for Incident Continuity
5 exercises — handing off ongoing incidents, describing investigation state, explaining what has been tried, flagging escalation criteria, and writing handoff summary messages.
0 / 5 completed
1 / 5
You are ending your on-call shift and handing off an ongoing incident to the next engineer. Which handoff message opener is BEST?
Incident handoff openers should immediately convey: incident ID and severity, what is affected, when it started, current resolution status, and the incoming engineer's primary task. Option B covers all of these. This allows the incoming engineer to orient instantly without reading the entire incident thread.
2 / 5
You need to describe the current state of an investigation during handoff. Which description is MOST useful?
Describing investigation state: A useful handoff describes: what you believe the root cause is, the evidence supporting it, any confirmed vs unconfirmed status, and what the next investigative step is. Option B follows this structure precisely. The incoming engineer can immediately continue the investigation rather than starting from scratch.
3 / 5
You need to tell the incoming engineer what you have already tried. Which message is MOST complete?
Listing what has been tried: Number each action, include the outcome (not just what you did), and flag any important 'do not' instructions (like not restarting the reporting job). Option B does this. This prevents the incoming engineer from wasting time repeating failed actions and gives them a clear starting point.
4 / 5
You need to tell the incoming engineer when to escalate the incident further. Which escalation criteria message is BEST?
Escalation criteria must be specific and measurable — thresholds, not vague instructions. Option B gives three clear escalation triggers (error rate threshold, rollout failure, time limit) and names the escalation contact. 'Escalate if it gets worse' is subjective and forces the incoming engineer to make a judgment call without calibration.
5 / 5
You are writing a complete handoff summary message in the incident channel. Which summary format is BEST?
Handoff summary format: A complete handoff message is scannable (emoji status, bold section labels), covers all key information (root cause, fix, what was tried, next action, escalation, doc link), and names the incoming engineer explicitly. Option B follows this format. It saves the incoming engineer from reading potentially hours of thread history to orient themselves.