If you are preparing for the PRINCE2 7th Edition Practitioner exam, there is one area that quietly causes a surprising number of candidates to lose marks. It is not usually because they lack knowledge. It is because they confuse roles and responsibilities under exam pressure.
This is particularly frustrating because many candidates actually understand the scenario perfectly. They know what needs to happen. They recognise the problem. They understand the PRINCE2 method.
But then they assign the decision to the wrong role. And that is enough to lose the mark.
The PRINCE2 Practitioner exam frequently tests your understanding of who should do what, not just what should be done. This subtle distinction is one of the biggest differences between Foundation level learning and Practitioner level application.
Once you understand how PRINCE2 separates authority and responsibility, these questions become much easier to answer.
Why Role Confusion Happens in the PRINCE2 7 Practitioner Exam
In the real world, project governance is often blurred. Many organisations do not strictly follow PRINCE2 role definitions. Project Managers often make decisions that technically belong to senior stakeholders. Project Boards sometimes get involved in operational detail. Assurance roles are sometimes informal or even missing entirely.
Because of this, candidates bring their real-world experience into the exam, which is where the trouble starts.
The Practitioner exam is not testing how your organisation runs projects. It is testing how PRINCE2 expects projects to be governed. This means you must temporarily set aside your real-world habits and think purely in PRINCE2 terms.
When candidates fail to do this, they often:
- Assign governance decisions to the Project Manager
- Give operational tasks to the Project Board
- Confuse Project Assurance with project management
- Misunderstand the role of the Team Manager
These mistakes are extremely common, and the exam deliberately tests them.
The PRINCE2 7 Authority Structure Explained
The easiest way to avoid confusion is to think of PRINCE2 roles in terms of authority levels.
PRINCE2 is designed around clear decision boundaries. Each role has a defined level of authority, and this is what you should focus on when answering exam questions.
Let’s walk through the core roles.
The Project Board: Direction and Governance
The Project Board sits at the top of the project governance structure. Their role is to provide direction and ensure that the project remains viable, desirable, and achievable.
The Project Board is responsible for:
- Approving the Business Case
- Authorising project stages
- Making major decisions
- Providing overall direction
- Ensuring continued business justification
- Approving exceptions
Notice something important here. The Project Board is not managing the project day to day. They are governing it, and this distinction is critical.
If you see a scenario involving strategic direction, funding decisions, or stage approvals, you are almost certainly dealing with the Project Board.
A common exam trap is when candidates assign these responsibilities to the Project Manager. This is incorrect in PRINCE2.
The Project Manager: Day to Day Delivery
The Project Manager is responsible for managing the project within the tolerances set by the Project Board.
This includes:
- Planning stages
- Managing risks and issues
- Monitoring progress
- Managing the team
- Reporting to the Project Board
- Controlling stage delivery
The Project Manager has authority to manage the project within agreed tolerances. If those tolerances are forecast to be exceeded, the Project Manager must escalate to the Project Board.
This is the principle of management by exception in action.
The Practitioner exam often tests this boundary.
For example, you might see a scenario where costs are forecast to exceed tolerance. Many candidates choose an answer where the Project Manager resolves the issue alone.
But PRINCE2 says the Project Manager must escalate to the Project Board.
That is the difference between governance and management.
The Team Manager: Delivering Work Packages
The Team Manager is responsible for delivering the work assigned by the Project Manager.
Their responsibilities include:
- Accepting work packages
- Producing deliverables
- Reporting progress
- Managing team members
- Escalating issues to the Project Manager
The Team Manager does not report directly to the Project Board. They report to the Project Manager.
This reporting structure is another area where candidates sometimes get confused, as if you see operational delivery activity, the Team Manager is likely to be involved.
But if you see governance decisions, you are moving up into Project Manager or Project Board territory.
Project Assurance: Checking, Not Managing
Project Assurance is another role that often causes confusion.
Project Assurance does not manage the project. They provide independent oversight to ensure the project is being managed correctly.
Their responsibilities include:
- Monitoring compliance
- Checking progress
- Ensuring standards are followed
- Reviewing management products
- Providing independent assurance
Project Assurance supports the Project Board by providing confidence that the project is under control.
The key point is that Project Assurance does not make decisions or manage delivery.
If a scenario describes reviewing, checking, or monitoring, Project Assurance is likely involved.
If it describes planning, controlling, or delivering, you are dealing with management roles instead.
A Classic Practitioner Exam Scenario
Let’s look at a typical scenario.
The Project Manager identifies that a key supplier may cause a delay which could exceed stage tolerance.
The question asks what should happen next.
A Common incorrect answer:
The Project Manager revises the stage plan and proceeds.
Correct PRINCE2 thinking:
The Project Manager forecasts an exception and escalates to the Project Board.
The key here is recognising the authority boundary.
The Project Manager manages within tolerances. The Project Board decides when tolerances are exceeded.
The One Question That Solves Most Role Confusion
When you encounter a role-based question in the Practitioner exam, ask yourself one simple question:
Who owns this level of decision making?
- If the decision is strategic, it belongs to the Project Board.
- If the decision is operational within tolerance, it belongs to the Project Manager.
- If the decision is about delivery, it belongs to the Team Manager.
- If the activity is checking and monitoring, it belongs to Project Assurance.
This simple mental model works remarkably well in the exam.
Why the Practitioner Exam Focuses on Roles
PRINCE2 is built around controlled delegation and governance. Clear roles prevent confusion and ensure accountability.
If responsibilities are blurred:
- Decisions get delayed
- Accountability becomes unclear
- Governance weakens
- Projects drift off track
The Practitioner exam tests your ability to apply PRINCE2 governance in realistic scenarios. That is why roles and responsibilities appear frequently in exam questions.
How to Practise This for the Exam
A simple technique is to take any scenario question and identify:
- Who notices the problem
- Who manages the response
- Who makes the decision
This forces you to think in PRINCE2 governance terms, so with practice, this becomes second nature.
