A project status report should help a stakeholder understand whether delivery is on track and what needs attention. Lead with overall status, then show progress, upcoming milestones, risks, blockers, decisions, and accountable owners.
Project status report template
- Project name and reporting period.
- Overall status with a short evidence-based reason.
- Work completed during the period.
- Next milestones, owner, and target date.
- Risks and blockers with mitigation and owner.
- Decisions needed, decision-maker, and deadline.
Make status evidence-based
Use milestone and task data, not optimism. Explain changes to scope, timeline, or dependencies. Do not mark work green because nobody raised an issue; confirm progress against acceptance criteria. Keep the report concise and link to the detailed tracker.
Use a reporting rhythm
Choose a consistent weekly time and audience. Collect updates asynchronously, then meet only for decisions or complex blockers. Good reporting surfaces risks early and reduces repetitive status conversations. See project management services.
How long should a status report be? Short enough to scan, detailed enough for a decision. It should be written by someone who can verify the information and follow through.
Write status for decisions, not decoration
A project status report is useful when a sponsor can understand the situation quickly and act where needed. Put the overall status and date first, then summarize progress against milestones, upcoming work, risks, blockers, budget or scope changes, and decisions required. Use plain language and distinguish confirmed facts from estimates. If a deadline is at risk, state the cause, impact, owner, and recovery options rather than hiding it behind a green status.
Choose a rhythm that matches project risk. A short internal project may need a weekly update; a high-change launch may need more frequent notes. Keep the report connected to the project tracker so people do not maintain two versions of dates and owners. When possible, send a concise written update before a meeting and use meeting time for trade-offs and decisions.
Status report checklist
- Project name, reporting date, and accountable lead.
- Overall status with the reason behind it.
- Milestones completed and next milestones due.
- Risks, blockers, dependencies, and response owner.
- Decisions needed, by whom, and by when.
Use consistent definitions for “on track,” “at risk,” and “blocked.” This improves communication across projects and helps leadership compare situations accurately. Close the loop by recording decisions and updating the plan immediately.
Frequently asked: How long should a status report be?
As short as possible while still explaining progress, exceptions, and decisions. A one-page summary is often enough, with links to detailed records when needed.
A worked example: a weak update and a useful one
The weak version: "Website project is going well. We made good progress this week and the team is working hard. A few things are pending but we should be fine." The reader learns nothing and cannot act.
The useful version takes the same facts and makes them specific.
- Overall: at risk. Launch is still planned for the 28th, but depends on one approval this week.
- Done this week: home and services pages built and reviewed. Booking form connected and tested.
- Next: about page and contact page built by Wednesday. Full site review on Friday.
- Blocker: final about-page copy has not been approved. Needed by Tuesday to keep the launch date.
- Decision needed: approve the copy as drafted, or send changes by Tuesday at noon.
The second version is shorter, and the reader knows the one thing they must do and by when.
Mistakes that make status reports useless
- Reporting activity, not progress. "Worked on the design" says nothing. "Design approved" does.
- Always green. If a project is reported as on track until the week it is late, the report was not honest. Flag risk early, while there is still time to respond.
- Burying the ask. If you need a decision, put it at the top with a date.
- Changing the format. Use the same headings every week so readers can scan it in a minute.
Where to start this week
Take your last update and rewrite it under five headings: overall status, done, next, blockers, decisions needed. Send that version this week and keep the format. A report is much easier to write when the project started with a clear scope, which is what a lean project management system sets up.
Want a second opinion on your operations?
Take the free Business Scale Readiness Assessment, or book a strategy call and I will tell you what I would fix first.