Review Criminal Discovery: Timeline, Inconsistencies and Suppression Leads
Turn police reports, body-camera and interview transcripts, lab reports and warrant materials into a cited timeline, a side-by-side inconsistency list, a set of suppression leads to research and a list of discovery the prosecution has not produced.
When to use this
Use this when a discovery production arrives in a criminal case and you need to know what it shows, where the accounts conflict, what might support a motion, and what is missing. Claude cross-references every report and transcript you paste, keeps each fact tied to its source, and flags issues as leads for you to research. It does not decide which version of events is true or what the law permits.
Criminal discovery rarely tells one story. The arresting officer's narrative, the backup officer's supplement, the body-camera audio, the CAD log and the lab report were written by different people at different times for different purposes. The defense value is often in the gaps between them: a time that does not line up, a statement attributed to the client that the recording does not contain, a consent that appears in the report but not on camera.
This workflow has Claude build a single timeline from every source, with conflicting times shown side by side rather than reconciled, then compare the accounts and quote both versions of each discrepancy. From those facts it lists possible stop, search, seizure, statement, identification and chain-of-custody issues as leads, tied to specific facts and pinned to the discovery, with the law left as [JURISDICTION] and [APPLICABLE RULE] placeholders. It also lists items the reports refer to that were not produced and drafts a request letter for them.
Everything here is a starting point for the defense attorney's own review. Claude does not watch the video, and a transcript can omit what the recording shows. Claude does not know the controlling law in your jurisdiction and must not supply case names. Each lead is something to research and test against the actual recordings and evidence before it becomes a motion.
The Workflow
Set the context and load the discovery
Tell Claude you represent the defendant, the charges, the arrest date and what the review is for. Paste each item in its own labeled document tags, with Bates or page numbers, so every later cite points to a specific source.
PromptI represent the defendant, [CLIENT NAME OR INITIALS], charged with [CHARGES] in [COURT] arising from an arrest on [DATE]. The purpose of this review is [SUPPRESSION MOTION / PLEA EVALUATION / TRIAL PREPARATION]. Our working theory, if any, is [THEORY OR "none yet"]. The discovery produced so far follows, each item labeled. <document title="[OFFICER] Incident Report, [BATES RANGE]"> [PASTE] </document> <document title="[OFFICER] Supplemental Report, [BATES RANGE]"> [PASTE] </document> <document title="Body-camera transcript, [OFFICER], with timestamps"> [PASTE] </document> <document title="Search warrant and affidavit, [BATES RANGE]"> [PASTE] </document> <document title="Lab report, [BATES RANGE]"> [PASTE] </document> List each item with its label, author, date, page range and a one-line description. Note anything that looks incomplete, redacted, or referenced as an attachment but not included. Do not analyze yet.
What you get: An inventory of the production with incomplete or missing attachments flagged. Confirm the inventory against the production index you received.
Build a unified timeline
Have Claude merge every source into one timeline. Conflicting times or sequences stay side by side; Claude does not choose between them. Recording the basis for each officer's knowledge (observed, told by dispatch, told by another officer) matters for later analysis.
PromptBuild a single timeline from all the discovery. Use a table: Date / time | Event | Source and pin cite (label and page, paragraph or timestamp) | Actor | Basis of knowledge (personally observed / told by dispatch / told by another officer / stated by a civilian / unclear) | Conflicts Rules: - One row per event per source. If two sources give different times or sequences for the same event, put both rows next to each other and describe the conflict in the Conflicts column. Do not reconcile them. - Use the exact times as written, including "approx." and body-camera timestamps. - Include every statement attributed to the client, with who reported it and whether it appears in a recording. - If a time is missing, write "no time stated" rather than estimating.
What you get: A cited timeline with conflicts visible. Check the body-camera timestamps against the video itself; transcript timestamps can drift from the recording.
List the inconsistencies
Ask Claude to compare the reports against each other and against the transcripts, quoting both versions with cites and rating significance. It should flag uncertainty instead of assuming which version is right.
PromptCompare all sources and list every inconsistency. For each: No. | Topic | Version 1 (quote, source, pin cite) | Version 2 (quote, source, pin cite) | Nature of the difference (time, sequence, words attributed, presence of a person, physical evidence, other) | Significance to the defense (high / medium / low, with one sentence on why, given our purpose: [PURPOSE]) | Could it be innocent? (one sentence) Also list: - Statements attributed to the client in a report that do not appear in any transcript I provided, with the report quote and the transcript time range where it would be expected. - Facts asserted in the warrant affidavit that are not supported, or are contradicted, by other discovery, quoting both. Do not decide which version is accurate. Where the transcript is marked inaudible or unclear, say so rather than inferring the words.
What you get: A quoted, ranked list. The 'could it be innocent' column keeps the list honest and previews how the prosecution will explain each discrepancy.
Identify suppression and motion leads
From the timeline and inconsistencies, have Claude list possible issues as leads to research, each tied to specific facts and cites. The law stays as placeholders; Claude names the issue and the facts, not the cases.
PromptUsing the timeline and inconsistency list, identify possible motion leads for the defense. Consider: the basis for the initial stop or encounter; the scope and duration of any detention; any search or seizure (consent, warrant, exceptions claimed in the reports); custodial statements and the warnings given; identification procedures; chain of custody and handling of physical evidence; and the warrant affidavit's factual basis. For each lead give: Issue | Specific facts supporting it, each with a pin cite | Facts that cut against it, with pin cites | What we would need to establish it (testimony, video, records) | Governing law: [JURISDICTION / APPLICABLE RULE] placeholder describing the legal question to research. Rules: do not name cases or quote statutes. Do not state whether a motion would succeed. Rate each lead as worth researching / worth noting / weak, and explain the rating using only the facts.
What you get: A research list grounded in facts. Each lead goes through independent legal research (the Legal Research and Cite-Check workflow) and a review of the recordings before anything is drafted.
List missing discovery and draft a request
Have Claude list everything the produced materials refer to that was not produced, then draft a request letter for the attorney to review. Confirm what the prosecution must disclose under [APPLICABLE RULE] and constitutional disclosure obligations in your jurisdiction before sending. Also check whether requesting particular categories triggers reciprocal disclosure obligations for the defense (in federal court, Federal Rule of Criminal Procedure 16(b) works this way); confirm the effect under [APPLICABLE RULE] before deciding what to request.
PromptList every item referenced in the discovery that was not produced. For each: Item | Where it is referenced (quote and pin cite) | Why it matters to the defense (one sentence). Look especially for other officers' reports or notes, CAD or dispatch logs and audio, additional body-camera or dash-camera footage, photographs, lab bench notes and chain-of-custody forms, witness statements, and any recordings of the client's statements. Then draft a letter from [DEFENSE ATTORNEY] to [ASSISTANT PROSECUTOR / DISTRICT ATTORNEY] in [CASE NUMBER], requesting the items as a numbered list with the reference for each. Keep it professional and specific. Refer to the prosecution's disclosure obligations as "[APPLICABLE RULE] and the prosecution's constitutional disclosure obligations" and do not cite cases. Do not reveal defense theories, the inconsistency list or the motion leads in the letter.
What you get: A missing-items list and a draft request letter. Check the letter for anything that discloses defense strategy before it goes out.
Attorney review before anything is filed or sent
Verify every cite against the discovery, watch the recordings rather than relying on transcripts, research each lead independently, and confirm the disclosure rules, including any reciprocal discovery the request could trigger, before the letter goes out. Claude's output organizes the review; the judgment about what to pursue is the defense attorney's.
What you get: A verified timeline and inconsistency list, leads either researched or set aside, and a request letter sent only after attorney review.
Example Output
Illustrative example — names, facts, and figures are fictional.
INCONSISTENCY LIST EXCERPT (ILLUSTRATIVE / FICTIONAL)
State v. Darnell Whitcomb. We represent the defendant. Purpose: suppression motion.
1. Consent to search the vehicle
Version 1: "Whitcomb verbally consented to a search of the vehicle." (Ofc. Hale Incident Report, STATE-0004, para. 6)
Version 2: Ofc. Hale: "Mind if I take a look?" Whitcomb: "[inaudible] ... I mean, I'd rather you didn't." (Hale body-cam transcript, 00:14:32–00:14:41)
Nature: words attributed. Significance: high (the report relies on consent for the search).
Could it be innocent? Possibly, if consent was given off camera; no other source shows that.
2. Time of the stop
Version 1: "approx. 22:40" (Hale Report, STATE-0003, para. 2)
Version 2: CAD entry "TRAFFIC STOP 22:52" (CAD log, STATE-0019)
Nature: time. Significance: medium (affects how long the detention lasted before the canine arrived).
Could it be innocent? Yes, if the CAD entry was logged late.
MOTION LEAD (worth researching)
Issue: voluntariness of consent to the vehicle search.
Supporting facts: the transcript response above (00:14:32–00:14:41); two officers present at the driver's door (Ofc. Brandt Supp., STATE-0011).
Cutting against: Whitcomb later opened the trunk himself (body-cam 00:15:10).
Law: [JURISDICTION: standard for voluntary consent to a vehicle search].
MISSING DISCOVERY
Ofc. Brandt body-camera footage: referenced in STATE-0011 ("my BWC was activated"); not produced.
DRAFT for attorney review. Verify against the recordings and the production.Tips
- •Watch the video for every high-significance item. A transcript is someone's rendering of a recording, and tone, gestures, and what happened off-mic can change everything.
- •Keep conflicting times side by side. Choosing one too early hides exactly the discrepancies that can matter on detention length or the order of events.
- •Track the basis of each officer's knowledge. Whether a fact was observed directly or relayed by dispatch or another officer often matters to stop and warrant issues.
- •Never let Claude fill the law. Leads come back with [JURISDICTION] placeholders on purpose; the controlling standards in your court come from your own research.
- •Re-run the timeline and inconsistency steps when supplemental discovery arrives, pasting the new items alongside the old, and ask Claude to mark which rows changed.
A note on confidentiality
Criminal discovery often contains information about the client, complainants, witnesses and minors, including addresses, criminal histories and medical information, and it may be subject to a protective order or local rules limiting dissemination. Some jurisdictions restrict sharing discovery beyond the defense team. Confirm those limits before uploading anything, use a Claude plan whose terms exclude your inputs from model training (such as Team or Enterprise), and redact identifying details of complainants, witnesses and minors that the analysis does not need. Keep the defense analysis, including the inconsistency list and motion leads, as attorney work product. Everything Claude produces is a draft for attorney review; verify every cite against the discovery and research every legal issue independently.
Frequently Asked Questions
Can Claude review body-camera video directly?
This workflow works from transcripts, which is the reliable path in plain Claude. Use a transcript with timestamps and treat it as a guide to the recording, not a substitute. The defense attorney should watch the footage for every high-significance item before relying on it.
Will Claude tell me whether evidence should be suppressed?
No. It identifies leads: specific facts, with cites, that may raise a stop, search, statement, identification or chain-of-custody issue, plus the facts that cut against each one. Whether any lead supports a motion depends on the controlling law in your jurisdiction and on evidence beyond the reports, which the attorney researches and evaluates.
Is it appropriate to put criminal discovery into an AI tool?
It can be, with care. Check any protective order and local rules on dissemination of discovery, use a plan whose terms exclude your data from training, redact identifying details of complainants, witnesses and minors that you do not need, and keep the analysis within the defense team. Review your jurisdiction's ethics guidance on AI use.
How does this differ from building a case chronology?
A general chronology orders events. This workflow adds the defense-specific layers: conflicts kept side by side, the basis of each officer's knowledge, statements attributed to the client checked against recordings, motion leads, and a missing-discovery request.
Prompts used in this workflow
Get New Workflows Like This Every Week
Join the free Claude for Lawyers newsletter — practical workflows, prompts, and guides for everyday practice.