Free Project Status Report Template: Excel Download

01 · Template Sections

What's in the Template: All 8 Sections

The status report is structured to answer the questions sponsors ask in a predictable sequence: Where are we? What happened? What's next? What are the problems? What do you need from me? The template follows that logic, the most urgent information first, the detail later.

✦

From my experience: I kept my status reports to one page on every project I managed in the UAE. Sponsors read the RAG status and the decisions needed from them, and rarely much else, so this template puts those two things first.

Report Header

Project name, reporting period, PM, sponsor, overall RAG status, percentage complete and next milestone. The header answers "what is this and how is the project doing?" before the reader reaches Section 2.

Executive Summary

Three sentences maximum. Current status, the most significant development this period and the biggest risk or issue requiring sponsor attention. A sponsor who reads nothing else reads this. It must earn its own weight every month.

RAG Status by Dimension

Six rows: Schedule, Budget, Scope, Quality, Resources, Risks & Issues. Each with a RAG colour, a one-line status note and space for brief context. The source material for the project dashboard.

This Period: Achievements

Bullet list of what was actually completed or progressed this reporting period. Specific and verifiable, not "good progress on testing" but "integration testing completed for modules 1–4; 94% pass rate; 6 defects raised, 4 resolved".

Next Period: Planned Work

What will be completed or progressed in the next reporting period. Sets expectations, the sponsor knows what to ask about at the next governance meeting, and the PM is accountable for delivering it.

Key Issues and Risks

Top 3 issues (with owner, due date and status) and top 3 risks (with likelihood, impact and mitigation). Only the most significant, the issue log and risk register contain the full detail. The status report surfaces the items the sponsor needs to know about.

Budget Summary

Four numbers: planned spend to date, actual spend to date, variance and forecast at completion (EAC). Plus a one-line narrative explaining any significant variance. These four numbers answer 99% of the budget questions a sponsor asks.

Actions Required from Sponsor

The most important section in the report. A specific list of what the PM needs the sponsor to decide, approve, unblock or communicate: with a clear ask, a rationale and a required-by date. A PM who never has anything in this section is not using their sponsor effectively.

✦

Section 8 is the most important section. The status report is not just a record. It is a communication tool for getting things done. The Sponsor Actions section turns a passive report into an active request. If you need a decision by Friday, if you need a difficult stakeholder escalated, if you need budget approval for a change request. This is where you put it. A specific, time-bound ask in writing is far more likely to get a response than a verbal request in a meeting.

02 · Writing Well

How to Write a Status Report Sponsors Actually Read

Status reports fail for two reasons: they are too long, or they bury the important information in dense narrative. The solution is not shorter reports. It is more structured ones. Every section should answer one question, answer it directly and stop.

The Executive Summary: Three Sentences, One Rule

The executive summary should never exceed three sentences. One for current status ("The project is on track for the 28 March go-live date: SPI 1.02, CPI 0.98"). One for the key development this period ("Integration testing completed with 94% pass rate: on plan"). One for the most significant concern ("Integration with the legacy billing system is amber: vendor documentation gap is being resolved but creates a 3-day risk to the UAT start date").

✗ Weak Status Summary

"The project is continuing to progress well and the team has been working hard this month. There are some issues with the integration work but we expect these to be resolved soon. Testing is going well and we are broadly on track for delivery."

Vague on every dimension. "Some issues", "broadly on track", "expect to resolve": none of these inform a decision. The sponsor reading this knows nothing more than before they read it.

✓ Strong Status Summary

"The project is on track: SPI 1.02, CPI 0.98, 62% complete against 61% planned. Integration testing completed Modules 1–4 this period with 94% pass rate; 4 defects outstanding, all P2 or below. The legacy billing integration is Amber: vendor API docs delayed by 5 days, creating a 3-day risk to the 14 April UAT start. Mitigation plan in Section 6."

Specific numbers, named achievement, specific risk with quantified impact and a pointer to the mitigation. A sponsor reads this in 30 seconds and knows the project's position precisely.

The Budget Section: Four Numbers, One Sentence

The budget summary needs exactly four numbers: planned spend to date, actual spend to date, variance in currency and variance as a percentage. Then one sentence explaining the variance if it is more than ±5%. Anything more than that belongs in the EVM tracker or budget variance report, not the status report.

Issues and Risks: Top 3 Only

The status report should surface the top 3 issues and top 3 risks, not the entire issue log and risk register. The selection criterion: which items would the sponsor most need to know about to have an informed discussion in the governance meeting? Everything else stays in the detailed registers. Listing 12 risks in a status report signals poor prioritisation, not thoroughness.

✦

Send the report before the meeting: not in the meeting. A status report shared 48 hours before the governance meeting gives the sponsor time to read it, form views and arrive with informed questions. A report circulated in the meeting means the first 15 minutes are spent reading rather than discussing. The pre-read is not a courtesy. It is what makes governance meetings productive.

03 · Related Documents

Status Report vs Dashboard vs KPI Tracker

Three reporting documents serve different needs in the monthly reporting cycle. They are not duplicates. Each answers a different question for a different audience.

This Template

Status Report

Question: What happened, why, and what next?

Length: 1–2 pages with narrative

Cadence: Monthly / fortnightly

Audience: Sponsor, steering committee

Companion Documents

Dashboard & KPI Tracker

Dashboard: One-page visual health summary: RAG + metrics, no narrative. Sits on the cover of the reporting pack.

KPI Tracker: Detailed metric history by period: shows trends over time. Referenced in the budget section and RAG dimensions.

The monthly reporting pack sequence: dashboard (cover, 30-second scan) ? status report (body, 3-minute read) ? KPI tracker (appendix, available if the sponsor wants to dig into numbers). The entire pack should be readable in 5 minutes: anything longer will not be read in full.

04 · FAQ

Status Report: 4 Common Questions

A project status report should include: an overall RAG status and reporting period; a brief 2–3 sentence executive summary; what was achieved this period; what is planned for the next period; key issues with owners and resolution dates; key risks with likelihood, impact and mitigation; a budget summary (planned vs actual spend, variance, forecast); and decisions or actions required from the sponsor. It should not exceed two pages, a status report that requires extensive reading defeats its own purpose.

Monthly is the standard cadence, aligned with the typical governance cycle. For fast-moving or high-risk projects, fortnightly reporting may be appropriate. Weekly reporting is generally too frequent to show meaningful change and creates a disproportionate reporting burden. The frequency should be agreed with the sponsor at project start and documented in the communications plan. Whatever the cadence, the report should always be distributed 48 hours before the governance meeting, not in the meeting itself.

A project dashboard is a one-page visual summary showing key metrics and RAG status without narrative: designed for a 30-second scan. A status report provides narrative context around the current position: what happened, why, and what is being done about it. Both serve different audiences and purposes: the dashboard is for executives who need a quick health check; the status report is for the sponsor and steering committee who need to understand and discuss the position. A monthly reporting pack includes both: dashboard on the cover, status report as the body.

The primary audience is the project sponsor and steering committee, the people with authority to make decisions and provide resources when escalation is needed. Secondary audiences may include the PMO, programme manager, key stakeholders and the project team. The same report may not be appropriate for all audiences: a detailed status report for the steering committee may need to be summarised to a single paragraph for a broader stakeholder newsletter. The communications plan should define who receives what format and at what frequency.

Free Project Status Report Template Excel Download