Study guide
7.2 Last-Week Review Map
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
7.2 Last-Week Review Map
Key Takeaways Explain This Topic AI
PRINCE2 7 has five integrated elements: principles, people, practices, processes, and project context — review must touch all five.
Lock down the 7 principles by name first; they are foundational, high-yield, and underpin every practice and process.
For each of the 7 practices, memorise its purpose and its key management product (business case, risk register, issue register, quality records, plans, progress controls).
Map the 7 processes in flow order and know who owns each: project board directs, project manager controls, team manager delivers.
Stop adding new material in the final days; consolidate the error log and confirm manage-by-exception tolerances including the 7th-edition sustainability target.
Last updated: June 2026
Start From the Five Integrated Elements
PRINCE2 7 is described through five integrated elements that work together. Your last-week map should mirror them so nothing is orphaned:
Element What it is Foundation focus
Principles 7 universal guiding obligations Know all 7 by name; they are non-negotiable and define what 'using PRINCE2' means
- People Leadership, culture, communication, and change Recognise it as a first-class element, not a sub-topic
- Practices 7 aspects to address continuously (formerly called themes) Purpose + key management product of each
- Processes 7 chronological sets of activities Flow order + which role owns each
Project context The environment in which the project operates Understand how context influences tailoring and application
The 7th edition's strengthened emphasis on people, sustainability, and digital/data is frequent exam content, so do not treat people or project context as background.
The 7 Principles and the 7 Practices
Lock the seven principles by name; missing-word and standard items test them directly:
- Ensure continued business justification
- Learn from experience
- Define roles, responsibilities and relationships
- Manage by stages
- Manage by exception
- Focus on products
- Tailor to suit the project
Then attach each of the seven practices to its purpose and its key management product — the registers and approaches the exam loves to test:
- Practice Key product / approach
- Business case Business case + benefits management approach (a living justification, revalidated at each stage)
- Organizing Project management team structure + role descriptions
- Plans Project, stage, team and exception plans (product-based planning)
- Quality Quality management approach + quality register + product descriptions
- Risk Risk management approach + risk register (threats and opportunities)
- Issues Issue management approach + issue register (7th edition renamed 'change' to 'issues')
- Progress Controls, tolerances, and progress reporting
Note the 7th-edition consolidation: the daily log, lessons log, issue register, quality register and risk register can now sit inside a single central project log , kept together or separated as needed.
The 7 Processes and the Tolerance Lines
Rehearse the seven processes in flow order, and pair each with the role that owns it:
Starting up a project — pre-project; appoint executive and project manager, create the project brief.
Directing a project — the project board 's process; runs throughout, makes the key go/no-go decisions.
Initiating a project — the project manager builds the Project Initiation Documentation (PID).
Controlling a stage — project manager's day-to-day control within a stage.
Managing product delivery — the team manager delivers specialist products via work packages.
Managing a stage boundary — prepare the next stage plan (or exception plan) and confirm continued viability.
Closing a project — confirm objectives met and close in a controlled way.
Manage-by-exception tolerances
Manage by exception delegates authority using tolerances — the permissible deviation before a level must escalate. The 7th edition recognises seven tolerance areas : time, cost, quality, scope, benefits, risk, and sustainability . The addition of sustainability is a flagship 7th-edition change and a common exam target. If a manager forecasts breaching a tolerance, they raise an exception report to the level above. In the final days, stop consuming new material: drill the principle names, the practice-to-register mapping, the process flow, and the seven tolerances until recall is instant.
A Day-by-Day Final-Week Plan
A calm, sequenced final week beats cramming. High-yield, foundational material comes first; polish and rest come last:
Day Focus Why
Day 7 The 7 principles by name and one-line meaning Foundational; underpin everything else, and tested directly
Day 6 The 7 practices + their key management products/registers High question density; the practice-to-product mapping is core
Day 5 The 7 processes in flow order + role ownership Process-flow and 'who does what' items are common
Day 4 Tailoring , people , and the seven tolerances 7th-edition emphasis areas that distinguish current material
- Day 3 Full timed mock #1; build the error log by 7+7+7 area Converts knowledge into exam execution
- Day 2 Re-drill only the weakest areas from the error log Targeted, not scattered
- Day 1 Full timed mock #2; light review; rest early Confidence and stamina, not new learning
- Stop signals
Two rules keep the final week productive. First, stop adding new resources — a third textbook or a new question bank this late fragments your memory rather than reinforcing it. Second, review by your error log, not by re-reading everything . If your mocks show 'risk' and 'managing a stage boundary' are weak, spend your limited hours there, not re-reading the principles you already score full marks on. Short mixed-topic sets keep domain-switching sharp, which matters because the live exam jumps between principles, practices and processes question to question.
End the week rested: a tired brain misreads negative-style questions, and on a 60-minute exam there is no recovery time.