Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
A strong business case can survive scrutiny even if the preferred option is removed: the problem is evidenced independently, alternatives including doing nothing are considered fairly, estimates and assumptions are visible, benefits are tied to measurable outcomes, and the recommendation reflects risk as well as upside.
Business case Executive summary: [decision + recommendation] Problem/opportunity: [baseline evidence] Objectives: [measurable outcomes] Options: [including status quo] Costs: [one-time + recurring + assumptions] Benefits: [measurable + timing + confidence] Risks/dependencies: [x] Implementation: [scope/owner/timeline] Recommendation: [why this option] Decision requested: [approval/funding/next gate]
Option comparison Criterion | status quo | option A | option B | evidence/source | uncertainty
One-page business case Problem: [x] Proposed action: [x] Cost range: [x] Expected benefit: [x] Top assumptions: [x] Top risks: [x] Decision: [x]
Business-case audit Problem independent of solution? [ ] Do-nothing option considered? [ ] Forecasts labeled? [ ] Recurring cost included? [ ] Benefits measurable? [ ] Decision/owner explicit? [ ]
Provenance and classification audit for Business Case: draft statement/example → [ ]; classify as fact / interpretation / recommendation / convention / original example → [ ]; source or internal provenance → [ ]; source date / version / checked date → [ ]; attribution needed → [ ]; recency risk → [ ]; final publishable wording → [ ].
Source-record and update audit for Business Case: statement / example → [ ]; external fact, project fact, interpretation, recommendation, convention, or original example → [ ]; controlling first-party / primary source → [ ]; secondary source if used → [ ]; source record / locator → [ ]; date or version checked → [ ]; update trigger → [ ]; publish / qualify / revise / hold → [ ].
Source-ledger and revision-history audit for Business Case: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].