PRINCE2 7 Practitioner · Domain 3 of 4

PRINCE2 7 Practitioner Domain 3: Applying and Tailoring PRINCE2 Practices

The seven practices carry over half the marks. You apply each practice's management products, roles and techniques to the scenario, then judge whether an approach is fit for purpose and properly tailored.

Exam weight
51%
Official syllabus topics
7
Estimated questions estimate
~36
Suggested study time estimate
25–35 hrs

About 19 min read Reviewed October 2026

Overview

This domain covers the seven practices that run throughout a PRINCE2 project: business case, organization, plans, quality, risk, issues and progress. For each, criterion x.x.1 asks you to apply the practice at Bloom's level 3, using its management products, the key roles and its techniques, and criterion x.x.2 asks you to analyse at level 4 whether an approach is effective and fit for purpose, considering the principles, the practice's techniques and tailoring to the project's context.

The 7th edition reshaped this material: themes became practices, change became issues, and new PID components appeared, including the benefits, sustainability, commercial and digital and data management approaches. The practices are applied through the processes, so you will meet the same products again in the processes domain, this time asking who does what and when.

How it's tested

Expect the most questions and the widest range of formats here. Level 3 items ask you to apply a practice: choose a correct register entry, plan element or role. Level 4 items ask whether an approach is effective and fit for purpose, often in yes-or-no-with-a-reason form. Matching items commonly pair situations with issue types, risk responses, roles or report types.

  • Correct entry in a product

    An extract from a risk register, issue register, product description or plan is shown, and you judge whether an entry is correct and why.

  • Who is responsible?

    A practice activity is described, and you decide which role produces, approves, reviews or is consulted, using the practice's role table.

  • Fit-for-purpose tailoring

    A tailored practice is proposed for the scenario, and you judge whether it still meets the practice's purpose and the principles.

Reasoning it through

A risk register entry reads: 'Risk: the supplier may be late. Owner: team manager. Response: chase weekly.' Test each part. The description lacks cause, event and effect, so it is weak. The owner should be the person best placed to manage the risk, and the response must be a recognised strategy with a sensible action. The answer explaining the missing cause and effect is usually the one being tested.

Syllabus topics 7

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

3.1 Business caseJudge whether the project is and remains desirable, viable and achievable.
What it means
The business case practice establishes how the project's investment is justified and how benefits are defined, measured and realized. Its products are the business case, the benefits management approach, the sustainability management approach and the project brief.
What to understand
The project executive owns the business case and the senior user specifies benefits and is accountable for showing they are realized; the project manager prepares the business case for the executive. Outputs lead to outcomes, which lead to benefits and sometimes dis-benefits. The benefits management approach plans benefit reviews, many of which occur after closure, and the sustainability management approach sets how sustainability targets are defined and measured.
How it shows up
A question gives a business case extract or a benefits entry and asks whether it is appropriate, for example an output listed as a benefit or a benefit with no measure.
Common confusion
Candidates list outputs such as 'new website' as benefits; a benefit is a measurable improvement, such as a stated reduction in call volumes.
3.2 OrganizationSet up the structure of accountability across business, user and supplier interests.
What it means
The organization practice defines the project management team, role descriptions and the commercial management approach, so decisions are made by the right people and commercial relationships are managed.
What to understand
The project board has one project executive plus senior users and senior suppliers. Project assurance is independent of the project manager and acts for board members. The board may delegate change decisions to a change authority. Team managers and project support are optional roles the project manager can perform if tailored. The commercial management approach covers how supplier relationships are procured and managed.
How it shows up
A role assignment or team structure is described and you judge whether it is appropriate, for example the project manager also providing project assurance.
Common confusion
Candidates confuse project assurance, which serves the board inside the project, with quality assurance, which is independent of the project management team.
3.3 PlansDefine how, by whom, when and at what cost products will be delivered.
What it means
The plans practice provides project, stage, team and exception plans, plus the project product description and work package descriptions, so that delivery can be communicated and controlled.
What to understand
The project plan is approved by the board, stage plans give detail for one management stage, team plans are optional and belong to team managers, and an exception plan replaces the plan it covers. Planning is product-based: define the products, sequence them, estimate, schedule and document. The work package description is the agreement between project manager and team manager, including tolerances and reporting arrangements.
How it shows up
You judge whether a plan's level, owner, content or a work package description entry is appropriate for the scenario.
Common confusion
Candidates think an exception plan is added alongside the current plan; it replaces the plan whose tolerance is forecast to be exceeded.
3.4 QualityDefine and implement how products are verified as fit for purpose.
What it means
The quality practice covers quality planning and quality control, using product descriptions, the quality management approach, the product register and the quality register.
What to understand
Quality planning captures the customer's quality expectations and acceptance criteria in the project product description, then sets quality criteria, tolerances and methods in each product description. Quality control carries out those methods and records results in the quality register. The quality review technique uses chair, presenter, reviewer and administrator roles. Project assurance checks the project's quality approach on the board's behalf.
How it shows up
A quality register entry, product description or review arrangement is shown and you judge whether it is correct.
Common confusion
Candidates mix up acceptance criteria, which apply to the project product, with quality criteria, which apply to each individual product.
3.5 RiskIdentify, assess and control uncertainty to improve the chance of success.
What it means
The risk practice defines the risk management approach and the risk register, so threats and opportunities are managed against the project's risk appetite and tolerance.
What to understand
Risks are described by cause, event and effect, assessed for probability, impact and proximity, and given responses for threats and for opportunities. The risk owner manages a risk and the risk actionee carries out a specific response. A risk budget may fund responses to identified risks. The risk management approach records procedure, roles, scales, tolerances and reporting.
How it shows up
A risk register extract or a proposed response is shown and you decide whether it is appropriate and why.
Common confusion
Candidates write a risk as only its effect, such as 'project will be late', or name an actionee as the owner.
3.6 IssuesCapture, assess and control issues and changes to baselines.
What it means
The issues practice provides the issue management approach, issue register and issue reports, so that requests for change, off-specifications and problems or concerns are handled by the right authority.
What to understand
A request for change proposes altering a baseline; an off-specification is something that should be provided but is not, or will not be; a problem or concern is any other matter the project manager must resolve or escalate. Formal issues go in the issue register; informal ones can be handled in the daily log. The board decides on changes unless it delegates to a change authority, possibly with a change budget. Accepting an off-specification without correction is a concession.
How it shows up
An event in the scenario is described and you decide its issue type, how it should be recorded, and who should decide.
Common confusion
Candidates treat a supplier's failure to meet a criterion as a request for change; it is an off-specification.
3.7 ProgressMonitor actual against planned performance, forecast and control deviations.
What it means
The progress practice uses tolerances, logs and reports to let each level control the one below and escalate forecast breaches. Its products include the daily log, lessons log, lessons report, checkpoint, highlight, end stage, end project and exception reports, and the digital and data management approach.
What to understand
Time-driven controls, such as checkpoint and highlight reports, occur at set intervals; event-driven controls, such as exception and end stage reports, occur when something happens. Checkpoint reports go from team manager to project manager; highlight reports from project manager to board. The digital and data management approach sets how project data and digital tools are managed.
How it shows up
A reporting arrangement or tolerance handling is described and you judge whether the right report, frequency or escalation path is used.
Common confusion
Candidates send checkpoint reports to the board or use a highlight report to escalate a forecast breach, which needs an exception report.

High-yield concepts

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

  • Output, outcome, benefit, dis-benefit

    An output is a product, an outcome is the result of the change it enables, a benefit is a measurable improvement, and a dis-benefit is a measurable decline someone perceives as negative.

    Remember
    A benefit needs a measure, baseline and timing; many are measured after the project closes.
    Tested as
    Business case extracts often list an output or vague aim as a benefit.
    Trap
    Accepting 'deliver a new system' as a benefit.

  • Project executive vs. senior user on benefits

    The project executive owns the business case; the senior user specifies benefits and is accountable for demonstrating they are realized.

    Remember
    The project manager prepares the business case on the executive's behalf but does not own it.
    Tested as
    Role questions ask who is accountable for benefits or who approves the business case.
    Trap
    Assigning benefit realization to the project manager.

  • Project assurance vs. quality assurance

    Project assurance monitors the project for board members and must be independent of the project manager; quality assurance is an organizational function independent of the project management team.

    Remember
    Project assurance cannot be performed by the project manager or project support.
    Tested as
    Organization and quality questions test who can provide assurance.
    Trap
    Letting the project manager assure their own work.

  • Change authority and change budget

    The board may delegate decisions on requests for change and off-specifications to a change authority, often with a change budget.

    Remember
    Delegation is recorded in the issue management approach and must stay within agreed limits.
    Tested as
    Issue questions ask who should decide a change of a given size.
    Trap
    Assuming the project manager has authority to approve changes to baselines.

  • Three issue types

    Requests for change, off-specifications, and problems or concerns.

    Remember
    An off-specification can be resolved by correction or accepted as a concession.
    Tested as
    Matching items often ask you to classify scenario events by issue type.
    Trap
    Classifying a missing feature as a request for change.

  • Risk owner vs. risk actionee

    The risk owner is responsible for managing and monitoring a risk; the risk actionee carries out an assigned response action.

    Remember
    Owners should be the person best placed to manage the risk, often on the board or a team manager.
    Tested as
    Risk register extracts test whether owner and actionee are sensibly assigned.
    Trap
    Swapping the two roles or naming the project manager as owner of every risk.

  • Cause, event, effect

    A well-formed risk description states the cause, the uncertain event, and its effect on objectives.

    Remember
    An effect alone, such as 'the project may be late', is not a usable risk description.
    Tested as
    Level 4 questions ask whether a register entry is appropriate.
    Trap
    Treating a current problem as a risk; something that has happened is an issue.

  • Product description content

    Purpose, composition, derivation, format, quality criteria, quality tolerance, quality method, skills required and responsibilities.

    Remember
    Quality criteria must be measurable, and quality tolerance gives the acceptable range.
    Tested as
    Questions show an incomplete product description and ask what is wrong.
    Trap
    Writing quality criteria as vague aims such as 'user friendly'.

  • Quality review technique roles

    Chair, presenter, reviewer and administrator, with the chair deciding on the outcome of the review.

    Remember
    The presenter represents the producer; reviewers check against quality criteria.
    Tested as
    Matching items ask you to pair review activities with roles.
    Trap
    Letting the presenter chair a review of their own product.

  • Time-driven vs. event-driven controls

    Checkpoint and highlight reports are time-driven; end stage, exception and issue reports are event-driven.

    Remember
    The frequency of time-driven reports is set in the work package description or stage plan, not fixed by the method.
    Tested as
    Progress questions test whether the right report is used for the situation.
    Trap
    Using a highlight report to escalate a forecast tolerance breach.

  • Exception plan

    A plan that replaces the current stage or project plan when the board asks for one after an exception.

    Remember
    It covers the period from the present to the end of the plan it replaces.
    Tested as
    Plan questions ask what happens to the original plan.
    Trap
    Thinking the exception plan runs alongside the original plan.

  • 7th edition PID approaches

    The PID contains approaches for benefits, sustainability, commercial, communication, change, quality, risk, issue and digital and data management.

    Remember
    Each is created in initiating a project, owned by the relevant practice, and reviewed at stage boundaries.
    Tested as
    Questions ask which approach should hold a given rule or arrangement.
    Trap
    Placing a supplier procurement rule in the risk management approach instead of the commercial management approach.

  • Product register and quality register

    The product register tracks the status and versions of products; the quality register records planned and actual quality activities and their results.

    Remember
    Both are part of the project log in the 7th edition.
    Tested as
    Quality questions ask where a result or status should be recorded.
    Trap
    Recording a quality review outcome only in the daily log.

Side by side

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

Request for change vs. off-specification vs. problem or concern

ConceptMeaningKey differenceCommon trap
Request for change A proposal to alter a baseline, such as adding a feature The baseline is right but someone wants it changed Using it for a product that fails its agreed criteria
Off-specification Something that should be provided but is not, or is forecast not to be The product falls short of its agreed baseline Forgetting it can be accepted as a concession by the board or change authority
Problem or concern Any other issue the project manager must resolve or escalate Not a change to, or failure against, a baseline Escalating every problem rather than resolving it within tolerance

Checkpoint vs. highlight vs. exception report

ConceptMeaningKey differenceCommon trap
Checkpoint report Team manager to project manager on work package progress Time-driven, at the frequency in the work package description Sending it to the project board
Highlight report Project manager to project board on stage progress Time-driven, at the frequency the board sets Using it to request a decision on a tolerance breach
Exception report Project manager to board when stage or project tolerance is forecast to be exceeded Event-driven, triggered by a forecast breach Raising it when the variance is still within tolerance

Project assurance vs. quality assurance

ConceptMeaningKey differenceCommon trap
Project assurance Board members' assurance that the project is being run properly Within the project, independent of the project manager Letting project support perform it
Quality assurance Organizational assurance that the project's direction and management are adequate Outside and independent of the project management team Treating it as the board's own responsibility

Acceptance criteria vs. quality criteria

ConceptMeaningKey differenceCommon trap
Acceptance criteria Measurable conditions the project product must meet for the users and operators to accept it Recorded in the project product description Applying them to each individual product
Quality criteria Measurable characteristics each product must meet, with tolerances Recorded in each product description Writing them as general aims with no measure

Exam traps

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

  1. Senior user approves a concession alone

    What candidates pick
    Accept a defective product because the senior user is satisfied.
    Why it looks right
    The senior user represents users, so their satisfaction seems decisive.
    Why it's wrong
    Accepting an off-specification is a concession decided by the project board or a delegated change authority, and must be recorded in the issue register.

    Clue to watch for A product fails an agreed quality criterion and someone proposes accepting it as it is.

  2. Risk written as an effect

    What candidates pick
    Accept a risk entry 'the stage may overrun' as correctly described.
    Why it looks right
    It is clear and points at an objective that matters.
    Why it's wrong
    A useful risk states cause, event and effect, so responses can target the cause; an effect alone gives nothing to act on.

    Clue to watch for The entry describes only an impact on time, cost or quality.

  3. Project manager as assurance

    What candidates pick
    Agree the project manager can perform project assurance on a small project.
    Why it looks right
    Combining roles is valid tailoring on small projects.
    Why it's wrong
    Project assurance must be independent of the project manager; this combination removes the board's independent check.

    Clue to watch for The tailoring combines project assurance with the project manager or project support.

  4. Exception plan runs in parallel

    What candidates pick
    Keep the stage plan as the baseline and add the exception plan alongside it.
    Why it looks right
    It seems to preserve a record of the original intent.
    Why it's wrong
    An exception plan replaces the plan it covers once approved; progress is then measured against the exception plan.

    Clue to watch for The board has asked for an exception plan after a forecast breach.

  5. Benefits measured at stage end only

    What candidates pick
    Plan all benefit reviews before the project closes.
    Why it looks right
    It keeps benefit tracking inside the project's control.
    Why it's wrong
    Many benefits arise after closure, so the benefits management approach plans post-project reviews owned by the business.

    Clue to watch for The benefit depends on users working in a new way for months after handover.

  6. Approach in the wrong product

    What candidates pick
    Record supplier contract and procurement rules in the risk management approach.
    Why it looks right
    Supplier failure is a risk, so the risk approach feels relevant.
    Why it's wrong
    The 7th edition has a commercial management approach in the PID for how commercial relationships are set up and managed.

    Clue to watch for The item describes contracts, procurement or supplier relationship management.

  7. Tailoring away the issue register

    What candidates pick
    Use only the daily log for all issues on a small project.
    Why it looks right
    It reduces paperwork and the daily log can hold informal issues.
    Why it's wrong
    Informal issues may go in the daily log, but issues needing formal handling, such as requests for change, must be captured and tracked so the board can control baselines.

    Clue to watch for The issue changes a baseline or needs a board or change authority decision.

Answer framework

Use these steps for any practice question that shows an extract or proposes an approach.

  1. Name the practice and its purpose, then locate its products and role table in the official manual.
  2. Identify which product or role the question concerns, and recall what that product must contain or what that role is accountable for.
  3. Test the extract or approach against the practice's technique, such as cause, event and effect for risks or issue types for issues.
  4. Check the principles and tailoring: does the approach keep independent assurance, product focus, tolerances and a valid business case?
  5. Choose the option whose verdict and reason both match the manual's guidance for this context, rejecting reasons that are true but irrelevant.

Practice question

A team manager reports that a completed module meets all quality criteria except response time, which is 3 seconds against a criterion of 2. The senior user says the module is good enough. How should the project manager handle this under the issues practice?

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

Checklist

0 of 15

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

Study strategy

Study the practices in the order the manual presents them, but in pairs that share logic: business case with organization, plans with progress, quality with issues, then risk. For each practice, build a one-line summary in the margin of its chapter covering purpose, products and key roles, and tab the role tables the syllabus cites, because the exam is open book and those tables answer many 'who' questions.

Give the most attention to issues, risk and progress, since their products appear as extracts that you must critique, and to the 7th edition additions: the sustainability, commercial, change and digital and data management approaches. Candidates underestimate the business case distinctions between outputs and benefits, and the independence rules for project assurance.

Afterwards, practise with extracts: take a sample risk register, issue register or product description and mark each entry right or wrong with a reason. Then move to the processes domain, where the same products are created and updated by named roles at specific points in the project lifecycle.

FAQ

How much of the PRINCE2 7 Practitioner exam covers practices?

The practices learning outcome is 51% of the 70 marks, the largest share. A weight-based estimate is about 36 marks, but PeopleCert does not publish per-practice counts.

What changed from themes in the 6th edition?

Themes are now called practices, the change theme is now the issues practice, and new PID components such as the sustainability, commercial and digital and data management approaches were added.

Are all seven practices weighted equally?

The syllabus gives one weight for the whole learning outcome and does not split it by practice. Prepare all seven, since each has its own apply and analyse criteria.

What does 'effective and fit for purpose' mean in criterion 3.x.2?

You judge an approach against three things the syllabus names: the principles, the practice's effective management and techniques, and tailoring to the project's environment and context.

How do I tell an off-specification from a request for change?

Ask whether the product fails its agreed baseline or whether someone wants the baseline changed. Failure is an off-specification; a proposed change to a correct baseline is a request for change.

Can I rely on the manual during the exam?

Yes, the official manual is permitted and may contain your notes. Time is limited, so tab the role tables and product sections in advance rather than searching from scratch.

How do practices relate to processes?

Practices are applied throughout the project through the processes. The processes domain tests which activity, role and timing apply each practice's products.

Other Project Management certifications

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

Test your Domain 3 knowledge

You have worked through applying and judging all seven practices, from benefits to issue types and reports. Test whether you can critique register extracts and role choices against the clock.

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

Keep going