Highlight Report

What is a Highlight Report?

A highlight report is a short, regular progress report from a project manager to the project board or sponsor. It summarizes progress, status against tolerances, risks, issues and plans for the next period, and comes from PRINCE2.

Updated November 2026 · 2 min read


What a highlight report contains

In PRINCE2, the project board does not manage the project day to day. It sets limits, called tolerances, for time, cost and scope, and relies on the project manager to report regularly. The highlight report is that regular report. It is meant to be brief, often one or two pages, so the board can see quickly whether the project is on track or needs its attention.

SectionWhat it covers
Date and periodThe reporting period, set by the board, often every two or four weeks
Status summaryAn overall view, often with a RAG status
This periodWork packages and products completed
Next periodWork planned, and products due
Tolerance statusTime, cost, scope, quality, risk and benefits against agreed limits
Issues and risksChanges since the last report, with actions
Change requestsRequests raised, approved or pending
LessonsAnything learned that others should know

Highlight report vs other project reports

ReportFrom and toPurpose
Highlight reportProject manager to project boardRegular status during a stage
Checkpoint reportTeam manager to project managerProgress on a work package
Exception reportProject manager to project boardWarns that a tolerance is forecast to be exceeded
End stage reportProject manager to project boardSummary at the end of each stage, before approval of the next

The highlight report keeps the board informed without meetings. If a tolerance is at risk, the project manager raises an exception report instead of waiting for the next highlight report.

An example

A council's new parking-permit system is in its build stage. Every two weeks, the project manager sends a one-page highlight report to the board. This one shows amber overall: integration with the payments provider has slipped by eight days, still within the stage's ten-day time tolerance, and costs are on budget. One new risk is added to the RAID log: a supplier key person leaving. The board reads it, asks one question by email and takes no further action.

Writing a useful highlight report

  • Lead with the overall status and the one thing the board should know
  • Report against tolerances, not just tasks; the board cares about limits
  • Be specific about risks and issues: what, impact, owner, action
  • Keep it short and in the same format every time, so changes stand out
  • Do not soften bad news; early warnings are the point of the report

Common pitfalls

Highlight reports lose value when they become long activity logs, when every project is reported green until it suddenly turns red, or when nobody reads them. They also fail when the RAG definitions are unclear or differ between projects, which makes portfolio comparison impossible. Many PMOs now generate highlight reports from a portfolio dashboard or PPM software rather than writing them by hand. The general term outside PRINCE2 is a status report; see also project governance and steering committee.

Frequently asked questions

What is a highlight report in PRINCE2?

It is the regular report the project manager sends to the project board during a stage, at a frequency the board sets. It summarizes progress, overall RAG status, status against time, cost and other tolerances, risks, issues and work planned for the next period. It lets the board stay in control without frequent meetings.

How often should a highlight report be produced?

The project board decides the frequency, usually set in the project initiation documentation. Every two or four weeks is common, with shorter intervals for fast-moving or high-risk projects. The report should be regular and predictable, so the board can rely on it and spot changes from one report to the next.

What is the difference between a highlight report and an exception report?

A highlight report is a routine update sent at regular intervals. An exception report is sent only when the project manager forecasts that a tolerance, such as time or cost, will be exceeded. It explains the problem and options, and asks the board to decide how to proceed, rather than waiting for the next highlight report.