Try 60 free PRINCE2 Foundation questions across the exam domains, with answers and explanations, then continue in PM Mastery.
This free full-length PRINCE2 Foundation practice exam includes 60 original PM Mastery questions across the exam domains.
The questions are original PM Mastery practice questions aligned to the exam outline. They are not official exam questions and are not copied from any exam sponsor.
Count note: this page uses a 60-question full-length practice format for PRINCE2 Foundation Version 7 review. Always confirm current booking, language availability, and delivery rules directly with PeopleCert.
Set a 60-minute timer and answer all 60 questions before reading explanations. Track misses by PRINCE2 concepts, principles, people, practices, or processes.
Use this page as a PRINCE2 Foundation diagnostic, not as the only measure of readiness. The most useful result is the pattern behind your misses.
| Result pattern | What it usually means | Next step |
|---|---|---|
| Strong score and misses are scattered | Your PRINCE2 recognition may be stable. Review explanations and protect timing. | |
| Many principle misses | Revisit continued business justification, roles, stages, tolerances, and learn-from-experience logic. | |
| Many practice misses | Drill Business Case, organizing, plans, quality, risk, issues, and progress purposes. | |
| Many process misses | Review the PRINCE2 lifecycle and who authorizes what at each control point. | |
| Similar terms feel interchangeable | Write short distinction rules for roles, products, and process purposes. |
| Field | Record |
|---|---|
| Overall score | ___ / 60 questions |
| Timing result | Finished early / on time / rushed late |
| Highest-miss area | concepts / principles / people / practices / processes |
| Most expensive mistake type | role confusion / product confusion / wrong process step / weak tolerance logic / other: ___ |
For concept review before or after this set, use the PRINCE2 Foundation guide on PMExams.com.
This static page is useful for one diagnostic pass. PM Mastery is better for repeated practice because it gives you varied timed attempts, focused PRINCE2 drills, explanations, and progress history instead of one page you can memorize.
| Checkpoint | Approximate time budget | What to do |
|---|---|---|
| Questions 1-20 | 20 minutes | Keep concept and role decisions quick. |
| Questions 21-40 | 40 minutes cumulative | Watch for practice-purpose and management-product traps. |
| Questions 41-60 | 60 minutes cumulative | Finish with enough time to review marked process and tolerance items. |
If you retake this free diagnostic, treat the second attempt as a reasoning check rather than a fresh score. Give more weight to varied timed attempts in PM Mastery than to repeating one static page.
| Item | Detail |
|---|---|
| Issuer | PeopleCert |
| Exam route | PRINCE2 Foundation |
| Official exam name | PRINCE2 Project Management Foundation (Version 7) |
| Full-length set on this page | 60 questions |
| Exam time | 60 minutes |
| Topic areas represented | 5 |
| Topic | Approximate official weight | Questions used |
|---|---|---|
| Project and PRINCE2 Key Concepts | 3% | 2 |
| PRINCE2 Principles | 8% | 5 |
| People in Successful Projects | 14% | 8 |
| PRINCE2 Practices | 60% | 36 |
| PRINCE2 Processes | 15% | 9 |
Topic: People in Successful Projects
A project is delivering a new online booking journey for a public service. The product is built and the project manager is preparing to request acceptance at the end of the stage. User representatives who trialled the journey say the wording and step order may confuse customers, which could reduce the expected benefits (fewer calls to the helpdesk). Time tolerance for the stage is almost exhausted.
What is the BEST next action?
Best answer: A
What this tests: People in Successful Projects
Explanation: In PRINCE2, users define and confirm product acceptance, so their feedback is essential before requesting acceptance. Using feedback to check the product against its acceptance criteria helps avoid accepting something that undermines benefits realization. Any resulting changes should be captured as issues and managed through agreed controls, especially when tolerances are tight.
User feedback supports product acceptance by validating the product against its defined acceptance criteria (set from the user perspective) before formal sign-off. It also supports benefits realization by confirming the product is likely to be used as intended and will enable the outcomes described in the Business Case and benefits management approach.
Best next action is to obtain structured feedback from user representatives (for example, via a quality review or acceptance review) and then control the consequences:
Accepting first and “fixing later” risks approving a product that will not deliver the expected benefits.
User feedback is needed to confirm acceptance criteria are met and to protect benefits, with any required changes captured and controlled.
Topic: PRINCE2 Practices
A project manager wants to design the project management team structure and clarify interfaces with line management. She creates a table of key activities (e.g., authorizing work, approving products, reporting progress) and, for each activity, identifies who is Responsible, Accountable, Consulted, and Informed.
Which PRINCE2 organizing technique is this?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: This is a responsibility assignment matrix, commonly expressed as a RACI. It is used in the Organizing practice to define who does what and to make interfaces between roles (including line management and project roles) clear.
The technique described is a responsibility assignment matrix (RACI). In PRINCE2, this is used to design and communicate the project management team structure and its interfaces by making accountabilities explicit for key activities and decision points. By mapping each activity to who is Responsible (does the work), Accountable (owns the outcome/decision), Consulted (provides input), and Informed (kept up to date), the project manager reduces role ambiguity and improves governance and handoffs.
Key takeaway: an organization chart shows reporting lines, but a RACI shows responsibility and interfaces for specific work.
A RACI matrix defines roles and interfaces by assigning Responsible, Accountable, Consulted, and Informed for project activities.
Topic: PRINCE2 Practices
A project manager wants a single place to log all planned quality activities and track what quality checks have been completed, including dates, responsibilities, and the results (for example, pass/fail and any follow-up actions).
Which PRINCE2 management product is being described?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: The Quality Register provides an audit trail of quality activities across the project. It is used to record what quality checks are planned and what has been performed, along with key details such as dates, responsibilities, and outcomes. This matches the need to track completion and results of quality work in one place.
In PRINCE2, the Quality Register is the management product used to plan and record quality management activities and to capture the results of those activities. It supports control by giving visibility of what quality methods (for example, reviews, tests, inspections) are scheduled for products and whether they have been carried out, by whom, when, and with what outcome (including follow-up actions).
The key point is that it is a log of quality activity and results across products, not a description of a product, and not a log of issues or general notes.
It records planned and completed quality management activities and their results for each product.
Topic: PRINCE2 Processes
In the Managing Product Delivery process, which role is responsible for accepting an authorized Work Package, managing the work to create the agreed products, and handing the completed Work Package back to the project manager?
Best answer: D
What this tests: PRINCE2 Processes
Explanation: Managing Product Delivery is about the team accepting, doing, and delivering assigned work. The team manager takes receipt of the authorized Work Package, manages its execution, and returns the completed products (and confirmation of completion) to the project manager. The project manager focuses on authorizing and monitoring the Work Package rather than executing it.
In PRINCE2, a Work Package is the mechanism for agreeing, authorizing, and controlling work that produces one or more products. Within the Managing Product Delivery process, the team manager’s responsibilities are to:
By contrast, the project manager is responsible for authorizing Work Packages, agreeing reporting and tolerances, and reviewing progress and completion against what was agreed. The key distinction is that acceptance and delivery of the Work Package sits with the team manager, while authorization and overall control sits with the project manager.
The team manager accepts the Work Package, coordinates its execution, and delivers the completed products back to the project manager.
Topic: PRINCE2 Practices
A project will replace a company’s delivery fleet. The Project Board has set a sustainability constraint (reduce lifecycle CO\(_2\) by at least 30%) and a tolerance (overall carbon footprint must not exceed an agreed limit).
At the end of the current stage, the Project Board asks for evidence that the project is still justified and that these sustainability considerations are reflected in the justification and the agreed constraints/tolerances.
Which management product should the project manager provide?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: Sustainability considerations can be built into the project’s justification as benefits and dis-benefits, and also expressed as constraints and tolerances. The management product used to evidence continued justification to the Project Board is the Business Case, which should be kept under review and updated as the project progresses.
In PRINCE2, the Business Case supports the principle of continued business justification. It is where the project’s justification is documented and maintained, including sustainability-related benefits and dis-benefits, and any sustainability constraints that must be met for the project to remain viable. Sustainability can also be represented through measurable targets and limits that relate to tolerances (for example, allowable carbon footprint variation) so decision-makers can judge whether the project remains acceptable.
At stage boundaries and whenever significant changes occur, the Business Case is reviewed and updated so the Project Board can confirm the project is still justified and that key constraints and tolerances (including sustainability ones) remain achievable. Progress reports may reference these factors, but they are not the primary justification product.
The Business Case is the primary management product for demonstrating continued justification, including how sustainability benefits, constraints, and tolerances are addressed.
Topic: PRINCE2 Practices
Midway through a delivery stage, several products have been handed over by teams, but stakeholders disagree about what is actually complete and approved. The Project Board asks the project manager for an objective, up-to-date view of the current status of all products to support governance and decision-making.
In PRINCE2 terms, what should be produced next?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: A Product Status Account is used to provide transparent, reliable product status information to those exercising governance (such as the Project Board). It is derived from maintained product records (for example, the Product Register) so it resolves disagreement and supports informed control decisions.
The key need is transparency about what products are complete and approved, so governance can act on accurate information. In PRINCE2, product status information is maintained in registers/records (such as the Product Register and related quality records) and can be summarized for stakeholders in a Product Status Account.
Producing a Product Status Account:
Progress reporting like checkpoints and highlights may use this information, but they do not replace the specific purpose of a Product Status Account.
A Product Status Account provides an objective snapshot of product status drawn from the product records/registers for transparent reporting to governance.
Topic: PRINCE2 Practices
A three-stage software rollout has repeated the same problems in each stage: requirements are misunderstood, defects are reworked, and the team says “we’ll do it differently next stage.” At each stage boundary, the project manager produces an End Stage Report focused on time/cost and approves the next Stage Plan, but there is no record of learning from the stage just completed.
Which is the MOST likely underlying cause in PRINCE2 terms?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: PRINCE2 expects lessons to be captured throughout the project (in a Lessons Log) and then formally summarized and communicated at stage end and at project end (Lessons Report). If this is not done, the same issues can recur from stage to stage because improvements are not fed into planning and ways of working.
The key concept is PRINCE2’s lessons mechanism within the Progress practice: learn continuously and ensure learning is communicated and used. During delivery, lessons are captured as they occur in a Lessons Log. At stage end, lessons should be reviewed and included in stage-end reporting so they can influence the next Stage Plan and how work will be managed. At project end, lessons are consolidated into a Lessons Report so the organization can benefit beyond the project.
If stage boundaries only focus on time/cost status and moving on, without recording and reporting lessons, recurring rework and repeated misunderstandings are a typical outcome. The closest trap is confusing lessons reporting with routine progress reporting such as Checkpoint Reports.
Without capturing and reporting lessons at stage end (and at project end), repeated problems are not identified and acted on in the next stage.
Topic: People in Successful Projects
A project to introduce a new customer portal is midway through a stage. The Senior User asks the Project Manager to add an extra feature that will increase cost and may delay delivery, but says it is “worth it”. Tolerances and decision authority are not stated.
What should the Project Manager clarify first before deciding whether to proceed?
Best answer: C
What this tests: People in Successful Projects
Explanation: PRINCE2 assigns a single point of accountability for the Business Case to the Executive. When a request could change costs, timescales, risks, or expected benefits, the first check is whether the project remains justified and whether the Executive agrees the impact. This protects the project from being driven by conflicting stakeholder preferences instead of business value.
In PRINCE2, the Executive owns the Business Case and is accountable for ensuring continued business justification throughout the project. This “single point of accountability” avoids competing stakeholder priorities driving decisions that reduce value, and ensures there is one clear authority to balance benefits, costs, and risks.
When a change request is likely to increase cost and delay delivery, the first clarification is the impact on the Business Case (including whether the project is still justified) and whether the Executive has confirmed that justification still stands and will sponsor the decision. Planning updates and delivery feasibility are important, but they come after confirming the project still makes business sense.
The Executive is the single point of accountability for the Business Case, so the decision must be based on whether the project remains justified.
Topic: PRINCE2 Principles
In PRINCE2, when the project manager forecasts that a stage will exceed an agreed tolerance, what is the correct escalation action and who must be informed?
Best answer: D
What this tests: PRINCE2 Principles
Explanation: PRINCE2 uses management by exception, so a forecast that tolerances will be exceeded must be escalated rather than managed within the stage. The project manager escalates by producing an Exception Report. The Project Board is informed because it owns the authority to decide how to proceed when tolerances are forecast to be breached.
Under the PRINCE2 principle of management by exception, authority is delegated to the project manager to run the stage within agreed tolerances. If the project manager forecasts that stage tolerances will be exceeded, they must escalate rather than continue under the existing authority. The escalation mechanism is an Exception Report, which is submitted to the Project Board so it can decide what action to take (for example, request an Exception Plan, adjust tolerances, or stop the project). A Highlight Report is routine progress reporting and does not replace escalation when a tolerance breach is forecast.
Forecasting a tolerance breach requires escalation by exception, with an Exception Report sent to the Project Board for a decision.
Topic: PRINCE2 Practices
On a software implementation project, several change requests have been handled inconsistently. Some minor changes wait weeks for Project Board approval, while a recent change that increased stage cost was approved by the project manager and later reversed by the Board, causing rework and delays.
What is the most likely underlying cause in PRINCE2 terms?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: PRINCE2 expects change approval to be delegated appropriately: the project manager can approve within agreed limits, a change authority can approve defined types/levels of change, and the Project Board approves changes beyond delegated authority. The inconsistent escalation and the project manager approving a cost-increasing change indicate missing or unclear approval limits and roles in change control.
In PRINCE2, issues and change requests are controlled through a defined decision-making structure. The project manager can only approve changes within the delegated authority and tolerances set by the Project Board (often documented in the change control approach and reflected in stage/project tolerances). A change authority may be appointed to take decisions for a defined scope of changes.
In the scenario, small changes are unnecessarily sent to the Project Board, and a cost-increasing change was approved by the project manager and then overturned. That pattern points to unclear or missing definitions of:
When these are not explicit, decisions become inconsistent, slow, and prone to rework when escalated later.
Without clear delegated authority and limits, minor changes are over-escalated and larger changes may be approved at the wrong level, leading to reversals and rework.
Topic: PRINCE2 Principles
A project is delivering a new online payments service. In the current stage, the same issue has occurred three times: late discovery of interface defects between the internal platform and the external gateway supplier, causing rework.
The stage is forecast to finish within time and cost tolerances, so no exception is needed. The next stage will involve more supplier integrations, and the Business Case is tight.
What should the project manager do to apply the ‘learn from experience’ principle when preparing for the next stage?
Best answer: A
What this tests: PRINCE2 Principles
Explanation: The ‘learn from experience’ principle means identifying recurring problems as lessons and applying them to improve future performance. Here, the stage remains within tolerance, so the right optimization is to incorporate preventive actions into the next Stage Plan (and relevant management approaches) to reduce risk and protect benefits while maintaining governance.
PRINCE2 expects teams to proactively learn from experience: seek, record, and act on lessons so recurring issues are less likely to repeat. In this scenario the defects are a clear pattern, and the next stage increases exposure because it adds more integrations.
The project manager should capture the insight (e.g., earlier interface validation, stronger supplier coordination, tighter acceptance/quality criteria) and apply it when creating the next Stage Plan and updating relevant approaches (such as Quality, Risk, and Communication). Because forecasts remain within tolerances, this is handled through normal stage planning and approval at the end-stage boundary, rather than exception escalation.
The key takeaway is to improve the next stage based on evidence, not to overreact or bypass change control.
Recurring issues should be turned into lessons and used to adjust plans and approaches for the next stage without unnecessary escalation.
Topic: PRINCE2 Practices
During the initiation stage of a customer-portal project, the project manager notices repeated delays because several team members are unsure who has decision-making authority, what each person is responsible for, and who they should consult or report to.
In PRINCE2 terms, what is the most appropriate next step to establish effective working relationships?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: PRINCE2 role descriptions are used to remove ambiguity about who does what and how people interact. They should set out responsibilities, authority (including decision rights), and key working interfaces such as reporting and consultation lines. Agreeing these role descriptions is the best next step to enable effective working relationships in the project management team.
In the Organizing practice, PRINCE2 uses role descriptions to make the project’s working relationships clear and workable. In this scenario the problem is unclear responsibilities and authority, so the next step is to produce and agree role descriptions for the relevant roles.
A good role description typically covers:
Communication planning can help once roles are clear, but it does not replace agreeing who is accountable and how decisions are made.
Role descriptions clarify responsibilities, authority, and key interfaces so people know how to work together effectively.
Topic: PRINCE2 Practices
Which PRINCE2 management product describes how and when the project’s expected benefits will be measured and reviewed, helping ensure plans and product descriptions can be traced back to business objectives?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: The benefits management approach explains how the project’s benefits will be realized, measured, and reviewed over time. By setting out benefit measures and review points, it provides a clear line of sight from what is planned and specified (including product descriptions) to the business objectives those products are meant to support.
In PRINCE2, the benefits management approach is the management product that defines the benefit profiles, how benefits will be measured, who is responsible, and when reviews will occur (often extending beyond project closure). This information supports traceability: plans can be built around the work needed to enable those benefits, and product descriptions (including acceptance criteria and quality tolerances) can be written to confirm the outputs and outcomes required to achieve the intended business objectives. The Business Case justifies why the project should proceed and is kept under review, but the detailed “how/when we will measure benefits” is set out in the benefits management approach.
It defines how benefits will be identified, measured, and reviewed so delivery work can be linked back to the intended business outcomes.
Topic: PRINCE2 Processes
During a management stage, the project manager needs regular, time-driven updates from a team manager on work package progress (completed work, issues, and forecast remaining effort) so the project manager can decide whether to take corrective action within stage tolerances.
Which PRINCE2 management product is used for this purpose?
Best answer: D
What this tests: PRINCE2 Processes
Explanation: Within Controlling a Stage, progress is monitored through regular reports from those doing the work. A Checkpoint Report is produced by the team manager at agreed intervals to inform the project manager about work package status, enabling timely corrective action while staying within tolerances.
In the Controlling a Stage (CS) process, the project manager maintains control by monitoring work package progress against the Stage Plan and taking corrective action when needed. The primary routine input from delivery teams is the Checkpoint Report, created by the team manager as agreed in the Work Package. This report gives the project manager visibility of actual progress, issues, and forecasts so the project manager can intervene early.
If forecasts show tolerances will be exceeded, routine monitoring is no longer enough and escalation is required (via an Exception Report), whereas Highlight Reports are the project manager’s summary updates to the project board.
Checkpoint Reports provide the project manager with regular progress updates from the team manager to support monitoring and corrective action within a stage.
Topic: People in Successful Projects
A stakeholder raises a concern that could cause the current stage to exceed its agreed tolerance.
Which PRINCE2 management product should the project manager use to escalate this to the project board, and what should it include?
Best answer: B
What this tests: People in Successful Projects
Explanation: A stakeholder concern that may drive a stage beyond tolerance is treated as an issue requiring escalation. In PRINCE2, the project manager escalates such issues to the project board using an Issue Report. This report provides enough information for a decision, including the likely impacts and available response options.
Stakeholder concerns are captured and assessed as issues when they require action or a decision. When an issue may cause a stage or project to exceed agreed tolerances, the project manager must escalate to the project board rather than manage it solely within day-to-day control.
The standard way to escalate is an Issue Report, which provides decision-making information, typically:
Status-style reports are for routine progress communication, not for requesting decisions on significant stakeholder concerns.
An Issue Report is used to escalate an issue needing project board attention and should summarize impacts and decision options with a recommendation.
Topic: PRINCE2 Principles
A project manager has tailored PRINCE2 by removing routine reporting products, relying on informal verbal updates instead. Midway through a management stage, the project board says this undermines governance because they have no consistent evidence of progress against the Stage Plan.
Which management product should be reinstated to validate stage-level progress for the project board?
Best answer: B
What this tests: PRINCE2 Principles
Explanation: Removing routine reporting is poor tailoring because it removes an essential control for monitoring and directing. To validate progress at the project board level during a stage, PRINCE2 uses a regular, summarized report from the project manager. Reinstating this product restores consistent evidence of status against the Stage Plan.
Tailoring must not remove PRINCE2’s minimum requirements for effective control, including clear roles and appropriate controls for directing and managing by stages. For board-level oversight during a management stage, PRINCE2 expects the project manager to provide periodic, summarized progress information against the Stage Plan so the board can confirm the project remains within tolerances and justified.
A Highlight Report is designed for this purpose and reporting level. A Checkpoint Report supports day-to-day control between the team manager and project manager, while an End Stage Report is produced at the end of a stage, not mid-stage. The key takeaway is to reinstate the reporting product that matches the governance level needing evidence.
A Highlight Report provides regular, stage-level progress information from the project manager to the project board.
Topic: PRINCE2 Practices
A project is building a new customer self-service portal. During quality inspections, the same defects are found repeatedly in a key module, causing rework and schedule slippage. The project manager notes that defects are discussed in meetings and email, but there are no corresponding entries in any formal log and no agreed corrective actions are being tracked.
In PRINCE2 terms, what is the most likely underlying cause?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: Repeated defects and rework, combined with defects being handled only via informal discussions, indicates weak issue control. In PRINCE2, defects and other nonconformance are treated as issues and should be formally recorded and managed so that corrective actions, ownership, and decisions are visible and controlled.
A product defect/nonconformance discovered through quality control is a type of issue (a problem/concern) in PRINCE2. If defects are only discussed in meetings or email, they are not under control: you cannot track status, assign ownership, analyze trends, or ensure decisions and actions are taken.
Proper control is to record defects as issues (typically in the Issue Register), then manage them through the issue management procedure (assess impact, decide response, assign actions, and monitor to closure). The Quality Register supports planning and recording quality activities, but the defect itself needs issue control so the rework and corrective actions are managed and visible.
Reporting frequency or missing tolerances may affect oversight, but they do not explain why defects recur without tracked corrective action.
In PRINCE2, product defects/nonconformance should be captured and managed through issue control (e.g., logged in the Issue Register) so actions and decisions are tracked.
Topic: PRINCE2 Practices
A project manager is using product-based planning and has defined Product Descriptions with quality criteria for each specialist product. The Project Board asks for evidence that the products completed so far have been quality-checked and accepted against those criteria.
Which management product should the project manager provide?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: Product-based planning keeps attention on defined products and their acceptance/quality criteria. The best validation that completed products have actually been checked and accepted is the record of quality activities and outcomes for those products. The Quality Register provides that evidence at product level.
Product-based planning supports a focus on products by defining what must be delivered (via products, their relationships, and Product Descriptions) and by enabling progress to be tracked in terms of product completion and acceptance.
To validate that this focus is being maintained, you need objective evidence that the completed products have met their defined quality criteria. The Quality Register is the management product that logs, for each product, the quality activities (e.g., reviews, tests) and their results, including whether the product was accepted or required rework. Reports like Highlight Reports and End Stage Reports summarize status for governance, but they are not the primary evidence of product acceptance.
It records the planned and completed quality activities and results for each product, providing evidence of acceptance against defined criteria.
Topic: PRINCE2 Practices
During Stage 2 of a customer-portal project, the Project Board set the stage tolerances at time: +5 days and cost: +$20,000.
Halfway through the stage, the Project Manager forecasts that a supplier delay will make the stage finish 8 days late, while cost will still be within tolerance.
What is the best action, in line with PRINCE2 escalation and governance, and why?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: An Exception Plan is required when a plan-level tolerance is forecast to be exceeded and the deviation cannot be handled within agreed tolerances. Here, the Stage Plan time tolerance is +5 days but the forecast is +8 days, so the Project Manager must escalate. The Project Board then considers options and, if it decides to continue, approves an Exception Plan to replace the Stage Plan.
In PRINCE2, tolerances define the delegated authority for the Project Manager to control the work without referring decisions upward. When it is forecast that a plan (such as a Stage Plan) will exceed an agreed tolerance for time, cost, scope, quality, risk, or benefits, the Project Manager must escalate to the next management level.
In this scenario, the stage is forecast to be 8 days late against a +5 day stage tolerance, so it is an exception at stage level. The correct governance response is to raise an Exception Report to the Project Board and prepare an Exception Plan (once requested/required) that replaces the affected plan and provides a controlled way forward for the Board’s decision. Even if overall project tolerances might still be met, a breach of stage tolerances still requires escalation.
A forecast breach of stage tolerance requires escalation and an Exception Plan to replace the Stage Plan once the Project Board decides how to proceed.
Topic: PRINCE2 Processes
A project mandate has been issued to replace a finance system. The organization has not yet authorized initiation, and the Project Board wants enough information to decide whether to allow the project to enter the Initiating a Project process.
Which management product is typically produced by the end of Starting up a Project to support that decision?
Best answer: B
What this tests: PRINCE2 Processes
Explanation: Starting up a Project aims to confirm that the project is viable and worthwhile before significant effort is spent on initiation. A key outcome is a Project Brief, which provides the Project Board with enough information (including the initial project management team structure and an outline Business Case) to decide whether to authorize initiation.
Starting up a Project is the pre-initiation process used to ensure there is a sound basis to invest in Initiating a Project. Typical outcomes include appointing the Executive and Project Manager, designing and appointing the project management team, selecting the project approach, preparing an outline Business Case, and capturing lessons.
These are brought together in the Project Brief (along with the Initiation Stage Plan) so the Project Board can decide whether to authorize the initiation stage. By contrast, the PID is created during Initiating a Project, once initiation has been authorized.
The Project Brief is produced in Starting up a Project to provide sufficient definition for the Project Board to decide whether to initiate.
Topic: People in Successful Projects
A government department and an external supplier are delivering a shared digital service. Over the last month, development teams have completed work packages but then had to redo them because different groups gave conflicting approvals. Some decisions are made in email threads without clear authority, and the project manager is unsure who can approve changes that affect both organizations.
What is the most likely underlying cause in PRINCE2 terms?
Best answer: A
What this tests: People in Successful Projects
Explanation: The key symptom is conflicting approvals from multiple groups, with no clear authority for change approval across two organizations. In PRINCE2, this points to unclear roles, responsibilities, and decision rights (e.g., who can approve what, and through which route), rather than a delivery performance or reporting frequency problem.
The scenario shows repeated rework because different parties give approvals, and the project manager cannot identify who is authorized to approve changes affecting both organizations. In PRINCE2, this is primarily a people-and-governance problem: decision rights and responsibilities are not clear across organizational boundaries.
The practical PRINCE2 implication is that authority should be made explicit (who decides, who advises, who is informed), and the approval route for changes should be clear so that teams receive a single, authoritative direction. Without this clarity, informal channels (like email threads) create conflicting direction, delays, and rework.
Reporting cadence or late delivery may be present, but they do not explain contradictory approvals and uncertain change authority.
Decision-making authority and approval paths are not defined, causing conflicting approvals and rework.
Topic: Project and PRINCE2 Key Concepts
A city council is running a PRINCE2 project to install EV charging points. The Business Case depends on meeting a sustainability target (recycled materials where feasible). Delivery is in waves (iterative roll-out). The supplier is on a fixed-price contract that allows component substitution with buyer approval.
During the current stage, the supplier proposes switching to recycled-aluminium enclosures. Impact assessment shows +4 days and +$10,000, with no change to required scope or acceptance criteria. Stage tolerances are ±1 week time and ±$15,000 cost.
What should the project manager do to best balance objectives while following PRINCE2 governance?
Best answer: D
What this tests: Project and PRINCE2 Key Concepts
Explanation: The project context makes the sustainability target a key driver of benefits, and the commercial arrangement requires formal buyer approval of substitutions. Because the assessed impacts remain within delegated stage tolerances, the change can be handled through normal change control and communicated via regular reporting, rather than escalating as an exception.
PRINCE2 is applied to fit the project context, including sustainability goals, delivery approach, and commercial constraints. Here, the sustainability target is part of the justification for the project, so a change that improves sustainable outcomes is desirable if it remains viable.
Because the fixed-price contract allows substitutions only with buyer approval, the project manager should handle the proposal through change control (capture and assess the issue, decide within delegated authority, and update baselines as needed). The forecast impacts (+4 days, +$10,000) are within stage tolerances (±1 week, ±$15,000), so escalation via exception is not required; progress and the approved change can be communicated in the next Highlight Report. The key takeaway is to optimize benefits (including sustainability) while staying within tolerances and respecting governance and contractual controls.
It supports sustainability benefits and stays within stage tolerances, so it can be managed via change control without an exception escalation.
Topic: PRINCE2 Practices
An organization is starting two projects:
They plan to use a simplified governance structure for Project A (some roles combined, minimal reporting) but a more formal structure for Project B (separate Project Board roles and dedicated assurance).
Which PRINCE2 principle is this approach an example of?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: PRINCE2 expects governance to be proportionate to the project’s scale and risk. Using a lighter structure for a small, low-risk project and a stronger structure for a large, high-risk project is a direct application of the tailoring principle. Tailoring can include combining roles, adjusting assurance, and changing reporting frequency.
The principle “Tailor to suit the project” means PRINCE2 is applied in a way that is appropriate to the project’s context, including its size, complexity, risk, and importance. Governance is one of the key areas to tailor: for a small/low-risk project it can be efficient to combine roles (while still covering required accountabilities) and keep reporting lightweight, whereas a large/high-risk project typically needs clearer separation of responsibilities, more formal controls, and stronger assurance.
The key takeaway is that the governance structure should be designed to be fit for purpose rather than identical across all projects.
It adapts the governance structure to match the project’s size, complexity, and risk.
Topic: PRINCE2 Practices
A company is starting two PRINCE2 projects at the same time:
The sponsor asks the project manager to propose the governance structure and key role appointments.
What is the BEST next action?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: PRINCE2 governance is tailored to the project’s size, complexity, and risk. A small, low-risk project can combine Project Board roles to keep overhead proportionate. A large, high-risk project needs clear separation of Executive, Senior User, and Senior Supplier, plus appropriate assurance, to provide effective direction and control within tight tolerances.
In PRINCE2, the Organizing practice sets up a governance structure that enables effective decision-making, direction, and accountability, and it should be tailored to suit the project.
For a small/low-risk project, it is usually appropriate to keep governance lightweight by combining roles (for example, one person covering more than one Project Board role) while still maintaining business, user, and supplier interests.
For a large/high-risk project with multiple suppliers and tight tolerances, a clearly defined Project Board with separate Executive, Senior User, and Senior Supplier roles (and appropriate project assurance) is needed to provide robust oversight and timely decisions.
The key takeaway is to reduce overhead only where risk and complexity are low, not by removing essential governance.
PRINCE2 expects governance to be tailored: keep roles combined for small/low-risk work, but use a fully defined board and assurance for large/high-risk delivery.
Topic: PRINCE2 Practices
Midway through a delivery stage, the project manager has been directing an in-house engineering team day to day. Because internal capacity is now unavailable, the executive approves outsourcing the remaining component build to a specialist supplier, who will provide a team lead.
What is the most likely near-term impact on team structure and responsibilities for managing this stage?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: Outsourcing changes how work is directed and controlled because the project manager cannot manage supplier staff directly. The supplier’s team lead will take Team Manager responsibilities for producing specialist products. The project manager will control progress through Work Packages, agreed reporting, and formal handover/acceptance of delivered products.
The delivery approach influences team structure and responsibilities. When work is delivered in-house, the project manager may be closer to the team and can use internal line-management arrangements (while still controlling via Work Packages in PRINCE2). When delivery is outsourced, the supplier side normally provides a Team Manager (or equivalent) responsible for creating the agreed products, managing the supplier resources, and reporting progress.
In the near term for stage control, the project manager needs to:
This is an immediate governance and responsibility shift, not an automatic change to tolerances or who accepts final outputs.
With outsourced delivery, the supplier’s team lead typically acts as Team Manager and the project manager controls work through authorized Work Packages and product acceptance.
Topic: People in Successful Projects
A PRINCE2 project is delivering a new customer portal. The development work is being done by an external partner.
Mid-stage, the partner starts building extra features that were not agreed, and the project manager is concerned this will affect time and cost tolerances. The current Work Package for the partner is vague and does not include clear acceptance criteria or reporting arrangements.
What is the BEST next action?
Best answer: A
What this tests: People in Successful Projects
Explanation: When working across organizational boundaries, the project manager should align the external partner to the project’s agreed products and controls. A clear Work Package is the mechanism to define what is to be delivered, how it will be accepted, and how progress will be reported. Re-authorizing it sets shared expectations without bypassing governance.
Leading across organizational boundaries in PRINCE2 means building a cooperative working relationship while keeping clear accountabilities and controls between customer and supplier. In this scenario, the problem is not only the extra scope, but that the partner’s Work Package is too vague to manage delivery, acceptance, and communication.
The best next step is to re-baseline the supplier interface at working level by:
Escalation is appropriate only once the impact is understood and forecast to exceed agreed tolerances; clear supplier controls come first.
Leading across the boundary means establishing shared expectations and controls with the supplier via a clear Work Package, including acceptance criteria and reporting.
Topic: PRINCE2 Practices
A project to implement a new CRM system was approved last month after an initial investment appraisal supported the Business Case. The project is now in the middle of stage 1 delivery, and the project manager learns that supplier costs will be 15% higher than forecast, reducing expected return.
What is the MOST PRINCE2-aligned action to support continued business justification?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: The project has already been authorized, so the investment decision is not being made for the first time. In PRINCE2, when new information changes the cost/benefit forecast during delivery, the Business Case needs to be updated and reviewed so the Project Board can confirm that the project remains justified.
Initial investment appraisal is the up-front evaluation used to decide whether to commit to the project (or authorize initiation) based on forecast costs, benefits, and risks. Once the project is underway, PRINCE2 requires ongoing maintenance of the Business Case so that continued business justification can be confirmed whenever forecasts change and at key decision points (notably stage boundaries).
Here, the project is mid-stage and new information changes the expected return, so the appropriate response is to update the Business Case information and escalate it for governance review (typically to the Project Board, with the Executive accountable for the Business Case). The key takeaway is that appraisal supports the initial go/no-go decision, while maintenance supports continued justification during delivery.
During delivery, PRINCE2 requires ongoing Business Case maintenance and review to confirm continued justification.
Topic: PRINCE2 Practices
A project is approaching the end of stage 2. Several issues were managed during the stage and the schedule is now forecast to slip, but the impact on expected benefits has not yet been confirmed. The Project Board asks whether it should authorize stage 3 or change direction.
Before it can make this decision, what is the FIRST thing that must be verified using (or as input to) an End Stage Report?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: The End Stage Report is used by the Project Board at a stage boundary to decide whether to authorize the next stage, request an exception, or stop the project. That decision is driven first by whether the project remains justified, based on the updated Business Case (including revised costs, timescales, risks, and expected benefits). If justification is not confirmed, continuing is not appropriate.
The purpose of an End Stage Report is to give the Project Board a clear view of stage performance and an updated forecast so it can decide what to do next at the stage boundary (authorize the next stage, request corrective action/exception, or stop).
To support a decision to continue or change direction, the critical check is continued business justification. In practice, this means the End Stage Report (and associated updates) should confirm:
Even if the stage was well controlled, a revised forecast that undermines the Business Case is a strong reason for the Project Board to change direction rather than authorize the next stage.
An End Stage Report supports the Project Board’s continuation decision by confirming continued business justification using an updated Business Case.
Topic: PRINCE2 Principles
A project to implement a digital case-management system has an approved Project Plan and is currently in Stage 2. The Stage Plan for Stage 2 has tolerances of +2 weeks and +10% cost. The project manager forecasts a supplier delay that will add 4 weeks and 12% cost to Stage 2, but the Business Case remains viable.
What is the BEST action to balance control and business justification while following PRINCE2 escalation rules?
Best answer: D
What this tests: PRINCE2 Principles
Explanation: The forecast shows Stage 2 will exceed its agreed tolerances, so the project manager no longer has authority to proceed under the current Stage Plan. PRINCE2 requires escalation to the project board and the production of an Exception Plan for the level of plan being exceeded. If approved, the Exception Plan replaces the Stage Plan to regain control while maintaining a viable Business Case.
In PRINCE2, the Project Plan provides the overall baseline for the project, and each Stage Plan provides the detailed forecast and control baseline for a management stage. Tolerances are set for each level of plan; when a deviation is forecast to exceed the tolerance at that level, the project manager must escalate.
Here, the forecast exceeds Stage 2 tolerances, so the correct response is to raise an exception to the project board and prepare an Exception Plan for Stage 2. If the project board approves it, the Exception Plan replaces the current Stage Plan, re-establishing an approved baseline for controlling the rest of the stage. Updating plans without escalation would break governance even if the Business Case remains justified.
A forecast breach of stage tolerances must be escalated, with an Exception Plan produced to replace the affected Stage Plan if approved.
Topic: PRINCE2 Practices
A project is in Initiating a Project. The Project Manager is drafting the PID, but stakeholders are asking:
What is the BEST next action?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: In PRINCE2, the Quality Management Approach is the management product used to explain how quality will be planned and controlled on the project. It should cover the applicable standards, the methods/techniques to be used, who is responsible for quality activities (including approvals), and what quality records will be maintained. Creating this gives stakeholders clear, agreed information for inclusion in the PID.
The core control here is to define the project’s approach to quality before delivery work proceeds. PRINCE2 captures this in the Quality Management Approach (part of the PID), which explains how the project will ensure products are fit for purpose.
A good Quality Management Approach should include:
Starting reviews or delegating decisions without this agreed approach risks inconsistent expectations and weak evidence. The key takeaway is to define and document the approach to quality as part of initiation governance.
The Quality Management Approach defines the project’s quality standards, techniques, roles/responsibilities, and required quality records.
Topic: PRINCE2 Processes
During Starting up a Project (SU), the project manager has received a project mandate from corporate management.
Which management product is created next to give the Project Board enough information to decide whether to authorize project initiation?
Best answer: B
What this tests: PRINCE2 Processes
Explanation: In PRINCE2, the project mandate is an external trigger that authorizes Starting up a Project. During SU, the project manager creates the Project Brief (including elements like the outline Business Case and project approach) so the Project Board can decide whether it is worthwhile and viable to authorize initiation.
The project mandate is provided by corporate, programme management, or the customer and is the trigger to start SU; it expresses the initial idea or need at a high level. In SU, the project manager uses that mandate to prepare the Project Brief, which consolidates enough definition to enable the Project Board to decide whether to authorize initiation (and therefore proceed to Initiating a Project).
The Project Brief typically brings together:
The PID is produced during Initiating a Project, not during SU, and the Business Case is developed in more detail during initiation rather than being the single “go/no-go for initiation” product on its own.
The Project Brief is produced in SU from the project mandate to support the Project Board’s decision to authorize initiation.
Topic: PRINCE2 Practices
A project is delivering a new digital customer portal. The current management stage is about to finish and performance is within tolerance. The project manager has produced the next Stage Plan (with updated schedule, costs, and resource needs) so that work can continue.
In PRINCE2 terms, what is the correct next step to obtain plan approval and support the governance decision to continue?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: Stage Plans are approved by the Project Board as part of their control over stage boundaries. Presenting the next Stage Plan at the end of a stage enables the Project Board to make a governance decision: whether to authorize the next stage, request changes, or stop the project. This is done through Managing a Stage Boundary and a request to proceed.
In PRINCE2, plan approval is a governance control: the approving authority uses the plan to decide whether work is justified and controlled before authorizing commitment of resources. At the end of a management stage, the project manager uses the Managing a Stage Boundary process to prepare information for the Project Board, including the next Stage Plan (and typically an End Stage Report). The Project Board reviews and approves the next Stage Plan as part of the decision to authorize the next stage, ensuring continued alignment with the Business Case and agreed tolerances.
Key takeaway: approval of the next Stage Plan is not a team-level action; it is a Project Board authorization decision at a stage boundary.
The Project Board approves the next Stage Plan to decide whether to authorize the next management stage.
Topic: PRINCE2 Practices
A project has identified a risk: “The new customer portal may fail security accreditation, delaying go-live.”
The agreed response is to run an additional independent penetration test and fix any critical findings. The Security Lead will arrange and perform this work.
Which option correctly describes the PRINCE2 responsibilities of the risk owner and the risk actionee for this risk?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: In PRINCE2, the risk owner is accountable for the risk’s management: monitoring it, ensuring responses are planned, and reporting status. The risk actionee is responsible for carrying out specific response actions. Because the Security Lead will perform the penetration test work, they fit the risk actionee role, while someone else should own and track the risk.
PRINCE2 separates accountability for managing a risk from responsibility for executing the response. The risk owner is assigned to a specific risk and is accountable for controlling it: keeping it under review, ensuring appropriate responses are defined and implemented, and escalating/reporting if needed. The risk actionee is assigned to carry out one or more agreed risk response actions.
In this scenario, running the penetration test and fixing findings are response actions, so the Security Lead is best placed as the risk actionee. A Business Change Manager (or another appropriate role) can be the risk owner, accountable for monitoring whether the risk is reducing and ensuring the response is completed. The key takeaway is: owner manages the risk; actionee executes the actions.
The risk owner is accountable for managing and monitoring the risk, while the risk actionee carries out the agreed risk response actions.
Topic: PRINCE2 Practices
Midway through a delivery stage, new market data indicates that ongoing operating costs for the product will be 30% higher than assumed in the approved Business Case. This may reduce forecast benefits, but the impact has not yet been analysed.
As project manager, what is the BEST next action to keep the Business Case current?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: PRINCE2 requires the Business Case to be kept under review so decisions are based on current forecasts. The project manager should first analyse the impact of the changed assumption and update the Business Case accordingly. If the updated forecast indicates that continued business justification may be at risk, the change should be escalated through the issue and exception controls for a Project Board decision.
Keeping the Business Case current means updating it when key assumptions, costs, timescales, or benefits forecasts change, so governance decisions reflect the latest viability.
In this situation, the operating cost assumption has changed but the effect on benefits and overall value is not yet known. The best next step is therefore to:
Deferring the update or making unapproved corrective changes risks decisions being made on an out-of-date justification.
The project manager should analyse and update forecasts to keep the Business Case current, escalating via an issue if viability may be affected.
Topic: PRINCE2 Practices
A project is delivering a customer-facing mobile app. During a review, the Senior User says the app must meet stricter accessibility and usability expectations before it can be accepted. The Senior Supplier says those expectations were not included in the agreed build specification and will increase effort.
As project manager, what should you verify first before deciding how to handle this conflict?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: In PRINCE2, quality conflicts should be resolved by referring first to what was agreed as acceptable. The baselined acceptance criteria and quality tolerances (in the relevant Product Description and Project/Product acceptance definitions) provide the authoritative basis to decide whether the Senior User’s expectation is already required or represents a change to be assessed and controlled.
This is a Quality practice question about conflicting expectations between user and supplier interests. Before deciding what to do, the project manager should confirm the agreed definition of “acceptable” for the product: the baselined acceptance criteria and quality tolerances captured in the relevant Product Description(s) (and, at project level, the project product description/acceptance definition). If the stricter accessibility/usability expectations are already in the baselined criteria, the supplier must meet them (and the plan may need updating). If they are not, the request is a change to be evaluated through change control for impact on time, cost, scope, and benefits, and then approved or rejected by the appropriate authority.
The key takeaway is to anchor decisions in agreed acceptance criteria before considering impacts such as schedule, risk, or viability.
The agreed acceptance criteria/quality tolerances define what “fit for purpose” means and whether a change is required to reconcile user and supplier expectations.
Topic: People in Successful Projects
A project is delivering a new HR system across several departments and an external payroll provider. In the last month, draft release dates and policy changes were shared with staff and the supplier before the Executive approved them, causing confusion, complaints, and rework to “walk back” messages. The project manager says it is unclear who is allowed to communicate what, to whom, and when.
What is the MOST likely underlying cause in PRINCE2 terms?
Best answer: A
What this tests: People in Successful Projects
Explanation: The symptoms point to uncontrolled and inconsistent stakeholder messaging: sensitive information is being released without the right approvals and at the wrong time. In PRINCE2, this is prevented by defining and using a Communication Management Approach that sets who communicates, what, when, to which audiences, and through what approval routes.
Sensitive communications that need careful timing, audiences, or approvals should be governed through the project’s Communication Management Approach (often aligned with stakeholder engagement needs). In this scenario, messages about release dates and policy changes are being issued before Executive approval, and the project manager cannot state who is authorized to communicate what and when. That indicates the communications approach is missing, not agreed, or not being followed.
A fit-for-purpose Communication Management Approach typically clarifies:
Reporting products like Checkpoint Reports support control, but they do not define external-facing communication authority and approvals.
PRINCE2 requires an agreed approach defining audiences, timing, and approvals so sensitive messages are controlled and consistent.
Topic: PRINCE2 Practices
At the end of Stage 2 of a customer self-service portal project, new data shows operating costs will increase and some benefits will be delayed by 3 months. The Executive is accountable for ensuring there is continued business justification before authorizing Stage 3.
Which management product provides the best evidence to validate whether the project should continue?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: The Executive must be able to confirm that the Business Case remains viable when deciding whether to continue. At a stage boundary, the product designed to support this decision is the End Stage Report, which consolidates stage performance and provides the information needed (including updated forecasts/Business Case) to assess continued justification.
The Executive is accountable for ensuring continued business justification throughout the project, particularly when the Project Board makes a decision to authorize the next stage. At a stage boundary, the key validation point is whether the updated Business Case still justifies further investment given changes to costs, timescales, and expected benefits. The End Stage Report is produced to support this decision by summarizing how the stage performed against the plan and providing the information needed to assess whether it remains worthwhile to proceed. A Highlight Report is regular progress reporting, but it is not the primary product for the stage boundary “continue or stop” decision.
It supports the Project Board’s stage boundary decision by summarizing stage performance and presenting the updated Business Case/forecasts for continued justification.
Topic: PRINCE2 Processes
Midway through a management stage, the project manager needs objective evidence of how a team is progressing against an agreed Work Package so that any required corrective action can be taken within stage tolerances.
Which management product provides this evidence?
Best answer: D
What this tests: PRINCE2 Processes
Explanation: During a stage, progress is monitored by comparing actuals to the Work Packages and Stage Plan, using regular reports from the teams doing the work. The Checkpoint Report is the standard management product used by a team to report progress to the project manager, enabling timely corrective action within tolerances.
In Controlling a Stage (CS), the project manager maintains control by monitoring progress and taking corrective action as needed. The most direct evidence of progress while work is being carried out comes from regular reporting by the team responsible for a Work Package. A Checkpoint Report is produced by the Team Manager (or the person leading the work) and sent to the project manager at an agreed frequency; it reports progress, issues, and forecasts for the Work Package, allowing the project manager to adjust assignments, re-plan within the stage, or escalate if tolerances are forecast to be exceeded. Highlight Reports are aimed at the Project Board, and end-of-stage reporting happens later.
It provides regular, team-level progress information against a Work Package so the project manager can monitor and take corrective action.
Topic: PRINCE2 Practices
A company is starting a project to introduce a new customer self-service portal. The Project Board is being designed, and the project manager wants to keep governance “light”.
Which statement is INCORRECT about why the three project interests (business, user, supplier) must be represented on the Project Board?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: PRINCE2 requires the Project Board to include representation of the business, user, and supplier interests so that decisions balance value, need, and delivery feasibility. Each interest brings a different perspective and authority, reducing bias and ensuring decisions are viable, desirable, and achievable. Treating user or supplier input as “informal” undermines governance and decision-making.
In PRINCE2, the Project Board provides unified direction and decision-making, and it must represent three distinct project interests:
These interests are intentionally separated so that trade-offs (for example, scope vs. cost vs. quality) are made with the right authority and a balanced view, rather than being dominated by a single perspective. A project manager supports governance but does not replace Project Board representation of these interests.
PRINCE2 requires business, user, and supplier interests to be represented for balanced decisions and effective governance.
Topic: PRINCE2 Practices
A project manager is delegating delivery of an integration module to a supplier team led by a team manager. The project manager wants the team to work autonomously day to day, but still keep clear control, reporting, and accountability for what will be delivered.
What should the project manager do?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: In PRINCE2, delegation to a delivery team is enabled through a Work Package. It authorizes the work and records what products are required, the constraints/tolerances, quality expectations, and how progress will be reported back. This lets the team manager manage the work while the project manager retains control and accountability.
A Work Package is the key mechanism for delegating work from the project manager to a team manager while maintaining control. It is a formal authorization and agreement that defines the scope of the work in product terms, the constraints (including any tolerances), required quality criteria/methods, and the frequency and format of progress reporting (typically via Checkpoint Reports).
By agreeing and issuing a Work Package, the team manager can manage delivery day to day, while the project manager can monitor progress, ensure products meet acceptance/quality expectations, and take action or escalate if delivery is forecast to exceed agreed tolerances.
A Work Package is the formal agreement that delegates work to a team manager while defining acceptance, constraints/tolerances, and progress reporting for control.
Topic: People in Successful Projects
A project manager has agreed a Work Package with a team manager to develop a set of digital training materials. The Work Package defines required products, quality criteria, and how often progress information must be provided.
During delivery, the project manager wants evidence that the Work Package is on track and that progress is being monitored at the team level. Which management product is the BEST evidence?
Best answer: B
What this tests: People in Successful Projects
Explanation: Work Packages support collaboration by creating a clear agreement between the project manager and team manager, including products, quality expectations, and reporting frequency. The team manager then provides progress information back to the project manager using regular reports against that Work Package. The product that evidences this ongoing team-level monitoring and progress is the Checkpoint Report.
In PRINCE2, a Work Package is the formal mechanism that enables collaboration between the project manager and team manager: it defines what must be delivered, how it will be checked (quality criteria/methods), constraints such as tolerances, and the reporting requirements. Once the Work Package is authorized, the team manager manages the work and provides the agreed progress updates to the project manager.
The management product used for these regular updates is the Checkpoint Report, which reports actual progress (and any forecast issues) for the Work Package. This provides the project manager with evidence that delivery is being controlled at the team level and supports effective escalation if tolerances are at risk. By contrast, higher-level or end-of-stage reporting does not validate day-to-day Work Package progress.
A Checkpoint Report is the team manager’s regular progress report against an agreed Work Package.
Topic: PRINCE2 Practices
During a delivery stage, two similar issues occurred: software changes were implemented without peer review, causing rework. The project manager records this as a lesson and immediately updates the Work Package instructions so peer review sign-off is mandatory and must be confirmed in Checkpoint Reports. The stage is still within time and cost tolerances.
What is the most likely near-term impact of this decision?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: Using lessons from issues should result in improved controls to prevent recurrence. Updating the Work Package and requiring confirmation in Checkpoint Reports strengthens stage-level monitoring immediately. Because the stage remains within tolerances, the main near-term effect is additional control effort rather than formal escalation or replanning.
In PRINCE2, issues can generate lessons that are used to improve how the project is controlled and to prevent the same problem happening again. Applying the lesson immediately by tightening Work Package instructions and asking for evidence via Checkpoint Reports strengthens day-to-day stage control (work is done with clearer constraints and is monitored more closely).
Because the stem states the stage is still within time and cost tolerances, introducing an additional review step is handled by the project manager and team management within the existing stage. Escalation to the Project Board (exception) is only needed if forecasts show tolerances will be exceeded, and updating the Business Case is only needed if viability is affected.
Adding a mandatory peer-review control affects near-term delivery effort but can be absorbed within stage tolerances without escalation.
Topic: People in Successful Projects
A government department (customer) is running a PRINCE2 project to implement a new case-management system. An external supplier will build and host the solution, and a systems integrator will manage several subcontractors.
During delivery, the supplier proposes a design change that could affect data residency and user acceptance. The project manager is unsure whether to ask the supplier to decide, or to escalate for approval.
What must be clarified first before deciding what to do?
Best answer: C
What this tests: People in Successful Projects
Explanation: When multiple organizations are involved, PRINCE2 separates governance (direction, approval, accountability) from delivery (building products). A design change with potential impacts on acceptance and compliance should be handled according to the project’s defined approval authority. The first step is to confirm who is empowered to make the decision and what authority has been delegated to suppliers or delivery teams.
This scenario is about distinguishing governance responsibilities from delivery responsibilities across organizational boundaries. In PRINCE2, governance decisions (such as approving changes that may affect the Business Case, acceptance, or constraints like data residency) are made by the project’s directing/approval authority (Project Board or a defined change authority), not by delivery organizations unless that authority has been explicitly delegated.
Before deciding whether to let the supplier proceed or to escalate, the project manager must confirm:
Delivery feasibility questions (capacity, sprint timing, subcontractor availability) are relevant only after the governance route for approval is clear.
Approval is a governance decision, so the project manager must first confirm where decision-making authority sits across the organizations.
Topic: PRINCE2 Practices
A project is selecting between two solution options for a new customer portal. Since initiation, a new data-residency regulation has been announced and its impact is uncertain; it could increase costs and delay benefits for one option. The Project Board asks for evidence that the preferred option is still justified and that the project remains viable before committing further funding.
Which management product should be used to validate this justification?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: PRINCE2 requires continued business justification, and risk and uncertainty must be reflected when comparing options and confirming viability. The management product that consolidates costs, benefits, timescales and the impact of risk/uncertainty on those forecasts is the Business Case. Updating it provides the Project Board with the basis to decide whether to proceed.
In PRINCE2, option selection and ongoing viability are assessed through the Business Case. When new risks or uncertainty emerge (for example, a regulatory change with unclear impact), the forecasts that underpin justification can change: costs may rise, benefits may reduce or be delayed, and delivery timescales may extend. The Project Board needs an updated view of these impacts to judge whether the preferred option still offers value and whether the project should continue.
The Risk Register supports this by capturing and tracking risks, but it does not, by itself, demonstrate that the overall investment case remains worthwhile. The key takeaway is: risks and uncertainty inform the decision, but the updated Business Case is what validates continued justification.
The Business Case is the source of truth for continued justification and should be updated to reflect how risk and uncertainty affect option selection and viability.
Topic: PRINCE2 Practices
A project manager needs a plan that sets out the products to be delivered, activities, resources, and timescales for the next management stage. It will be used as the baseline for monitoring progress and controlling work during that stage.
Which PRINCE2 plan type is being described?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: The Plans practice provides a basis for delivery and control by defining what will be delivered, how, by whom, and when, and then using that plan as a baseline to compare actual progress. A plan focused on a single management stage supports day-to-day stage control by the project manager. That description matches the purpose and horizon of a Stage Plan.
In PRINCE2, the Plans practice supports delivery and control by providing approved baselines for targets (products, timescales, costs, resources) and enabling progress to be monitored and corrective action to be taken when needed. A Stage Plan is the plan for one management stage and is used by the project manager to control work within that stage and to report progress against agreed targets. By contrast, a Project Plan is the high-level view for the whole project, a Team Plan is for a team’s work (often within a work package), and an Exception Plan replaces a plan when tolerances are forecast to be exceeded.
A Stage Plan is the detailed baseline used to manage, monitor, and control a single management stage.
Topic: PRINCE2 Practices
A project is repeatedly surprised by problems (a supplier delivery delay, a new data-privacy constraint, and an outage in a test environment). The team reacts each time with urgent fixes, but no risk owners are assigned, stakeholders say they are hearing about threats “for the first time,” and the Risk Register has not been updated since initiation.
In PRINCE2 terms, what is the most likely underlying cause?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: The symptoms point to reactive firefighting with no assigned risk ownership and no current Risk Register. In PRINCE2, that indicates the risk management procedure is not being completed: after identification, risks should be assessed, responses planned, actions implemented, and information communicated to stakeholders. The missing ownership and stale register are key clues.
PRINCE2’s risk management procedure is a set of steps to handle uncertainty proactively: identify risks, assess them (estimate and evaluate), plan responses, implement the agreed actions, and communicate (record and report) risk information. In the scenario, risks are emerging repeatedly but are handled ad hoc, with no risk owners and no updates to the Risk Register, so risk information is not being communicated or controlled. That combination most strongly indicates the procedure is not being followed beyond initial identification.
Key takeaway: a current Risk Register with owners and planned/implemented responses is evidence that the assess–plan–implement–communicate steps are happening, not just identification.
Risks are not being assessed, planned, implemented, and communicated via ownership and the Risk Register.
Topic: PRINCE2 Processes
A project to implement a new CRM system is running to two management stages. Midway through the delivery stage, the Project Manager forecasts that time tolerance for the stage will be exceeded and escalates to the Project Board.
Which action is NOT a Project Board responsibility within the Directing a Project (DP) process?
Best answer: D
What this tests: PRINCE2 Processes
Explanation: In Directing a Project, the Project Board provides overall direction and makes key decisions, such as authorizing plans and responding to exceptions. The Project Manager manages day-to-day control and produces management products needed for those decisions. Therefore, creating an Exception Plan is not a Project Board responsibility.
DP is the Project Board’s process for exercising governance: it authorizes major decisions (initiation, stages, exceptions, and closure) and provides direction when needed. When a forecast shows a stage will exceed tolerance, the Project Manager escalates and supports decision-making by preparing the appropriate information and plans.
In this scenario:
The key takeaway is that the Project Board authorizes and directs; the Project Manager prepares and manages.
Creating the Exception Plan is the Project Manager’s responsibility; the Project Board reviews and authorizes it.
Topic: PRINCE2 Practices
A project manager needs a quick, consistent way to compare several identified risks and decide which ones should be escalated to the Project Board. Only ordinal scales are available (e.g., Very Low to Very High for likelihood and impact), and no reliable cost/time data exists for numerical analysis.
Which qualitative risk assessment approach is most appropriate?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: This situation calls for qualitative risk assessment because only ordinal (non-numeric) likelihood/impact information is available. A probability–impact matrix provides a simple, repeatable way to rate and rank risks so the project manager can focus responses and escalate the most significant risks. It fits early or data-poor contexts where speed and consistency matter more than precision.
PRINCE2’s Risk practice includes assessing risks using qualitative techniques when precise numerical data is unavailable or the decision needs a quick prioritization. A probability–impact matrix combines an ordinal estimate of likelihood with an ordinal estimate of impact to produce a risk rating (often visualized as a heat map). That rating helps compare many risks consistently, set response priorities, and decide which risks should be escalated because they threaten tolerances or exceed risk appetite. Quantitative techniques (such as EMV, Monte Carlo, or sensitivity analysis) depend on credible numeric inputs and are typically used when the project needs more precise forecasting and the data supports it.
Key takeaway: use qualitative ranking (like probability–impact) when you need fast, consistent prioritization without reliable numbers.
It uses ordinal likelihood and impact scales to prioritize risks quickly and consistently for escalation decisions.
Topic: Project and PRINCE2 Key Concepts
A project is building a new online self-service portal. Work has slipped because features are repeatedly reworked after reviews, and progress reporting is inconsistent (one team reports “80% complete” while another says “still designing”). Stakeholders keep disagreeing about what “done” looks like.
In PRINCE2 terms, what is the MOST likely underlying cause?
Best answer: C
What this tests: Project and PRINCE2 Key Concepts
Explanation: PRINCE2’s product focus relies on clearly defining what must be delivered and how it will be accepted. Weak or missing Product Descriptions mean unclear acceptance criteria and quality expectations for the specialist products, which drives rework and makes progress hard to measure consistently. This points to a product-definition problem, not just reporting or decision delays.
The symptoms (rework, disagreement about “done”, inconsistent progress measures) indicate that the outputs are not defined in a way people can build, review, and accept consistently. In PRINCE2, those definitions are captured using Product Descriptions, which are management products used to specify a product’s purpose, composition, quality criteria, and quality methods.
PRINCE2 distinguishes:
Focusing on products helps align expectations, enable objective quality control, and allow progress to be tracked by completed/accepted products rather than vague “percent complete”.
Without clear Product Descriptions (a management product), teams lack agreed acceptance and quality criteria for specialist products, causing rework and unclear progress.
Topic: PRINCE2 Processes
A project manager has just been appointed and has received a Project Mandate to replace an organisation’s HR system. During Starting up a Project, the project manager has created the Daily Log, captured previous lessons in the Lessons Log, and drafted the Project Brief (including an Outline Business Case and Project Product Description).
Before asking the Project Board for permission to move into Initiating a Project, what management product should be produced next?
Best answer: C
What this tests: PRINCE2 Processes
Explanation: Starting up a Project prepares enough information for the Project Board to decide whether it is worth initiating the project. Once the Project Brief has been assembled, the project manager produces the Initiation Stage Plan to request authorization to proceed into the initiation stage. This matters because it sets the immediate stage controls and resources needed for initiation.
In Starting up a Project (SU), the aim is to ensure the prerequisites for initiation are in place and the Project Board can make an informed decision to authorize initiation. Typical SU management products include the Daily Log and Lessons Log (created), and the Project Brief (assembled/created, including the Outline Business Case and Project Product Description).
After the Project Brief is ready, the next key SU output is the Initiation Stage Plan. This is what the Project Board uses to authorize the initiation stage, because it defines what will be done in initiation, when, by whom, and within what constraints for time and cost. The PID is created during Initiating a Project, not during SU.
The Initiation Stage Plan is produced in SU so the Project Board can authorize the initiation stage with agreed time/cost controls.
Topic: PRINCE2 Principles
During a management stage, the project manager is seeing repeated rework and slow decisions from key stakeholders. The stage plan has a time tolerance of +/-1 week, but the latest forecast shows the stage will finish 3 weeks late.
According to PRINCE2, what is the appropriate escalation action and who should be informed?
Best answer: B
What this tests: PRINCE2 Principles
Explanation: Because the forecast finish date is outside the agreed stage tolerance, the situation is an exception in PRINCE2 terms. The project manager must escalate by producing an Exception Report for the Project Board, who decide how to proceed (for example, via an Exception Plan).
PRINCE2 manages control using tolerances and the principle of management by exception. When the project manager forecasts that a stage will exceed its agreed tolerance (here, 3 weeks late versus a +/-1 week tolerance), they no longer have delegated authority to continue as planned.
The correct escalation is to:
Routine progress reporting can continue, but it does not replace the required exception escalation when tolerances are forecast to be exceeded.
A forecast breach of stage tolerance must be escalated as an exception to the Project Board using an Exception Report.
Topic: PRINCE2 Processes
A project to implement a new HR system is being closed. During the final review, the project manager says there is “nothing left to do” and asks the project board to authorize closure.
Two weeks later, the operational support team discovers several known minor defects and an outstanding data-migration risk. No owner in business-as-usual was assigned, and the Issue Register and Risk Register show these items as closed.
What is the most likely underlying PRINCE2 cause?
Best answer: D
What this tests: PRINCE2 Processes
Explanation: In Closing a Project, remaining issues and risks are not ignored; they must be captured as follow-on actions and transferred to the appropriate authority (often business-as-usual) with clear owners. Marking items as “closed” without handover leads to unresolved defects/risks resurfacing after closure and surprises for operations.
In the Closing a Project (CP) process, the project manager confirms acceptance of the project’s products and then ensures the project is left in a controlled state. That includes dealing properly with any unresolved issues and risks.
If issues/risks cannot be resolved within the project, they should be:
Simply closing register entries and ending the project without assigning ownership creates the exact symptom in the scenario: known defects and risks reappear after closure with nobody accountable. The other options point to delivery-time controls or product definition rather than closure-time handover.
At Closing a Project, unresolved issues/risks should be recorded as follow-on action recommendations and handed over with clear ownership rather than simply being marked closed.
Topic: PRINCE2 Practices
On a software project, most deliverables pass informal peer checks but then fail during user acceptance testing. Defects are logged late, and the team often reworks items because meeting notes do not show clear decisions or agreed actions. The project manager says “we do reviews”, but there is no defined chairperson, no one records actions, and reviewers usually see the product for the first time during the meeting.
What is the most likely underlying cause in PRINCE2 terms?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: The symptoms point to weak, ad hoc reviews: late defect discovery, unclear decisions, and repeated rework. In PRINCE2, this is typically caused by not using the structured quality review technique, including the defined roles and the prepare–review–follow-up steps that ensure issues, decisions, and actions are captured and resolved early.
PRINCE2’s quality review technique is a structured, facilitated review of a product against its defined quality criteria. It uses specific roles to make the review efficient and auditable: a chair (runs the review and confirms the result), a presenter/producer (introduces the product), reviewers (check against criteria), and a scribe (records defects, actions, and decisions).
A typical flow is:
If these roles and steps are missing, reviews become informal, defects are found late, and decisions/actions are not captured—driving rework and failed acceptance.
PRINCE2 quality reviews require defined roles (chair, presenter, reviewers, scribe) and preparation, review, and follow-up to capture decisions and actions early.
Topic: PRINCE2 Processes
A project manager has been appointed to deliver a new customer portal. The only information available is a project mandate from the Executive stating the desired outcome and a target go-live date. The Executive asks for approval to start the initiation work immediately, but there is no agreed definition of what will be delivered or how the initiation will be managed.
What is the BEST next action in Starting up a Project?
Best answer: A
What this tests: PRINCE2 Processes
Explanation: Starting up a Project prepares enough information for the Project Board to decide whether it is worth initiating the project. Creating the Project Brief (including the Project Product Description) clarifies what the project is and what product is required, while the Initiation Stage Plan shows how the initiation work will be done. These together support governance by enabling authorization to initiate on an informed basis.
In PRINCE2, Starting up a Project (SU) is about ensuring the prerequisites for initiation are in place before significant time and money are spent. The project manager develops key management products that give the Project Board a reliable basis for decision-making.
In this scenario the next step is to prepare:
The Project Board then uses these to authorize the project to proceed into initiation, rather than starting work without an agreed definition and control baseline.
In SU these products provide the minimum definition and plan needed for the Project Board to authorize initiation.
Topic: PRINCE2 Practices
During a quality review of a new customer self-service portal, a defect is found: audit logging does not meet the Product Description’s acceptance criteria. The team estimates rework will take 3 days and cost $6,000. The current management stage has tolerances of ±1 week and ±$15,000, and there is no expected impact on the end-stage date.
What should the project manager do to best balance control and progress in line with PRINCE2?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: A quality nonconformance found in a quality review is a product defect and should be captured and controlled as an issue. The project manager should assess impact and take corrective action within delegated authority when it remains inside agreed stage tolerances. Normal reporting then provides visibility without unnecessary escalation.
In PRINCE2, a product defect (nonconformance against the Product Description’s quality criteria) is handled through issue control: it should be recorded in the Issue Register, assessed for impact, and given an owner and action. The project manager can authorize and manage corrective rework when the forecast remains within the agreed tolerances for the management stage (time and cost in this scenario). Quality records should also be updated to show the follow-up quality activity (for example, re-test/re-review) and progress should be communicated using normal controls such as Checkpoint/Highlight reporting.
Escalation (for example, an Exception Report) is needed when the response would exceed tolerances or requires a decision outside the project manager’s authority; that is not the case here.
A product defect is an issue that should be logged and assessed, and since the corrective action is within tolerances it can be handled without escalation.
Topic: PRINCE2 Practices
Midway through a delivery stage, the project manager learns that a key supplier might be unable to provide a specialist for two weeks. If it happens, the stage end date could slip by up to 10 days, but the stage time tolerance is ±5 days.
To support a decision that balances business justification with appropriate governance, what is the best way to record this in PRINCE2 and what information should be captured for it?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: The Risk Register’s purpose is to identify, assess, and control risks by holding enough information for informed decisions and ongoing monitoring. For each risk it records the risk’s description (cause–event–effect), assessment data (probability, impact, proximity), and response/control data (owner, planned actions, status). This supports escalation decisions when stage tolerances are at risk.
In PRINCE2, the Risk Register is the central management product used to capture, maintain, and communicate information about threats and opportunities so they can be systematically assessed and controlled. In this scenario the supplier shortfall is uncertain (so it is a risk, not an issue) and it could push the stage beyond time tolerance, so the project manager needs a complete, comparable record to support decisions and potential escalation.
For each risk, the Risk Register typically records:
Capturing only a workaround, only financial exposure, or relying on informal email does not provide controlled, auditable risk information for governance and escalation.
The Risk Register exists to capture and maintain structured risk information (including assessment and response details) so exposure can be controlled and escalated if tolerances may be exceeded.
Topic: PRINCE2 Practices
What is the purpose of the Issue Register in PRINCE2?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: The Issue Register is the project’s central log for all issues that need to be managed, such as requests for change, off-specifications, and problems/concerns. It supports control by recording key details, ownership, status, and outcomes so issues can be monitored through to closure.
In PRINCE2, an issue is any relevant event that has happened, was not planned, and requires project management action. The Issue Register exists to provide a single, controlled place to record and track these issues throughout their lifecycle.
It should record enough information to manage each issue, such as:
This is different from risk management (future uncertainty), routine progress reporting, or configuration records.
It provides a central record to manage and monitor issues (e.g., requests for change, off-specifications, problems/concerns) through to closure.
Topic: PRINCE2 Practices
What is the purpose of the Benefits Management Approach, and what information should it include?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: The Benefits Management Approach explains how the project’s benefits will be realized, measured, and reported, including who is responsible and when reviews will take place. It ensures benefits tracking is planned and continues for as long as needed, which may extend beyond project closure. This supports continued business justification and effective handover to operational ownership.
The Benefits Management Approach is used to plan and manage the realization of benefits from the project’s outputs. Its purpose is to define how benefits will be measured, tracked, and reported so that the organization can confirm the Business Case is being achieved.
It should include information such as:
It complements the Business Case: the Business Case explains why the project is worthwhile; the Benefits Management Approach explains how benefit realization will be managed and verified.
It sets out the approach to realizing and measuring benefits, including measures, owners/responsibilities, and when reviews will occur.
Topic: PRINCE2 Practices
A project is delivering a new digital claims system. The Business Case expects annual savings of $1.0m after go-live, with a benefits tolerance of \(\pm 10\%\) agreed in the PID.
Midway through the current stage, new regulatory requirements reduce the forecast savings to $0.8m. Cost and schedule are still within tolerance.
What should the project manager do to best balance business justification and PRINCE2 governance?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: During the project, benefits are managed as forecasts in the Business Case (expected benefits), not as realized outcomes. When an updated forecast moves outside the agreed benefits tolerance, the project manager must escalate to the Project Board for a decision. Realized benefits are assessed after project closure through benefits reviews.
PRINCE2 treats benefits in the Business Case as expected (forecast) while the project is being delivered; they are only realized after the project outputs are in use, typically measured through post-project benefits reviews. In this scenario, the forecast savings drop from $1.0m to $0.8m (a 20% reduction), which breaches the agreed \(\pm 10\%\) benefits tolerance in the PID. Even though time and cost remain within tolerance, a benefits tolerance breach threatens continued business justification, so the project manager should update the Business Case and escalate via the project’s exception route (e.g., an Exception Report) for the Project Board to decide how to proceed.
The key takeaway is to act on forecast (expected) benefits during delivery, and measure realized benefits after closure.
The benefits forecast is now outside agreed tolerance, so it must be escalated while benefits remain expected until realized after closure.
Topic: PRINCE2 Practices
In PRINCE2, a risk budget is money set aside to fund what?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: A risk budget is a planned amount of money reserved to implement agreed responses to identified risks. It supports proactive risk management by ensuring that funding is available for actions such as avoiding, reducing, transferring, exploiting, or enhancing risk impacts.
In the PRINCE2 Risk practice, a risk budget is money set aside specifically for planned risk responses. It is used to pay for agreed actions that address identified threats and opportunities (for example, extra testing to reduce a technical threat, or a pilot to exploit an opportunity). This budget supports planned responses by making funding explicit and available, rather than relying on ad-hoc approvals or treating response costs as unplanned overruns. It is distinct from money used to pay for scope changes, to correct issues after they occur, or to cover general estimation error within tolerances.
A risk budget is allocated specifically to pay for agreed risk response actions, rather than to cover general overspends or changes.
Use the PRINCE2 Foundation Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Read the PRINCE2 Foundation guide on PMExams.com for concept review, then return here for PM Mastery practice.