Project Status Report Pre-Send Checklist: Required Items to Include Before Sending
Before sending a project status report, you must include a clear executive summary, core progress updates, budget and timeline status, risk updates, and assigned next steps for all stakeholders.
- Most important section for C-suite stakeholders
- 1-2 paragraph executive summary with overall project health status
- Standard project health coding
- Green = on track, Yellow = at risk, Red = off track
- Top mandatory metrics to include
- Percent complete, budget spent, timeline variance, active risks
- Final pre-send verification time
- 2-5 minutes to fact-check all metrics and action item assignments
- Most common missing pre-send item
- Explicit owner and deadline for each listed next step
Executive Summary
This 2-3 sentence opening is non-negotiable for busy senior stakeholders who may only read the first paragraph of your report. It must state the project’s overall health, typically coded green/yellow/red per your organization’s standard, whether you are on track for key deliverables, and 1-2 top high-priority updates that require stakeholder attention. Skip jargon here: keep it accessible for cross-functional stakeholders who do not work on the project day-to-day.
Core Progress and Performance Metrics
This section confirms you have delivered on work promised since the last status report. It must explicitly reference the goals outlined in your previous report, so stakeholders can easily compare planned vs. completed work.
Required progress details to include:
- Percentage of work completed for the current reporting period
- Status of all key milestones scheduled for the period, with notes on early, on-time, or delayed delivery
- Customer or team feedback highlights that impact project direction
Do not include granular task-level updates that do not impact broader project outcomes. Focus only on metrics that are tied to the project’s formal success criteria.
Budget, Timeline, and Resource Status
These three core constraints are the most common questions stakeholders ask, so they must be clearly documented in every status report before sending. For budget, state the percentage of allocated funds spent to date, and any expected overages or underspends that will impact the final project cost. For timeline, confirm your current projected completion date, and note any shifts from the original baseline timeline, along with root causes for delays. For resources, note any gaps in staff, tools, or vendor support that are impacting delivery, or any upcoming resource reallocations that will change project velocity.
Risk, Blocker, and Change Request Updates
Never send a status report that hides risks or blockers, as this can lead to unaddressed issues that derail the project later. For each active risk, state its likelihood, potential impact, and any mitigation steps you are already taking. For active blockers, explicitly state what support you need from stakeholders to resolve the issue, and the deadline by which you need that support to avoid delays. If there are any approved or pending change requests to the project scope, budget, or timeline, include those here with a note pointing to the formal change request document for reference.
Final Pre-Send Verification Checklist
Before you hit send, run through this quick checklist to confirm you have not missed any mandatory items:
- All dates, metrics, and stakeholder names are fact-checked for accuracy
- You have noted who is responsible for each upcoming action item, with clear deadlines
- You have removed any internal-only notes or draft comments that were not intended for stakeholders
- The report is formatted to match your organization’s standard project status report requirements
- You have added contact information for the project lead for follow-up questions
Even if you are using an automated tool to generate your status report, this manual verification step ensures you avoid common errors that can reduce stakeholder trust in your project updates.
Step by step
- Draft core sections first Write the executive summary, progress update, budget/timeline status, risk section, and next steps before running your pre-send check.
- Fact-check all data points Verify all metrics, dates, stakeholder names, and action item owners are accurate to avoid errors that reduce stakeholder trust.
- Run through pre-send checklist Confirm all mandatory items are included, internal comments are removed, and the report matches your organization’s required format.
- Confirm recipient list is correct Double-check you are sending the report to all relevant stakeholders, and omit recipients who do not need access to project status details.
FAQ
Do I need to include every small task completed in the report?
Can I omit minor risks from the pre-send report?
Should I adjust metrics to make the project look better before sending?
Do I need to include change requests that are still pending approval?
Still have a question about Project Status Report?
Ask the AI Office Work assistant - it answers in your words and can turn the answer into a document.
Ask AI