Project Initiation

1. Strategy and Business Justification

This section explains why the project exists.

It contains evidence that:

  • A real business need or opportunity exists

  • The project aligns with organisational strategy

  • The expected benefits justify the investment

This section answers the executive question:

  • “Why should the organisation commit to this project?”

2. Financial Authorisation

This section confirms how the project is funded.

It captures:

  • High-level cost estimates

  • Funding requests and approvals

  • Budget constraints and assumptions

This section exists to demonstrate that:

  • Funding has been considered and approved

  • Financial authority has been formally granted

It answers:

  • “Who is paying for this, and have they approved it?”

3. Governance and Authority

This section defines who has decision-making power.

It documents:

  • Governance structures

  • Sponsor and project manager appointments

  • Escalation and approval authority

This section ensures the project has:

  • Clear ownership

  • Legitimate authority to operate

It answers:

  • “Who is accountable, and who can make decisions?”

4. Compliance and Regulatory

This section addresses external and internal obligations.

It contains:

  • Regulatory requirements

  • Compliance assessments

  • Standards and policy alignment

This section demonstrates that:

  • Regulatory impacts were identified early

  • Compliance risks are understood

It answers:

  • “What rules must this project comply with?”

5. Legal and Contractual

This section captures legal constraints and protections.

It includes:

  • Legal reviews

  • Confidentiality agreements

  • Intellectual property considerations

This section exists to ensure:

  • Legal exposure is understood

  • Obligations are documented before work begins

It answers:

  • “What legal risks or obligations exist?”

6. Risk and Assurance

This section identifies what could go wrong.

It contains:

  • Initial risk registers

  • Compliance and enterprise risk assessments

  • Assurance and audit inputs

This section ensures:

  • Major uncertainties are visible early

  • Leadership understands exposure before approval

It answers:

  • “What are the key risks if we proceed?”

7. Stakeholder and Impact Assessment

This section focuses on the impact on people and organisations.

It documents:

  • Key stakeholders

  • Influence and interest analysis

  • Organisational and change impacts

This section ensures:

  • Affected parties are identified

  • Change impact is considered upfront

It answers:

  • “Who will be affected, and how?”

8. Project Definition

This section defines what is being approved.

It captures:

  • High-level scope

  • Objectives and outcomes

  • Success criteria and constraints

This section draws the boundary of the project and answers:

  • “What exactly are we authorising?”

9. Development Approach and Tailoring

This section explains how the project will be delivered.

It documents:

  • Chosen lifecycle approach

  • Methodology tailoring

  • Governance alignment

This section ensures the approach is:

  • Appropriate for risk and complexity

  • Aligned with organisational standards

It answers:

  • “How will this project be managed?”

10. Project Charter

This section is the formal authorisation point.

It contains:

  • The approved project charter

  • Supporting review evidence

The charter consolidates decisions from all prior folders and:

  • Officially authorises the project

  • Grants authority to the project manager

It answers:

  • “Is this project officially approved to start?”

11. Stage-Gate and Approvals

This section records formal decisions.

It includes:

  • Gate review materials

  • Approval records

  • Authorization to proceed

This section exists to prove:

  • Governance processes were followed

  • The project passed the required gates

It answers:

  • “What decisions were made, and when?”

12. Communications and Records

This section preserves decision context.

It stores:

  • Executive briefings

  • Formal communications

  • Meeting notes and decision logs

This section supports transparency and answers:

  • “How were decisions communicated and documented?”

13. Audit and Record Retention

This section provides traceability and evidence.

It includes:

  • Evidence indexes

  • Document control registers

  • Approval traceability

This section exists primarily for:

  • Auditors

  • Regulators

  • Internal assurance

It answers:

  • “Can we prove this project was initiated correctly?”