PRINCE2 Initiation Pack
For detailed management product definitions, read ../../references/prince2-management-products.md when the user needs a complete PRINCE2 document set or asks what each artifact is for.
Use this workflow when the project has passed startup and needs a controlled baseline before delivery begins.
Inputs To Ask For
- Approved project brief
- Outline business case
- Project product description
- Initiation stage plan
- Corporate, programme, portfolio, or customer standards
- Delivery approach and supplier model
- Known risks, issues, assumptions, dependencies, and constraints
- Governance and reporting expectations
Output Structure
1. Initiation Decision
- Recommendation: authorize project, revise documentation, or stop
- Conditions for approval
- Open decisions for the project board
2. Project Initiation Documentation
- Project definition
- Project approach
- Business case
- Project management team structure
- Role descriptions and responsibilities
- Project plan
- Tolerances and controls
- Tailoring decisions
3. Management Approaches
Create concise approaches for:
- Benefits
- Communication
- Quality
- Risk
- Issues and change control
- Data or information management
- Commercial or supplier management if relevant
- Sustainability if relevant
4. Plans And Product Definitions
- Project plan
- Stage plan for the next stage
- Product breakdown or product list
- Product descriptions
- Quality criteria
- Acceptance criteria
5. Control Setup
- Reporting cadence
- Highlight report rhythm
- Checkpoint expectations
- Escalation route
- Risk and issue review rhythm
- Change authority and change budget if used
Quality Bar
- Keep the pack tailored to the project size and risk.
- Every control should have an owner and cadence.
- The business case must be testable at stage boundaries.
- The project board should be able to authorize delivery from this pack.