Build
the Record

The record argues by existing

Free, open methods and AI prompts for building a professional-grade case file: the dated, verified, quote-them-verbatim paper record that wins reviews, appeals, and disputes — or hands your lawyer a running start. Developed inside a real self-represented case; everything specific removed, everything repeatable kept.

See a demonstration case file Get the methods on GitHub

§ 1 Who this is for

Representing yourself The prompts walk an AI assistant through building the entire case file — inventory, timeline, ledgers, records requests, adversarial review, the packet — while every decision that matters stays yours.
Preparing for counsel The same file is the one every attorney wishes clients brought to the first meeting: complete, dated, honestly curated, with your own weak points flagged for your lawyer instead of discovered by the other side.

§ 2 The methods — and what a finished case file looks like

Each method produces a working case file. The demonstrations below are fully fictional, but the shape is the real product: the ledger of what they did in their own words, the timeline, the evidence grid, every document one click away.

buildtherecord.org/lemon-case-file
Demonstration lemon-law case file: swimlane timeline and exemplar recordings

Vehicle defects & lemon law

Component ledger · defect timeline · diagnostic-records request · gated evidence site with an access log.
Open the demonstration Method
buildtherecord.org/health-insurance-case-file
Demonstration insurance appeal file: deadline board and denial ledger

Health-insurance denials

Deadline board · claim-file request · denial ledger · appeal packet · external review. Under 1% of denials are appealed; a third of appeals win.
Open the demonstration Method
buildtherecord.org/contractor-case-file
Demonstration contractor case file: payment-to-scope table and promise ledger

Contractor disputes

Payment-to-scope trace · promise ledger · public permit record · demand letter · two-tier packet for counsel.
Open the demonstration Method

§ 3 The doctrine, short form

One source of truth: every artifact is generated from a single catalogue, and every number is computed and asserted at build time. A document proves only what it shows. Quote them verbatim. Curate ruthlessly; never omit what would make you look dishonest.

The counterparty-file principle: whoever decided against you assembled a file to do it — request it before you argue with it.

Adversarial review before sending: have your own case attacked from the other side's perspectives, and fix what the hostile reading finds. State facts. The record argues by existing.

§ 4 Contribute

Every method improves when someone runs it. Prompt fixes from real use, per-jurisdiction signpost files (dated and cited — see any repo's jurisdictions/), and anonymized outcomes are the contributions that compound. Real case documents are never accepted: the repositories stay 100% synthetic. New domains are welcome where the fitness test holds — disputes decided on paper, with a records right, a deadline ladder, and many unrepresented people losing by default.

Not legal advice These are methods for organizing evidence and process, not a substitute for a lawyer. Deadlines are real and jurisdiction-specific; the repositories' own rule is that no deadline is ever taken from a template — everything is re-verified against primary sources at use. When the stakes are high, bring the record to counsel. That is half of what it is for.