4.1 Purpose, Content, and Roles in Developing the Business Case

4.1 Purpose, Content, and Roles in Developing the Business Case

Quick Answer: A Business Case provides the justification for undertaking and continuing a project, demonstrating that the investment is desirable (strategically aligned), viable (financially and commercially sound), and achievable (deliverable with available capability). The Project Sponsor owns the business case and is accountable for benefits realization, while the Project Manager assists by supplying technical estimates, schedules, and risk assessments. It is a live governance document, drafted in Concept, baselined in Definition, and re-evaluated at every phase gate.

---

What is a Business Case?

Organizations do not commit capital, human talent, and corporate time to projects on a whim. Every project represents an investment decision that must compete with alternative corporate initiatives for scarce organizational resources. To ensure that investments are made prudently and deliver demonstrable value, organizations rely on a structured governance document known as the Business Case.

According to the APM Body of Knowledge (7th Edition):

"The Business Case provides justification for undertaking a project, programme, or portfolio. It evaluates the benefit, cost and risk of alternative options and provides a rationale for the preferred solution."

The Business Case is not merely an administrative prerequisite to secure initial funding; it is the central reference point against which the project’s ongoing viability is scrutinized throughout its entire life cycle. If changing market conditions, escalating costs, or emerging technical barriers eliminate this business justification, the project must be reshaped or brought to a controlled termination.

---

The Core Purpose: Continued Business Justification

The fundamental purpose of a Business Case is to confirm and maintain continued business justification. In the APM framework, this justification is evaluated across three core tests:

1. Desirable: Does the project align with corporate strategy, mission, and long-term organizational goals? Do the key stakeholders want the business change, and will the anticipated operational outcomes deliver beneficial value?
2. Viable: Do the projected financial and non-financial benefits outweigh the total expected capital, operational, and transitional costs, taking into account the project's risk profile? Is the return on investment (ROI) acceptable?
3. Achievable: Does the organization possess—or can it acquire—the necessary capabilities, technical resources, supply chain partners, and management bandwidth to successfully deliver the outputs and embed the operational changes?

The "Golden Thread" of Strategic Alignment

The Business Case functions as the "golden thread" uniting high-level corporate strategy with front-line tactical execution. It articulates why an abstract strategic objective (such as "expanding digital customer reach by 30%") requires this specific project output (such as "developing an integrated mobile commerce application"). Without a clear Business Case, projects drift into aimless technical delivery, disconnected from corporate priorities.

---

Typical Structure and Key Content of the Business Case

While the exact format of a Business Case varies depending on organizational standards, a comprehensive, APM-compliant Business Case typically comprises seven core sections. The table below details each section, its specific purpose, and the critical questions it must answer:

The Critical Role of the 'Do Nothing' (Status Quo) Option

A common mistake in project proposal writing is evaluating only preferred intervention options. In professional project governance, an options appraisal is incomplete without a rigorous evaluation of the 'do nothing' (status quo) option.

The 'do nothing' option represents the counterfactual scenario: what happens to the organization if zero capital is invested and current operations continue unaltered? Evaluating this baseline is crucial because:

• Revealing the True Cost of Inaction: Operational costs often escalate over time due to deteriorating equipment, rising maintenance fees, manual inefficiencies, or regulatory penalties. Inaction is rarely cost-neutral.
• Objective Comparison: It provides the mathematical and operational baseline against which all incremental costs, risks, and benefits of the proposed intervention options can be compared.
• Preventing Unnecessary Spend: If the analysis shows that the operational impact of doing nothing is negligible, the organization can avoid wasting capital on unnecessary projects.

---

Evolution of the Business Case Across the Project Life Cycle

A Business Case is not a static document drafted once and filed away. It is a living management tool that matures progressively across the project life cycle:

Concept Phase           Definition Phase          Deployment Phase        Transition (incl. closure)
[Outline Business Case] -> [Full Business Case] -> [Gate Reviews / Control] -> [Benefits Realisation Review]

1. Concept Phase: The Outline Business Case

During the Concept phase, information is preliminary and uncertainty is high. The project team produces an Outline Business Case (sometimes referred to as a Project Brief or Concept Proposal). This document establishes high-level strategic alignment, presents early feasibility findings, outlines broad options, and provides rough-order-of-magnitude (ROM) cost and schedule estimates. It is presented at Gate 1 to seek executive authorization to invest resources into detailed planning.

2. Definition Phase: The Full Business Case

Once entry into Definition is approved, the chosen option is subjected to rigorous planning. Requirements are engineered, competitive supplier tenders may be received, risk profiles are quantified, and detailed schedules and cost baselines are assembled in the Project Management Plan (PMP). The Outline Business Case is refined into the Full Business Case. Presented at Gate 2, this document serves as the formal investment appraisal upon which the executive board authorizes the commitment of major capital expenditure.

3. Deployment Phase: Continuous Validation at Phase Gates

During Deployment, the Business Case serves as the baseline for ongoing justification. At every scheduled phase gate—and whenever a major change request or tolerance breach occurs—the governance board asks: "Does the Business Case remain valid?" If forecast cost overruns, schedule delays, or market shifts destroy the anticipated return, the Business Case dictates whether the project should be paused, restructured, or immediately terminated.

4. Transition (Handover, Acceptance and Formal Closure) and Post-Project Operations

At handover and formal closure — both of which sit inside the Transition phase in APM BoK7 — the Business Case is referenced to verify that delivered outputs meet agreed acceptance criteria. Following project closure, the Business Case becomes the foundation for formal Benefits Reviews, comparing the actual benefits realized in Business as Usual (BAU) against the forecasts approved in the baseline business case.

---

Roles and Accountabilities in Developing the Business Case

A strict separation of accountability governs the creation and maintenance of the Business Case between governance and delivery roles:

The Project Sponsor: Business Owner and Champion

• Ultimate Accountability: The Project Sponsor owns the Business Case. The Sponsor is personally accountable to the corporate executive or governance board for demonstrating continued business justification and ensuring that the projected business benefits are realized.
• Strategic Alignment & Funding: The Sponsor ensures the project directly supports corporate strategy, secures capital and operational funding, champions the initiative across executive committees, and defends its business rationale against competing corporate priorities.
• Decision at Gates: The Sponsor chairs gate reviews and holds the authority to approve, rework, or terminate the project based on business case health.

The Project Manager: Technical and Planning Contributor

• Assists and Advises: The Project Manager assists the Sponsor in drafting and refining the Business Case. The Project Manager does not own the business rationale, but provides the technical and operational planning expertise necessary to make the business case credible.
• Supplying Realistic Estimates: The Project Manager provides work breakdown structures (WBS), resource plans, realistic cost estimates, schedule models, supplier tender analyses, and risk register data.
• Impact Assessments: During deployment, when variances or change requests emerge, the Project Manager conducts rigorous impact assessments to inform the Sponsor how changes affect project cost, schedule, and business case validity.

Additional Contributing Specialists

Developing a robust Business Case requires collaboration with key enterprise specialists:

• Finance Analysts: Model discounted cash flows, Net Present Value (NPV), and internal rates of return (IRR).
• Commercial / Procurement Officers: Assess supplier market capacity, contract terms, and supply chain vulnerabilities.
• Business Change Managers (BCMs) / User Representatives: Validate operational feasibility, transition requirements, and benefits realization profiles.