Back to playbooks

Complaint to Case File

Use when: people keep saying “this keeps happening” and you want something usable.
Goal: turn anecdotes into a clean record that can support an ask, an oversight complaint, or a pattern claim.

Why this matters

Complaints are easy to dismiss when they stay vague. Case files create structure:

• what happened
• what it cost
• who decided
• what fix is being requested

This is how you build receipts without turning into rumor culture.

What belongs in a case file

• dates
• names and offices if known
• bills, notices, screenshots, emails
• money lost, time lost, service denied, or harm caused
• the exact rule, form, or decision point involved

Use the case file intake template.

The pattern test

Before you claim a larger pattern, ask:

• Is this one incident or a recurring failure mode?
• Do the facts point to the same bottleneck each time?
• What would count as disconfirming evidence?

Decision rules

• If the story is still mostly memory, document it before you broadcast it.
• If the harm is ongoing, ask for the immediate fix and the structural fix separately.
• If the facts are thin, say “possible pattern” instead of “proven pattern.”
• If you have 3-5 similar files, you probably have a usable oversight or reporting ask.

Good outputs

• one clean case file
• one short summary paragraph
• one practical ask tied to the case

Definition of done

Leave with:

1. one documented case file
2. one named owner or venue
3. one next step
4. one log entry

Back to playbooks