WorkbamiReports & meetings
Weekly status report template: free Word & Excel download with example
A weekly status report tells your manager and stakeholders, in a few minutes of reading, what got done this week, what is planned next, and where you need help. Done well, it replaces a status meeting; done badly, it is a list nobody reads.
Below is a free weekly status report template in Word and Excel, an explanation of every section, a filled-in example, a 15-minute writing routine and the mistakes that make reports useless.
What is a weekly status report?
A weekly status report (also weekly work report, weekly progress report or weekly update) is a short, recurring summary of one person's, team's or project's work: overall status, accomplishments, next week's plan, risks and blockers, and decisions needed.
Its job is alignment, not proof of effort. A reader should be able to answer three questions from the first lines: are we on track, what changed since last week, and does anyone need to act?
When to use it
- Every Friday afternoon or Monday morning as a team or individual update to your manager.
- For client or stakeholder updates on a project with a fixed scope and deadline.
- When a team works across time zones or remotely and a written update replaces a meeting.
- To collect input for a monthly or quarterly report without starting from scratch.
- During onboarding, so a new hire's manager can see progress and blockers early.
Weekly status report template: what goes in each section
The downloadable files contain exactly these sections. Keep the order: a busy reader stops after the summary.
Header
| Section | What to write | Example |
|---|---|---|
| Report week | The week covered, with dates. | Week 43 · Oct 19–23, 2026 |
| Author / team | Who wrote it and for which team or project. | Maya Chen, Customer Success |
| Recipients | Manager, stakeholders or client contacts. | Head of CS, Sales lead |
| Overall status | Green (on track), Amber (at risk) or Red (off track), with one reason. | Amber: data migration two days late |
Body
| Section | What to write | Example |
|---|---|---|
| Summary | Two or three sentences: the most important result and the most important risk. | Onboarded 4 of 5 new accounts; migration for Delta Co slipped to Oct 28. |
| Accomplishments | Finished outcomes, with numbers where possible, not activities. | Renewed Acme (12 seats, +20%). |
| Plan for next week | Top 3–5 priorities with owners and dates. | Finish Delta migration by Oct 28 (Maya). |
| Risks and blockers | What could derail the plan and what you are doing about it. | Waiting on Delta's admin export; escalated to their IT. |
| Decisions / help needed | Specific asks with a deadline. | Approve 1-week extension for Delta by Tue. |
| Metrics | The 2–4 KPIs your team is measured on, with the trend. | NPS 61 (↑3), tickets 48 (↓12%). |
Weekly status report example
A customer success team lead's report for one week. The status line and summary are enough for a busy reader; details follow in the task table.
| Week | Week 43 · Oct 19–23, 2026 |
|---|---|
| Author | Maya Chen, Customer Success |
| Overall status | Amber: Delta Co migration two days late |
| Summary | 4 of 5 new accounts live; Acme renewed with 20% more seats. Delta's migration slipped to Oct 28 because their export arrived late. |
| Help needed | Approve a one-week extension for Delta's go-live by Tuesday. |
Tasks and progress
| Task | Owner | Status | Progress | Due |
|---|---|---|---|---|
| Onboard 5 new accounts | Maya | On track | 4 of 5 | Oct 30 |
| Acme renewal | Sam | Done | Signed, +20% seats | Oct 22 |
| Delta Co data migration | Maya | At risk | 60% | Oct 28 |
| Q4 webinar content | Leo | On track | Draft ready | Nov 6 |
Tip: write the summary last, after the table, and keep it under 50 words.
Free download
Free, no sign-up. Opens in Excel, Google Sheets, Numbers, Word, Google Docs and LibreOffice.
Open the downloaded file in Nobami, our web office, to edit it right away.
How to write a weekly status report in 15 minutes
- Start from last week's plan. Copy last week's priorities and mark each one done, moved or dropped; this keeps reports honest and comparable.
- Set the overall status. Pick green, amber or red and give a one-line reason; amber and red always need a mitigation.
- List outcomes, not activities. "Closed 3 renewals worth $18k" beats "had many calls"; add numbers and links to evidence.
- Write next week's 3–5 priorities. Each with an owner and a date, so next week's report can check them.
- Flag risks and asks. Name the decision you need, from whom and by when.
- Write the summary last and send it. Two or three sentences at the top, then share it at the same time every week.
Good practice and privacy notes
Status reports are internal business records. Keep personal data out of them: no customer phone numbers, health details or HR matters. If you work in the EU or UK, remember that names and performance information about colleagues are personal data under the GDPR, so share reports only with the people who need them.
If reports are used to evaluate individual performance or are generated by tools that track activity, check your company policy and, in some countries, works-council or employee-consultation rules before rolling them out.
Keep reports in a shared, searchable place instead of scattered e-mails, so the team can look back at decisions and you can build monthly reports from them.
Sources
- European Commission: data protection explained (checked October 29, 2026)
General information, not legal advice. Employment and privacy rules differ by country and company; follow your internal policy.
Common weekly report mistakes
- Listing every meeting and e-mail instead of results.
- Hiding a red status in paragraph four; put it in the first line.
- Reporting risks without a mitigation or an ask.
- Changing the format every week, so readers cannot compare.
- Writing a novel: one page or one screen is enough.
- Sending it at random times; a fixed slot builds the habit for writer and reader.
Weekly status report FAQ
What should be included in a weekly status report?
The report week, author and recipients, an overall status (green, amber or red), a short summary, accomplishments, next week's plan, risks and blockers, decisions or help needed, and a few key metrics.
How long should a weekly report be?
One page or one screen. The summary at the top should be readable in under a minute; details can follow in a table or linked documents.
What is RAG status?
Red, Amber, Green: a traffic-light rating of whether the work is off track, at risk or on track. Always add a one-line reason and, for amber or red, what you are doing about it.
Should I send it on Friday or Monday?
Friday afternoon captures the week while it is fresh; Monday morning lets the plan reflect weekend changes. Pick one and keep it consistent.
Can I use this template in Google Docs or Sheets?
Yes. Upload the .docx file to Google Drive and open it with Google Docs, or open the .xlsx version in Google Sheets.