PRINCE2 7 Practitioner common mistakes
PRINCE2 7 Practitioner · Understand the traps and how to avoid them.
When a question asks who should approve a stage plan or authorise work, the candidate picks 'the Project Manager' because the Project Manager built the plan, instead of the Project Board (or the delegated authority defined in the project's organization structure).
Everyday PM habits treat the person who produces a document as the person who signs it off, and the PRINCE2 accountability split between 'responsible for' and 'accountable for' is easy to blur under time pressure.
What to do instead
Before answering any role question, write the four-level hierarchy (corporate/programme, Project Board, Project Manager, Team Manager) and place the product against it. Learn the pattern that the Project Board authorises stage plans and work packages above tolerance, while the Project Manager authorises work packages within stage tolerance.
The candidate selects an option that says a principle may be dropped or scaled back for a small or agile project, e.g. 'the project can be run without defined roles because the team is only three people'.
Tailoring is taught as adapting PRINCE2 to the project, and candidates over-extend that idea from practices and processes into the principles themselves.
What to do instead
Anchor the rule: all seven principles must always be applied; tailoring changes how they are applied, never whether. Reject any option in which a principle is absent, and prefer options that show the principle applied in a lighter-weight way.
The candidate mixes up Project Assurance, Project Support and Change Authority, for example by saying Project Support independently monitors the project's performance, or that Project Assurance administers the change control log.
All three are optional, board-adjacent roles with short definitions, and their one-line descriptions overlap in wording about 'monitoring' and 'supporting the board'.
What to do instead
Memorise each role by its single defining purpose: Project Assurance gives the board an independent view on whether the project is on track against its interests; Project Support provides administrative and tooling services to the Project Manager; Change Authority is a delegated decision-maker for changes. Match the verb in the question ('independently monitor', 'administer', 'decide') to the role.
The candidate confuses similar-sounding progress products, e.g. choosing the End Stage Report when the question is about closing the project, or choosing a Highlight Report where a Checkpoint Report is required, or treating the Benefits Management Approach as the Business Case.
The products share audiences and content, and the question often describes the content rather than naming the product.
What to do instead
Build a one-page matrix of each progress-related product with four columns: producer, audience, timing (regular or event-driven), and trigger. Specifically separate Checkpoint Report (Team Manager to Project Manager, per work package), Highlight Report (Project Manager to Project Board, per reporting period), End Stage Report (stage boundary), End Project Report (project closure).
The candidate places an activity in the wrong process, for example saying the Project Board is appointed during Initiating a Project, or that the Business Case is first drafted during Initiating a Project, or that benefits are reviewed in Controlling a Stage.
The seven processes share similar activity names and many activities recur across processes at different levels of detail, so candidates recognise the phrase without checking which process owns it.
What to do instead
Learn each process by its trigger and its end product rather than by its activity list. Key anchors: appointing the board and drafting the outline Business Case happen in Starting up a Project; developing the detailed Business Case and stage plans happen in Initiating a Project; authorising a stage happens in Managing a Stage Boundary and Directing a Project.
On a tolerance question, the candidate answers that the Project Manager should 'resolve the issue and report it later', even though the scenario describes a forecast breach of stage-level tolerance that must be escalated to the Project Board as an exception.
Candidates learn that the Project Manager 'manages by exception within tolerance' and then over-apply it, treating escalation as a failure of management rather than a defined control.
What to do instead
Work through the escalation chain explicitly: Team Manager to Project Manager on work-package tolerance, Project Manager to Project Board on stage tolerance, Project Board to corporate or programme on project tolerance. When a question says a tolerance is forecast to be exceeded, the answer must involve an Exception Report and escalation to the next level up.
The candidate answers a scenario question with the full textbook configuration of a practice (all roles, all documents, all reports) even where the scenario describes a small, low-risk project embedded in a supportive programme.
Definitions are memorised in their untailored form, and candidates treat an option containing the most PRINCE2 artefacts as the most correct.
What to do instead
Before evaluating options, extract the tailoring clues from the scenario - scale, risk level, complexity, commercial arrangements, governance already provided by the host organization - and reject any option that duplicates something the scenario says already exists or that imposes overhead the scenario cannot sustain.
The candidate treats People-domain questions as communications-planning mechanics, answering questions about team leadership, conflict, or stakeholder engagement with references to reporting lines, RACI-style accountability, or the Communications Management Approach.
The People content is qualitative and less rule-like than the practices, so candidates default to the tangible artefacts they have memorised.
What to do instead
Study the People content as a distinct topic: leading a team, collaborating across organizational boundaries, and engaging stakeholders, each with its own behaviours and success factors. When the stem mentions motivation, resistance, dispersed teams, or behaviour, evaluate options on the human behaviour described, not on documentation.
The candidate chooses an option that is true in PRINCE2 but does not answer the question asked, having skipped the command word and any qualifier such as FIRST, BEST, MOST likely, NEXT, or a timing phrase such as 'at the end of the stage'.
Under exam time pressure, candidates match keywords in the stem to keywords in the options and stop reading once a familiar phrase appears.
What to do instead
Adopt a fixed routine for every question: underline the command word, the role named, and the timing, then read all four options before choosing. Where two options are both correct PRINCE2 statements, the command word decides which one is the answer.
The candidate says the Project Manager owns and maintains the Business Case and is accountable for realising the benefits, rather than the Senior User being accountable for benefits realisation and the Project Board owning the Business Case as a decision tool.
The Project Manager is visibly the person who writes and updates most documents, so authorship is mistaken for accountability, and 'benefits' is assumed to sit with the person running delivery.
What to do instead
Learn the Business Case by its accountabilities rather than its author: the Executive is accountable for the Business Case, the Senior User is accountable for benefits realisation and for specifying and monitoring the benefits, and the Project Manager prepares and maintains the document and the Benefits Management Approach on their behalf. Reinforce with the rule that benefits are typically realised after the project has closed.