The Splice field guide
Status Update Email Template: Progress, Blockers, Decisions
A practical status update email template guide: on-track, blocked, and uncertain states with source-of-truth tables, decision deadlines, and AI drafting tips.
13 min readBy Splice Work
Project emails can fail when the person writing them tries to make things sound better than they are. A delivery date can appear "on track" in the email when it has already moved. A blocker can be softened into a "minor dependency." Consider the stakeholder who needs to make a call by Thursday but never finds out they're the one holding things up.
This guide gives you three ready-to-use versions of a status update email template—one for each honest project state: on-track, blocked, and not-yet-verified. Each sits beside a compact source-of-truth table so you can check every sentence before you send.
This is about periodic project reporting by email. Not daily standups. Not launch announcements. The kind of update you send weekly or fortnightly to the people who funded, depend on, or need to decide something about your project.
Your turn · A one-minute experiment
Which sentences in this status update hold up against the source record?
Fictional one-minute exercise. All project names, people, dates, and figures below are invented for practice.
The situation
FICTIONAL PROJECT STATUS SCENARIO Business: Caldwell Events Ltd. (fictional) Project: venue booking platform rollout Project lead: fictional character Nadia Ferris Stakeholders: Operations Director (fictional: Tom Alcott), Finance Director (fictional: Beth Oren) Period: week ending Friday, 17 January SOURCE-OF-TRUTH TABLE (from the actual task board): — Completed: payment gateway integrated and tested by Dev lead Osei (confirmed done) — In progress: vendor directory import — 140 of 300 records loaded, 160 still to go — Blocker: mapping file from Beth's finance system not yet received; 160 records on hold — Decision needed: Beth must approve the revised data-mapping schema by Wednesday 22 Jan to hold the go-live date of 31 Jan — Delivery date: 31 Jan — originally proposed, not yet confirmed; status at risk if decision slips DRAFT EMAIL EXCERPT (written by Nadia before the checklist): 'Good progress this week — the payment gateway is live and the vendor directory import is nearly complete. We are on track for the 31 January go-live. No major blockers at this time. A small data-mapping item is being sorted and should resolve itself shortly. No action needed from stakeholders this week.'
Choose what you would do, then open it to see the reasoning. You can explore every option.
Check · The sentence 'payment gateway is live' is supported by the source record.
The source-of-truth table confirms the payment gateway was integrated and tested by Osei and is marked as confirmed done. The article's checklist states that every completed item must be 'confirmed done, not nearly done.' This sentence holds up — it accurately reflects the task board entry without overstating or softening.
Check · 'Vendor directory import is nearly complete' accurately describes the import status.
This sentence does not hold up. The source record shows 140 of 300 records loaded with 160 still to go — just under half complete, not nearly complete. The article warns against softening blockers or progress into vague reassurance. 'Nearly complete' is an optimistic gloss on a figure that is closer to half-done, and it obscures the fact that the remaining 160 records are actively blocked.
Check · 'We are on track for 31 January' accurately describes the delivery date status.
This sentence does not hold up. The source record marks the 31 January date as 'at risk if decision slips' and labels it as originally proposed, not confirmed. The article is explicit: delivery dates must be labelled as proposed, confirmed, or changed — never stated without qualification. Presenting an at-risk proposed date as on-track misinforms stakeholders who may need to act to preserve it.
Check · 'No action needed from stakeholders' is accurate given the source record.
This sentence does not hold up. The source record explicitly requires Beth to approve a revised data-mapping schema by Wednesday 22 January to hold the go-live date. The article's blocked-update template is built around naming the decision-maker and the deadline precisely because stakeholders cannot act on a blocker they have not been told about. Saying no action is needed when a named decision has a four-day deadline is the clearest possible failure of an honest status update.
A status update email is only as honest as its weakest sentence. Vague hedges like 'nearly complete' and 'no major blockers' replace specific facts with optimism. The source-of-truth table exists to catch exactly this: every sentence in the email should trace back to something the record actually says.
The Source-of-Truth Table: Build This First
Before you open your email client, make a short table. Three columns is enough.
| Item | What the record actually says | Owner |
|---|---|---|
| Period covered | Week ending [date] | — |
| Completed this period | List only confirmed done items | — |
| In progress / next step | What starts or continues next | Named person |
| Blocker | Specific, concrete, owned | Named person |
| Decision needed | Who decides, by when | Named person |
Fill this from your actual project log, task board, or whatever record your team keeps. If a field is blank because you don't know yet, write "not yet confirmed" rather than leaving it empty or inventing an answer.
This table is the check you run before AI drafts anything, and the check you run again after.
Three Templates You Can Copy Today
Each template below is built from the same fictional project: a website migration for a company called Meridian Foods, run by project lead Priya Okonkwo, with a stakeholder group that includes the head of operations and the finance director. The period covered is the week ending Friday, 3 October.
Template 1: On-Track Update
Source-of-truth table (Meridian Foods, week ending 3 Oct)
| Item | Record says | Owner |
|---|---|---|
| Completed | DNS records transferred; staging environment signed off | Dev: Sam |
| Next step | Content migration begins Monday 6 Oct | Content: Aisha |
| Blocker | None at this time | — |
| Decision needed | None this week | — |
Subject: Meridian Foods site migration — week ending 3 Oct | On track
To: Head of Operations, Finance Director CC: Sam, Aisha
Summary: Migration is on schedule. No blockers. No decision needed this week.
Hi Claire, Raj,
Period covered: Week ending Friday, 3 October.
Completed this week:
- DNS records transferred and verified
- Staging environment reviewed and signed off by Sam
Next step: Content migration begins Monday 6 October. Owner: Aisha. Estimated completion: Wednesday 8 October, subject to content team availability (not yet confirmed).
Blockers: None.
Decision needed: None this week.
Next update: Friday 10 October.
Priya
Two things to notice. First, "estimated completion: Wednesday 8 October, subject to content team availability (not yet confirmed)" — that hedge is honest and appropriate. The date is a working estimate, not a commitment. Second, there is no percentage. Percentages without a clear basis ("we're 67% done") are invented reassurance. If your project management tool calculates completion automatically from tasks, you can cite that figure and its source. Otherwise, leave it out.
Template 2: Blocked Update
This is where it is tempting to reach for diplomatic fog. Resist it. A blocked project needs a named blocker, a named owner, and a decision deadline that's specific enough to mean something.
Source-of-truth table (Meridian Foods, week ending 3 Oct)
| Item | Record says | Owner |
|---|---|---|
| Completed | Content migration: 60 of 90 product pages moved (task board count) | Aisha |
| Blocker | Supplier image library access not granted; 30 pages on hold | Raj (Finance) to approve vendor contract |
| Delivery date | Previously proposed: 10 Oct. Status: at risk, not yet revised | Priya |
| Decision needed | Contract approval by Raj by Tue 7 Oct to hold original date | Raj |
Subject: Meridian Foods site migration — week ending 3 Oct | Blocked: decision needed by Tue 7 Oct
To: Head of Operations, Finance Director CC: Sam, Aisha
Summary: Content migration is partially blocked. 30 pages are on hold pending supplier image access. Contract approval is needed from Raj by Tuesday 7 October to avoid a delay to the go-live date.
Hi Claire, Raj,
Period covered: Week ending Friday, 3 October.
Completed this week:
- 60 of 90 product pages migrated (source: project board, verified this morning)
Blocker: The remaining 30 pages require images from the supplier library. Access is gated on a vendor contract that has not yet been approved. Owner of the approval decision: Raj (Finance Director).
Decision needed — by Tuesday 7 October: Contract approval from Raj. If approved by Tuesday, the content team can complete migration by Thursday 9 October, and the original go-live date of 10 October remains achievable.
If the decision slips past Tuesday: The go-live date will need to be revised. I will send a revised schedule as soon as I have confirmation either way.
What I am not doing: I am not revising the go-live date in this update, because the original date is still achievable if the decision is made on time. I will update you by end of day Tuesday.
Next update: Tuesday 7 October (earlier than usual, given the decision point).
Priya
Notice the explicit paragraph about what the sender is not doing — and why. That prevents the stakeholder from reading "10 October" as a confirmed date and the project lead from inadvertently promising something they can't control.
Template 3: Not-Yet-Verified Update
Sometimes you genuinely don't know the state of something when the update is due. A dependency hasn't reported in. A test result is pending. The right move is to say so, rather than filling the gap with optimism.
Source-of-truth table (Meridian Foods, week ending 3 Oct)
| Item | Record says | Owner |
|---|---|---|
| Completed | DNS transfer complete | Sam |
| Pending verification | Staging sign-off: review meeting scheduled Mon 6 Oct, outcome not yet known | Sam / Claire |
| Next step | Content migration start date depends on staging outcome | Aisha |
| Delivery date | 10 Oct originally proposed. Status: dependent on Mon review outcome | — |
| Decision needed | None until staging outcome is known | — |
Subject: Meridian Foods site migration — week ending 3 Oct | Staging review pending
To: Head of Operations, Finance Director CC: Sam, Aisha
Summary: DNS transfer is complete. Staging sign-off is scheduled for Monday 6 October; I cannot confirm next steps or the delivery date until that review is complete.
Hi Claire, Raj,
Period covered: Week ending Friday, 3 October.
Completed this week:
- DNS transfer complete and verified
Not yet confirmed: The staging environment review is scheduled for Monday 6 October. I do not yet know the outcome. Content migration and the go-live date depend on that review.
What happens Monday: Sam and Claire will review staging. I will send a short follow-up update by end of day Monday with the outcome and revised next steps.
Blocker: None confirmed. Staging review outcome is pending, not blocked.
Decision needed: None until Monday.
Priya
How a Changed Date Differs from a Proposed Date
This trips up a lot of teams, so it's worth its own section.
- Proposed date: A working target, not yet committed. Use language like "the proposed go-live date is 10 October, subject to staging sign-off."
- Changed date: A previous commitment has moved. Name what moved it, by how much, and what the new date is. "The go-live date has moved from 10 October to 17 October. Reason: staging review identified three content errors requiring correction. Owner: Sam."
Never silently swap one date for another in an email without labelling it as a change. Stakeholders notice when dates shift without explanation; it can significantly erode trust.
AI Drafting: What It Helps With and What It Can't Fix
Tools like Microsoft Planner Agent can generate status report drafts from your plan data — pulling task completion, dates and owners from the plan automatically (Microsoft support documentation). As of its general availability rollout, it works with both shared basic plans and shared premium plans, and requires a Microsoft 365 Copilot licence and a minimum of ten tasks.
Google's Workspace AI prompts guide suggests structuring project update prompts around accomplishments, challenges, and next-week priorities (Google Workspace).
Both approaches share the same constraint: the draft is only as accurate as the data you put in. If your task board says "content migration: in progress" when it's actually blocked on a vendor contract, the AI will draft an update that sounds plausible and is wrong.
The practical rule: fill your source-of-truth table first. Feed the table to the AI. Review the draft against the table line by line before you send. The AI is helping you structure and phrase; it cannot verify.
Archived Microsoft release-plan documentation from 2023 noted that project managers reported spending two to three hours per status report on manual assembly (archived Microsoft Dynamics 365 release plan, 2023 wave 2, not current documentation). That figure is from archived material and is offered as illustrative context only — but if that time range resonates, it suggests where the friction usually lives: pulling data from multiple places, not the writing itself.
For teams sending the same email status update template weekly across multiple projects, the bottleneck is often data assembly — for teams pulling information from multiple systems. Solving that with an AI draft tool doesn't help if the underlying record is incomplete.
Review Checklist Before You Send
Run through this before every update:
- Period covered is stated explicitly (start and end date)
- Every completed item is confirmed done, not "nearly done"
- Next step has a named owner and an honest estimate (or says "not yet confirmed")
- Blocker is specific: what, why, who owns the resolution
- Decision needed has a named decision-maker and a deadline
- Delivery date is labelled as proposed, confirmed, or changed — never silent
- No invented percentages without a traceable source
- Executive summary (one sentence) matches the body of the email
- Recipients are appropriate — stakeholders who need this, not everyone
When the Update Itself Is the Bottleneck
If you're assembling a project status email every week from three different tools, a task board, and someone else's verbal update, the template above is a fix for the format. The deeper problem is the assembly process.
Teams with recurring, structured reporting workflows — where the same fields are pulled from the same systems every week — are candidates for an automated drafting step. The agent reads what the system contains, populates the source-of-truth fields, drafts the email, and holds it for a person to review before it goes anywhere.
This isn't an off-the-shelf product for project reporting specifically, but it describes what a custom-built reporting workflow can do. Splice Work's custom AI solutions service is built for exactly this kind of problem: a team with an existing process and existing software that needs an agent reading, deciding and drafting — with a person approving before anything is sent.
The illustrative workflow on that page shows a Slack or Microsoft Teams change request loop, which gives a sense of how a team would interact with a custom-built agent on an ongoing basis. The custom AI solutions page is explicit that the agent drafts and a person approves; no automation replaces the human check before the update goes out.
If your team is spending hours each week on status report assembly, the question worth asking is whether the data already exists in your systems and the bottleneck is pulling it together — because that's a solvable problem.
Try This Now
Take one real project you're currently reporting on. Fill the source-of-truth table at the top of this article from your actual project record — not from memory. Then ask yourself: which of the three states above is this project actually in? Pick the matching template, replace the Meridian Foods details with your own, and run it through the checklist.
If a field in the table is blank, write "not yet confirmed" in the email. Don't fill it with optimism.
That's the whole discipline. Honest fields, matching template, named decisions.
If the assembly itself is the part that takes hours each week, a walkthrough with the Splice Work team is a reasonable next step to see whether a custom drafting workflow fits your situation.
Automated Voice Messaging System: A Small Business Guide
Landscape Company Software: What It Does and What It Misses
Text Message Bot for Small Business: When You Need One