Guides /

How to send a project status update before a client call

Learn when to send the sponsor's written status update before a client call, when the lead should review it first, and how to ask for decisions in advance.

By The Unblockd teamPublished

Send the sponsor's written status update on a date counted back from the client call, after the sponsor's agreed reply window and the lead's review. Send the lead the internal draft first, so the status and wording are checked before the sponsor reads them. Put decisions at the end of the update, and open the call with them.

When should the written status update reach the sponsor?

Send the written status update to the sponsor on a date you count back from the call, not on a default weekday. Work back in this order: the sponsor's reply window, then the lead's review, then drafting time. Agree the reply window in the project thread before you draft.

Team rule: set the sponsor send date [number] working days before the call, and write that number in the project thread with the call details. Choose a number large enough to cover the sponsor's reply window and the lead's review. If the sponsor has already named a window, use theirs.

Work back from the call in this order:

  1. Write down the call name and the call date.
  2. Subtract the sponsor's reply window, the time the sponsor needs to read the update and answer. Use the window the sponsor gave in the thread, or [agreed reply window] if the sponsor has not said.
  3. Before that date, leave a slot for the lead's review. Before that, leave a slot for drafting.
  4. Add [draft date], [lead-review date], and [sponsor send date] to your calendar as tasks linked to the call invite.

Ask once, in the project thread, with the call details filled in:

Could you read a short status update before our [call name] on [call date]? It lists the decisions I need from you, and a reply by [reply date] would help.

If your updates already follow a set weekday, move the send to fit the call instead of the weekday.

Should the lead see the internal version a day earlier?

Yes. Send the internal draft to the lead the day before the sponsor send, so the lead can check the status against the project record and move any team-only item out before the sponsor reads it. Treat the day-before order as our suggestion, not a rule from the guides we compared.

The reasons are practical:

  • The lead checks the status line against the tasks, evidence, and decisions in the project record.
  • The lead can move a team-only item out of the sponsor version before the sponsor reads it.
  • The sponsor gets the update with enough time to reply, because the sponsor send date is set in advance.

Kalvium defines a blocker as something the client must resolve. Use that test during the lead review: an item the sponsor cannot resolve belongs in the team's notes, not the sponsor version.

Send the lead the same draft with a short note, and set the lead-review date when you plan the call:

[Lead name], the draft for the [call name] on [call date] is below. Please check the status line and the decisions in the last section by [lead reply date]. I will send the sponsor version on [sponsor send date], after your reply.

In what order should the steps run?

After the dates are set, run these actions in order: send the sponsor version on its date, check replies, run the pre-call check, then open the call with the first decision. Keep the sponsor send after the lead's reply, so the review is never skipped.

Before the sponsor send date, the lead's changes are in and any item that needs the sponsor's decision is in the decisions list. Then:

  1. On [sponsor send date], send the sponsor version in the project thread, and ask for a short reply by [sponsor reply date].
  2. On [sponsor reply date], check for replies and update the status line if a reply changes it.
  3. Before the call, run the pre-call check in the section below.
  4. On [call date], open the call with the first decision on the list.

The dates are the team's working plan, not a measured result. If the lead has not replied by [lead reply date], use the fallback in the FAQ.

What should the written update say first?

The written update should open with the status line, then what changed, the next steps with owners and dates, and last the decisions or help needed. Use that order on every update, so the sponsor knows where to look each time.

**Subject:** [Project name] status before [call name] on [call date]

**Status:** [status label, such as On track, At risk, or Needs decision]. [A few sentences on what this status means now.]

**What changed since [last date]**
- [Deliverable or result, named by its state]
- [Confirmed change to timing, scope, or owner]

**Next steps**
- [Owner], [action], [date]

**Decisions or help needed**
- [Decision], needed from [sponsor name] by [date]. If it stays open, [plain consequence].

**For the call**
- [Question or item to discuss live]

Name results, not effort. Write "the [deliverable] is ready for [reviewer] review" rather than "the team worked on [deliverable]." Sydnee's client template uses the same order and says to write the status before the explanation. Sydnee also defines status labels with usage criteria, and Kalvium uses labels such as On track, At risk, and Needs decision. Use a label only when you can explain it in a plain sentence. Read the status line and the sentence after it together before you send, so they say the same thing.

What does the written update settle, and what does the call settle?

The written update settles what the sponsor can answer from reading: the status, the changes, and each decision with a deadline. The call settles what needs back-and-forth: questions the sponsor raises after reading, and any decision that needs discussion first. Keep each item in one place, so the sponsor does not answer the same question twice.

Examples, with placeholders:

  • Written: "[Decision], needed from [sponsor name] by [date]: [option A] or [option B]." Call: the sponsor asks what [option B] would change, and the team talks through the trade-off live.
  • Written: the status line reads "[status label]", with the reason in one sentence. Call: the sponsor asks why the status changed, and the lead explains from the project record.
  • Written: "[Blocker] needs [sponsor name] to [action] by [date]." Call: the sponsor proposes a different owner, and the team agrees the change before the call ends.

If a decision is still open after the call, record it in the recap with a new date.

How do you get a decision from the sponsor before the call?

To get a decision before the call, name the decision, give a date, list the options side by side, and state the plain consequence of waiting. The sponsor can then answer in a short reply. Send each request in the same thread as the status update.

[Decision], needed by [date]: [option A] or [option B]. If this stays open, [plain consequence, such as the date that moves].

Sydnee turns vague blockers such as "waiting on client" into specific, dated decision requests. Use the same wording in the status update's decisions list, so the sponsor sees one request, not two.

When the sponsor replies, move the decision from the decisions list into what changed. Update the status line if the answer changes it, then log the reply in the thread.

What if bad news comes up just before the call?

The lead sends the sponsor a short written flag as soon as the bad news is confirmed, then asks to talk it through live. The flag makes sure the sponsor hears the news before the meeting and knows what the call is for. The lead does not hold it for the next scheduled status update.

Subject: [Project name]: [issue] before our call

[Sponsor name], I want to raise [issue] before [call name] on [call date]. What we know: [facts]. What we are doing: [action, owner]. What we need from you: [decision or help] by [date]. I would like to talk it through on the call, and I will bring [options].

The lead writes and sends the note, and decides how much detail it includes.

Kalvium names significant bad news as a case where a call beats writing. The same page's status labels can be read as calling for an early written flag, and the page does not reconcile the two, so the order here is our judgment. If the sponsor asks for a call sooner, book it in the same thread.

How do you turn the update into a call agenda?

Build the call agenda from the decisions and questions at the end of the update, with decisions listed first. Send the agenda in the project thread before the call, so the sponsor can see what the meeting is for and what to decide.

  1. Decisions needed: [decision], owner [name], by [date]
  2. Items the sponsor can clear: [item]
  3. Questions from the sponsor's reply: [question]
  4. Next steps: confirm owners and dates

If the sponsor has read the update, skip its status items on the call. If the sponsor has not read it, use the note in the next section first.

What if the sponsor does not read the update before the call?

If the sponsor has not read the update by the agreed check, send a short note in the same thread asking for a reply on the first decision, and open the call with that decision. The decision's stated consequence still applies whether or not the sponsor replies.

  1. On [sponsor reply date], send a note in the same thread: "Could you reply with [decision] or 'no change' by [date]? The rest can wait for the call."
  2. Record the reply, or the lack of one, in the decisions list. If there is no reply, the decision stays open.
  3. At the start of the call, say: "The first item is [decision]. Is anything in the update unclear before we start?"

What do you send after the call?

After the call, send a short recap in the same thread that lists each decision with its owner and date, plus the items still open. Send it soon after the call, while the wording is fresh, and let the recap be the team's record of what was agreed.

Subject: [Project name]: decisions from [call name] on [call date]

Decisions made

  • [Decision], owner [name], by [date]

Open items

  • [Item], owner [name], next step [action], by [date]

Next steps

  • [Owner], [action], [date]

Reply in this thread by [reply date] if anything above is wrong.

Carry each decision into the next status update under what changed, so the sponsor can see it closed.

What mistakes should you avoid?

The common mistakes are sending the sponsor version without the lead's review, sending it on the morning of the call, and using one version for both the sponsor and the team. Each one leaves the sponsor too little time to reply, or puts team-only material in front of them.

  • Do not send the sponsor version in place of the lead's review. If the lead is unavailable, use the fallback in the FAQ.
  • Do not send on the morning of the call. A send that late leaves no room for a reply to change the status line.
  • Keep team-only detail in the team's own notes. The sponsor version holds only the status, changes, decisions, and questions the sponsor can act on.

What do you check before the call starts?

Before the call starts, confirm that the sponsor version matches the draft the lead approved, that every decision has an owner, a date, and a consequence, and that any sponsor reply is in the status line. Fix anything that fails before the call opens.

  • The sponsor version matches the draft the lead approved.
  • Each decision has an owner, a date, and a plain consequence.
  • Any sponsor reply is reflected in the status line.
  • No internal-only notes remain in the sponsor version.
  • The call agenda lists decisions first, as set out in the agenda section.

If an item fails, tell the sponsor in the thread when the change affects a decision they need to make.

What should you do next?

Send the sponsor a request in the project thread now, using the sentence in the timing section, and fill in the call name and call date. Once the sponsor replies, count back from the call to set every date that follows. Send it before you draft anything else, because the sponsor's reply window sets every other date.

Questions people ask

What if the lead is not available to review the draft?

Agree a fallback in the project thread before the sponsor send date. Name a second reviewer, or hold the sponsor send until the lead replies. Do not send an unreviewed update to the sponsor in the lead's place.

Which status label should I use?

Use a label only when you can explain it in a plain sentence. [Sydnee defines status labels with usage criteria](https://sydnee.app/blog/insights/client-project-status-update-template), and [Kalvium uses On track, At risk, and Needs decision](https://www.kalviumlabs.ai/blog/ai-project-status-update-clients-actually-read/). Pick the set your sponsor already reads, so the labels stay the same from one update to the next.

What if the call date moves after the update is sent?

Tell the sponsor in the same thread with the new date. If the status or decisions have changed, send the lead the revised draft first, and send the sponsor the revised version only after the lead's reply.

What if the call is cancelled after the sponsor has the update?

Send a short note in the same thread saying the call is off. Keep each open decision with its date and consequence until the sponsor replies.

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.