Study guide
6.2 Starting Up a Project (SU) Process
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
6.2 Starting Up a Project (SU) Process
Key Takeaways Explain This Topic AI
Starting Up a Project (SU) is a pre-project process designed to prevent poorly conceived projects from entering full initiation.
SU is triggered by the Project Mandate, which is provided by Corporate, Programme Management, or Customer.
The primary outputs of SU are the Project Brief and the Initiation Stage Plan, which are submitted to the Project Board for approval.
SU is NOT a management stage; it is a short, low-cost pre-project activity that takes place before the first stage begins.
Last updated: July 2026
6.2 Starting Up a Project (SU) Process
The primary purpose of the Starting Up a Project (SU) process is to ensure that the prerequisites for initiating a project are in place. It acts as a lightweight, low-cost pre-project filter designed to answer one critical question:
Core Objective: Do we have a viable and worthwhile project?
Organizations frequently propose ideas for new initiatives. Initiating a project requires a significant investment of time, resources, and executive attention. By conducting the SU process before formally committing resources to detailed planning, PRINCE2 prevents unfeasible, unaligned, or poorly defined ideas from consuming organizational budgets.
The Trigger and Input: Project Mandate
Every PRINCE2 project is triggered by a Project Mandate . The mandate is an external document or command provided by Corporate, Programme Management, or the Customer .
Characteristics of a Project Mandate
External to the Project Team: It originates from outside the temporary project organization.
Flexible Format: It can range from an informal verbal instruction or email to a detailed 50-page feasibility study, strategic plan, or commercial tender document.
Content: It defines the high-level business reason for the project, target outcomes, and any known constraints or boundaries.
Incompleteness: A project mandate is rarely sufficient on its own to start detailed project work. The SU process takes this raw mandate and refines it into a clear, structured Project Brief .
The 6 Key Activities of the SU Process
The Starting Up a Project process consists of six sequential activities executed by the Project Manager, Executive, and key stakeholders during the pre-project phase: 1. Appoint Executive & Project Manager
- |
- v
- 2. Capture Previous Lessons (Lessons Log)
- |
- v
- 3. Design & Appoint Project Management Team
- |
- v
- 4. Prepare Outline Business Case
- |
- v
- 5. Select Project Approach & Assemble Project Brief
- |
- v
- 6. Plan the Initiation Stage (Initiation Stage Plan)
- 1. Appoint the Executive and the Project Manager
Corporate or Programme Management appoints the Executive , who represents business ownership and bears ultimate accountability for project success.
The Executive then appoints the Project Manager , who will run the day-to-day pre-project activities and subsequent stages.
2. Capture Previous Lessons
The Project Manager reviews lessons from previous similar projects (internal archives, external audits, industry benchmarks) and populates the Lessons Log .
Learning from experience ensures past mistakes are avoided and proven practices are embedded right from startup.
3. Design and Appoint the Project Management Team
The Executive and Project Manager define the project management structure, identifying candidates for key roles: Senior User(s) , Senior Supplier(s) , Project Assurance , and Project Support .
Role Descriptions are created to clarify responsibilities and authority lines.
4. Prepare the Outline Business Case
The Executive drafts the Outline Business Case (assisted by the Project Manager).
This document provides the preliminary business rationale, outlining why the project is needed, expected strategic benefits, preliminary cost estimates, and major business risks.
5. Select the Project Approach and Assemble the Project Brief
The Project Manager evaluates how the project deliverables will be provided (e.g., in-house development vs. commercial off-the-shelf purchase, predictive waterfall vs. iterative agile delivery, bespoke construction vs. leasing).
The Project Manager combines the Outline Business Case, Project Definition, Project Approach, Role Descriptions, and User's Quality Statement into the Project Brief .
6. Plan the Initiation Stage
The Project Manager creates the Initiation Stage Plan , detailing the resources, activities, timeline, and costs required to perform the Initiating a Project (IP) process during Stage 1.
Key Management Products Created in SU
Management Product Created By Primary Purpose & Content
Lessons Log Project Manager Records historical lessons to apply during startup and throughout the project lifecycle.
Outline Business Case Executive (assisted by PM) Preliminary business justification detailing high-level costs, benefits, and strategic alignment.
Project Management Team Structure Executive & PM Defines project roles, reporting hierarchy, and individual Role Descriptions.
Project Brief Project Manager Assembles project rationale, scope definition, approach, role descriptions, and quality expectations.
Initiation Stage Plan Project Manager Detailed schedule and resource allocation for executing the Initiation Stage (IP process).
Crucial Exam Concept: SU is NOT a Stage!
A major trap on the PRINCE2 7 Foundation exam is confusing Starting Up a Project (SU) with a management stage.
SU is a Process, NOT a Stage: SU is a short, pre-project activity that takes place before the project is formally authorized.
The First Stage is Initiation: The project officially begins when the Project Board approves the Project Brief and Initiation Stage Plan, authorizing the first formal stage: The Initiation Stage .
Cost Efficiency: Because SU occurs before formal authorization, it is kept intentionally brief and low-cost.