Escalate a blocked task with useful options

‘Still waiting’ describes a state but gives an escalation recipient little to act on. Explain what is blocked and why their involvement is needed. Escalation is most useful when it changes the available options, not when it merely adds more people to a frustrated conversation.

Make the blockage concrete

Name the task and the dependency preventing progress. Distinguish a missing answer from a disagreement, a lack of access or a resource conflict. Those problems require different interventions. Include the relevant date and the consequence if the issue remains unresolved.

Summarise the attempts already made. A short chronology can be helpful: the request was sent, a clarification was provided and the agreed response window has passed. Keep it factual. Do not use the escalation to speculate that someone is ignoring the work or does not care about the deadline.

Link to the material needed to decide. The recipient should not have to search an email chain for the current draft or reconstruct which version is awaiting approval. If the information is sensitive, use the appropriate restricted channel rather than copying the entire history to a wider group.

Ask for a specific intervention

You may need a priority decision, an authorised substitute, access to a system or approval to change the sequence. State that request. ‘Please advise’ can be too broad when you already know the choice that would unblock the task.

For a hypothetical launch, an escalation might say: ‘The technical description is awaiting approval and the reviewer is unavailable. We can delay publication or publish the already approved overview without the new section. Please confirm which route we should use by the design cut-off.’ The options are examples, not universally suitable solutions. Each must preserve the actual requirements of the project.

Explain the trade-offs without selecting an unauthorised shortcut. If no safe alternative exists, say that work must remain paused. A deadline does not make an essential approval unnecessary.

Tell the original participants that the issue is being escalated when appropriate to the situation and process. This avoids an unnecessary surprise and keeps the escalation focused on resolving the work. After a decision, update everyone who needs the outcome and close the old requests so that two routes do not proceed at once.

Repeated escalations around the same dependency suggest a process issue. Review ownership, capacity or approval timing after the immediate blockage is resolved. Escalation should not become the routine mechanism by which ordinary work gets noticed.