6.5 Assembling the Project Initiation Documentation (PID)

6.5 Assembling the Project Initiation Documentation (PID)

The Project Initiation Documentation (PID) is the single most important management product created during project setup. It brings together all the key information required to specify, plan, and govern the project.

Definition: The PID is the single authoritative source of reference for defining the project—serving as the formal contract between the Project Board and the Project Manager.

---

The 7 Core Components of the PID

The PID consolidates seven vital pieces of project information into a unified baseline:

+-----------------------------------------------------------------------+
|                   PROJECT INITIATION DOCUMENTATION (PID)              |
+-----------------------------------------------------------------------+
| 1. Project Definition (Background, Scope, Deliverables, Constraints)   |
| 2. Detailed Business Case (Financial Justification & ROI)             |
| 3. Project Management Team Structure & Role Descriptions               |
| 4. Project Plan (Master Schedule & Product Breakdown Structure)        |
| 5. Management Approaches (Risk, Quality, Change, Comm, Sust, Data)    |
| 6. Project Controls (Stage Boundaries, Reporting, Tolerances)         |
| 7. Tailoring Statement (Adaptations for Project Context & Environment)|
+-----------------------------------------------------------------------+

1. Project Definition: Details the project background, objectives, in-scope deliverables, out-of-scope boundaries, constraints, assumptions, and the User's Quality Statement.
2. Detailed Business Case: Provides the comprehensive business rationale, expected benefits, total estimated costs, financial ROI, and key business risks.
3. Project Management Team Structure: Defines the project organization hierarchy, reporting lines, and formal Role Descriptions for all team roles.
4. Project Plan: Outlines the overall project schedule, major milestones, product breakdown structures, resource allocations, and stage divisions.
5. Management Approaches: Integrates all six management approaches (Risk, Quality, Change Control, Communication, Sustainability, Data).
6. Project Controls: Specifies stage boundary mechanisms, tolerance levels across the 6 performance aspects, exception escalation rules, and reporting formats.
7. Tailoring Statement: Explains precisely how PRINCE2 7 has been tailored to suit the specific project scale, commercial context, delivery approach (predictive/agile/hybrid), and organizational culture.

---

Assembly, Approval, and Baselining Lifecycle

The PID undergoes a strict lifecycle from drafting to baselining:

1. Assembly (IP Process): The Project Manager gathers outputs from the IP activities and compiles the PID.
2. Approval (DP Process): Near the end of Stage 1, the Project Board reviews the assembled PID during the Authorize the Project activity.
3. Baselining: Once approved by the Board, the PID is baselined. This means its content cannot be altered without going through formal Change Control.
4. Benchmark for Performance: Throughout subsequent delivery stages, the PID serves as the baseline benchmark against which the Project Manager and Project Board measure progress, assess change requests, and evaluate project closure.

---

Tailoring the PID in PRINCE2 7

A common misconception is that the PID must be a massive 100-page document. PRINCE2 7 explicitly requires tailoring the PID format to fit project complexity and delivery mechanisms:

• Small / Simple Projects: The PID can be a concise 5-page document, a slide deck, or a simple online form.
• Agile / Digital Projects: In agile environments, the PID often exists as a dynamic Digital Collaboration Space (e.g., Jira dashboard, Confluence wiki, or enterprise portal), where product backlogs represent flexible scope baselines while stage boundaries enforce fixed timebox governance.
• Large / Commercial Projects: Requires formal legal contracts, structured documents, and strict configuration management logs.

---

Master Summary of Pre-Project & Initiation Products

---

Deep-Dive: The 6 Management Approaches in the PID

The PID integrates six distinct Management Approaches that define how specific ongoing practices will be conducted throughout the project lifecycle:

1. Change Control Approach: Defines how changes to baselined products will be identified, assessed, authorized, and controlled. Specifies the Change Authority role, change budget allocations, and configuration management procedures.
2. Commercial Approach: Details how third-party procurement, vendor management, contract administration, and customer-supplier commercial relationships will be governed.
3. Communication Management Approach: Outlines stakeholder communication requirements, reporting formats, frequency of distribution, and channels (interactive, push, pull).
4. Data Management Approach: Establishes digital data storage standards, single source of truth architecture, PMIS tooling, data security, access permissions, and audit logging.
5. Quality Management Approach: Specifies quality standards, quality control techniques, quality assurance responsibilities, and acceptance procedures for specialist products.
6. Sustainability Management Approach: Sets environmental and social sustainability targets, metrics, monitoring procedures, and green procurement requirements.

---

Common PID Exam Traps & Misconceptions

Candidates preparing for the PRINCE2 7 Foundation exam must be aware of several classic exam traps regarding the PID:

• Trap 1: Believing the PID is created in Starting Up a Project (SU). False! The Project Brief is created in SU. The PID is assembled in Initiating a Project (IP).
• Trap 2: Assuming the PID cannot be changed once approved. False! The PID is baselined upon approval, but it CAN be modified during the project through formal Change Control procedures or when updating the Stage Plan during Managing a Stage Boundary (SB).
• Trap 3: Confusing the Project Brief with the PID. The Project Brief is a temporary, lightweight document used by the Project Board to decide whether to authorize initiation (IP). The PID is the comprehensive, baselined master plan created during IP for overall project execution.
• Trap 4: Expecting the PID to be a physical bound document. In modern PRINCE2 7 projects, the PID is often hosted dynamically in digital tools (e.g., Confluence, SharePoint, Jira), functioning as a living digital baseline rather than a printed paper binder.