Study guide
7.1 Organising: Roles & Accountability
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
7.1 Organising: Roles & Accountability
Key Takeaways Explain This Topic AI
The Organising practice defines the project's accountability structure — the 'who' — and separates three primary interests: business (Executive), user (Senior User), and supplier (Senior Supplier).
The Project Board is chaired by the Executive and contains Senior User(s) and Senior Supplier(s); the Project Manager is NOT a board member and cannot be the Executive or hold a Project Assurance role.
Roles are not job titles — one person can hold multiple roles provided there is no conflict of interest, and a single role can be shared across several people.
Project Assurance acts as the board's 'eyes and ears' providing independent assurance, while Project Support provides tools, administrative services, and configuration management to the PM and teams.
Last updated: August 2026
The Organising practice answers the who question of a PRINCE2 project. Before any product is built, the project needs a defined accountability structure that ties every decision and deliverable to a named role. PRINCE2 v7 frames accountability around three primary interests that must be represented on every project: the business interest (those who pay and benefit), the user interest (those who will use the outputs), and the supplier interest (those who create the outputs). Each interest maps to a specific board role.
The Project Board
The Project Board is the project's top-level decision-making body, accountable to corporate or programme management for the project's success. It is chaired by the Executive , who represents the business interest and has overall accountability. The Executive is a single individual — never a committee — because accountability must rest with one person. The board also contains one or more Senior Users (representing the user community) and one or more Senior Suppliers (representing the teams building the products). The Project Board approves the project, authorises each stage, commits resources, and provides ongoing direction and decisions.
A common exam trap is treating the Project Manager (PM) as a board member. The PM is not on the board. The PM manages the project day-to-day within the tolerances set by the board and escalates issues when tolerances are forecast to be breached. Because the PM reports to the board, the PM cannot also be the Executive, a Senior User, or a Senior Supplier — that would create a conflict in which the PM approves their own work. Equally, the PM cannot hold a Project Assurance role, because assurance must be independent of the management it checks.
Role Definitions
Role Primary Interest Core Responsibility
Executive Business Overall accountability; chairs the Project Board; secures funding; represents the business case
Senior User(s) User Specifies user needs; ensures the product delivers the benefits; prioritises user requirements
Senior Supplier(s) Supplier Provides the resources and skills to build the products; ensures technical quality and feasibility
Project Manager — (management) Day-to-day management within tolerances; plans, delegates, monitors, controls, reports
Team Manager Supplier side Produces the products assigned in a Work Package; manages a team's delivery
Project Assurance All three Independent assurance to the board that the project is on track; the board's 'eyes and ears'
Project Support — (support) Provides tools, administration, configuration management, and specialist help to the PM and teams
Roles Are Not Job Titles
A PRINCE2 role is not a job title . Roles are defined by the responsibilities they carry, not by the position on an organisational chart. This means one person can hold multiple roles , and one role can be shared across several people , provided no conflict of interest is created. On a small project a single person might be Senior User and Team Manager; on a large programme the Senior Supplier role may be split across an internal IT lead and an external vendor lead. The conflict test is the exam's favourite discriminator: a person cannot hold two roles where one is accountable for checking the other. Hence the PM cannot be Project Assurance, and the Executive cannot also be the PM.
Project Assurance and Project Support
Project Assurance is delegated by the Project Board and provides independent monitoring across three perspectives — business (is the business case still viable?), user (will the product meet user needs?), and supplier (can the products be delivered to quality?). Assurance is independent of the Project Manager and reports concerns directly to the board. The board can assign assurance to people inside or outside the project, but never to the PM or a Team Manager working under the PM.
Project Support is the lighter-weight counterpart: it is not independent assurance. Project Support provides the tools, templates, configuration management, issue logging, and administrative help the PM needs to run the project. On a small project, support may be a part-time corporate PMO function; on a large project it may be a dedicated team. Crucially, Project Support helps the PM; it does not monitor the PM on behalf of the board.
Exam Scenario Patterns
In the practitioner exam, Organising scenarios usually take one of three forms. The first asks you to assign the right role to an action — for example, 'who is accountable for securing funding?' (Executive) or 'who specifies user needs?' (Senior User). The second asks you to spot a role conflict — for example, a PM who also chairs the board, or a Team Manager who also performs Project Assurance for the same work. The third asks who chairs the Project Board — the answer is always the Executive. Watch for distractors that describe a 'co-chair' or a rotating chair; PRINCE2 is explicit that the Executive chairs the board alone.
Tailoring Note
On very small projects the board may be a single person holding the Executive and Senior User roles, with the supplier interest provided by an external vendor. Even then, the PM must remain separate, and assurance must be independent. The practice is tailorable, but the conflict rule is not.