A project status update email opens with the overall status in a word or two (on track, at risk, blocked), then covers what got done, what's next, and anything you need from the reader. Keep it scannable and under 200 words. Sending it on the same day each week sets an expectation, so fewer people ask for ad hoc updates.
Weekly project status update
The standard format for a team or stakeholder list. Status goes in the subject so people who only read subjects still get it.
Hi all, Status: [On track]. [One sentence on where things stand, e.g. Beta build is on schedule for the 24th.] Done this week - [Item] - [Item] Next week - [Item], [owner] - [Item], [owner] Risks and blockers - [Risk or blocker, and what you're doing about it] Needed from you - [Name]: [decision or input] by [date] Full tracker: [link] [Your name]
Three-line update for executives
Senior readers want the status, the date, and whether they need to do anything. Link to detail rather than including it.
Hi [Name], [Project] is on track for [milestone] on [date]. This week we [biggest progress]. One thing to watch: [risk], which we're handling by [action]. Nothing needed from you right now. Details are in [link]. [Your name]
Status update when the project is at risk
Send this as soon as you know, not at the next scheduled update. Lead with the new date and the options.
Hi [Name / all], [Milestone] is at risk. [One-sentence cause, e.g. the vendor API we depend on is two weeks late.] Options: 1. Move [milestone] to [new date], full scope. 2. Keep [original date], cut [feature or scope]. 3. [Other option, e.g. add a contractor], cost [amount]. I recommend option [number] because [reason]. I need a decision by [date] to keep the new plan realistic. [Your name]
When a status email helps, and when a dashboard is enough
- Send an email when stakeholders don't open the project tool, or when a decision is needed from them.
- If everyone already works in a shared tracker, a two-line email linking to it is enough.
- Don't wait for the weekly update to report bad news. Send the at-risk version the day you know.
What to avoid
- Listing every task. Include what changed, not everything that exists.
- "Green" status on a project that everyone privately knows is late. It costs trust at the next update.
- Requests buried in paragraph four. Put asks in their own section with names.
- Changing the format every week. The same headings make it faster to read.
How Synced drafts a status update
When someone asks "where are we on this?", Synced searches your connected email, Slack, Teams, and Drive for the latest on that project and drafts the reply from what it finds. You review and edit it in Decide before it goes out. See search for which sources it looks through.