PRINCE2 7 Foundation · Domain 5 of 5

PRINCE2 7 Foundation Domain 5: PRINCE2 Processes

Seven processes take a PRINCE2 project from mandate to closure. Foundation asks you to know each process's purpose, what triggers it, who carries it out and which key products it creates.

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

About 15 min read Reviewed October 2026

Overview

This domain covers the seven PRINCE2 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. Each process is a structured set of activities for a particular point or level in the project, and each has a defined purpose, objectives, trigger, responsible roles and key products.

The processes are where the practices are applied in time order: the project brief and outline business case appear in starting up a project, the PID in initiating a project, highlight and exception reports in controlling a stage, and the end project report in closing a project. Four processes map to management levels: directing is the project board's, controlling a stage and managing a stage boundary are the project manager's, and managing product delivery is the team manager's.

How it's tested

Process questions test purpose, sequence and responsibility. A stem names a process and asks for its purpose or an objective, describes an activity and asks which process it belongs to, or asks what triggers a process. Expect similar-sounding options from neighbouring processes, so precise knowledge of start and end points matters.

  • Purpose of a process

    You choose the statement that matches a named process's purpose, with distractors taken from the purposes of related processes.

  • Which process does this?

    An activity or product, such as preparing the project brief or producing an end stage report, is described and you name the process.

  • Trigger and sequence

    You identify what starts a process, such as the project mandate, or what happens next at a given point in the life cycle.

Reasoning it through

A stem asks which process provides the board with information to decide whether to approve the next stage plan. Reason by timing: the decision falls at the end of a stage, so the information comes from managing a stage boundary, which produces the end stage report and the next stage plan. Controlling a stage is the tempting distractor, but it manages work within a stage rather than preparing for the next.

Syllabus topics 7

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

5.1 Starting up a projectThe pre-project process that checks whether the project is worthwhile and viable before initiation.
What it means
Starting up a project ensures the prerequisites for initiating the project are in place by answering whether the project is viable and worthwhile. It is triggered by the project mandate from the business layer.
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, the project approach is chosen, the project brief is assembled and the initiation stage is planned.
How it shows up
Expect a question on what triggers this process, or which product it assembles, usually the project brief.
Common confusion
Confusing it with initiating a project; start-up is pre-project and produces the project brief, while initiation produces the PID.
5.2 Directing a projectHow the project board exercises overall control and makes key decisions.
What it means
Directing a project enables the project board to 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
It runs from the request to initiate the project until closure. The board authorizes initiation, authorizes the project, authorizes each stage or exception plan, gives ad hoc direction, and authorizes project closure. It manages by exception and keeps the business layer informed.
How it shows up
A stem lists board activities and asks which is part of directing a project, or which decision comes first.
Common confusion
Thinking the board manages daily work or attends frequent team meetings; it directs through decisions and reports.
5.3 Initiating a projectThe first management stage, establishing the foundations before significant spend is committed.
What it means
Initiating a project establishes solid foundations so the organization understands the work required to deliver the products before committing to significant spend.
What to understand
The project manager agrees tailoring requirements, prepares the management approaches, sets up project controls, creates the project plan and, with the executive, refines the business case. These are assembled into the project initiation documentation (PID) for the board's decision to authorize the project.
How it shows up
Expect questions on the main output of this process or on what the board decides at the end of it.
Common confusion
Thinking the initiation stage is optional for small projects; it is always the first management stage.
5.4 Controlling a stageThe project manager's day-to-day management of a stage within tolerance.
What it means
Controlling a stage covers assigning work, monitoring it, dealing with issues and risks, reporting progress to the board and taking corrective action to keep the stage within tolerance.
What to understand
The project manager authorizes work packages, reviews their and the stage's status, receives completed work packages, issues highlight reports, captures and assesses issues and risks, takes corrective action within tolerance, and escalates with an exception report when stage tolerance is forecast to be exceeded.
How it shows up
A stem describes a deviation and asks what the project manager does within this process.
Common confusion
Escalating every deviation to the board; corrective action within tolerance stays with the project manager.
5.5 Managing product deliveryThe team manager's process for accepting, executing and delivering work packages.
What it means
Managing product delivery controls the link between the project manager and team managers by agreeing the requirements for accepting, executing and delivering work.
What to understand
The team manager accepts a work package, may produce a team plan, ensures the products are developed and quality-checked, sends checkpoint reports, obtains approval of completed products and delivers the work package back to the project manager.
How it shows up
Expect a question on which role carries out this process or which report it produces.
Common confusion
Assuming it describes how specialist work is technically done; it covers management of the work package, not the specialist technique.
5.6 Managing a stage boundaryPreparing the board's decision at the end of a stage or when an exception plan is needed.
What it means
Managing a stage boundary gives the board the information 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 prepare 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 with an end stage report and, where useful, a lessons report.
How it shows up
A stem asks which process produces the end stage report, or which process is used to create an exception plan.
Common confusion
Thinking it only applies at planned stage ends; it is also used when the board requests an exception plan.
5.7 Closing a projectProviding a fixed point for acceptance and handover, or for premature 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 that nothing more can usefully be done.
What to understand
The project manager confirms acceptance, hands over products, evaluates the project with an end project report and a lessons report, makes sure benefits reviews are planned, and recommends closure to the board, which then authorizes it. Premature closure follows a board instruction.
How it shows up
Expect questions on the purpose of closing a project or on who authorizes closure.
Common confusion
Thinking the project manager closes the project alone; the project manager recommends closure and the board authorizes it.

High-yield concepts

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

  • Project mandate

    The trigger for starting up a project, provided by the business layer.

    Remember
    It may be anything from a brief instruction to a detailed document.
    Tested as
    Trigger questions for the first process.
    Trap
    Choosing the project brief as the trigger; the brief is an output of start-up.

  • Appointment sequence

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

    Remember
    The rest of the team is designed and appointed afterwards in start-up.
    Tested as
    Questions on who appoints whom.
    Trap
    Assuming the project manager appoints the executive or the board.

  • Project brief

    Assembled in starting up a project to give a full and firm foundation for initiation, including the outline business case.

    Remember
    It is the basis of the board's decision to authorize initiation.
    Tested as
    Which-process and which-product questions.
    Trap
    Confusing it with the PID.

  • Project initiation documentation (PID)

    Assembled in initiating a project; contains the management approaches, project plan, business case, controls and tailoring.

    Remember
    The board reviews it when deciding to authorize the project.
    Tested as
    Output of initiating a project.
    Trap
    Placing its creation in starting up a project.

  • Board decisions in directing a project

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

    Remember
    The board makes decisions; the project manager prepares the information.
    Tested as
    Questions list activities and ask which belong to the board.
    Trap
    Including day-to-day work allocation as a board activity.

  • Work package

    The set of information about products to be delivered, agreed between project manager and team manager, including tolerances and reporting.

    Remember
    Authorized in controlling a stage, accepted and executed in managing product delivery.
    Tested as
    Links the project manager's and team manager's processes.
    Trap
    Thinking the team manager starts work without an agreed work package.

  • Corrective action vs. escalation

    Within tolerance, the project manager takes corrective action; a forecast breach of stage tolerance is escalated with an exception report.

    Remember
    The tolerance boundary decides who acts.
    Tested as
    Controlling a stage scenarios.
    Trap
    Escalating a deviation that is still within tolerance.

  • End stage report

    Produced in managing a stage boundary to summarise stage performance and the project's status for the board.

    Remember
    It is event-driven and supports the board's next-stage decision.
    Tested as
    Which-process-produces-it questions.
    Trap
    Placing it in controlling a stage.

  • Exception plan

    Prepared in managing a stage boundary at the board's request after an exception report, replacing the plan it covers.

    Remember
    The same process handles planned stage ends and exception plans.
    Tested as
    Questions on which process creates an exception plan.
    Trap
    Thinking it is created in controlling a stage.

  • End project report

    Produced in closing a project to review how the project performed against the PID.

    Remember
    It is accompanied by a lessons report and a check that benefit reviews are planned.
    Tested as
    Closing-process questions.
    Trap
    Confusing it with the end stage report.

  • Premature closure

    Closing the project early on the board's instruction, for example when the business case is no longer valid.

    Remember
    Useful products are salvaged and gaps documented.
    Tested as
    Questions on what happens if justification is lost.
    Trap
    Assuming the project manager can decide to close early alone.

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 check that the project is viable and worthwhile Triggered by the mandate; produces the project brief and initiation stage plan Placing the PID or detailed business case here
Initiating a project First management stage establishing solid foundations Produces the PID and project plan for authorization of the project Treating it as optional or as part of start-up

Controlling a stage vs. managing a stage boundary

ConceptMeaningKey differenceCommon trap
Controlling a stage Day-to-day management of the current stage Work packages, highlight reports, issues and risks, exception reports Using it to prepare the next stage plan
Managing a stage boundary Preparing the board's decision at stage end or for an exception plan Next stage plan, updated project plan and business case, end stage report Forgetting it also prepares exception plans

Which level runs which process

ConceptMeaningKey differenceCommon trap
Project board Directing a project Decisions and overall control Assigning day-to-day management to the board
Project manager Starting up (with the executive), initiating, controlling a stage, managing a stage boundary, closing Day-to-day management within tolerances Thinking the project manager authorizes the project
Team manager Managing product delivery Delivers work packages and checkpoint reports Thinking the team manager reports directly to the board

Exam traps

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

  1. Brief versus PID

    What candidates pick
    Initiating a project as the process that assembles the project brief.
    Why it looks right
    Both are early documents describing the project.
    Why it's wrong
    The project brief is assembled in starting up a project; initiating a project assembles the PID.

    Clue to watch for Brief means start-up; initiation documentation means initiation.

  2. Mandate versus brief as trigger

    What candidates pick
    The project brief as the trigger for starting up a project.
    Why it looks right
    The brief sounds like an initial instruction.
    Why it's wrong
    The trigger is the project mandate from the business layer; the brief is produced by the process.

    Clue to watch for Ask whether the item comes from outside the project or from the process itself.

  3. Stage boundary work in controlling a stage

    What candidates pick
    Controlling a stage as the process that produces the next stage plan or end stage report.
    Why it looks right
    Both happen while the project manager is running the current stage.
    Why it's wrong
    Planning the next stage and reporting the stage end are in managing a stage boundary.

    Clue to watch for Words such as next stage, end of stage or exception plan point to managing a stage boundary.

  4. The board runs the work

    What candidates pick
    An option listing work package authorization as a board activity.
    Why it looks right
    The board is accountable, so it seems to authorize everything.
    Why it's wrong
    The board authorizes the project and stages; the project manager authorizes work packages in controlling a stage.

    Clue to watch for Work package language belongs to the project manager and team manager.

  5. Project manager closes the project

    What candidates pick
    The project manager as the role that authorizes closure.
    Why it looks right
    The project manager carries out most closing activities.
    Why it's wrong
    The project manager recommends closure; the board authorizes it in directing a project.

    Clue to watch for Authorize is a board verb in PRINCE2.

  6. Processes run once

    What candidates pick
    A statement that each process is performed once in sequence.
    Why it looks right
    A numbered list of processes suggests a linear flow.
    Why it's wrong
    Controlling a stage, managing product delivery and managing a stage boundary repeat for each delivery stage, and directing runs throughout.

    Clue to watch for Options with 'once' or 'only at the start' about these processes are wrong.

Answer framework

Use this sequence to place an activity or product in the correct process.

  1. Locate the point in the life cycle: before initiation, the initiation stage, during a delivery stage, near a stage end, or at closure, using clues such as mandate, PID or next stage.
  2. Identify the role doing the work: business layer, project board, project manager or team manager.
  3. Match the key product to its process, such as brief in start-up, PID in initiation, end stage report at the stage boundary.
  4. Separate the neighbouring pairs: start-up versus initiation, and controlling a stage versus managing a stage boundary.
  5. Check verbs: the board authorizes and directs, the project manager prepares, controls and recommends, and the team manager accepts, executes and delivers work packages.

Practice question

A business layer has issued a project mandate. The newly appointed project executive and project manager now assemble a document that sets out the project definition and outline business case so the project board can decide whether to authorize initiation. Which process are they in?

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

Checklist

0 of 14

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

Study strategy

Allow four to five hours and study this domain after the practices, because most process questions turn on which practice product a process creates. Start with a one-page timeline: pre-project, initiation stage, delivery stages, final stage. Place each process on it and mark which role runs it.

High-priority content is the purpose of each process, the trigger for starting up a project, the board's decisions in directing a project, and the key products of each process. The commonly underestimated areas are the two neighbouring pairs. Write a two-line comparison for start-up versus initiation and for controlling a stage versus managing a stage boundary, and test yourself on them until you can place any product correctly.

Then practise with questions that describe an activity and ask for the process. For every miss, note whether you misjudged the timing or the role, since those are the two errors this domain produces. Finish with a full-length timed mock exam of 60 questions in 60 minutes, which also checks your pace across all five learning outcomes.

FAQ

How many questions come from the processes?

The learning outcome is weighted at 15%, about nine of 60 questions as an estimate. Per-outcome counts are not published.

Is starting up a project part of the first stage?

No. Starting up a project is pre-project work; the initiation stage is the first management stage.

Which processes repeat during the project?

Controlling a stage, managing product delivery and managing a stage boundary repeat for each delivery stage, and directing a project runs from the request to initiate until closure.

Who runs managing product delivery?

The team manager. If no separate team manager is appointed, the project manager may carry out the role.

What is the difference between an end stage report and an end project report?

The end stage report is produced in managing a stage boundary to support the next-stage decision; the end project report is produced in closing a project to evaluate the whole project.

Do I need to memorise every process activity name?

Know each process's purpose, trigger, main activities in plain terms, responsible roles and key products; recognising activities is more useful than reciting their names.

How do the processes relate to the practices?

The processes say when practice products are created and updated, such as the business case being outlined in start-up, detailed in initiation and updated at stage boundaries.

Other Project Management certifications

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

Test your Domain 5 knowledge

Check that you can place products and activities in the correct process and tell start-up from initiation under timed conditions.

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

Keep going