Most project updates get written in a hurry, on a Thursday afternoon, because someone in leadership asked for "a quick status." So you paste last week's doc, swap the dates, change one bullet from "in progress" to "in progress (still)," and hit send. Nobody reads it. Two weeks later a VP asks a question the update should have answered, and you're on a call explaining what a one-paragraph note could have covered.
The fix isn't a fancier template. It's deciding, before you type, what the reader should do after reading. That single decision changes what you include, what you cut, and how the whole thing reads.
Start with the decision, not the chronology
A status update is not a diary. Nobody needs the order in which things happened. They need to know whether the plan still holds and whether they have to do anything.
Before you write a word, answer this: what does the reader need to decide or approve? If the answer is "nothing," your update is a heads-up, and it should be short. If the answer is "whether to slip the launch date," then that decision goes in the first two lines, not buried under a wall of completed tickets.
I've watched PMs spend forty minutes formatting a status doc that had no ask in it. The reader skims, sees green, moves on. Then the PM is annoyed that nobody "engaged." There was nothing to engage with.
The four-line spine
Every update I write now has the same four-part skeleton, regardless of length:
- Where we are against the plan — one sentence, plain language.
- What changed since last time — only the deltas that matter.
- What I need from you — named person, specific ask, date.
- What I'm watching — risks that haven't hit yet.
That's it. Everything else is supporting detail for people who want it, and it goes below the fold.
Here's what it looks like filled in for a real project:
Where we are: On track for the March 14 beta, with one open dependency. What changed: The auth migration landed Tuesday. The export feature slipped two days because of a schema conflict we didn't see coming. What I need: Dana, can you confirm the security review slot by Friday? If it moves past the 10th, the beta date moves with it. Watching: Two enterprise accounts have asked about SSO. Not blocking, but if it becomes a beta requirement, we're adding a week.
Four sentences. A reader knows exactly what's happening and what to do. No one has to open a spreadsheet.
Name the person, name the date
The most common failure in project updates is the passive ask. "Security review needs to be scheduled" is not an ask. It's a wish. It floats in the document, and everyone assumes someone else owns it.
Compare that to: "Dana, confirm the security review slot by Friday." Now there's a name, a verb, and a deadline. Dana either does it or replies that she can't. Either way, you learn something.
If you can't name a person, you don't have an ask yet. You have a hope. Go find the person before you send the update.
Show the delta, not the whole history
New readers need context. Returning readers need change. You can't optimize for both in the same paragraph, so split them.
Lead with the delta. Put the background in a collapsed section or a linked doc. The people who've been on the project for six months don't want to re-read the origin story every Thursday, and the people who just joined can click.
This is the same principle behind a good weekly status report — the recurring reader wants to know what's different, not what's true. Treat the standing facts as a reference doc and the update as the news.
The green-yellow-red trap
RAG status has its uses, but it's also where project updates go to die. A yellow dot tells nobody anything actionable. Is it yellow because we're two days behind on a non-critical task, or because the whole architecture is wrong and we're pretending it isn't?
If you use RAG, pair it with a reason in the same line. "Yellow — export feature slipped two days, no impact on beta date." Now the color means something. A reader can decide whether to care.
Better yet, skip the color and use the sentence. "On track for March 14 with one open dependency" tells the reader more than a yellow square ever will.
What to leave out
Most project updates are too long because the writer is afraid of being blamed for what they didn't mention. So they include everything. Every ticket closed, every meeting held, every Slack thread summarized. The result is a document nobody reads, which is worse than a short one that gets skimmed.
Cut these without guilt:
- Completed tasks with no downstream effect. "Finished the settings page." Great. Does anyone care? If it unblocks something, say what. If not, skip it.
- Meeting recaps. A link to the notes is enough. Nobody reads a meeting summary inside a status update.
- Metrics that haven't moved. If the number is the same as last week, say "flat" and move on. Don't paste the same chart.
- Hedges and qualifiers. "We're cautiously optimistic that we might be able to potentially..." Pick one. Say it.
The discipline is the same one behind writing a work report that gets read — every sentence should earn its place by helping the reader decide something.
When things are actually on fire
The four-line spine still works, but the order flips. Lead with the fire, then the ask, then the plan. Don't make a reader scroll past "on track" to find out you're not.
Status: Red. The payment provider's sandbox has been down since Tuesday, and we can't test checkout. Ask: Marcus, can you escalate with their support by EOD? We need a workaround or a new sandbox by Thursday. Plan B: If we don't have a working sandbox by Friday, we ship the beta without checkout and add it in the next release. Watching: Two customers have already asked about checkout in the beta. If it's not there, we owe them a heads-up.
Four sentences. A reader knows the problem, the ask, the fallback, and the risk. No one has to schedule a meeting to find out what's wrong. That's the whole point.
The test before you send
Read your update once and ask three questions:
- Can a reader who's been on vacation for two weeks understand where we are?
- Is there a named person with a specific ask and a date?
- If nothing changes, will this update be useful next week too?
If any answer is no, revise. If all three are yes, send it. Then go do the actual work, because the update was never the point.
Generated by Reportify AI — Automate your team's status reports, standups, and weekly updates. Try free →