A Classic PRINCE2 Practitioner Exam Trap
When preparing for the PRINCE2 7th Edition Practitioner exam, there are certain topics that quietly trip up a surprising number of candidates. One of the most common is the misuse of the Issue Register when dealing with risks.
At first glance, risks and issues can feel very similar. Both describe problems that might affect the project. Both require management attention. And both appear frequently in scenario based exam questions.
But in PRINCE2 they are not treated the same way at all.
In fact, confusing the Issue Register and the Risk Register is one of those subtle mistakes that the Practitioner exam loves to test. If you get this distinction wrong, it can lead you to the wrong answer even when you otherwise understand the scenario perfectly.
Let’s unpack why this happens and, more importantly, how you can avoid the trap.
Why Candidates Confuse Risks and Issues
In the real world, many organisations use the terms risk, issue, problem, and change almost interchangeably. A project manager might hear phrases like:
- “Log that as a risk.”
- “Add it to the issue list.”
- “We’ve got a problem, track it somewhere.”
Because of this informal language, many candidates approach the exam with slightly blurred boundaries between these terms.
PRINCE2, however, is far more precise.
Each item has a specific definition, a specific register, and a specific management approach.
Understanding that distinction is essential for the Practitioner exam.
The Key Principle: Risks Are Uncertain, Issues Are Happening Now
The easiest way to anchor the difference is this.
A risk is something that might happen.
An issue is something that has already happened or is happening now.
That sounds simple, but in the pressure of an exam scenario it is easy to overlook.
Consider these two examples.
Example one:
“A supplier might miss the delivery date due to staffing shortages.”
This is a risk. It has not happened yet. It represents uncertainty and should therefore be recorded in the Risk Register.
Example two:
“The supplier has confirmed that the delivery will be two weeks late.”
This is an issue. The problem has already materialised and must now be managed through the Issue Register.
The Practitioner exam often disguises these situations inside longer scenario descriptions, which is where many candidates get caught out.
The PRINCE2 Issue Register Has a Specific Purpose
The Issue Register is not a general list of things that might go wrong.
It is used to record issues that require investigation and resolution.
PRINCE2 recognises three types of issue:
- Request for change
A stakeholder asks for a change to the project baseline. - Off specification
- Problem or concern
A general problem that needs investigation or resolution
Notice what is missing from this list.
Risks.
Risks are not logged in the Issue Register because they represent uncertainty rather than an actual situation requiring resolution.
The Risk Register Serves a Completely Different Function
The Risk Register records potential events that could affect the project.
Each risk includes information such as:
- Cause
- Event
- Effect
- Probability
- Impact
- Risk owner
- Response strategy
PRINCE2 treats risk management as a proactive activity. The aim is to identify threats and opportunities early so that action can be taken before they occur.
Once a risk actually happens, it is no longer a risk.
It becomes an issue.
This transition is another subtle detail the Practitioner exam sometimes explores.
The Scenario Trick the Exam Loves to Use
A common exam technique is to describe a situation that looks like an issue but is actually a risk.
For example, you might read something like this:
“The project team is concerned that a key supplier may not be able to provide specialist components due to financial difficulties.”
Many candidates immediately think:
“This is a problem. Log it as an issue.”
But look carefully at the wording.
The supplier may not be able to deliver. Nothing has actually happened yet.
This means it is still a risk, and it belongs in the Risk Register, not the Issue Register.
These small wording clues are exactly what the exam expects you to spot.
When a Risk Turns into an Issue
Here is where things get interesting.
In PRINCE2, risks can evolve into issues when the uncertain event actually occurs.
Let’s take a simple example.
Initially the project identifies this risk:
“The software supplier might fail to deliver the integration module on time.”
The project team records this in the Risk Register and assigns a response strategy.
Later in the project, the supplier confirms they cannot meet the agreed deadline.
At this point the uncertainty disappears.
The situation has now become a real problem.
It is no longer managed as a risk. It becomes an issue and should be logged in the Issue Register for investigation and resolution.
Understanding this lifecycle shift is very helpful in the Practitioner exam.
A Simple Way to Spot the Correct Register in the Exam
When reading a scenario question, pause and ask yourself one simple question:
Has the event already happened?
If the answer is no, you are almost certainly dealing with a risk.
If the answer is yes, you are dealing with an issue.
This small mental check can quickly steer you toward the correct answer.
It also prevents the common mistake of treating every potential problem as an issue.
The Other Boundary Candidates Often Miss: Issues vs Changes
Another exam trap is confusing an issue with a change request.
In PRINCE2, a request for change is actually a type of issue.
That means it is recorded in the Issue Register and then assessed through the change control process.
For example:
“A stakeholder requests an additional reporting feature in the system.”
This is not a risk. It is not simply a problem either.
It is a request for change, which is one of the recognised issue types in PRINCE2.
The Project Manager would log it in the Issue Register and assess its impact on time, cost, scope, and benefits.
Why the Practitioner Exam Focuses on This Distinction
You might wonder why the exam places so much emphasis on something that seems quite subtle.
The reason is that good project management relies on clear categorisation of information:
- Risks require proactive management.
- Issues require investigation and resolution.
- Changes require impact assessment and approval.
If these categories become blurred, the project quickly loses control of its decision making process.
PRINCE2 emphasises structure and clarity. The exam expects candidates to demonstrate that they understand these distinctions.
A Quick Practical Tip for Exam Preparation
When revising the PRINCE2 practices, try creating a small mental checklist for scenario questions.
Ask yourself:
- Is this uncertainty or reality?
- Is this a potential event or a current problem?
- Does it require risk management or issue resolution?
These questions help anchor your thinking firmly in the PRINCE2 method rather than relying on instinct.
The Way Ahead
The misuse of the Issue Register for risks is one of those deceptively simple traps that catches many Practitioner candidates.
The distinction between a risk and an issue may appear small, but in PRINCE2 it is fundamental.
A risk represents uncertainty and belongs in the Risk Register.
An issue represents a situation that has already occurred and belongs in the Issue Register.
Once you train yourself to recognise that boundary quickly, you will find many Practitioner exam questions become much easier to navigate.
And more importantly, you will be applying PRINCE2 exactly as the method intends.
