PRINCE2 7 Practitioner · Domain 4 of 4

PRINCE2 7 Practitioner Domain 4: Applying and Tailoring PRINCE2 Processes

Processes turn the practices into a lifecycle: who does what, with which inputs and outputs, from mandate to closure. You carry out each process for the scenario and judge whether its activities and roles are fit for purpose.

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

About 18 min read Reviewed October 2026

Overview

This domain covers the seven processes: starting up a project, directing a project, initiating a project, controlling a stage, managing product delivery, managing a stage boundary and closing a project. Criterion x.x.1 asks you to carry out each process at Bloom's level 3, knowing its activities, inputs and outputs, the roles and responsibilities shown in its RACI table, and how the practices are applied within it. Criterion x.x.2 asks you to analyse at level 4 whether a process's activities and roles are effective and fit for purpose, considering tailoring, the practices, and the process's purpose and objectives.

Processes are where timing matters. The same product, such as the business case, is drafted in starting up, completed in initiation, updated at each stage boundary and reviewed at closure. Questions place you at a point in the scenario and ask what should happen next and who should do it.

How it's tested

Process questions place you at a moment in the scenario and ask what should be done, by whom, or whether an action is appropriate. Level 3 items test activities, inputs, outputs and RACI roles. Level 4 items judge whether a process is being carried out or tailored in a way that meets its purpose. Matching items may pair activities with roles or processes.

  • What happens next?

    The scenario reaches a point, such as a stage nearing its end, and you choose the correct next activity and product.

  • Who is responsible?

    An activity is described and you choose the role that is accountable or responsible, using the process RACI table in the manual.

  • Is this process carried out appropriately?

    A shortened or tailored process is described and you judge whether it still meets the process's purpose and objectives.

Reasoning it through

The scenario says stage 2 is almost complete and the project manager has asked the team managers to start stage 3 work while the board meets next month. Identify the process: managing a stage boundary, followed by the board authorizing a stage in directing a project. Work for stage 3 cannot be authorized until the board approves the next stage plan, so starting it early fails the process purpose and manage by stages.

Syllabus topics 7

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

4.1 Starting up a projectPre-project checks that the project is viable and worthwhile before initiation.
What it means
Starting up a project is triggered by the project mandate from the business layer and ensures the prerequisites for initiation are in place, so that no one commits to initiation without a reasonable basis.
What to understand
The business layer appoints the project executive, who appoints the project manager. Previous lessons are captured, the project management team is designed and appointed, the outline business case is prepared by the executive with the project manager's help, the project approach is chosen, the project brief is assembled and the initiation stage is planned. It ends with a request to the board to authorize initiation.
How it shows up
A scenario describes a mandate arriving and asks which activity comes next or who should appoint whom.
Common confusion
Candidates think the project board appoints the executive or that the project manager owns the outline business case; the business layer appoints the executive, and the executive owns the business case.
4.2 Directing a projectThe project board's decision-making from start-up to closure.
What it means
Directing a project lets the project board be accountable for the project's success by making key decisions and exercising overall control, while delegating day-to-day management to the project manager.
What to understand
The board authorizes initiation, authorizes the project, authorizes each stage or an exception plan, gives direction during a stage when needed, and authorizes closure. It manages by exception, relying on highlight, exception and end stage reports, and keeps the business layer informed. It does not run the work itself.
How it shows up
A board decision is described and you judge whether it is appropriate or which decision point it belongs to.
Common confusion
Candidates assume the board must meet regularly to review progress; it receives highlight reports and meets mainly at decision points or when an exception arises.
4.3 Initiating a projectEstablish the foundations for the project and create the PID.
What it means
Initiating a project sets up the management foundations, so the organization understands the work needed to deliver the project's products before committing significant spend.
What to understand
The project manager agrees tailoring requirements and prepares the management approaches, sets up project controls, creates the project plan, and with the executive refines the outline business case into a full business case. These are assembled into the project initiation documentation (PID), which the board reviews when deciding to authorize the project.
How it shows up
A scenario shows initiation being shortened or skipped and asks whether that is appropriate, or which product should be created now.
Common confusion
Candidates think the PID is created in starting up; starting up produces the project brief and initiation stage plan, and the PID comes from initiation.
4.4 Controlling a stageDay-to-day management of a stage by the project manager.
What it means
Controlling a stage covers how the project manager assigns work, monitors it, deals with issues and risks, reports progress and takes corrective action so the stage stays within tolerance.
What to understand
The project manager authorizes work packages, reviews their status and the stage status, receives completed work packages, issues highlight reports to the board, captures and assesses issues and risks, takes corrective action within stage tolerance, and escalates with an exception report when stage tolerance is forecast to be exceeded.
How it shows up
A deviation or new issue is described and you decide whether the project manager should take corrective action or escalate.
Common confusion
Candidates escalate any deviation; the project manager acts within stage tolerance and escalates only a forecast breach.
4.5 Managing product deliveryThe team manager's link between the project manager and the specialist work.
What it means
Managing product delivery controls the link between the project manager and team managers by agreeing requirements for acceptance, execution and delivery of work packages.
What to understand
The team manager accepts a work package after agreeing it with the project manager, produces a team plan if needed, executes the work, sends checkpoint reports, ensures quality activities are carried out and recorded, obtains approval for completed products and delivers the work package back. Team tolerances are set in the work package description, and a forecast breach is raised to the project manager as an issue.
How it shows up
A team manager's action is described and you judge whether it is appropriate, for example starting work without an agreed work package.
Common confusion
Candidates let team managers escalate directly to the board; they escalate to the project manager, who set their tolerance.
4.6 Managing a stage boundaryPrepare for the board's decision at the end of each stage or after an exception.
What it means
Managing a stage boundary gives the board the information it needs to review the current stage, approve the next stage plan, review the updated project plan, and confirm continued business justification; it is also used to produce an exception plan.
What to understand
Near the end of each stage except the last, the project manager plans the next stage, updates the project plan and business case, reviews risks, and reports stage end with an end stage report, possibly with a lessons report. When the board asks for an exception plan, the same process prepares it.
How it shows up
A scenario reaches a stage end and asks what should be prepared or updated, or whether an approach skips something essential.
Common confusion
Candidates forget that the business case and project plan are updated at every boundary, not only when something changes.
4.7 Closing a projectConfirm acceptance, hand over and evaluate the project, then recommend closure.
What it means
Closing a project provides a fixed point at which acceptance of the project product is confirmed and the project's objectives are recognised as achieved, or it is recognised that nothing more can usefully be done.
What to understand
For planned closure, the project manager confirms acceptance, hands over products, evaluates the project against the PID in an end project report, produces a lessons report, makes sure the benefits management approach covers post-project reviews, and recommends closure to the board. Premature closure follows a board instruction and salvages anything useful.
How it shows up
A closure situation is described and you decide what should happen, such as who receives follow-on actions or what happens to post-project benefit reviews.
Common confusion
Candidates think the project manager closes the project; the project manager recommends closure and the board authorizes it in directing a project.

High-yield concepts

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

  • Project mandate

    The trigger from the business layer that starts the starting up a project process.

    Remember
    Its content can range from a verbal instruction to a detailed document, and starting up builds the project brief from it.
    Tested as
    Questions place the scenario at the mandate and ask what happens first.
    Trap
    Treating the mandate as the approved PID.

  • Appointment sequence

    The business layer appoints the project executive, and the executive appoints the project manager.

    Remember
    The rest of the project management team is designed and appointed in starting up, before initiation.
    Tested as
    Role questions test who appoints whom at the very start.
    Trap
    Having the project board appoint its own executive.

  • Five board decision points

    Authorize initiation, authorize the project, authorize a stage or exception plan, give direction during the stage, authorize closure.

    Remember
    Only giving direction is ad hoc; the other four are planned decisions in directing a project.
    Tested as
    Board questions test which decision fits the scenario moment.
    Trap
    Assuming the board approves every work package.

  • Project brief vs. PID

    The project brief comes from starting up and supports the decision to initiate; the PID comes from initiation and supports the decision to authorize the project.

    Remember
    The PID is the baseline for the end project report's comparison at closure.
    Tested as
    Questions ask which product is being reviewed at a given decision.
    Trap
    Expecting the full business case in the project brief.

  • Outline vs. full business case

    The outline business case is prepared in starting up; it is refined into the full business case in initiation.

    Remember
    The business case is then updated at each stage boundary and reviewed at closure.
    Tested as
    Business case timing is tested through process questions.
    Trap
    Thinking the business case is frozen once the PID is approved.

  • Work package

    The authorized set of information about one or more products that a team manager agrees to deliver.

    Remember
    It includes the work package description, product descriptions, tolerances, reporting and constraints.
    Tested as
    Managing product delivery questions start from whether a work package was properly agreed.
    Trap
    Letting team managers begin work from an informal request.

  • Corrective action vs. escalation

    The project manager takes corrective action within stage tolerance and escalates with an exception report when a breach is forecast.

    Remember
    Team managers raise forecast team tolerance breaches as issues to the project manager.
    Tested as
    Controlling a stage questions hinge on the size of the deviation versus tolerance.
    Trap
    Escalating a deviation the project manager has authority to fix.

  • End stage report

    The project manager's report at a stage boundary on how the stage performed and the project's status.

    Remember
    It accompanies the next stage plan and the updated project plan and business case.
    Tested as
    Stage boundary questions ask which products the board needs.
    Trap
    Using a highlight report in place of the end stage report.

  • Exception plan through the stage boundary

    When the board requests an exception plan, managing a stage boundary produces it for approval.

    Remember
    Once approved, it replaces the plan whose tolerance was forecast to be exceeded.
    Tested as
    Questions test which process prepares the exception plan.
    Trap
    Placing exception planning in controlling a stage.

  • Planned vs. premature closure

    Planned closure follows completion of the final stage; premature closure follows a board instruction when the project is no longer justified or viable.

    Remember
    Premature closure still hands over useful products and records lessons and follow-on actions.
    Tested as
    Closing questions test what still happens when a project stops early.
    Trap
    Abandoning products and lessons when a project closes early.

  • Post-project benefit reviews

    Benefit reviews after closure are planned in the benefits management approach and owned outside the project.

    Remember
    Closing a project ensures the approach covers reviews after the project management team disbands.
    Tested as
    Questions ask who carries out benefit reviews after closure.
    Trap
    Keeping the project open until all benefits are realized.

  • RACI tables

    Each process chapter has a table showing which roles are responsible, accountable, consulted and informed for each activity.

    Remember
    Syllabus criterion b for every process cites the RACI table, so tab them in the manual.
    Tested as
    Many 'who does what' questions are answered directly by these tables.
    Trap
    Answering from instinct when the table gives the exact role.

Side by side

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

Starting up a project vs. initiating a project

ConceptMeaningKey differenceCommon trap
Starting up a project Pre-project process checking the project is worthwhile and viable Produces the project brief and initiation stage plan Expecting detailed approaches and the project plan here
Initiating a project First management stage that builds the project's foundations Produces the PID, including the full business case, project plan and approaches Treating it as optional on small projects

Controlling a stage vs. managing a stage boundary

ConceptMeaningKey differenceCommon trap
Controlling a stage Day-to-day management of work, issues, risks and reporting within the stage Uses highlight reports and corrective action within tolerance Preparing the next stage plan here
Managing a stage boundary Preparing the board's decision at the end of a stage or after an exception Produces the next stage plan or exception plan and the end stage report Skipping the business case update because nothing seems to have changed

Project manager vs. team manager vs. project board in delivery

ConceptMeaningKey differenceCommon trap
Project board Authorizes stages, exception plans and closure in directing a project Decides at planned points and on exceptions Approving individual work packages
Project manager Authorizes work packages and manages the stage in controlling a stage Acts within stage tolerance and escalates forecast breaches Authorizing the next stage without the board
Team manager Accepts, executes and delivers work packages in managing product delivery Reports by checkpoint reports to the project manager Escalating directly to the project board

Exam traps

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

  1. Start the next stage early

    What candidates pick
    Let team managers begin next-stage work while waiting for the board meeting.
    Why it looks right
    It keeps the team busy and protects the schedule.
    Why it's wrong
    Work in a new stage needs the board to approve the next stage plan through directing a project; starting early bypasses manage by stages.

    Clue to watch for The board has not yet reviewed the end stage report and next stage plan.

  2. Project manager closes the project

    What candidates pick
    Have the project manager notify stakeholders that the project is closed once products are handed over.
    Why it looks right
    The project manager runs closing a project, so closure feels like their call.
    Why it's wrong
    The project manager recommends closure; the board authorizes closure in directing a project and notifies the business layer.

    Clue to watch for Products are accepted and the question asks who confirms closure.

  3. Skip initiation for a small project

    What candidates pick
    Move straight from the project brief to delivery work to save time.
    Why it looks right
    Small projects are tailored, and initiation can feel like overhead.
    Why it's wrong
    Initiation can be short and light, but it is the first management stage and gives the board the PID to authorize the project; removing it breaks manage by stages.

    Clue to watch for The option removes the board's authorization of the project, not just reduces documentation.

  4. Team manager escalates to the board

    What candidates pick
    Have the team manager send an exception report to the board for a work package overrun.
    Why it looks right
    It seems fast and transparent.
    Why it's wrong
    Team managers raise forecast breaches of work package tolerance to the project manager as an issue; only the project manager raises exception reports to the board.

    Clue to watch for The deviation is at work package level.

  5. Business case untouched at the boundary

    What candidates pick
    Agree the business case need not be updated because costs have not changed.
    Why it looks right
    Updating an unchanged document looks like busywork.
    Why it's wrong
    Managing a stage boundary reviews and updates the business case every time, because benefits, risks and context can change even when costs do not, and the board must confirm continued justification.

    Clue to watch for The scenario is at a stage end and the business case was last reviewed at initiation.

  6. Post-project reviews inside the project

    What candidates pick
    Keep the project open until all benefits have been measured.
    Why it looks right
    It seems to prove the project delivered value before closing.
    Why it's wrong
    Benefits that occur after closure are reviewed under the benefits management approach by the business; keeping the project open wastes resources.

    Clue to watch for Benefits are expected months after handover.

Answer framework

Use these steps whenever a process question places you at a point in the scenario.

  1. Identify which process is running from the scenario's timing: before initiation, within a stage, near a boundary, or at the end.
  2. Recall that process's purpose and its activities, then find the activity the question describes in the manual chapter.
  3. Check the RACI table for who is responsible and accountable, and reject options that give the action to the wrong role.
  4. Identify which practice products are created, updated or used at this point, such as the business case, plans or registers.
  5. Choose the option that meets the process objectives with any tailoring the context justifies, without removing a board decision or a principle.

Practice question

During a stage, a team manager reports a forecast three-day delay to a work package, exceeding its time tolerance. The stage has ten days of time tolerance left, and no other tolerances are affected. What should the project manager do?

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

Checklist

0 of 13

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

Study strategy

Learn the processes as a single timeline before studying each one: mandate, starting up, authorize initiation, initiation, authorize the project, stages with controlling a stage and managing product delivery, stage boundaries, and closing. Sketch the timeline inside the manual's cover and note at each point which board decision applies, because many questions are really about where in this sequence the scenario sits.

Then study each process chapter for its purpose, activities and RACI table, and mark the practice products it creates or updates. Give the most time to controlling a stage and managing a stage boundary, since they run repeatedly and generate most 'what next' situations. Candidates underestimate directing a project, assuming the board does little, and closing a project, especially premature closure and post-project benefit reviews.

Afterwards, practise with full-length scenarios: for each question, write the process, the role and the product before choosing an answer. Then take a timed mock exam, using the manual only to confirm roles and products rather than to learn them.

FAQ

How much of the exam is about processes?

The processes learning outcome is 30% of the 70 marks. About 21 marks is a weight-based editorial estimate; PeopleCert does not publish per-process counts.

Do I need to memorise every activity in every process?

The exam is open book, so you can check activities and RACI tables in the manual. You still need enough familiarity to recognise which process applies and find the right table quickly.

What is the difference between criteria x.x.1 and x.x.2 for processes?

x.x.1 asks you to carry out the process: activities, inputs and outputs, roles, and how practices are applied. x.x.2 asks whether its activities and roles are effective and fit for purpose, considering tailoring, the practices and the process objectives.

Can initiation be skipped on a small project?

No. Initiation can be short and light, but it is always a separate management stage, giving the board the PID to authorize the project.

Who closes a PRINCE2 project?

The project manager carries out closing a project and recommends closure. The project board authorizes closure in directing a project.

How do processes connect to practices?

Each process applies the practices at a specific moment, for example the business case is drafted in starting up, completed in initiation and updated at each stage boundary. The processes chapters' tables show how each practice is applied.

How long should I spend on processes?

An editorial estimate is 15 to 20 hours, mostly on scenario practice. Study after the practices, since process questions assume you know the products they create.

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

You have traced the seven processes from mandate to closure, with their roles and decision points. Check whether you can place a scenario moment in the right process and choose the right role under time pressure.

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

Keep going