PRINCE2 Foundation is a recall exam, and that single fact should shape everything about how you study for it. It does not ask you to manage a tricky project or weigh competing options under pressure; it asks whether you know the PRINCE2 method accurately, in its own words. The whole of PRINCE2 is built from three sets of seven, the seven principles, the seven practices (called themes before PRINCE2 7), and the seven processes, plus the idea of tailoring that ties them to a real project. Learn those, understand how they connect, and the exam becomes very passable. This guide is a full self-study course. It teaches each of the sevens, explains what each is for rather than listing it, shows how the parts work together across a project’s life, and turns it into a short, tight study plan. It is original teaching material only. It contains no real or simulated exam questions, and you should confirm the current structure and terminology against PeopleCert’s official materials, since PRINCE2 7 refined several terms.
Chapter 1: Exam overview and how to use this guide
What PRINCE2 Foundation actually measures
PRINCE2 Foundation measures whether you understand the PRINCE2 method well enough to work effectively within a project that uses it, contributing to and following its products and processes. It is deliberately a knowledge exam, not an application exam: that distinction is the job of the higher Practitioner level, which tests whether you can apply and tailor the method to a scenario. For Foundation, the questions test recall and comprehension of the method’s structure, terminology, and the purpose of its parts. This is good news for planning, because it means your study should aim at accurate, confident knowledge of a defined body of content rather than at situational judgement, and the content does not change with the difficulty of imaginary projects.
The format and what it implies
The exam is 60 multiple-choice questions in 60 minutes, closed-book, and you need 36 correct out of 60, which is 60%, to pass. (PRINCE2 7 raised the pass mark from the older 55%, so make sure any practice you do is calibrated to 60%.) A minute per question is comfortable for a recall test, so time pressure is not the challenge; precision is. Because it is closed-book, you cannot look anything up, and because the questions hinge on PRINCE2’s specific wording, vague familiarity is not enough. The practical implication is that this is a vocabulary-and-structure exam, best prepared for with deliberate memorisation and frequent self-testing rather than with long, passive reading.
What PRINCE2 is, and how to use this course
PRINCE2 (PRojects IN Controlled Environments) is a structured, process-based project management method that is widely used in the UK, Europe and the public sector, and it provides a common language and a defined way of organising, managing and controlling a project. Read the chapters in order, because the principles set the rules, the practices describe the aspects you manage throughout, the processes describe the lifecycle in which you do that managing, and tailoring explains how it all flexes to fit a project. Treat the bold terms as items you must be able to define and place. Crucially, do not learn the three sets of seven as isolated lists; the exam rewards understanding how a practice (say, risk) is handled within a process (say, controlling a stage), and that connective understanding is what the later chapters build.
Chapter 2: The seven principles
The principles are the foundation of PRINCE2 and the right place to start, because they are the universal rules that must be true for a project to be a genuine PRINCE2 project. They are not optional and they are not tailored away; a project that ignores them is not using PRINCE2 even if it borrows the templates.
Justification, learning, and roles
Continued business justification is the first and most pervasive principle: there must be a justifiable reason to start the project, and that justification must remain valid throughout. If it ever stops being worthwhile, the project should be stopped. This is why the business case runs through the whole method. Learn from experience requires teams to seek out lessons from previous and current work and to act on them, rather than repeating known mistakes, which is why a lessons log and lessons reports exist. Defined roles, responsibilities and relationships (the wording was broadened in PRINCE2 7) requires that everyone knows who is doing what, with a clear project management team structure representing the business, user and supplier interests, because projects cross normal departmental lines and ambiguity causes failure.
Managing the work: stages, exception, and products
Manage by stages breaks the project into discrete management stages that are planned, monitored and controlled one at a time, giving the project board defined points to review progress and the continued business justification before committing to the next stage. Manage by exception establishes tolerances (permitted deviations) for objectives, and means that a level of management only escalates to the level above when those tolerances are forecast to be exceeded, which lets senior people delegate day-to-day control and stay focused on the bigger picture. Focus on products insists that a project agrees and defines its products (its deliverables, with their quality criteria) before deciding the activities to create them, because clarity about what is to be delivered is what keeps scope and expectations under control.
Tailoring as a principle
The seventh principle, in PRINCE2 7 phrased as ensure tailoring to suit the project (previously “tailor to suit the project environment”), is itself one of the universal rules: PRINCE2 must always be adapted to the project’s size, environment, complexity, importance, capability and risk. This matters because newcomers sometimes imagine PRINCE2 as a rigid bureaucracy, when the method explicitly requires you to scale it sensibly. Understanding the principles as a connected set, justification gives the why, defined roles the who, stages and exception the control, and products the focus, is far more durable for the exam than memorising seven phrases, and it is the lens through which the practices and processes make sense.
Chapter 3: The seven practices (themes), part one
The practices, which PRINCE2 7 renamed from themes, are the aspects of project management that must be addressed continually throughout the project rather than only at one point. There are seven, and each answers a basic project question and is supported by specific management products. This chapter covers the first three; the next covers the rest.
Business case: why?
The business case practice answers “why are we doing this?”. It develops and maintains the justification for the project, capturing the costs, the expected benefits, the timescales and the risks so that the project board can judge whether the project is and remains desirable, viable and achievable. The central management product is the business case itself, and a closely related idea is the benefits management approach, which defines how and when the project’s benefits will be measured, often after the project closes. Because continued business justification is a principle, this practice is in a sense the engine room of PRINCE2: it is what every stage boundary checks.
Organisation: who?
The organisation practice answers “who is involved and what are their responsibilities?”. PRINCE2 defines a project management team structure based on three project interests, business (is it value for money?), user (will it deliver usable products?), and supplier (can we build it?), and it sets out roles including the project board (which directs the project), the project manager (who manages it day to day), and team managers. Understanding that the project board owns the project and the project manager runs it within delegated tolerances is essential, because the split between directing and managing recurs throughout the processes.
Quality: what (standard)?
The quality practice answers “what must the products be like, and how good is good enough?”. It covers defining the products and their quality criteria, planning how quality will be achieved and checked, and controlling quality through methods such as the quality review technique. Key management products are the project product description (which defines the project’s overall output and acceptance criteria) and individual product descriptions. This practice operationalises the focus-on-products principle: by writing down what each product is and the criteria it must meet, the team turns vague expectations into checkable standards, which is also why product descriptions feed planning.
Chapter 4: The seven practices (themes), part two
The remaining four practices cover planning the work, and then the three aspects you must keep watching as the project runs: risk, change, and progress.
Plans: how, how much, when?
The plans practice answers “how, how much and when?”. PRINCE2 envisages plans at more than one level, typically a project plan owned by the project board and stage plans used by the project manager to control each management stage, with team plans and exception plans as needed. Its signature technique is product-based planning: you identify the products first (using the project product description, a product breakdown structure, and product descriptions), then work out the activities and dependencies to create them. This is the focus-on-products principle expressed as a planning method, and it is a favourite topic because it links a principle, a practice and a technique together.
Risk: what if?
The risk practice answers “what if?”. It is the systematic identification, assessment and control of uncertainty, both threats (negative risks) and opportunities (positive ones), so the project can improve its chances of success. The main management product is the risk register, which records each risk, its analysis and the chosen response. PRINCE2 recognises response types for threats (such as avoid, reduce, transfer, accept and prepare contingent plans) and mirrored responses for opportunities, and it frames a recommended risk-management procedure of identify, assess, plan, implement and communicate. The exam expects you to know that risk is managed continuously and to recognise the register and the response types.
Change and progress: impact, and where are we?
The change practice answers “what is the impact of this change, and do we approve it?”. It handles issues (anything raised during the project, including requests for change and off-specifications) in a controlled way, typically via an issue register and a defined issue-and-change procedure, often supported by configuration management so the project always knows the status of its products. The progress practice answers “where are we now, and should we continue?”. It is about monitoring actual progress against the plan, controlling through the delegated tolerances, and reporting via products such as the highlight report (project manager to board) and the exception report (raised when a tolerance is forecast to be breached). Progress is where manage-by-exception becomes concrete: the board steers by reviewing progress at stage boundaries and by responding to exceptions, not by supervising daily work.
Chapter 5: The seven processes
The processes describe the project lifecycle, the structured set of activities that take a project from a mere idea through to a controlled close, and which level of the team is responsible at each point. Where the principles are the rules and the practices are the ongoing aspects, the processes are the chronological story. Learning them in order, and noticing who owns each, is the most reliable way to hold them.
Starting up, directing, and initiating
Starting up a project (SU) happens before the project proper and answers “do we have a viable and worthwhile project?”. It is triggered by a project mandate, produces an outline business case and a project brief, and asks the project board to authorise initiation. Directing a project (DP) runs from the end of starting up to the end of the project and is the project board’s process: it is how senior management authorises initiation, the project itself, each stage, and closure, and gives ad hoc direction, all without getting involved in day-to-day management. Initiating a project (IP) establishes solid foundations: it produces the project initiation documentation (PID), the project’s baseline that brings together the detailed business case, the various management approaches (risk, quality, change, communication), the project plan and the controls. Recognising that DP is the board’s process while SU and IP set the project up is a high-value distinction.
Controlling delivery: stages, delivery, and boundaries
Controlling a stage (CS) is the project manager’s day-to-day process within a management stage: authorising work packages, monitoring progress, dealing with issues and risks, reporting via highlight reports, and taking corrective action within tolerance. Managing product delivery (MP) is the team’s process: it is the controlled interface where team managers (or teams) accept, execute and hand back work packages, building the products to the agreed quality. Managing a stage boundary (SB) happens near the end of each management stage: the project manager updates the business case and project plan, plans the next stage, and gives the board the information it needs to decide whether to continue, which is manage-by-stages made operational.
Closing a project
Closing a project (CP) brings the project to a controlled end, whether planned or premature: it confirms the products have been accepted and handed over, checks that objectives and the business case have been met, captures lessons in an end project report, and recommends closure to the board. A common misconception the exam guards against is thinking closure is a separate phase run by the board; in PRINCE2 it is work done by the project manager within the final stage, with the board authorising the actual closure through directing a project. Seeing the processes as a connected flow, set up, then a repeating loop of control a stage, deliver products, and cross a stage boundary, then close, turns seven names into one coherent lifecycle.
Chapter 6: Tailoring, management products, and how it all fits together
The final piece of understanding, and a recurring exam theme, is that PRINCE2 is meant to be adapted, and that the method holds together through its defined management products and the relationships among principles, practices and processes.
Tailoring and the project environment
Tailoring is adapting PRINCE2 to suit a particular project’s context, its scale, complexity, importance, team capability and risk, so that the method adds value rather than bureaucracy. Tailoring can adjust how practices are applied, how management products are combined or formatted, and how processes are handled, but it must never discard the seven principles, which are universal. PRINCE2 also distinguishes tailoring for a single project from embedding the method across an organisation, and PRINCE2 7 strengthened its attention to broader factors such as sustainability, people and digital and data considerations, so confirm the current emphasis in PeopleCert’s syllabus. The exam tests that you grasp the idea and limits of tailoring, not that you can perform a complex tailoring exercise.
Management products as the connective tissue
PRINCE2 organises its documents as management products, and recognising the main ones, and which practice or process they belong to, ties the whole method together. Baselines such as the project brief, the project initiation documentation (PID), the business case and product descriptions define what is agreed; records such as the risk register, issue register, lessons log and quality register capture ongoing information; and reports such as the highlight report, exception report, end stage report and end project report communicate status and outcomes. You do not need to memorise every field, but you should be able to say what a product is for and where it sits, because many questions are essentially “which product, which practice, which process?”.
Seeing the method as one system
The most durable way to hold PRINCE2 for the exam is to see the three sevens as one system rather than three lists. The principles are the always-true rules; the practices are the aspects you manage continuously and the products that support them; the processes are the lifecycle in which that managing happens, with clear ownership between the directing board and the managing project manager; and tailoring is how the whole thing is sized to a real project without breaking the principles. When a question describes a situation, this system lets you locate it, an escalation question is manage-by-exception and the progress practice within controlling a stage, a justification question is the business case practice driven by the continued-business-justification principle, and locating it is usually most of the way to the answer.
Chapter 7: Study plan and timeline
Because Foundation is a recall exam, the plan is short and depends on consistency rather than total hours. The structure is simple: learn the sevens with understanding, drill them until they are reliable, and confirm readiness on official sample papers.
A tight multi-week plan
Most candidates need roughly 20 to 40 hours over three to five weeks, with people new to structured project methods at the higher end. A workable shape is: week one on the structure of PRINCE2 and the seven principles, until you can state each and explain what it forces the project to do; week two on the seven practices, tying each to the question it answers and its main management products; week three on the seven processes in lifecycle order, noticing who owns each and how the practices show up inside them; and a final stretch on tailoring, terminology drills, and full-length sample papers. PRINCE2 Foundation is often taken at the end of an accredited course, which compresses this, but the same sequence applies to self-study. To turn it into dated weeks for your own start date, use the free study-plan generator.
Memorise the sevens deliberately
The core skill is recalling the three sets of seven accurately, so make memorising them an active, spaced exercise rather than a hopeful by-product of reading. Use a mnemonic for each set, write the lists from memory until they are perfect, and for every practice pair it with the question it answers and its key products, and for every process pair it with its purpose and its owner. Short, frequent reviews lock these in far better than one long session, and they unlock a large share of the questions directly. Because the exam is recall-based, momentum matters: if you let the plan drift, the sevens fade and need relearning, so a steady cadence beats sporadic cramming. If you are weighing PRINCE2 against another credential for your market, the PMP vs PRINCE2 comparison covers how the two differ by region and approach.
Chapter 8: Final preparation, exam day, and format
Use the official sample papers
PeopleCert publishes official sample papers, and they are the best readiness gauge because they match the real wording and difficulty far better than generic question sets. Sit them under the 60-minute, closed-book condition, then review every wrong answer against the official manual or syllabus to find the exact terminology you have not pinned down, since the gap is almost always a precise definition rather than a concept. Aim to be scoring comfortably above the 60% (36/60) pass mark on fresh papers before you book, and make sure the practice is calibrated to 60% rather than the older 55%.
Confirm the current PRINCE2 7 terminology
Because PRINCE2 7 refined several terms, the most common avoidable error is studying outdated wording. Confirm against PeopleCert’s current materials that you are using practices rather than the older themes, the updated principle wording (for example, defined roles, responsibilities and relationships, and ensure tailoring to suit the project), and any changed emphasis such as the increased attention to people, sustainability and data. Getting the current names right protects easy marks that older study guides would quietly cost you.
Exam day and format
On the day, the exam is 60 multiple-choice questions in 60 minutes, closed-book, requiring 36 correct (60%), taken either at the end of an accredited course or via PeopleCert’s online proctoring with suitable identification. With a comfortable minute per question, the discipline that matters is accuracy: read each question for the precise PRINCE2 term it is testing, answer from the method as the current syllabus defines it rather than from how projects work in general, and flag and return to anything uncertain rather than stalling. Prepared with the sevens understood as one connected system and drilled to reliable recall, a recall exam at a 60% bar is very achievable, and the structure you built is exactly what carries you through it.