Study guide
4.4 Common Traps in 7 PRINCE2 Processes
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
4.4 Common Traps in 7 PRINCE2 Processes
Key Takeaways Explain This Topic AI
The Project Board never authors Work Packages or Stage Plans — it only authorizes in Directing a Project.
The detailed Business Case is created in IP and refined throughout; the outline Business Case comes from SU.
Checkpoint Reports flow Team Manager → Project Manager (MP); Highlight Reports flow Project Manager → Board (CS).
Managing a Stage Boundary runs at the end of every stage except the last, plus whenever an Exception Plan is needed.
Initiation is itself a management stage; the PID is created in IP, not in SU.
Last updated: June 2026
4.4 The Traps Item Writers Use
Trap one: putting the board in the wrong seat. Distractors often have the Project Board creating a Stage Plan, authorizing a Work Package , or writing the PID . The board does none of these. The board acts only in Directing a Project , and its verbs are authorize, approve, direct, and decide . Work Packages are authorized by the Project Manager in CS; the PID is assembled by the Project Manager in IP; Stage Plans are produced by the Project Manager in SB (or the initiation stage plan in SU).
Trap two: confusing the two business cases. The outline Business Case is drafted in SU to support the decision to initiate. The detailed Business Case is developed in IP , then reviewed and updated at every stage boundary (SB) and confirmed at closure (CP). A question that asks where the detailed Business Case is first produced is testing IP, not SU.
Trap three: report direction and naming. Two reports are routinely swapped:
- Report From → To Process
- Checkpoint Report Team Manager → Project Manager MP
- Highlight Report Project Manager → Project Board CS
- Exception Report Project Manager → Project Board CS
- End Stage Report Project Manager → Project Board SB
- End Project Report Project Manager → Project Board CP
If a stem says a Team Manager sends a Highlight Report , it is wrong — Team Managers send Checkpoint Reports .
More High-Frequency Traps
Trap four: where Managing a Stage Boundary runs. SB runs at the end of every management stage except the last . The last stage has no 'next stage' to plan, so closure is handled by Closing a Project instead. SB is also invoked outside the normal end-of-stage rhythm when the board requests an Exception Plan after an exception. A distractor claiming SB runs at the end of every stage including the final one is wrong.
Trap five: forgetting initiation is a stage. Initiation is the project's first management stage , controlled by the initiation stage plan produced in SU. The PID is created in IP , not SU — SU produces only the lighter Project Brief . Watch for stems that try to attribute the PID to Starting up a Project.
Trap six: skipping the authorization gate. PRINCE2 is gated. The Project Manager cannot move from IP straight into delivery; the board must authorize the project in DP first. Likewise, no delivery stage starts until the board has authorized the stage . An answer that has work beginning without board authorization violates the process model.
- Quick disambiguation list
- Worthwhile? → SU (outline Business Case)
- Foundations / PID → IP
- Authorize anything → DP (Project Board)
- Run the stage day to day → CS (Project Manager)
- Build the products → MP (Team Manager)
- End a stage, plan the next → SB
- Confirm acceptance, close down → CP
Edition-Specific and Vocabulary Traps
Trap seven: outdated PRINCE2 6 vocabulary. The 2023 (7th edition) exam updated several terms. Item writers may use a stale term as a distractor or expect the current one. The seven themes are now practices , and the separate strategy documents (Risk Management Strategy, Quality Management Strategy, and so on) are now management approaches (Risk Management Approach, etc.), created in IP. The process names and activity logic, however, did not change between editions — so do not assume a renamed process; there isn't one.
Trap eight: confusing 'approve' with 'accept'. Within a Work Package, the Project Manager approves completed products against quality criteria; the customer or user ultimately accepts the project's product (recorded at closure in CP). A distractor may swap these. Approval is a within-stage quality act; acceptance is a closure-level confirmation that the product is fit to own.
Trap nine: assuming every process produces a plan. Only certain processes create plans: SU creates the initiation stage plan , IP creates the Project Plan , and SB creates the next Stage Plan (or an Exception Plan). CS, MP, DP, and CP do not create stage-level plans. A stem implying that Controlling a Stage produces the next Stage Plan is wrong — that is SB's job.
- Confusable pair Correct distinction
- Theme vs Practice 'Practice' is the PRINCE2 7 term; 'theme' is legacy
- Strategy vs Approach PRINCE2 7 uses 'management approach', created in IP
- Approve vs Accept PM approves products; user/customer accepts the project product
- Project Brief vs PID Brief is from SU (light); PID is from IP (full baseline)
Clearing these vocabulary traps is often the difference between two otherwise identical-looking answer choices.
Trap ten: thinking SU is part of the project. Starting up a Project is a pre-project activity — it happens before the project is authorized, so the resources spent on it are deliberately minimal. The project formally begins only when the board authorizes initiation. A distractor that treats SU as the first delivery stage, or that asks the board to authorize Work Packages during SU, contradicts this. Likewise, post-project benefit reviews described in the Benefits Management Approach happen after CP — they are not a separate process.