How to Write a Weekly Status Update That People Read

A weekly status update answers three questions for people who are not in the room: what is done, what is next and what is stuck. Written well, it takes ten minutes, saves meetings and stops surprises. Here is a simple format and a template.

By Rohan Rawat

Why write a weekly update

People who rely on your work need to know where it stands without asking. A regular written update replaces many small "any news?" messages, creates a record and gives you a moment to notice when something is drifting.

The four-part format

  1. Headline (one line). The overall status in plain words: on track, at risk or blocked, and the single most important fact.
  2. Done this week. Three to five outcomes, written as results, not activities. "Finished the supplier shortlist" beats "Worked on suppliers".
  3. Next week. The main two or three things you plan to do, in order of importance.
  4. Risks and help needed. Anything that could delay the work, and a specific request: who needs to do what by when.

Writing tips

  • Lead with the conclusion. A busy reader may read only the headline.
  • Be honest about status. A risk reported early is a conversation; a risk reported late is a crisis.
  • Use numbers only when you have them. "Three of five sections drafted" is clear. Do not guess percentages.
  • Keep it to one screen. Link to details instead of pasting them.
  • Write it like any clear message. The structure in how to write a clear email applies here too.
  • Send it at the same time each week. A predictable rhythm helps readers trust it.
Example update

Headline: At risk. The website content is on track, but images are blocked until Thursday.

Done: final text for four of six pages; navigation agreed with Sam; tested the contact form.

Next: finish the last two pages; add images once received; start testing on phones.

Risks and help needed: photographer files are late. Sam, could you confirm a new delivery date by Wednesday? If images arrive after Thursday, launch moves by two days.

Edge cases

  • Nothing much happened. Say so briefly, and explain why. Maintenance and waiting are real work.
  • Bad news. State it in the headline, with what you are doing about it. Avoid blame; stick to facts.
  • Several projects. Give each a headline, then details beneath. If it grows past a page, consider separate updates.
  • Confidential information. Check who receives the update. Leave out personal data and anything restricted.
  • Stakeholders who want daily updates. Agree a cadence and a quick channel for urgent news so that you are not writing a report every day.

Weekly update template

WEEKLY UPDATE   Project: ____________   Week of: ________

HEADLINE (on track / at risk / blocked): ____________________

DONE THIS WEEK
- ____________________
- ____________________
- ____________________

NEXT WEEK
1. ____________________
2. ____________________

RISKS AND HELP NEEDED
- Risk: ________  Impact if it happens: ________
- Request: ________ from ________ by ________

LINKS: ____________________
Recap

Use four parts: a one-line headline, results done, plans for next week, and risks with a specific request. Be honest early, keep it short, link for detail and send it at a regular time.

Next step

Write this week's update before you log off on Friday, as part of the daily work shutdown routine. For a new project, agree what to report in the one-page project brief.