TL;DR:
A status update answers three questions: what is done, what is next, and what is blocked.
Keep it to a few lines, lead with the most important thing, and link to details instead of pasting them.
Send it at the same time every week, so readers learn where to look and what to expect.
Friday afternoon you write a long update. You list everything you touched, every meeting, every small fix. Your manager skims the first two lines and replies "thanks". The one thing you needed from them, a decision on Monday, was in paragraph six.
A status update is not a diary. It is a short message that helps someone else decide what to do. If readers do not read it, the usual reason is that it is too long or too vague, not that they do not care.
What the reader wants
Imagine the reader opening your message between two other things. They want to know three things fast: is everything on track, is anything needed from me, and what is changing. Everything in the update should serve one of those.
That is why the best updates look boring and predictable. The same shape every week lets the reader find the bit they need in seconds.
Collect while you work
Don't rebuild the week from memory on Friday. Keep a running note, and every time you finish something or hit a snag, add one line. On Friday, you only have to choose and tidy.
Include a link next to each item that someone might want to open: the document, the ticket, the page, the folder. A link lets the reader check details without asking you.
The shape: done, next, blocked
Done: what was finished this week, in outcomes and not activities. "Sent the proposal to the client" beats "worked on the proposal".
Next: what you plan to do in the coming week, in priority order.
Blocked: anything waiting on someone else, with the name of the person and the date you need it by.
If there is nothing blocked, write "Nothing blocked". An empty slot is useful information: it tells the reader that you checked.
Worked example: a five-line status update
Say you are updating your manager on the website refresh. This is an invented example.
Subject: Website refresh, week of 16 Nov: on track, one decision needed
Done: Home page text approved (link: Home page draft).
Done: Four of five photos received from Marcus (link: Photos folder).
Next: Draft the menu page text by Wed 25 Nov.
Next: Build the home page once the last photo arrives.
Blocked: Need a yes or no on the order form wording from Sam by Fri 20 Nov.Read it as the manager would. The subject line says the status and that a decision is needed. The two done lines show progress with proof. The next lines say what happens and by when. The last line names the person, the question and the date. The whole thing takes about twenty seconds to read.
Check the dates against a calendar. If the week began on Monday 16 November 2026, then Friday 20 November is that same week, and Wednesday 25 November is the following week. A date that does not exist, or one that falls on the wrong weekday, undermines trust in everything else in the message.
Lead with what needs action
Put anything the reader must do at the very top, in the subject line if you can. Many people read only the subject and the first lines. Compare "Weekly update" with "Weekly update: need your decision on the order form by Friday". The second one gets read.
If the status is not good, say so plainly and early. A late project that is reported as late can be helped. One that is reported as fine until the last day cannot.
Writing for more than one reader
Often the same update goes to a manager, teammates and people from other teams. Write for the least-informed reader who still needs it. Spell out a project name the first time, avoid in-jokes, and don't assume everyone saw last week's message.
If different readers care about different things, keep one message and use the order of the lines to serve them. Requests for action come first, since those are for specific people. Progress comes next, for everyone. Detail lives behind links, for the few who want it.
Name people next to the things they own. "Marcus has sent four of five photos" gives credit and tells readers who to ask. Do not use an update to criticise someone. If there is a problem with a person's work, raise it with them directly first.
Finally, read your update once as the reader before you send it. If a line would make them ask a question, answer it in the line.
Mistakes to avoid
Listing activities ("attended meetings") instead of results.
Burying the request. Anything you need goes first.
Vague blockers such as "waiting on feedback". Say whose feedback and by when.
Pasting long detail into the message. Link to it.
Changing the format every week.
Sending late or at random times.
Doing it faster
Save the three-part shape as a template and set a recurring reminder at the same time each week. Take the done lines from your running note and the next lines from your task list. For a hand with the wording, DuckyHelper can read your draft on screen and point at lines that sound vague. Whatever you use, send it yourself and check the dates before you do.
Frequently asked questions
How often should I send a status update?
As often as your reader needs to act on it. Weekly suits most projects. Send an extra note any time something important changes.
What if I got nothing done?
Say it, and say why. If the reason is a blocker, put it in the blocked line with the person who can fix it.
Get started
