Study guide
5.5 Practice Drills and Readiness Markers
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.5 Practice Drills and Readiness Markers
Key Takeaways Explain This Topic AI
Readiness means you can state each of the four levels, name the three mandatory Board roles, and recall the Executive/Project Manager single-person rule without hesitation.
Drill the three Project Assurance perspectives and the rule that assurance is independent of the Project Manager, Team Manager and Project Support.
Be able to route every management report: highlight (PM to Board), checkpoint (TM to PM), exception (PM to Board on tolerance breach).
Practise the communication management approach: owned by the Project Manager, it defines who gets what information, when, and how.
A domain is ready when mixed-role scenario questions stay stable after a one-day break.
Last updated: June 2026
Rapid-Recall Drills
Run these as flash prompts; you should answer each in one breath.
- Name the four levels of organization. (Corporate/programme/customer; directing; managing; delivering.)
- Name the three mandatory Project Board roles . (Executive, Senior User, Senior Supplier.)
- Which two roles must be a single named person and never combined? (Executive and Project Manager.)
- Who owns the Business Case ? (The Executive.)
- Who owns benefits ? Technical integrity? (Senior User; Senior Supplier.)
- Name the three Project Assurance perspectives . (Business, user, supplier.)
- Who may never perform Project Assurance? (Project Manager, Team Manager, team members, Project Support.)
- What does a Change Authority do? (Decides changes/off-specs within a delegated limit.)
- Is Project Support mandatory? (No — optional; the PM performs it if not appointed.)
- Who owns the communication management approach ? (The Project Manager.)
- Where in the processes is the Executive first appointed ? (Starting up a Project.)
- Who does the Team Manager report to , and via what? (The Project Manager, via checkpoint reports.)
- What is the equivalent PRINCE2 term for a 'steering committee'? (The Project Board.)
- Can the Senior User and Senior Supplier be the same person? (Not advised — their interests conflict.)
- What did the 7th edition add to Organizing? (A people dimension: leadership, culture, change, wellbeing.)
Reporting and Communication Drill
The Organizing practice connects to progress reporting, so drill the flows until automatic.
- Report From To Trigger
- Highlight report Project Manager Project Board Time-driven, within a stage
- Checkpoint report Team Manager Project Manager Time-driven, within a Work Package
- Exception report Project Manager Project Board Stage/project tolerance forecast to be breached
- End stage report Project Manager Project Board At each stage boundary
- Communication Management Approach
The communication management approach is the management product that records how the project will engage stakeholders: what information is shared, to whom , how often , and through which channel . It is created by the Project Manager during initiation and reviewed at stage boundaries. Stakeholder engagement is continuous, not a one-off — the 7th edition's people emphasis stresses understanding stakeholders' interests and influence and adapting communication to them. If a question asks where stakeholder communication is planned, the answer is the communication management approach.
Readiness Checklist
Mark each as solid, shaky, or unknown, and re-drill anything not solid.
I can draw the four-level structure and place each role in it.
I can state the single-Executive and Executive-not-Project-Manager rules.
I can assign Business Case, benefits and technical integrity to the correct Board role.
I can list the three assurance perspectives and the independence rule.
I can distinguish Project Assurance, Change Authority and Project Support.
I can route highlight, checkpoint and exception reports correctly.
I can name the owner and purpose of the communication management approach.
I can explain what the 7th edition added: the people, leadership and culture focus.
Readiness Markers
You are ready when: mixed scenario questions that hide the role behind a described action are answered correctly and consistently; you no longer confuse assurance with the change authority; and your accuracy holds after a one-day gap rather than depending on having just reviewed. Trace every miss to a specific cue you overlooked — interest, level, or delegation limit — rather than treating it as random.
Spaced Drilling Plan
Don't cram the organisation chart once and move on. Use short, spaced repetitions because role-and-level facts decay quickly under exam pressure.
- Session Focus Target
- Day 1 Four levels + three Board roles + single-person rule 100% recall in under 30 seconds
- Day 2 Assurance perspectives + independence rule + Change Authority Distinguish all three supporting roles
- Day 3 Reporting flows + communication management approach owner Route every report correctly
- Day 5 Mixed scenario set (action-to-role) 85%+ with no notes
- Day 8 Full mixed retest after a 3-day gap Stable score, no role swaps
- Linking Organizing to the Rest of the Method
The organisation does not live in isolation, and the exam may test it through other topics. Tie these threads together:
Business Case practice: the Executive owns it; the Senior User supplies expected benefits; the benefits management approach records how benefits will be measured.
Plans and Progress: tolerances delegated through the four levels are what make management by exception work; highlight, checkpoint and exception reports are the heartbeat between levels.
Issues and Change: the Change Authority's delegated limit is set in the change control approach, agreed during initiation.
Quality: the Senior Supplier's accountability for technical integrity connects to the quality management approach and product descriptions.
When you can explain why each role exists — to protect a specific interest or to keep a specific decision independent — rather than merely listing names, you have reached the depth the Foundation exam rewards.