Free CITE Prompt Builder · No signup
Choose the work product, record type, and practice context. Get a copy-ready prompt with explicit scope, output format, and pinpoint-citation rules—assembled in your browser.
Prompt text only. No case-file upload. Matter-specific details are assembled on this device and are not sent to a CasePrompts API by the deterministic builder.See the public-tool data path →
Free builder output
Runs in your browserEvery result includes the four CITE blocks an AI needs before it touches the record.
Evidence requirement
47:12–48:3Cite every material statement to the record. If support is not present, say “not found in the record” rather than infer.
Free and working now
Pick a task, source, and practice context. CasePrompts assembles a copy-ready CITE prompt in your browser. No document upload. No signup.
Already have a prompt? Check its structure locally →Eligible prompts assemble with your practice priorities already composed in.
Current public-tool boundary
The free builder assembles prompt text on your device. The public site has no case-file upload or record-ingestion workflow, and matter-specific detail values do not enter setup links. Optional cloud review is a separate, explicit action. Review the full data boundary →
Start with the deliverable
Each workflow defines the assignment, output shape, and evidence standard before the record is reviewed.
Turn a complete deposition transcript into a topic-based page-line summary with precise cites, verbatim excerpts, admissions, exhibits, and unanswered questions.
Pull every admission, damaging concession, and 'I don't know' on your key issues out of a transcript — with verbatim Q&A and page:line cites.
Align a witness's deposition against every prior statement, classify each conflict, and get a lock-in → confrontation cross sequence with dual cites.
Turn the verified case record into a topic-based deposition outline with fact-locking goals, record-cited exhibits, conflict probes, and open-to-closed question sequences.
The review standard
CITE defines who the work is for, what the task is, the output shape, and the source standard. In today’s tools it creates copy-ready prompt text. In the planned workbench it becomes the workflow contract.
C — Context
Who you are, the matter, the document, the case posture.
I — Instructions
The precise task with explicit scope.
T — Template
The exact output format the AI must fill.
E — Evidence
Citation requirements — page:line, timestamp, Bates — plus the anti-hallucination directive: if it’s not in the record, say “not found in the record” — never infer.
Practice context
Practice lenses change what a workflow prioritizes—not the requirement to show its source.
View all 12 practice lenses →Privacy, source & review
A pinpoint makes a finding inspectable. It does not make the finding accurate.
Any Workbench pilot would require an explicit draft state and human approval before export or downstream use.
The public builder creates prompt text in the browser and does not upload case files.Review the data path →
CasePrompts Workbench · Planned product preview
Workbench is the planned next layer: one certified deposition, its exhibits, and a defined work product with the page and line kept beside every material finding.
Begin with one certified deposition and the exhibits that belong with it.
Set the context, instructions, output template, and evidence rule before asking for analysis.
Require each material finding to carry the certified transcript page-and-line location.
A person checks the source, revises the draft, and decides what becomes work product.
Planned product preview. File upload, matter processing, and review controls are not live on the public site.
Explore the Workbench preview →
I’m Andrew. I’ve spent my career in Florida litigation support—depositions, transcripts, and the certified record.
CasePrompts started because “summarize this” is not a litigation workflow. The CITE library made the assignment clearer. The Workbench is the next step: pair that assignment with the record and make source review part of the product.
The public builder remains a practical, local-first tool, like depoaudio.com. It generates prompt text in your browser and does not accept case files. The private Workbench shown here is still in development and is not accepting matter files. Provider routing, retention, deletion, access controls, and legal terms must be set and disclosed before processing opens. See how today’s tools handle data.
More about me at andrewmayes.com or on LinkedIn. Something broken, or a template you wish existed? support@caseprompts.com