The Software Investment Business Case: Scope, Total Cost, Risk and Operating Economics

A software quotation may leave out costs the business will still carry. Build the case around scope uncertainty, alternatives, lifetime costs, operating work and downside. Keep forecasts separate from verified value and release further funding only when the next commitment is justified.

1. The Market Connection Context

The recognisable problem is not merely that software costs more than expected. It is that leadership cannot tell which market or service condition the investment will change, which costs belong to creating and sustaining that change, or what evidence would justify the next release of capital. Discovery, migration, integration, assurance, adoption, support, incident response, renewal, change and retirement disappear behind a build quotation. Benefits are stated as totals without an eligible population, baseline, attribution boundary or owner.

accepted need and investment route
→ bounded scope and credible alternatives
→ lifecycle cost and operating burden
→ value mechanism and uncertainty
→ downside, sensitivity and funding gates
→ fund, validate, change, defer or stop

By [decision date], the CFO and Product Sponsor will assign FUND NEXT PHASE, VALIDATE, CHANGE, DEFER or STOP to a named software investment case. The decision will identify the option and baseline alternative, the next bounded commitment, lifecycle cost boundary, value conditions, downside exposure, operating owner, evidence needed before later funding and the matters not concluded. It will not approve a supplier, final architecture, full delivery, production release or claimed return.

Use this after The Build, Buy, Configure, Integrate or Stop Decision: An Executive Technology Investment Playbook has established a credible build, buy, configure, integrate, retire or no-build route and The Solution Architecture and Non-Functional Requirements Standard: Designing for Supportable Value has supplied decision-level architecture and quality conditions where material. Return to The Build, Buy, Configure, Integrate or Stop Decision: An Executive Technology Investment Playbook when alternatives are not genuinely comparable. Return to The Solution Architecture and Non-Functional Requirements Standard: Designing for Supportable Value when a material cost rests on an unresolved architecture or non-functional condition. The Software Delivery Partner Appointment and Technical Due-Diligence Playbook owns partner appointment, The Product Delivery Governance Standard: From Discovery through Production Acceptance owns delivery authority, and The Product Adoption, Operability and Scale Gate: Proving Value after Launch owns post-launch adoption, operating economics and scale. A quotation is evidence from an interested source, not an independent total-cost conclusion.

Working files

• Investment Charter and Alternative Baseline Register
• Lifecycle Cost and Operating Burden Model
• Value Risk Sensitivity and Evidence Ledger
• Executive Phase Funding and Review Register

The HM Treasury Green Book 2026 is VERIFIED official guidance for appraisal and its Five Case Model, options, proportionality, risk and optimism-bias disciplines. The U.S. GAO Cost Estimating and Assessment Guide is VERIFIED official guidance on technical baselines, work breakdown, assumptions, data, sensitivity, uncertainty and updating estimates with actuals. The UK Technology Code of Practice is VERIFIED official guidance connecting technology choices to organisational strategy and full lifecycle management. The NIST Secure Software Development Framework is VERIFIED official guidance showing that preparation, protection, secure production and vulnerability response create lifecycle work, not optional extras after build. The UK Government Service Standard is VERIFIED official guidance linking user needs, accessibility, security, performance and reliable operation. These public-sector and standards sources inform disciplines; they do not prescribe a private organisation's accounting treatment, discount rate, tax position, prices or investment threshold. This guide's operating method is PROPOSED. Every local cost, value, probability, baseline and threshold is REQUIRES VALIDATION; any conclusion derived from them is INFERRED until accepted evidence exists.

2. The Leadership vs. Delegation Boundary

The reader recognises that a defensible business case must model scope uncertainty, alternatives, phased commitments, operating cost, downside and value thresholds.

An internal team can lead where it can challenge sponsor and supplier assumptions, reconcile finance and operating records, inspect the full lifecycle and preserve a credible stop route. Independent challenge is proportionate where a preferred solution is already politically committed, a supplier shaped the estimate, cross-functional costs sit in hidden budgets, or decision makers cannot separate sunk cost from future choice. Specialists can model uncertainty; they cannot manufacture precision or accept the organisation's downside.

The finance lead and sponsor share scope, assumptions, evidence thresholds, prioritisation, measures, dependencies and phase gates; the CFO retains funding and affordability authority. Use a narrower specialist for one bounded finance, tax, procurement, security, privacy, accessibility or operating question, and escalate any unaffordable or materially changed exposure to the CFO before commitment. Ask providers how they disclose lifecycle cost, dependency, exit, support and change assumptions and leave reproducible evidence. The Software Investment Business Case: Scope, Total Cost, Risk and Operating Economics is the anchor for economics and funding; provider changes still require The Software Delivery Partner Appointment and Technical Due-Diligence Playbook and delivery authority remains with The Product Delivery Governance Standard: From Discovery through Production Acceptance. Reuse evidence only with matching boundary and retain one shared decision ID for combined work.

3. The Step-by-Step Execution Standard

Step 01: Charter the investment decision

Purpose and decision served Define the precise funding decision, authority and evidence boundary.

Accountable owner CFO.

Delegated lead and contributors Finance lead, Product Sponsor, CIO, operations, procurement, risk and assurance owners.

Preconditions, inputs and access Accepted need, The Build, Buy, Configure, Integrate or Stop Decision: An Executive Technology Investment Playbook route, material The Solution Architecture and Non-Functional Requirements Standard: Designing for Supportable Value conditions, finance policy and source access.

Actions

1. State the decision date, decision owner, allowed dispositions and maximum authority.
2. Name the affected market or service condition, value path and excluded claims.
3. Record evidence access, conflicts, accounting questions, stop rights and escalation authorities.

Evidence to retain Signed charter, predecessor decisions, authority map, conflict record and source index.

Decision or scoring rule Proceed only when the case can recommend stop and the next commitment is separable from the total ambition.

Output and template Investment charter rows in T01.

Acceptance gate CHARTERED, CHANGE or STOP.

Leadership checkpoint CFO confirms that case development is not funding approval.

Human control point CFO and Product Sponsor accept the question, value boundary and authority.

Failure modes and safeguards Reject charters framed as justification for a predetermined product or supplier.

Change, stop or escalation condition Stop when no executive owns both the decision and consequences of non-achievement.

Handoff to the next step The charter controls the baseline and alternatives.

Step 02: Establish the counterfactual baseline

Purpose and decision served Make the current condition and credible future without the proposal comparable.

Accountable owner Product Sponsor.

Delegated lead and contributors Finance analyst, service owner, operations, customer research and data owners.

Preconditions, inputs and access Charter, current workflows, service records, existing commitments and accepted measurement definitions.

Actions

1. Separate current performance from a forecast of continuing unchanged.
2. Document current tools, workarounds, risks, committed changes and unavoidable costs.
3. Define eligible population, period, baseline range, limitations and owner.

Evidence to retain Source extracts, baseline contract, current-cost evidence and alternative explanations.

Decision or scoring rule No incremental value claim is accepted without a versioned counterfactual and eligible population.

Output and template Baseline and counterfactual rows in T01.

Acceptance gate ACCEPT, VALIDATE, CHANGE or REJECT.

Leadership checkpoint Product Sponsor accepts what is likely to happen without the investment.

Human control point Finance and operating owners accept source meaning and limitations.

Failure modes and safeguards Do not label all current cost avoidable or assume the existing service stands still.

Change, stop or escalation condition Validate when a disputed baseline could reverse the disposition.

Handoff to the next step The baseline anchors option comparison.

Step 03: Define credible alternatives

Purpose and decision served Prevent one preferred proposal from becoming its own comparator.

Accountable owner CIO.

Delegated lead and contributors Product, architecture, operations, finance, procurement and affected workflow owners.

Preconditions, inputs and access The Build, Buy, Configure, Integrate or Stop Decision: An Executive Technology Investment Playbook evidence, baseline, constraints and mandatory controls.

Actions

1. Include continue, improve without new software, retire and defer where credible.
2. Define each option at comparable outcome, boundary and maturity.
3. Record dependencies, reversibility, switching conditions and excluded capability.

Evidence to retain Option definitions, The Build, Buy, Configure, Integrate or Stop Decision: An Executive Technology Investment Playbook references, constraint evidence and dissent.

Decision or scoring rule An option remains eligible only if it can meet mandatory value and control conditions or has a funded validation gate.

Output and template Alternative rows in T01.

Acceptance gate COMPARABLE, VALIDATE, RETURN TO The Build, Buy, Configure, Integrate or Stop Decision: An Executive Technology Investment Playbook or STOP.

Leadership checkpoint CIO confirms that architecture preference has not removed credible alternatives.

Human control point CFO accepts the baseline alternative; Product Sponsor accepts outcome comparability.

Failure modes and safeguards Do not compare a detailed preferred option with deliberately vague alternatives.

Change, stop or escalation condition Return to The Build, Buy, Configure, Integrate or Stop Decision: An Executive Technology Investment Playbook when route diligence is incomplete or biased.

Handoff to the next step Comparable options enter scope decomposition.

Step 04: Decompose scope and uncertainty

Purpose and decision served Expose what must be learned, delivered, changed and operated.

Accountable owner Product Sponsor.

Delegated lead and contributors Product lead, architect, delivery, security, data, accessibility, operations and finance.

Preconditions, inputs and access Comparable options, architecture conditions, research and workflow evidence.

Actions

1. Separate discovery, product, integration, migration, assurance, adoption, operation and retirement scope.
2. Assign proof status, range driver, dependency and owner to each scope element.
3. Identify scope that is mandatory, optional, deferrable or prohibited before evidence.

Evidence to retain Scope breakdown, requirements references, assumptions, dependencies and uncertainty log.

Decision or scoring rule Unknown scope is not zero; it becomes a bounded validation activity or explicit exposure.

Output and template Scope and uncertainty rows across T01 and T02.

Acceptance gate BOUNDED, VALIDATE, CHANGE or STOP.

Leadership checkpoint Product Sponsor accepts minimum coherent scope and excluded outcomes.

Human control point Qualified control owners confirm mandatory assurance scope.

Failure modes and safeguards Reject feature-only scope and contingency used to conceal unnamed work.

Change, stop or escalation condition Return to The Solution Architecture and Non-Functional Requirements Standard: Designing for Supportable Value when architecture uncertainty materially controls cost or feasibility.

Handoff to the next step The scope breakdown becomes the cost structure.

Step 05: Build the lifecycle cost structure

Purpose and decision served Capture resources consumed from decision through retirement.

Accountable owner CFO.

Delegated lead and contributors Finance analyst, technology finance, product, delivery, procurement and operations.

Preconditions, inputs and access Scope breakdown, finance treatment, internal rates, supplier evidence and contracts.

Actions

1. Record internal and external labour, services, licences, infrastructure and assurance separately.
2. Include discovery, implementation, migration, integration, testing, security, privacy, accessibility, training and transition.
3. Include support, monitoring, incident response, vulnerability remediation, renewal, enhancement, data exit and retirement.

Evidence to retain Cost-source links, basis, unit, quantity, range, owner, period and accounting classification.

Decision or scoring rule No total is presented without its technical baseline, inclusion boundary, period and confidence state.

Output and template Lifecycle cost rows in T02.

Acceptance gate COMPLETE FOR DECISION, VALIDATE or REJECT.

Leadership checkpoint CFO accepts category completeness, not the accuracy of unsupported inputs.

Human control point Finance determines accounting treatment; source owners attest inputs.

Failure modes and safeguards A supplier quote cannot stand in for internal work, change, support or exit cost.

Change, stop or escalation condition Escalate when excluded material cost sits outside the sponsor's budget.

Handoff to the next step Lifecycle costs are reconciled with operating burden.

Step 06: Model operating burden and capability

Purpose and decision served Determine whether the organisation can sustain the option after delivery.

Accountable owner COO.

Delegated lead and contributors Service owner, support, security, data, platform, finance and workforce owners.

Preconditions, inputs and access Architecture scenarios, service model, capacity data and cost structure.

Actions

1. Define service hours, monitoring, support tiers, incident, continuity and change obligations.
2. Model scarce roles, recruitment, training, on-call, supplier dependency and management attention.
3. Record consumption drivers, capacity limits, manual fallback and burden transfer between teams.

Evidence to retain Operating model, role commitments, consumption basis, workload observations and owner acceptance.

Decision or scoring rule An option is not supportable when mandatory ownership or capacity is missing, regardless of build affordability.

Output and template Operating-burden rows in T02.

Acceptance gate OWNED, VALIDATE, CHANGE or STOP.

Leadership checkpoint COO accepts ongoing resource and service consequences.

Human control point Named operating owners accept responsibilities and limits.

Failure modes and safeguards Do not assume automation removes human exception, assurance or support work.

Change, stop or escalation condition Stop when a mandatory operating duty has no competent owner or funding path.

Handoff to the next step Cost and burden inform the value mechanism.

Step 07: Contract the value mechanism

Purpose and decision served Connect the intervention to an observable market, service or operating change.

Accountable owner Product Sponsor.

Delegated lead and contributors Finance, customer, operations, analytics and commercial owners.

Preconditions, inputs and access Baseline, eligible population, option scope, process evidence and metric contracts.

Actions

1. State the causal path from changed capability through behaviour to value.
2. Separate revenue, cost, capacity, retention, risk and service mechanisms without double counting.
3. Assign baseline, unit, period, attribution boundary, lag, threshold and accountable owner.

Evidence to retain Value contracts, source links, causal assumptions, overlap reconciliation and dissent.

Decision or scoring rule Activity, feature completion and usage alone are not value; each claim needs an eligible outcome definition.

Output and template Value rows in T03.

Acceptance gate DECISION-FIT, VALIDATE, CHANGE or REJECT.

Leadership checkpoint Product Sponsor accepts accountability for benefit conditions, not a guaranteed result.

Human control point CFO accepts financial translation; outcome owners accept operational definitions.

Failure modes and safeguards Reject totals that mix gross benefit, cash consequence, released capacity and avoided risk.

Change, stop or escalation condition Validate when value depends mainly on behaviour or market response not yet evidenced.

Handoff to the next step Value and cost assumptions enter risk analysis.

Step 08: Model uncertainty, sensitivity and downside

Purpose and decision served Show which assumptions control affordability and desirability.

Accountable owner CFO.

Delegated lead and contributors Finance analyst, risk, product, technology, operations and independent challenger.

Preconditions, inputs and access Versioned cost and value models, dependencies and evidence states.

Actions

1. Define plausible ranges without inventing probability distributions.
2. Vary material cost, adoption, timing, operating and value drivers separately and in coherent scenarios.
3. Record downside exposure, irreversible commitments, contingent liabilities and response options.

Evidence to retain Sensitivity runs, scenario definitions, risk ledger, source confidence and challenge notes.

Decision or scoring rule A case is decision-fit only when leadership can see which assumption changes the disposition.

Output and template Risk and sensitivity rows in T03.

Acceptance gate TOLERABLE, VALIDATE, REDESIGN, DEFER or STOP.

Leadership checkpoint CFO and risk owner accept downside boundary and response capacity.

Human control point Executives choose exposure; analysts do not average it away.

Failure modes and safeguards Do not present precision beyond evidence or use one optimistic case as the plan.

Change, stop or escalation condition Stop when downside breaches mandatory liquidity, service, legal or risk conditions.

Handoff to the next step Material uncertainty is converted into phased gates.

Step 09: Design phased commitments and evidence gates

Purpose and decision served Match capital at risk to evidence maturity and reversibility.

Accountable owner Product Sponsor.

Delegated lead and contributors Finance, product, technology, procurement, assurance and operations.

Preconditions, inputs and access Uncertainty map, cost structure, evidence needs and decision rights.

Actions

1. Define the smallest coherent next phase and what it must not authorise.
2. Assign deliverables, evidence, acceptance tests, maximum exposure and stop conditions.
3. Define later phase ranges as planning boundaries, not committed budgets.

Evidence to retain Phase boundaries, gate contracts, authority, dependency and exit records.

Decision or scoring rule Release only the phase needed to resolve or deliver the accepted next decision.

Output and template Phase and gate rows in T04.

Acceptance gate FUNDABLE NEXT PHASE, VALIDATE, CHANGE or STOP.

Leadership checkpoint CFO confirms later ambition is not an approved commitment.

Human control point Product, finance and control owners accept evidence required for the next release.

Failure modes and safeguards Avoid artificial phases that cannot produce usable evidence or a safe exit.

Change, stop or escalation condition Change when the proposed phase creates irreversible dependency before validation.

Handoff to the next step Phased options are tested for affordability and opportunity cost.

Step 10: Test affordability, opportunity cost and controls

Purpose and decision served Establish whether the next phase can be funded and governed in the real portfolio.

Accountable owner CFO.

Delegated lead and contributors Portfolio, treasury, finance, workforce, procurement, risk and technology owners.

Preconditions, inputs and access Phase model, current commitments, funding limits, scarce capacity and control requirements.

Actions

1. Reconcile cash, expense, capital, capacity and contingent exposure under applicable policy.
2. Identify displaced work, scarce capability and portfolio dependency.
3. Confirm procurement, security, privacy, accessibility, data and legal gates remain funded and independent.

Evidence to retain Affordability record, portfolio trade-offs, policy determinations and control-owner positions.

Decision or scoring rule Positive value does not make an unaffordable, uncontrolled or capacity-infeasible phase fundable.

Output and template Affordability and opportunity-cost rows in T04.

Acceptance gate AFFORDABLE, RESEQUENCE, CHANGE, DEFER or STOP.

Leadership checkpoint CEO and CFO accept the work or capacity displaced by funding.

Human control point Qualified authorities retain non-delegable approval and refusal rights.

Failure modes and safeguards Do not hide internal capacity in sunk payroll or treat a budget ceiling as value evidence.

Change, stop or escalation condition Defer when resources exist nominally but mandatory capability does not.

Handoff to the next step The complete case enters independent challenge.

Step 11: Reconcile and independently challenge the case

Purpose and decision served Test traceability, internal consistency and decision susceptibility.

Accountable owner CFO.

Delegated lead and contributors Independent finance or assurance lead with product, technology, operations and risk responders.

Preconditions, inputs and access Versioned charter, alternatives, model, sources, risks and phase gates.

Actions

1. Trace every material total to sources, owners, units, periods and assumptions.
2. Test double counting, omissions, inconsistent option maturity and circular benefit logic.
3. Record dissent, unresolved conditions and the consequences of contrary evidence.

Evidence to retain Reconciliation report, challenge log, model version, corrections and unresolved issues.

Decision or scoring rule Material unresolved defects remain visible and cannot be closed by sponsor assertion.

Output and template Challenge and reconciliation rows across T03 and T04.

Acceptance gate READY FOR DECISION, CORRECT, VALIDATE or STOP.

Leadership checkpoint CFO confirms limitations are prominent in the executive pack.

Human control point Independent challenger signs only the work performed, not the investment result.

Failure modes and safeguards Avoid approval theatre, hidden spreadsheet overrides and undocumented manual adjustments.

Change, stop or escalation condition Return to the responsible step when a material claim cannot be reproduced.

Handoff to the next step The reconciled case goes to executive disposition.

Step 12: Make the executive funding disposition

Purpose and decision served Convert evidence into one accountable, bounded funding decision.

Accountable owner CFO and designated investment authority.

Delegated lead and contributors Product Sponsor, CIO, COO, risk, procurement and secretary.

Preconditions, inputs and access Reconciled case, dissent, authority rules and phase gate.

Actions

1. Compare baseline and credible options across value, cost, burden, downside and reversibility.
2. Assign FUND NEXT PHASE, VALIDATE, CHANGE, DEFER or STOP with reasons.
3. Record maximum commitment, conditions, prohibited interpretations, owner and next decision date.

Evidence to retain Signed decision record, evidence version, dissent, conditions and funding authority.

Decision or scoring rule No aggregate score overrides a failed mandatory value, control, affordability or ownership gate.

Output and template Executive decision rows in T04.

Acceptance gate DISPOSITION RECORDED.

Leadership checkpoint Decision authority reads the downside, limitations and stop route before signature.

Human control point Only the named authority releases the bounded commitment.

Failure modes and safeguards Approval cannot be interpreted as partner appointment, delivery acceptance or full-programme funding.

Change, stop or escalation condition Defer when conditions cannot be stated in testable form.

Handoff to the next step The decision transfers to the appropriate controlled route.

Step 13: Transfer, monitor and reopen the case

Purpose and decision served Keep the case alive as evidence changes without converting it into perpetual approval.

Accountable owner Product Sponsor.

Delegated lead and contributors Finance controller, delivery governance, operations, procurement and benefits owners.

Preconditions, inputs and access Signed disposition, accepted phase, measures, change triggers and receiving authority.

Actions

1. Transfer only accepted assumptions, limits, costs, value contracts and gate evidence.
2. Reconcile actual commitments and evidence against the approved case without rewriting history.
3. Reopen, change, defer or stop when a material trigger is crossed; route delivery to The Product Delivery Governance Standard: From Discovery through Production Acceptance and later operating proof to The Product Adoption, Operability and Scale Gate: Proving Value after Launch.

Evidence to retain Handover acceptance, actual-versus-case updates, trigger log, decisions and closure record.

Decision or scoring rule An expired or materially changed case returns to decision; it does not inherit approval indefinitely.

Output and template Review, transfer and closure rows in T04.

Acceptance gate TRANSFERRED, REOPENED, CLOSED or STOPPED.

Leadership checkpoint CFO reviews material variance and later commitment before capital release.

Human control point Receiving owner accepts obligations; funding authority retains stop rights.

Failure modes and safeguards Actuals cannot be used to erase the original estimate, uncertainty or dissent.

Change, stop or escalation condition Reopen for material scope, architecture, supplier, cost, value, control or operating change.

Handoff to the next step Accepted partner diligence belongs to The Software Delivery Partner Appointment and Technical Due-Diligence Playbook, delivery to The Product Delivery Governance Standard: From Discovery through Production Acceptance, and adoption, operability and scale to The Product Adoption, Operability and Scale Gate: Proving Value after Launch.

4. The Evidence & Measurement Checklist

Preflight and authority

• The funding question names one decision date and accountable authority. Evidence: signed investment charter. Owner: CFO.
• Allowed dispositions include a credible stop decision. Evidence: charter disposition field. Owner: CFO.
• The next commitment is distinct from the total ambition. Evidence: phase boundary. Owner: Product Sponsor.
• Supplier and sponsor conflicts are recorded. Evidence: conflict register. Owner: Procurement Lead.
• Approval exclusions name partner, delivery, release and scale decisions. Evidence: prohibited-interpretation record. Owner: CFO.

Evidence access and quality

• The counterfactual has an eligible population, period and owner. Evidence: baseline contract. Owner: Product Sponsor.
• Current cost is separated from avoidable future cost. Evidence: baseline reconciliation. Owner: Finance Lead.
• Continue, improve, defer, retire and stop were considered where credible. Evidence: alternative register. Owner: CIO.
• Options are described at comparable outcome and maturity. Evidence: option-normalisation record. Owner: Product Lead.
• The Build, Buy, Configure, Integrate or Stop Decision: An Executive Technology Investment Playbook references support the selected investment route. Evidence: predecessor decision links. Owner: CIO.

Method execution

• Discovery, design, delivery, integration and migration have separate cost rows. Evidence: lifecycle cost model. Owner: Finance Lead.
• Security, privacy, accessibility, quality and assurance work is included. Evidence: assurance cost rows. Owner: CIO.
• Internal labour and scarce capacity are visible. Evidence: resource basis. Owner: COO.
• Support, monitoring, incidents, renewal, change and retirement are included. Evidence: operating cost rows. Owner: Service Owner.
• Every material cost has source, unit, period, range and owner. Evidence: cost-source trace. Owner: Finance Lead.

Governance, privacy, security and risk

• Each value claim links intervention, behaviour and eligible outcome. Evidence: value mechanism contract. Owner: Product Sponsor.
• Revenue, cost, capacity, retention, risk and service are not double counted. Evidence: overlap reconciliation. Owner: CFO.
• Baselines and thresholds remain unapproved until evidence owners accept them. Evidence: proof-state ledger. Owner: Data Owner.
• Usage and feature completion are not treated as outcome proof. Evidence: measurement contract. Owner: Product Lead.
• Market and operating contributors remain visible in attribution. Evidence: attribution boundary. Owner: Outcome Owner.

Deliverables and acceptance

• Scope uncertainty has a named driver, effect and validation route. Evidence: uncertainty ledger. Owner: Product Sponsor.
• Sensitivity tests vary material assumptions separately. Evidence: sensitivity record. Owner: Finance Lead.
• Coherent downside scenarios include operating and control consequences. Evidence: downside scenario. Owner: Risk Owner.
• Irreversible commitments and contingent exposure are visible. Evidence: exposure register. Owner: CFO.
• No probability or precision is presented without evidence. Evidence: modelling-method note. Owner: Independent Challenger.

Measurement

• The next phase is the smallest coherent evidence or delivery commitment. Evidence: phase definition. Owner: Product Sponsor.
• Later phase ranges are not described as approved budgets. Evidence: funding boundary. Owner: CFO.
• Affordability includes cash, capacity and mandatory control resources. Evidence: affordability record. Owner: CFO.
• Displaced portfolio work and opportunity cost are named. Evidence: portfolio trade-off. Owner: CEO.
• Every phase has acceptance, change and stop conditions. Evidence: phase gate contract. Owner: Product Sponsor.

Decision and handover

• Material totals reproduce from controlled source rows. Evidence: reconciliation report. Owner: Independent Challenger.
• Dissent and unresolved limitations appear in the executive pack. Evidence: challenge log. Owner: CFO.
• The executive disposition states reason, maximum commitment and conditions. Evidence: signed decision record. Owner: Investment Authority.
• Receiving owners accept the transferred obligations. Evidence: handover acceptance. Owner: Product Sponsor.
• The Software Delivery Partner Appointment and Technical Due-Diligence Playbook, The Product Delivery Governance Standard: From Discovery through Production Acceptance and The Product Adoption, Operability and Scale Gate: Proving Value after Launch authorities remain distinct. Evidence: route-control record. Owner: CIO.

Review, change and stop controls

• Actual commitments retain comparison with the original estimate. Evidence: actual-versus-case ledger. Owner: Finance Controller.
• Material scope, cost, value and control triggers reopen the case. Evidence: change-trigger register. Owner: CFO.
• Expired evidence cannot inherit approval. Evidence: evidence-expiry record. Owner: Proof Owner.
• Later funding requires the accepted phase evidence. Evidence: release-gate record. Owner: Investment Authority.
• Stopped cases retain reasons, residual obligations and lessons. Evidence: closure record. Owner: Product Sponsor.

Measurement contracts

Measure A: Cost-model evidence coverage

Measure B: Critical uncertainty retirement

Measure C: Phase commitment variance

Measure D: Operating burden readiness

Measure E: Accepted value outcome

Measure F: Downside exposure at decision

Evidence classifications used in this guide

• VERIFIED: an authoritative source supports the fact within a stated scope, population, period and limitation.
• INFERRED: a transparent interpretation is derived from retained evidence but remains distinguishable from fact.
• PROPOSED: an option, phase, value mechanism or threshold awaits accountable human acceptance.
• REQUIRES VALIDATION: a material cost, value, probability, baseline, dependency or operating condition is not decision-fit.

Controlled source record