A weekly report template gives you the same five sections every Friday: overall status, what got done, what is next, what is blocked, and the numbers that show progress. Keeping the format fixed is the point. Your manager learns where to look, and you spend ten minutes filling it in instead of an hour writing from scratch. Copy the template, look at the sample, then let an agent draft it from your tracker.
The weekly status report template
## Weekly status: [team or project], week of [date] **Status:** [On track / At risk / Off track]. [One sentence on why.] ### Done this week - [An outcome, not an activity, with a link to the ticket or PR] ### Planned for next week - [Item, owner] ### Blocked or need help - [What is blocked, on whom, since when, and what would unblock it] ### Risks - [What could slip, and what you are doing about it] ### Numbers | Measure | This week | Last week | |----------------------------|----------:|----------:| | [Items done] | | | | [Items in progress] | | | | [The key metric for this team] | | |
Weekly status report sample
Weekly status: Web team, week of October 12, 2026
Status: At risk. The checkout redesign is on track, but the payment provider migration slipped a week waiting for sandbox access.
Done this week
- New checkout page live for 20% of visitors; conversion steady at 3.1%.
- Fixed the coupon bug that applied discounts twice. It caused 8 support tickets the week before and none since.
- Search results load in 240 ms at p95, down from 610 ms.
Planned for next week
- Roll checkout out to all visitors if conversion holds (frontend lead).
- Test refunds and disputes in the new payment provider's sandbox (backend lead).
Blocked or need help
- Sandbox access from the payment provider, requested October 6 and still pending. We need someone with an account manager contact to escalate.
Risks
- If sandbox access arrives after October 20, the migration misses the November 1 cutover. Fallback: stay on the current provider through November.
Numbers
| Measure | This week | Last week |
|---|---|---|
| Items done | 14 | 11 |
| Items in progress | 9 | 12 |
| Open bugs | 23 | 27 |
| Checkout conversion | 3.1% | 3.0% |
Weekly status report format: what makes it work
- Status first, with a reason. "At risk" alone starts a meeting; "at risk because of sandbox access" starts a fix.
- Outcomes, not activity. "Search p95 down from 610 to 240 ms" beats "worked on search performance".
- Blockers with an ask. Name who or what blocks you and exactly what you need from the reader.
- The same sections every week, even when one is empty. "No blockers" is information too.
- A few numbers that trend. Three measures tracked weekly show direction better than a paragraph does.
- Short. A manager reading ten of these wants each one to fit on a screen.
Weekly status report examples by team
The sections stay the same; what goes in them changes with the work:
| Team | "Done" looks like | Numbers to track |
|---|---|---|
| Engineering | PRs merged, releases shipped, incidents closed | Items done, in progress, open bugs, deploys |
| Marketing | Campaigns launched, posts published | Sessions, signups, cost per signup |
| Sales | Deals moved forward, deals won | Pipeline added, closed won, meetings booked |
| Support | Queues cleared, help articles updated | Open tickets, first response time, CSAT |
| Project management | Milestones hit, decisions made | Milestones on time, budget used, open risks |
For a single project reported against milestones and budget, use the project status report template instead.
Have an agent draft it from your tracker
Most of "done", "next" and "blocked" already sits in Jira, Asana, Linear or Notion. A skill can query it every Friday and write the draft, leaving you the status call and the risks:
- Jira weekly status report: what got done, what is in flight, what is blocked and what scope was added, written for people who never open Jira.
- Asana weekly project status update: what got done in a project this week, what is due next week and what is at risk.
- Linear weekly changelog: the issues completed this week, filtered to what customers will notice.
For Jira, the core queries are statusCategory = Done AND resolved >= -7d for done and Flagged is not EMPTY for blocked. Or prompt your agent directly:
From Jira project WEB, list work items resolved in the last 7 days, items in progress, and flagged items with how long each has been flagged. Fill in this weekly status template: [paste it]. Write outcomes, not ticket titles, and link each one. Leave Status and Risks for me.
The skills post their drafts to your Briefkin board on Friday afternoon, so you edit and send instead of starting from a blank page.
Questions
What should a weekly status report include?
An overall status with the reason, what got done, what is planned next, blockers with the help you need, risks, and a few numbers you track every week. Keep it to one screen.
How do I write a weekly report for my manager?
Lead with the status and anything you need from them, then list outcomes with links as evidence. Managers skim, so put asks where they can't be missed and keep the same format every week.
What is the difference between a weekly status report and a project status report?
A weekly status report covers a person's or team's week across all their work. A project status report follows one project against its plan, with milestones, budget, risks and decisions for sponsors.
Can I use this weekly report template in Excel or Google Sheets?
Yes. Keep one tab per week with rows for done, next and blocked, and a small numbers table at the top. To paste the Markdown table, split the pasted column on the pipe character.