PRINCE2 7 Practitioner · Domain 1 of 4

PRINCE2 7 Practitioner Domain 1: PRINCE2 Principles in Context

The seven principles are what make a project a PRINCE2 project. At Practitioner level you judge whether a scenario's actions genuinely apply each principle, which is the reasoning every other domain relies on.

Exam weight
10%
Official syllabus topics
7
Estimated questions estimate
~7
Suggested study time estimate
5–7 hrs

About 18 min read Reviewed October 2026

Overview

This domain tests one assessment criterion, analysing the application of the seven PRINCE2 principles in context: ensure continued business justification, learn from experience, define roles, responsibilities and relationships, manage by stages, manage by exception, focus on products, and tailor to suit the project. Foundation asked you to recognise them; Practitioner asks whether a specific action in the exam scenario applies a principle well, poorly, or not at all.

The principles are universal and non-negotiable: a project that drops any one is not being run as PRINCE2, while the practices and processes may be tailored. Every judgement you make in the practices and processes domains comes back to them, because the syllabus asks you to weigh those approaches against the principles. Expect the scenario's people, plans and reports to be the evidence you test each principle against.

How it's tested

Principle questions are scenario-based analysis at Bloom's level 4. You are given an action taken on the scenario project and asked whether it applies a named principle, or which principle it best demonstrates, and why. Matching items may ask you to pair three actions with the principles they apply. The reason matters as much as the verdict.

  • Does this action apply the principle?

    An action from the scenario is paired with a principle, and you decide whether it applies it and pick the correct justification.

  • Which principle is demonstrated?

    A practical decision, such as setting work package tolerances, is described and you identify the principle it most directly supports.

  • Tailoring that breaks a principle

    A simplification is proposed and you judge whether it is legitimate tailoring or removes something a principle requires.

Reasoning it through

The scenario says the project board will approve the whole project at initiation and then meet only if the project manager calls them. Ask what each principle needs. Manage by stages needs the board to authorize each stage at a boundary, so a single up-front approval undermines it, even though infrequent meetings on their own are consistent with manage by exception. Separate the two ideas before choosing the option and its reason.

Syllabus topics 7

Official syllabus topics from the PeopleCert outline, in outline order.

1.1a Ensure continued business justificationA valid, documented reason to start the project that is re-checked throughout.
What it means
The project must have a justifiable reason to start, that reason must stay valid for the whole project, and it must be recorded and approved in the business case. If the justification disappears, the project should be changed or stopped.
What to understand
Justification is tested at every key decision: in starting up (outline business case), at initiation (full business case), at each stage boundary and whenever an exception is raised. Mandatory or compliance projects still need a business case to justify the option chosen, even if 'do nothing' is not allowed.
How it shows up
A scenario introduces a cost rise, a competitor launch or a reduced benefit, and asks whether continuing, or reviewing the business case, applies the principle.
Common confusion
Candidates think justification is checked only at the start; the principle is about it staying valid, so a business case that is never updated after initiation does not apply it.
1.1b Learn from experienceSeek, record and act on lessons at the start, during and after the project.
What it means
Project teams seek lessons from previous projects before starting, keep capturing lessons during the project, and pass lessons on at closure, so mistakes are not repeated and good practice spreads.
What to understand
Lessons are sought actively, not waited for: previous lessons are captured when starting up, the lessons log is used throughout, and lessons reports can be produced at stage ends as well as at closure. Learning only counts if it changes how the project or organization works.
How it shows up
An option shows lessons being recorded but never used, or a lessons report issued mid-project; you judge whether the principle is applied.
Common confusion
Recording lessons in a log is not the same as learning from them; and a lessons report is not restricted to the end of the project.
1.1c Define roles, responsibilities, and relationshipsClear accountability across business, user and supplier interests, plus working relationships.
What it means
A PRINCE2 project has an agreed structure in which the business, user and supplier interests are represented in decision-making, everyone knows what is expected of them, and relationships with stakeholders are deliberately built.
What to understand
The 7th edition stresses relationships as well as structure: people who hold roles must be able to work together and with stakeholders outside the project. A role can be shared or combined if tailored sensibly, but the three interests must still be represented and accountability must stay clear, with one project executive.
How it shows up
A scenario combines roles, such as the senior user also acting as project manager, and asks whether the principle is still applied.
Common confusion
Candidates assume the principle forbids combining roles; it forbids losing an interest or blurring accountability, and some combinations (such as executive and senior user) can be appropriate on a small project.
1.1d Manage by stagesPlan, monitor and control the project one management stage at a time.
What it means
The project is split into management stages separated by decision points at which the project board reviews progress and justification and authorizes the next stage only.
What to understand
Stages give the board control points and match planning detail to the planning horizon: a high-level project plan plus a detailed plan for the current stage. There are at least two management stages, initiation and at least one more. Stage length depends on risk and complexity, not on a calendar.
How it shows up
A scenario has one detailed plan for the whole project, or a board that authorizes all stages at once, and asks whether manage by stages is applied.
Common confusion
Management stages are often confused with delivery steps or technical phases; a management stage is defined by a board decision point, and technical work can overlap a boundary.
1.1e Manage by exceptionDelegate authority with tolerances so each level escalates only forecast breaches.
What it means
Each management level sets tolerances for the level below on performance targets and lets it get on with the work, needing to be involved only when a tolerance is forecast to be exceeded.
What to understand
The 7th edition performance targets are time, cost, scope, quality, benefits, risk and sustainability. The business layer sets project tolerances, the project board sets stage tolerances, and the project manager sets work package tolerances. The trigger for escalation is a forecast breach, not an actual one.
How it shows up
A scenario describes a project manager seeking board approval for a small variance well within tolerance, or a team manager absorbing a forecast overrun; you judge the application.
Common confusion
Candidates think manage by exception means the board does nothing between boundaries; the board still receives regular highlight reports and gives direction, it just does not micromanage.
1.1f Focus on productsDefine and agree products and their quality criteria before doing the work.
What it means
The project concentrates on the definition and delivery of products, especially their quality requirements, so that scope is clear and the people doing the work know what acceptable looks like.
What to understand
Products are described before work starts using product descriptions with quality criteria, and the project product description captures the customer's quality expectations and acceptance criteria. Product focus drives planning, work package authorization, quality control and acceptance.
How it shows up
A scenario shows work starting from an activity list with no agreed product descriptions, and you judge whether the principle is applied or what to do first.
Common confusion
Candidates equate products with physical deliverables only; management products such as plans and reports are also products, and a focus on activities instead of outputs is the failure the principle prevents.
1.1g Tailor to suit the projectAdapt the method to the project's environment, scale, complexity, capability and risk.
What it means
PRINCE2 is adapted to fit the project's context, so that the level of control and formality matches what the project actually needs, while the principles remain intact.
What to understand
Tailoring changes how the practices and processes are applied: reports may be verbal, roles combined, management products merged. It does not remove a principle. Tailoring decisions are agreed and recorded, typically in the project initiation documentation (PID), so everyone knows how the method is being applied.
How it shows up
A scenario simplifies something, such as dropping highlight reports or merging documents, and asks whether that is appropriate tailoring.
Common confusion
Tailoring is not omitting controls because they are inconvenient; if the change removes the board's ability to manage by exception or by stages, it breaks a principle rather than tailoring the method.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Seven principles as a set

    The seven principles are universal, self-validating and empowering, and all seven must be applied for a project to count as a PRINCE2 project.

    Remember
    Principles cannot be tailored away; only the way practices and processes apply them can be adapted.
    Tested as
    Options that remove a principle to simplify a small project are wrong even when the simplification sounds efficient.
    Trap
    Treating one principle as optional on a small or low-risk project.

  • Business case validity test

    A project is justified when its expected benefits outweigh its costs and risks in a way the business finds worthwhile and achievable.

    Remember
    The test is reapplied at each stage boundary and exception, using the current forecast rather than the original estimate.
    Tested as
    Scenarios change a cost, benefit or risk, and the right answer usually involves reassessing viability with the project executive.
    Trap
    Assuming a stage within its cost tolerance means the project is still justified overall.

  • Lessons at three points

    Lessons are sought when starting up, captured during the project in the lessons log, and handed on in lessons reports.

    Remember
    A lessons report can be issued at a stage end or when a significant lesson emerges, not only at closure.
    Tested as
    Questions test whether an action at a particular moment counts as learning from experience.
    Trap
    Thinking the principle is satisfied simply because a lessons log exists.

  • Three project interests

    Business, user and supplier interests are represented on the project board through the project executive, senior user and senior supplier.

    Remember
    Any combination of roles must still give each interest a voice, and there is only one project executive, who is ultimately accountable.
    Tested as
    Scenarios combine or omit roles and ask whether roles and responsibilities are properly defined.
    Trap
    Believing roles can never be combined, or that the senior user can also hold supplier accountability without conflict.

  • Management stage vs. delivery step

    A management stage ends with a board decision point; delivery steps or technical phases describe how specialist work is done.

    Remember
    Stage boundaries are placed at decision points, considering risk and planning horizon, and specialist work may cross them.
    Tested as
    Questions ask whether a proposed stage structure gives the board adequate control.
    Trap
    Placing boundaries purely to match technical phases or calendar months.

  • Minimum of two management stages

    Every PRINCE2 project has an initiation stage plus at least one further management stage.

    Remember
    Even a short project needs initiation as a separate control point before delivery work is authorized.
    Tested as
    A scenario proposes starting delivery immediately without initiation; this fails manage by stages.
    Trap
    Assuming a small project can be a single stage.

  • Seven performance targets

    PRINCE2 7 sets tolerances against time, cost, scope, quality, benefits, risk and sustainability.

    Remember
    Sustainability is a performance target in the 7th edition, so a forecast breach of a sustainability target is an exception too.
    Tested as
    Scenarios include an environmental or social target and test whether a forecast breach is escalated.
    Trap
    Escalating only time and cost breaches and ignoring the other targets.

  • Three levels of tolerance

    Project tolerances come from the business layer, stage tolerances from the project board, and work package tolerances from the project manager.

    Remember
    Each level escalates to the level that set its tolerance, and only when a breach is forecast.
    Tested as
    Questions ask who should be informed of a forecast breach at a given level.
    Trap
    A project manager reporting a work package breach straight to the business layer, bypassing the board.

  • Product description and quality criteria

    A product description defines a product's purpose, composition, quality criteria and tolerances, and how it will be checked.

    Remember
    Product descriptions are written before the work that creates the product is authorized.
    Tested as
    Focus on products answers usually involve defining or agreeing a product description first.
    Trap
    Starting work from a task list and writing the description after the product is built.

  • Tailoring vs. omission

    Tailoring adapts the method's formality and format; omission removes a control that a principle depends on.

    Remember
    Every tailoring choice should still let the board direct by stages and exceptions with a valid business case.
    Tested as
    Practitioner options often pair a sensible simplification with a reason that reveals whether a principle survives.
    Trap
    Accepting any change described as 'tailoring' without checking which principle it touches.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Manage by stages vs. manage by exception

ConceptMeaningKey differenceCommon trap
Manage by stages The board authorizes one management stage at a time at planned decision points Control comes from scheduled boundaries where viability and the next stage plan are reviewed Thinking frequent board meetings are what this principle requires
Manage by exception Each level works within tolerances and escalates only forecast breaches Control comes from delegated limits, between boundaries, triggered by events Treating any variance as an exception even when it is inside tolerance

Legitimate tailoring vs. removing a principle

ConceptMeaningKey differenceCommon trap
Legitimate tailoring Combining roles, giving verbal highlight reports, merging approaches into the PID The control still exists in a lighter form, and the decision is recorded Assuming tailoring must be formally documented as a separate product to count
Removing a principle Authorizing all stages at once, no business case for a mandatory project, no product descriptions A capability the principle needs is gone, not just simplified Accepting it because the scenario calls it tailoring

Business, user and supplier interests

ConceptMeaningKey differenceCommon trap
Business (project executive) Represents the investment and owns the business case Ultimately accountable for the project and its value for money Letting the senior user own the business case
User (senior user) Represents those who will use the products and realize benefits Specifies requirements and is accountable for demonstrating benefits Treating the senior user as responsible for building the products
Supplier (senior supplier) Represents those who design, develop and deliver the products Accountable for the quality of products and the supplier resources Assuming the supplier is always an external company; it can be an internal team

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Whole-project approval at initiation

    What candidates pick
    Agree that authorizing all stages at once applies the principles because it saves board time.
    Why it looks right
    It looks like empowering the project manager and reducing overhead, which sounds like manage by exception.
    Why it's wrong
    Manage by stages requires the board to decide at each boundary whether to continue; one up-front approval removes that control.

    Clue to watch for The board 'will not need to meet again unless there is a problem' and has approved every stage.

  2. Within stage tolerance, so justified

    What candidates pick
    Continue because the current stage is inside its cost tolerance.
    Why it looks right
    Stage tolerance is the project manager's authority, so it seems no one needs to be told.
    Why it's wrong
    Continued business justification looks at the whole project; a forecast that benefits no longer outweigh costs must reach the board regardless of stage tolerance.

    Clue to watch for The change affects total project cost, benefits or viability rather than just the stage.

  3. Lessons log equals learning

    What candidates pick
    Say learn from experience is applied because the team records lessons.
    Why it looks right
    A lessons log is a visible PRINCE2 product, so its existence feels like compliance.
    Why it's wrong
    The principle requires lessons to be sought and acted on; a log that never changes behaviour does not apply it.

    Clue to watch for The scenario mentions a repeated problem that an earlier lesson already identified.

  4. Combining roles breaks the principle

    What candidates pick
    Reject any arrangement where one person holds two roles.
    Why it looks right
    Foundation material stresses clear separation of roles.
    Why it's wrong
    Roles can be combined when tailoring, as long as all three interests are represented and the combination does not create a conflict, such as the project manager also providing project assurance.

    Clue to watch for Check which two roles are combined and whether one would review the other's work.

  5. Tailoring by deletion

    What candidates pick
    Accept dropping product descriptions on a small project as appropriate tailoring.
    Why it looks right
    It reduces documentation and the scenario labels it tailoring.
    Why it's wrong
    Without agreed quality criteria the project cannot focus on products or accept them objectively; tailoring could make descriptions brief, not absent.

    Clue to watch for The simplification removes a definition of what will be delivered or how it will be judged.

  6. Escalating within tolerance

    What candidates pick
    Have the project manager ask the board to approve a small slippage.
    Why it looks right
    It looks transparent and cautious.
    Why it's wrong
    If the forecast stays within stage tolerance the project manager should handle it and report it in the next highlight report; escalating wastes the board's time and undermines manage by exception.

    Clue to watch for The variance is described as within the tolerance the board set.

Answer framework

Use these steps whenever a principle question asks whether an action is appropriate.

  1. Name the principle the question asks about, and recall the specific capability it requires rather than its title alone.
  2. Find the evidence in the scenario or additional information: who acted, at what point, with which product or tolerance.
  3. Test whether that capability still exists after the action; a lighter or verbal version still counts, a removed one does not.
  4. Check the stated reason in each option, because a correct verdict paired with a wrong justification is a wrong answer.
  5. Prefer the option that keeps the board directing by stages and exceptions, with a valid business case and agreed products, at the least overhead the context allows.

Practice question

In stage 3 of a warehouse automation project, the supplier announces a price rise. The stage remains within its cost tolerance, but the revised forecast shows total project costs will now exceed the expected benefits. What should the project manager do?

Want more like this? The PRINCE2 7 Practitioner practice test has questions for every domain.

Checklist

0 of 12

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Start by rewriting each principle as a test you can apply to an action: what must still be true after the action for the principle to hold? For manage by stages it is a board decision at each boundary; for manage by exception it is tolerances on all seven performance targets with escalation of forecast breaches. Write these tests as margin notes beside chapter 2 of your official manual, since the exam is open book and the notes are allowed.

Give the most time to manage by exception, continued business justification and tailoring, because they appear inside practice and process scenarios as well as on their own. Candidates underestimate the relationships part of the third principle and the difference between tailoring and omission; both produce plausible wrong options.

Then practise with full scenarios rather than isolated statements. For each action in the scenario, name the principle it touches and say whether it is applied, and why, in one sentence. After that, move to the practices domain, where criterion 3.x.2 asks you to weigh every practice against these same principles.

FAQ

How much of the PRINCE2 7 Practitioner exam is about principles?

The principles learning outcome is weighted at 10% of the 70 marks. Their real reach is wider, because the practices and processes criteria ask you to analyse approaches taking the principles into consideration.

What kind of principle questions should I expect?

Scenario-based analysis questions at Bloom's level 4, asking whether an action applies a principle and why, plus matching items that pair actions with principles. The justification in each option is part of what is being tested.

Can a principle be tailored out on a small project?

No. All seven principles must be applied for a project to be a PRINCE2 project. Tailoring changes how the practices and processes apply them, for example combining roles or using verbal reports.

Is a stage the same as a phase of the technical work?

No. A management stage is defined by a board decision point at its end. Technical or delivery work can be organized differently and may overlap a stage boundary.

What changed in the principles for the 7th edition?

The seven principles remain, with 'define roles, responsibilities and relationships' emphasising relationships, and sustainability added as a performance target that manage by exception sets tolerances for.

How do I use the manual for principle questions in an open-book exam?

Chapter 2 sets out each principle. Mark the key capability for each, so you can check an option against it quickly, but expect the answer to come from applying the principle to the scenario, not from finding a matching sentence.

How should I split study time for this domain?

Plan roughly 5 to 7 hours as an editorial estimate, most of it on scenario practice. The same principle reasoning is reused in the practices and processes domains, so time here pays back across the exam.

Other Project Management certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 1 knowledge

You have worked through testing each of the seven principles against scenario actions. See whether you can pick both the right verdict and the right reason under timed conditions.

Take the PRINCE2 7 Practitioner practice test Check your PRINCE2 7 Practitioner readiness

Keep going