A weekly status update is a short note to your manager that says what you finished, what's next, and where you're stuck. Done well, it takes five minutes to write, keeps your 1:1 for real conversation, and quietly builds the record you'll need when your self-review is due.
Below is a template you can copy, examples for three kinds of roles, and the mistakes that make managers skim past updates.
The weekly status update template
Copy this into an email, a chat message or the top of a running doc:
Weekly update: [week of Month Day]
Done
- [Outcome] by [what you did]. ([link or number if you have one])
- [Outcome] by [what you did].
Next week
- [Priority 1]
- [Priority 2]
Blockers / risks
- [What's stuck], waiting on [who or what]. Need by [date].
Need from you
- [One decision, intro or review you need from your manager]
Four sections are enough. If a week has no blockers, delete the section instead of writing "none".
What to put in each section
Done
This is the section your manager will reuse, so write it in a way they could forward without editing. Start with the result, then how you got there.
| Instead of | Write |
|---|---|
| Worked on the onboarding doc | New support hires now have one onboarding checklist; ran the first session with it |
| Meetings with legal | Got legal sign-off on the new pricing page copy |
| Fixed bugs | Fixed the export job that failed overnight; added a test so it doesn't come back |
If you have a number, include it. If you don't, describe what changed in plain words. Don't guess a number to make a line look stronger. A made-up figure is the one thing you'll have to defend later.
Next week
Two or three priorities, in order. This is where your manager can redirect you before you spend a week on the wrong thing, which is the main reason to write it.
Blockers and risks
Name what is stuck, who or what you're waiting on, and when it starts to hurt. "Waiting on finance for the Q4 budget numbers; the forecast slips if they don't arrive by Thursday" gives your manager something to act on. "Some delays" doesn't.
Need from you
One specific ask: a decision, an introduction, a review, air cover. Managers like updates that make it obvious how they can help.
Weekly status update examples
These are illustrative examples. Swap in your own work and only use numbers you can back up.
Operations / BizOps
Weekly update: week of Oct 13
Done
- Vendor invoices now go through one approval sheet, so finance no longer chases sign-offs by email.
- Closed out the September headcount report and shared it with the finance lead.
Next week
- Draft the Q4 vendor renewal list
- Start the travel policy FAQ
Blockers / risks
- Waiting on IT to add two approvers to the sheet. Needed before month-end close.
Need from you
- 15 minutes to review the renewal list before it goes to finance.
Product manager
Weekly update: week of Oct 13
Done
- Pricing page relaunch shipped on the planned date after legal's copy changes.
- Ran three customer calls on the reporting feature; notes and themes in the research doc.
Next week
- Write the one-pager for reporting v2
- Align with design on the empty-state flow
Blockers / risks
- Analytics event for plan upgrades is missing, so we can't measure the relaunch yet. Eng ticket filed.
Need from you
- A decision on whether reporting v2 or the onboarding fix goes first next quarter.
Software engineer
Weekly update: week of Oct 13
Done
- Found and fixed the timezone bug behind the nightly export failures; added a regression test.
- Reviewed and merged the new auth middleware with the platform team.
Next week
- Start the search indexing migration
- Pair with the new hire on the billing service
Blockers / risks
- Staging database is out of disk; migration testing is paused until infra resizes it.
Need from you
- Help getting infra to prioritize the staging resize.
Five mistakes that make managers skim
- Listing activity instead of outcomes. "Had meetings about X" tells your manager how you spent time, not what changed.
- Burying the blocker. Put the thing that needs attention where it can't be missed, not in the fourth paragraph.
- Writing for yourself. Skip internal shorthand and ticket numbers without context. Your update may be forwarded.
- Sending it irregularly. An update that arrives on Friday afternoon every week becomes part of your manager's routine. A random one gets lost.
- Inflating it. "Significantly improved" and invented percentages make every other line less believable.
Your weekly updates are your review prep
The hardest part of a self-review is remembering what you did in February. If you've sent a weekly update every Friday, that problem is mostly solved: your year is already written down, in your own words, with dates.
A few habits make that record more useful later:
- Keep all updates in one place (a running doc or one email thread) instead of scattered chat messages.
- Write the result while you still remember it. The numbers and names are gone a month later.
- Mark the lines you'd want in your review with a star as you go.
When review season comes, read back through your updates and pull the starred lines into a brag sheet. Our guide on writing a self-review when you can't remember what you did walks through that step, and the brag doc template gives you a place to put it.
If you'd rather not keep the doc by hand, WinStash takes a short note each week and turns it into a weekly update, a brag sheet and STAR stories, using only what you wrote.