Guides › Template
Weekly status report template
Your weekly report should take stakeholders two minutes to read and you twenty to write. Use the same structure every week so changes stand out.
The structure
- Overall RAG, with one sentence on why it is that colour.
- Done this week: three to five outcomes, not activities.
- Planned next week.
- Milestones: due date, forecast date and status.
- Risks and issues that changed this week.
- Decisions or help needed, with a name and a date.
Writing tips
- Lead with what changed since last week.
- Use dates, not 'soon' or 'on track'.
- Never let a RAG turn green without a reason.
Keep this live, not in a spreadsheet
Senshin keeps your plan, RAID, budget and reports in one place, so this template stays current without a weekly copy-and-paste. A 14-day trial, with sample projects.
Start your 14-day trialFrequently asked questions
What should a weekly status report include?
Overall RAG, progress this week, plans for next week, milestones, changes to risks and issues, and any decisions or help needed.
Who is the weekly status report for?
The project team, the sponsor and the stakeholders who need to know about progress without attending every meeting.
How do I make a status report honest?
Report against a baseline, use dates instead of adjectives, and make sure the RAG matches the facts underneath it.