PRINCE2 Practitioner is not a bigger Foundation exam - it is a different exam. Foundation asks what the method says; Practitioner hands you a project scenario and asks whether a proposed action is appropriate, and why. It is open book (the official PRINCE2 manual), 56 questions and sub-questions worth 70 marks in 150 minutes, with a 60% pass mark, delivered as a web-based proctored exam through PeopleCert. This guide is built as a self-study course for the PRINCE2 7 exam: it explains how the scenario questions work, walks through the method’s five integrated elements - people, principles, practices, processes and project context - from an application angle, and turns it all into a week-by-week plan with an open-book strategy. It contains study guidance and original explanations only, no real or simulated exam questions. PeopleCert does not publish per-topic question weights, so always confirm the current structure against the official syllabus via the PRINCE2 7 Practitioner page before you book.
Chapter 1: What the Practitioner exam actually tests
From recall to judgement
Practitioner measures whether you can apply and tailor PRINCE2 7 to a running project. The questions are objective-testing items built around scenarios: a project with a context, a set of events, and proposed actions. You are asked things like whether an action is appropriate, which role should take a decision, which management product should record a piece of information, or which principle a behaviour supports or undermines. Two options will often both sound sensible; the correct one is what the method prescribes for that situation, not what a pragmatic manager might improvise. That distinction - method over habit - decides more marks than any single topic.
The format, and what open book really means
The exam runs 150 minutes for 56 questions and sub-questions worth 70 marks, pass mark 60% (42 marks). It is open book: the official PRINCE2 manual is the permitted reference under PeopleCert’s exam rules. Treat the book as a safety net, not a strategy. With roughly two minutes per mark, a candidate who looks up every answer will not finish. The working rule: answer from knowledge, flag what you are unsure of, and use the manual to confirm flagged answers. Before exam day, tab the manual - principles, each practice, each process, the roles appendix, the management-product descriptions - so any lookup lands within seconds. Since 2025 only PRINCE2 7 is examinable; the 5th and 6th Editions are retired, which means any study material built for the old 68-question exam is describing a different test.
Question styles to expect
Objective testing goes beyond simple multiple choice. Expect matching-style items (pair actions with principles, products with processes), assertion-reason style reasoning (is the statement true, is the reason true, does the reason explain the statement), and clusters of sub-questions hanging off one scenario. None of this changes what is being tested - correct application of the method - but practising each style before exam day removes the surprise factor and speeds you up.
Chapter 2: The frame - five integrated elements and seven principles
The five integrated elements
PRINCE2 7 presents the method as five integrated elements: people, principles, practices, processes, and the project context everything is tailored to. The elements are examined together, not separately: a scenario about a risk response can simultaneously test the risk practice, the manage-by-exception principle, and whether the right role acts. Keep the frame in mind as you study - each chapter of this guide is one element, but the exam will mix them.
The seven principles as decision tests
The principles are the non-negotiables: a project that abandons them is not a PRINCE2 project. For Practitioner, convert each from a definition into a test you can apply to a scenario. Ensure continued business justification: if the justification disappears, the correct action is to escalate and potentially stop the project, not to push on. Learn from experience: lessons are actively sought at the start, recorded during, and passed on at the end - a scenario where lessons sit unread in a log violates this. Defined roles, responsibilities and relationships: everyone should know who decides what; a sponsor bypassing the project board is a red flag. Manage by stages: the board commits one stage at a time, reviewing at each boundary. Manage by exception: tolerances give each level room to manage; escalation happens when a tolerance is forecast to be exceeded, not after the fact and not for every wobble. Focus on products: agree what will be delivered, to what quality, before planning activity. Tailor to suit the project: apply the method proportionately - but tailoring never means dropping a principle. In the exam, when an action is proposed, ask which principle it serves or breaks; that single habit answers a surprising number of questions.
Chapter 3: People - the element PRINCE2 7 added weight to
The project ecosystem
PRINCE2 7 treats people as central to method success, a real shift from older editions - and a blind spot if you study from old notes. Projects run inside an organisational ecosystem: the project team, the wider organisation, and external parties whose interests and culture shape what will work. Scenarios test whether you account for that ecosystem - for instance, recognising that a change touching many business users needs communication and change support, not just a revised plan.
Leading change, communication and culture
Expect people-element scenarios about leading change (preparing people to adopt what the project delivers, so benefits actually materialise), communication (the right information to the right stakeholders, deliberately managed), and culture and collaboration (how ways of working affect delivery). The management thread to hold on to: PRINCE2 distinguishes managing (structures, plans, decisions) from leading (direction, motivation, trust), and PRINCE2 7 expects a project manager to do both. When a scenario shows a technically correct plan failing because nobody prepared the people affected, the gap being tested is this element.
Chapter 4: The seven practices, part one - business case, organizing, plans
Business case
The business case practice keeps the justification for the project current and honest. Know the chain from output (what the project produces) to outcome (the change the output enables) to benefit (the measurable improvement) - and dis-benefits, the negative consequences accepted knowingly. The business case is baselined at initiation and reviewed at every stage boundary; the benefits management approach defines how benefits will be measured, often after the project closes. Scenario trap: benefits claimed by the project team, when the senior user is the role accountable for specifying and later demonstrating them.
Organizing
The organizing practice defines who is accountable for what. The project board carries executive (accountable for the business case, the single decision-maker in the end), senior user (represents those who will use the products and owns benefit realisation) and senior supplier (represents those building the products). The project manager runs the project day to day within tolerances; team managers deliver work packages; project assurance gives the board independent confidence (and cannot be delegated to the project manager); a change authority may be delegated decisions on changes within limits; project support provides administration. Practitioner scenarios constantly test role boundaries: who approves a stage plan (the board), who checks quality on the board’s behalf (assurance), who fixes a work-package problem within tolerance (the team manager, reporting via checkpoints).
Plans
The plans practice runs on levels: the project plan for the board, stage plans for the project manager’s day-to-day control, optional team plans for work packages, and an exception plan when a tolerance breach requires a re-planned path for board approval. Planning in PRINCE2 is product-based: first define the project product description, break the scope into products with product descriptions (including quality criteria), then work out the activities. Scenario trap: jumping to activity scheduling when the products have not been defined - the method says products first.
Chapter 5: The seven practices, part two - quality, risk, issues, progress
Quality
The quality practice turns “good enough” into something checkable. Quality planning captures the customer’s quality expectations and acceptance criteria in the project product description; each product description carries quality criteria, the checkable specifics; the quality register tracks planned and completed quality activities. Keep two role pairs straight: quality planning is management’s job, quality control (reviews, testing) happens in delivery, and project assurance checks quality on the board’s behalf independent of the project manager. A scenario where acceptance criteria appear only at handover is a quality-planning failure - the criteria belong up front.
Risk
The risk practice manages uncertainty in both directions: threats (negative) and opportunities (positive). Each risk gets a cause-event-effect description, an assessment of probability and impact, a chosen response, and an owner; everything lives in the risk register. Know the response types for threats (avoid, reduce, transfer, accept, and preparing contingent plans) and that opportunities have mirrored responses (exploit, enhance, share, reject). The organisation’s risk appetite and the project’s risk tolerance set how much uncertainty is acceptable - and a risk forecast to exceed risk tolerance is escalated like any other exception. Scenario trap: treating an issue (has happened) as a risk (might happen); the registers, and the responses, differ.
Issues
The issues practice handles things that have happened: requests for change, off-specifications, and problems or concerns. Formal issues go in the issue register; minor matters can live in the project manager’s daily log. The decision chain matters: the project manager assesses impact, and decisions on changes belong to the project board or its delegated change authority, usually funded through a change budget. A baseline can only be changed through this controlled path. Scenario trap: a project manager quietly approving a customer-requested scope change to keep goodwill - that bypasses change control, however small the change looks.
Progress
The progress practice is management by exception made operational. Tolerances - around time, cost, quality, scope, benefits, risk and sustainability - are set for each management level. Event-driven and time-driven controls track actuals: checkpoint reports from team manager to project manager, highlight reports from project manager to board, end stage reports at boundaries. When a tolerance is forecast to be exceeded, the project manager raises an exception report to the board; if the board wants to continue, it commissions an exception plan. Learn which report flows between which roles and when - it is one of the most-tested chains in the exam.
Chapter 6: The seven processes - who does what, when
From idea to commitment
Starting up a project is pre-project due diligence: appoint the executive and project manager, capture lessons, produce the project brief and outline business case, and plan initiation - enough to ask whether the project is worthwhile at all. Directing a project is the board’s process, running from initiation to closure: authorise initiation, authorise the project, authorise each stage, give ad-hoc direction, authorise closure. The board directs through these decision points - it does not manage day to day. Initiating a project builds the project initiation documentation (PID): the assembled definition of how the project will be managed - approaches, controls, plans, refined business case - the contract between board and project manager.
Delivering through stages
Controlling a stage is the project manager’s home process: authorise work packages, review progress, capture and examine issues and risks, take corrective action within tolerance, escalate beyond it, and report highlights to the board. Managing product delivery is the team manager’s mirror: accept the work package, build the products to their descriptions, report checkpoints, and hand back completed work. Managing a stage boundary prepares the board’s next commitment: update the business case and project plan, report on the ending stage, and prepare the next stage plan - or an exception plan if that is why the boundary was reached. Closing a project confirms product acceptance, checks the objectives were met, hands over products, captures lessons and recommends closure - which the board authorises. Planned or premature, closure is a controlled process, never just stopping.
How processes carry the products
Scenario questions often hinge on where a management product is created or used: the project brief belongs to starting up, the PID to initiating, work packages and highlight reports to controlling a stage, checkpoint reports to managing product delivery, end stage reports and next-stage plans to the boundary process, and acceptance records to closing. Build yourself a one-page map of processes, roles and products - drawing it from memory is one of the highest-value revision exercises for this exam.
Chapter 7: Tailoring, the open-book strategy, and exam day
Tailoring without breaking
Tailor to suit the project is a principle, so tailoring questions run through every topic: a small project might merge stages, combine roles (within rules - the executive and project manager roles stay separate, and assurance stays independent of the project manager), simplify reports into shorter forms, or lighten registers. What tailoring never does is drop a principle, skip a process entirely, or blur accountability. When a scenario proposes a shortcut, test it: does this keep the principles intact in proportionate form, or does it abandon control? That is usually the line between the right and the almost-right option.
Prepare the book, then rehearse with it
Your open-book preparation has two halves. Prepare the manual: tabs for each practice, each process, the principles, roles and management products; margin notes where your practice questions went wrong. Rehearse the exam: timed blocks of scenario questions, answering first from knowledge and confirming flagged items from the tabbed pages. Time yourself against marks, not questions - 70 marks in 150 minutes is just over two minutes per mark. If you are entering directly via PMP, CAPM or IPMA, add vocabulary time up front: the exam’s language is strictly PRINCE2’s, and translating mid-exam costs minutes. To turn any of the week plans above into dated weeks from your own start date, use the free study-plan generator.
Exam day
The exam is booked through PeopleCert and delivered as a web-based proctored online session (accredited training organisations can also arrange it). Run the system check early, prepare your ID and a cleared room, and have the permitted manual ready in line with PeopleCert’s current exam rules. During the exam: bank the marks you know, flag and return to the rest with the manual, and answer everything - there is no penalty for a wrong answer. Afterwards, diary the renewal decision: the certification is valid three years, renewable by re-taking the exam or via PeopleCert Plus membership with 20 CPD points logged per year. If you are still weighing this credential against its main alternative, the PMP vs PRINCE2 comparison sets out which markets reward which.