How to Write a Weekly Team Status Update That People Actually Read
How to write a weekly team status update people actually read: a simple 5-part format, a fill-in template, a before-and-after example, tips for managers collecting updates and how to replace a status meeting.

The weekly status update is one of the most common documents in modern work, and one of the most skimmed. Too often it is a long list of everything someone touched that week, written to prove they were busy. Readers scroll past, miss the one line that mattered, and then ask the same questions in a meeting.
A good update does the opposite. It tells the reader in under two minutes what changed, what is at risk and what you need from them. This guide gives you a format, a template, a real before-and-after example and advice for managers who collect updates from a team.
What a status update is for
Before writing, remember who reads it and why. Most readers want three things:
- Is the work on track? They need to know whether to worry.
- Do they need to act? Approve something, unblock someone, make a decision.
- What is coming next? So they can plan their own work.
Everything else is optional. If a line does not help a reader answer one of those questions, it probably belongs in a task tracker, not the update.
The 5-part format
This structure works for an individual update, a team update or a project update.
1. One-line summary
Start with a single sentence that a reader could stop after. Use a simple status label:
- On track: Work is going as planned.
- At risk: A problem could cause a delay if not handled.
- Off track: A deadline or goal will be missed without a change.
Example: "On track. Spring catalog is 80% complete; final review starts Monday."
2. Wins and progress
List 2 to 4 results, not activities. "Finished supplier price comparison; chose two vendors" beats "Worked on supplier research." Tie each item to a goal or project when you can.
3. Risks and blockers
Name problems early and plainly, with what you are doing about them. A blocker without a proposed next step forces the reader to do your thinking.
4. Asks and decisions needed
This is the most important section for the reader. Put a name and a date on each ask: "Maria: approve the revised budget by Thursday so we can place the order Friday."
5. Next week
List 2 to 4 priorities for the coming week. This lets people spot conflicts early and holds you to a plan. If you plan your week on Fridays, this section comes almost for free; see how to plan your week.
Fill-in template
Copy this into an email, chat post or document:
Status: [On track / At risk / Off track] - [one-sentence summary]
Done this week
- [Result + why it matters]
- [Result]
Risks and blockers
- [Problem] → [What I'm doing / what would fix it]
Needs from others
- [Name]: [Decision or action] by [day]
Next week
- [Priority]
- [Priority]
Links: [project board] · [key document]
Aim for 150 to 300 words. Paste your draft into the word counter if you tend to run long.
A before-and-after example
Here is a typical first draft from a marketing coordinator at a small company:
This week I had meetings with the design team about the newsletter and the website. I worked on the newsletter copy and sent some drafts around. I also looked into the giveaway rules and talked to the vendor about the trade show booth. There were some issues with the booth size. I also updated the social calendar and answered a lot of emails. Next week I'll keep working on these things.
It is honest, but the reader cannot tell what is finished, what is at risk or what they need to do. Here is the same week rewritten:
Status: At risk. Newsletter and social calendar are on track; the trade show booth may not fit our display.
Done this week
- November newsletter copy approved; scheduled for Tuesday 9 a.m.
- Social calendar filled through December 15.
- Giveaway rules drafted and sent to the owner for review.
Risks and blockers
- The booth we reserved is 8x8 ft; our display needs 10x10. Vendor can upgrade for an extra fee if confirmed by Nov. 22 → I recommend upgrading.
Needs from others
- Sam: approve the booth upgrade by Friday.
- Lee: final logo files for the banner by Wednesday.
Next week
- Send newsletter, review results.
- Order banner once logo files arrive.
The second version is shorter in spirit, even though it has more structure. The reader knows exactly where to look and what to do.
Writing tips that make updates readable
- Lead with what changed, not what you did. Outcomes over activities.
- Use the same structure every week. Readers learn where to look and skim faster.
- Bold names and status labels. People scan for their own name first.
- Use numbers and dates. "Three of five product pages done; last two by Wednesday" is clearer than "making good progress."
- Keep bad news at the top. Hiding a risk in the fourth bullet erodes trust when it surfaces later.
- Link instead of pasting. Put details in the project tool and link to them. If you are choosing one, see how to choose a project management app.
- Send at a predictable time. Friday afternoon or Monday morning both work; pick one and stick with it.
Where to send it
| Team size and style | Best channel | Why |
|---|---|---|
| Solo freelancer to a client | Creates a record the client can forward | |
| Small team in one chat tool | A dedicated chat channel or thread | Easy to scan and reply in one place |
| Several projects or teams | A shared document with one section per person | Keeps history and avoids long chat threads |
| Larger company | Your project management tool's status feature | Ties updates to tasks and dates |
Whatever you choose, keep updates in one place so people can look back at the history.
For managers: collecting updates from a team
If you lead a team, the way you ask for updates shapes what you get:
- Share the template and a good example, like the one above.
- Set a deadline that leaves you time to read and respond, such as noon on Friday.
- Respond to asks quickly. If people raise blockers and nothing happens, they stop raising them.
- Roll up, don't copy. When reporting upward, combine your team's updates into a short summary with the most important risks and decisions, and credit the people who did the work.
- Use updates to cut meetings. If written updates are good, a weekly status meeting can become a shorter discussion of only the risks and decisions. Our guide on running shorter, better meetings shows how to make that switch.
If you manage several workstreams, the "next week" sections become a simple early-warning system for overload. Read them alongside how to manage multiple projects at once.
Mistakes to avoid
- The diary. Listing every meeting and email makes the update long and unclear.
- Status theater. Marking everything "on track" until the deadline passes. Early "at risk" flags are a sign of good judgment, not failure.
- No asks. If you need nothing from anyone, fine, but most weeks someone needs to approve or provide something.
- Changing the format every week. Consistency is what makes updates fast to read.
- Writing it from memory on Friday at 5 p.m. Keep a running note during the week, or use your meeting notes as a source.
Frequently asked questions
How long should a weekly status update be?
Most should take under two minutes to read: roughly 150 to 300 words. Project updates for a large group can be longer, but put the summary and asks at the top.
What is the difference between a status update and a report?
A status update is a short, regular snapshot focused on progress, risks and asks. A report is usually longer, less frequent and focused on analysis or results over a period.
Should I include tasks that are not finished?
Include unfinished work only if it is a priority, at risk or needs something from someone. Routine in-progress tasks belong in your task tracker.
Can AI help write status updates?
Yes. You can paste your rough notes into an AI assistant and ask it to format them into the five-part structure. Always check the result, since it may overstate progress or drop an important risk.
Spotted an error? Tell us and we will review it under our editorial policy.



