Advanced
Writing
#escalation
#stakeholders
#urgency
Escalation Emails
5 exercises — opening with impact, quantifying business cost, security escalation framing, and requesting decisions with deadlines.
0 / 22 completed
1 / 22
You need to escalate a blocked infrastructure request to your VP. Which email opening is most effective?
An escalation email opening must state what is blocked, how long it has been blocked, the business impact, and what decision is needed — immediately, before any pleasantries. Option B hits all four in two sentences. Option A opens with an apology ("sorry to bother") which undermines urgency and buries the issue. Option C is vague ("some issues", "too long"). Option D names a team in a blame-attributing way ("not responding") — frame the obstacle as a process gap, not a people failure.
2 / 22
Complete this escalation: "This ticket _____ (block) two sprint deliverables. I _____ (already/escalate) to the infrastructure team lead on May 19 with no response. At current trajectory, the release _____ (miss) its June 3 deadline."
Is blocking (present continuous) describes an ongoing, active obstruction happening right now — the correct tense for a current blocker. Have already escalated (present perfect) links a past action (the May 19 escalation) to the present situation — it shows a prior step was taken and the problem persists. Will miss (future simple) is a factual prediction about a future deadline. Option D ("is going to miss") is grammatically possible but weaker — "will miss" is more decisive and confident in an escalation context.
3 / 22
Which sentence correctly quantifies the impact in an escalation email?
Escalation emails should quantify impact in business terms that a VP or director can act on: cost per day, SLA breach amounts, milestone slippage in concrete days. Option B does exactly that — $4,200/day in SLA credits and a 1:1 day slip on Q2. This gives the escalation recipient everything they need to justify action to their own stakeholders. Options A, C, and D use vague intensifiers ("significant", "quite serious", "very high priority") — these are not actionable because they don't tell a decision-maker what the actual cost of inaction is.
4 / 22
You've been asked to escalate an unresolved security vulnerability. What must your escalation email include that other escalations don't typically require?
Security escalations require standardized severity framing that lets recipients understand risk without domain expertise. The CVSS score (e.g., CVSS 9.1 / Critical) is universally understood. Attack surface scoping ("publicly reachable API endpoint") tells leadership who is at risk. Public disclosure status (CVE published, active exploitation in the wild) drives legal and PR considerations. Together these let a VP or CISO decide whether to invoke the incident response process immediately or schedule a fix. Repeating "urgent" (Option C) doesn't add information — severity scores do.
5 / 22
Choose the best closing for an escalation email: "I _____ (request) a decision by EOD Thursday so we _____ (can/keep) the June 3 release on track. I _____ (be/happy) to join a 15-minute call today or tomorrow to discuss options."
Request (present simple) is the most direct and professional register for a formal written request — it is declarative and confident. Can keep (present simple modal) expresses a condition: given the decision, the release can stay on track. Am happy (present simple) is the standard English phrase for expressing willing availability. Option A ("am requesting") uses present continuous which sounds more tentative and informal. Option C uses "would" throughout, which makes the email sound too conditional and soft for an escalation that needs action. Option D uses present perfect ("have requested") which refers to the past — but this is a new request being made right now.
6 / 22
Team Lead just sent you this Slack message: 'Hey, the new API endpoint is timing out consistently for users in Europe. We've increased the timeout but it's still happening. Can you look into it?' You need to escalate this issue to the DevOps team and highlight the potential impact on user experience. Which of the following email subject lines would be most effective?
The best subject line immediately communicates the problem's location (Europe) and its potential significance (Urgent). Options A and C are too generic. While 'Requesting Assistance' is polite, it doesn't convey the severity or focus of the issue. Using 'Urgent' in the subject line signals the need for immediate attention and prioritization, which is crucial when escalating a production-level problem.
7 / 22
Sarah, a junior developer, has been working on integrating a new third-party library into the core application. During code review, her team lead, David, left a comment highlighting potential performance issues with the library's heavy data processing. Sarah responded by saying 'I'll look into it later.' David replied in Slack: 'This is impacting user latency significantly. Can you provide an estimated timeframe for resolving these bottlenecks?'. Which of the following email drafts would be most appropriate for Sarah to send to David, escalating the issue and requesting support?
The correct option demonstrates proactive communication and provides concrete steps being taken. It acknowledges the issue's severity (latency), outlines Sarah's investigation plan (profiling), and sets a realistic timeframe for reporting back. Options A and B are passive and don't show urgency or a commitment to resolution, while option C is too vague and doesn't offer specific details. Option D is completely unhelpful – it avoids the issue entirely.
8 / 22
Sarah is investigating a performance bottleneck introduced by a new third-party library. David's Slack message indicates the issue is already impacting user latency and he needs an estimated timeframe for resolution. Which of the following email drafts best addresses this situation while escalating effectively?
**A.** Hi David, Just wanted to update you on my progress with the new library. I'm still investigating the performance issues and will keep you posted. **B.** David, The integration is taking longer than anticipated. I'm working on addressing the performance bottlenecks but need more time to fully understand the scope of the impact. Let me know if you have any questions. **C.** Hi David, We've identified a significant performance impact due to the new library – users are experiencing increased latency. I'm currently estimating the resolution timeframe at [estimated time] and would appreciate your support in prioritizing this issue. Please let me know if you need any further information. **D.** Hey David, Just checking in on the library integration. Any updates?
Subject: Urgent: Performance Impact - New Library Integration
**A.** Hi David, Just wanted to update you on my progress with the new library. I'm still investigating the performance issues and will keep you posted. **B.** David, The integration is taking longer than anticipated. I'm working on addressing the performance bottlenecks but need more time to fully understand the scope of the impact. Let me know if you have any questions. **C.** Hi David, We've identified a significant performance impact due to the new library – users are experiencing increased latency. I'm currently estimating the resolution timeframe at [estimated time] and would appreciate your support in prioritizing this issue. Please let me know if you need any further information. **D.** Hey David, Just checking in on the library integration. Any updates?
The correct answer (C) is the most effective because it directly addresses the severity of the problem – 'significant performance impact' – and provides a clear estimate of the resolution timeframe. It also proactively requests support from David, framing the issue as requiring prioritization. Options A and D are too vague and don't convey the urgency or need for assistance. Option B is passive and doesn't clearly articulate the impact or request action.
9 / 22
Team Lead just sent you this Slack message: 'Hey, the new API endpoint is timing out consistently for users in Europe. We've increased the timeout but it's still happening. Can you look into it?' You need to escalate this issue to the DevOps team and highlight the potential impact on user experience. Which of the following email subject lines would be most effective?
The best subject line immediately communicates the problem's location (Europe) and its potential significance (Urgent). Options A and C are too generic. While 'Requesting Assistance' is polite, it doesn't convey the severity or focus of the issue. Using 'Urgent' in the subject line signals the need for immediate attention and prioritization, which is crucial when escalating a production-level problem.
10 / 22
Sarah, a junior developer, has been working on integrating a new third-party library into the core application. During code review, her team lead, David, left a comment highlighting potential performance issues with the library's heavy data processing. Sarah responded by saying 'I'll look into it later.' David replied in Slack: 'This is impacting user latency significantly. Can you provide an estimated timeframe for resolving these bottlenecks?'. Which of the following email drafts would be most appropriate for Sarah to send to David, escalating the issue and requesting support?
The correct option demonstrates proactive communication and provides concrete steps being taken. It acknowledges the issue's severity (latency), outlines Sarah's investigation plan (profiling), and sets a realistic timeframe for reporting back. Options A and B are passive and don't show urgency or a commitment to resolution, while option C is too vague and doesn't offer specific details. Option D is completely unhelpful – it avoids the issue entirely.
11 / 22
Sarah is investigating a performance bottleneck introduced by a new third-party library. David's Slack message indicates the issue is already impacting user latency and he needs an estimated timeframe for resolution. Which of the following email drafts best addresses this situation while escalating effectively?
**A.** Hi David, Just wanted to update you on my progress with the new library. I'm still investigating the performance issues and will keep you posted. **B.** David, The integration is taking longer than anticipated. I'm working on addressing the performance bottlenecks but need more time to fully understand the scope of the impact. Let me know if you have any questions. **C.** Hi David, We've identified a significant performance impact due to the new library – users are experiencing increased latency. I'm currently estimating the resolution timeframe at [estimated time] and would appreciate your support in prioritizing this issue. Please let me know if you need any further information. **D.** Hey David, Just checking in on the library integration. Any updates?
Subject: Urgent: Performance Impact - New Library Integration
**A.** Hi David, Just wanted to update you on my progress with the new library. I'm still investigating the performance issues and will keep you posted. **B.** David, The integration is taking longer than anticipated. I'm working on addressing the performance bottlenecks but need more time to fully understand the scope of the impact. Let me know if you have any questions. **C.** Hi David, We've identified a significant performance impact due to the new library – users are experiencing increased latency. I'm currently estimating the resolution timeframe at [estimated time] and would appreciate your support in prioritizing this issue. Please let me know if you need any further information. **D.** Hey David, Just checking in on the library integration. Any updates?
The correct answer (C) is the most effective because it directly addresses the severity of the problem – 'significant performance impact' – and provides a clear estimate of the resolution timeframe. It also proactively requests support from David, framing the issue as requiring prioritization. Options A and D are too vague and don't convey the urgency or need for assistance. Option B is passive and doesn't clearly articulate the impact or request action.
12 / 22
Team Lead just sent you this Slack message: 'Hey, the new API endpoint is timing out consistently for users in Europe. We've increased the timeout but it's still happening. Can you look into it?' You need to escalate this issue to the DevOps team and highlight the potential impact on user experience. Which of the following email subject lines would be most effective?
The best subject line immediately communicates the problem's location (Europe) and its potential significance (Urgent). Options A and C are too generic. While 'Requesting Assistance' is polite, it doesn't convey the severity or focus of the issue. Using 'Urgent' in the subject line signals the need for immediate attention and prioritization, which is crucial when escalating a production-level problem.
13 / 22
Sarah, a junior developer, has been working on integrating a new third-party library into the core application. During code review, her team lead, David, left a comment highlighting potential performance issues with the library's heavy data processing. Sarah responded by saying 'I'll look into it later.' David replied in Slack: 'This is impacting user latency significantly. Can you provide an estimated timeframe for resolving these bottlenecks?'. Which of the following email drafts would be most appropriate for Sarah to send to David, escalating the issue and requesting support?
The correct option demonstrates proactive communication and provides concrete steps being taken. It acknowledges the issue's severity (latency), outlines Sarah's investigation plan (profiling), and sets a realistic timeframe for reporting back. Options A and B are passive and don't show urgency or a commitment to resolution, while option C is too vague and doesn't offer specific details. Option D is completely unhelpful – it avoids the issue entirely.
14 / 22
Sarah is investigating a performance bottleneck introduced by a new third-party library. David's Slack message indicates the issue is already impacting user latency and he needs an estimated timeframe for resolution. Which of the following email drafts best addresses this situation while escalating effectively?
**A.** Hi David, Just wanted to update you on my progress with the new library. I'm still investigating the performance issues and will keep you posted. **B.** David, The integration is taking longer than anticipated. I'm working on addressing the performance bottlenecks but need more time to fully understand the scope of the impact. Let me know if you have any questions. **C.** Hi David, We've identified a significant performance impact due to the new library – users are experiencing increased latency. I'm currently estimating the resolution timeframe at [estimated time] and would appreciate your support in prioritizing this issue. Please let me know if you need any further information. **D.** Hey David, Just checking in on the library integration. Any updates?
Subject: Urgent: Performance Impact - New Library Integration
**A.** Hi David, Just wanted to update you on my progress with the new library. I'm still investigating the performance issues and will keep you posted. **B.** David, The integration is taking longer than anticipated. I'm working on addressing the performance bottlenecks but need more time to fully understand the scope of the impact. Let me know if you have any questions. **C.** Hi David, We've identified a significant performance impact due to the new library – users are experiencing increased latency. I'm currently estimating the resolution timeframe at [estimated time] and would appreciate your support in prioritizing this issue. Please let me know if you need any further information. **D.** Hey David, Just checking in on the library integration. Any updates?
The correct answer (C) is the most effective because it directly addresses the severity of the problem – 'significant performance impact' – and provides a clear estimate of the resolution timeframe. It also proactively requests support from David, framing the issue as requiring prioritization. Options A and D are too vague and don't convey the urgency or need for assistance. Option B is passive and doesn't clearly articulate the impact or request action.
15 / 22
Team Lead just sent you this Slack message: 'Hey, the new API endpoint is timing out consistently for users in Europe. We've increased the timeout but it's still happening. Can you look into it?' You need to escalate this issue to the DevOps team and highlight the potential impact on user experience. Which of the following email subject lines would be most effective?
The best subject line immediately communicates the problem's location (Europe) and its potential significance (Urgent). Options A and C are too generic. While 'Requesting Assistance' is polite, it doesn't convey the severity or focus of the issue. Using 'Urgent' in the subject line signals the need for immediate attention and prioritization, which is crucial when escalating a production-level problem.
16 / 22
Sarah, a junior developer, has been working on integrating a new third-party library into the core application. During code review, her team lead, David, left a comment highlighting potential performance issues with the library's heavy data processing. Sarah responded by saying 'I'll look into it later.' David replied in Slack: 'This is impacting user latency significantly. Can you provide an estimated timeframe for resolving these bottlenecks?'. Which of the following email drafts would be most appropriate for Sarah to send to David, escalating the issue and requesting support?
The correct option demonstrates proactive communication and provides concrete steps being taken. It acknowledges the issue's severity (latency), outlines Sarah's investigation plan (profiling), and sets a realistic timeframe for reporting back. Options A and B are passive and don't show urgency or a commitment to resolution, while option C is too vague and doesn't offer specific details. Option D is completely unhelpful – it avoids the issue entirely.
17 / 22
Sarah is investigating a performance bottleneck introduced by a new third-party library. David's Slack message indicates the issue is already impacting user latency and he needs an estimated timeframe for resolution. Which of the following email drafts best addresses this situation while escalating effectively?
**A.** Hi David, Just wanted to update you on my progress with the new library. I'm still investigating the performance issues and will keep you posted. **B.** David, The integration is taking longer than anticipated. I'm working on addressing the performance bottlenecks but need more time to fully understand the scope of the impact. Let me know if you have any questions. **C.** Hi David, We've identified a significant performance impact due to the new library – users are experiencing increased latency. I'm currently estimating the resolution timeframe at [estimated time] and would appreciate your support in prioritizing this issue. Please let me know if you need any further information. **D.** Hey David, Just checking in on the library integration. Any updates?
Subject: Urgent: Performance Impact - New Library Integration
**A.** Hi David, Just wanted to update you on my progress with the new library. I'm still investigating the performance issues and will keep you posted. **B.** David, The integration is taking longer than anticipated. I'm working on addressing the performance bottlenecks but need more time to fully understand the scope of the impact. Let me know if you have any questions. **C.** Hi David, We've identified a significant performance impact due to the new library – users are experiencing increased latency. I'm currently estimating the resolution timeframe at [estimated time] and would appreciate your support in prioritizing this issue. Please let me know if you need any further information. **D.** Hey David, Just checking in on the library integration. Any updates?
The correct answer (C) is the most effective because it directly addresses the severity of the problem – 'significant performance impact' – and provides a clear estimate of the resolution timeframe. It also proactively requests support from David, framing the issue as requiring prioritization. Options A and D are too vague and don't convey the urgency or need for assistance. Option B is passive and doesn't clearly articulate the impact or request action.
18 / 22
During a code review of a new feature, Alex points out a potential memory leak in the caching logic. He suggests adding explicit cleanup routines. Your team lead, Maria, replies with: 'Thanks for flagging this! Can you provide a rough estimate on the effort to implement these changes and their impact on performance?' Which of the following responses best reflects a professional escalation email?
This scenario tests framing a technical concern as an escalation. Option 1 provides a clear estimate and acknowledges Maria's request. Options 2 is overly dramatic and doesn't offer solutions; option 3 deflects responsibility, while option 4 avoids addressing the issue entirely. It demonstrates appropriate communication regarding impact and effort.
19 / 22
You receive this Slack message from your senior engineer, Ben: 'The new microservice is intermittently failing to connect to the database. We've seen a few errors in production logs related to connection timeouts. Rolling back deployments isn't feasible at this stage.' What key information should you immediately include in an escalation email to the relevant team (DevOps and Product)?
The core of escalation is highlighting severity and requesting action. Option 1 is passive and doesn't convey urgency. Option 2 directly addresses the critical impact and asks for immediate help. Options 3 ignores the problem, while option 4 suggests a preventative measure instead of addressing an existing issue.
20 / 22
You're drafting the PR description for a significant refactoring of a core API endpoint. The change introduces several performance improvements and addresses some outdated code. However, you've identified a potential edge case that *might* cause brief service unavailability during peak load. Which sentence would be MOST appropriate to add to the PR description to signal the need for escalation?
It's vital to proactively communicate potential risks. Option 1 focuses solely on positive changes. Option 2 is too vague. Option 3 *directly* identifies the risk and requests further investigation – this is the correct approach for an escalation. Option 4 overstates confidence in the code.
21 / 22
During your daily stand-up, you report that a newly deployed feature is causing intermittent errors for users submitting large form submissions. You've identified a potential bottleneck in the data validation process. Your manager asks: 'Can you provide an estimated time to resolution?' What should you say to appropriately escalate this issue?
Escalations require clear communication about the root cause and the need for assistance. Option 1 delays action. Option 2 clearly identifies the technical problem and requests help. Options 3 provides a reasonable update timeline and option 4 minimizes the issue, failing to acknowledge the impact.
22 / 22
David, your team lead, comments on a pull request: 'This implementation uses a callback function that could lead to race conditions. Consider using Promises or async/await for better error handling and concurrency.' You realize the potential issue is significant and could impact multiple services. Which of the following responses would best initiate an escalation?
The key to escalation is recognizing the severity and proactively requesting assistance. Option 1 delays action. Option 2 is passive. Option 3 clearly articulates the risk and requests guidance – demonstrating you understand the potential impact. Option 4 dismisses the concern.
Frequently Asked Questions
What does the "Escalation Emails — Writing Exercise" exercise cover?
Practice writing professional escalation emails: quantifying impact, framing blockers, security escalations, and requesting decisions with deadlines. 5 interactive exercises.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Escalation Emails — Writing Exercise"?
This exercise has 22 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Email & Writing exercises?
Browse the full Email & Writing hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.