📋 Contents
- Why most weekly reports go unread
- The four-part template
- Writing the summary line
- Writing "done" as results, not activities
- Next week: commit to dates
- Blockers with dates and owners
- Email vs. Slack: the same update in two formats
- Weekly update to your manager vs. project status report
- Examples by role
- Make it fast to write every week
PART 1
Why most weekly reports go unread
Most weekly reports fail for the same reasons: they list activities instead of results, they bury the one thing the manager needs to decide, and they look identical every week so nobody notices when something changes.
A good report flips that. It starts with a one-line summary, shows what actually moved, says what is next, and puts blockers in plain view with dates and owners. It takes ten to fifteen minutes to write if you have notes from the week, and it saves your manager from asking you the same questions in a meeting.
PART 2
The four-part template
| Section | What goes in it | Length |
|---|---|---|
| 1. Summary | One sentence: overall status and the most important point | 1 line |
| 2. Done / results | What finished and what changed because of it | 3–5 bullets |
| 3. Next week | What you will deliver, with target dates | 3–5 bullets |
| 4. Blockers and asks | What is stuck, since when, and what you need from whom by when | 0–3 bullets |
✍️ Copy-ready template
Subject: Weekly update — [your name / project] — week of [date]
Summary: [On track / at risk / off track]. [The single most important thing this week.]
Done this week:
• [Deliverable] → [result or what it unblocks]
• [Deliverable] → [result]
Next week:
• [Deliverable] — by [day]
• [Deliverable] — by [day]
Blockers / asks:
• [Issue] — blocked since [date]. Need [decision/input] from [person] by [date].
PART 3
Writing the summary line
The summary is the most read line in the report and the hardest to write. It should answer: is everything fine, and if not, what is the one thing to know?
✍️ Weak vs. strong summary lines
Weak: Busy week, lots of progress across several projects.
Strong: On track. Pricing page is live; the checkout redesign needs a decision on payment options by Wednesday to keep the March date.
Weak: Continued working on the migration.
Strong: At risk. Data migration is 70% done but the vendor API limit is slowing transfers; requesting a higher limit, answer expected Tuesday.
💡 Use a status word
Starting with "On track," "At risk" or "Off track" (or green / yellow / red, if your team uses traffic-light status) lets readers sort your report instantly. Use "At risk" early, when there is still time to help. A report that jumps from green to red with no yellow in between erodes trust.
PART 4
Writing "done" as results, not activities
The done section is where most reports become a diary. Each bullet should name what finished and why it matters.
| Activity (weak) | Result (strong) |
|---|---|
| Worked on the onboarding emails | Finished the 3-email onboarding sequence; it goes live Monday to all new signups |
| Had meetings with the vendor | Agreed contract terms with the vendor; legal review starts Tuesday |
| Fixed bugs | Fixed the two bugs blocking the mobile release; release is back on schedule for Thursday |
| Helped the support team | Trained four support agents on the new refund flow; refund tickets no longer escalate to engineering |
If something is in progress, say how far along it is in terms the reader understands: "draft done, in review with legal" is clearer than "60% complete."
PART 5
Next week: commit to dates
List what you expect to finish, not everything you will touch. Attach a day or date to each item. Next week, your done section should mostly match this list, and when it does not, a one-line explanation builds credibility.
- Publish the Q3 pricing FAQ — Tuesday.
- Send revised vendor contract to legal — Wednesday.
- First draft of the customer survey results — Friday.
PART 6
Blockers with dates and owners
A blocker without a date and an owner is a complaint. A blocker with both is a request that someone can act on.
✍️ Blocker rewrites
Before: Still waiting on design.
After: Waiting on final checkout designs since Oct 2. Need them from Sam by Oct 9 to hold the Oct 20 release.
Before: Budget is unclear.
After: Need a yes/no on the extra contractor budget by Friday; without it the analytics work moves to next quarter.
⚠️ Don’t hide blockers in the middle
If something needs your manager’s action, mention it in the summary line too. Readers who stop after the first line should still see it.
PART 7
Email vs. Slack: the same update in two formats
On many remote and hybrid teams, the weekly update has moved from email into a Slack or Microsoft Teams channel, or a recurring thread your manager starts on Friday. The structure stays the same; the format gets tighter.
✍️ Slack / Teams version
Weekly update — week of Oct 6 — Green / on track
Wins: Pricing page live → sales stopped getting the "which plan" question on calls. Vendor contract terms agreed.
Next: Checkout redesign spec (Tue), vendor contract to legal (Wed).
Need: Decision on payment options from @manager by Wed to hold the March date.
| Slack / Teams thread | ||
|---|---|---|
| Best for | Managers who archive updates; readers outside your team | Teams that already work in channels; several readers at once |
| Length | Up to one screen | Four to six lines; link to details |
| Asks | Name the person and date in the blockers section | Tag the person directly so they get notified |
| Record | Easy to search by subject line | Pin or bookmark the thread; channels scroll away fast |
⚠️ Don’t let async replace the hard conversation
A red status or a serious blocker deserves a direct message or a quick call in addition to the post. Async updates are for information; decisions under pressure usually need a live conversation.
PART 8
Weekly update to your manager vs. project status report
Search results mix two different documents. A weekly update to your manager covers everything you personally worked on, and its main reader is one person. A project status report covers one project across everyone working on it, and its readers are stakeholders: other team leads, a sponsor, sometimes a client.
Project reports usually add a few fields: overall status and the dates of key milestones, budget or resourcing status if relevant, risks with an owner and mitigation, and decisions needed from sponsors. The four-part template still works; you simply widen "done" and "next" to the whole team and add a short milestone list.
PART 9
Examples by role
Software engineer
✍️ Engineer weekly update
Summary: On track. Search indexing fix shipped; starting on the export API next.
Done: Shipped the indexing fix → search results now update within a minute instead of hourly. Reviewed 6 PRs for the payments team.
Next: Export API design doc — Tue. First endpoint behind a flag — Fri.
Blockers: Need read access to the billing database; requested Oct 3 from IT.
Marketing
✍️ Marketing weekly update
Summary: At risk. Webinar registrations are behind target; adding a partner email send to recover.
Done: Launched the webinar landing page and two social posts. Finished the case study draft with the customer’s approval.
Next: Partner email — Mon. Case study published — Wed.
Blockers: Need approval on the paid promotion budget by Tuesday.
Operations
✍️ Operations weekly update
Summary: On track. New supplier onboarded; inventory count scheduled.
Done: Onboarded the second packaging supplier → removes our single-supplier risk. Updated the returns SOP.
Next: Quarterly inventory count — Thu. Returns SOP training — Fri.
Blockers: None.
PART 10
Make it fast to write every week
The report is quick when the raw material is already there. Keep a one-line note at the end of each day about what you finished and what changed. On Friday, pick the three to five most important lines for "done," and the report almost writes itself. The same notes later feed your brag document and review.
☐ Summary line starts with a status word.
☐ Every done bullet says what changed.
☐ Every next-week item has a day.
☐ Every blocker has a since-date, an owner and a need-by date.
☐ The whole report fits on one screen.
Frequently asked questions
Q. What should be included in a weekly status report?
A one-line summary with a status word, what you finished and what it changed, what you will deliver next week with dates, and blockers or asks with an owner and a need-by date.
Q. How do I write a weekly update email to my boss?
Use a consistent subject line ("Weekly update — [name] — week of [date]"), lead with the summary line, keep each section to a few bullets, and put any decision you need from them in both the summary and the blockers section.
Q. How long should a weekly status report be?
Short enough to read on a phone screen without scrolling much: a summary line and roughly ten bullets at most. Link to details rather than including them.
Q. Should I send it by email or post it in Slack?
Use whatever your team reads. Email works for managers who archive updates; a Slack or Teams channel works when several people need the same information. Keep the structure identical either way.
Q. What day should I send it?
Friday afternoon or Monday morning are common. Friday captures the week while it is fresh; Monday lets you include plans after weekend reflection. Pick one and be consistent.
Q. What if nothing much happened this week?
Say so honestly in the summary and explain briefly, such as time spent on planning or support. A short, honest report is better than padding.
Q. Should I include metrics?
Include one or two that matter to the goal you are working on. Do not add numbers just to look busy.
Q. My manager never replies. Should I keep sending it?
Yes, but ask once whether the format is useful or whether they want something different. Even unread reports create a record you can use at review time.
This article is general guidance. Review formats, rating scales and expectations vary by company — check your own company’s guidelines alongside it.
PLAN2FOLIO
Evidence for reviews, raises and job moves — starting with one line today
Write what you did today in one line. PLAN2FOLIO sorts it into the outcomes of your role, drafts your weekly report on Fridays and gathers evidence by outcome at review time. Free to start.
Start free →