5.5 Management Reports & Logs/Registers
Key Takeaways
- PRINCE2 7 classifies management products into three categories: Baseline Products, Records (logs/registers), and Reports.
- Logs and Registers act as dynamic repositories storing live data: Daily Log, Lessons Log, Risk Register, Issue Register, and Quality Register.
- Management Reports provide structured communication across governance levels: Checkpoint, Highlight, End Stage, End Project, Exception, and Lessons Reports.
- The Daily Log captures informal day-to-day items and minor risks, whereas the Risk and Issue Registers hold formal project controls.
- The End Stage Report provides the evidence required by the Project Board to decide whether to authorize the next management stage.
Last updated: July 2026
5.5 Management Reports & Logs/Registers
Information is the lifeblood of effective project governance. In PRINCE2 7, governance relies on standardized management products that capture data, record decisions, and communicate progress. Understanding the exact purpose, author, target audience, and trigger for each management product is vital for the PRINCE2 7 Foundation examination.
Classification of PRINCE2 Management Products
PRINCE2 divides all management products into three primary categories:
- Baseline Products: Documents that define project targets, plans, approaches, and product specifications. Once approved, they can only be changed via formal change control (e.g., Project Initiation Documentation, Stage Plans, Product Descriptions).
- Records (Logs & Registers): Dynamic management products that continuously record operational data, events, risks, issues, and quality activities throughout project execution.
- Reports: Structured communication products used to report status, performance, stage completion, or exceptions to decision-making bodies.
Detailed Examination of Logs & Registers (Project Log)
In PRINCE2 7, the following logs and registers are maintained as part of the Project log—the living set of records used for day-to-day control.
1. Daily Log
- Purpose: An informal repository maintained by the Project Manager to record day-to-day events, informal issues, minor risks, task commitments, and observations that do not warrant formal logging.
- Owner/Author: Project Manager.
- Lifecycle: Created during Starting up a Project, updated continuously throughout delivery.
2. Lessons Log
- Purpose: A repository used to record lessons learned from previous projects or identified during the current project that can be applied immediately or shared across the organization.
- Owner/Author: Project Manager.
- Key Distinction: Information in the Lessons Log is aggregated into the formal Lessons Report at stage boundaries and project closure.
3. Risk Register
- Purpose: A formal record of all identified risks (threats and opportunities), including risk statements, probability/impact scores, response strategies, risk owners, and implementation status.
- Owner/Author: Maintained by the Project Manager (with updates from Team Managers and Risk Owners).
4. Issue Register
- Purpose: A formal record of all captured issues (Requests for Change, Off-Specifications, and Problems/Concerns), detailing issue descriptions, severity ratings, impact assessments, and decisions.
- Owner/Author: Project Manager / Project Support.
5. Quality Register
- Purpose: A formal record of all planned and completed quality management activities (e.g., quality reviews, inspections, user acceptance tests, sign-offs).
- Owner/Author: Project Support / Project Manager.
Detailed Examination of Management Reports
1. Checkpoint Report
- Flow: Team Manager $\rightarrow$ Project Manager.
- Purpose: Reports the progress of a Work Package against agreed Work Package targets.
- Frequency: Set out in the Work Package (e.g., weekly or bi-weekly).
2. Highlight Report
- Flow: Project Manager $\rightarrow$ Project Board.
- Purpose: Provides a regular, concise summary of stage status, accomplishments, upcoming milestones, tolerance usage, and risk/issue summaries.
- Frequency: Set out in the Project Initiation Documentation (e.g., monthly or per sprint).
3. End Stage Report
- Flow: Project Manager $\rightarrow$ Project Board.
- Purpose: Summarizes stage performance against the Stage Plan, reviews overall project Business Case viability, updates risk/issue profiles, and presents lessons.
- Trigger: End of each management stage (during Managing a Stage Boundary).
4. End Project Report
- Flow: Project Manager $\rightarrow$ Project Board / Corporate Management.
- Purpose: Evaluates final project performance against initial baselines, confirms product handover and customer acceptance, and previews expected benefits realization.
- Trigger: Project closure (during Closing a Project).
5. Exception Report
- Flow: Project Manager $\rightarrow$ Project Board.
- Purpose: Formally notifies the Board that a stage or project tolerance is forecast to be breached, detailing options and recommendations.
- Trigger: Forecast breach of tolerance.
6. Lessons Report
- Flow: Project Manager $\rightarrow$ Project Board / Corporate Management.
- Purpose: Captures valuable lessons and statistics regarding project execution to refine corporate standards and future project delivery.
- Trigger: End Stage Reviews and Project Closure.
Master Comparison Table of PRINCE2 7 Management Products
| Product Name | Category | Primary Author | Main Recipient | Primary Purpose / Trigger |
|---|---|---|---|---|
| Daily Log | Record | Project Manager | Project Manager | Informal day-to-day items & minor risks |
| Lessons Log | Record | Project Manager | Project Team | Live repository of lessons learned |
| Risk Register | Record | Project Manager | Project Manager / Board | Formal tracking of threats & opportunities |
| Issue Register | Record | Project Manager | Project Manager / Board | Formal tracking of RFCs, Off-Specs & Problems |
| Quality Register | Record | Project Support | Project Manager | Schedule & results of quality activities |
| Checkpoint Report | Report | Team Manager | Project Manager | Work Package progress update |
| Highlight Report | Report | Project Manager | Project Board | Stage status summary for executive board |
| End Stage Report | Report | Project Manager | Project Board | Stage completion & Business Case review |
| End Project Report | Report | Project Manager | Board / Corporate | Final project performance & handover check |
| Exception Report | Report | Project Manager | Project Board | Alert board of forecast tolerance breach |
| Lessons Report | Report | Project Manager | Corporate / Board | Knowledge transfer for future projects |
Loading diagram...
Test Your Knowledge
Which progress report is submitted by Team Managers to the Project Manager to report on Work Package execution?
A
B
C
D
Test Your Knowledge
Where should a Project Manager initially record an informal day-to-day observation or minor team query?
A
B
C
D
Test Your Knowledge
What is the primary reporting product used by the Project Manager to provide regular, summary updates on stage progress to the Project Board?
A
B
C
D