What You Must Know to Pass the Practitioner Exam
Understanding the difference between an issue and a change in PRINCE2 7the Edition is one of the most critical skills you need to pass the Practitioner exam. It is also one of the top reasons candidates struggle or fail. Even experienced project managers can find themselves confused when exam scenarios blend real-world terminology with PRINCE2 definitions.
This confusion is completely understandable. Many organisations use the words “issue”, “risk”, “change request” and “problem” interchangeably, but PRINCE2 uses each term very precisely.
The 7th Edition, released with a clearer focus on adaptability and practical use, tightened these definitions even further. As a result, many candidates still preparing with older habits or outdated materials fall into avoidable traps.
This article explains in clear non-cryptic language how to distinguish PRINCE2 7 Issues from Changes, how the four issue types work, and how to apply this knowledge correctly in the Practitioner exam. By mastering this single topic, you give yourself a significant advantage over other candidates and show your employer that you understand structured governance at a professional level.
Why Candidates Struggle with Issues and Changes
The misunderstanding normally comes from three sources.
Legacy definitions from previous versions
Earlier editions of PRINCE2 (including 2009 and 2017) explained “issues” in similar but not identical ways. PRINCE2 7 clarifies the topic, adds modernised examples and places stronger emphasis on governance. Many training providers still recycle older materials, which does not help the candidate.
Misinterpreting the four issue types
PRINCE2 7 defines four types of issue:
Request for Change, Off-specification, Problem or Concern, and a general or uncategorised issue.
Most exam mistakes occur because the candidate jumps at the wrong category without examining the scenario fully.
Everyday workplace language conflicts with PRINCE2
In many organisations, a “change” may simply mean “something is going wrong”, while an “issue” might refer to a formal request. PRINCE2 uses these terms differently, and the exam expects you to follow the PRINCE2 model, not workplace habits.
The Practitioner exam deliberately tests your ability to recognise these distinctions. Questions often hide the category within a scenario, so clarity is essential.
The Four PRINCE2 7 Issue Types – Clearly Explained
Getting these four types fully understood is central to passing the exam. Here they are in clear, real-world language with examples.
Request for Change (RFC)
A Request for Change is a proposal to modify a baseline product or requirement. It does not mean anything has failed or gone wrong. It is simply a suggestion to alter something.
Example:
A stakeholder requests an extra automated report in a new HR system. The project is working correctly, but they want additional functionality.
Exam tip: If the request is voluntary, forward-looking or enhancement-related, it is almost always a Request for Change.
Off-Specification
An off-specification is something the project is required to deliver but currently cannot or will not. This is usually linked to performance issues, design faults, supplier failures or incorrect assumptions.
Example: A contractor informs you they cannot deliver the compliance reporting module that is specified in your Project Product Description.
Exam tip: If a required product or requirement cannot be delivered as originally agreed, it is an off-specification. This is one of the most commonly misidentified issue types in the Practitioner exam.
Problem or Concern:
This is the broadest of the four categories. It covers anything that is worrying the project team, any unexpected situation, or a risk that has now occurred. Problems and concerns may escalate into changes later, but they begin as issues.
Example: A team member is worried that a key subject matter expert will be unavailable next month, which may delay testing.
Exam tip: If the scenario mentions uncertainty, doubt, or emerging risk symptoms, select Problem or Concern.
General Issue (uncategorised)
PRINCE2 7 acknowledges that not every issue fits neatly into a category. You may record an issue temporarily without assigning a specific type, especially when the facts are incomplete.
Example: Two stakeholders disagree about how a new dashboard should function, but neither has made a formal request and no requirement is breached yet.
Exam tip: Use this category only when nothing else fits clearly.
What Counts as a Change in PRINCE2 7?
Understanding this section removes half of all exam traps!
A change in PRINCE2 is the approved result of a Request for Change, an Off-specification or another issue that triggers evaluation. A change modifies a baseline – such as scope, time, cost, quality, benefits or design.
A change only exists after assessment and approval. Before approval, it is an issue.
Change Control Steps
Identify: the issue is logged.
Assess: determine the impact on project objectives.
Decide: either the Change Authority or Project Board makes the decision.
Implement: update baselines and plans accordingly.
The Change Authority is central to PRINCE2 7. Delegating decision-making is encouraged, and the exam expects you to identify who has the authority in each scenario.
Exam trap: If the scenario simply describes a request, it is not yet a change. The change only exists once approved.
Common Practitioner Exam Traps Involving Issues vs Changes
Labelling a concern as a change
A team member raising a worry is never a change. It is a Problem or Concern.
Misclassifying supplier failures as “Problems” instead of “Off-specifications”
If the project is required to deliver something and the supplier cannot provide it, that is an off specification. Many candidates miss this.
Treating tolerance deviations as changes
A deviation may or may not be a change. If it breaches tolerance, it becomes an Exception, which itself triggers escalation, not necessarily a change request.
Assuming all changes must go to the Project Board
Wrong. PRINCE2 7 encourages delegating Change Authority where appropriate. The exam tests this.
Thinking every issue generates a Request for Change
Issues may be logged and monitored without altering any baseline. An issue is not automatically a change request.
Understanding these traps dramatically improves accuracy.
Real-World Examples Clarifying Issues vs Changes
Here are three practical situations to strengthen your understanding.
Scenario 1 – IT integration failure
A planned integration between two systems cannot be built due to a vendor limitation.
Correct classification: Off-specification
The project is required to deliver this integration and now cannot
Does it trigger change control? Probably yes, because this affects scope and product delivery.
Scenario 2 – New regulatory requirement in a construction project
New legislation requires additional safety reporting not included in the original scope.
Correct classification: Request for Change
The requirement did not exist at the start, so this is a new proposal to update scope.
Does it trigger change control? Yes. It affects baselines and requires approval.
Scenario 3 – Stakeholders want added dashboard features
A manager asks for real-time updates instead of daily summaries.
Correct classification: Request for Change
This is an enhancement request; nothing is failing.
Does it trigger change control? Only once assessed and approved. Until then, it is simply an issue.
How to Answer Issue and Change Questions in the Practitioner Exam
Use this simple four-step method:
Step 1: Has something gone wrong or is someone proposing a new idea? If it is voluntary or new, it is likely a Request for Change.
If something no longer meets requirements, it is likely an Off-specification.
Step 2: Does the scenario describe a baseline deviation? If yes, you may be dealing with an exception or an off-specification.
Step 3: Is this within tolerance or above? If above tolerance, escalate to the Project Board. If within, handle at the appropriate management level.
Step 4: Should this trigger change control? Not every issue does. Only change proposals affecting baselines do. This structured approach keeps you consistent and maximises exam marks.
How Employers Benefit When You Understand Issues vs Changes
Professionals who understand PRINCE2 7 issue management and change control stand out immediately. Employers value people who:
- maintain clear governance
- reduce decision delays
- minimise rework
- communicate more effectively
- understand which issues matter and which can be handled locally
- protect baselines without unnecessary escalation
By mastering these distinctions, you show that you can handle structured project environments and support senior stakeholders with confidence.
The Way Ahead
The difference between Issues and Changes in PRINCE2 7 is more than a terminology exercise. It is a vital part of effective project control and one of the highest-value exam skills you can develop.
Misunderstanding these definitions is the most common reason candidates fail the Practitioner exam, but the topic becomes straightforward once explained clearly.
By mastering the four issue types, understanding what a change truly is, and learning to identify exam traps, you can approach the Practitioner exam with confidence and clarity.
PRINCE2® 7 Foundation and Practitioner
Learn PRINCE2® 7 Foundation and Practitioner Online
** Enhance your PRINCE2 career now **
PRINCE2® Masterclass gives you the skills necessary to manage projects effectively and achieve your objectives.
Get 7 days a week 12 months one to one coaching with ex PRINCE2 examiner Dave Litten.
PRINCE2® is a globally recognized project management framework. By completing both the Foundation and Practitioner courses through our self-paced e-learning, you will develop an understanding of the methodology and learn how to effectively adapt it to any project.
The PRINCE2® 7 Foundation and Practitioner Masterclass is PeopleCert Accredited and guarantees to take you from PRINCE2 Novice to PRINCE2 Practitioner with our famous video learning, study guides and practice exams.
What Does the Masterclass Cover?
The PRINCE2 Foundation examination assesses your knowledge and comprehension of the PRINCE2 project management methodology as detailed in the syllabus. The PRINCE2 Practitioner examination, on the other hand, gauges your ability to apply and tailor the PRINCE2 method. Candidates who pass the Practitioner exam should be able to start implementing the method on an actual project with some guidance. However, their effectiveness may differ based on their experience in project management, the complexity of the project, and the level of support they receive in their work environment.
