Skip to main content

Overview

The arckit sobc command creates a Strategic Outline Business Case (SOBC) following HM Treasury Green Book 5-case model. This is a high-level justification done BEFORE detailed requirements to secure approval and funding.

Command Syntax

arckit sobc "<project ID or initiative>"

Arguments

initiative
string
required
Project ID or initiative name, e.g. 001, cloud migration programme, digital transformation

What It Creates

Generates a comprehensive Green Book 5-case business case:
  • File: projects/{NNN}-{project-name}/ARC-{PROJECT_ID}-SOBC-v1.0.md
  • Document ID: ARC-{PROJECT_ID}-SOBC-v1.0
  • Content: Strategic Outline Business Case with 5 cases (Strategic, Economic, Commercial, Financial, Management)

Prerequisites

MANDATORY: Must run arckit stakeholders first. Every SOBC benefit MUST trace to a stakeholder goal.
RECOMMENDED: Also run arckit principles to extract strategic alignment and technology standards, and arckit risk to populate the Management Case Part E.

Business Case Lifecycle

The SOBC is the first stage in the UK Government business case lifecycle:
  • SOBC: Strategic Outline (this command) - High-level case for change, done BEFORE detailed requirements
  • OBC: Outline Business Case - After some design work, with refined costs
  • FBC: Full Business Case - Detailed case with accurate costs, ready for final approval

Green Book 5-Case Model

A. Strategic Case

Purpose: Make the case for change and strategic fit
  • Problem Statement: What’s broken? (from stakeholder pain points)
  • Strategic Fit: How does this align with organizational strategy?
  • Stakeholder Drivers: Map to stakeholder analysis
    • Link EACH driver to strategic imperative
    • Show intensity (CRITICAL/HIGH/MEDIUM)
  • Scope: What’s in/out of scope (high-level)
  • Dependencies: What else must happen?
  • Why Now?: Urgency and opportunity cost

B. Economic Case

Purpose: Demonstrate value for money through options analysis

Options Analysis

For EACH option:
  • High-level costs (rough order of magnitude)
  • Benefits delivered (% of stakeholder goals met)
  • Risks
  • Pros/cons

Benefits Mapping

  • Link EACH benefit to specific stakeholder goal
  • Quantify where possible (use stakeholder outcomes for metrics)
  • Categorize: FINANCIAL | OPERATIONAL | STRATEGIC | COMPLIANCE | RISK

Cost Estimates

  • Capital costs (build)
  • Operational costs (run)
  • 3-year TCO estimate

Economic Appraisal

ROM costs with quantified key benefits and basic NPV — when some financial data is available
Detailed costs, quantified benefits, NPV, BCR, sensitivity analysis — typically for OBC/FBC stage, but may be required for large investments

C. Commercial Case

Purpose: Demonstrate commercial viability and procurement route

Procurement Strategy

  • UK Government: Digital Marketplace route (G-Cloud, DOS, Crown Hosting)
  • Private Sector: Build vs Buy vs Partner

Market Assessment

  • Supplier availability
  • SME opportunities (UK Gov requirement)
  • Competition considerations

Sourcing Route

How will we acquire this?

Contract Approach

Framework, bespoke, managed service?

D. Financial Case

Purpose: Demonstrate affordability and funding arrangements
  • Budget Requirement: How much needed?
  • Funding Source: Where does money come from?
  • Approval Thresholds: Who must approve?
    • UK Gov: HMT approval needed above £X?
    • Private: Board approval needed?
  • Affordability: Can organization afford this?
  • Cash Flow: When do we need money?
  • Budget Constraints: Any spending controls?

E. Management Case

Purpose: Demonstrate project deliverability

Governance

  • Who owns this? (from stakeholder RACI matrix)
  • Steering committee membership
  • Decision authorities

Project Approach

Agile? Waterfall? Phased?

Key Milestones

  • Approval gates
  • Major deliverables
  • Go-live target

Resource Requirements

  • Team size (estimate)
  • Skills needed
  • External support

Change Management

  • Stakeholder engagement plan (from stakeholder analysis)
  • Training needs
  • Resistance mitigation (from stakeholder conflict analysis)

Benefits Realization

  • How will we measure success? (use stakeholder outcomes)
  • Who monitors benefits?
  • When do we expect to see benefits?

Risk Management

  • Top 5-10 strategic risks
  • Mitigation strategies
  • Risk owners (from stakeholder RACI)

Real-World Examples

Example 1: Technology Modernization

  • Strategic Case: Legacy systems failing, stakeholder frustration high
  • Economic Case: 3-5 options from do-nothing to complete rebuild
  • Commercial Case: Cloud migration, Digital Marketplace G-Cloud
  • Financial Case: £2-5M over 3 years, CFO approval needed
  • Management Case: Phased migration, minimal disruption

Example 2: New Digital Service

  • Strategic Case: Citizen/customer demand, competitive pressure
  • Economic Case: MVP vs full-featured comparison
  • Commercial Case: Build in-house vs platform vendor
  • Financial Case: £500K-2M year 1, ongoing £200K/year
  • Management Case: Agile delivery, beta to live

Example 3: Compliance/Risk Driven

  • Strategic Case: Regulatory requirement, audit findings
  • Economic Case: Minimum compliance vs best practice
  • Commercial Case: Specialist vendors, certification needed
  • Financial Case: Non-negotiable spend, insurance cost reduction
  • Management Case: Deadline-driven, stakeholder compliance team owns

UK Government Specifics

Key HM Treasury references: The Green Book provides the 5-case model, the Magenta Book provides evaluation design guidance, and the Sourcing Playbook covers should-cost modelling and market assessment.
For UK Government/public sector projects, ensure:

1. Strategic Case includes

  • Policy alignment (manifesto commitments, departmental objectives)
  • Public value (not just efficiency, but citizen outcomes)
  • Minister/Permanent Secretary drivers
  • Parliamentary accountability

2. Economic Case includes

  • Social Cost Benefit Analysis (if required)
  • Green Book discount rates (3.5% standard)
  • Optimism bias adjustment (add contingency)
  • Wider economic benefits

3. Commercial Case includes

  • Digital Marketplace assessment (G-Cloud, DOS)
  • SME participation commitment
  • Social value (minimum 10% weighting)
  • Open source consideration

4. Financial Case includes

  • HM Treasury approval thresholds
  • Spending Review settlement alignment
  • Value for money assessment
  • Whole-life costs

5. Management Case includes

  • Service Standard assessment plan
  • GDS/CDDO engagement
  • Cyber security (NCSC consultation)
  • Accessibility (WCAG 2.2 AA compliance)
  • Data protection (ICO/DPIA requirements)

Traceability Example

Every element must link back to stakeholder analysis:
Stakeholder Driver D-1 (CFO: Reduce costs - FINANCIAL, HIGH)
  → Strategic Case: Cost pressure driving change
    → Economic Case: Benefit B-1: £2M annual savings (maps to CFO Goal G-1)
      → Financial Case: 18-month payback acceptable to CFO
        → Management Case: CFO sits on steering committee (RACI: Accountable)
          → Success Criterion: CFO Outcome O-1 measured monthly

Command Handoffs

Define Detailed Requirements

arckit requirements
After SOBC approval, define detailed requirements that align to the recommended option.

Create Strategic Roadmap

arckit roadmap
Create strategic roadmap from SOBC investment plan and timeline.

Interactive Configuration

The command prompts for two strategic choices:

Question 1: Options Count

“How many strategic options should be evaluated in the Economic Case?”
  • 4 options (Recommended): Do Nothing + Minimal + Balanced + Comprehensive
  • 3 options: Do Nothing + two alternatives
  • 5 options: Do Nothing + four alternatives

Question 2: Appraisal Depth

“What level of economic appraisal should be applied?”
  • Strategic estimates (Recommended): ROM costs and qualitative benefits
  • Semi-quantitative: ROM costs with quantified key benefits and basic NPV
  • Full quantitative: Detailed costs, NPV, BCR, sensitivity analysis

Important Notes

If stakeholder analysis doesn’t exist, the command will STOP and warn: “SOBC requires stakeholder analysis to link benefits to stakeholder goals. Please run arckit stakeholders first.”

Key Concepts

  • SOBC is strategic, not detailed: High-level estimates and qualitative benefits appropriate
  • Every benefit traces to a stakeholder goal: Ensures business case is grounded in real needs
  • Options appraisal is critical: Must evaluate multiple options, not just one preferred solution
  • Recommended option must be justified: Reference stakeholder goals met, not just cost
  • This enables OBC/FBC: After requirements and design, create refined business cases

Build docs developers (and LLMs) love