Try free PRINCE2 Practitioner practice across the exam domains, with answers and explanations, then continue in PM Mastery.
This free full-length PRINCE2 Practitioner practice exam includes original PM Mastery practice across the exam domains, modeled around the 70-mark practitioner assessment emphasis.
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: PeopleCert’s current PRINCE2 Practitioner Version 7 page lists 56 questions and sub-questions worth 70 marks. PM Mastery uses this page as a 70-mark diagnostic-style practice run, so confirm current booking, book rules, language availability, and delivery rules directly with PeopleCert.
Set a 150-minute timer and treat the set as an applied PRINCE2 scenario diagnostic. Track misses by whether the problem was scenario evidence, role accountability, management product, process step, or exception logic.
Use this page as a PRINCE2 Practitioner scenario 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 applied PRINCE2 judgment may be stable. Review explanations and protect timing. | |
| Many practice misses | Drill Business Case, organizing, plans, quality, risk, issues, and progress in scenario context. | |
| Many process misses | Review who authorizes what, when products are updated, and when exceptions escalate. | |
| Many people or communication misses | Revisit stakeholder engagement, role responsibilities, and decision-quality cues. | |
| Open-book lookup takes too long | Practice using the book to confirm a judgment, not to discover every concept from scratch. |
| Field | Record |
|---|---|
| Overall score | ___ / 70-mark diagnostic emphasis |
| Timing result | Finished early / on time / rushed late |
| Highest-miss area | concepts / principles / people / practices / processes |
| Most expensive mistake type | weak scenario evidence / role confusion / wrong control product / exception logic error / other: ___ |
For concept review before or after this set, use the PRINCE2 Practitioner 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 scenario drills, explanations, and progress history instead of one page you can memorize.
| Checkpoint | Approximate time budget | What to do |
|---|---|---|
| First third | 50 minutes | Read the scenario facts before selecting the PRINCE2 control response. |
| Second third | 100 minutes cumulative | Watch for role, product, and exception-management traps. |
| Final third | 150 minutes cumulative | Finish with enough time to review marked scenario decisions and book references. |
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 Practitioner |
| Official exam name | PRINCE2 Project Management Practitioner (Version 7) |
| Full-length set on this page | 70 questions |
| Exam time | 150 minutes |
| Topic areas represented | 5 |
| Topic | Approximate official weight | Questions used |
|---|---|---|
| Project and PRINCE2 Key Concepts | 3% | 2 |
| PRINCE2 Principles | 8% | 6 |
| People in Successful Projects | 14% | 10 |
| PRINCE2 Practices | 60% | 42 |
| PRINCE2 Processes | 15% | 10 |
Topic: People in Successful Projects
A project to implement a new customer self-service portal is approaching a stage boundary. The Executive says: “Before I approve the next stage, I need confidence the project still represents value for money and remains the best way to achieve the expected benefits, given the latest costs, risks, and market changes.”
Which PRINCE2 management product BEST matches this stakeholder information need?
Best answer: C
What this tests: People in Successful Projects
Explanation: The Executive’s primary information need is continued business justification at a decision point. The management product that consolidates the latest costs, benefits, and risks to demonstrate ongoing viability is the Business Case. Updating it supports the Project Board decision to authorize the next stage or stop the project.
In PRINCE2, different stakeholder groups need different levels and types of information to make decisions or carry out their responsibilities. The Executive is accountable for ensuring continued business justification, so at a stage boundary they need an up-to-date view of whether the project is still viable and worthwhile compared with alternatives. That information is provided through the Business Case, which is maintained and updated to reflect current forecasts for costs, benefits, timescales, and key risks.
Other reports may be used at a stage boundary, but they primarily summarize performance and status rather than proving value for money. The key takeaway is to match the stakeholder’s decision responsibility (continue/stop based on viability) to the product that addresses that decision.
It provides the Executive with the current justification, including updated costs, benefits, and risks to support the decision to continue.
Topic: PRINCE2 Practices
A project is delivering a new cloud-based HR system. The current Stage Plan is within time and cost tolerances, but a new corporate policy will mandate use of a shared enterprise platform within 12 months, reducing the forecast benefits of the HR system by about 50%.
Constraints:
What is the BEST next action for the Project Manager to apply the business case management technique and maintain control?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: PRINCE2 requires continued business justification, so when an external change significantly reduces forecast benefits the Project Manager should not wait for the next stage boundary. The Business Case needs to be updated to reflect the new forecast and escalated via exception so the Project Board can decide whether to continue, change direction, or stop while contractual options are still available.
Business case management is a continuous technique: develop the Business Case, check it remains viable, maintain it with updated forecasts/actuals, and confirm justification through key decision points. Here, the policy change materially undermines the forecast benefits and there is a time-limited break clause, so the project’s justification is at immediate risk and needs prompt governance action.
A suitable application is:
Waiting for the stage boundary would weaken control and may remove the low-penalty termination option.
The Project Manager should trigger an exception when justification is threatened, updating the Business Case and escalating to the Project Board for direction.
Topic: People in Successful Projects
A project to roll out a new HR system uses a matrix team from IT, HR, and an external supplier. The Project Board is fixed and meets monthly.
Symptoms over the last 6 weeks:
In PRINCE2 terms, what is the MOST likely underlying cause the Project Manager should address to improve motivation and accountability within the existing governance constraints?
Best answer: A
What this tests: People in Successful Projects
Explanation: The pattern of conflicting instructions, unclear “done”, and informal scope changes points to missing clarity on who is accountable to decide, direct, and accept products. In PRINCE2, clear roles and responsibilities (and explicit acceptance and change authority) support motivated teams because people know what they own and what authority they have.
This situation shows a breakdown in accountability rather than simply a scheduling or reporting problem. When multiple parties give direction and work is accepted informally, teams cannot rely on a single agreed source of priorities, acceptance criteria, and change authority. In PRINCE2 terms, the Project Manager should address unclear roles and responsibilities by ensuring decision-making and acceptance accountabilities are defined and communicated (for example: who provides direction as Senior User, who accepts products on behalf of users, who is change authority within tolerances, and who reports progress as a Team Manager).
Practical PRINCE2-aligned actions include:
Improving role clarity enables faster decisions, reduces rework, and makes progress reporting meaningful.
Conflicting direction, informal change, and inconsistent reporting indicate accountabilities for decisions and acceptance are not clearly defined and applied.
Topic: PRINCE2 Practices
Halfway through stage 2 of a customer portal project, the Project Manager learns that the organization has signed a 3-year enterprise contract for an existing portal that will go live in 4 months.
The Senior User confirms the planned benefits in the Business Case will no longer be realized if this project continues. The project is still forecast to deliver within time and cost tolerances for the current stage.
What is the MOST appropriate PRINCE2 action now?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: PRINCE2 requires continued business justification; once the Business Case is no longer viable, the project should not continue just because it is within tolerances. The Project Manager should promptly escalate the situation so the Project Board can decide whether to stop the project (premature closure) or provide new direction.
The decisive factor is that the Senior User has confirmed the Business Case benefits will not be realized, meaning business justification has been lost. Under PRINCE2, continued business justification is mandatory throughout the project, so the Project Manager must not continue work simply because stage time/cost tolerances are still forecast to be met.
The Project Manager should:
Waiting for routine reporting or trying to “deliver something anyway” undermines the principle of stopping when the project is no longer justified.
Loss of business justification requires immediate escalation so the Project Board can decide on premature closure.
Topic: PRINCE2 Practices
You are the Project Manager initiating a data-platform project with an internal development team and an external analytics supplier. The Project Board has agreed the main roles, but there is confusion over who is accountable for approving data-quality rules and who should be consulted on change requests. The Executive asks you to clarify the project management team structure and interfaces before work starts.
What is the most appropriate next step in PRINCE2 terms?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: To design the project management team structure and interfaces, PRINCE2 uses responsibility assignment techniques such as a RACI chart. This makes accountabilities and consultation paths explicit across internal and supplier roles. The agreed responsibilities are then captured in the PID’s project management team structure and role descriptions before delivery begins.
The organizing practice needs a clear, agreed project management team structure with well-defined interfaces, especially when multiple delivery groups are involved. When role boundaries are unclear, the most direct organizing technique is to map responsibilities (responsible, accountable, consulted, informed) for key decisions and products using a responsibility assignment matrix such as RACI.
After agreeing the RACI with the relevant stakeholders, the Project Manager should reflect it in the management products that define how the project will be managed:
Management approaches (e.g., change control) can support how decisions are handled, but they do not replace explicitly defining who does what.
A responsibility assignment matrix (e.g., RACI) is the organizing technique to design clear role interfaces and then document them in the PID/role descriptions.
Topic: PRINCE2 Practices
A project is approaching a Stage Boundary. The next stage includes delivery of a new customer portal, and each increment must be formally accepted by a user representative before release. The Senior User has left the organization and no replacement has been named. The Project Board set stage tolerances at <=11 week and <=20,000, and the supplier wants to start build work immediately to avoid delays.
What is the BEST next action for the Project Manager?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: This is a governance gap: there is no accountable role to confirm user acceptance, so control over product quality and benefits realization is at risk. PRINCE2 requires the Project Board to ensure roles are filled and responsibilities are clear, so the Project Manager should escalate and get an explicit appointment/delegation for acceptance authority before proceeding.
The core issue is a role gap affecting product acceptance, which is essential for ensuring outputs meet user needs and enable benefits. In PRINCE2, the Senior User is accountable for specifying needs and accepting products on behalf of users; the Project Manager should not take on this accountability, and neither should the supplier side.
Best next action is to use the escalation path and get the Project Board (typically via the Executive) to:
This preserves manage-by-exception and avoids unauthorized acceptance that could undermine control at the stage boundary.
Product acceptance is a Senior User accountability, so the Project Board must assign a suitable user acceptance role and confirm escalation paths before authorizing progress.
Topic: PRINCE2 Practices
A project is implementing a digital self-service portal. The approved Business Case assumes a government rebate will fund 30% of running costs for the first two years.
Mid-stage, the government announces the rebate will be withdrawn. The Project Manager’s early re-forecast shows the stage will still finish within current cost and time tolerances, but forecast net benefits over the product’s life will reduce significantly.
Which management product is the best evidence to validate whether the project remains justified and to keep the justification current for a Project Board decision?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: When key assumptions or forecasts change, PRINCE2 requires the Business Case to be kept current so the Project Board can confirm continued business justification. Even if the stage is still within tolerances, a material reduction in forecast benefits must be reflected in an updated Business Case. This provides the evidence needed for a continue/change/stop decision.
The Business Case is the primary management product used to justify starting and continuing the project. When an assumption (such as funding) changes, the key action is to update the Business Case with the revised costs, benefits, risks, and timescales so the Project Board can re-assess whether the project still represents value for money and remains aligned to objectives.
In this scenario the project is not (yet) forecast to exceed stage tolerances, so escalation via exception is not automatically triggered. The decision need is specifically “are we still justified?”, and the most direct and complete evidence for that decision is the updated Business Case, which should then be reviewed/approved through the project’s normal governance controls.
It is the definitive product for re-validating continued business justification when benefits, costs, risks, or assumptions change.
Topic: PRINCE2 Practices
You are the Project Manager preparing for the Stage Boundary. The Project Board has asked for evidence to decide whether to authorize the next stage or change direction.
Exhibit: Draft End Stage Report (excerpt)
Stage 1 tolerance: Time +2w / Cost +\$50k / Scope: must deliver P1–P4
Actuals: +3w / +\$30k / P1–P3 delivered; P4 70% complete
Forecast to finish P4: +2w and +\$15k in Stage 2
Benefits forecast: down 10% due to lower user adoption
Risks: R12 (integration delay) probability increased to High
Recommendation: Proceed to Stage 2 with revised plan
Which interpretation best reflects the purpose of the End Stage Report in supporting the Project Board’s decision?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: An End Stage Report is a control for the Project Board at a stage boundary, consolidating what was achieved, how performance compared to tolerances, and what is forecast next. By including updated benefits and risk outlook, it enables an informed decision to authorize the next stage, request replanning, or change direction based on continued viability.
The End Stage Report is produced at a stage boundary to give the Project Board a clear basis for control decisions. It brings together the stage’s actual results versus the approved Stage Plan (including any tolerance breaches), plus forecasts for the remainder of the project and the impact on project viability.
In this exhibit, the report highlights a time tolerance breach, incomplete scope, a cost position, a forecast to complete remaining work in the next stage, a reduction in benefits forecast, and an increased key risk. That combination supports the Project Board deciding whether to:
It is a stage-end summary and decision support product, not a mechanism for day-to-day team authorization or for replacing logs/registers.
An End Stage Report summarizes stage results and forecasts (including Business Case impact) so the Project Board can decide whether to continue, change, or stop.
Topic: PRINCE2 Principles
A project is replacing a local authority’s customer portal. Stage 1 (pilot) has finished, and the Project Manager is preparing the Stage Plan for Stage 2 (full rollout).
During Stage 1, several defects were caused by inconsistent test environments between supplier and authority teams. The Project Manager also finds a similar lesson from a previous programme in the organization’s knowledge base.
Which action best applies the PRINCE2 principle of learning from experience at this point?
Best answer: D
What this tests: PRINCE2 Principles
Explanation: PRINCE2 expects lessons to be sought, recorded, and applied throughout the project, not saved until the end. A stage boundary is the ideal point to apply learning because the next Stage Plan and Work Packages are being produced/authorized. Updating the Lessons Log and tailoring the next stage’s approach ensures the lesson is acted on immediately.
The learn from experience principle requires the project to actively look for relevant lessons (including from previous projects), record new lessons as they emerge, and apply them to improve performance. In this scenario, the key discriminator is that the project is at a stage boundary and the next Stage Plan and Work Packages are being prepared. That is the most effective moment to embed the environment-alignment lesson into how Stage 2 will be delivered and controlled (e.g., stronger acceptance criteria, agreed environment standards, earlier integration checks), while also capturing it in the Lessons Log for future reuse. The method expects lessons to influence current planning and decision-making, not only retrospective reporting.
At a stage boundary, lessons should be recorded and immediately used to shape the next stage’s planning and controls.
Topic: PRINCE2 Processes
Midway through a management stage of a customer portal project, the Project Board complains that it is repeatedly surprised by delays and cost increases. The Project Manager is receiving ad hoc updates from team leads and often learns about problems only when a product is nearly due. As a result, decisions are made late, completed products are returned for rework, and small scope changes are being accepted informally to “keep stakeholders happy”. No stage tolerances have yet been forecast as breached.
Which is the MOST likely underlying PRINCE2 cause of these symptoms during Controlling a Stage?
Best answer: D
What this tests: PRINCE2 Processes
Explanation: The pattern of surprises, late decisions, and informal change acceptance points to weak stage control rather than inevitable performance issues. In PRINCE2, the Project Manager should monitor progress through Work Packages and regular Checkpoint Reports, then take corrective action within authority before issues become urgent. When that control loop is missing or poorly applied, reporting becomes ad hoc and corrective action is delayed.
During Controlling a Stage, the Project Manager’s “control loop” relies on agreeing and tracking Work Packages, getting regular Checkpoint Reports, comparing actuals to the Stage Plan, and then taking corrective action (or escalating if forecasts exceed tolerance). In this scenario, the Project Manager is getting ad hoc updates and only discovering problems near due dates, so there is insufficient visibility to act early. That leads directly to late decisions, avoidable rework (because problems are found late), and informal scope changes slipping in without being handled as issues/changes.
A practical sequence is:
The key diagnostic clue is “surprised by delays/cost increases” despite no forecast tolerance breach, indicating monitoring and reporting are ineffective rather than tolerances being exceeded.
Without agreed Checkpoint Reports against Work Packages, progress is not monitored frequently enough to trigger timely corrective action and informed reporting.
Topic: PRINCE2 Practices
You are the Project Manager for a small internal project delivering a new employee self-service portal in one 6-week management stage. Governance requires clear agreement on what will be delivered and how it will be accepted, but the delivery team is using an agile approach and wants minimal documentation.
Which tailoring decision for the Product Description is MOST appropriate while keeping PRINCE2 controls effective?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: Tailoring should simplify format, not remove essential control. A Product Description still needs to state what the product is made of (composition), the measurable quality criteria, and the method by which it will be checked and accepted (including who will accept). A one-page format aligns to agile while preserving clear acceptance and quality expectations.
In PRINCE2, a Product Description is the baseline for understanding and controlling a product’s definition and quality. Tailoring can reduce documentation effort (for example, a one-page template or an agile-friendly form), but it must still include the key content needed to plan and control delivery.
For this scenario, the Product Description should, at minimum:
Removing acceptance definition or relying on informal agreement weakens control and increases rework risk, even on a small agile project.
It keeps the essential Product Description content while tailoring the format to be lightweight for agile delivery.
Topic: People in Successful Projects
A Project Board will decide whether to authorize project closure for a digital service rollout. The Senior User asks the Project Manager for objective evidence that all agreed products have been completed and approved (i.e., no outstanding products awaiting review), without asking the project support office to “sign off” acceptance.
Project support maintains the configuration records and registers.
Which management product is the BEST evidence for the Project Board to validate product completion/approval status?
Best answer: C
What this tests: People in Successful Projects
Explanation: A Product Status Account is designed to confirm the current status of planned and delivered products, including whether they have been completed and approved. Project support can compile it from configuration item records and related registers, providing evidence without taking accountability for acceptance decisions. This allows governance roles to make the closure decision using controlled records.
Project support can help controls by maintaining registers/records and producing status information, but governance accountabilities (e.g., accepting products and authorizing closure) remain with the appropriate roles such as the Senior User and Project Board. When the decision need is “are all required products complete and approved?”, the most direct validation is a Product Status Account: a configuration management output that lists products and their current states/versions and approval status. Project support can compile this from the configuration records, giving the Project Board objective evidence to support the closure decision.
The key takeaway is to use configuration-based status evidence for product completion, rather than narrative progress reporting or issue-only views.
It provides an objective snapshot of each product’s current state (e.g., complete/approved) drawn from configuration records that project support can maintain.
Topic: PRINCE2 Practices
A project is delivering a new online billing system. Stage 2 has an approved Stage Plan with a time tolerance of ±1 week. Mid-stage, the Team Manager reports a supplier dependency will delay a critical product by 3 weeks. The Project Manager forecasts the stage will exceed its time tolerance, but the overall project is still within the Project Board’s project-level time tolerance.
Select TWO statements that correctly describe what should happen next.
Correct answers: A, C
What this tests: PRINCE2 Practices
Explanation: A forecast breach of a stage tolerance triggers management by exception at stage level. The Project Manager should therefore prepare an Exception Plan for the rest of the stage and provide updated whole-project forecasting (via the Project Plan) so the Project Board can make an informed decision on whether to approve the exception approach.
PRINCE2 uses different plan horizons for control. The Project Plan provides the high-level baseline and forecast for the whole project, while a Stage Plan is the day-to-day control baseline for the current stage. When the Project Manager forecasts that a stage tolerance will be exceeded, they must escalate (typically via an Exception Report) and develop an Exception Plan covering the remainder of that stage; if the Project Board approves it, the Exception Plan replaces the current Stage Plan for the remaining work.
In parallel, the Project Manager should update the Project Plan forecast to show how the stage exception affects overall delivery, even when project-level tolerances are not forecast to be breached. Team Plans remain optional and are used by Team Managers for detailed delivery of agreed Work Packages, not as a replacement for stage- or project-level control.
A forecast breach of stage tolerance triggers an exception, requiring an Exception Plan to replace the Stage Plan for the remainder of the stage if approved.
Even if project tolerance is not forecast to be breached, the Project Plan forecast is updated to show the expected impact and support governance decisions.
Topic: PRINCE2 Principles
You have been asked to manage a new internal project using PRINCE2. The Executive says, “This should be lightweight—tailor out as much management overhead as you can.”
At this point you only know that the project will deliver a new workflow and a small supporting IT change, but you do not yet know how critical the change is, the level of uncertainty, or any constraints from corporate governance.
What should you verify/obtain FIRST before deciding how much to tailor PRINCE2 controls and management products?
Best answer: A
What this tests: PRINCE2 Principles
Explanation: PRINCE2 tailoring is driven by the project context, especially risk, complexity, and governance expectations. Before reducing controls or omitting management products, you need to understand the project’s risk exposure and the tolerances within which the Project Manager can operate. That baseline lets you judge whether a “lightweight” approach is appropriate and what minimum controls are still needed.
Tailoring means adapting PRINCE2 to suit the project, while keeping adequate control. The first input you need is the project’s context, particularly how much risk and uncertainty the organization is willing to accept and how it will be governed. In PRINCE2, that is expressed through risk exposure and agreed tolerances (manage-by-exception): tighter tolerances and higher exposure generally require stronger controls, more frequent reporting, and more complete management products; wider tolerances and low exposure may justify lighter documentation and fewer formal reviews.
Once risk exposure/tolerances are clear, you can sensibly tailor items such as the number/length of stages, reporting frequency, and the level of detail in product descriptions and plans. Tooling, team naming, and copying old documentation are secondary considerations and can’t safely drive tailoring decisions.
Tailoring should be based first on scale, complexity, and risk so controls/products match the project’s risk exposure and exception boundaries.
Topic: Project and PRINCE2 Key Concepts
A project aims to meet a business objective to reduce invoice processing costs by 20% within 6 months of go-live. At the end of the current stage, the automated invoicing system has been built and internally tested (the main product output), but deployment and user adoption activities are planned for the next stage.
The Project Manager reports in the Highlight Report that the “20% cost reduction benefit has been achieved” because the system build is complete.
What is the most likely near-term impact on project governance and business justification?
Best answer: A
What this tests: Project and PRINCE2 Key Concepts
Explanation: The system build is an output; the cost reduction is a benefit that can only be evidenced after the output is used and the outcome (changed invoicing process) occurs. Reporting the benefit as already achieved weakens decision-making at the stage boundary. Governance should therefore insist the Business Case/benefits information is corrected before authorising further work.
Outputs are the specialist products delivered by the project (e.g., a built system). Outcomes are the result of using those outputs in operations (e.g., a changed invoicing process). Benefits (and dis-benefits) are measurable improvements (or negative impacts) that flow from outcomes and support (or hinder) business objectives.
Here, the project has only completed the output; deployment/adoption has not happened, so the outcome and the 20% cost reduction benefit cannot yet be claimed. Near-term governance at a stage boundary relies on an accurate Business Case and benefits profile to decide whether the project remains viable. The misreporting should be corrected (and, if needed, benefits timing/forecast updated) before the Project Board authorises the next stage.
Benefits depend on outcomes from using outputs, so governance will challenge the misstatement and require updated justification for the next stage.
Topic: PRINCE2 Practices
A Project Manager is running a risk workshop for a customer-relationship-management (CRM) replacement project. The delivery team is confident the data migration will be “straightforward” and has rated several migration risks as low probability, mainly based on the supplier’s assurances and the team’s positive experience on the last project.
The Project Manager is concerned that decision biases are distorting the assessment and wants to reduce their impact before updating the Risk Register and reporting to the Project Board.
Which action is NOT aligned with PRINCE2 ways of reducing decision-bias impact in risk assessment?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: PRINCE2 expects risk assessment to be evidence-based and appropriately challenged, especially where optimism, anchoring, or confirmation bias is likely. Techniques such as independent facilitation, using historical data/lessons, and assurance challenge help counter biased estimates. Retaining an initial rating just to avoid delay bakes the bias into the Risk Register.
The core issue is biased probability assessment (e.g., optimism bias and anchoring on the supplier’s view). In PRINCE2, risk assessment should be credible, transparent, and open to challenge so that decisions reflect the project’s risk appetite and tolerances.
Good ways to reduce bias include:
Choosing to keep an initial estimate because it is convenient does the opposite: it preserves the anchor and weakens the quality of risk information provided to the Project Board.
This reinforces anchoring/confirmation bias instead of using challenge and evidence to improve the risk assessment.
Topic: PRINCE2 Practices
Midway through a management stage, a key supplier proposes a design change to meet a new data-retention requirement. The supplier says it will add “some extra effort” and may delay the next milestone, but cannot yet give firm estimates.
The Project Manager must decide whether this should be handled through normal change approval or whether it is likely to require an Exception Plan.
What information should the Project Manager obtain FIRST?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: In PRINCE2, normal change control can be used while performance is forecast to remain within the delegated tolerances. An Exception Plan is required when forecasts show a stage or project tolerance will be exceeded, which removes the Project Manager’s authority to continue without escalation. Therefore the first step is to establish the forecast impact and compare it to the agreed tolerances.
The decision point between “handle as a normal change” and “treat as an exception” is governed by manage-by-exception. A change can be assessed and, if within the Project Manager’s delegated authority (including any Change Authority limits) and within stage/project tolerances, it can proceed through issue and change control.
Before choosing the route, the Project Manager should:
Approval authority and updated specifications matter, but they come after confirming whether the situation is (or is likely to become) an exception.
An Exception Plan is only triggered when forecast performance is expected to exceed an agreed tolerance, so the first need is a forecast comparison to tolerances.
Topic: People in Successful Projects
A project is delivering an AI-assisted case management system that will eliminate manual triage work for two departments. Five days before the next stage boundary, a journalist asks for comment after hearing the pilot will lead to job reductions.
Constraints: the Communication Management Approach says any media or workforce-impact messages must be approved by the Executive and Corporate Communications; the Project Board will review the updated Business Case at the stage boundary; current stage is within time/cost tolerances.
What is the BEST next action for the Project Manager?
Best answer: A
What this tests: People in Successful Projects
Explanation: Sensitive communications in PRINCE2 should follow the agreed Communication Management Approach, including defined approvals and audiences. Here, a media query creates an immediate need to respond, but the project is not in exception, so the Project Manager should not bypass governance. Preparing controlled messaging and obtaining Executive (and Corporate Communications) approval preserves appropriate control and timing.
The core decision is how to communicate sensitive information without bypassing governance. A media enquiry is time-critical, but the project has an agreed Communication Management Approach that defines who approves workforce-impact and external communications. The Project Manager should therefore prepare an appropriate response (often a short holding statement) and route it for approval through the Executive (and Corporate Communications) before any release.
A practical sequence is:
This maintains trust and consistency while avoiding unauthorized commitments ahead of the Business Case review.
This follows the agreed approval route for sensitive communications while enabling a timely, controlled response.
Topic: PRINCE2 Practices
A project to implement a digital permitting portal is midway through stage 2 of 3. A change request proposes adding an AI-assisted application checker. The Senior User believes it will increase adoption, but the Senior Supplier estimates it will add 6 weeks and increase total project cost by 12%.
The Project Board asks the Project Manager to update the Business Case before deciding whether to approve the change. What information is MOST needed to update the Business Case?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: A significant change request can alter whether the project remains viable, desirable and achievable. The Business Case must therefore be updated with the latest forecasts of costs, timescales, benefits and the associated risks/dis-benefits, so the Project Board can reassess continued business justification before authorizing the change.
The Business Case practice supports decisions by showing whether the project is still justified and worth continuing. When a significant issue or change request affects forecast cost and schedule (and potentially benefits), the near-term governance need is to re-baseline the Business Case with updated forecasts so the Project Board can compare the revised expected value against the remaining investment and exposure.
Practically, the update should include:
Plans, reporting frequency, and lessons are useful controls, but they do not, on their own, re-establish whether the project remains justified.
Updating the Business Case requires current forecasts of value, cost, time and risk so the Project Board can re-test continued business justification.
Topic: PRINCE2 Principles
Halfway through Stage 2 of a data-migration project, the Project Manager receives a Checkpoint Report from the supplier Team Manager. A newly discovered regulatory security requirement will add 10 working days and $30,000 to the team’s Work Package.
Stage 2 tolerances (set by the Project Board) are: time \(+/-5\) working days and cost \(+/-\$20,000\). The Project Manager’s assessment is that even with replanning within the stage, Stage 2 will exceed both tolerances.
What is the BEST next action?
Best answer: C
What this tests: PRINCE2 Principles
Explanation: Because the forecast impact exceeds stage tolerances, the situation is an exception that must be escalated. Under manage-by-exception, the Project Manager is accountable for reporting the forecast breach to the Project Board, who decide how to proceed and whether to authorize an exception plan or other corrective action.
PRINCE2 governance delegates day-to-day control to the Project Manager within agreed tolerances, while reserving decision-making for the Project Board when tolerances will be exceeded. Here, the Team Manager has correctly reported progress and forecast impacts via a Checkpoint Report, and the Project Manager has assessed a forecast breach of Stage 2 time and cost tolerances.
The appropriate role-based action is:
Replanning and continuing without escalation would remove the Project Board’s control over agreed tolerances.
Forecast breach of stage tolerances requires the Project Manager to raise an Exception Report for Project Board direction.
Topic: PRINCE2 Practices
On a CRM implementation project, the Project Manager reports recurring late decisions, rework, poor status reporting, and frequent scope churn.
In the logs, several items are kept only in the Risk Register even after they have happened (e.g., “supplier interface delivery is delayed” is recorded as a 100% probability risk after the delivery date has been missed). No Issue Reports are being raised; the team says they will “review the risks” at the next meeting.
What is the MOST likely underlying cause in PRINCE2 terms?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: The scenario shows events that have already happened being left in the Risk Register with “100% probability” and no Issue Reports raised. In PRINCE2, a risk is an uncertainty; when it materializes (or becomes certain), it becomes an issue and must be managed through the issues practice and appropriate decision-making.
This is primarily a risk-versus-issue classification problem. A risk is an uncertain event that may occur and, if it does, affects objectives; it belongs in the Risk Register with planned responses. When the uncertainty is removed—because the event has happened (or is now inevitable)—it is no longer a risk; it is an issue that needs to be captured, assessed, and progressed using the issues practice (typically via an Issue Report and appropriate decision-making/change control where relevant).
In the scenario, missed delivery dates and “100% probability risks” are clear indicators that threats have materialized, yet they are not being managed as issues, leading to unmanaged scope changes, unclear decisions, and weak reporting of what action is required and by whom. The key takeaway is to reclassify materialized risks as issues and manage them through the issue management route, not continue treating them as uncertainties.
Once an uncertain event has occurred (or is certain to occur), it must be handled as an issue requiring assessment, decision, and action.
Topic: PRINCE2 Practices
A public-sector organization is delivering a 4-month customer-portal upgrade. The Project Board can only meet monthly, but the project expects frequent minor change requests (mostly text and layout) from the Senior User group.
In the PID, the Project Board set stage tolerances of +5 working days and +$15,000, and agreed that these minor changes are unlikely to affect benefits, risk exposure, or sustainability targets. The Project Manager is asking how to tailor change approval so decisions are timely but governance remains effective.
Which tailoring approach is MOST appropriate for approving changes?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: To keep decisions timely without weakening control, the Project Board should delegate defined change-approval authority for low-impact changes. The Project Manager can then approve changes within the agreed limits and stage tolerances, while anything that breaches delegation or tolerances (or threatens the Business Case) is escalated. This applies manage-by-exception and avoids unnecessary bureaucracy.
PRINCE2 tailors change control by defining who can decide which changes, based on impact and delegated authority. In this scenario, frequent minor changes need fast turnaround and are stated not to affect benefits, risk exposure, or sustainability targets, so it is appropriate to delegate a change authority.
A practical tailoring is:
This preserves governance while avoiding delays caused by infrequent Project Board availability.
This keeps manage-by-exception by letting the Project Manager approve low-impact changes within delegated limits while reserving exceptions for the Project Board.
Topic: PRINCE2 Practices
A project is at the end of Stage 2. In the last week, one delivery team reported a 3-week delay and a cost increase, but the Project Manager has not yet consolidated the end-of-stage information. The Project Board meeting is tomorrow to decide whether to authorize Stage 3 or change direction.
What should the Project Manager obtain/confirm FIRST to support that decision?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: At a stage boundary, the Project Board needs a consolidated view of how the stage performed and what that means for the rest of the project. The End Stage Report provides that summary, including performance against the Stage Plan and tolerance status, plus updated forecasts that inform whether to authorize the next stage or redirect the project.
The End Stage Report is the Project Manager’s management product used at a stage boundary to enable the Project Board’s decision to continue, change direction, or stop. It consolidates what happened in the completed stage (progress against the Stage Plan, including tolerance status and significant issues/risks) and presents an updated outlook (forecasts for time/cost/scope/benefits and impacts on the Business Case and plans). With this information, the Project Board can judge ongoing viability and control the project by authorizing the next Stage Plan or requesting replanning/escalation if tolerances are (or will be) exceeded. Detailed team-level data may feed the report, but it does not replace the board-level, decision-focused summary.
The End Stage Report provides the Project Board with stage performance and an updated view of viability to decide whether to continue, change, or stop.
Topic: PRINCE2 Practices
During a stage, the Project Manager reviews the Risk Register and sees a risk: “External supplier may deliver the data-migration script late; trigger = supplier misses internal design sign-off date.”
Today the supplier confirms the sign-off date has been missed and the delivery will be 2 weeks late. The Stage Plan has 3 weeks of schedule tolerance remaining.
What is the MOST PRINCE2-aligned action now?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: Once the trigger has occurred and the delay is confirmed, the uncertainty has materialized and becomes an issue to be assessed and decided via issue control. Because the predicted impact is within stage tolerance, it can be handled at the Project Manager level without immediate exception escalation. Proactive risk management still matters for any remaining uncertainty, residual risk, and secondary risks.
PRINCE2 uses proactive risk management to anticipate and treat uncertainty before it happens (identify, assess, plan responses, and monitor triggers). When a threat or opportunity actually occurs, it is no longer uncertain; it becomes an issue that must be captured and handled through issue control (e.g., as an off-specification if a product or delivery will not meet what was agreed).
In this scenario, the supplier has confirmed a 2-week slip, so the risk has materialized and should be managed as an issue. Because the stage still has 3 weeks of schedule tolerance, the Project Manager can assess and decide the response within delegated authority, updating plans and records as needed. The key takeaway is: risks help you prepare; issues help you respond when reality changes.
The event has happened, so it should be handled as an issue (off-specification) using issue/change control, while risk management continues for remaining uncertainty.
Topic: PRINCE2 Processes
You have just been appointed Project Manager for a project to implement a new CRM system. The Project Brief and outline Business Case were produced in Starting up a Project.
Before you decide how to proceed with Initiating a Project (for example, what level of planning effort and supplier engagement is justified), what information should you obtain or verify FIRST?
Best answer: A
What this tests: PRINCE2 Processes
Explanation: Initiating a Project is where the project’s justification is firmed up, with the Business Case developed/updated as part of the PID. If the viability is uncertain, this should be clarified first so the amount of initiation planning and any supplier commitment is proportionate. Without a confirmed Business Case, subsequent plans and controls may be wasted effort.
In Initiating a Project, the Project Manager prepares the PID by developing/agreeing key management products, including an updated Business Case, the Project Plan (and stage breakdown), management approaches, and initial registers. The first clarifying need in an underspecified situation is whether the project remains justified, because business justification drives how much initiation effort to invest and whether it is appropriate to engage suppliers beyond pre-initiation.
A practical sequence is:
This avoids committing to delivery activities before the project’s viability is confirmed.
During Initiating a Project the Business Case is developed/updated to confirm the project remains justified before committing further planning and delivery effort.
Topic: PRINCE2 Practices
A project is implementing a new HR system. The Project Board has set project tolerances of +4 weeks and +$150,000.
The Project Manager is planning Stage 2 and will hand a Work Package to a supplier Team Manager. During delivery, the Team Manager forecasts the Work Package will be 5 working days late compared with the plan.
Select TWO statements that correctly describe how tolerances should be set in plans and monitored during delivery.
Correct answers: B, F
What this tests: PRINCE2 Practices
Explanation: In PRINCE2, tolerances are delegated limits that enable manage-by-exception. Project-level tolerances are set by the Project Board, and stage and Work Package tolerances are set and agreed at the level where the corresponding plan or authorization is issued. Monitoring focuses on whether performance is forecast to stay within tolerance, escalating by exception when a breach is forecast.
Tolerances are set at each planning level so responsibility can be delegated with clear limits. The Project Board sets project tolerances and, when approving a Stage Plan, agrees the tolerances for that stage so the Project Manager can control it day-to-day without board involvement.
Work Package tolerances are then agreed between the Project Manager and Team Manager (within the stage tolerances) so the Team Manager can manage and report progress, typically through Checkpoint Reports. Monitoring is based on comparing actuals and forecasts to the relevant tolerances; escalation is triggered when a tolerance breach is forecast, not only after it has happened. This preserves timely decision-making and avoids unmanaged exceptions.
Stage-level tolerances are set in the Stage Plan and authorized by the Project Board when approving the stage.
Work Package tolerances are agreed between the Project Manager and Team Manager so the Team Manager can manage-by-exception within delegated limits.
Topic: PRINCE2 Practices
A project is delivering a new customer portal. The current stage has tolerances of +1 week and +5% cost, and the Project Board has delegated a Change Authority to approve any change that can be implemented within these tolerances.
A Senior User submits a request to add an accessibility audit report to the portal. The Project Manager’s initial estimate is +3 days and +2% cost, with a small increase in delivery risk but improved compliance value.
What should the Project Manager do next to best protect business justification and value while keeping change under control?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: The issues practice exists to keep change and other issues controlled by ensuring they are captured, assessed against baselines and the Business Case, and then decided by the right authority. Here, the change appears to be within delegated tolerances, so the Project Manager should use formal issue assessment and route it to the Change Authority for an authorized decision before implementing.
The purpose of the issues practice is to provide a controlled way to handle any problem, concern, request for change, or off-specification so that the project’s baselines (including the plans and Product Descriptions) and the Business Case remain protected.
In this scenario the request is a potential change to scope/quality, with impacts on time, cost, risk and value. The Project Manager should:
This preserves business justification while avoiding uncontrolled scope change or unnecessary escalation.
This applies the issues practice to capture, analyse and obtain an authorized decision on the change before updating baselines or proceeding.
Topic: PRINCE2 Practices
During stage 2 of a citizen-portal project, a change request is raised to add a new encryption library to meet an updated security policy. The Team Manager says the library will replace a component already built and quality-tested, and may also affect two interfaces that the Senior User has already accepted.
Constraints:
What is the BEST next action for the Project Manager?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: Before any approval route can be chosen, the change needs an impact assessment based on what is actually built, baselined, and accepted. Configuration records provide traceability of versions and relationships so the scope of rework is clear. Quality records show what has been tested/accepted and what must be re-verified, enabling an informed change control decision.
In PRINCE2 change control, decisions should be based on evidence about the current product set and its quality/acceptance state. Configuration item records (and a product status account derived from them) identify which versions are baselined, which products are complete, and which other products/interfaces are related and therefore potentially impacted by the proposed change. Quality records (e.g., test results, approvals, quality register entries) show what has already met its acceptance criteria and what quality activities would need to be repeated or amended if rework occurs.
Using these records, the Project Manager can produce a credible impact assessment (time, cost, risk, and re-acceptance implications) and then route the decision to the Change Authority if within tolerance, or to the Project Board if it would exceed tolerance. The key takeaway is: configuration and quality records turn a change request into a controlled, evidence-based decision.
Configuration and quality records show the current versions, acceptance/quality status, and affected products needed for a justified change control decision.
Topic: PRINCE2 Processes
A project to migrate a customer billing platform is in Delivery Stage 2. Stage tolerances are ±2 weeks time and ±$50,000 cost.
The Project Manager’s latest Highlight Report forecasts a 1-week delay due to a supplier integration issue. The Project Manager proposes re-sequencing work to recover time with no additional cost and no change to agreed products.
Which action is NOT consistent with Project Board responsibilities in the Directing a Project process?
Best answer: A
What this tests: PRINCE2 Processes
Explanation: In Directing a Project, the Project Board controls by setting direction, requesting assurance, and monitoring progress against tolerances. Day-to-day control and administration, including maintaining the Risk Register and Issue Register, sits with the Project Manager. Because the forecast remains within tolerance, the Board can continue to direct and monitor without taking over management actions.
The Project Board’s role in Directing a Project is to provide overall direction and control at the right level: authorize key points (stages/exception responses), monitor progress via reports, give ad hoc direction, and ensure appropriate assurance is being performed. The Project Manager is accountable for day-to-day control, including recording and managing risks and issues, taking corrective actions within delegated tolerances, and keeping management products such as registers up to date.
Here, the forecast delay is within stage tolerance, so the Board should remain in a directing posture (monitor, request assurance, and provide guidance if needed) rather than performing project management administration. The key takeaway is to keep the Board focused on governance and decisions, while the Project Manager maintains control records and implements agreed actions within tolerance.
Maintaining project registers is a Project Manager responsibility, not the Project Board’s, even when the Board is directing and monitoring.
Topic: PRINCE2 Practices
You are the Project Manager for a project to implement a new online appointment booking system. During initiation, a risk has been logged and assessed.
Exhibit: Risk Register entry (excerpt)
ID: R-07
Risk: Data migration scripts may fail in live cutover
Probability: High Impact: High Proximity: 6 weeks
Response: TBC
Risk owner: TBC
Status: Assessed
What should you do NEXT, based on the exhibit?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: The exhibit shows the risk has been identified and assessed (probability, impact, proximity) but the response and ownership are still “TBC”. In the PRINCE2 risk management procedure, the next step after assessment is to plan the response, including selecting actions and assigning a risk owner and actionees, and recording these in the Risk Register.
PRINCE2 uses a simple risk management procedure: identify, assess, plan, implement, and communicate. In the exhibit, the risk statement and assessment fields are complete, and the status is “Assessed”, which indicates the project understands the level and timing of the threat. The missing information is the planned response and accountability.
The appropriate next step is to:
Communication and escalation may follow, but planning the response is the immediate next action indicated by the register entry.
The risk is already identified and assessed, so the next step is to plan and record responses with ownership.
Topic: PRINCE2 Practices
A Project Board complains that decisions on change requests are slow and often lead to rework. The Project Manager’s Issue Reports mainly describe the problem and proposed fix, but do not explain how the issue would affect the approved plans and intended outcomes. Scope changes continue to be approved, then reversed when impacts emerge later.
Which additional information should the Project Manager include to properly assess the issue’s impact on time, cost, scope, quality, risk, and benefits?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: To judge an issue, PRINCE2 expects impact information that relates directly to the project baselines and intended benefits. That means quantifying effects on plans (time/cost), defining what products and quality criteria would change (scope/quality), updating risk exposure, and stating any impact on benefits/Business Case. Without this, decisions are delayed and reversals/rework are likely.
In the Issues practice, the key to effective decision-making is providing enough information to evaluate an issue’s impact across the project’s key performance areas. In this scenario, the Board is forced to decide with only a description of the problem and proposed fix, so impacts surface later as reversals and rework.
The Project Manager should ensure the Issue Report (or supporting analysis) includes:
Symptom reporting may be useful for lessons, but it does not replace impact analysis needed for control and authorization.
A decision-ready Issue Report needs impact against time, cost, scope, quality, risk, and benefits so the Board can compare against tolerances and the Business Case.
Topic: PRINCE2 Principles
A Team Manager tells the Project Manager that a key component may need to be replaced with an alternative that “should work” but could change the delivery approach. The Team Manager asks who must approve the change before they proceed. No impact assessment has been provided (cost, schedule, scope, or expected benefits).
What should the Project Manager obtain or verify FIRST to decide the correct approval route in PRINCE2?
Best answer: B
What this tests: PRINCE2 Principles
Explanation: In PRINCE2, decision-making is delegated to the Project Manager within agreed tolerances and escalated to the Project Board only by exception. Before deciding who approves a change, the Project Manager must first understand whether it would cause a forecast breach of stage tolerances. That information determines whether the Project Manager can decide or must refer upward.
PRINCE2 governance uses manage-by-exception: the Project Board sets direction and delegates day-to-day control to the Project Manager within agreed tolerances. When a potential change arises from delivery (often via a Team Manager), the Project Manager should first establish its likely impact so they can determine whether it remains within their delegated authority.
A practical first check is: will the forecast impact breach stage tolerances (time, cost, scope, quality, risk, benefits)? If it stays within tolerance, the Project Manager can handle it using the project’s change control approach and update plans/controls as needed. If it is forecast to exceed tolerance, the Project Manager must escalate to the Project Board using an exception path (e.g., Exception Report and a decision).
Supplier choice and task assignments are not the starting point for deciding approval authority.
Approval authority depends on whether the forecast impact stays within the tolerances delegated to the Project Manager or must be escalated to the Project Board by exception.
Topic: PRINCE2 Processes
A project is at the end of its final management stage. The Project Manager has confirmed the specialist products have been handed over and accepted, any remaining issues have been captured as follow-on actions, and lessons have been recorded. The Project Board now asks for evidence that the project can be closed and that the overall justification/outcome is understood before making the closure decision.
Which management product should the Project Manager provide?
Best answer: C
What this tests: PRINCE2 Processes
Explanation: Closing a Project ensures products are accepted and handed over, open items are not left unmanaged, and the Project Board has a clear view of what was delivered versus what was planned and why. The management product that provides this end-to-end evidence and supports the closure decision is the End Project Report.
The purpose of Closing a Project is to provide a controlled end to the work and enable the Project Board to make an informed decision to close. Before recommending closure, the Project Manager should check that the acceptance and handover of products are complete, that any remaining risks/issues are closed or transferred into follow-on actions, and that lessons are captured for future work.
The End Project Report is produced specifically to support the closure decision by summarizing what was delivered, performance against the baselines, the final status of scope/quality, and any follow-on actions and lessons. It gives the Project Board the consolidated evidence needed to confirm acceptance readiness and continued business justification at project end.
It consolidates closure checks and overall performance/justification so the Project Board can decide to close the project.
Topic: PRINCE2 Practices
Midway through delivery, a new regulatory requirement means an extra reporting feature is needed. The Project Manager wants to assess the change impact and knows that, if approved, some documents must be updated under change control because they are used as reference points for measuring performance.
Which statement best reflects what a PRINCE2 baseline is and which management products commonly form baselines on this project?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: In PRINCE2, a baseline is an approved version of a management product that becomes a stable reference point for control and measurement. When a change is proposed, its impact is assessed against these approved reference points, and any updates to them must follow change control. Common baselined products include the Business Case, approved plans, and Product Descriptions.
A PRINCE2 baseline is a “frozen” (approved) version of a management product used to compare actuals and forecasts against what was agreed, and to provide a controlled basis for decision-making. In the scenario, the new regulatory requirement is a change that must be assessed against what the project was approved to deliver and why.
Common baselines are:
Status reports and registers are important controls, but they are not the primary baselines used as the project’s agreed performance and scope reference points.
Baselines are approved reference points (e.g., Business Case, plans, Product Descriptions) that are only changed through formal change control.
Topic: PRINCE2 Practices
You are the Project Manager for a CRM replacement project. At the end of Stage 1 you are preparing the End Stage Report and the plan for Stage 2.
Exhibit: Business Case / delivery update (excerpt)
Baseline (PID): Selected option after initial appraisal: SaaS CRM
Cost estimate (total): \$1.20m; Benefits: \$1.80m over 3 years
Stage 2 budget: \$400k; stage cost tolerance: +/-5%
New info (supplier): licence cost +\$250k (from Stage 2)
New info (Senior User): benefits start 6 months later than baseline
Current forecast for Stage 2: \$460k
Which is the BEST action to take next?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: Initial investment appraisal selected the SaaS option at initiation, but during delivery the Business Case must be maintained to reflect current forecasts and viability. The exhibit shows a material cost increase and benefit delay, plus a Stage 2 cost forecast outside tolerance. This should trigger an updated Business Case and escalation so the Project Board can decide whether to proceed.
Initial investment appraisal is done to compare options and select the preferred approach (here, the SaaS CRM) during starting up/initiating. During delivery, PRINCE2 expects ongoing Business Case maintenance: updating forecasts for costs, timescales, and benefits, and using this to confirm continued justification.
In this scenario, new supplier pricing and delayed benefit realization change the Business Case assumptions, and the Stage 2 forecast breaches stage cost tolerance. The Project Manager should update the Business Case (e.g., revised cost/benefit forecasts and timings) and escalate for direction (typically via the End Stage Report/Highlighting and, because tolerance is forecast to be exceeded, an Exception Report) so the Project Board can decide whether to continue, change scope, or stop.
Re-appraising and selecting a different solution is a separate decision and would only follow if the Project Board directs reconsideration.
The project’s justification may have changed, so the Business Case must be updated and the Project Board asked to decide whether to continue.
Topic: PRINCE2 Principles
You are the Project Manager for a data platform upgrade. The current delivery stage (Stage 2) has a time tolerance of +1 week and cost tolerance of +$20,000 (all amounts USD).
A key supplier has reported a 3-week delay to an interface component needed for user acceptance testing. Your forecast shows Stage 2 will finish 3 weeks late but only $10,000 over budget. Project-level time tolerance is +4 weeks, so the overall project end date can still be met.
You have sent an Exception Report to the Project Board. The Executive has asked you to provide a plan for completing Stage 2, to be approved at the next Project Board meeting.
What is the BEST next action?
Best answer: B
What this tests: PRINCE2 Principles
Explanation: Stage 2 is forecast to exceed its agreed time tolerance, so the current Stage Plan can no longer be used as the approved baseline for control. After raising an exception, the Project Board requests a replacement plan for the remainder of the stage. In PRINCE2 this is an Exception Plan, submitted for approval before work continues beyond tolerance.
PRINCE2 uses manage-by-exception: the Project Board delegates day-to-day control to the Project Manager within agreed tolerances. When the Project Manager forecasts that a stage will exceed its tolerance (here, +1 week but forecast +3 weeks), the stage plan is no longer an acceptable control baseline.
In this situation the Project Manager escalates (via an Exception Report) and, when directed by the Project Board, produces an Exception Plan. The Exception Plan is a replacement for the current Stage Plan (or Project Plan, if project tolerances are forecast to be exceeded) and shows how the remaining work will be completed under revised targets for approval.
A Stage Plan for the next stage is produced at a normal stage boundary, not as the response to a stage exception.
Because stage tolerance will be exceeded, an Exception Plan must be produced to replace the current Stage Plan and seek Project Board approval.
Topic: PRINCE2 Practices
A project to implement a new digital customer portal is reaching the end of Stage 2. During the stage-end review, the Project Manager reports that a competitor launch has reduced forecast user uptake, so expected benefits are now significantly lower than in the baseline. The Project Board must decide whether to authorize Stage 3.
Who should approve the (updated) Business Case at this decision point, and what evidence should primarily support that approval?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: At a stage boundary, continued business justification is confirmed as part of the Project Board’s authorization decision. The Business Case should be updated to reflect the revised benefits forecast and reviewed alongside the stage-end performance information. The End Stage Report provides the primary evidence set for that decision.
PRINCE2 requires continued business justification, and key decision points (especially stage boundaries) are where the project’s viability is re-confirmed before committing to more spend. The Project Board is accountable for authorizing the next stage and therefore approves continuation of the Business Case at that point (the Executive owns the Business Case, but the decision to proceed is a Project Board decision).
At the end of a stage, the Project Manager provides the Project Board with the End Stage Report, which should include the updated Business Case (and other stage-end information) so the board can judge whether the project remains desirable, viable, and achievable before authorizing the next stage.
Progress reports alone are not sufficient evidence for re-justifying the project at a stage boundary.
At a stage boundary the Project Board authorizes continuation based on the End Stage Report, including the updated Business Case.
Topic: PRINCE2 Practices
A project is delivering a digital HR self-service portal. The current stage is ending and the Project Board will decide whether to authorize the next stage.
Progress information at the end of the stage shows:
What is the BEST next action for the Project Manager to support continued business justification at this stage boundary?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: At stage boundaries, authorization to continue depends on whether the project remains justified. The Project Manager should use end-of-stage progress information (actuals and updated forecasts) to update the Business Case and present it with the end-stage package so the Project Board can make an informed decision.
Continued business justification is confirmed at each stage boundary by comparing what has happened so far (actual progress, costs, and performance) with what is now expected to happen (forecast costs, timescales, risks, and benefits). The Project Manager should therefore use end-of-stage progress information to update the Business Case and include it within the end-stage information provided to the Project Board, alongside the End Stage Report and the Next Stage Plan.
Because the forecast remains within agreed tolerances, this is not an exception escalation; it is a normal stage-boundary decision point. The key is that the Board’s authorization is based on current, evidence-based forecasts rather than the original assumptions.
At a stage boundary, the Project Board needs updated progress-based forecasts in the Business Case (via the End Stage Report package) to confirm continued justification before authorizing the next stage.
Topic: PRINCE2 Practices
A project to implement a new customer self-service portal is in Starting up a Project. The Executive wants enough information to decide whether to authorize Initiating a Project.
Which statement is INCORRECT about the Business Case and the Project Brief in this situation?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: In PRINCE2, the Project Brief is an early, start-up product used to support the decision to initiate, typically containing an outline Business Case. The Business Case is the justification product that is elaborated during initiation and then kept under review and updated to reflect current viability. Therefore, making benefits measurement/realization the Project Brief’s main purpose is not aligned.
The Project Brief is created in Starting up a Project to give the Project Board enough information to decide whether to authorize Initiating a Project; it commonly contains the Project Product Description, an outline Business Case, the project approach, and initial project management team structure.
The Business Case is a separate management product that explains why the project is worth doing (costs, benefits, risks, timescales, and alignment) and is developed in detail during initiation and then maintained and reviewed throughout the project to confirm continued justification. After initiation, the PID becomes the primary baseline for managing the project, reducing reliance on the Project Brief.
The closest trap is confusing early start-up information (Project Brief) with ongoing justification and benefits thinking (Business Case).
Defining and managing benefit measurement/realization sits with the Business Case (and related benefits approach), not as the main purpose of the Project Brief.
Topic: PRINCE2 Practices
A government department is delivering a new online licensing service. The Project Board set a sustainability objective to reduce the solution’s annual hosting energy use compared with the current service.
Mid-stage, a supplier proposes an analytics feature that would increase compute consumption. The Project Manager must forecast the impact and enable the Project Board to make an informed trade-off decision at the next progress review.
Which PRINCE2 response is the BEST match?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: A Sustainability Management Approach sets out how sustainability objectives will be achieved, measured, and reported, including who uses the information and when. By defining indicators (for example, energy-use measures) and integrating them into progress reporting and forecasting, it enables consistent, evidence-based trade-offs. This gives the Project Board the information needed to balance benefits with sustainability impacts.
The Sustainability Management Approach explains how the project will manage sustainability as part of normal control: the sustainability objectives/targets, the measures and data sources to monitor them, how they will be reported in progress controls, and who is accountable for reviewing and acting on the information. In this scenario, the Project Manager needs a consistent basis to forecast the impact of the proposed analytics feature and present decision-ready information to the Project Board. Using (and updating if required) the Sustainability Management Approach ensures the sustainability impact is assessed against agreed measures and fed into progress reporting, supporting informed trade-offs rather than ad-hoc judgments. The key takeaway is that it is the project’s agreed “rules of engagement” for sustainability decisions and reporting.
It provides agreed sustainability targets, measures, and reporting so progress forecasts can support informed decisions and trade-offs.
Topic: PRINCE2 Practices
During delivery of Stage 2 of a customer-portal project, the Project Manager learns that a key supplier component will arrive 5 working days late and will add $12,000 of expediting cost. Stage 2 tolerances set by the Project Board are: time \(+10 working days / -0\) and cost \(+\$40,000 / -\$0\). All other stage products and benefits remain achievable.
What is the most likely near-term impact on governance and controls?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: Because both the time and cost impacts remain within the stage tolerances agreed by the Project Board, the Project Manager can continue to control the stage without triggering management-by-exception. The appropriate near-term governance action is to update forecasts and communicate through routine reporting rather than escalating for an exception decision.
PRINCE2 uses tolerances to enable manage-by-exception. The Project Board delegates authority to the Project Manager within agreed tolerances for each stage (e.g., time and cost). Here, the forecast delay (5 days) is within the +10-day time tolerance and the extra cost ($12,000) is within the +$40,000 cost tolerance, and there is no stated threat to benefits or stage viability.
Therefore the Project Manager should:
Escalation via an Exception Report (and then an Exception Plan if requested) is only needed when forecasts exceed tolerance or threaten continued business justification.
The forecast deviation is within stage tolerances, so the Project Manager manages it and keeps the Board informed without escalating an exception.
Topic: PRINCE2 Practices
A project is delivering a new customer portal. Near the end of the current stage, market analysis shows expected annual benefits will be 25% lower than assumed, and the main supplier has proposed a design change that would increase whole-life operating energy use.
The Project Board will decide whether to authorize the next stage at the stage boundary review. The Project Manager wants to ensure the project’s continued business justification is evidenced using the correct PRINCE2 management products.
What is the BEST next action?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: At a stage boundary, the Project Board needs up-to-date evidence that the project remains worthwhile. The Business Case captures the revised justification (including dis-benefits such as higher energy use), and the Benefits Management Approach shows how benefits will be tracked and realized. Updating these within the PID provides the controlled baseline for the authorization decision.
The Business Case practice requires that continued business justification is reviewed and kept current, especially when forecasts change or new dis-benefits emerge. In this scenario, reduced benefits and higher operating energy use directly affect whether the project is still desirable, viable and achievable.
The Project Manager should therefore update the management products that evidence and govern business justification:
Plans and Product Descriptions may also need updates, but they do not replace the Business Case evidence needed for the Project Board’s go/no-go decision.
These products support continued business justification by showing the updated value, dis-benefits and how/when benefits will be measured and realized.
Topic: PRINCE2 Practices
A project is developing a new customer self-service portal with an external supplier. During delivery, the Senior User repeatedly rejects completed screens as “not usable enough”, while the Senior Supplier argues the work meets the contract’s “standard build”. Decisions on acceptance are delayed, the team reworks the same products multiple times, progress reporting is disputed (“done” vs “done-done”), and many change requests are raised to “clarify” what is in scope.
In PRINCE2 terms, what is the MOST likely underlying cause?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: The pattern points to a systematic mismatch in what “acceptable quality” means to customer and supplier. In PRINCE2, quality expectations must be translated into clear acceptance criteria and quality methods in the relevant product descriptions and agreed by the appropriate authorities. If this baseline is missing or weak, acceptance decisions drift, rework repeats, and “done” becomes subjective.
This scenario shows persistent disagreement about whether products meet quality, leading to repeated rework and delayed acceptance. In PRINCE2, the Quality practice prevents this by capturing customer quality expectations and translating them into measurable acceptance criteria and agreed quality methods (e.g., reviews, testing, usability/accessibility checks) within the Project Product Description and lower-level Product Descriptions. These definitions should be agreed early (and kept under change control) so the Senior User and Senior Supplier share the same “definition of done” and can make timely acceptance decisions.
When quality criteria are unclear or not baselined:
The core issue is weak/unaligned product definition for quality, not a generic communication problem.
Without agreed quality criteria/methods, user and supplier apply different standards, causing rework, delayed acceptance, and scope churn.
Topic: PRINCE2 Practices
A project is replacing an organization’s payment gateway. In a risk workshop, the team rated “integration with legacy fraud service fails” as low probability because “the supplier has done this many times”. The Project Manager suspects anchoring/optimism bias and the Project Board wants objective evidence that overall exposure is within the agreed risk appetite before approving the next stage.
Which management product is the best evidence to validate this decision?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: The Project Board needs evidence specifically about risk exposure and whether it remains within risk appetite. A Risk Report is designed to provide an objective, decision-focused view of key risks, changes, and overall exposure, enabling independent challenge of biased probability/impact ratings before authorizing the next stage.
Decision biases in risk assessment (e.g., anchoring on a supplier’s confident estimate or optimism bias) are reduced by using structured, transparent evidence and independent challenge. For a Project Board authorization decision, the most appropriate PRINCE2 product is a Risk Report because it consolidates and communicates the current risk picture for governance: key risks, their assessed levels, changes since the last report, and the overall exposure compared with the project’s agreed risk appetite/tolerances. This gives the Board a basis to question assumptions, request supporting data, or adjust responses without waiting for an exception situation.
A Highlight Report and Checkpoint Report focus on progress/status, while an Exception Report is only triggered when a forecast breach of tolerance needs escalation.
A Risk Report summarizes current risk exposure and trends (from the Risk Register) for the Project Board to compare against risk appetite and challenge biased assessments.
Topic: PRINCE2 Practices
A project is developing a customer portal. A change request proposes replacing the authentication component with a newer library to address a security concern.
Before deciding whether to approve the change, the Change Authority asks for evidence of the current authentication component’s exact version and whether it has already passed its quality checks and been accepted.
Which management product is the BEST evidence to provide?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: To decide on approving a change, the Change Authority needs verifiable information about what is currently built and controlled (version and status) and whether it has met its quality/acceptance criteria. The configuration records provide product and version status, and the quality records provide objective evidence of completed checks and acceptance readiness. Together they support a robust change control decision.
Change control decisions should be based on controlled, auditable information about the affected products. Configuration records (such as a Configuration Item Record) show what version of a product is currently under configuration control, its status (e.g., in development, baselined, released), and relationships to other products.
Quality records provide objective evidence of whether the product has met defined quality/acceptance criteria (e.g., test results, review outcomes, sign-off). When a change is proposed, using the configuration item’s current version/status and the associated quality evidence allows the Change Authority to judge whether the product is already accepted, whether rework would invalidate acceptance, and what will need re-testing and re-approval.
Reporting products like Issue Reports or Highlight Reports summarize information, but they are not the primary source of controlled product-version and quality evidence.
It identifies the current baselined version/status of the product and provides traceable evidence of completed quality checks needed for an approval decision.
Topic: PRINCE2 Practices
A PRINCE2 project is integrating a new payment gateway for an online permit service. Certification from the payment provider is due in 3 weeks and is outside the project’s control.
The Project Manager wants to record this as a risk in the Risk Register. Which risk statement is the BEST written using risk cause, event, and effect?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: A good PRINCE2 risk statement distinguishes the cause (what might trigger it), the event (what might happen), and the effect (impact on objectives). The best option uses an “if…then…” structure to show uncertainty and a clear consequence on time/cost, making it easy to assess and plan responses.
In PRINCE2, a risk is an uncertain event that, if it occurs, will affect objectives. Writing it as cause–event–effect improves clarity and makes analysis easier (probability relates mainly to the cause and event; impact relates to the effect).
A strong statement typically follows:
The best statement keeps these distinct and avoids turning the risk into an issue (something already happening) or into a response action.
Key takeaway: describe uncertainty and impact, not the solution.
It clearly separates an external cause, the uncertain event, and the project impact (effect) in one statement.
Topic: PRINCE2 Practices
A project is delivering a new customer portal. During a stage, the Senior User requests an additional “guest checkout” feature. The Project Manager has captured it as a request for change and completed an impact assessment (cost, schedule, risks, and benefits). The Change Authority will decide whether to approve and implement the change.
Which management product is the best evidence to provide to the Change Authority to support this decision?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: A request for change is assessed and then presented to the decision-maker with sufficient detail to decide and authorize implementation. The management product designed to capture the issue, its impact, and the recommended action is the Issue Report. This provides the needed evidence trail from capture through decision.
In PRINCE2 issue and change control, a request for change is first captured and logged, then assessed for impact (e.g., cost, time, risk, benefits), and finally submitted to the appropriate authority (Change Authority or Project Board) for a decision and, if approved, implementation. The Issue Report is the product used to present a specific issue/change with its impact assessment and recommendation so that the decision-maker can approve, reject, defer, or ask for more information. The Issue Register is mainly a tracking log, while regular progress reports (highlight/checkpoint) are not designed to support formal change decisions with full impact analysis. The key takeaway is to match the product to the control need: decision support for a specific change requires an Issue Report.
It documents the change request with impact analysis and a recommended decision for the decision-maker.
Topic: PRINCE2 Practices
A Project Manager is about to authorize a Work Package to an external Team Manager to build and test an API for a new customer portal. The Work Package defines the required products and references Product Descriptions that include quality criteria (code review, automated tests, security scan).
Before authorizing the Work Package, the Project Manager wants the best evidence that these quality activities have been planned and integrated into the team’s schedule (with tasks, dates, and effort) so progress can be monitored.
Which management product should the Project Manager request?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: To validate that quality activities are planned into the schedule, the Project Manager needs the team’s detailed plan of work. The Team Plan is where tasks such as reviews and testing are explicitly scheduled and resourced, allowing monitoring against the Work Package and stage tolerances.
Quality activities must be planned as part of the work, not treated as optional checks at the end. In PRINCE2, Product Descriptions define the quality criteria and quality methods, but the scheduling of the quality work (e.g., review sessions, test execution, rework) is shown in the plan that breaks the work down into activities. When the Project Manager needs evidence that the team has integrated those quality activities into its schedule for a Work Package, the Team Plan is the most direct management product because it details tasks, sequencing, effort, and dates at delivery-team level.
The Work Package sets what is to be done and the constraints/reporting; the Team Plan demonstrates how the team will perform the work, including quality activities, within those constraints.
A Team Plan provides the team-level schedule where quality activities are included as planned tasks with timing and effort.
Topic: PRINCE2 Principles
A project to implement a new customer self-service portal is starting delivery. The Project Manager finds that the Team Manager has only a task list and intends to begin build work immediately. The Senior User says they will “know it when they see it” and has not agreed any acceptance criteria.
Which action is INCORRECT according to the PRINCE2 principle of focus on products?
Best answer: C
What this tests: PRINCE2 Principles
Explanation: PRINCE2 focuses planning and control on defined products, using product descriptions and agreed acceptance criteria to make “done” objective. In this scenario, beginning build work without agreed acceptance criteria undermines quality planning and makes acceptance subjective. The incorrect action is the one that postpones acceptance criteria until after delivery work has started.
The PRINCE2 principle of focus on products requires the project to define and agree products before committing significant work, so progress and quality can be managed against clear outcomes rather than activities. Product descriptions capture what is to be delivered and how it will be checked (including quality criteria and quality methods), while acceptance criteria define what must be true for the customer to accept the final product.
Applied here, the Project Manager should ensure acceptance criteria are agreed with the Senior User (and documented, typically in the Project Product Description) and that key product descriptions exist early enough to shape Work Packages and quality controls. Starting build while deferring acceptance criteria encourages subjective evaluation and late rework, which is the opposite of product-based planning and control.
This breaks product focus by delaying agreed acceptance criteria and product descriptions, increasing rework and acceptance risk.
Topic: People in Successful Projects
A project is delivering a new HR self-service portal for 3,000 employees. At the end of Stage 2 (pilot), several regional managers say the portal will increase workload and may not be adopted unless workflows are changed.
The Project Board is about to decide whether to authorize Stage 3 rollout and wants evidence that stakeholder support and engagement are sufficient to keep the Business Case viable.
Which management product is the BEST evidence to review at this stage boundary?
Best answer: C
What this tests: People in Successful Projects
Explanation: At a stage boundary, continued justification depends not only on cost/time performance but also on whether stakeholders will accept and use the outputs so benefits remain achievable. The best evidence for this is the current stakeholder analysis and engagement status. That information is maintained and updated in the Communication Management Approach and should be reviewed when seeking authorization for the next stage.
Stage boundary decisions rely on whether it is still sensible to invest in the next stage (continued business justification). In this scenario, the risk is poor adoption driven by key regional managers, so the Project Board needs consolidated, current stakeholder information.
The Communication Management Approach is where the project maintains and updates:
Reviewing the updated approach provides the most direct evidence that stakeholder readiness and commitment are being actively managed, which underpins realistic benefit realization.
It contains the current stakeholder analysis and engagement/communication effectiveness needed to judge whether adoption (and hence benefits) remains realistic.
Topic: PRINCE2 Processes
A project is nearing the end of Stage 2. The Project Board has asked the Project Manager to recommend whether to authorize Stage 3, but the only information currently available is a set of Checkpoint Reports from Team Managers.
What should the Project Manager obtain/prepare FIRST before making a recommendation to the Project Board?
Best answer: C
What this tests: PRINCE2 Processes
Explanation: Managing a Stage Boundary starts by consolidating what happened in the current stage so the Project Board can make an informed authorize-or-stop decision. The End Stage Report provides that performance picture and becomes the basis for preparing the next Stage Plan and updating the Business Case and Project Plan for approval.
In Managing a Stage Boundary, the Project Manager must give the Project Board enough evidence to decide whether to authorize the next stage (or request an exception/stop). The first step is to assemble an objective view of how the current stage performed against its Stage Plan (progress, costs, quality results, issues/risks, and tolerance status). That is captured in the End Stage Report, which then informs the key stage-boundary outputs:
Registers (risk/quality) and team-level status data may feed this, but on their own they do not provide the integrated stage-end picture needed for the decision.
It provides the consolidated view of stage performance needed to update the Business Case and Project Plan and to justify the next Stage Plan request.
Topic: PRINCE2 Practices
A city council is running a PRINCE2 project to launch a digital permits portal. The project has two delivery stages:
The Project Board wants benefits governance, but the project is small and must avoid unnecessary bureaucracy. What is the MOST appropriate tailoring of Business Case-related management products/controls to distinguish benefits expected during the project from benefits realized after project closure?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: Benefits in PRINCE2 are forecast and justified through the Business Case while the project is delivering outputs, then measured through planned benefit reviews once outcomes can be observed (often after closure). Here, some benefits can start during Stage 1, but most are only measurable months after handover. Tailoring should therefore keep lightweight forecasting during the project and explicitly schedule/assign post-project benefit reviews.
The key distinction is that during the project you typically manage and report expected benefits (forecasts linked to planned outputs, adoption and leading indicators), while many realized benefits can only be confirmed after the project has transitioned products into use.
In this scenario, tailoring should:
This preserves continued business justification without turning delivery reporting into benefits-accounting.
This keeps benefits as forecasts during delivery while planning separate, owned reviews to measure realized benefits after handover and closure.
Topic: PRINCE2 Practices
Halfway through a PRINCE2 project to implement a new customer service platform, the Senior User tells the Project Manager: “We’ve already achieved a 15% reduction in average call handling time, so we should close the project early and release the remaining budget.”
The Project Manager is unsure whether this is an expected benefit during delivery or a benefit that should only be realized and confirmed after the project has closed.
What should the Project Manager obtain/verify FIRST before advising the Project Board?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: Before acting on a claimed benefit, the Project Manager needs the baseline definition of that benefit and its measurement timing. The benefits profile (supported by the Business Case/benefits management approach) distinguishes benefits expected during the project from benefits realized and confirmed after closure through benefits reviews. Without that, “15% achieved” cannot be interpreted reliably for governance decisions.
In PRINCE2, the Business Case defines expected benefits and typically includes (or is supported by) a benefits profile showing each benefit’s measurement method, timing, and owner. Some benefits are expected to start during delivery (e.g., early releases), while others are only realized and confirmed after the project closes via planned benefits reviews.
Here, “15% reduction” could be an early, partial indicator, a temporary effect, or a benefit that was only planned to be measured post-project. The first clarification is therefore to check the benefits baseline:
Only after that can the Project Manager meaningfully advise on early closure or continued investment.
This clarifies whether the improvement is an expected in-project benefit or a post-closure realized benefit and what evidence is valid at this point.
Topic: PRINCE2 Practices
You are the Project Manager for a customer-portal upgrade. The current stage has a time tolerance of +5 working days.
Exhibit: Checkpoint Report (excerpt)
Work Package: Self-service UI screens
Baseline WP end date: June 20
Forecast WP end date: June 23
Scope/quality changes: None (10 screens as agreed)
Reason: Extra accessibility review effort
New issues/risks: None
What is the BEST next action?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: The exhibit shows a schedule variance but no change to agreed products, quality, or scope. Because the forecast delay is within the stage time tolerance, it should be handled as a planning update (update actuals/forecast and continue to monitor). Baselines support control by providing the reference to measure deviation and decide whether escalation is needed.
Change control is used to assess and decide on proposed changes to agreed baselines (typically scope, quality, or other baselined products), such as requests for change and off-specifications. Here, the Work Package products are unchanged and the only information is an updated forecast end date.
Use the baselined dates as the control reference:
In this case, a 3-day slip is within the stage’s +5-day tolerance, so it is managed as a planning update rather than formal change control.
This is a planning update within tolerance with no change to baselined scope/quality, so the plan is updated for forecasting and control without invoking change control.
Topic: PRINCE2 Practices
A project is delivering a new self-service portal for a call centre. The portal has passed all quality checks defined in the Product Description and the results are recorded in the Quality Register. A user representative has completed UAT and says the portal is “good to go”.
The Project Manager is preparing to confirm product acceptance so the project can close. The Senior User is unavailable this week and asks the Project Manager to “just sign off acceptance” to avoid delay.
What is the BEST PRINCE2-aligned action?
Best answer: D
What this tests: PRINCE2 Practices
Explanation: Quality control evidence shows whether products meet their defined quality criteria, but acceptance is a governance decision. In PRINCE2, the Senior User is accountable for confirming that the delivered product is acceptable for use (against the agreed acceptance criteria), unless that authority is explicitly delegated. The Project Manager should therefore obtain a formal acceptance decision rather than signing it personally.
PRINCE2 separates checking quality from accepting a product. Quality control confirms conformance to the Product Description’s quality criteria and produces records (for example in the Quality Register), which the Project Manager can review and report. Product acceptance is a decision that the product meets the agreed acceptance criteria and is fit for operational use; accountability for that decision sits with the Senior User on the Project Board (acting for those who will use, operate, and benefit).
If the Senior User is unavailable, acceptance can only be made by someone else if the authority is formally delegated and understood (and then recorded). Otherwise, the Project Manager should wait for the Senior User’s decision and document the acceptance as part of closure evidence.
Independent assurance supports confidence in the decision, but it does not replace the accountable acceptance authority.
Acceptance decisions are accountable to the Senior User (Project Board), so the Project Manager must obtain their formal acceptance or documented delegation.
Topic: People in Successful Projects
A project is delivering a new digital case-management system for a public agency. In the PID, the change management approach includes user communications, training, and a readiness assessment before go-live to support adoption and benefits.
At the stage boundary, the Project Manager proposes removing most training and communications from the next Stage Plan to meet the go-live date (stage time tolerance is tight). Technical acceptance criteria for the system can still be met.
What is the most likely near-term impact?
Best answer: B
What this tests: People in Successful Projects
Explanation: Removing training, communications, and readiness work weakens confidence that users will adopt the output and that benefits will be realized. At a stage boundary, this most immediately affects governance decisions because the Project Board must be satisfied that the next stage remains justified and achievable. The likely immediate consequence is challenge, re-planning, or delayed authorization of the next Stage Plan.
Change management supports adoption by preparing people and the organization to take the project outputs into use (e.g., communications, training, readiness, operational engagement). If these actions are removed, the project may still deliver a technically acceptable product, but the ability to realize benefits becomes uncertain.
At a stage boundary, the Project Board uses the Stage Plan and continued business justification to decide whether to authorize the next stage. With adoption work stripped out, the near-term governance impact is that the Board is likely to ask for the plan to be revised (and associated impacts assessed) before allowing the stage to proceed.
This is more immediate than later effects such as delayed benefits or increased operational costs.
Without planned change management actions, the Project Board lacks confidence in adoption and benefits, so it is likely to challenge or delay authorizing the next stage.
Topic: PRINCE2 Practices
A PRINCE2 project is three days from a stage boundary. The main product for this stage (a pilot release) has failed an agreed acceptance criterion (response time must be under 2 seconds; test result is 2.5 seconds). The supplier proposes deferring the fix to the next stage to avoid delay. Fixing it now is forecast to add 1 week and $12,000. Stage tolerances are time +0 weeks and cost +$10,000. The early benefits depend on the pilot meeting the performance criterion.
What is the BEST next action?
Best answer: C
What this tests: PRINCE2 Practices
Explanation: The forecast time and cost overrun exceeds the stage tolerances, so the Project Manager must escalate as an exception. Because the issue also affects product acceptance and planned benefits, the Project Board (with the Executive accountable for business justification) must decide whether to accept, rework, or re-plan and authorize any Exception Plan.
In PRINCE2, the Project Board delegates day-to-day control to the Project Manager within agreed tolerances and makes decisions when an exception is forecast. Here, the performance failure threatens product acceptance (Senior User interest) and the expected early benefits, and the forecast fix exceeds both time and cost stage tolerances. The Project Manager should therefore escalate using an Exception Report, presenting options and impacts so the Project Board can decide and (if appropriate) authorize an Exception Plan.
Key accountabilities applied:
The key takeaway is that tolerances drive escalation and the Project Board retains decision-making authority beyond them.
Forecast breach of stage tolerances and a key acceptance/benefits impact requires Project Board direction (led by the Executive) under manage-by-exception.
Topic: People in Successful Projects
Midway through a stage, the main supplier proposes adding an AI module to the new CRM system. The Senior User supports it, but Finance says the extra cost may remove the expected return. No one has yet provided an updated view of whether the project is still justified.
As Project Manager, what should you verify/obtain FIRST before deciding how to proceed?
Best answer: A
What this tests: People in Successful Projects
Explanation: PRINCE2 assigns single-point accountability for the Business Case to the Executive to ensure one clear owner protects continued business justification. When justification is uncertain and stakeholders disagree, the Project Manager should first confirm who holds that accountability and obtain their direction on whether the project (or change) remains viable. This avoids conflicting guidance and uncontrolled commitment.
The core issue is continued business justification: adding scope may change costs, timescales, and benefits, and stakeholders are giving conflicting signals. In PRINCE2, the Executive is accountable for the Business Case, providing a single point of accountability so that viability is owned, assessed consistently, and decisions are not diluted across multiple interests.
Before committing to plans or criteria, the Project Manager should:
This establishes clear decision authority for the project’s justification before detailed solution work proceeds.
The Executive is the single point of accountability for the Business Case, so their confirmed ownership and view on continued justification must drive next steps.
Topic: PRINCE2 Processes
You are the Project Manager preparing for the stage boundary at the end of Stage 2. The Project Board set the following tolerances:
Exhibit: End Stage Report (excerpt)
Stage 2 actual: +4 working days; +\$20,000
Approved project budget: \$900,000
Forecast at completion (EAC): \$1,030,000
Forecast completion: +3 weeks vs baseline
Business Case: benefits unchanged; costs increasing
Based on this exhibit, what is the BEST next action at this stage boundary?
Best answer: B
What this tests: PRINCE2 Processes
Explanation: At a stage boundary, actuals confirm what happened, and the latest forecast indicates whether the project can still remain within agreed tolerances. The exhibit shows Stage 2 is within stage tolerance, but the forecast at completion exceeds project tolerances for both time and cost. This requires escalation to the Project Board using exception management rather than routine approval of the next Stage Plan.
In Managing a Stage Boundary, the Project Manager uses actual performance (End Stage Report) and the updated forecast for the rest of the project to decide whether planning can proceed normally or whether exception management is required. Here, Stage 2 actuals are within stage tolerances, but the forecast at completion shows +3 weeks and +$130,000 versus the approved baseline, breaching the Project Board’s project tolerances (+2 weeks and +$100,000). When a forecast indicates a tolerance breach, the Project Manager must escalate to the Project Board with an Exception Report and, if directed, prepare an Exception Plan covering the remaining work (replacing the next Stage Plan for approval). The key point is that forecasts, not just actuals, drive exception decisions at stage boundaries.
The end-of-stage forecast breaches project tolerances (time and cost), so the Project Board must be notified and asked to decide using exception management.
Topic: Project and PRINCE2 Key Concepts
A project is delivering a new online licensing service. The project is approaching the end of the current management stage, and the team has completed all stage products within agreed tolerances. However, a new policy change may reduce expected benefits, so the Project Board wants to decide whether to commit funding and resources for the next stage.
What should the Project Manager do next, in PRINCE2 terms, to support governance and decision making?
Best answer: D
What this tests: Project and PRINCE2 Key Concepts
Explanation: PRINCE2 uses management stages to create defined decision points where the Project Board can review viability and control continued investment. At a stage boundary, the Project Manager prepares information (notably the next Stage Plan and updated Business Case) so the Project Board can decide whether to authorize the next stage.
Management stages provide governance by breaking the project into manageable chunks and limiting the Project Board’s commitments to one stage at a time. As a stage ends, PRINCE2 uses the Managing a Stage Boundary process to give the Project Board reliable, current information to decide whether to continue, change direction, or stop.
In this scenario, the stage has finished within tolerances but the expected benefits may change, so the Project Board needs an updated view before committing further:
This is a planned decision point, not an exception situation, so the focus is on stage-boundary products that enable informed authorization.
Stage boundaries are used to provide the Project Board with an updated plan and Business Case so it can decide whether to authorize the next stage.
Topic: PRINCE2 Practices
A project is delivering a new customer self-service portal. The Project Board keeps delaying decisions on proposed changes because they ask, “Will this increase the expected benefits?” The Project Manager can only report progress against delivered features and costs; there is no agreed set of benefit measures, benefit owners, or timing for post-project reviews. As a result, change requests are debated repeatedly, priorities shift, and rework increases.
In PRINCE2 terms, what is the MOST likely underlying cause?
Best answer: A
What this tests: PRINCE2 Practices
Explanation: The core problem is not the volume of change or reporting cadence, but the inability to judge proposals against expected benefits. In PRINCE2, the Benefits Management Approach is a key management product that supports the Business Case by defining benefit measures, owners, and when/how benefits will be reviewed. Without it, the Project Board lacks objective information to make timely value-based decisions.
PRINCE2’s Business Case practice relies on management products that make the justification measurable and controllable, not just stated. Here, the Board’s repeated question is about benefits, but the project has no agreed benefit measures, owners, or review points, so each change becomes a subjective debate and causes churn.
The Benefits Management Approach supports the Business Case by setting out:
With this in place, proposed changes can be assessed consistently for impact on benefits and continued justification, enabling faster decisions and reducing rework caused by shifting priorities.
Without a Benefits Management Approach, benefits are not measurable or owned, so changes cannot be assessed against the Business Case and decisions stall.
Topic: PRINCE2 Processes
A Project Manager has authorized a Work Package to an external supplier Team Manager to build and test an API component. The work is proceeding within agreed tolerances, but because the component is on the critical path the Project Manager wants regular, time-driven visibility of progress (completed products, next activities, and forecast completion) during execution.
Which is the BEST matching PRINCE2 management product for the Team Manager to produce during Managing Product Delivery?
Best answer: B
What this tests: PRINCE2 Processes
Explanation: During Managing Product Delivery, the Team Manager provides regular progress information about Work Package execution to the Project Manager. The time-driven, routine mechanism for this is checkpoint reporting, which summarizes what has been done and what is forecast next. This supports day-to-day control without waiting for an exception situation.
In Managing Product Delivery, the Team Manager’s key reporting responsibility is to keep the Project Manager informed about Work Package progress while the team develops the agreed products. When the need is regular, routine visibility (for example twice-weekly) and the work remains within tolerances, the appropriate management product is the Checkpoint Report.
This report is used to communicate status such as completed products, work in progress, any emerging problems/risks, and forecast completion, enabling the Project Manager to maintain control of the stage without escalating to exception.
Exception- and issue-driven reports are used only when something needs specific attention or decisions beyond routine progress tracking.
A Checkpoint Report is the Team Manager’s routine progress update to the Project Manager during execution of a Work Package.
Topic: PRINCE2 Practices
You are the Project Manager for a project to implement a customer self-service portal. You are reviewing the latest issue entry.
Exhibit: Issue Register entry (excerpt)
ID: ISS-22
Type: Off-specification
Summary: New regulation mandates a national portal; our portal adoption likely halved
Impact (Business Case): Expected annual benefit drops from \$600,000 to \$300,000
Business Case viability rule: NPV must remain \ge \$250,000 (benefits tolerance \pm10%)
Latest forecast NPV: \$90,000
Status: Open
What is the BEST next action?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: The exhibit shows the forecast NPV has fallen below the Business Case viability rule, so the project may no longer be justified. Under PRINCE2, when continued business justification is threatened, the situation must be escalated for a Project Board decision, rather than being handled solely within day-to-day management.
Continued business justification is a core PRINCE2 principle: the project should proceed only while there is a valid Business Case. Here, the issue’s stated impact drops forecast NPV to $90,000 against a viability requirement of at least $250,000, which indicates the Business Case is no longer viable.
The Project Manager should therefore:
Local planning actions or team-level workarounds may be useful later, but they are secondary to obtaining governance direction when justification is undermined.
The issue reduces forecast benefits so far that continued business justification is no longer met, requiring Project Board direction.
Topic: People in Successful Projects
A project is delivering a new self-service HR portal to six departments. The solution has passed acceptance tests and is planned to go live at the end of the current stage.
A pilot showed only 40% of managers are using the portal; the Business Case benefits depend on at least 80% adoption within 3 months of go-live. The Change Manager proposes extra coaching sessions and a network of “change champions”. This would add 1.5 weeks and $30,000 to the stage. The stage tolerances allow up to 2 weeks and $40,000.
As Project Manager, what should you do next to best protect business justification and value while balancing performance within tolerances?
Best answer: D
What this tests: People in Successful Projects
Explanation: Low adoption threatens realization of benefits, so change management should be used to increase user readiness and uptake. Because the proposed activities fit within stage tolerances, the Project Manager should incorporate them into the stage-level plans and approach, and ensure benefits monitoring reflects adoption measures. This protects business justification while staying within agreed time and cost limits.
Change management supports adoption by preparing, engaging, and enabling people to use the project outputs so that expected benefits are actually realized. In this scenario, the pilot data shows a significant adoption risk that directly undermines the Business Case’s benefit assumptions.
Because the additional coaching and change champion activities are within the stage tolerances, the appropriate response is to re-plan within delegated authority and strengthen the change management and benefits arrangements:
This preserves value by addressing the real constraint (adoption), rather than optimizing schedule or cost at the expense of benefits; escalation is needed only if tolerances would be exceeded.
These actions use available tolerances to address adoption risk and protect benefits realization without creating an exception.
Topic: PRINCE2 Processes
A PRINCE2 project to implement a new HR self-service portal has reached the end of its final stage. All products have been accepted and the Project Manager is preparing to close the project. The Senior User says, “We can now disband the team; benefits will take care of themselves.”
Before deciding what follow-on actions are needed to help ensure benefits are realized after closure, what should the Project Manager seek to confirm FIRST?
Best answer: D
What this tests: PRINCE2 Processes
Explanation: In Closing a Project, the project can only support ongoing benefits if there is a clear handover of responsibility for measuring and realizing them. Confirming who will maintain and execute the post-project benefits approach (including timing and reporting of reviews) is the key missing information before choosing closure follow-on actions. Without an owner, planned benefit reviews are unlikely to happen.
Follow-on actions to support benefits realization after project closure rely on governance that continues after the project management team disbands. In PRINCE2, benefits are typically realized during operations, so the Project Manager should first confirm that there is a defined owner (usually on the customer/business side) for the post-project Benefits Management Approach and the benefit review plan (what will be measured, when, and how it will be reported). Once ownership and review points are clear, the Project Manager can ensure closure outputs align to that need (for example, confirming handover, capturing any residual actions as follow-on recommendations, and ensuring the Benefits Management Approach is up to date and baselined as appropriate). The closest trap is focusing on project controls (tolerances/exceptions) rather than post-project accountability.
Ensuring benefits realization after closure depends first on confirming accountable ownership and review responsibilities beyond the project.
Topic: People in Successful Projects
A project is delivering a new customer portal using an external system integrator. In the last stage, decisions about priorities and acceptance criteria are repeatedly delayed, completed components are reworked after user testing, and progress reports focus on technical tasks rather than whether user outcomes will be achieved. Scope changes are frequent because different user groups raise conflicting requests late.
The Executive says, “We have both Senior User and Senior Supplier on the Project Board, so representation is covered.”
What is the MOST likely underlying cause in PRINCE2 terms?
Best answer: A
What this tests: People in Successful Projects
Explanation: The pattern points to missing ownership of user requirements, prioritization, and acceptance. In PRINCE2, that accountability sits with the Senior User representing users’ interests, while the Senior Supplier represents the suppliers’ capability and resources. When those responsibilities are blurred or unfilled, user-driven decisions arrive late and drive rework and scope churn.
This is a people/roles root cause: the project is not getting timely, authoritative decisions on user requirements, priorities, and acceptance criteria, and reporting is not framed around realizing user outcomes. In PRINCE2, the Senior User represents the users and is accountable for defining user needs and ensuring the solution will be acceptable and deliver benefits; the Senior Supplier represents supplier interests (solution design/build capability, technical integrity, and resourcing).
When the Senior Supplier (or the Project Manager) effectively “stands in” for the Senior User, typical symptoms are:
The key fix is to clarify and enforce Senior User vs Senior Supplier responsibilities, ensuring user acceptance and benefit-focused direction is owned at board level.
If the Senior User is not clearly owning user needs and acceptance, user decisions slip, rework rises, and scope churn increases.
Topic: PRINCE2 Processes
A project to implement a new HR self-service portal has delivered all products and the Senior User has confirmed acceptance. During the final review, the Project Manager notes two open issues (minor configuration improvements) and one open risk (supplier may stop supporting an add-on within 12 months). These items are not within the agreed project scope to address, and the Project Board wants to close the project this week.
What is the MOST PRINCE2-aligned action for handling these outstanding issues and risks at project closure?
Best answer: D
What this tests: PRINCE2 Processes
Explanation: At project closure, PRINCE2 expects all issues and risks to be either closed or formally handed over with clear ownership and next steps. Because the remaining items are outside the agreed scope and the project products are accepted, the project can close while recording and transferring these items as follow-on actions for BAU or corporate/programme management to manage.
In the Closing a Project process, the Project Manager prepares to close by confirming acceptance and ensuring there is nothing left that the project must deliver. For any outstanding issues and risks that will not be resolved by the project (because they are outside scope or not justified), PRINCE2 handles them by documenting what needs to happen next and who will take responsibility after closure.
Typical closure handling is:
The key is to avoid keeping a completed project open just to monitor items that should be managed operationally or by a subsequent initiative.
At closure, unresolved items outside scope should be recorded as follow-on actions with agreed owners and handed over so the project can close.
Topic: PRINCE2 Practices
You are Project Manager for a customer self-service portal project. The Stage Plan shows these products for the next 4 weeks: “Payment gateway interface”, “End-to-end payment test results”, and “Go-live readiness report”.
A Team Manager proposes starting “end-to-end payment testing” next week to protect the schedule, even though the external supplier has not yet confirmed when the “payment gateway interface” will be available. The schedule impact is unclear.
Before you decide how to re-sequence activities in the Stage Plan, what information should you obtain FIRST?
Best answer: B
What this tests: PRINCE2 Practices
Explanation: Sequencing work depends on knowing which products are prerequisites for others and any external dependency dates. Here, end-to-end payment testing may depend on the supplier-delivered payment gateway interface, so you must confirm that dependency and the interface delivery/availability before deciding whether testing can start or must be re-planned. Only then can you create a feasible activity network and schedule.
In PRINCE2 planning, activities are sequenced to deliver products by identifying dependencies between the products (and any external deliverables) and then translating these into predecessor/successor links in the schedule. In this scenario, the proposed testing may be impossible or wasteful if the payment gateway interface is a prerequisite or if the supplier’s delivery date creates a hard external constraint.
A practical order is:
Tolerances, approvals, and acceptance criteria matter, but they do not tell you what can be scheduled before what.
You must first establish predecessor/successor dependencies (including the external interface date) to sequence activities realistically.
Topic: People in Successful Projects
You are the Project Manager for a PRINCE2 project to implement a new HR self-service portal across six regions. The project is mid-stage; the Project Board receives monthly Highlight Reports. A supplier Team Manager provides weekly Checkpoint Reports to you.
Two weeks before the stage boundary, the Senior User reports that regional HR managers and the staff union are hearing rumours and are resisting upcoming process changes. There is also a high data-privacy risk, so detailed issue information cannot be broadcast widely.
What is the BEST next action?
Best answer: C
What this tests: People in Successful Projects
Explanation: The immediate issue is ineffective stakeholder engagement: key groups are not receiving appropriate, timely information, and misinformation is driving resistance. In PRINCE2, the Project Manager should define and tailor who needs what information, when, and how, and agree this with the appropriate project governance. Updating the Communication Management Approach with the Senior User ensures user-facing groups get the right messages without breaching data-privacy constraints.
Different stakeholder groups need different levels of information, delivered through controlled PRINCE2 channels. Here, the Senior User is best placed to help identify and represent user-side stakeholders (regional HR managers, union, end users) and clarify what information they need (impacts, timing, training/transition, acceptance criteria), while the Project Manager updates the Communication Management Approach so communications are planned, consistent, and sensitive to data privacy.
A good next step is to:
This addresses resistance proactively without bypassing roles or oversharing sensitive issue detail.
This targets the right stakeholder groups and information needs while keeping communication under agreed PRINCE2 controls and sensitivities.
Topic: PRINCE2 Processes
You are the Project Manager for a two-stage project to implement a new customer portal. Stage 1 is nearing completion and the project is due to move into Stage 2 (build and rollout).
In the last week, a supplier advised that their hosting service will be replaced with a newer platform during Stage 2, but has not provided details. The Senior User is asking the Project Board to decide quickly whether to proceed into Stage 2, pause to reconsider options, or stop the project.
As you prepare to manage the stage boundary, what information should you obtain FIRST to support the Project Board’s decision?
Best answer: C
What this tests: PRINCE2 Processes
Explanation: Managing a stage boundary exists to give the Project Board reliable information to decide whether to authorize the next stage, request changes, or stop the project. The quickest way to ground that decision in this scenario is to update the Business Case with the supplier-driven change and the resulting forecast of benefits, costs, and risks for Stage 2.
In PRINCE2, Managing a Stage Boundary is a control point where the Project Manager updates key forecasts and prepares information so the Project Board can decide to continue, change direction, or stop. In this scenario, the supplier platform change could materially affect costs, timetable, risks, and the ability to realize benefits, so the first thing to confirm is whether the project remains viable and desirable.
To support that decision, the Project Manager should:
Lessons and communications may be useful, but they do not provide the viability evidence needed for a go/no-go stage authorization decision.
Managing a stage boundary primarily enables the Project Board’s go/no-go decision using updated forecasts of continued viability.
Use the PRINCE2 Practitioner Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Read the PRINCE2 Practitioner guide on PMExams.com for concept review, then return here for PM Mastery practice.