An urgent request lands while your manager is travelling, offline or in back-to-back meetings. The client wants an answer today. A colleague says the change is simple. You know the work, but you are not sure who can approve the decision. Waiting silently might cost the team time; deciding too much on your own might create a commitment nobody authorized.
The practical response is neither panic nor automatic escalation. It is to sort the request by urgency, authority and reversibility, then take the safest useful action you can own. This guide shows how to do that, what to write, and when an unavailable manager really does mean you must wait.
First, separate the deadline from the pressure
“Urgent” is often a description of how the requester feels, not a verified deadline. Ask what will actually happen if the answer arrives later. Is a customer waiting to make a purchase? Will a scheduled release miss a cutoff? Or would tomorrow simply be less convenient? This distinction matters because an urgent-looking message can sometimes wait for the next agreed decision point.
Ask for the consequence and the latest safe decision time. A useful reply is: “I can review this now. What happens if we confirm the decision at 2 p.m. rather than immediately?” That question is not resistance. It turns vague urgency into a specific constraint you can plan around.
Find out which part you can decide yourself
Break the request into three parts: information you can provide, reversible work you can start, and commitments that require authority. You can usually explain a documented process, check the current status, compare options, or prepare a draft without promising a client a new price or delivery date. The last two may need an authorized approver.
Do not confuse subject expertise with delegated authority. Knowing what solution would work does not mean you can approve expenditure, waive a contract term, change policy or accept a material risk. Check the existing approval matrix, project brief or previous decision record before assuming the manager is the only person who can answer. For a durable approach, see how to create an approval path before work gets stuck.
Use a simple decision ladder
Start with the lowest-risk action that moves the request forward. First, supply factual information that has already been verified. Second, complete preparatory work that can be changed without external consequence. Third, seek a named alternate approver for a choice outside your authority. Fourth, if the decision is irreversible or high-risk and there is no authorized substitute, hold that specific commitment and explain the next checkpoint.
The ladder keeps the entire task from freezing just because one approval is missing. A client proposal can be prepared while commercial terms remain unapproved. A project team can assemble the evidence while the final go/no-go decision waits. This is not a loophole around controls; it is a way to distinguish helpful progress from unauthorized action.
Check the agreed backup before escalating widely
Look for a designated deputy, project sponsor, duty manager, team lead or escalation contact. Identify what that person is empowered to approve. A backup for routine scheduling does not automatically have authority for spending or legal exceptions. If the route is unclear, ask the relevant operations or management contact who owns the decision rather than sending the same request to a large group.
When you ask for help, provide a short recommendation instead of forwarding a confusing thread. State what was requested, the constraint, the choice required, your proposed option and the latest useful reply time. The method in asking for help before you are completely stuck is especially useful when several people may be able to unblock one narrow issue.
Send an interim reply that does not invent approval
If the requester needs an answer before a decision-maker returns, acknowledge the request and distinguish confirmed facts from pending choices. For example: “I have checked the current delivery plan and can confirm the existing date. The proposed earlier date needs approval, so I am checking the authorized backup. I will update you by 3 p.m. with either a confirmed decision or the next decision point.”
This message provides useful information without implying the requested change is approved. Avoid phrases such as “should be fine,” “we can probably do that,” or “consider it done” when the remaining question affects cost, delivery or customer commitments. Readers may treat those phrases as promises even if you meant them as provisional reassurance.
Record your assumptions and the stop point
You may need to act with incomplete information. In that case, write down the assumptions behind any reversible preparation. For example: “Drafting the revised client timeline based on current capacity; not sending it until the launch-date change is approved.” That sentence shows the team what is happening and makes the boundary visible.
A stop point is the moment preparation would become commitment. It might be sending an external price, publishing a customer announcement, placing an order or changing a production system. Name that point before the work advances. If the approval is missing when you reach it, stop that step—not necessarily everything around it.
Handle conflicting urgent requests with an explicit trade-off
An unavailable manager can create a second problem: colleagues from different teams may each believe their request should come first. Do not promise both deadlines if the same person or resource is needed. Compare the concrete consequences, including the real cutoff, dependent work and work already promised.
Send a brief choice to the authorized decision-maker: “Request A has a client submission at noon; Request B needs a revised internal draft today. I can complete A first and move B’s review to tomorrow, or reverse the order if the customer impact is lower than expected. Which priority should govern?” For recurring shifts, use the approach in managing work priorities that keep changing to document what moved and why.
Escalate risks, not frustration
When a decision genuinely cannot wait, describe the operational exposure rather than how many messages have gone unanswered. A concise escalation identifies the blocked action, the business effect, the proposed decision and the latest safe response time. It also notes any reversible mitigation already underway.
For example: “We cannot confirm the revised customer shipment date without approval. If no authorized decision is made by 1 p.m., the courier cutoff will pass and the earliest confirmed dispatch remains Friday. The packing documents are ready. Can the duty manager approve the change, or should we retain the original commitment?” This is specific, answerable and neutral.
Update your manager without creating a long trail
Once your manager is reachable, send a compact record of what arrived, what you confirmed, what reversible work you completed, and which decision remains open. State whether anyone else approved the change. This protects the manager from having to reconstruct scattered chats, and it prevents an interim suggestion from becoming a false record of approval.
Keep the status useful even when nothing changed. The four-part structure in giving a status update with no progress—state, blocker, next action and checkpoint—also works when the main obstacle is an unavailable approver.
A ready-to-use response for the next urgent request
Use this as a starting point: “Thanks for flagging this. I understand you need [decision or deliverable] by [time]. I can confirm [verified fact] and prepare [reversible work] now. [Specific commitment] needs approval from [role]; I am checking the agreed backup. If approval is not available by [decision point], I will [safe fallback]. I will update you at [checkpoint].”
Before sending, check that the named fallback is real, the time is tied to a genuine dependency, and you have not accidentally promised something beyond your authority. If a policy or legal requirement applies, follow that requirement rather than relying on an informal response template.
Build a better backup process after the urgent moment
If this happens repeatedly, the problem is no longer just an unavailable manager. It is an unclear delegation system. Propose a one-page decision map listing routine decisions, authorized backups, spending or risk limits, and the place where approvals should be recorded. Add an escalation path for time-sensitive exceptions and a clear rule for what must never proceed on silence.
Review the map with the people who actually hold authority. Keep it short enough for staff to use under pressure. An effective backup is not an invitation to bypass judgment; it is a pre-agreed way to make ordinary decisions without turning every absence into a crisis.
Final takeaway
When your manager is unavailable, do not choose between total delay and unauthorized promises. Confirm the real deadline, separate preparation from commitment, follow the agreed approval path, record assumptions and give the requester a realistic checkpoint. You can keep work moving while respecting the decisions that are not yours to make.