Project management · Practical guide
Project Status Report Template: Progress, Risks and Decisions
By My First Task editorial team
Updated
The short answer
How to approach the work
A task export shows activity; a status report explains what that activity means for delivery. Define the audience and reporting period before choosing metrics. A red, amber or green label is useful only when the team agrees its meaning and explains the evidence. Separate an observed issue from a risk that might occur. Report a forecast as a forecast, with assumptions, rather than turning a hopeful date into a commitment. Keep the narrative short enough for readers to find the requested decision.
A practical sequence
- State the project outcome, reporting period and report owner.
- Summarize completed deliverables with evidence or links.
- Compare the current milestone forecast with the previous commitment.
- Explain active issues and future risks separately.
- List decisions needed with an owner and decision date.
- Name the next reporting date and the work planned before it.
Illustrative scenario · not customer research
Worked example
For a sample website project, the weekly report says the product pages passed content review, while checkout testing is waiting for test credentials. Launch is amber under the team's definition because testing cannot start until access arrives. The decision requested is whether the sponsor can arrange access by Tuesday or approve a revised launch date. '18 of 24 tasks complete' is included as supporting context, but the report explains that the remaining testing work controls the release. Task count alone does not establish that the project is 75% ready to launch.
Copyable project status report
Adapt this starting point to your own project. Examples describe a planning practice, not an automated app workflow.
| Section | Prompt |
|---|---|
| Project and period | [Project] · [start–end] · Report owner: [name] |
| Overall status | [Status] because [evidence and delivery impact]. |
| Delivered | [Outcome] accepted by [reviewer]; evidence: [link]. |
| Next | [Deliverable] · [owner] · [agreed date]. |
| Risks and issues | [Condition] → [impact] → [mitigation owner]. |
| Decision needed | [Decision] from [person] by [date]. |
Common mistakes to avoid
- Reporting completed task count as a precise measure of remaining effort.
- Giving a status color without the reason and next action.
- Hiding a decision request in a long activity log.
Try the method with your own inputs
Questions answered
How often should I send a project status report?
What belongs in a one-page report?
Can a completion percentage predict the finish date?
Apply it in a shared workspace
Keep the agreed owner, completion criteria and important decisions with the work. Explore the relevant My First Task feature.
Research context is available in our source library. The worked example above is an editorial illustration.
Continue learning
Scope Creep: Examples and a Practical Change Checklist
Scope creep is growth in project work without an explicit agreement about its effect on time, cost or the intended outcome. Manage it by documenting the baseline, recording proposed changes and making the trade-off visible before accepting more work.
ExploreMilestones vs. Tasks: Project Planning Examples
A task describes work to perform; a milestone marks a significant checkpoint or accepted outcome. Use tasks to assign the work and milestones to communicate whether the project has reached an agreed stage.
ExploreAsynchronous Status Updates That Lead to Decisions
An asynchronous update lets people review progress without attending at the same time. A useful update states what changed, what happens next and which decision or help is needed, with an owner and response deadline.
ExploreTurn the plan into shared work
Give each next action an owner, a completion condition and a realistic date. My First Task brings tasks, boards, project workflows and issue tracking into one workspace.