How do I keep a checkable record of AI research done for a legal matter?
Record the research as steps with their source states, so every claim in the output can be walked back to what was resolved, what was not resolved, and what was never checked. Review the receipt and actual deliverable before accepting a handover.
Scope: general information about organising research records, not legal advice, and not a statement about privilege in your matter. Privilege and work-product questions belong to the responsible lawyer.
AI research for a legal matter has a specific credibility problem: the output reads with uniform confidence whether its sources were solid, shaky, or never opened. A checkable record removes the uniformity. Each research step saves its result and its source states at the time it runs (receipts in the AER-1 format, IETF Internet-draft-zambo-aer1-21), so the memo's claims inherit the record's honesty: this authority resolved, that one did not, this line was never source-checked and is labelled accordingly.
The privilege boundary is a records-design question, and it is answered by separation. The research record holds the research: questions asked of sources, sources consulted, findings. Strategy, assessments of the client, and litigation thinking live in the lawyer's own files, not in shared job records. Within a firm, handovers can be scoped to the matter team; the rule is that what gets shared is chosen at setup, not discovered at disclosure.
For the responsible lawyer, the record's practical gift is verification speed: sampling a memo means walking three claims back to their steps and sources, in minutes, instead of re-running the research. Research that cannot survive that walk gets fixed while it is still a draft, which is when fixing is cheap.
Checklist: the legal research record
1. One job per matter, named by matter reference, not by client secrets. 2. Research steps saved as they run, with source states per step. 3. Findings steps: each memo or summary saved as its own step when delivered internally. 4. Unresolved and unchecked items listed on the record, reviewed by the responsible lawyer before reliance. 5. Sharing: handover scoped to the matter team; strategy documents kept outside the job record. 6. Retention: per the matter's file policy, exported with the matter file at close.
Worked example
Sample: a research memo on a limitation question. The record shows six research steps: five authorities resolved, one not resolved and flagged; the memo step cites the five. The reviewing lawyer samples two claims back to their steps in minutes and sends the sixth source for manual checking before the memo leaves the building. Public handovers in this section show the step and source-state shape. (Sample scenario; no live record is cited.)
Frequently asked questions
Does recording research create disclosure risk?
Records questions are real ones for your firm's own policies, which is why the page separates research records from strategy and scopes sharing deliberately. What the record changes is accuracy and verifiability; how it is held and shared follows the matter's privilege advice, not this page.
The AI cited a case that does not exist. How does the record help?
The source state for that step shows the citation was never resolved against a real source, which catches the failure at review instead of in court. Unresolved flags are the record doing its most valuable work in legal research.
Who should be able to open the record?
The matter team, through the handover's sharing, and no one else by default. The record's checkability is for its intended readers; public verify paths check a receipt's integrity, not the matter's contents.
By Brennan Zambo, founder of Zambo.
Last verified: 2026-10-17.
Try a handover
A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.
try it: say 'use zambo to hand this over to <client>' in your ai