A clear status update can replace a meeting, calm an anxious stakeholder, and surface a problem before it becomes a crisis. A bad one does the opposite: it buries the real news, forces three follow-up questions, and trains people to skip your emails. The good news is that a great status update follows a repeatable format you can fill in every week in ten minutes. This guide gives you that format, plus a full example you can copy.
What a status update is actually for
A status update is not a diary of everything you did. It is a decision-support document. Its job is to tell readers, fast, whether the project is healthy, what changed since last time, and whether they need to do anything.
Most readers fall into two camps. Stakeholders want the headline and the risks. The working team wants the detail. A good update serves both by putting the summary on top and the depth below, so each person can stop reading the moment they have what they need.
If you remember nothing else, remember this: write for someone who will read only the first three lines. Everything important should survive that test.
A repeatable format
Use the same structure every time. Consistency is half the value, because readers learn where to look and trust that nothing is hidden in a new place each week.
- TL;DR. Two or three sentences. The headline of the week.
- Overall status. A single color or word: on track, at risk, or off track.
- What shipped. Concrete progress since the last update.
- What is next. The plan for the coming period.
- Risks and blockers. What could go wrong and what already is.
- Asks and decisions needed. Anything you need from the reader, with owners and dates.
That order is deliberate. The summary and status come first because they are what a busy executive reads. The asks come last because they are the action items people scroll to.
Use a status color, and be honest about it
Many teams use a red, amber, green (RAG) system. Green means on track. Amber means at risk but recoverable. Red means off track and needs intervention. Whatever scheme you use, the rule is the same: the color must tell the truth.
The temptation is to keep everything green so you look in control. This is a trap. The whole point of a status color is early warning. A project that goes from green straight to red with no amber in between destroys trust, because it means the warning system was switched off.
Mark something amber the moment you see a credible threat to the timeline, scope, or budget. Amber is not an admission of failure. It is you doing your job: flagging early so there is time to react.
Do not bury the bad news
The fastest way to lose a stakeholder's trust is to hide a problem in paragraph six and hope nobody notices. They will notice, usually at the worst possible moment, and they will wonder what else you buried.
Put bad news up top, in the TL;DR, stated plainly. "We will miss the original launch date by about a week because the payment integration failed testing" is uncomfortable to write and exactly what readers need. Pair every problem with what you are doing about it, so the message is a plan, not a panic.
Honesty also makes your green updates believable. If readers know you flag problems early and clearly, they will trust you when you say things are fine.
Write for skimmers
Status updates are skimmed, not read. Format accordingly.
- Lead each section with the conclusion, then add detail underneath.
- Use bullets and bold for scannability. A wall of prose hides the signal.
- Quantify where you can. "Sprint 3 is 80 percent complete" beats "good progress."
- Name owners and dates for every open item. "Someone will look into it" is not a status.
The same discipline that makes any email easier to act on applies double here. If you want to sharpen this skill more broadly, our guide on how to write concise emails covers the cutting that makes updates land.
A full example status update
Here is a complete weekly update for a fictional product launch. Notice how the first four lines tell the whole story.
Subject: [Status] Project Helix, Week 14, AT RISK
Hi all,
TL;DR: Helix is at risk for the original launch date. The payment integration failed load testing this week, which puts us roughly one week behind. We have a recovery plan and need a decision on scope by Thursday.
Overall status: AMBER (was GREEN last week)
What shipped this week:
- Checkout redesign live in staging and passing QA
- Onboarding email sequence finalized and approved
- Search indexing now 40 percent faster after the database tuning
What is next:
- Re-run payment load tests with the patched integration (Owner: Dev, by Wed)
- Final accessibility audit (Owner: Maya, by Fri)
- Go or no-go review (Owner: me, Thu 2pm)
Risks and blockers:
- Payment integration failed at 5,000 concurrent users. Vendor patch is in testing now. This is the cause of the amber status.
- Content team is one writer short this week, which may slow help-doc updates. Watching, not yet blocking.
Decisions needed:
- By Thursday: ship on time with the payment vendor as a fast-follow, or hold the full launch one week. I will bring a recommendation to the go or no-go review.
Full details and the test logs are in the project board. Reply here or grab me before Thursday if you have questions.
Thanks, Devon Park Product Lead, Helix
The reader knows in four lines that the project is at risk, why, and that a decision is needed Thursday. Everything below is there for anyone who wants the depth.
Cadence and subject lines
Pick a regular rhythm and hold to it. Weekly works for most active projects. The value of a status update compounds when it arrives predictably, because people start planning around it.
Keep the subject line consistent and searchable. A pattern like "[Status] Project Name, Week N, STATUS" lets anyone scan their inbox and find the latest update or trace the history. Putting the RAG status right in the subject means a stakeholder can triage without even opening the message.
A well-run cadence of written updates also cuts down on meetings, which is the whole point of working asynchronously. If your team is shifting away from constant calls, our guide to async communication pairs naturally with a strong status habit. And when an update does surface a decision that genuinely needs a live conversation, a tight meeting request email gets people in the room without wasting the week.
Tailor the detail to the audience
One update can serve everyone if you layer it. But sometimes the audiences are different enough that a single email does not fit.
For a leadership-only update, lead with the TL;DR, status, risks, and asks, and trim the granular task list. For the working team, keep the detail and the owners. If you find yourself writing two genuinely different messages, send two, but keep the headline identical so the story stays consistent across audiences.
The mistake is flattening everything to the lowest detail for everyone. Executives drown in task lists. Engineers feel patronized by vague summaries. Layering the same update solves both.
Frequently Asked Questions
How long should a project status update be?
Short enough to read in two minutes. For most projects that means a screen or less: a few-line summary, a status color, three to five bullets each for progress and next steps, and a short risks and asks section. If it runs longer, push the detail into a linked document and keep the email itself a scannable summary. Length signals importance to no one; clarity does.
How often should I send a status update?
Match the cadence to the pace of change, but pick a fixed rhythm and stick to it. Weekly suits most active projects, while a long, slow-moving program might be biweekly or monthly. Predictability is the point: when updates arrive on a known schedule, people stop chasing you for status and start planning around your reports. Send an out-of-cycle update only when something urgent changes.
What if the project is in trouble and I do not want to look bad?
Flag it early and plainly, because hiding it always backfires worse. Mark the status amber or red, state the problem in the TL;DR, and pair it with a concrete recovery plan and the decision you need. Leaders respect a manager who surfaces risk in time to act far more than one who keeps everything green until it collapses. Honest early warnings are exactly what makes your good news believable later.
The habit that pays off
A great status update is not about writing more. It is about the same reliable format every time: a clear headline, an honest status color, what shipped, what is next, the risks, and the asks. Master that and you replace meetings, build trust, and catch problems while they are still small. Close each update with a clean, professional sign-off so the people reading know exactly who to come back to. If you need one, you can create a free email signature in a couple of minutes.
