Most weekly status updates are unreadable. They’re either too vague (“working on things”) or too detailed (a full project log no one has time to parse). Here’s how to write one that gives your manager what they need: a clear picture of progress, blockers, and priorities in under five minutes.
What a Status Update Is — and Isn’t
It is: a summary of work completed, work in progress, blockers, and upcoming priorities. It’s written for someone who trusts you but doesn’t have time to track every detail themselves.
It is not: a minute-by-minute log, a list of everything you did, or a place to defend yourself.
The Five-Paragraph Structure
1. One Line on Overall Status
How is the overall picture? Not “things are going well” — something specific.
- “On track for the Friday launch.”
- “Slightly behind due to the design delay, but still hitting the main deadline.”
- “Blocked on two items — details below.”
One sentence. Front-loaded. Your manager reads this and immediately knows where things stand.
2. Completed This Week
What did you finish? Keep it specific and outcome-oriented.
- Shipped the onboarding email sequence (was blocking new user activation)
- Completed design review with marketing, approved assets for development
- Resolved the data sync error that was causing duplicate user records
Avoid activity-only language. “Worked on the project” is not a deliverable. “Finished the project” is.
3. In Progress
What are you actively working on right now? One or two bullets max — only what matters.
- Building the reporting dashboard (70% complete, targeting completion by Tuesday)
- Reviewing vendor contract and comparing against two alternatives
Not everything you’re doing. Just the things that matter to the project or your manager.
4. Blockers and Risks
What’s preventing progress? Be direct.
- Waiting on design assets from marketing — no update since Monday; escalated to [manager name] on Wednesday
- Legal review of vendor contract delayed; original timeline was Friday, now looking at Monday
If there are no blockers, say that: “No blockers this week.”
5. Up Next
What are you prioritizing next week?
- Launch the beta test by Wednesday pending design sign-off
- Finalize vendor selection and begin onboarding
Common Mistakes
Writing it as a diary. Every task you did, in the order you did it. Your manager doesn’t need to know you spent three hours debugging — they need to know whether the feature is working.
Being vague to avoid commitment. “Working on improving the customer experience.” vs. “Completed A/B testing on the checkout flow; results show 12% reduction in cart abandonment.”
Including too much context. Background belongs in a separate document, not in a weekly update. The update should stand on its own.
Missing the blockers section entirely. If you’re not surfacing blockers, your manager assumes everything is fine — until it isn’t.
How to Send It
Send it on the same day and time every week. Pick a cadence and own it. Consistency is how you build trust with your manager — they learn to trust the format and actually read it.
The Template
**Status Update — [Your Name] — Week of [Date]
Overall: [One line on status]
Completed: [2-4 bullets, specific outcomes]
In Progress: [1-3 bullets, with progress indicators where relevant]
Blockers: [List or “None”]
Next Week: [1-3 bullets on priorities]