Weekly Project Status Report (Word)
A short weekly report (one to two pages) that a sponsor can read in two minutes. It opens with the overall Red, Amber or Green status and a three-line summary, then shows schedule, cost, scope and quality status, what was done this week, what comes next, the milestone dates, the top risks and issues, and the decisions you need from the reader.
Free · no sign-up · opens in Microsoft Word, Google Docs, LibreOffice and WPS Office. Files contain no macros.
Preview
Real view of the file with its sample data (yellow cells are where you type).
WEEKLY PROJECT STATUS REPORT
[Project name]
| Report no. | [12] | Period | [DD-MMM] to [DD-MMM-YYYY] |
| Project manager | [ ] | Sponsor | [ ] |
| Overall status | [GREEN / AMBER / RED] | Target go-live | [DD-MMM-YYYY] (forecast [DD-MMM-YYYY]) |
Summary
Three lines: progress, the main problem, and what you need from the reader.
[Example: Design is 90% done and the build has started. Approval of the design is two days late because the sponsor is travelling. Decision needed: who can approve the design by Wednesday?]
Status by area
| Area | Status | Comment |
| Schedule | [G / A / R] | [ ] |
| Cost | [G / A / R] | [ ] |
| Scope | [G / A / R] | [ ] |
| Quality | [G / A / R] | [ ] |
| Resources / team | [G / A / R] | [ ] |
Key: GREEN = on track. AMBER = at risk; the team has a plan to recover. RED = off track; needs a decision or help from the sponsor.
Done this period
• [Example: Home page and contact page mockups delivered]
• [ ]
• [ ]
Planned for next period
• [Example: Design sign-off meeting on Wednesday]
• [ ]
• [ ]
Milestones
| Milestone | Planned | Forecast | Status |
| [Design approved] | [DD-MMM] | [DD-MMM] | [On track / At risk / Late / Done] |
| [ ] | |||
Top risks and issues
| Risk or issue | Impact | Owner | Action and date |
| [ ] | [High / Medium / Low] | [ ] | [ ] |
| [ ] | |||
Budget snapshot ([currency])
| Budget | Spent to date | Forecast at completion | Variance |
| [ ] | [ ] | [ ] | [ ] |
Decisions or help needed
| Decision or help needed | From whom | Needed by |
| [ ] | [ ] | [DD-MMM-YYYY] |
…
What's inside
- Header: project, reporting period, project manager, sponsor and report number
- Overall RAG status with a short explanation, and a RAG key that defines Green, Amber and Red
- Status by area: schedule, cost, scope, quality and resources, each with a comment
- Accomplishments this period and planned for the next period
- Milestones table: planned date, forecast date and status
- Top risks and issues with owner and action, and a "decisions or help needed" box
- Budget snapshot: budget, spent, forecast and variance
How to use it
- Copy last week's report and change the period and report number.
- Update the milestones table and the budget snapshot first: they decide the RAG status.
- Set the status of each area (Green, Amber or Red) using the key on the page, then the overall status.
- Write the summary last: three lines on progress, the main problem and what you need.
- List decisions you need with a date by which you need them.
- Send it on the same day every week, as PDF (File › Save As › PDF).
Tips
- Amber with a plan is better than a surprise Red. Report problems early.
- Use the same RAG rules every week so the colours mean something.
- Prefer the online status report maker in this toolkit when you want the report ready to print in two minutes.
Questions and answers
What does RAG status mean?
Red, Amber, Green. Green: on track. Amber: at risk, but the team can recover it. Red: off track; the sponsor needs to decide or help.
How long should a status report be?
One or two pages. If the reader needs more, attach the plan or the registers.
Who should get it?
The sponsor and the key stakeholders listed in the charter, and the project team so everyone sees the same picture.