Study guide
5.4 Common Traps in Project Organization
PRINCE2 Foundation Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: PRINCE2 Foundation Orientation and Exam Strategy
1.1 Current PRINCE2 Foundation Exam Facts 1.2 Eligibility, Application, and Scheduling 1.3 Blueprint Domains and Weighting 1.4 Question Style and Score Report Thinking 1.5 Study Calendar and Practice Plan
2 Chapter 2: 7 PRINCE2 Principles
2.1 7 PRINCE2 Principles Overview 2.2 Core Workflows and Decision Points 2.3 Scenario Practice for 7 PRINCE2 Principles 2.4 Common Traps in 7 PRINCE2 Principles 2.5 Practice Drills and Readiness Markers
3 Chapter 3: The 7 PRINCE2 Practices
3.1 7 PRINCE2 Practices Overview 3.2 Core Workflows and Decision Points 3.3 Scenario Practice for 7 PRINCE2 Practices 3.4 Common Traps in 7 PRINCE2 Practices 3.5 Practice Drills and Readiness Markers
4 Chapter 4: 7 PRINCE2 Processes
4.1 7 PRINCE2 Processes Overview 4.2 Core Workflows and Decision Points 4.3 Scenario Practice for 7 PRINCE2 Processes 4.4 Common Traps in 7 PRINCE2 Processes 4.5 Practice Drills and Readiness Markers
5 Chapter 5: Project Organization
5.1 Project Organization Overview 5.2 Core Workflows and Decision Points 5.3 Scenario Practice for Project Organization 5.4 Common Traps in Project Organization 5.5 Practice Drills and Readiness Markers
6 Chapter 6: Management Products
6.1 Management Products Overview 6.2 Core Workflows and Decision Points 6.3 Scenario Practice for Management Products 6.4 Common Traps in Management Products 6.5 Practice Drills and Readiness Markers
7 Chapter 7: Final Review and Test Day
7.1 Timed Practice Strategy 7.2 Last-Week Review Map 7.3 Exam-Day Checklist 7.4 After the Exam and Next Steps
5.4 Common Traps in Project Organization
Key Takeaways Explain This Topic AI
There is exactly one Executive — beware distractors that suggest a project may have several Executives or a separate Sponsor outside the Board.
PRINCE2 defines roles, not jobs; combining roles is allowed except Executive+Project Manager, and Project Assurance must never be combined with the Project Manager, Team Manager or Project Support.
The Senior User owns benefits and the Senior Supplier owns technical quality — do not swap these or hand benefits to the Executive.
Project Assurance and Change Authority are distinct: assurance gives an independent view, while the Change Authority makes change decisions within a delegated limit.
The Project Manager and Team Manager are both optional-to-combine in small projects, but the Project Board is mandatory on every PRINCE2 project.
Last updated: June 2026
The Single-Executive Trap
The most frequently tested misconception is that a project might have more than one Executive , or that an external "Sponsor" overrides the Board. PRINCE2 is unambiguous: there is one Executive , appointed first, ultimately accountable, owning the Business Case, with the deciding voice on the Board. Corporate, programme management or the customer sits above the project and mandates it, but it is not a Board member and does not run the project. When a question offers "two co-Executives share accountability" or "the Sponsor outranks the Executive on the Board," both are wrong.
A related trap is forgetting that the Project Board is mandatory . Even a tiny project must have the three Board roles defined, although in a small project one person could legitimately hold the Executive and Senior User roles together, or the Executive could also be the Senior Supplier in some customer/supplier setups — but never Executive and Project Manager. Another variant claims a project 'has no Executive yet' partway through delivery; PRINCE2 appoints the Executive in Starting up a Project , before initiation, so a project running without an Executive is not a valid PRINCE2 project.
Watch too for the claim that the Project Manager 'sits on the Board' — the Project Manager attends and reports to the Board but is not a Board member, because direction and management are kept on separate levels.
- Swapping and Combining Roles
- Accountability swaps
Exam writers love to swap the ownership of benefits and technical quality .
- Item Correct owner Wrong answer to reject
- Specifying and realising benefits Senior User Executive or Senior Supplier
- Technical integrity / quality of products Senior Supplier Senior User
- Business Case and value for money Executive Senior User
- Day-to-day management Project Manager Project Board
If a stem says the Senior Supplier is accountable for benefits, or the Senior User for technical quality, it is testing this swap. A reliable memory hook: the Senior User cares about using the product, so they own benefits and requirements ; the Senior Supplier supplies and builds , so they own quality and technical integrity ; the Executive holds the purse and the Business Case . Anchor each role to a single verb — use, build, justify — and the swaps stop fooling you.
Illegal combinations
PRINCE2 defines roles, not jobs, so combining is normally allowed. The hard limits are:
Executive and Project Manager must never be the same person.
Project Assurance must never be combined with the Project Manager, Team Manager, team members or Project Support.
Senior User and Senior Supplier should not be combined (conflict of interest), though this is guidance rather than an absolute prohibition.
Project Support, by contrast, can be combined with the Project Manager role in a small project.
Assurance vs. Change Authority vs. Support
These three supporting roles are easy to confuse because all three "help" the Board or Project Manager. Keep them separate:
Project Assurance = an independent view that the project is being run correctly, across business/user/supplier perspectives. It checks; it does not decide changes.
Change Authority = decides on requests for change and off-specifications within a delegated cost/severity limit. It is about decision rights, not oversight.
Project Support = administrative help — registers, logs, configuration management, planning tools. It does not assure and does not decide changes.
A classic distractor blends these: "Project Assurance approves the change request." Wrong — assurance advises, the Change Authority (or Board) approves. Another: "Project Support provides an independent check of quality." Wrong — support and assurance must stay separate precisely so support cannot mark its own homework. Finally, never let the Project Manager authorise a stage or perform assurance on their own work ; both are deliberate separations baked into the framework.
Wording Traps in the Stem
Foundation questions are often decided by a single qualifying word. Train yourself to spot these.
"must" vs "may" — The Project Board must exist; Project Assurance and Project Support may exist as separate roles. An answer that makes an optional role mandatory, or a mandatory role optional, is wrong.
"owns" vs "performs" — Project Assurance is owned by the Board even if assurance staff perform it. The Communication Management Approach is owned by the Project Manager. Watch for answers that move ownership to the wrong level.
"accountable" vs "responsible" — The Executive is accountable for the Business Case; others may be responsible for contributing to it. Accountability is singular and cannot be shared.
"day-to-day" — This phrase almost always points to the Project Manager, never the Board.
The 'Sponsor', 'Steering Committee' and Programme Traps
PRINCE2 uses specific terms, and exam writers slip in look-alikes from other methods. A steering committee is not a PRINCE2 term — the equivalent is the Project Board . A sponsor is not a defined PRINCE2 role — the nearest equivalent is the Executive . Corporate, programme management or the customer is a level , not a Board member, so any answer that seats it on the Project Board or lets it run the project day to day is wrong. Likewise, the Project Manager does not sit on the Project Board ; the Project Manager reports to the Board.
When an option imports unfamiliar governance vocabulary, suspect a trap and map it back to PRINCE2's own terms before answering.