Skip to main content

Case Report Template

What report shape creates confidence without hiding risk?

Use six sections. Each section earns the next one.

Preconditions

  • The business spec is complete enough to name the reader, decision, and first workflow.
  • Research has produced company evidence, market signals, and tech/data-flow notes.
  • The rhetoric layer exists before report copy starts: evidence ledger, argument map, objection map, and confidence case.

Report Spine

SectionJobRequired Proof
RealityName the present-day constraint.Current pain, decision lag, cost, or risk.
DreamName the desired future state.Backcast horizon and what changes for the reader.
BridgeName the gap-crossing with confidence.90-day bet, owner, metric, budget, kill signal.
EvidenceShow why the claim can be trusted.Sources, dates, confidence tags, contradictions.
RhetoricExplain why change now, in this form.Thesis, objection map, counter-evidence, action logic.
DecisionMake the next action hard to misunderstand.GO/NO-GO, day-14 prerequisites, first meeting agenda.

Required Fields

FieldRule
ReaderOne role, not a committee.
DecisionApprove, reject, or investigate one action.
First workflowOne named workflow with before/after metric.
90-day proofMetric, owner, budget, threshold, kill signal.
ConfidenceVERIFIED, INFERRED, ASSUMPTION, or CONTRADICTED.
Source trailEvery major claim links to its source artifact.
Backcast24 months, 12 months, 90 days, and day 14.

Section Pattern

Each section should answer four questions in order:

  1. What hurts?
  2. What future becomes possible?
  3. What objection would stop the reader?
  4. What action should they take next?

If a section cannot answer all four, it belongs in research notes, not the report.

Rhetoric Gate

Before presentation, pressure the case through five instruments from Rhetoric:

InstrumentCase Question
EthosWhy can this source, agent, or adviser be trusted here?
LogosWhat exact claim and proof path hold the case together?
PathosWhat felt risk or reward makes action matter now?
ToposWhat shared frame lets the reader recognize the case?
KairosWhy this action, now, in this form?

The case should then meet the Wisdom test: what is the right decision, at the right time, with the right people, under the right proof condition?

Decision Summary

End the report with:

ItemRequired Shape
VerdictGO, NO-GO, or INVESTIGATE.
One thingThe first workflow or proof module.
ConditionsWhat must be true by day 14.
Kill signalThe trigger that stops spend cleanly.
Next actionOne verb-led action with owner and date.

Checks

  • A cold reader can name the business constraint in 60 seconds.
  • A CFO can find the conservative breakeven and kill signal without help.
  • The report does not ask for full transformation before the first proof.
  • The first action is verb-led and specific.
  • No section uses generic AI claims without business evidence.

Context

Questions

  • Which claim would the reader challenge first?
  • Is the kill signal visible before the ask?