Be honest. When was the last time you read a project status update all the way through? Most of them are long, vague, and written to prove work happened rather than to say anything. They get skimmed, archived, and ignored, and then everyone is surprised when nobody knows what is going on.
A status update is a short, regular written summary that tells everyone what changed, what is blocked, and what needs deciding. That is all it is. Not a novel. Not a defence. A tool for keeping a project honest about where it stands.
Why does nobody read them?
Because most status updates answer questions nobody asked. They list tasks completed in loving detail and bury the one thing that matters: the decision that has been waiting for nine days. Readers learn quickly that there is nothing useful inside, and they stop opening them.
There is a second reason. Updates written by someone afraid of bad news all sound the same. Everything is on track until the day it is not. A status update that never contains bad news is fiction, and people can tell.
The fix is not a better template. It is a braver writer. Someone has to be willing to write the sentence everyone is avoiding, and that someone is usually the delivery owner, not the project team.
What should a status update contain?
Three things, in this order. What needs deciding, with a name and a date. What is blocked, and by whom. What changed since last time. Everything else is optional. If you can read it in ninety seconds, it is the right length.
Lead with the uncomfortable part. The blocker goes first, not last. Teams that hide bad news at the bottom train everyone to stop reading at the top. Put the problem where it cannot be missed and watch how fast it gets solved.
How often should you send one?
Weekly, same day, same format. Rhythm is the whole point. A status update that arrives every Friday becomes part of how the team thinks. One that arrives randomly becomes another email to ignore.
And keep the audience small. The update goes to the people who decide and the people who do. CCing the whole company guarantees nobody reads it. If fourteen people are on the thread, it belongs to no one, which brings us back to who actually owns delivery.
What does good look like in practice?
Subject line with the date and one honest word: on track, at risk, or off track. Then the three sections. Then done. The best status update I ever received was eleven lines long and it saved a project, because the at risk flag forced a conversation two weeks before the deadline died.
If writing it feels hard, the project is probably in worse shape than you think. Easy projects write easy updates. The update is a thermometer, not a treatment.
Keep old updates where everyone can find them. A shared thread of weekly updates is the project's memory. When someone asks why a decision was made, the answer is there, dated and plain. That is also why agencies love clients who do this: it ends the budget arguments before they start.
Working with Avy
Part of what I do inside marketing teams is run the weekly rhythm: the update, the decisions, the chasing. It is unglamorous and it is the reason projects land. Boring process, exciting results.
If your team is flying blind between meetings, book a call. I will show you what ninety seconds of honesty a week can do.
Need someone to get your project over the line?
Project delivery support for brand, digital, and creative teams that need clearer direction and smoother progress.