PRINCE2 7 Foundation · Domain 4 of 5

PRINCE2 7 Foundation Domain 4: PRINCE2 Practices

The seven practices carry 60% of the Foundation exam. You need to know each practice's purpose, its management products, who is responsible for what, and the key concepts the manual defines.

Exam weight
60%
Official syllabus topics
7
Estimated questions estimate
~36
Suggested study time estimate
15–20 hrs

About 18 min read Reviewed October 2026

Overview

This domain covers the seven PRINCE2 practices: business case, organization, plans, quality, risk, issues and progress. Each practice is an aspect of project management that must be addressed continually throughout the project, and each has its own purpose, management products, role responsibilities and techniques. In the 7th edition the practices replace the 6th-edition themes, the old change theme becomes issues, and new management approaches cover areas such as sustainability, commercial management and digital and data.

At Foundation level you are expected to recall and explain, not tailor: what the practice is for, which products it uses, and who owns them. The practices are where the principles are made concrete, so each one maps to at least one principle, and the processes in domain 5 describe when each practice's products are created and updated.

How it's tested

Practice questions are mostly single-answer recall and comprehension. Stems name a product, role or concept and ask for its purpose, owner or content, or describe a short event and ask how PRINCE2 classifies it. Negative wording, such as which is NOT a purpose, and statement-selection questions are common enough to read every stem carefully.

  • Product purpose or owner

    A management product is named and you choose its purpose, its content or the role responsible for it, such as who owns the business case.

  • Classify the event

    A short event is described and you classify it, for example as a risk or an issue, or as a request for change, off-specification or problem or concern.

  • Who does what

    A responsibility, such as setting stage tolerances or specifying benefits, is described and you identify the role or management level that holds it.

Reasoning it through

A stem says a delivered report omits a section that its product description requires, and asks how PRINCE2 classifies this. Reason from definitions: something that should be provided but is not, or is forecast not to be, is an off-specification. A request for change is the tempting distractor, but that proposes changing an agreed baseline, whereas here the baseline is clear and the product falls short of it.

Syllabus topics 7

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

4.1 Business caseEstablishing and maintaining justification, and planning how benefits are measured and realized.
What it means
The business case practice provides mechanisms to judge whether the project is and remains desirable, viable and achievable. Its products include the business case, the benefits management approach, the sustainability management approach and the project brief.
What to understand
An outline business case is prepared in starting up a project, developed into a detailed business case in initiation, updated at stage boundaries and used to confirm benefits after closure. The project executive owns the business case; senior users specify benefits and are accountable for their realization. Outputs lead to outcomes and then benefits, and some outcomes create dis-benefits.
How it shows up
Expect questions on who is accountable for the business case, when it is first created, or what the benefits management approach is for.
Common confusion
Thinking the project manager owns the business case because they prepare much of it; the project executive owns it.
4.2 OrganizationThe project management team structure, roles, and commercial relationships.
What it means
The organization practice defines the project's structure of accountability and responsibilities. Its products include the PID sections for the project management team structure, role descriptions and the commercial management approach.
What to understand
There are four levels: the business layer, directing (project board), managing (project manager) and delivering (team managers). The board has one project executive plus senior users and senior suppliers. Project assurance is independent of the project manager, a change authority may be delegated change decisions, and project support and team manager roles can be combined with the project manager role when tailored.
How it shows up
A stem describes a responsibility and asks which role holds it, or asks which roles can be combined.
Common confusion
Treating project assurance as quality assurance, or assuming the project manager can perform project assurance; assurance must be independent of the project manager.
4.3 PlansProject, stage, team and exception plans built from products.
What it means
The plans practice provides a framework to design, develop and maintain plans so that everyone knows what is required, how, by whom, when and at what cost. Products include the project plan, stage plans, team plans, exception plans, the project product description and work package descriptions.
What to understand
The project plan is high level for the whole project, 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 when tolerance is forecast to be exceeded. Planning is product-based: identify and describe the products, sequence them, then estimate and schedule the work.
How it shows up
Expect questions on which plan is optional, what an exception plan replaces, or the first step of product-based planning.
Common confusion
Starting planning with activities; PRINCE2 starts with the products and derives activities from them.
4.4 QualityQuality planning and quality control so products meet expectations and are accepted.
What it means
The quality practice defines how the project creates and verifies products that are fit for purpose. Products include product descriptions, the project product description, 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 and sets quality criteria and methods in each product description. Quality control carries out the methods, records results in the quality register and obtains approval and acceptance. Quality assurance is independent of the project, while project assurance acts for the board.
How it shows up
Expect questions distinguishing acceptance criteria from quality criteria, or asking what the quality register records.
Common confusion
Using quality assurance and project assurance as synonyms; quality assurance sits outside the project management team.
4.5 RiskIdentifying, assessing and controlling uncertainty, both threats and opportunities.
What it means
The risk practice identifies, assesses and controls uncertain events that would affect objectives, both threats and opportunities. Products include the risk management approach and the risk register.
What to understand
A risk is described by its cause, event and effect, and assessed for probability, impact and proximity. The risk management procedure covers identifying, assessing, planning and implementing responses, with communication throughout. The risk owner manages a risk, a risk actionee carries out a specific response, and risk appetite and tolerance set how much risk is acceptable.
How it shows up
Expect a question on the difference between risk owner and actionee, or on which part of a risk description is the event.
Common confusion
Treating risks as only negative; PRINCE2 risks include opportunities.
4.6 IssuesHandling requests for change, off-specifications and problems or concerns.
What it means
The issues practice identifies, assesses and controls events that have happened and need management action, including proposed changes to baselines. Products include the issue management approach, the issue register and issue reports.
What to understand
The three issue types are a request for change, an off-specification and a problem or concern. Issues are captured, assessed, a response recommended, decided by the appropriate authority and implemented. The board decides on requests for change unless it delegates to a change authority, possibly with a change budget; informal issues can be handled in the daily log.
How it shows up
A short event is described and you classify the issue type, or identify who may approve a request for change.
Common confusion
Confusing a risk, which is uncertain, with an issue, which has happened; and confusing an off-specification with a request for change.
4.7 ProgressMonitoring and controlling progress against plans and escalating forecast tolerance breaches.
What it means
The progress practice compares actual achievement with plans, provides a forecast, and controls deviations through tolerances and escalation. 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
The business layer sets project tolerances, the board sets stage tolerances and the project manager sets work package tolerances. Time-driven controls, such as checkpoint and highlight reports, occur at set intervals; event-driven controls, such as end stage and exception reports, are triggered by events. A forecast breach of stage tolerance is escalated to the board with an exception report.
How it shows up
Expect questions on who sets which tolerance, which report goes to whom, and whether a control is time-driven or event-driven.
Common confusion
Mixing checkpoint and highlight reports; checkpoint reports go from team manager to project manager, highlight reports from project manager to project board.

High-yield concepts

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

  • Outline business case vs. detailed business case

    The outline business case is created by the project executive in starting up a project; it is developed into the detailed business case during initiation.

    Remember
    The business case is then updated at each stage boundary and reviewed at closure.
    Tested as
    Questions ask when the business case is first prepared or when it is refined.
    Trap
    Thinking the full business case is required before initiation is authorized.

  • Benefits management approach

    Defines how and when benefits will be measured and reviewed, including reviews after the project closes.

    Remember
    It is created in initiation and covers post-project benefit reviews.
    Tested as
    A stem asks which product plans the measurement of benefits.
    Trap
    Assuming all benefits are measured before closure.

  • Project board composition

    One project executive, one or more senior users and one or more senior suppliers.

    Remember
    There is only ever one project executive, who is ultimately accountable for the project.
    Tested as
    Frequently tested as a single fact or through a role-matching question.
    Trap
    Assuming the board can have two executives or that the project manager sits on the board.

  • Project assurance

    Monitoring of the project's performance on behalf of board members, independent of the project manager.

    Remember
    Board members can delegate assurance, but never to the project manager.
    Tested as
    Questions test independence and the difference from quality assurance.
    Trap
    Treating it as the organization's quality assurance function.

  • Change authority and change budget

    A person or group to whom the board delegates decisions on requests for change or off-specifications, optionally with a budget to fund them.

    Remember
    Without delegation, the project board is the change authority.
    Tested as
    A stem asks who can approve a change.
    Trap
    Assuming the project manager approves all changes by default.

  • Acceptance criteria vs. quality criteria

    Acceptance criteria are measurable attributes for the whole project product, in the project product description; quality criteria apply to individual products, in their product descriptions.

    Remember
    Acceptance criteria are prioritised and agreed between customer and supplier.
    Tested as
    A stem names a criterion and asks where it is recorded.
    Trap
    Recording project-level acceptance criteria in a single product description.

  • Product register and quality register

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

    Remember
    These 7th-edition records replace older configuration management terminology.
    Tested as
    Questions ask which register shows quality review results.
    Trap
    Using 6th-edition names such as configuration item records.

  • Quality review technique roles

    Chair, presenter, reviewer and administrator.

    Remember
    The presenter represents the producer of the product; the chair runs the review.
    Tested as
    Role-matching questions use these four names.
    Trap
    Assuming the producer chairs their own review.

  • Cause, event, effect

    A risk description states the source of the risk, the uncertain event, and the impact on objectives.

    Remember
    The event is the uncertain occurrence, not its cause or consequence.
    Tested as
    A stem gives a risk description and asks which part is the event.
    Trap
    Labelling a known current fact as the event; facts are causes.

  • Risk owner vs. risk actionee

    The risk owner manages all aspects of a risk; the risk actionee carries out a specific response under the owner's direction.

    Remember
    Owner is accountable for the risk; actionee performs an action.
    Tested as
    Role definition questions.
    Trap
    Assuming they must be the same person.

  • Three issue types

    Request for change, off-specification, and problem or concern.

    Remember
    Off-specification is something that should be provided but is not, or is forecast not to be.
    Tested as
    Classification questions with a short event description.
    Trap
    Calling a missing required feature a request for change.

  • Tolerance levels

    Business layer sets project tolerances, the project board sets stage tolerances, the project manager sets work package tolerances.

    Remember
    A forecast breach is escalated one level up.
    Tested as
    Who-sets-what questions.
    Trap
    Thinking the board sets project-level tolerances.

  • Time-driven vs. event-driven controls

    Time-driven controls occur at set intervals; event-driven controls occur when something happens, such as the end of a stage or a forecast breach.

    Remember
    Highlight and checkpoint reports are time-driven; exception and end stage reports are event-driven.
    Tested as
    Classification questions.
    Trap
    Calling the end stage report time-driven because stages have planned end dates.

  • 7th-edition management approaches

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

    Remember
    Strategies became approaches, and the configuration management strategy is gone.
    Tested as
    A stem names an approach and asks which practice it belongs to.
    Trap
    Choosing a 6th-edition strategy name in an answer option.

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 change a baseline The agreed requirement itself would change Using it when a product simply fails its specification
Off-specification Something that should be provided but is not, or is forecast not to be The baseline stays the same; the product falls short Treating a missing required feature as a new requirement
Problem or concern Any other issue the project manager must resolve or escalate Not about changing or failing to meet a baseline Forcing every issue into the first two types

Checkpoint vs. highlight vs. exception report

ConceptMeaningKey differenceCommon trap
Checkpoint report Progress report on a work package Team manager to project manager, time-driven Sending it to the project board
Highlight report Regular summary of stage progress Project manager to project board, time-driven Confusing it with the checkpoint report
Exception report Report of a forecast breach of stage or project tolerance with options Project manager to project board, event-driven Using it for deviations still within tolerance

Risk vs. issue

ConceptMeaningKey differenceCommon trap
Risk An uncertain event that would affect objectives if it occurred Has not happened; may be a threat or opportunity Logging an event that has already occurred as a risk
Issue A relevant event that has happened and needs management action Already occurred or certain; handled by the issues practice Ignoring that a materialised risk becomes an issue

Project assurance vs. quality assurance

ConceptMeaningKey differenceCommon trap
Project assurance Board members' monitoring of the project on their own behalf Part of the project management team, independent of the project manager Allowing the project manager to perform it
Quality assurance Independent check that the organization's quality approach is appropriate and followed Outside the project management team, a corporate responsibility Treating it as the same thing as project assurance

Exam traps

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

  1. Project manager owns the business case

    What candidates pick
    The project manager as the role accountable for the business case.
    Why it looks right
    The project manager often writes and updates the document.
    Why it's wrong
    The project executive owns the business case and is accountable for the project's justification; the project manager prepares it on the executive's behalf.

    Clue to watch for Words such as accountable or owner point to the project executive.

  2. Off-specification called a change

    What candidates pick
    Request for change for a delivered product missing a required feature.
    Why it looks right
    Fixing the product changes it, so 'change' sounds right.
    Why it's wrong
    The requirement has not changed; the product fails to meet it, which is an off-specification.

    Clue to watch for If the product description already requires the missing item, it is off-specification.

  3. Risk or issue

    What candidates pick
    Logging a supplier's confirmed late delivery as a risk.
    Why it looks right
    Late delivery is a classic example of a risk.
    Why it's wrong
    Once it has happened or is certain, it is an issue that needs management action.

    Clue to watch for Past tense or confirmed facts mean issue; may, might or could mean risk.

  4. Board sets project tolerances

    What candidates pick
    The project board as the setter of project-level tolerances.
    Why it looks right
    The board approves the project plan.
    Why it's wrong
    Project tolerances are set by the business layer; the board sets stage tolerances within them.

    Clue to watch for The word project-level or the whole project points to the business layer.

  5. Project manager does project assurance

    What candidates pick
    An option allowing the project manager to perform project assurance to save cost.
    Why it looks right
    Combining roles is permitted in tailoring.
    Why it's wrong
    Project assurance must be independent of the project manager, so it cannot be delegated to them.

    Clue to watch for Any combination involving the project manager and project assurance is wrong.

  6. Checkpoint to the board

    What candidates pick
    Checkpoint report as the regular report the project board receives.
    Why it looks right
    Both checkpoint and highlight reports are regular progress reports.
    Why it's wrong
    Checkpoint reports go from team manager to project manager; the board receives highlight reports.

    Clue to watch for Identify the sender and recipient named in the stem.

  7. Planning starts with activities

    What candidates pick
    Identifying activities and dependencies as the first planning step.
    Why it looks right
    Many scheduling methods start from task lists.
    Why it's wrong
    PRINCE2 uses product-based planning, starting by defining the products, beginning with the project product description.

    Clue to watch for A focus-on-products principle link in the stem signals product-first planning.

Answer framework

Use this sequence for practice questions, which mostly test products, roles and definitions.

  1. Identify which practice the stem belongs to from its key word, such as benefits, tolerance, off-specification or quality review.
  2. Recall that practice's purpose and its management products, using 7th-edition names, and note which products are part of the PID and which are registers, logs or reports.
  3. If a role is asked, check the level: business layer, project board, project manager or team manager, and whether accountability or preparation is meant.
  4. If an event is described, classify it first: risk or issue, then the issue type.
  5. Read for negatives such as NOT before selecting, and reject options using retired 6th-edition terms such as themes or the configuration management strategy.

Practice question

The business layer has set time and cost tolerances for the whole project. The project manager is now preparing the plan for the next management stage. Which role sets the tolerances that the project manager must work within for that stage?

Want more like this? The PRINCE2 7 Foundation 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

Plan fifteen to twenty hours here, more than half your study time, and work through the practices in manual order: business case, organization, plans, quality, risk, issues, progress. For each, make one page listing its purpose, management products, role responsibilities and two or three defined terms. That structure matches how questions are asked.

The highest-priority items are the role responsibilities in organization, the tolerance levels and reports in progress, and the issue types. Learn the 7th-edition product names carefully, especially the management approaches in the PID, because old 6th-edition names appear as distractors. The most commonly underestimated area is quality: candidates skim it, then lose marks on acceptance versus quality criteria, the quality register versus the product register, and quality review roles.

After each practice, take a short targeted quiz before moving on, because recall fades quickly across seven similar chapters. When all seven are done, build a single table of every management product with its owning practice, creator, approver and the process where it is first produced. Then move to the processes domain, which reuses the same products in time order.

FAQ

How many questions come from the practices?

The learning outcome is weighted at 60%, about 36 of 60 questions on that basis. PeopleCert publishes the weight, not a per-outcome count.

What happened to the themes from the 6th edition?

They are now called practices. The change theme became the issues practice, and strategies became management approaches in the PID.

Which practices should I prioritise?

Spend most time on organization, progress and issues, where role, tolerance and classification questions are frequent, but do not skip quality, which candidates often underestimate.

Who owns the business case?

The project executive. The project manager may prepare it, and senior users specify the benefits and are accountable for their realization.

What is the difference between a risk and an issue?

A risk is uncertain and may or may not occur; an issue has happened or is certain and needs management action. A risk that occurs becomes an issue.

Do I need to memorise the content of every management product?

Know the purpose, owner and main content of each product well enough to recognise them; you are not asked to reproduce product outlines word for word.

How do the practices relate to the processes?

Practices are addressed throughout the project; processes say when practice products are created, reviewed and updated, such as the PID in initiating a project.

Other Project Management certifications

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

Test your Domain 4 knowledge

Check that you can name each practice's products and owners, classify issues and risks, and say who sets each tolerance under timed conditions.

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

Keep going