Study guide
11.2 Starting Up a Project
PRINCE2 Practitioner Version 7
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Exam Strategy & Open-Book Technique
2 PRINCE2 7 Method Overview
2.1 The PRINCE2 7 Method 2.2 What Changed in PRINCE2 7 2.3 Performance Targets, Tolerances & Project Context
3 PRINCE2 Principles (1–4)
3.1 Continued Business Justification 3.2 Learn from Experience 3.3 Defined Roles, Responsibilities & Relationships 3.4 Manage by Stages
4 PRINCE2 Principles (5–7) & Applying Principles
4.1 Manage by Exception 4.2 Focus on Products 4.3 Tailor to Suit the Project 4.4 Applying Principles in Context
5 People Management in Projects
5.1 Organisational & Project Ecosystems 5.2 Leadership in Projects 5.3 Team Culture & Diversity 5.4 Communication, Stakeholder Engagement & Change Management
6 Practices Overview & Business Case
6.1 The Seven Practices & Tailoring 6.2 Business Case: Desirability, Viability & Achievability 6.3 Business Case Lifecycle & Management Products 6.4 Business Case Application & Tailoring Scenarios
7 Practices: Organising & Plans
7.1 Organising: Roles & Accountability 7.2 Organising: 5-Step Ecosystem Technique 7.3 Plans: Three Levels & Product-Based Planning 7.4 Plans: Techniques, Tolerances & Tailoring
8 Practices: Quality & Risk
8.1 Quality: Planning, Control & Assurance 8.2 Quality Techniques & Management Products 8.3 Risk: Threats & Opportunities 8.4 Risk 5-Step Technique & Application
9 Practices: Issues
9.1 Issues Practice: Issue vs Change & Categories 9.2 Issues 5-Step Technique & Supporting Techniques 9.3 Change Control, Configuration & Priority/Effort Assessment
10 Practices: Progress, Sustainability & Application
10.1 Progress: Controls, Tolerances & Reports 10.2 Sustainability as the 7th Performance Target 10.3 Tailoring the Practices 10.4 Practices Application Scenarios (BL4)
11 Processes: Model, Starting, Directing & Initiating
11.1 The Seven Processes & Process Model 11.2 Starting Up a Project 11.3 Directing a Project 11.4 Initiating a Project
12 Processes: Controlling a Stage & Product Delivery
12.1 Controlling a Stage 12.2 Managing Product Delivery 12.3 Stage Control & Exception Scenarios (BL4) 12.4 Work Packages & Reporting Cycle
13 Processes: Stage Boundary, Closing & Tailoring
13.1 Managing a Stage Boundary 13.2 Closing a Project 13.3 Tailoring the Processes 13.4 Process Application Scenarios (BL4)
14 Tailoring, Management Products & Exam Technique
14.1 Tailoring to Project Environment, Scale & Agile 14.2 Management Products & the v7 Project Log 14.3 Final Exam Technique, Full Scenarios & Common Traps
11.2 Starting Up a Project
Key Takeaways Explain This Topic AI
Starting Up a Project is a pre-project process triggered by the Project Mandate; it does NOT authorise the project — the Project Board does that when authorising Initiating.
Its purpose is to check that the project is worthwhile before committing to initiation, and to appoint the Project Board and Project Manager so that somebody is accountable from day one.
The primary output is the Project Brief: outline Business Case, Project Product Description, project approach, project management team structure, and the initiation Stage Plan, plus a request to initiate.
Activities include appointing the Executive and PM, capturing previous lessons, designing and appointing the project management team, and preparing the outline Business Case and Project Product Description.
Last updated: August 2026
Trigger and purpose
Starting Up a Project (SU) is triggered by the Project Mandate , an input that usually arrives from corporate management or a programme. The mandate is often thin — a sentence in a strategy document, a customer request, a regulatory deadline — and one of SU's jobs is to flesh it out into something the board can act on.
The process has two core purposes. First, check that the project is worthwhile before the organisation spends the much larger effort of Initiating a Project. PRINCE2 treats initiation as an investment, and SU is the screening step that stops bad ideas early. Second, appoint the Project Board and Project Manager so that accountability exists before any delivery decisions are made. A project with no designated Executive is a project with nobody to authorise it.
A critical exam point: Starting Up does NOT authorise the project. It produces a request to initiate . The actual authorisation — the decision to spend money on initiation and to commit to the project — is made by the Project Board in the Directing a Project process, in the activity authorise initiation . Many scenario questions hinge on this distinction.
Activities and outputs
Activity What it produces Who performs it
Appoint the Executive and PM Role descriptions, named individuals Corporate/programme management, then the Executive
- Capture previous lessons Lessons from prior projects (input to Risk and Quality approaches) PM (designate)
- Design and appoint the project management team Team structure and role descriptions Executive + PM
- Prepare the outline Business Case Outline rationale, costs, benefits, risks Executive (with PM)
- Prepare the Project Product Description What the project must deliver, quality criteria PM (with Executive)
- Select the project approach Delivery strategy (e.g. agile, waterfall, hybrid) PM
- Assemble the Project Brief The consolidated pre-project document PM
- Plan the initiation stage Initiation Stage Plan PM
- Request project initiation Formal request asking the board to authorise the initiation stage PM
The Project Brief is the headline output. It is a composite management product containing:
Outline Business Case — enough to judge whether the project is worth pursuing.
Project Product Description — the project's output, its quality criteria, and acceptance method.
Project approach — how the work will be delivered (the way , not the plan ).
Project management team structure — who fills which role.
Initiation Stage Plan — the plan for the initiation stage itself, because initiation is itself a stage that must be authorised and controlled.
The request to initiate is then handed to the Project Board, which decides whether to authorise Initiating a Project.
Common exam scenarios
"A new project has been suggested by a programme. What triggers Starting Up a Project?" — the Project Mandate .
"Which document assembles the outline Business Case, Project Product Description, and project approach?" — the Project Brief .
"Who is appointed during Starting Up?" — the Executive first, then the Project Manager , then the rest of the project management team.
"Is the project authorised in Starting Up?" — No. SU produces a request to initiate; the board authorises initiation in Directing a Project.
"Does Starting Up create a full Project Plan?" — No. It creates an Initiation Stage Plan only; the full Project Plan is built in Initiating a Project.
Tailoring notes
SU is intentionally lightweight. For a very small project, the Project Brief may be a one-page document; for a major programme-aligned project, it may be a substantial folder. The v7 guidance is explicit that SU should be proportionate — enough to make the go/no-go decision, not enough to pre-empt initiation. If the PM finds themselves building a detailed Project Plan during SU, they have over-run the process boundary.
Worked example: from thin mandate to decision-ready Brief
A programme issues a mandate: "Deliver an online assessment platform for the new professional certification." The PM designate, appointed by the Executive, first captures lessons from a prior e-learning project that overran because vendor selection was rushed; those lessons will later feed the Risk and Quality approaches built in Initiating. The Executive drafts an outline Business Case showing €450k cost against €1.2m of avoided manual-marking spend over three years, and the PM drafts the Project Product Description naming the platform, its pass/fail analytics, and 99.5% uptime as quality criteria. The PM selects a hybrid delivery approach — agile sprints for the candidate-facing portal, waterfall for the item-bank migration — and assembles the Project Brief by consolidating these pieces plus the team structure and the Initiation Stage Plan (a four-week, €40k initiation). The board reads the Brief, judges the outline case credible, and authorises initiation — not the project. Only after Initiating produces the PID will the board decide whether to commit to delivery. This sequencing is what stops a weak outline case from consuming a full initiation budget.
Common misconceptions
Misconception Correction
SU authorises the project No — it produces a request to initiate ; the board authorises initiation in Directing a Project
SU builds the full Project Plan No — it builds only the Initiation Stage Plan ; the Project Plan is an Initiating output
SU creates the management approaches (Risk, Quality, Communication) No — those are created in Initiating; SU only captures lessons that feed them
The Project Brief and the PID are the same document No — the Brief is a pre-project input; the PID is the authorised baseline built in Initiating
SU must be long and formal No — it should be proportionate; for a small project the Brief may be a one-page document
The Project Mandate and the Project Brief are interchangeable No — the mandate is the raw trigger from corporate/programme; the Brief is the structured output of SU
Authorisation boundary — a closer look
The single most tested point in SU questions is the authorisation boundary. Starting Up produces a request to initiate , which is a recommendation, not a decision. The Project Board, in the authorise initiation activity of Directing a Project, is the body that decides whether the outline Business Case justifies the cost of a full initiation. If the board declines, the project stops before initiation is funded. If the board accepts, Initiating a Project begins. Remember the sequence: mandate → SU → request to initiate → board decision (authorise initiation) → Initiating → PID → board decision (authorise project and first stage). Two board decisions, two different questions, two different processes producing the input for each.