Guide
Sign up free
How to write a project status report
A status report is read in two minutes by people with other things to do. Make those two minutes count.
Try it freeSee pricingFree for up to 3 plans of 50 lines.
Website launchAt risk
Status report · generated from the plan
34% complete · 7 days behind the baseline
11tasks
3done
2overdue
5on critical path
The outline
- Overall health. On track, at risk or behind, in one word, with the reason.
- Progress. Percent complete and what was finished since the last report.
- Schedule. Planned versus forecast finish. Use a baseline so the gap is a number.
- Risks and issues. What could or did go wrong, and what you are doing about it.
- Next period. What will be done, and who is on it.
- Asks. Decisions or help you need from the reader.
Tips
- Lead with the answer; details come after.
- Use numbers from the plan instead of adjectives.
- Keep the format the same every time so changes stand out.
GenuinePlan fills in health, progress, overdue tasks and variance from the plan: status report PDF.
Frequently asked questions
How often should I send a status report?
Match the pace of the project: weekly is common, fortnightly for slower work.
Related
Status reports
Stop rebuilding the Friday update by hand. Download a PDF made from the plan itself.
Read more →Project baseline
A baseline is a snapshot of the approved plan. Without it, you can see that dates moved but not by how much.
Read more →Due date reminders
A bell in the planner and an optional weekday email: what is overdue, and what is due today or next working day.
Read more →Plan your first project in a few minutes.
Free to start. Upgrade when you outgrow it.