A practical delivery guide
When should you escalate a delivery issue?
Escalate when a delivery issue needs a decision you cannot make alone and waiting is likely to make the impact worse. If you can still act locally, hold it and watch. If someone needs early visibility but no decision yet, flag it. If a named person must choose a trade-off, raise it clearly.
Build your free Escalation PackThe Hold–Flag–Raise test
Choose the move that the situation justifies now.
These are actions, not severity labels. A serious issue may need a flag first if the decision, evidence or owner is not ready.
01
Hold
Keep owning it and keep watching.
- You can act within your role and the impact is still recoverable.
- The evidence is incomplete or the decision owner is not yet clear.
- You know the next check that would tell you whether the risk is growing.
Ask: What can I do locally before anyone else needs to act?
02
Flag
Make the risk visible early while you still own the actions.
- The right person could be surprised later if they do not hear about it now.
- The issue may affect a date, scope, dependency or stakeholder expectation.
- You are not asking for a decision yet, but you need a shared record of the risk.
Ask: Who needs early visibility, and what will I do next?
03
Raise
Ask a named person to decide something you cannot decide alone.
- A real trade-off needs a decision about scope, date, money, risk or priority.
- Waiting is likely to make the impact harder to recover.
- You can name the decision required, the evidence behind it and who should make it.
Ask: What decision do I need, from whom, and by when?
Before you raise it
Check the evidence and the decision owner.
Evidence threshold
Bring the smallest set of facts that would help a sceptical person understand the risk: what has happened, what is likely to happen next and what changes if nothing changes.
Do not use a raised issue to discover the facts for the first time.
Decision-owner check
Raise the issue to the person who can make the trade-off. If that owner is unclear, ask for help finding the owner rather than escalating broadly.
A clear decision ask is more useful than a general request for help.
Do not escalate yet when
The next useful move is still within your control.
- You have not yet confirmed the basic facts or impact.
- You can make a local change and set a clear point to review it.
- The request is really for awareness, not a decision.
- You do not know which decision needs to be made or who owns it.
An invented example
A date risk becomes a decision ask.
The situation
A delivery team has lost two days to a dependency failure. The milestone is still possible, but only if a lower-priority reporting change moves.
The move
Raise. The delivery lead cannot decide which commitment moves. The sponsor can.
The wording
“The dependency failure has removed two delivery days. To protect the milestone, I need a decision today: move the reporting change to the next slot, or accept the milestone moving by two days.”
Keep the conversation useful
Common over-escalation mistakes.
- Treating anxiety or urgency as proof that someone else must decide.
- Sending a long list of problems without naming the decision required.
- Asking a senior person to intervene before the owner, evidence or next action is clear.
- Waiting so long that a useful flag becomes an emergency raise.