Guides /

Project status report vs executive status report

How a project status report differs from an executive status report by audience, depth, and length, with steps to build the sponsor version.

By The Unblockd teamPublished

Also in Español, Nederlands

A project status report is the working record a team uses to run one project: progress, work remaining, risks, and the detail behind each. An executive status report is a shorter version for a sponsor or steering committee, built around health, milestones, risks, and the decisions they need to make. Use the project report to run the work, and the executive report to get the sponsor's decision.

What is the difference between a project status report and an executive status report?

A project status report tracks how one project is progressing, with tasks, deliverables, and risk detail for the people doing the work. Both draw on the same evidence but differ in reader, depth, and the question each answers.

The table is the author's summary of how the sources below describe each report. It is not a quotation from any of them.

Project status report Executive status report
Main reader Delivery team and working stakeholders Sponsor or steering committee
Question it answers Where the work stands and what comes next Whether the project is on plan and what needs a decision
Level of detail Tasks, responsibilities, and dependencies Outcomes, business impact, and decisions

MustardSeed PMO puts the split this way: the team report covers the "how" of tasks and responsibilities, while the executive report covers the "so what" of outcomes, business impact, and decisions.

Which report should you write for each reader?

Write the project status report for the people who run the work, and the executive status report for the sponsor who has to decide something. Ask these questions before you draft: who will read it, and what will they do after reading it?

  1. Name the reader and the action they take after reading: "[Reader name] will [review, approve, or decide] [item] before [meeting or date]."
  2. Write the one thing you need from them and the date you need it: "[Decision or help needed] by [date]."
  3. If you cannot fill in step 2, the document is a status log. Keep the project status report for the team, and hold the sponsor version until there is a decision or help to ask for.

How long should each report be?

The executive status report should be short enough to read before a decision meeting, with health in the opening lines. The project status report has no fixed length; it should hold enough detail for the team to act without opening another file. MustardSeed PMO suggests keeping the executive summary under six sentences.

Treat the reading-time test below as the author's judgment, not a sourced figure. If the sponsor reads between meetings, put the health, the top risk, and the decision in the first lines, and place the rest below them.

How do you build the executive version from the project report?

Build the executive status report by cutting down the project report, not by writing a second document from scratch. Keep the overall status, the milestones that moved or come next, the risks that need a response, and the decisions the sponsor must make. Link to the full project report rather than pasting it in.

  1. Copy the overall status and the date it is true for: "[Project name] is [on track / at risk / behind] against [milestone] as of [date]."
  2. List only the milestones due before the next sponsor review, plus any that moved. Show both dates: "[Milestone] moved from [old date] to [new date] because [reason]."
  3. Move a risk up only if it passes the test in the next section.
  4. For each open problem, write one line with the response, the owner, and the date.
  5. Link to the full project report and the risk log instead of pasting them in. EPW advises that a status report should link to detailed registers rather than copy them.
  6. Read the summary as the sponsor. Can they answer from the summary alone?

Which items move from the project report to the executive report?

An item moves up when the sponsor must know about it or decide on it to protect a milestone, budget, or scope the sponsor has named. Team-only detail, such as routine task completion or an internal dependency the team resolves, stays in the project report. The sources do not give a cut-off, so this test is the author's judgment.

Check the item against both of these with your sponsor:

  • The team cannot close the item without the sponsor's decision or help.
  • The item threatens a date, budget, or scope limit the sponsor has already named.

If neither is true, keep the item in the project report, and adjust the test with your sponsor after the first update.

What does one risk look like in each report?

A risk appears in the project status report as a detailed log entry and in the executive status report as one line with a response, an owner, and a date. The example below uses placeholders for every fact, so you can replace them with your project's details.

Illustrative example. The project report keeps the detail:

[Risk ID]: [Vendor name] has not confirmed [deliverable] for [workstream]. Blocks [number] tasks. Owner: [team member]. Next review: [date]. Log reference: [log reference].

The executive summary keeps the milestone, the response, the owner, and the date:

[Milestone] at risk: [Vendor name] has not confirmed [deliverable]. Response: [action], owner [name], by [date]. Choice needed: [option A] or [option B], by [date].

The task count and the log reference stay in the project report. The sponsor can reach the full entry through the link in the summary.

What mistakes make the executive report less useful?

The most damaging mistakes are sending a task list with no decision in it, holding a risk back until it is late, and leaving out the next step. MustardSeed PMO names too much detail, hidden risks, no path forward, and missing executive priorities as common mistakes.

Check these before you send:

  • The health sentence appears in the first lines, not below the task list.
  • Every risk shown has a response and an owner.
  • Every choice needed names the date it is needed by.
  • Every fact in the executive version appears in the project report, so the sponsor can check any line against it.

Do the sources agree on what an executive status report is?

In the author's reading, the sources agree on the core contrast but not on classification. Plane and status.net list the executive report beside daily and weekly reports as a type, while MustardSeed PMO treats it as a version written for a different reader. EPW does not define it.

Plane's wording is the most useful guide here: the format and depth may shift depending on the audience, but the core purpose stays the same. Status.net describes the executive report as a brief, high-level summary for top management, with status indicators and decisions needed. Treat the executive version as written for a different reader. The team report and the sponsor report can run on different rhythms and still share the same evidence.

Which report should you send next?

Send the project status report to the team on the rhythm it already uses, and send the executive status report to the sponsor before the review where they decide. Link the executive version to the full project report so the sponsor can check any line.

Next step: pick the sponsor's next review date, draft the summary from your latest project report using the steps above, and ask the sponsor to reply by [date].

Questions people ask

Can one document serve both the team and the sponsor?

Usually not well. A single document with the full task list and the sponsor's decision tends to bury the decision. Keep the project status report for the team and a short executive version that links back to it.

What if the sponsor asks for the full project report?

Send the link and name the section to read first, such as the top risk line or the decision. Keep the full report out of the email so the sponsor's message stays short.

Does a steering committee need a different report from a single sponsor?

Start with the same executive version you would send a sponsor. Then ask the chair whether the committee needs a view across several projects before adding that section.

How do I know the executive report is working?

Check whether the sponsor replies with a decision or a question by the date you asked for. If they keep asking for the same detail, move that detail into the summary for the next update, and remove any section they never use.

The Unblockd team

Unblockd helps teams deliver projects faster by getting stuck work in front of the sponsor who can clear it: an AI agent drafts the ask from the project's evidence, the team checks and sends it, and the sponsor answers without signing up.

Get the sponsor ask checklist

One screen to check before you send an ask: the decision, the options, the date, and what waits on it. Then one email a week with new guides.