# Case Study Capture Playbook

Capture the raw material for strong case stories before the details disappear.

## Capture Windows

The best case-study material usually appears in four windows:

- right before the work starts
- during the key intervention
- at the first visible outcome
- during the follow-up or stabilization phase

If those windows pass, the case story usually gets weaker fast.

## What to Capture

- screenshots
- baseline metrics
- workflow pain points
- customer quotes
- before/after observations
- operator notes
- timeline and next-step details

## Story Structure

Use a compact story spine:

1. `Situation`
2. `Friction`
3. `Intervention`
4. `Outcome`
5. `Why it matters`

This gives you enough structure for a short proof block or a flagship case page.

## Evidence Ladder

Rank evidence from strongest to lightest:

- attributable metrics
- attributable quote
- screenshot or visual proof
- operator observation
- structured before/after note

Use the strongest evidence available, but do not wait for perfect evidence to publish every story.

## Approval Flow

Create a clear approval path:

- capture owner collects raw material
- marketer or operator shapes the story
- sensitive details get reviewed
- final publish owner approves public use

Track consent and confidentiality status with every story.

## Publishing Ladder

One case story can support several surfaces:

- proof strip on a service page
- result block on a results page
- FAQ example
- blog/article deep dive
- sales follow-up asset

Publish the lightest useful version first, then deepen later if the signal is strong.

## Story Quality Checks

Before publishing:

- does the story explain what changed?
- is the evidence real and supportable?
- does it sound specific rather than generic?
- does it help a buyer understand fit or confidence?

## Monthly Review

Every month:

- review which stories were captured
- identify which ones deserve promotion to stronger surfaces
- note missing industries, service lines, or proof types

## 30-Day Installation

### Week 1

- define capture triggers
- assign story owners

### Week 2

- pilot the first 3 stories
- test the approval workflow

### Week 3

- publish light versions
- connect them to results and service pages

### Week 4

- review what worked
- improve the template and routing