discussion, women, exchange, sitting, discussion, discussion, discussion, discussion, discussion
Photo by 422737 on Pixabay

Meetings

Part of Decision efficiency

Escalating a blocked decision with clear options

Escalation works when the recipient can decide without reconstructing weeks of discussion.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Meetings.

Escalation works when the recipient can decide without reconstructing weeks of discussion. Send a short brief that states the choice, options, recommendation and consequence of waiting.

Assemble a decision-ready note

Use five parts: the question and deadline; why the current owner cannot decide; two or three feasible options; the main benefit, cost and risk of each; and the recommended choice with its uncertainty. Attach detailed evidence separately.

If a missing fact could change the recommendation, name who can obtain it and when. Atlassian's DACI model separates the driver who gathers input from the approver who decides, which helps identify the right escalation route.

Be explicit about the authority needed. Does the choice require budget, a policy exception or priority across teams?

If the recipient lacks that authority, forwarding the brief to them merely adds a hand-off.

Give a default interim action if the deadline passes and that action is safe and authorised.

Keep the tone factual. An escalation is a request for a decision, not a complaint about colleagues, so describe the blockage in terms of the missing authority or information rather than who failed to act.

Timing matters as well. Escalate when the cost of waiting begins to exceed the cost of interrupting a senior person, not at the very last minute. Early escalation with a clear brief gives the recipient room to consult others.

DACI Model: Clarifying Roles in Decision-Making

Driver
Gathers input and prepares the decision note (e.g., project manager)
Approver
Makes the final decision (e.g., team lead or executive)
Contributor
Provides expertise or data (e.g., finance or legal team)
Informed
Notices the outcome but not involved in the process (e.g., stakeholders)

Close the loop

Record the decision or the remaining blocker, including owner and date. Share the outcome with contributors and implementers, not only the person who escalated it. If the answer is “gather more evidence”, specify the exact evidence and the next decision date.

Check that the decision actually unblocked the work. A day or two later, confirm with the team doing the task that they have what they need and that the answer was clear enough to act on. If it was not, ask for a short clarification rather than starting a second escalation.

Track recurring escalations. They may reveal unclear delegated authority or missing criteria. Fixing that source saves more time than becoming faster at writing escalation emails.

Further reading: Project escalation procedures: When and how to escalate issues (plane.so).

More from Meetings

Meetings

Decision efficiency

Teams lose time when a discussion has no named decision, the wrong people are asked to approve it or a settled choice is debated again without new…