Sponsors answer faster when a decision is easy to make and has a clear deadline. Send each decision on its own, with the ask first, then the options, your recommendation, what waiting costs, a respond-by date, and what you will do if no answer comes. Show open decisions in every status report and follow up on a schedule you agreed in advance.
Why do sponsors take so long to answer decisions?
Slow sponsor answers usually come from one of a few causes, in this guide's working view: the sponsor is overloaded, lacks information, is worried about the risk, or the call isn't theirs to make. Treat the list as a diagnosis, not a rule. Work out which cause fits before changing your approach, because each points to a different fix.
Dave Litten suggests starting by finding out why the sponsor isn't engaging, and making it easy for them to help. Extra reminders suit a busy sponsor; for the other causes, change the request itself. Use this table to match what you notice to a fix:
| What you notice | Likely cause | What to change |
|---|---|---|
| The sponsor replies "will look at this" and then goes quiet | Overloaded | Send a shorter request with a recommendation they can accept in one reply |
| The sponsor asks follow-up questions each round | Missing information | Put the evidence and trade-offs in the request itself |
| The sponsor asks you to "explore more options" | Risk concern | Spell out the downside of each option, including doing nothing |
| The sponsor says "I need to check with [name]" | Lacks authority | Ask who owns the decision, then send them the same request, copying your sponsor |
If you can't tell which it is, ask: "What would you need to see to make this call by [date]?"
What should a decision request include?
A decision request should let the sponsor decide without opening anything else. Lead with the decision and the date you need it by. Follow with the options, your recommendation, the evidence, what delay costs, and what happens if you hear nothing. Send one decision per message so a reply can't cover some items and skip the rest.
You don't have to invent this format. Rebel's Guide to PM gives a decision brief that covers the decision required, your recommendation, alternatives, trade-offs, evidence, what happens if no decision is made, and the date the answer is needed. The template below turns that into a message you can send:
Subject: Decision needed by [date]: [one-line decision]
[Sponsor name], I need your decision on [decision] by [date].
My recommendation: [option A], because [one-sentence reason].
Options:
- [Option A]: [what it means for scope, cost, or timeline]
- [Option B]: [what it means for scope, cost, or timeline]
- Do nothing: [what happens]
Evidence: [link or one-line summary of the work, test, or estimate behind this]
Cost of waiting: each [week/sprint] without a decision moves [deliverable] by [amount] and [other impact].
If I don't hear from you by [date], I will [default action], which sits within [the authority you gave me / our agreed tolerances]. Reply "A", "B", or "let's talk".
For a chat channel such as [chat tool], use the short version:
[Name], decision needed by [date]: [decision]. I recommend [A] because [reason]. If I don't hear by [date], I'll [default]. Reply A, B, or "let's talk".
Before you send either one, check the following. The subject line or first line should state the decision by itself. Your recommendation should come before the options. The default should be something you are actually allowed to do.
How do I show the cost of waiting in a status report?
Put a pending decisions section near the top of every status report. List each open decision with its owner, the date you asked, how long it has been open, the date you need it by, and what slips if it stays open. A pending decisions section makes the delay visible without anyone having to complain about it.
Rebel's Guide to PM recommends tracking pending decisions with owners and required-by dates and showing the impact of delay. Here is a block you can copy:
Pending decisions
| Decision | Owner | Asked | Open for | Needed by | If still open on [date] |
| [Decision] | [Sponsor] | [date] | [n days] | [date] | [Deliverable] moves to [date]; [team] idle on [workstream] |
Update the Open for column in every report. A decision that has been open a long time stands out on its own, and the sponsor sees it before anyone has to raise it. If you already use a short update format, slot this into it. BrightWork describes S-I-R (Status, Issues, Risks), and pending decisions fit naturally beside Issues.
Should I ask by email, chat, or wait for the sponsor meeting?
Send urgent, single decisions by email or the chat channel your sponsor prefers, and save linked or larger decisions for a fixed sponsor meeting slot. Agree the channel and the slot with your sponsor once, then keep every decision request in those places so the sponsor always knows where to find them.
Agree the setup with your sponsor once:
- Book a standing decision slot. Ask: "Can we keep [time] on [day] for decisions only? I'll send the list beforehand." BrightWork's sponsor meeting agenda includes reviewing pending decisions. Put that item first, not last.
- Send the pre-read early. Dave Litten advises keeping meetings focused on decisions and sending background reading beforehand.
- Pre-brief the big ones. Rebel's Guide to PM suggests discussing big decisions with the sponsor before the formal meeting. A brief call ("I'll be bringing [decision] on [date]; anything you'd want to see?") means the sponsor doesn't come in cold.
- Agree the channel for urgent asks. Ask: "When something can't wait for our slot, is email or [chat tool] better for you?" Then use only that channel.
Unblockd offers "asks to the sponsor by email with one-tap answers (no account), or answered by replying to the email."
How do I set a default answer without overstepping?
A default answer is fine only when the action is within authority the sponsor has already given you. Agree on default answers ahead of time, not halfway through a stalled decision. Then "if I don't hear by [date], we proceed with [option]" is a step you were already allowed to take, not a way of taking power.
Rebel's Guide to PM starts by advising you to know which decisions are yours. Dave Litten warns that taking over the sponsor's decisions leaves you accountable for things you were never given, and that temporary workarounds can become permanent without approval.
At the start of the project, or at your next sponsor slot, say:
"For decisions inside [tolerance, e.g. scope/budget/timeline limits we agreed], can we agree that if I've asked with a recommendation and a date and haven't heard back, I'll go with my recommendation and tell you? Anything outside that, I'll wait for you."
Write down what you agree and refer to it in each default line.
How do I follow up without nagging?
Follow-ups feel like nagging when they repeat the request with no new information. Each reminder should add something: what changed, what is now at risk, or a smaller version of the question. Agree the reminder schedule with the sponsor beforehand, so the schedule reads as the process you both set up and not as pressure.
Use a sequence like this, with the timing you agreed:
- [n working days] after sending: "Quick nudge on [decision]. Still recommending [option A]. Reply 'A' and we're moving."
- The day before [respond-by date]: "[Decision] is due tomorrow. If I don't hear, I'll [default]. If you'd prefer to talk, I can take a few minutes at [time]."
- On [respond-by date]: "No decision came through on [decision], so as agreed we're going with [default]. Let me know today if you want to change course."
If the decision is outside your authority and has no default, the last message names the impact instead: "[Deliverable] is now on hold from [date]. I'm adding it to the risk log and to [next sponsor slot]."
What do I do when there is still no answer?
Treat a missing sponsor decision as a project risk, not a personal frustration. Log it with its impact, raise it in the next status report, and if it is still open, take it to whoever the sponsor answers to. Tell the sponsor first, so they never find out from someone else.
This follows Dave Litten's advice to log sponsor disengagement as a risk described by its impact. Raise it early. As BrightWork puts it, "Sponsors dislike bad news, but dislike late bad news even more."
Steps:
- Add a risk entry: "Decision on [topic] open since [date]. Impact: [deliverable] moves to [date], [cost or team impact]."
- Tell the sponsor before you escalate: "I'm going to raise [decision] with [steering group/next level] on [date] so it doesn't hold up [deliverable]. Happy to bring your view if you'd like to share it first."
- Escalate with the same decision request format, so whoever picks it up can decide without starting over.
- Once the decision is made, record it. Rebel's Guide to PM recommends closing the loop by recording each decision afterward.
When is pushing for a faster decision the wrong move?
Pushing a sponsor for a quick decision is the wrong move when the decision should be slow: when it changes the business case, depends on facts still coming in, or needs other leaders to agree. In those cases, ask for a decision date and an interim instruction for the team instead of an immediate answer.
Rebel's Guide to PM suggests matching the decision process to the decision, being explicit about uncertainty, and using ranges instead of false precision. When a sponsor holds back for good reason, ask: "What should the team do until you decide, and by when will you know?" You get a next step for the team without forcing a premature call.
Show the agreement in your status report, so the Open for count doesn't make a deliberate pause look like a stalled decision:
| [Decision] | [Sponsor] | [date] | Deferred by agreement until [date]; interim instruction: [x]. |
What can I do this week?
This week, list your open decisions, rewrite the oldest one as a clear decision request, and add a pending decisions section to your next status report. Then ask your sponsor for a standing decision slot and agree the tolerances for default answers. Each step uses the tools and meetings you already have.
- List every open decision with its owner, the date you asked, how long it has been open, and the date you need it by.
- Rewrite the oldest one using the decision request template and send it.
- Add a pending decisions section to your next status report.
- Ask your sponsor for a standing decision slot and agree which channel to use for urgent asks.
- At that slot, agree on the tolerances within which a default answer applies.