# Stakeholder escalation scenarios: ask for a decision without blame

Practise a supplier delay and an unresolved acceptance dispute. See weak responses, stronger requests and a simple reasoning rubric.

Canonical: https://project.responseshift.academy/stakeholder-escalation-scenarios/
Publisher: Response Shift
Updated: 2026-10-31

## Escalate the decision outside your authority

Escalation is useful when a decision, resource or unresolved conflict exceeds the team’s authority or threatens a commitment. It should bring the right person a clear choice while there is still time to act.

Before escalating, establish what is known, what you tried and what the decision owner can change. Avoid sending a long chronology with no request. Urgent safety or compliance concerns must follow the organisation’s actual escalation route.

## Scenario one: an unconfirmed supplier date

Fictional situation: installation begins on day 6, but the supplier has not confirmed shipment by the agreed day-3 trigger. Rental equipment is possible but requires sponsor spending authority.

| Response | Why it helps or fails |
| --- | --- |
| The supplier is letting us down. Please chase them. | Blame does not identify the authority or latest useful decision. |
| Shipment remains unconfirmed. I have requested allocation evidence and obtained a rental estimate. Please authorise the capped rental option by day 4 or accept the current opening-date risk. | Separates evidence, action, options and a time-bound approval. |

## Scenario two: acceptance criteria are disputed

Fictional situation: facilities accepts the handover but security says an agreed test is incomplete. “Everyone signed off except security” misstates readiness. Identify the missing evidence and ask the accountable authority to resolve the acceptance sequence.

A stronger request is: “Security test S4 remains open. Facilities readiness is confirmed. We can complete S4 tomorrow or postpone opening; opening before acceptance would require a separate authorised decision under our policy.” The correct decision depends on the real policy and stakes, not a practice score.

## Score the reasoning



| Criterion | 0 · missing | 1 · partial | 2 · clear |
| --- | --- | --- | --- |
| Evidence | Unsupported claim | Some facts, assumptions mixed in | Facts and uncertainty separated |
| Options | Only a demand | Alternatives with little impact | Viable choices and trade-offs |
| Authority | No owner | Owner implied | Named role and exact decision |
| Timing | ASAP | Date without consequence | Latest useful date and effect of delay |

## Rehearse the request



```text
What changed and what evidence supports it?
Which commitment or acceptance condition is affected?
What have we already done?
Which options remain and what does each cost?
Who has authority to decide?
What decision is needed by when?
What happens if no decision is made?
```

- [Download the template (Markdown)](https://project.responseshift.academy/stakeholder-escalation-scenarios/stakeholder-escalation-scenarios-template.md)
- [Download the worked example (CSV)](https://project.responseshift.academy/stakeholder-escalation-scenarios/stakeholder-escalation-scenarios-example.csv)

## Continue

[Project practice week](https://project.responseshift.academy/practice-week/)

- [APM: project controls background](https://www.apm.org.uk/resources/what-is-project-management/what-is-project-controls/)
