In this article
I want people to think before they escalate an issue. I also want to hear about serious risks while there is still time to act.
Those expectations need to work together. If staff believe they must arrive with a complete solution before speaking up, an escalation rule can delay information a manager needs. This is the format I would use for routine issues, with a separate route for urgent concerns.
When should you escalate an issue?
Escalate when the decision falls outside your authority. You may know what you would recommend but still need permission to change a customer commitment or use another team’s resources. State the boundary you cannot cross, so the manager understands why their decision is needed.
A different trigger is an unresolved dependency that has passed its agreed limit. Record the commitment and the follow-up already made. An information update tells the manager what is happening; a decision request states what you need them to resolve. Label the message accordingly.
I would not require someone to exhaust every imaginable option. Missing expertise or access may prevent a reliable recommendation. Asking for help can be a responsible next step, provided the employee explains what they need to establish.
Clarify decision ownership before setting the reporting rule.
Copy this employee escalation template.
Subject: Decision needed on [issue] by [date and time]
Issue: What happened? Separate confirmed facts from assumptions.
Impact: What is affected, and what could happen if we wait?
What I have tried: What action has already been taken?
Blocker: What prevents me from resolving this within my authority?
Options: What realistic choices are available? Do not invent extra options.
Recommendation: What do I suggest, and what support would it require?
Decision needed: What exactly do I need you to decide, and by when?
Follow through: Who will act after the decision, and when is the next update?
It is acceptable to write, “I do not yet have a reliable option because…” and identify the missing information or expertise. The decision you need may be permission to investigate. A short, honest request is more useful than a confident recommendation built on guesses.
A worked example of a routine escalation.
Illustrative example: a required internal review is pending before a client presentation. “The review is pending. Please advise.” leaves the manager to reconstruct the situation. I would prefer a note like this, using the organisation’s actual names and decision deadlines.
Subject: Decision needed on presentation review by [decision deadline].
Issue and impact: The required review has not been completed. The presentation is due at [client meeting time]. We cannot release the material without the required approval.
What I have tried: I sent the review request at [time] and followed up at [time]. Completion remains unconfirmed.
Blocker and options: I cannot appoint a reviewer or revise the client timetable. The options are an authorised backup reviewer or an agreed revised timetable. Neither is approved yet.
Recommendation and decision: I recommend the backup only if you confirm their authority and availability. Please choose the authorised route by [time], or tell me what else you need to decide.
Follow through: [Project owner] will communicate the confirmed decision. The next update is at [time and channel].
The employee has made the decision easier to assess without assuming the manager’s authority. The note also preserves uncertainty: a possible backup is not a confirmed reviewer. If neither option is feasible, the manager needs to set a different route rather than treating the recommendation as an instruction already issued.
When the full template should wait.
If waiting could increase serious harm, raise the concern through the appropriate urgent channel now. Supply fuller context after receipt. Existing emergency and incident procedures take priority. Do not wait for perfect evidence, a recommendation or help from AI.
An immediate safety concern belongs on the designated emergency route. A suspected security incident belongs on the organisation’s incident-reporting route; share sensitive details only with authorised recipients. Take only safe actions within your authority. A routine email is unsuitable when the urgent procedure requires a direct call.
Sensitive complaints should follow designated reporting procedures. If the manager is involved, an independent reporting route may be needed. Confirm the alternative contact through the organisation’s policy. This template does not promise anonymity or legal protection.
Urgent concern: [what I have observed]
Possible impact: [what may be affected; state uncertainty]
Action already taken: [only safe and authorised actions]
Help needed now: [who needs to respond and how to reach me]
The manager needs a response template too.
Thank you for raising this.
My understanding: [brief confirmation]
Decision: [approved action, declined action with reason, or specific information needed]
Decision owner and deadline: [name and time]
Action owner: [who will do what]
Next update: [time and channel]
If the risk changes or I am unavailable: [designated backup route]
Acknowledging a message does not resolve its decision. If you need more information, identify what is missing and who will obtain it. If you cannot decide, name the person who can and confirm when they will take ownership. Otherwise the employee may read “noted” as permission to proceed.
I would resolve the immediate issue before coaching the quality of a routine escalation. A manager can challenge weak reasoning without humiliating the person who raised it. Ask what evidence supports the recommendation and what would change it. Keep that discussion separate from whether reporting the concern was welcome.
AHRQ’s healthcare guidance emphasises acknowledging raised concerns. Its mutual-support material also treats asking for assistance as compatible with responsibility. Those are useful principles to consider, not evidence validating this business template. Speaking up and acknowledgement; Mutual support in healthcare.
Agree what happens when nobody responds.
Agree response expectations for your organisation rather than copying universal deadlines. Keep the unresolved decision visible until responsibility is accepted. If the risk increases or the agreed response time passes, use the designated backup route. Do not let an unanswered message become an unspoken transfer of responsibility.
| Issue category | Decision owner | Response expectation | Backup route |
|---|---|---|---|
| Routine decision | [Authorised manager] | [Agreed decision time] | [Named alternate] |
| Urgent concern | [Designated responder] | [Existing urgent procedure] | [Emergency or incident route] |
| Sensitive complaint | [Designated reporting contact] | [Applicable reporting procedure] | [Independent route if needed] |
Where AI can help.
AI may organise authorised notes or flag a missing decision request. Use an approved tool with information you are permitted to share. I would use a bounded prompt like this:
Organise these authorised notes into our escalation template. Keep confirmed facts separate from assumptions. Mark missing information as unknown. Do not invent options or make the decision.
The employee verifies the final message against the source notes. The authorised manager retains the decision. AI does not replace urgent reporting, and a polished paragraph does not establish that its explanation is correct.
Read more about human accountability in AI workflows.
Introduce the standard without creating more paperwork.
I would trial the format with a small team using a recent anonymised issue. Ask the employee to prepare the note and the manager to answer it. Look for information that changed the decision, and remove fields that add effort without helping that review. Keep the urgent route visible throughout.
Review decision turnaround and unresolved items past their agreed deadlines. Also check whether urgent reporting has become slower. These are proposed measures, not promised improvements. Preparation should improve routine decisions while preserving early reporting of important concerns.