It’s Friday, 4:40 p.m. You open a blank email, type “Weekly Update,” and start listing everything you did. Meetings. Emails. That spreadsheet you fixed. The call that ran long. By the time you’re done, it’s a wall of bullet points, and it looks impressive.
You hit send. Your manager opens it Monday morning, scrolls for three seconds, and archives it. Not because they don’t care. Because they couldn’t find what they needed.
Here’s the thing most people get wrong about status updates: they’re not a record of how busy you were. They’re a tool your manager uses to make decisions. Once you write them that way, they get read. They also quietly become one of the best career tools you have.
This guide shows you exactly how to do it, with a before-and-after example and six templates you can use this week.
What Your Manager Actually Does With Your Update
Before you write a single line, it helps to know what happens on the other end. Your manager usually reads your update looking for four things:
- Is anything about to go wrong? They want to spot problems while there’s still time to fix them. A surprise in week six is far worse than a warning in week two.
- What do I tell my boss? Your manager has their own status meeting. If your update gives them a clean sentence they can repeat upward, you’ve just made their week easier.
- Does this person need something from me? A decision, an introduction, a budget sign-off, someone to push another team.
- What has this person accomplished? Months from now, at review time, your manager won’t remember your March. Your updates will.
Notice what’s not on the list: how many meetings you attended or how hard you worked. Effort matters, but your update is the wrong place to prove it.
The Biggest Mistake: Reporting Activity Instead of Outcomes
Compare these two lines:
- ❌ “Had three calls with the vendor about the delivery timeline.”
- ✅ “Vendor confirmed delivery for October 15, one week earlier than planned.”
The first tells your manager you were busy. The second tells them something changed. Only the second one is useful.
A quick test: for every bullet, ask “So what?” If the answer is “so… I did it,” rewrite it until the answer is a result, a decision, or a risk.
- “Worked on the Q3 report” → “Q3 report draft is done and with Priya for review.”
- “Researched new scheduling tools” → “Narrowed scheduling tools to two options; need your pick by Thursday.”
- “Met with the design team” → “Design team agreed to deliver mockups by the 20th.”
Same work. Completely different impact.
The 5-Part Structure Managers Actually Read
Put these in order of importance, not in the order things happened. Most managers read the top and skim the rest, so the top has to carry the weight.
1. The headline (one sentence)
Start with the overall picture: is this on track, at risk, or off track? And why, in a few words.
Overall: On track. Launch still set for Nov 3; one risk on vendor pricing (details below). If your manager reads nothing else, they know where things stand.
2. Done this week (outcomes only, 3 max)
Only the things that moved something forward. If you did twelve things, pick the three that matter most. Leaving things out isn’t hiding work. It’s editing.
3. Risks and blockers
This is the section managers value most, and the one people most often skip because it feels like admitting failure. It isn’t. Flagging a problem early is one of the most senior things you can do.
For each risk, include what you need: Blocker: Still waiting on legal review of the contract (sent Sept 28). If it’s not back by Oct 10, launch slips a week. Could you nudge the legal team?
4. Decisions needed from you
If you need your manager to decide something, give them a recommendation and, where it makes sense, a default. It turns a thinking task into a yes/no.
Decision needed: Go with Vendor A ($4K, ready in 2 weeks) or Vendor B ($3K, ready in 5 weeks)? I recommend A because of the launch date. If I don’t hear otherwise by Wednesday, I’ll move forward with A.
5. Next week (top 3 priorities)
What you’re focusing on, so your manager can redirect you early if priorities have changed.
Optional: FYI. Anything useful but not urgent: a small win, a heads-up about someone’s vacation, a link. Keep it short and keep it at the bottom.
A Note on Red, Yellow, and Green
Traffic-light labels (🟢 on track, 🟡 at risk, 🔴 off track) are a great shorthand. But they only work if you’re honest.
There’s a term project managers use: the watermelon project. Green on the outside, red on the inside. It’s the project that reports “on track” for months and then suddenly misses its deadline by six weeks. Nobody trusts a status report after that.
Use yellow generously. Yellow doesn’t mean “I’m failing.” It means “I see something coming, and I’m telling you now.” Managers love yellow. What they hate is a surprise red.
Before and After: A Real Rewrite
Before:
Hi Sam, Here’s what I worked on this week: – Meetings with marketing team (Mon, Wed) – Worked on the onboarding guide – Emails with IT about laptop setup – Reviewed survey results – Started planning for November training – Call with vendor – Updated the tracker Let me know if you have questions!
It’s not wrong. It’s just impossible to act on. Is the onboarding guide done? Is the IT thing a problem? What did the survey say? Sam has to reply with questions or, more likely, just won’t.
After:
Subject: Status: New Hire Onboarding | Week of Oct 6 | 🟡 At risk
Hi Sam,
Overall: At risk. Onboarding guide is on schedule, but laptop setup for the Oct 20 cohort may be late.
Done this week – Onboarding guide draft finished and shared with marketing for feedback – Survey results in: 78% of new hires want a buddy system. Summary attached.
Risks and blockers – IT says laptops may not arrive until Oct 22, two days after the cohort starts. I’m asking about loaners as a backup. If you have a contact on the IT leadership side, a quick word could help.
Decision needed – Should we pilot the buddy system with the Oct cohort? I’d recommend yes. It only needs 5 volunteers, and I have 3 already.
Next week – Finalize the onboarding guide – Lock in a laptop plan (or loaners) – Draft November training agenda
Thanks, Jordan
Same week. Same work. But now Sam knows exactly where things stand, what could go wrong, and what Jordan needs, in under a minute.
6 Weekly Status Update Templates
Copy these, change the brackets, and keep the format the same every week. Consistency matters: when your manager knows where to look, they read faster.
1. The Standard Email Update
Subject: Status: [Project] | Week of [Date] | [🟢/🟡/🔴]
Hi [Name],
Overall: [On track / At risk / Off track]. [One-sentence reason.]
Done this week – [Outcome 1] – [Outcome 2]
Risks and blockers – [Risk + what you’re doing + what you need]
Decisions needed – [Question + your recommendation + default if no reply by (day)]
Next week – [Priority 1] – [Priority 2] – [Priority 3]
Thanks, [Your Name]
2. The 5-Line Slack or Teams Version
For teams that live in chat. Short enough to read on a phone.
Weekly update: [Project] 🟢 ✅ Done: [biggest outcome] ⚠️ Risk: [one risk, or “none this week”] ❓ Need from you: [decision or “nothing right now”] ➡️ Next: [top priority]
3. For a Senior Leader or Skip-Level
Executives want even less. Three lines, maximum.
[Project]: [🟢/🟡/🔴] [One sentence on progress toward the goal.] [One sentence on the biggest risk, or “No major risks.”] [One sentence on what you need, if anything.]
4. When Things Are Going Badly
Bad news gets easier to deliver when you pair it with a plan.
Overall: Off track. [What happened, in one sentence.]
Impact: [What this affects: deadline, budget, customer.]
What I’m doing about it: [Your plan, with dates.]
What I need from you: [Specific help, or “Nothing yet. Keeping you posted.”]
Options if the plan doesn’t work: [Option A / Option B, with your recommendation.]
The key is not to soften it into mush. “We’ve hit a few minor challenges” when the launch is slipping three weeks does more damage than the delay itself.
5. For Remote Workers Who Need Visibility
When you’re remote, your update is often the only picture your manager has of your work. Add a short “impact” line so wins don’t disappear.
This week’s impact: [One result that matters to the team or business, e.g., “Cut report turnaround from 3 days to 1.”]
Done / Risks / Next: [Standard format.]
Shout-out: [Credit a teammate who helped.]
The shout-out isn’t just nice. It shows you’re a team player, and people remember who gave them credit.
6. When Nothing Much Happened
Some weeks are slow: waiting on others, holidays, a lot of maintenance work. Send the update anyway. Silence makes managers wonder.
Overall: On track, quieter week. Mostly waiting on [dependency], expected [date].
Done: [Small but real progress.]
Next week: [What picks up once the dependency clears.]
Three honest lines beat a padded list every time.
Small Habits That Make a Big Difference
Keep a running note all week. Open a doc on Monday and add one line whenever something happens. On Friday, you’re editing, not remembering. Most people who hate writing status updates hate the remembering part.
Send it at the same time every week. Thursday afternoon or Friday morning works well: late enough to have news, early enough that your manager can act before the weekend.
Use numbers where you can. “Faster” is vague. “Two days faster” is a result.
Bad news goes near the top. Burying a problem in the last bullet feels safer. It isn’t. Managers notice, and it costs you trust.
Name people. “Priya’s analysis helped us catch the pricing error” makes you look like a leader and makes Priya want to help you again.
Make the subject line do work. Include the project, the week, and the status color. Your manager should be able to search for it in six months, and they should know the story before they open it.
The Secret Benefit: Your Updates Write Your Performance Review
Here’s what most people don’t realize until review season: those weekly updates are a complete record of what you accomplished, in your own words, with dates.
Save every one in a folder. When it’s time for your self-assessment, you won’t be staring at a blank page trying to remember what you did in April. You’ll have 40+ weeks of outcomes, problems you solved, and decisions you drove. Your manager has the same record. So when they sit down to write your review or argue for your raise, the evidence is already in their inbox.
Can You Use AI to Write Your Status Update?
Yes, and it can save real time, as long as you give it the right raw material. AI is good at organizing your notes. It’s bad at knowing what matters, because it wasn’t in your meetings.
Paste your running notes into ChatGPT or Claude with a prompt like this:
Turn these notes into a weekly status update for my manager. Use this structure: overall status in one sentence, top 3 outcomes (results, not activities), risks and blockers with what I need, decisions needed with my recommendation, and top 3 priorities for next week. Keep it under 200 words. Here are my notes: [paste]
Then read it like your manager would. Check that the headline is honest, the risks are real, and it sounds like you. AI tends to make everything sound fine. Your job is to make sure it’s true.
Related: 73+ ChatGPT Prompts for Resume
Quick Answers
How long should a weekly status update be? Short enough to read in under a minute. For most roles, that’s 100 to 250 words. If it’s longer, you’re probably reporting activities instead of outcomes.
What if my manager never replies to my updates? That’s normal. Many managers read without replying. If you need something, put it under “Decisions needed” with a default, so silence still moves things forward. If you genuinely aren’t sure they read it, ask in your next one-on-one: “Are my weekly updates useful? Anything you’d like more or less of?”
Should I send one even if my manager didn’t ask? Usually, yes. Few managers will complain about a short, clear update, and it’s one of the easiest ways to build trust. Just keep it brief and ask after a few weeks whether the format works for them.
Email, Slack, or a shared doc? Whatever your manager already reads. Email works best for formal updates and records. Slack works for fast-moving teams. A shared doc works well if several people need to see it. When in doubt, ask.
Should I include things that went wrong? Always, as long as you include what you’re doing about it. A status update with no problems in it for months isn’t reassuring. It’s suspicious.
A good status update isn’t about looking busy. It’s about making your manager’s job easier: showing them what’s working, what’s at risk, and what you need, in under a minute. Do that every week, and something shifts. Your manager starts trusting your judgment. Problems get solved earlier. And when review time comes, your work speaks for itself, because you’ve been writing it down all along.
