Weekly Project Status Report: Template and Examples
A weekly project status report gives stakeholders a regular, honest view of progress against the formal plan. Use it to show what was completed, what comes next, and anything that could affect timeline, budget, or delivery.
What a status report does
A project status report is a recurring document that compares actual progress with the formal project plan. It is commonly reviewed in weekly or biweekly meetings with stakeholders, clients, and team members.
Its job is to keep everyone aligned on moving parts, surface expectations set at the start, and make work, process, budget, and problems visible early. Regular, transparent reporting helps build trust because readers do not have to guess what is happening.
Decision check before you send: Can a busy stakeholder answer, in under a minute, what changed, what is next, whether time and money are on track, and what decision or help you need?
Seven sections to include
Adapt the structure to your project. Not every section fits every project, and that is acceptable. Send the report by email, Slack, or in your project tool, then follow up in person, by phone, or by video to discuss it.
Share as much relevant detail as you can. Transparency is the point: when teams and clients have the same facts, they can act sooner.
Use this seven-part order:
- Introductory note — flag the hot topics so readers know where to focus before the follow-up discussion.
- Summary — brief bullets on what did and did not happen last week, plus what you expect this week. Cover tasks, deliverables, meetings, communications, and decisions.
- Overall project timeline completion — give the whole-project percentage and a percentage for each phase, deliverable, or task group.
- Budget status — show overall budget or task budgets, and consider percentage spent versus hours spent. Add a note when a number might worry clients or executives, and agree internally how transparent to be.
- Upcoming tasks and milestones — use a table for specific items, including holidays or events people need to note. Detail here is not redundant with the summary; it is the scannable forward look.
- Action items — list to-dos that affect timeline or budget, with a named owner for each so expectations are clear.
- Project risks, issues, and mitigation plans — describe risks and issues in detail and be ready to discuss them. Keep this section even when there is nothing to report; stating that you are actively watching for problems, and ending on a positive note when clear, is itself useful information.
Keep status current between reports
Keep the live plan current so the report writes itself from real data:
- Update task progress in the Gantt chart as work happens. If stakeholders have a view-only link, they can see progress in real time.
- When tasks lag, use a request-progress-update prompt to nudge owners to update their tasks.
- Watch estimated versus actual hours. A red striped line on a taskbar means tracked hours exceed estimated hours, so the task is over budget. If the striped line is longer than the progress shown, time spent is outpacing progress and the task is at risk of overage.
- Use a project health snapshot for a daily or weekly at-a-glance view. It breaks down how many tasks are on time, running behind, or overdue, and lets you drill into details behind the numbers.
Pre-send checklist
Before sending, run this checklist:
- Intro points to the two or three items that need attention.
- Summary bullets cover last week, this week, decisions, and communications.
- Timeline percentages are updated for the whole project and each phase.
- Budget figures match tracked hours and include context for any variance.
- Upcoming milestones are in a table with dates.
- Every action item has an owner.
- Risks have a mitigation step, or the section explicitly says none were found.
- You have scheduled the follow-up conversation.
| Signal | What it means | What to do |
|---|---|---|
| Red striped line | Tracked hours exceed estimated hours | Treat as over budget; explain cause and correction |
| Striped line longer than progress | Time spent outpacing progress made | Treat as at risk of overage; intervene early |
| Tasks running behind or overdue in health snapshot | Progress is slipping against plan | Drill into details and update the report |
Hourly estimation and time tracking required for the striped-line signal.
Frequently asked questions
How can I share this guide?
Share on LinkedIn, X, or Facebook using the share controls on the page.