The Project Business Case: What It Contains and When It Gets Approved

A business case is the document that justifies starting a project: it defines the problem or opportunity, compares possible solutions, estimates costs and benefits, and recommends whether the investment is worth making. On the CompTIA Project+ (PK0-005) life cycle, the business case is developed and approved during the discovery/concept preparation phase — the earliest phase, before the project is formally initiated. If the business case is not approved, the project never begins; if it is, its contents become the foundation for the project charter.

Where the business case sits in the life cycle

PK0-005 frames the project life cycle as discovery/concept preparation, then initiation, planning, execution, and closing. The discovery phase exists to answer one question: should we do this at all? The organization has limited money and people, and multiple ideas compete for them. The business case is the discovery phase’s central artifact — a structured argument that lets decision-makers compare the proposed project against alternatives and against doing nothing.

Two timing facts matter for the exam. First, the business case comes before the charter: the business case argues the project should exist; the charter, produced in initiation, formally authorizes it and names the project manager. Second, approval of the business case is what moves an idea out of discovery — a project that reaches planning without an approved business case is a governance failure, not a normal shortcut.

What a business case contains

A complete business case typically includes:

• Problem or opportunity statement — what business pain or opening justifies action, stated in business terms rather than technical ones
• Analysis of options — the viable alternatives, usually including the “do nothing” baseline, with the trade-offs of each
• Recommended solution — which option the sponsor proposes and why it beats the others
• Cost estimate — what the organization will spend, both to build and to operate
• Expected benefits — revenue gained, costs avoided, risks reduced, or compliance achieved; quantified wherever possible
• Financial justification — the math connecting cost to benefit, most commonly return on investment (ROI)
• High-level risks and assumptions — the major uncertainties the estimate depends on, which later seed the project’s risk register
• Alignment with organizational strategy — how the project advances stated business goals

The business case is a decision document, not a plan. Detailed schedules, task lists, and resource assignments belong to the planning phase; the business case works at the altitude where an executive can compare investments.

ROI: the financial heart of the case

Return on investment expresses benefit relative to cost as a percentage:

ROI = (net benefit ÷ cost) × 100, where net benefit is total expected benefit minus total cost.

A project costing $200,000 that is expected to return $260,000 in benefits has a net benefit of $60,000 and an ROI of 30%. Decision-makers use ROI to rank competing proposals: a portfolio board reviewing five business cases will fund the ones with the strongest returns relative to their risk. The project manager should also understand that ROI in a business case is a forecast built on assumptions — one reason the benefits are revisited at project close to see whether the promise held.

CapEx vs OpEx in the cost estimate

Business-case cost estimates distinguish two spending types, because they are budgeted, approved, and accounted for differently:

	Capital expenditure (CapEx)	Operational expenditure (OpEx)
What it buys	Long-lived assets — servers, buildings, purchased software licenses	Ongoing costs — subscriptions, salaries, utilities, cloud service fees
Payment pattern	Large up-front outlay	Recurring (monthly/annual)
Accounting treatment	Capitalized and depreciated over the asset’s life	Expensed in the period incurred
Approval reality	Often needs higher-level sign-off and longer lead time	Fits within operating budgets; easier to adjust
Classic project example	Buying data-center hardware	Paying for software as a service (SaaS)

This distinction is why cloud adoption appears so often in business cases: moving from owned hardware to cloud services converts CapEx into OpEx, trading a big up-front purchase for a recurring subscription. Neither model is universally better — the business case should present the total cost over a realistic time horizon so the options can be compared honestly.

Who builds and who approves it

The sponsor owns the business case — it is the sponsor’s argument for funding, often drafted with help from business analysts and subject-matter experts. Approval belongs to whoever controls the investment: an executive, a steering committee, or a portfolio governance board. The project manager is frequently not yet assigned when the business case is written, but inherits it as a key input: it tells you why the project exists, what benefits you are accountable for enabling, and which assumptions to validate early. Reviewing the business case is also a fast way to spot the people who care about the outcome — useful input to stakeholder identification once initiation begins.

How the PK0-005 exam tests this

• Phase-placement questions: the exam asks in which life cycle phase the business case is developed and approved, with the other phases as distractors. The credited answer is the discovery/concept preparation phase — resist the pull of “initiation,” which is where the charter lives.
• Artifact-matching scenarios: a description of a document that justifies investment, compares options, and estimates ROI must be identified as the business case rather than the charter, scope statement, or project plan.
• ROI calculation or interpretation: simple numbers (cost and expected benefit) with a request for the ROI percentage, or a choice among proposals where the highest justified return should be selected.
• CapEx vs OpEx classification: a purchase is described (hardware bought outright vs a cloud subscription) and you classify it — often wrapped in a business-case or budgeting context.

Life cycle questions like these anchor the Project Life Cycle Phases domain — the full PK0-005 study guide walks through every phase and domain weighting. Phase-placement traps are best beaten by repetition, so run PK0-005 practice questions until the sequence is automatic.

Quick reference

• Business case = the justification document; developed and approved in the discovery/concept preparation phase, before initiation.
• Sequence: business case (should we?) → charter (we formally authorize it) → planning (how exactly?).
• Core contents: problem statement, options analysis, recommended solution, costs, benefits, ROI, risks, strategic alignment.
• ROI = (net benefit ÷ cost) × 100; used to rank competing investment proposals.
• CapEx = up-front asset purchases, depreciated; OpEx = recurring operating costs, expensed — cloud shifts spend from CapEx to OpEx.
• The sponsor owns the business case; executives or a governance board approve it.
• No approved business case, no project — it is the gate out of discovery.