Project template
Weekly Project Status Report Template for Small Teams
A one-page format for sharing what changed, what comes next, where work is at risk and which decisions need an owner.
What a weekly project status report should answer
A weekly project status report should make the next decision easier. Keep it focused on the outcome, the work completed, the next deliverables, risks and decisions. It is a summary of progress, not a second copy of every task.
Copyable weekly status report template
One-page report
Project or workstream: Reporting week: Overall status: Green / Amber / Red Outcome or target: Completed this week: Planned next week: Blockers and risks: Decisions needed (decision / owner / date): Next actions (action / owner / due date): Changes to scope, dates, cost or priority:
| Field | What to include |
|---|---|
| Overall status | Define Green, Amber and Red with your team. Add the evidence behind the status. |
| Outcome or target | State the result the project should deliver, not only the activity list. |
| Completed and next | Name finished deliverables and the next work the team expects to complete. |
| Risks and blockers | Explain the likely impact and the action or decision that could address it. |
| Owner and due date | Give each next action one accountable owner and a clear date. |
| Changes | Note material changes to scope, timing, cost or priority since the last update. |
Filled example (fictional)
Project: New customer onboarding refresh · Week: 12–16 October · Status: Amber
- Outcome: Make the first-week onboarding steps easier to follow.
- Completed: Drafted the welcome email and mapped the first three steps.
- Next: Review the workflow with support and test the checklist with two internal reviewers.
- Risk: The final approval owner is not confirmed, which could move the review date.
- Decision: Operations lead to confirm the approval owner by Wednesday.
- Next action: Maya (fictional owner) sends the revised workflow by Friday.
How to run a 15-minute review
- Start with the intended outcome and the evidence behind the status.
- Ask owners for one completed result, one next action and one blocker.
- Separate risks that may happen from issues that have already happened.
- Record each decision needed with a named decision-maker and date.
- Share only changes that affect delivery; link to detailed work instead of copying it.
When work is blocked or overdue
Describe what is blocked, the effect on the outcome and the next action. “Waiting for feedback” is hard to act on. “The client approver has not replied; the account lead will follow up Tuesday” gives the team a clear owner and checkpoint. If a deadline has passed, record the new plan instead of leaving the old date unexplained.
Common mistakes
- Listing activity without saying whether the outcome moved forward.
- Marking a project Green because no one has raised a concern.
- Listing blockers without an owner or next action.
- Changing the format so readers must relearn it each week.
- Writing a long narrative when a short decision would unblock the work.
Frequently asked questions
How long should a weekly project status report be?
Start with one page. Include progress, next steps, risks, decisions and owners. Add detail only when the project needs it.
Who should write the status report?
The project owner can assemble it, while task owners provide updates about their own work. One person should publish the final report.
What is the difference between a status report and a task list?
A task list records individual work. A status report summarizes progress toward an outcome and highlights decisions or intervention needed.
How often should a status report be updated?
Weekly is a practical starting point for many teams. Fast-moving or high-risk work may need shorter intervals.
Keep the update connected to the work
Link important updates to the current project plan so the report stays a summary. Clarityy’s published pages describe project and task tracking. Review the project management workspace, task management use case and current plans before choosing a workflow.