Business Case Theme — this is the heartbeat of every PRINCE2 project. It answers the single most important question: “Why are we doing this project at all?” For someone studying PRINCE2F, understanding this theme is critical because it is the thread that runs through the entire course and nearly every exam question tests your ability to link decisions back to business justification.
Jump to a section
£25,000 — that is the budget you set aside to renovate your kitchen. Before you start knocking down walls or buying fancy appliances, you sit down with your family and write a business case for the renovation. You list the benefits: increased home value, better energy efficiency, more space for entertaining. You estimate the costs: £15,000 for new cabinets and countertops, £5,000 for labour, £3,000 for appliances, and £2,000 for unexpected issues like plumbing surprises. You calculate the value — a renovated kitchen will add £30,000 to your home’s resale value, a net gain of £5,000.
But here is the crucial part: your business case is not a one-time document. Six months later, when your partner loses their job, you revisit the plan. The kitchen renovation no longer makes sense financially. You need that £25,000 for living expenses. The business case has changed, so you pause the project.
This is exactly how the Business Case Theme works in PRINCE2. It is the document that asks, “Why are we doing this?” at the very start and keeps asking it at every stage. Just like your home renovation plan, it captures the costs, benefits, risks, and expected value. And just as you would stop renovating if your financial situation changed, PRINCE2 demands that the project stops if the business case no longer justifies the effort. Without it, you are just spending money and resources on something that might not be worthwhile.
The Business Case Theme is one of the seven themes in PRINCE2. A theme is a required area of knowledge that must be applied throughout a project. The Business Case Theme specifically focuses on the business justification for starting and continuing a project. Every project must have a reason to exist — if there is no business case, there should be no project.
The central concept is ‘continued business justification’. This means you do not just write a business case once and ignore it. PRINCE2 requires that you review the business case at key moments: at the end of each stage (a stage is a section of the project with its own plan and control points), when major changes happen, and before any major investment decisions. If the business case becomes weak, the project should be stopped or changed.
Let us define the key terms you need to know:
Business Case: The document that justifies the project. It contains the reasons, options considered, benefits (the measurable improvements the project will deliver), costs (money, time, resources), risks (uncertainties that could affect the project), and the expected return on investment.
Benefits: The measurable improvements that the project is supposed to deliver. For example, a new website might have a benefit of ‘reducing customer support calls by 20%’. Benefits can be financial (cost savings, increased revenue) or non-financial (improved customer satisfaction, better staff morale).
Dis-benefits: The negative outcomes that the project creates but are not necessarily risks. For example, a new software system might be faster but require staff training, which costs time. Dis-benefits are costs or drawbacks that are expected, not uncertain.
Costs: The total investment required. This includes development costs (building the product), operational costs (running it after launch), and any ongoing maintenance costs.
Return on Investment (ROI): A simple calculation of (benefits minus costs) divided by costs, usually shown as a percentage. PRINCE2 itself does not mandate a specific calculation method — it simply requires that the business case shows the project is worthwhile.
Risk: In the business case, risks are uncertainties that could affect the project’s viability. For example, a risk might be “key supplier may go bankrupt, delaying the project and increasing costs”. The business case should include a risk assessment.
How does the Business Case Theme fit into the PRINCE2 roles and processes?
The Senior User (the person who represents the people who will use the project’s product) is responsible for defining the benefits. The Senior Supplier (the person who provides the resources and expertise) is responsible for estimating costs and understanding the feasibility. The Executive (the overall project sponsor) owns the business case and makes the final decision about whether the project is worth doing.
The project starts with an Initiation Stage (the first stage where you plan the project in detail). During initiation, you create the Initiation Business Case – a detailed version of the business case that will guide the rest of the project. Later, as the project progresses, you update it – this is called the Updated Business Case. At the end of the project, you produce a Benefits Review Plan (a plan for checking if the predicted benefits were actually achieved) and a Benefits Review Report (the actual results of checking those benefits).
Why does PRINCE2 put so much emphasis on the business case? Because projects can easily drift. Without a clear business case, a team might build something that nobody wants, overspend, or miss the real need. The business case keeps everyone focused on the value the project is supposed to deliver. It also ensures that if things change – like a competitor launches a better product, or new regulations appear – the project can adapt or stop.
In summary, the Business Case Theme is not just a document – it is a mindset. It says: “We will only invest time and money if the project makes business sense, and we will keep asking if it still makes sense at every step.”
Initiate the Business Case
During the Pre-Project stage, the Executive creates a high-level outline Business Case. It includes the expected benefits, costs, risks, and a rough timeline. This is the first decision point: is this project worth investigating further? If the answer is no, the project stops here.
Develop Detailed Business Case in Initiation Stage
In the Initiation Stage, the project manager works with the Senior User and Senior Supplier to create a detailed Initiation Business Case. This includes precise cost estimates, a benefits realisation plan, a risk assessment, and a clear statement of the value the project will deliver. The Project Board (Executive, Senior User, Senior Supplier) reviews and approves this version.
Review Business Case at Stage Boundaries
At the end of each management stage, the project manager presents an Updated Business Case to the Project Board. The board decides: does the business case still justify continuing? If costs have risen or benefits have shrunk, the project may be stopped or altered. This is the ‘continued business justification’ mechanism.
Update Business Case for Changes
Whenever a significant change request or issue arises (e.g., new regulation, competitor launch, technology problem), the project manager updates the business case to reflect the impact. The change cannot be approved unless the updated business case shows the project is still worthwhile. This step ensures the project stays aligned with business goals.
Plan and Perform Benefits Review After Project
Before the project ends, the Benefits Review Plan is created (often during initiation) to specify when and how benefits will be measured after delivery. After the project, the Benefits Review Report is produced, comparing actual benefits against the predictions in the business case. This step closes the loop and helps the organisation learn.
An IT professional working in a real company does not just write a business case as an academic exercise. It is a living document that shapes every major decision. Let me walk you through a concrete scenario: a company called ‘TechRetail’ decides to build a new mobile shopping app.
Step 1: The idea is born. A product manager notices that 70% of their website traffic comes from mobile phones, but their current mobile site is slow and unappealing. She writes a rough business case outline: the project will cost £200,000 over six months, and it will increase mobile sales by 30% in the first year. The Executive reviews this and says, “Show me more detail before I commit £200,000.”
Step 2: Initiation. The project manager assembles a small team to create a detailed business case. They do market research, talk to potential users, and get quotes from app developers. They discover that a simpler app with core features will cost £150,000 and take four months, with a projected benefit of 25% sales increase. The business case now includes a cost-benefit analysis, a risk register (e.g., risk: app store approval delays), and a benefits realisation plan. The Executive approves moving to the next stage.
Step 3: During development, the company’s main competitor launches a similar app with a flashy feature: in-app personalised recommendations. The project manager updates the business case to consider adding this feature. It costs £50,000 extra but could increase the sales benefit to 40%. The Executive reviews the updated business case and agrees to the change. The business case is now £200,000 with a projected benefit of 40% sales increase – still justified.
Step 4: At the end of the first development stage, the team realises that the chosen technology platform is causing performance issues. They need to switch to a different framework, costing an additional £30,000. The project manager updates the business case again, showing the new total cost of £230,000. The Executive must decide: is a 40% sales increase still worth £230,000? After recalculating, the ROI is still positive, so the project continues.
Step 5: After the app launches, the project manager monitors the actual benefits. Six months later, mobile sales are up by 22% — short of the 25% target but still positive. The business case is updated with the actual data. The benefits review shows that the app is delivering value, but the team learns that the recommendation feature (added later) actually increased sales more than expected. Next year, they can invest in improving that feature.
What does the IT professional do differently because of the Business Case Theme? - They continuously track costs against the business case budget. - They escalate any significant change (like a late feature request) to the Executive with an updated business case. - They ensure that every project decision is framed by the question: “Does this decision still make the business case valid?” - They create a Benefits Review Plan at the start, and a Benefits Review Report at the end, to close the loop on promised benefits.
Without this theme, projects can become “zombie projects” — projects that keep consuming money because nobody is brave enough to stop them. The Business Case Theme gives the project manager and Executive the tools to kill a project that no longer makes sense, and that is a real-world superpower.
The PRINCE2F exam loves to test the Business Case Theme because it is central to the whole methodology. Expect around 6 to 10 questions on this theme out of the 60 questions in the Foundation exam. Here is exactly what they test and how they try to trick you.
Key concepts they test repeatedly: - Continued business justification — this is the biggest concept. They will ask: “When should a business case be reviewed?” The correct answer is always: at key decision points (end of stages, major changes, before major investments). They will offer traps like “once at the start” or “only when the project is in trouble”. Both are wrong. - Who owns the business case? — It is always the Executive. Not the project manager, not the senior user, not the senior supplier. The Executive is the final decision-maker. The Senior User defines benefits, the Senior Supplier estimates costs, but the Executive owns the document. - What are the management products? — You need to know the names: Business Case (the main document), Initiation Business Case (the detailed version created during initiation), Updated Business Case (any version after a change), Benefits Review Plan (created during initiation, used at the end of the project or after), and Benefits Review Report (the actual results of reviewing benefits). Traps: they may ask “When is the Benefits Review Plan created?” — answer: during the Initiation Stage. They may ask “Who creates the Benefits Review Plan?” — answer: the Project Manager, with input from the Senior User. - What is a benefit vs a dis-benefit? — A benefit is a positive outcome you want. A dis-benefit is a negative outcome you expect. For example, a new system reducing errors is a benefit. The cost of training staff to use it is a dis-benefit. Not a risk — it is a known cost. Traps: they may list a risk as a dis-benefit. Remember: a risk is uncertain, a dis-benefit is a guaranteed negative effect. - What is the difference between a project and a programme? — PRINCE2 is about projects, but the exam may ask about the distinction. A project has a business case. A programme is a collection of projects with a programme business case. Traps: they may ask “Who approves the project business case?” — answer: the Project Board (which includes the Executive, Senior User, Senior Supplier). But the Executive has the casting vote.
Common traps in exam questions:
Trap 1: “The business case is only written at the start.” — The correct understanding is that it is reviewed and updated throughout the project.
Trap 2: “The project manager owns the business case.” — The Executive owns it. The project manager maintains it.
Trap 3: “A risk is the same as a dis-benefit.” — A risk might happen or not. A dis-benefit will happen (e.g., you will have to pay for training).
Trap 4: “Benefits review is done at the end of the project only.” — Actually, benefits are reviewed during the project and after. The Benefits Review Plan defines when.
Trap 5: “The business case includes only financial benefits.” — It includes both financial and non-financial benefits, as well as dis-benefits and risks.
Key definitions to memorise for the exam:
Business Case: The document that justifies the project.
Benefits: Measurable improvements expected from the project.
Dis-benefits: Negative outcomes expected (not risks).
Costs: Total investment (development + operational).
Executive: The person who owns the business case.
Benefits Review Plan: The plan for measuring benefits after delivery.
Benefits Review Report: The document recording actual benefits achieved.
Question style: They often give you a scenario (e.g., “A project manager notices a new regulation that will increase costs. What should they do?”) and you must pick the PRINCE2-aligned action: update the business case and escalate to the Executive. Or they give a list of activities and ask which is the purpose of the Business Case Theme (answer: to establish mechanisms to judge whether the project is desirable, viable, and achievable).
Study tip: Make flashcards for the three management products (Business Case, Benefits Review Plan, Benefits Review Report) and when each is created and used. Practice linking the roles to their responsibilities: Executive owns the case, Senior User defines benefits, Senior Supplier estimates costs. The exam loves role-to-responsibility matching.
The Business Case Theme answers the question 'why are we doing this project?' and requires continuous justification throughout the project's life.
The Executive owns the business case and makes the final decision to start, continue, or stop the project based on it.
Benefits are measurable improvements from the project; they can be financial (e.g., cost savings) or non-financial (e.g., customer satisfaction).
Dis-benefits are expected negative outcomes, not risks — they are certain consequences of the project, like training costs or downtime.
The Business Case is reviewed at the end of each management stage and whenever a significant change occurs, ensuring the project remains viable.
The three key management products are: Business Case, Benefits Review Plan (created during initiation), and Benefits Review Report (created after benefits are measured).
The Senior User defines the expected benefits; the Senior Supplier estimates the costs and feasibility; the Project Manager maintains the business case.
A project without a valid business case should be stopped — this is a fundamental PRINCE2 principle called 'continued business justification'.
These come up on the exam all the time. Here's how to tell them apart.
Business Case
Answers 'why are we doing this project?'
Focuses on justification (benefits, costs, risks)
Owned by the Executive
Project Plan
Answers 'how, when, and with what resources?'
Focuses on schedule, tasks, and resources
Created and maintained by the Project Manager
Benefit
A positive measurable outcome from the project
Examples: increased sales, faster processing
Desirable and part of the justification
Dis-benefit
A guaranteed negative outcome from the project
Examples: training costs, system downtime during migration
Undesirable but expected, not a risk
Executive
Owns the Business Case
Makes final decision to start/stop/change project
Senior sponsor role
Project Manager
Maintains the Business Case (writes and updates it)
Manages day-to-day activities and escalates issues
Day-to-day manager role
Initiation Business Case
Created during the Initiation Stage
Contains detailed estimates and a Benefits Review Plan
Approved once at the start of the project
Updated Business Case
Created whenever the business case is revised
Reflects changes in costs, benefits, risks, or timeline
Approved by the Project Board at each stage boundary
Mistake
The Business Case is a one-time document written at the start of the project and never changed.
Correct
The Business Case is updated throughout the project. PRINCE2 requires continued business justification, meaning the case is reviewed at the end of each stage and whenever a significant change occurs.
People often think of business cases like a budget or a contract — something you write once and then follow. But projects are dynamic, so the case must adapt to new information, risks, and opportunities.
Mistake
The project manager is responsible for approving the business case.
Correct
The Executive owns and approves the business case. The project manager writes it and maintains it, but only the Executive (the senior sponsor) can give the final go-ahead or stop the project.
This confusion arises because in many organisations the project manager does handle budgets and proposals. PRINCE2 is explicit that the Executive, not the project manager, has the authority to decide if the project is worthwhile.
Mistake
All benefits in a business case must be financial (like cost savings or revenue).
Correct
Benefits can be financial or non-financial. Examples include improved customer satisfaction, faster delivery times, or better staff morale. PRINCE2 accepts any measurable benefit as long as it justifies the project.
Many people come from a finance background where everything is measured in money. PRINCE2 is broader — it recognises that not all value is monetary, and that a business case can include qualitative benefits.
Mistake
A dis-benefit is the same as a risk.
Correct
A dis-benefit is a guaranteed negative outcome of the project, whereas a risk is an uncertain event that might happen. For example, training costs for staff are a dis-benefit; the risk that staff might leave after training is a risk.
The terms sound similar, and both are negative. The exam deliberately tests this distinction because beginners often mix them up. The key is certainty: dis-benefits are certain, risks are not.
Mistake
The Business Case Theme is only relevant for large, expensive projects.
Correct
Every project, no matter how small, should have a business case. The formality might differ, but the principle applies to all projects. A small project’s business case might be a single page, but it still answers ‘why’ and ‘what value’.
People assume PRINCE2 is only for huge corporate projects. The framework is scalable, and the business case is a core principle that applies to any project, from planning a team outing to launching a new product.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
The project manager typically writes and maintains the business case, but the Executive owns it and is responsible for approving it. The Senior User helps define the benefits, and the Senior Supplier helps estimate costs.
The Benefits Review Plan is created during the Initiation Stage, as part of the project plan. It defines when and how the project’s benefits will be measured after the project is delivered.
A benefit is a positive outcome the project aims to deliver (e.g., faster customer service). A dis-benefit is a guaranteed negative outcome that comes with the project (e.g., staff training costs or system downtime). Both are certain, but benefits are good, dis-benefits are bad.
No. PRINCE2’s principle of continued business justification means that if the business case becomes invalid (e.g., costs exceed benefits), the project should be stopped or changed. The Project Board makes this decision.
It is the detailed version of the Business Case created during the Initiation Stage. It contains precise estimates of costs, benefits, risks, and a plan for measuring benefits. It replaces the outline business case from the Pre-Project stage.
It is reviewed at least at every management stage boundary (end of each stage). It is also reviewed whenever a significant change occurs, such as a new risk, a change request, or a major issue. The Executive may call a review at any time if conditions change.
You've finished Business Case Theme. Continue through the PRINCE2F study guide to build a complete picture of the exam.
Done with this chapter?