Status Report
A standardised procedure for preparing and distributing regular project status reports that communicate progress, issues, risks, and upcoming activities to all stakeholders.
Purpose
To provide stakeholders with a consistent, timely, and accurate view of project health so they can make informed decisions, provide timely support, and maintain confidence in the project delivery.
Scope
Covers the preparation and distribution of regular status reports throughout the active delivery phase of the project, from kickoff to closure.
Prerequisites
- Approved project plan with defined milestones and deliverables for progress tracking
- Status report template agreed with stakeholders covering the required content areas
- Reporting cadence and distribution list confirmed in the communication management plan
- Access to current project data from the project management tool and time tracking system
Step-by-Step Procedure
Collect Progress Data
Gather up-to-date information from all work streams, team members, and project systems to form an accurate picture of current project status.
- 1.1Review the project management tool for task completion status, percentage complete, and any overdue items
- 1.2Collect updates from work stream leads on their progress, blockers, and upcoming activities
- 1.3Pull financial data including budget spend to date and forecast remaining costs
Assess Overall Project Health
Evaluate the collected data against the project plan to determine the overall health status and identify any areas requiring attention or escalation.
- 2.1Assess schedule health by comparing actual progress to the planned timeline
- 2.2Assess budget health by comparing actual spend to the planned budget profile
- 2.3Evaluate risk and issue status to determine their contribution to overall project health
- 2.4Assign a traffic light status for each dimension and an overall project health rating
- Define clear criteria for each traffic light status so ratings are consistent and objective
Draft the Status Report
Compile all collected information and assessments into the standard status report template, ensuring the content is clear, concise, and actionable.
- 3.1Complete the executive summary section highlighting the most important information for leadership
- 3.2Populate the detailed sections covering schedule, budget, risks, issues, and resource status
- 3.3List key accomplishments for the reporting period and planned activities for the next period
- 3.4Note any decisions or support needed from stakeholders
Review and Approve the Report
Have the draft report reviewed by appropriate parties to verify accuracy and completeness before distribution.
- 4.1Share the draft with work stream leads to verify the accuracy of their sections
- 4.2Incorporate any corrections or additions from the review
- 4.3Obtain final approval from the project sponsor if required by the project governance framework
Distribute the Status Report
Send the finalised status report to all stakeholders on the distribution list via the agreed communication channels.
- 5.1Distribute the report to the full stakeholder distribution list by the scheduled reporting deadline
- 5.2Archive a copy of the report in the project document repository for historical reference
Follow Up on Outstanding Actions
Track any actions, decisions, or escalations arising from the status report and follow up with responsible parties to ensure they are addressed.
- 6.1Log any new action items identified in the status report in the project action tracker
- 6.2Follow up with stakeholders on any decisions or support requested in the report
- 6.3Update the action tracker with progress and carry forward outstanding items to the next report
Quality Checkpoints
Common Mistakes to Avoid
Expected Outcomes
Percentage of status reports distributed on or before the scheduled deadline throughout the project duration
Average stakeholder rating of the usefulness, clarity, and timeliness of project status reports as measured by periodic feedback surveys
Frequently Asked Questions
How frequently should status reports be issued?
Weekly reporting is the most common cadence for active projects. Fortnightly reporting may be sufficient for low-risk projects or during quiet phases. High-profile or troubled projects may require more frequent updates. The cadence should be agreed during project setup.
What is the difference between a status report and a dashboard?
A dashboard provides a real-time or near-real-time visual snapshot of key metrics and is typically accessed on demand. A status report is a periodic document that provides context, analysis, and narrative commentary beyond what raw metrics show. Most projects benefit from both.
Should the status report include financial details?
Yes, budget status should be included at an appropriate level of detail. Senior stakeholders typically need a summary showing budget versus actual spend and forecast. Detailed financial breakdowns can be provided in a separate finance report if needed.
Want this customised for YOUR business?
We'll tailor every step to your exact operations, tools, and team structure.