Study guide
1.4 Management Products vs Specialist Products
PRINCE2 7 Foundation Certification Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Key Concepts, Framework & Integrated Elements
1.1 PRINCE2 7 Method Overview & Project Context 1.2 Seven Performance Aspects & Delivery Approaches 1.3 Outputs, Outcomes, Benefits & Value Creation 1.4 Management Products vs Specialist Products 1.5 PRINCE2 Governance, Tailoring & Distinct Features
2 Chapter 2: The Seven PRINCE2 7 Principles
2.1 Principle 1: Continued Business Justification 2.2 Principle 2: Learn from Experience 2.3 Principle 3: Define Roles, Responsibilities and Relationships 2.4 Principle 4: Manage by Stages 2.5 Principle 5: Manage by Exception 2.6 Principle 6: Focus on Products 2.7 Principle 7: Tailor to Suit the Project
3 Chapter 3: The People Element in PRINCE2 7
3.1 Capable People & Organizational Culture 3.2 Project Teams & Team Dynamics 3.3 Leading Project Teams 3.4 Communication & Stakeholder Engagement 3.5 Organizational Change Management (OCM)
4 Chapter 4: The PRINCE2 7 Practices - Strategy, Organization & Planning
4.1 Business Case Practice 4.2 Organizing Practice & Project Management Team 4.3 Commercial & Stakeholder Aspects of Organizing 4.4 Plans Practice & Levels of Plans 4.5 Product-Based Planning Technique 4.6 Quality Practice & Quality Control
5 Chapter 5: The PRINCE2 7 Practices - Risk, Change & Progress Control
5.1 Risk Practice & Risk Management Approach 5.2 Issues Practice & Issue Management Approach 5.3 Change Control & Configuration Management 5.4 Progress Practice & Control Mechanisms 5.5 Management Reports & Logs/Registers 5.6 Sustainability & Digital Integration in Practices
6 Chapter 6: The PRINCE2 7 Processes - Pre-Project & Initiation
6.1 Overview of PRINCE2 7 Process Model & Flow 6.2 Starting Up a Project (SU) Process 6.3 Directing a Project (DP) Process 6.4 Initiating a Project (IP) Process 6.5 Assembling the Project Initiation Documentation (PID)
7 Chapter 7: The PRINCE2 7 Processes - Delivery, Boundary & Closure
7.1 Controlling a Stage (CS) Process 7.2 Managing Product Delivery (MP) Process 7.3 Managing a Stage Boundary (SB) Process 7.4 Closing a Project (CP) Process 7.5 End-to-End PRINCE2 7 Process Flow & Exam Walkthrough
1.4 Management Products vs Specialist Products
Key Takeaways Explain This Topic AI
Specialist Products are the specific domain deliverables that make up the final product of the project.
Management Products are administrative, planning, and control deliverables used to manage the project.
Management Products are categorized into three types: Baselines, Records, and Reports.
Baseline Management Products define agreed targets and plans subject to formal change control (e.g. PID, Business Case, Plans).
PRINCE2 7 uses the Project log to hold dynamic records such as the Daily Log, Lessons Log, and registers (risk, issue, quality, product).
Last updated: July 2026
- 1.4 Management Products vs Specialist Products
- Product-Oriented Project Governance
PRINCE2 is fundamentally a product-focused methodology . It operates on the core premise that a project cannot be planned, estimated, or controlled effectively without first defining the explicit deliverables it must produce. In PRINCE2 terminology, everything created by the project is defined as a 'product', divided cleanly into two main classes:
Specialist Products: The domain-specific deliverables that constitute the physical or operational solution handed over to the user.
Management Products: The governance, planning, monitoring, risk management, and control artifacts used to direct, manage, and execute the project.
Specialist vs. Management Products
Attribute Specialist Products Management Products
Primary Purpose Form the operational end-product delivered to the customer or end-users. Enable governance, decision-making, planning, progress control, and risk management.
Domain Specificity Unique to the specific industry or domain (e.g., civil engineering, IT, pharmaceuticals). Standardized PRINCE2 governance artifacts adapted to project scale and context.
Authoring Responsibility Developed by technical specialists, domain experts, and external suppliers. Created and maintained by Project Manager, Project Board, and Project Assurance.
Examples Highway bridge, cloud application, medical device, training manual. Project Initiation Documentation (PID), Risk Register, Highlight Report, End Stage Report.
The Three Categories of Management Products
PRINCE2 7 classifies all Management Products into three distinct structural categories : +-----------------------+
- | MANAGEMENT PRODUCTS |
- +-----------+-----------+
- |
- +---------------------------+---------------------------+
- | | |
- +--------+--------+ +--------+--------+ +--------+--------+
- | BASELINES | | RECORDS | | REPORTS |
- | Approved targets| | Dynamic logs & | | Status snapshots|
- | & plans (PID) | | ongoing tracking| | & evaluations |
- +-----------------+ +-----------------+ +-----------------+
- Category 1: Baseline Management Products
Baseline products define approved management plans, requirements, targets, and governance approaches. Once formally approved by the designated authority (typically the Project Board), baselines are frozen and placed under formal change control . Any proposed modification requires a formal change request and impact evaluation.
Key Baseline Management Products include:
Project Initiation Documentation (PID): The single authoritative baseline source of truth for project governance, containing the project definition, management approaches, controls, and baseline plans.
Business Case: Defines the commercial justification, investment rationale, costs, benefits, dis-benefits, and risks.
Project Plan / Stage Plan / Team Plan: Approved operational schedules detailing activities, dependencies, resource allocations, and stage milestones.
Product Description: Defines the purpose, composition, quality criteria, and quality inspection methods for individual deliverables.
Management Approaches: Documented strategies in the PID defining how key aspects will be managed—commonly including Benefits, Change (organizational), Communication, Commercial, Digital & Data, Issues, Quality, Risk, and Sustainability management approaches.
Benefits Management Approach: Outlines how and when project benefits will be measured and realized during and after the project.
Category 2: Records
Records are dynamic management products created to log, track, and maintain operational data continuously throughout the project lifecycle. Unlike baselines, records are updated fluidly as operational events occur.
Key Record Management Products include:
Daily Log: Used by the Project Manager to record informal issues, operational notes, commitments, and minor risks not requiring formal escalation.
Lessons Log: Captures organizational lessons learned from previous projects or current project stages.
Risk Register: Maintains detailed records of identified risks, their probability, severity, proximity, and chosen response strategies.
Issue Register: Logs formal project issues, change requests, and non-conformances requiring investigation.
Quality Register: Summarizes all planned and completed quality management activities, inspections, and audit results.
Category 3: Reports
Reports are communication snapshots generated at specific intervals or triggered by specific events. They synthesize information on project performance to support decision-making.
Key Report Management Products include:
Checkpoint Report: Issued periodically by Team Managers to the Project Manager, summarizing Work Package execution progress.
Highlight Report: Issued periodically by the Project Manager to the Project Board, summarizing stage progress and forecasting future performance.
End Stage Report: Written by the Project Manager at the end of a management stage to evaluate performance against the Stage Plan.
Exception Report: Created when a stage or project tolerance breach is forecast, presenting options and recommendations to the Project Board.
End Project Report: Evaluates overall project performance against original PID baselines upon completion.
Lesson Report: Documents valuable lessons learned for application in future organizational projects.
Comparison Matrix: Baselines vs. Records vs. Reports
Category Core Governance Purpose Lifecycle State & Modification Rules Primary Exam Examples
Baseline Define agreed targets & management approaches Approved & frozen; subject to formal change control PID, Business Case, Stage Plan, Quality Approach
Record Dynamic tracking of events & ongoing items Continuously updated log without change control Daily Log, Risk Register, Issue Register, Quality Register
Report Snapshot communication for executive decision-making Periodic or event-driven static document Highlight Report, Checkpoint Report, Exception Report, End Stage Report
The Project Log (PRINCE2 7)
PRINCE2 7 groups dynamic records under the Project log . Foundation candidates should know that the project log contains (among other records):
- Daily Log — Project Manager's informal notes, reminders, and minor issues
- Lessons Log — lessons sought and recorded throughout the project
- Risk Register , Issue Register , Quality Register , and Product Register
Baseline products (Business Case, plans, management approaches, PID components) remain under formal change control; project-log records are updated continuously as events occur.
Tailoring Management Products in Modern & Digital Environments
Management products do not need to take the form of heavy Word documents or formal printed binder reports. In modern PRINCE2 7 projects, management products are tailored into agile, digital formats:
Baselines may exist as approved Confluence wiki charters or digital architecture decision records.
Records may be maintained as dynamic Jira, Azure DevOps, or Trello boards.
Reports may be delivered as real-time executive dashboard feeds or automated Slack/Teams progress notifications.