What should be included in an escalation message to the next team?

• A. A blame statement to the next team
• B. Clear problem statement, evidence, steps tried, impact, and a specific ask
• C. Evidence only
• D. A general request without specifics

Answer: (B)

Escalation messages should hand off the issue with enough context for the next team to act without a round of back-and-forth. The best answer includes a clear problem statement, evidence, steps tried, impact, and a specific ask because this combination gives the recipient a complete, actionable picture.

A clear problem statement sets the scene: what happened, when it started, where in the system you’re seeing the symptom, and any observable behavior. Evidence grounds the issue: logs, error messages, metrics, screenshots, timestamps, and anything reproducible that helps verify the problem and its scope. Steps tried show what you already attempted so the other team doesn’t duplicate work and can build on your efforts. Impact explains who and what is affected, the severity, and the business or user consequences, which helps with prioritization and urgency. A specific ask tells the next team exactly what you need from them—e.g., investigate a root cause, collect additional data, implement a workaround, or schedule a change window—and may include a requested ETA.

This format keeps the handoff productive. Blaming language isn’t helpful, and relying on evidence alone or making a vague request leaves the next team without direction or priority, delaying resolution.