Prompt
Draft Impediment Escalation Message
Use this when a blocker needs management or another team's help and you want a clear, factual escalation message.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a Scrum Master drafting an escalation message for a blocker the team cannot clear on its own. Optimise for a short, factual, respectful request that gives the recipient everything they need to act.
Context you provide
- {{impediment_description}}: what is blocked and why
- {{date_raised}}: when the team first flagged it
- {{impact_on_team}}: sprint goal, deliverable or customer affected
- {{delay_estimate}}: days blocked or forecast slip
- {{actions_taken}}: what the team already tried
- {{recipient}}: person, role or team being asked
- {{specific_ask}}: the decision, access, resource or introduction needed
- {{needed_by}}: date the answer must land
- {{channel}}: email, chat message or ticket comment
- {{tone}}: neutral, firm or urgent
Instructions
- Ask for any missing inputs, then draft the message.
- Open with the ask in one sentence, then describe the impediment in plain language.
- State the impact in concrete terms using only the inputs given.
- List what the team has already tried, so the recipient knows this is not a first attempt.
- Name the single specific ask and the date it is needed by.
- Close with the next step you will take if there is no response by that date.
- Keep the tone professional: no blame, no sarcasm, no replay of the disagreement.
Output format Subject line, then a message of 120 to 180 words. Short paragraphs or bullets. Plain business language. Leave out team politics, speculation about motives and any detail the recipient does not need in order to act.
Guardrails
- Do not invent dates, ticket numbers, names or commitments; use only the inputs provided and mark anything uncertain as an assumption.
- If the blocker touches contracts, budgets, legal or regulatory matters, state that the relevant owner or a licensed professional must confirm before the message is sent.
- Check your organisation's escalation path and tone norms before sending.
Example Impediment: staging environment unavailable; raised 3 June; blocks payment testing; 4 days blocked; tried restart and vendor ticket; recipient: platform team lead; ask: restore access by 10 June; channel: email; tone: firm.