Guides /

Customer sponsor not responding: what to do next

When a customer sponsor won't decide, confirm who can close it, send one brief, escalate in steps, and keep a stall log. Templates for each step are included.

By The Unblockd teamPublished

When a customer sponsor stops answering implementation decisions, start by confirming who can actually close each open decision. Send that person one decision brief with options, a dated ask, and a stated default. If the date passes, escalate through the customer's own governance, and keep a stall log so the delay is on record. The guides cited below are opinion and advisory pieces. In our review, none reports outcome data for these steps, so treat them as practice to test, not proven method.

Who actually owns each open decision?

The person who can close each blocked decision may not be the silent sponsor. Before chasing anyone, list each open decision and ask the sponsor in writing who on their side can make the call if they are unavailable by a set date. In our view, the project lead prepares the decision and the customer closes it.

AABDC's guide on executive ownership draws the same line: decision preparation can be delegated, but decision closure cannot.

  1. Open the project plan and list every decision the team is waiting on. For each one, write the decision, the date the work needs it, and the sponsor it was assigned to.
  2. Add a column called "Who can close it". Leave it blank where you do not know.
  3. Ask the sponsor in writing: "[Sponsor name], for [decision], who on your side can make the call if you are not available by [date]?"
  4. Sort each blocked item into one of the groups below.

In our view, the group decides your next move:

  • The sponsor has authority but not time. Shorten the brief and ask the sponsor to name a delegate.
  • The sponsor has named someone. Move the item to that person, and ask the sponsor to confirm the handover in writing.
  • The options were never framed as a choice. Rewrite your brief. A reminder will not fix it.

Only the last group is fixed by changing your own work. The first two need a different person on the other end.

How do I write a decision brief a sponsor can answer quickly?

A decision brief states one decision in a line, gives the options and their effects, names your recommendation, sets the date an answer is needed, and says what happens by default. Founded Partners recommends a written update that states the decision needed, its consequence, and a response date the governance has agreed.

In our view, one decision per brief gets a quicker answer than a long deck, because the sponsor can reply with a letter or a yes or no. Use this wording and replace each bracket:

Subject: Decision needed by [date]: [decision in a few words]

[Sponsor name],

We need a decision on [decision] to keep [deliverable] on track for [milestone date].

Option A: [option]. Effect: [what it changes on the timeline or scope]. Option B: [option]. Effect: [what it changes].

We recommend [option], because [one plain reason].

If we do not have your answer by [date], we will proceed with [default option], as agreed in [governance note or meeting]. You can change that at any point before [date].

Reply with A or B, or tell us who should decide. [Your name], [role]

Unblockd helps projects deliver faster by taking what's stuck to the sponsor who can clear it, and the ask arrives by email with one-tap answers (no account), or answered by replying to the email.

What default should I state if the sponsor stays silent?

State a default only when the customer's governance or the contract already lets the team proceed on it, and say so in the brief. Founded Partners advises against treating silence as approval, so log any default you apply as a default, not as a decision the sponsor made.

  • Confirm with the contract owner or the agreed governance note that the default is allowed.
  • Choose the default that is easiest to reverse. In our view, a reversible default is the safer one to apply.
  • Write down what the default changes and what would change it back.
  • Log it as applied, and state it in your next written update to the sponsor.

How do I escalate through the customer's governance?

Escalate in steps, each to someone who can close the decision, through the customer's steering or governance forum. Move to the next step only after the date in your brief has passed. Write each step's date into the governance note at kickoff or later, so the escalation is expected.

Renascence recommends a steering cadence the sponsor cannot skip and written decision rights, so that disputes become escalations. BuildBetter's implementation-plan guide says escalation thresholds should be agreed in advance, and that without an executive sponsor the escalation path is "useless." In our view, the ladder below is practice to test, not a method either source proves.

  1. Follow up with the sponsor using the same brief, with the passed date noted. Ask for a named delegate or a decision by [new date].
  2. Put the item on the agenda of the next steering or governance meeting, or take it to the delegate the sponsor named. Attach the brief.
  3. Ask the sponsor in writing whether someone more senior on the customer side should own the decision. Copy the sponsor on that message.

For step 1:

Subject: Following up: [decision], due [date]

[Sponsor name], the decision on [decision] was due on [date], and [deliverable] is waiting on it. The brief is below. Could you make the call by [new date], or name someone who can?

For step 2, as an agenda item:

Decision needed: [decision]. Owner: [name]. Needed by: [date]. If late: [deliverable] moves to [date]. Ask: [the specific choice the meeting should make].

For step 3:

[Senior name], I am writing about [decision] on [project]. [Sponsor name] has been our contact, and we do not yet have a decision. The brief is attached. We need an owner for this by [date]. [Sponsor name] is copied on this message.

How do I raise a silent sponsor without blaming them?

Describe what is waiting and what it affects, not the sponsor's behavior. Write that the decision has not been made and which deliverable it holds, instead of writing that the sponsor has not replied. Rework's at-risk guide lists an unresponsive executive sponsor as a warning sign of a cooling relationship, so treat the silence as information about the engagement.

A neutral opening line looks like this: "The decision on [decision] has not been made yet. [Deliverable] is held until it is, and we would like to agree a date with you."

When should I send a pause notice?

Send a written pause notice when a decision stays open past the agreed escalation date and the work behind it cannot move without it. The notice names the deliverables held, the decision holding them, and the date work resumes. Check the wording with the contract owner, because what a pause means for dates and fees depends on the contract.

Subject: Work paused on [deliverable] pending decision on [decision]

[Sponsor name], the decision on [decision] was needed by [date] and has not been made. [Deliverables] cannot move forward without it, so we are holding them from [date]. Work on [other items] continues. We will resume [deliverables] within [number] working days of receiving the decision. We will confirm the date for [milestone] by [date].

How do I keep a stall log that protects the timeline?

A stall log is a dated record of each open decision, each ask, each escalation step, and the work the delay touched. Keep its entries neutral, such as "no response recorded by [date]", and link them from the change log whenever a date moves.

Use these columns: date, decision, ask sent (date and recipient), response or none recorded, escalation step, work affected, and next date. An illustrative row with placeholders:

[date] | [decision] | Brief sent to [sponsor name] | No response recorded by [date] | Escalation: [step name] | [deliverable] held from [date] | Next: [date]

Write "no response recorded by [date]", not "sponsor failed to respond". The first is a fact you can show in a contract discussion. The second starts an argument about the sponsor.

What if the sponsor cannot make decisions at all?

Ask the customer in writing to name a co-sponsor or replacement, and list the decisions that person will now hold. AABDC's guide says the sponsor may need to change and that the handover should be deliberate, so use the stall log to show which open decisions the new person inherits. Renascence recommends bringing in a co-sponsor from another function.

What mistakes should I avoid?

The costliest mistake is treating a vague reply as a decision, such as "looks fine, we will see." Ask for the option letter or a yes or no in writing, and record the reply in the stall log as a reply, not as a decision. Other errors are chasing on several channels at once, which blurs who was asked what, and moving work forward on a default without writing that you did. Pick one written channel and keep the brief the same each time.

What else do project leads ask about a silent sponsor?

The questions below cover whether you can decide yourself, how long to wait before escalating, and what to do when the sponsor replies with a question. Each short answer draws on the steps above, so the same brief and dates run through the whole sequence.

Can the project lead make the decision myself?

Only if the customer's governance or the contract already gives you that authority for this kind of decision. Otherwise, ask the customer to name the person who can close it. Preparing the decision is usually your job, and closing it is theirs.

How long should I wait before escalating?

Wait until the date in your decision brief has passed, then move to the next step. Agree the dates with the customer at kickoff or in the governance note, so the escalation is expected rather than a surprise.

What if the sponsor replies with a question instead of a decision?

Answer the question in one or two sentences, restate the decision, and ask for an option letter or a yes or no by a named date. Keep the same brief so the decision stays in one place.

Is a stalled sponsor a reason to end the engagement?

Ending an engagement is a decision for the parties under the contract, not a project lead's call. Before that conversation, the stall log and escalation record show what was tried and when.

What should I do first this week?

Start by listing every open decision the team is waiting on, then confirm who can close the oldest one. Put that question to the sponsor in writing today, using the wording from the ownership step, and set the date for the decision brief.

Questions people ask

Should I copy the sponsor's manager on the first ask?

Not on the first ask. Follow up with the sponsor first, using the same brief. Copy a more senior person only when you reach the step that asks for someone senior to own the decision, and tell the sponsor you are doing so.

How do I tell whether the sponsor is the real decision-maker?

Ask in writing who on their side can make the call. If the reply names someone else, the decision belongs with that person for this item. Record the reply in the stall log.

Can I use the same decision brief for every follow-up?

Yes. Keep the decision, options, and recommendation the same so the customer sees one decision in one place. Change only the note that the date has passed and the new date you ask for.

The Unblockd team

Unblockd helps teams deliver projects faster by getting stuck work in front of the sponsor who can clear it: an AI agent drafts the ask from the project's evidence, the team checks and sends it, and the sponsor answers without signing up.

Get the sponsor ask checklist

One screen to check before you send an ask: the decision, the options, the date, and what waits on it. Then one email a week with new guides.