PRINCE2 Foundation v7 Cheat Sheet

April 8, 2026

High-yield PRINCE2 Foundation v7 review for key rules, traps, decision cues, formulas, and final-week reminders.

On this page

Use this for last-mile PRINCE2 Foundation review. Pair it with the Syllabus for coverage and Practice to validate recall.

PRINCE2 control flow

    flowchart LR
	  A["Forecast against tolerance"] --> B{"Within tolerance?"}
	  B -->|Yes| C["Project Manager controls and reports"]
	  B -->|No| D["Raise an exception"]
	  D --> E["Project Board reviews options"]
	  E --> F["Authorize, redirect, or stop"]

Foundation questions often reward the answer that keeps the project controlled, justified, and product-focused. When you are unsure, look for the option that makes the situation governable through the right role, product, or exception path.

The 7 principles

Principle	What it really means	Common trap
Continued business justification	the project must stay worth doing	treating the Business Case as a one-time startup document
Learn from experience	use lessons before and during delivery	treating lessons learned as a closure-only activity
Defined roles, responsibilities, and relationships	accountability must be explicit	assuming everyone “collectively owns” unclear decisions
Manage by stages	review and authorize work in chunks	planning the whole project once and never rechecking
Manage by exception	escalate only when tolerance is forecast to be exceeded	escalating everything or hiding real exceptions
Focus on products	define outputs and acceptance first	planning activity without clarifying product expectations
Tailor to suit the project	adapt the method to context	removing core controls in the name of simplicity

Practices and what they govern

Practice	What it governs	What changes the answer
Business Case	viability and justification	if value is in doubt, check justification first
Organizing	structure and accountability	if ownership is unclear, fix roles and reporting
Plans	levels of plan and baselines	if work is vague, the plan/product definition is often weak
Quality	acceptance criteria and methods	if “done” is unclear, quality logic is missing
Risk	uncertainty and responses	use risk logic for future uncertainty, not current issues
Issues	changes, concerns, and requests	current problems belong here, not in the risk register
Progress	monitoring, reporting, and exception control	tolerance and escalation cues matter here most

Processes and when you are probably in them

Process	When it fits	Fast cue
Starting up a Project (SU)	checking whether the project should begin	early validation and setup
Directing a Project (DP)	board-level authorization and oversight	authorizing project, stage, or exception
Initiating a Project (IP)	building the management baseline	approaches, controls, and project-level plan
Controlling a Stage (CS)	day-to-day management during a stage	monitor, issue, escalate within a stage
Managing Product Delivery (MP)	team accepts and delivers work packages	work-package level delivery
Managing a Stage Boundary (SB)	reviewing one stage and preparing the next	next-stage planning and end-stage evidence
Closing a Project (CP)	confirming acceptance and closure	handover, closure, lessons, follow-on actions

Roles and decision rights

Role	Main concern	Strong cue
Project Board	business, user, and supplier interests	authorizes project, stages, and exceptions
Project Manager	day-to-day control within tolerance	plans, monitors, reports, and manages issues
Team Manager	work-package delivery and reporting	accepts work packages and reports progress

Management-product picker

If the question is about…	Likely product
why the project should continue	Business Case
what the final product must be	Project Product Description
how work is baselined and sequenced	Project Plan or Stage Plan
how quality will be managed	Quality Management Approach
evidence of quality checks	Quality Register
current problems or requests for change	Issue Register
identified risks and responses	Risk Register
regular progress reporting	Highlight Report
exception escalation	Exception Report
end-of-stage review and next authorization	End Stage Report and Next Stage Plan

Tolerance and exception rules

Situation	Better answer	Why
forecast remains within tolerance	Project Manager handles and reports	management by exception
forecast moves outside tolerance	escalate via exception	board-level decision is now required
stage is ending	prepare end-stage evidence and next-stage plan	manage by stages
viability is threatened	revisit the Business Case	justification is a core principle

Fast elimination rules

If the stem says outside tolerance, look for an exception path.
If the stem asks what must be clear first, roles, products, and justification often come before activity detail.
If the option skips a management product that would make the situation controllable, it is often weak.

Ready to drill? Use the PRINCE2 Foundation practice handoff or go straight to the PRINCE2 Foundation practice preview on MasteryExamPrep.

Revised on Monday, April 27, 2026

Study Plan

Practice