Exam objective 1.3 asks you to describe the purpose and structure of the seven PRINCE2 themes. These themes are the beating heart of the methodology — they ensure every project is properly justified, organised, and controlled. Without understanding the themes, you cannot pass the PRINCE2 Foundation exam, because they appear in nearly every question.
Jump to a section
An experienced event planner is the central figure in organising a large wedding. They must handle the business case — is the budget approved, and will the venue and catering deliver value for money? They coordinate the organisation: who is the bride’s point of contact, who manages the caterers, who handles the band? They set quality standards: what colour must the tablecloths be, and how many tasting sessions are allowed before the menu is finalised? They create a plan: a timeline for booking the venue, sending invitations, and ordering the cake. They manage risk: what if it rains, or the caterer cancels? They handle change: the bride decides last-minute to switch from roses to peonies. And they track progress: are we on schedule to have everything ready by the wedding day?
These seven concerns — business case, organisation, quality, plans, risk, change, and progress — are exactly the PRINCE2 themes. Just as an event planner cannot run a wedding by only thinking about the flowers, a project manager cannot run a successful project by focusing on just one area. Each theme provides a specific lens through which you must view the project at all times. Without the business case theme, you might spend money without knowing if the project is still worthwhile. Without the progress theme, you would have no idea if you were running late. The themes are not separate boxes; they interact with one another. For example, a change request (change theme) might increase costs, which must be checked against the business case, and if approved, the plan and progress reports must be updated.
The word ‘theme’ in PRINCE2 means a specific area of project management that must be continuously addressed throughout the project’s life. Unlike a ‘process’ (a set of activities you do at a particular time), a ‘theme’ is a constant concern. Think of themes as lenses through which you look at your project at every stage. There are exactly seven themes: business case, organisation, quality, plans, risk, change, and progress.
Why do themes exist? Before PRINCE2, people often managed projects by just making a plan and hoping for the best. They forgot to check whether the project was still a good idea (business case). They did not define roles properly (organisation). They delivered work that did not meet the customer’s expectations (quality). PRINCE2’s seven themes force you to ask the right questions at the right time. They replace guesswork with discipline.
The Business Case theme answers the question: ‘Why are we doing this project, and is it still worth it?’ It is the most important theme. If there is no justifiable reason to start or continue a project, you should stop. The business case documents the expected benefits (the good things the project will deliver), the costs, and the risks. It is reviewed regularly.
The Organisation theme answers: ‘Who does what?’ It defines the roles and responsibilities. PRINCE2 has four levels of management: corporate or programme management, the project board (which includes the executive, senior user, and senior supplier), the project manager, and the team. Each has clear authority. This prevents confusion about who makes decisions.
The Quality theme answers: ‘What must we deliver, and how do we know it is good enough?’ It involves setting quality criteria (standards the product must meet), quality methods (how you will check, e.g., inspections or tests), and quality records (evidence that checks happened). The goal is to make sure the final product satisfies the customer’s needs.
The Plans theme answers: ‘How, when, and by whom will the work be done?’ Plans exist at three levels: the project plan (big picture, created at the start), the stage plan (detailed plan for the current stage of work), and, if needed, team plans and exception plans (used if things go badly wrong). Plans help you predict timelines and costs.
The Risk theme answers: ‘What could go wrong (or right), and what are we doing about it?’ A risk is an uncertain event that could affect the project. PRINCE2 requires you to identify risks, assess their probability and impact, and decide how to respond (e.g., avoid, reduce, transfer, accept, or share). You must also look for opportunities (positive risks).
The Change theme answers: ‘How do we handle requests for change and things that go wrong?’ When someone asks for a new feature (an issue) or something breaks (a defect), you need a controlled way to decide whether to accept it. PRINCE2 uses a change control approach and, for large projects, a change authority or a change board. Small changes can be delegated, but big ones must go through formal review.
The Progress theme answers: ‘Are we on track, and should we continue?’ This theme involves comparing actual progress against the plan. You use tolerances (allowable deviations in time and cost) to decide if action is needed. If tolerances are exceeded, you escalate to the project board, which decides how to respond. Progress is monitored through reports, checkpoint meetings, and stage assessments.
The seven themes are not optional — PRINCE2 mandates that every project must address them. However, how you apply them can be tailored (adjusted) to fit the project’s size and complexity. A small project might have a simple one-page business case, while a large one might have a detailed document approved by senior management. The exam tests your ability to recall the purpose of each theme and how they link together.
Identify the seven themes as permanent management lenses
Before you start a project, memorise the seven themes. They are not steps you do once; they are concerns you revisit throughout. This step is foundational because every exam question about themes assumes you know they are continuous.
Establish the Business Case theme
Create the business case document that justifies the project. Define the expected benefits, costs, and risks. The business case will be reviewed at the end of each stage to decide whether to continue. This theme ensures the project remains viable.
Define the Organisation theme
Define the project management team structure. Appoint the executive, senior user, senior supplier, project manager, and team managers. Write role descriptions. This step prevents confusion about who makes decisions and who does the work.
Plan using the Plans theme
Create the project plan (high-level) and the first stage plan (detailed). Define activities, dependencies, resources, and budgets. Without a plan, you cannot track progress or justify costs. The plans theme is how you turn ideas into a schedule.
Embed the Quality theme from the start
Define quality criteria (e.g., response time, accuracy) and quality methods (testing, review). Create a quality register to record checks. This step ensures the final product meets the customer’s expectations, not just the developer’s guesses.
Manage Risk continuously
Identify risks (both threats and opportunities) and log them in the risk register. Assess their probability and impact, then plan responses. Review the risk register regularly. This theme helps you avoid surprises and grab opportunities.
Control Changes and Issues through the Change theme
Set up a change control approach. When someone requests a change or reports a defect, log it in the issue register. Evaluate the impact on time, cost, and quality. The project board decides on major changes. This prevents scope creep and unauthorised work.
Monitor Progress against baselines
Compare actual progress (time, cost, scope, etc.) against the plan. Use tolerances to decide when to escalate. Produce highlight reports for the board and end-stage reports to authorise the next stage. This theme gives you control over the project’s trajectory.
An IT project manager working at a medium-sized software company is responsible for building a new mobile banking app for a retail bank. She uses PRINCE2 themes from day one.
Business Case in action: The bank’s senior executive (the project executive) writes a business case showing that the app will increase customer retention by 15% and save £200,000 per year compared to the old system. The project manager keeps this document updated. Every three months, she checks whether the cost estimates are still accurate. If development costs rise unexpectedly, she may need to recommend stopping the project — because the business case no longer stacks up.
Organisation in action: The project manager sets up the project board with three roles: the executive (the bank’s head of digital, who owns the budget), the senior user (the head of retail banking, who represents the end customers), and the senior supplier (the IT director from the software company, who provides the developers). She also drafts a project organisation chart showing each team member’s responsibilities. This prevents arguments about who approves changes to the user interface.
Quality in action: The quality theme requires clear acceptance criteria. The bank says the app must load in under 2 seconds and handle 10,000 concurrent users. The project manager ensures these are written into a quality register. The test team runs load tests and records results. When a developer submits code that makes the app load in 3 seconds, the quality register flags it as a failure, and the code is sent back for improvement.
Plans in action: The project manager creates a project plan showing the entire timeline: 18 months of work divided into six stages. She then creates a detailed stage plan for the first stage (design). The stage plan lists every task, who does it, how long it takes, and the budget. She uses this plan to track progress week by week.
Risk in action: The risk log starts with 30 identified risks. One high-probability risk is that the bank’s core system might not integrate with the new app. The project manager assigns a risk owner (an integration specialist) who investigates the risk and decides to mitigate it by building a prototype early. Another risk is that the bank’s competitor might launch a similar app first (a threat), so the team works to accelerate the schedule.
Change in action: Halfway through, the bank asks for a new feature: fingerprint login instead of just a password. This is a change request. The project manager assesses its impact: it will add 4 weeks to the schedule and £50,000 in costs. She presents the impact to the project board. The board decides the benefit (better security) is worth the extra cost, so they approve the change. The change is logged in the change register, and the plan is updated.
Progress in action: Each week, the project manager compares the actual time spent against the plan. She uses tolerance: the stage budget has a 10% tolerance. This week, costs are 8% over, so she does not escalate — it is within tolerance. But if costs reached 12%, she would write an exception report to the board, asking them to decide whether to reduce scope or add more money. At the end of each stage, she produces an end-stage report summarising progress, and the board decides whether to authorise the next stage.
The PRINCE2 Foundation exam tests ‘Themes’ in two ways: recall of purpose (what each theme achieves) and understanding of structure (the key things each theme contains, such as registers or approaches). Expect about 8–12 questions on themes out of the 60 total exam questions.
Common question types: - ‘What is the purpose of the [theme name] theme?’ — you must select the correct definition from a list of near-matches. - ‘Which management product is associated with the [theme name] theme?’ — e.g., the risk register belongs to the risk theme. - ‘True or false: the business case theme is optional in a small project.’ — false, it is never optional, but it can be tailored. - ‘Which role is responsible for ensuring the business case remains viable?’ — the executive. - ‘Which theme describes how to deal with issues and changes?’ — the change theme.
Traps the exam sets: - Confusing the purpose of the plans theme (how the project will be delivered) with the progress theme (monitoring whether the project is on track). - Thinking that the business case is only created at the start — the exam tests that it must be reviewed and updated at least at the end of each stage. - Mistaking the organisation theme for just a list of people — in PRINCE2, organisation defines accountability, not just names. - Believing that the quality theme only happens at the end — it must be planned from the start. - Mixing up the change theme (handling requests for change) with the risk theme (handling uncertain future events).
Concepts the exam loves: - The seven themes and their exact names (business case, organisation, quality, plans, risk, change, progress). Do not add or subtract any. - The fact that themes are applied throughout the project, not just at one stage. - The relationship between themes: for example, a risk response may require a change to the plan (plans theme) and an update to the business case. - The management products associated with each theme: e.g., business case (business case document), organisation (role descriptions), quality (quality register), plans (project plan, stage plan), risk (risk register), change (issue register, change log), progress (highlight reports, end-stage reports). - The concept of tolerances under the progress theme: time, cost, scope, risk, quality, and benefits. - The difference between a baseline (the original plan) and a current forecast (the latest estimate).
What you should memorise: - The exact definition of each theme from the PRINCE2 glossary (UK wording: ‘The purpose of the [theme] theme is to...’). - Which role approves the business case, and which role updates it. - The three-part structure of the quality theme: quality criteria, quality methods, and quality records. - The seven risk response types: avoid, reduce, transfer, accept, share, escalate, and fallback. - The four levels of management in the organisation theme: corporate, project board, project manager, team.
When you encounter a question about a theme, first identify whether it is asking about purpose (the ‘why’) or content (the ‘what’). If the question mentions a register, ask yourself: ‘Which theme does this register belong to?’ This will guide you to the correct answer.
The seven PRINCE2 themes are business case, organisation, quality, plans, risk, change, and progress — each addresses a specific management concern that must be applied throughout the project.
The business case is the most important theme because it justifies whether the project should exist at all, and it must be reviewed at the end of each stage.
The organisation theme defines four levels of management: corporate or programme, project board, project manager, and team — with clear accountability assigned to each role.
The quality theme requires setting criteria at the start and using methods like inspection or testing to confirm products meet those criteria before acceptance.
Plans exist at three levels (project plan, stage plan, and team plan or exception plan) and are progressively elaborated as more detail becomes known.
The risk theme treats both threats (negative risks) and opportunities (positive risks), offering seven response types: avoid, reduce, transfer, accept, share, escalate, and fallback.
The change theme uses a change control approach and, for large changes, a change authority or change board to evaluate and decide on issues and change requests.
The progress theme tracks six types of tolerances (time, cost, scope, risk, quality, and benefits) and escalates to the project board if tolerances are exceeded.
These come up on the exam all the time. Here's how to tell them apart.
Business Case Theme
Focuses on why the project is being done (justification)
Primary output is the business case document
Answers the question: 'Is the project still worthwhile?'
Plans Theme
Focuses on how the project will be done (schedule and resources)
Primary output is the project plan and stage plans
Answers the question: 'What activities need to happen and when?'
Risk Theme
Deals with uncertain future events (threats and opportunities)
Key management product is the risk register
Responses include avoid, reduce, transfer, accept, share, escalate, fallback
Change Theme
Deals with specific requests or defects that have already occurred
Key management product is the issue register or change log
Responses include approve, reject, defer, or refer to change authority
Progress Theme
Monitors time, cost, scope, risk, quality, and benefits against tolerances
Uses reports (highlight, end-stage, exception) to communicate status
Primary concern is whether project is on track to deliver
Quality Theme
Defines and verifies product standards using criteria and methods
Uses a quality register to record inspections and tests
Primary concern is whether products meet agreed specifications
Organisation Theme
Defines roles and responsibilities for the project management team
Key roles: executive, senior user, senior supplier, project manager
Answers: 'Who is accountable for what?'
Change Theme
Defines how to manage modifications to baselined products
Uses a change authority or change board for decision-making
Answers: 'How do we handle requests for change?'
Mistake
The themes are only used at the beginning of a project to plan things.
Correct
Themes are continuous — they are used from pre-project through to project closure and are reviewed at every stage.
Beginners often think project management is just about creating a plan and then following it, so they assume the themes are applied once and forgotten.
Mistake
The business case is the same as a project charter or a scope statement.
Correct
The business case justifies the project in terms of costs, benefits, and risks; a project charter authorises the project, and a scope statement defines deliverables.
Many beginners come from other frameworks (e.g., PMBOK, Agile) where those terms are used differently, and they incorrectly map them to PRINCE2.
Mistake
The organisation theme is only relevant for large projects with many people.
Correct
The organisation theme applies to every project, no matter how small, because it defines who is accountable for decisions — even a two-person project needs clear roles.
People assume that small teams can ‘just talk’, missing PRINCE2’s principle that clear accountability prevents confusion.
Mistake
The risk theme covers only threats (negative risks), not opportunities.
Correct
PRINCE2’s risk theme explicitly includes opportunities (positive risks) and requires you to respond to both threats and opportunities.
The word ‘risk’ in everyday language usually means something bad, so beginners forget the positive side.
Mistake
The progress theme is just about keeping a schedule.
Correct
Progress monitoring includes time, cost, scope, risk, quality, and benefits — it is broader than just a schedule.
Most people associate ‘progress’ with deadlines, so they overlook the other five performance dimensions.
Mistake
The change theme is optional if the project is simple.
Correct
Every project must have a change control approach — even a simple project needs a way to decide whether to accept a change request; it is never optional.
Beginners think change control is bureaucratic overhead, not a necessary guardrail.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Yes. You must be able to list them in order and state the purpose of each one. The exam will not ask you to list them, but you need to recognise them by name and definition in multiple-choice questions.
PRINCE2 considers the business case the most important because it justifies the project. Without a viable business case, you should not start or continue the project. However, all seven themes are mandatory.
No. All seven themes must be addressed in every project, but you can tailor them. A small project might use a one-page business case and a simple role description, but you cannot ignore a theme entirely.
The plans theme is about creating the road map (what you will do and when). The progress theme is about checking whether you are following that road map (actual vs. plan). They are complementary but distinct.
The seven themes support the seven principles. For example, the continued business justification principle is supported by the business case theme, and the manage by stages principle is supported by the plans and progress themes.
A management product is a document or record that the theme produces, such as the business case (business case theme), risk register (risk theme), or quality register (quality theme). You will need to match management products to their themes in the exam.
You've finished PRINCE2 Themes Introduction. Continue through the PRINCE2F study guide to build a complete picture of the exam.
Done with this chapter?