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 / 10 completed
1 / 10
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 / 10
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 / 10
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 / 10
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 / 10
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.
6 / 10
Sarah from On-Call just messaged you: 'We're seeing high latency on the API endpoint. Users are reporting timeouts.' Which response is BEST to acknowledge and begin gathering more details?
(Note: This simulates a Slack message during an ongoing incident.)
The best response directly asks for crucial information (affected users, latency numbers) to start diagnosing the issue. Option A is too vague, option C dismisses the problem, and option D doesn't initiate a productive conversation. Asking for specifics allows you to immediately understand the scope and severity.
7 / 10
You're reviewing a code change submitted by David that addresses an intermittent issue with database connection errors. He's included a comment in the PR: 'Fixed connection leaks.' Which follow-up question would be MOST helpful to ensure the fix is robust?
(Note: This simulates a code review scenario.)
Asking for details about *which* connections leaked and *how* they were fixed demonstrates a deeper understanding of the problem. Simply stating 'Great, thanks' is insufficient – it doesn't probe for verification or potential remaining issues. Running tests would be good, but pinpointing the root cause first is more effective.
8 / 10
Mark is updating the incident status in the team channel: 'We've identified a potential memory leak in the background worker process. We're currently running diagnostics and expect to have an update within the hour.' Which statement BEST complements this update for clarity?
(Note: This simulates a real-time incident update.)
Asking about the *impact* of the memory leak is crucial for prioritizing and understanding the urgency. While acknowledging the update is important, simply stating 'What's the impact?' ensures everyone understands the potential consequences of the issue. The other options are irrelevant or inappropriate for this stage.
9 / 10
During a handoff, Emily tells you: 'I've been running the standard debugging steps, but I'm still seeing intermittent errors. The logs show increased CPU usage.' Which action should you recommend to the incoming engineer?
(Note: This simulates discussing investigation findings.)
Suggesting more detailed logging is the most proactive step to understand the root cause of intermittent errors. Increased CPU usage *could* be a symptom, but simply monitoring isn't sufficient. The other options are either passive or dismissive of the problem.
10 / 10
You're writing an incident summary for the post-mortem report: 'The service experienced intermittent downtime due to a race condition in the order processing queue. We identified and mitigated the issue by introducing rate limiting.' Which addition would BEST complete this concise summary?
(Note: This simulates a PR description or incident recap.)
Including the quantifiable impact (a 2% drop in sales) provides context and demonstrates the severity of the incident. While acknowledging the root cause is important, focusing on the outcome – the measurable effect – strengthens the summary and helps with future decision-making. The other options are tangential or irrelevant.
What will I practise in "On-Call Handoff English: Phrases for Incident Continuity"?
This module focuses on Phrasebook — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Phrasebook exercises?
See the Phrasebook hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.