September 7, 2026 · 8 min read
TL;DR: The business case appears in 19 answer options across the bank and is keyed 6 times. It wins when the question is justification: should this be a project, and where is the reasoning written. It loses 13 times, and nearly every loss is to a neighbouring artefact doing a job the business case cannot do: the charter for authorisation, the benefits management plan for measurement, and the product backlog for a request on an agile delivery.
Three documents sit next to each other at the front of a project, and the exam tests whether you can tell which one a stem is asking for. The business case is the one candidates reach for when the stem sounds strategic. The bank rewards that reflex about a third of the time.
When the question is whether the project is justified, or where its justification lives.
A vice president returns from a conference impressed by blockchain and instructs a project manager to implement it. Keyed first step: begin work on the business case. The explanation says an executive's enthusiasm for a technology is not yet a project, and the business case is what establishes whether the idea is justified and what problem it would solve. A SWOT analysis sits inside it rather than ahead of it. Identifying requirements and allocating resources presume an initiative that has not been justified.
Rivals are rapidly taking market share, an executive says jobs are at risk within twelve months, and no projects are under way. Keyed is writing a business case covering the business need, situation analysis and solution options. Writing a charter with scope, milestones and cost is offered and loses, because a charter cannot be written before a case establishes how the project addresses the business goals.
A functional manager must lift profit by 57 per cent in three years and has eighteen ideas that would take seven years. Keyed is prioritising the ideas by impact and cost, marking each required, desired or optional in the business case. The business case is where the analysis of options belongs, and it gives the manager something to decide with.
An incoming project manager on a hybrid rollout needs to understand the project's strategic benefits and objectives. Keyed is the business case, because it holds the need the project answers, the options considered, the benefits expected and the costs and risks the organisation accepted. The roadmap is the closest miss and says what and when, never why.
The bank also keys reviewing business documents such as the business case and charter as the first source for identifying stakeholders, and revising the business case's margin assumptions through change control once the accounting group has confirmed an omission that affects them.
When the stem asks for authorisation, measurement, or an agile request, each of which belongs to a neighbouring artefact.
The question is authorisation. A sponsor asks for a document that formally authorises the project and pulls in the cost-benefit analysis, feasibility study and high-level risks. Creating the business case is offered and loses to creating the charter. The explanation names the tell: the word authorises. The business case is where the cost-benefit analysis genuinely sits, but it is an input to the charter, and it authorises nothing. A sponsor verbally says to start pulling people onto a project before any paperwork exists. Drafting a business case to justify the investment is offered and loses to waiting for the charter to be signed, because the business case precedes and justifies the charter rather than substituting for it. Senior leadership asks for the first steps toward launching a kiosk project. Building the cost-benefit analysis for the business case is offered and loses to gathering the inputs for the charter, because the first thing a project needs is authorisation.
The question is measurement. A sponsor worries she will not be able to tell whether the delivered product has the intended effect once released. Consulting the business case is offered and loses to the benefits management plan. The explanation is precise: the business case says what should happen and why it was worth funding, but not how anyone will know whether it did.
The request is agile. Department heads send an agile project manager several feature requests during an ERP rollout. Requiring a detailed business case for each feature is offered and loses to having the product owner add the requests to the backlog, because a business case per request imposes predictive change control on a framework that already has a mechanism for handling change.
The problem is elsewhere. A team treats a regulator's AI rule as paperwork and chooses the cheapest evidence that will pass. Adding a section on reputational benefits to the business case loses to naming what the rule protects and setting that as the outcome, because the business case is a document the engineers choosing the tests never open. Steering-group successors describe the programme in the words of the original business case, three approved changes later. Circulating that document with the changes marked up loses to briefing each new member on what the programme now commits to.
Common trap: confusing what justifies a project with what starts one. The bank offers the business case three times as an answer to a question about authorisation and keys it in none of them. A business case with no charter has a justification but no mandate, and the explanation for the sponsor's request states it in those words. Read the stem for the verb. Justify, assess, decide whether: business case. Authorise, name the project manager, commit resources: charter. Measure after release: benefits management plan. The bank explains every one of the 13 distractors this way rather than leaving the option marked wrong.
The business case justifies, the charter authorises, and the benefits management plan measures. Read the verb in the stem and the artefact follows.
| The stem asks | The keyed document | Why the neighbours lose |
|---|---|---|
| Is this worth doing, and what problem does it solve? | Business case | The charter presumes the answer; the benefits plan measures it later |
| Which of many ideas should we pursue, and in what order? | Business case | A charter per idea is premature; experts see only their own area |
| Which document formally authorises the project? | Project charter | The business case authorises nothing |
| Can I start assigning people on a verbal go-ahead? | Wait for the charter | A business case supplies justification, not the missing authority |
| How will we know the benefits arrived after handover? | Benefits management plan | The business case states the logic, not the measurement |
| Where do I read why this project exists, on day one? | Business case | The roadmap answers what and when |
| Which document is a documented economic feasibility study? | Business case | It is not a statement of work, a set of plans or a scope breakdown |
One more item keeps the boundary honest at closure. A transport authority's business case rests on a rise in off-peak passengers measured a year after the last display is fitted, and the team disbands next month. The keyed answer puts the benefit into the transport committee's standing quarterly review with the date it falls due. The business case named the benefit. Something that meets after the project has gone has to own the measurement.
When is the business case the keyed answer on the PMP exam? When the question is whether something should be a project at all, or where the reasons for it are recorded: an executive's enthusiasm for a technology, rivals taking market share with no projects under way, an incoming project manager who needs to understand the strategic benefits, or eighteen ideas that cannot all be done in three years.
What is the difference between the business case and the project charter? The business case argues that the project is worth doing and authorises nothing. The charter formally authorises the project and grants the project manager authority to apply resources. A project with an approved business case and no charter has a justification but no mandate.
What is the difference between the business case and the benefits management plan? The business case states the expected benefits and the investment logic that justified the project. The benefits management plan states how each benefit will be measured, when it should appear, who owns realising it and how it will be tracked after the project closes.
Does an agile feature request need a business case? No. On an adaptive delivery the request goes into the product backlog for the product owner to prioritise. Demanding a business case per feature imposes predictive change control on a framework that already handles change.
PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample — no card, no signup required to try it.
Related reading: The Project Charter: Keyed 15 Times, Wrong 40 Times, and the Split Is Clean and Value-Based Delivery: Why On Time and On Budget Is Not the Answer. Value tasks are mapped on the Process domain study page.
When is the business case the keyed answer on the PMP exam?
When the question is whether something should be a project at all, or where the reasons for it are recorded: an executive's enthusiasm for a technology, rivals taking market share with no projects under way, an incoming project manager who needs to understand the strategic benefits, or eighteen ideas that cannot all be done in three years.
What is the difference between the business case and the project charter?
The business case argues that the project is worth doing and authorises nothing. The charter formally authorises the project and grants the project manager authority to apply resources. A project with an approved business case and no charter has a justification but no mandate.
What is the difference between the business case and the benefits management plan?
The business case states the expected benefits and the investment logic that justified the project. The benefits management plan states how each benefit will be measured, when it should appear, who owns realising it and how it will be tracked after the project closes.