Skip to content
0 / 66 sessions

Course contents

Module 10 of 13 · 66 sessions

PRINCE2® Foundation

Free
Course overview

Course progress

0%

0 of 66 sessions complete

Sign in to save your progress across devices.

Module 10Session 53 of 6613 minKnowledge check

Progress reports

The reports that carry progress information up and down the project, who writes them and who reads them.

Sign in to track progress
Guided lesson
~0:22Scene 1 of 7
123

Scene 1

Progress reports

The reports that carry progress information up and down the project, who writes them and who reads them.

Caption 1 of 3

Describe the purpose of each PRINCE2 report

0:00 / 0:22
Read all scene text
  1. Describe the purpose of each PRINCE2 report
  2. Identify who produces and receives each report
  3. Explain how reports support management by exception

Scenes animate with GSAP. Use pause or replay at any time.

In this session

  • Describe the purpose of each PRINCE2 report
  • Identify who produces and receives each report
  • Explain how reports support management by exception

It's time to follow the York reports through a typical fortnight.

Let's say it's week 8. You're in Leeds baking and haven't been to York for two weeks. Yet you know exactly how the building works are going, what's at risk and what's coming next.

How do you know?

Select the arrow to learn more

1 of 4

From the team

Every Friday, the site foreman sends Sam a checkpoint report: what got done, what's next and any problems.

Regular reports

Two reports are produced at regular intervals:

  • Checkpoint report: from a team manager to the project manager, at the frequency agreed in the work package
  • Highlight report: from the project manager to the project board, at the frequency agreed in the stage plan

Event-driven reports

Other reports are triggered by events:

  • End stage report: from the project manager to the board, at the end of each stage
  • End project report: from the project manager to the board, at closure, reviewing how the project did against its baselines
  • Exception report: from the project manager to the board, when a stage or project is forecast to exceed tolerance
  • Issue report: describes a formal issue and recommends a response
  • Lessons report: passes lessons on to the wider business

Keep reports useful

A report should help someone decide or act. Sam's highlight report fits on one page and starts with what you need to know, not a list of every task.

For the app, Ana's checkpoint report might be the team's end-of-cycle demo plus a short note. Reports don't have to be documents; they can be dashboards, meetings or messages, as long as the information gets through.

Reports and decisions

Reports are linked to decisions. The end stage report supports the board's decision to authorise the next stage. The exception report supports its decision on how to handle an exception.

That's why reports must be honest and timely. A highlight report that hides a problem stops the board deciding at the right moment.

Key points to remember

  • Checkpoint reports go from team managers to the project manager.
  • Highlight reports go from the project manager to the board at regular intervals.
  • End stage, end project, exception, issue and lessons reports are event-driven.
  • Reports should be honest, timely and in whatever format does the job.
Knowledge checkQuestion 1 of 4

Knowledge check

Choose one answer

Practices

Which report reviews how the whole project performed against its baselines?

Which report reviews how the whole project performed against its baselines?
Choose one answer to continue.

Sign in to save your result. Knowledge checks can be retried any time.

PRINCE2® is a registered trademark of the PeopleCert group. MockAcademy is independent and not affiliated with, endorsed by or licensed by PeopleCert.