Can legal AI tools produce an AI disclosure record for a court?
legal AI vendors export a document level disclosure record covering the model used, the sources retrieved and the human verification.
A growing number of judges require anyone filing a document to state whether generative AI was used in preparing it and, if it was, to certify that a person checked every citation against the source. The question sounds procedural and it is not. Answering it honestly means knowing which model produced which passage, what was retrieved to produce it, whether the authority it cites is still good law, and who verified it. A product either keeps that record or it does not. Of 164 legal AI vendors recorded by the AI Legal Index, 1 export a document level disclosure record covering the model used, the sources retrieved and the human verification. 91 produce some of those elements, short of a per document export. 1 publish disclosure guidance or a template with no product support for producing the record, which is a courtesy that leaves the work exactly where it was. 71 publish nothing on court disclosure or verification certification at all. The certifying signature belongs to the lawyer in every case. What varies is whether the evidence behind it takes two minutes to produce or has to be rebuilt from memory under a deadline.
Whether an order applies to a given filing is a question for the court that issued it, and the duty to check the filing is the lawyer’s whatever the software did, so this page does not tell anyone what to disclose and is not a substitute for the order in front of them. What an index can do is answer the part the order leaves to the product: whether the record a judge is asking for exists anywhere except in the filer’s memory. The index records that on every vendor, alongside the two records that decide whether the certification behind it is worth anything.
vendors export a document level disclosure record covering the model used, the sources retrieved and the human verification.
give the filer nothing to work from: 1 publish a template or guidance with no product support behind it, and 71 publish nothing on the subject at all.
vendors with any record support also surface a good law check, the half of the certification a person cannot do by eye. The rest certify a verification that stops one step short.
vendors that appear in a public court record involving their output can now produce the record a court would ask for.
What a standing order actually asks for
The orders differ from courtroom to courtroom, and that is the first thing to know about them. Some require a disclosure of any use, some require a certification that a human verified the output, some cover generative AI only, and some courts have said in terms that they will require nothing of the kind. The strict version, the one that began in a federal court in Texas in 2023 and has been copied since, asks three things. Whether generative AI was used in preparing the filing. If so, which portions. And whether a human being checked every citation and every legal assertion against the source. Each line calls for a different piece of evidence, and the index records whether a product can supply it: 92 of 164 vendors keep any record that AI touched a document, 1 keep it at the level of the passage, and 15 of 164 surface a good law check on the authority the product cites, which is the part of the third line a person cannot do by eye.
The easiest line to answer and the hardest to evidence six months later. It needs a record that AI touched the document at all, attached to the document rather than to a subscription.
A yes on line one is useless without this. It needs the record kept per passage, with the model that produced it and the sources it was produced from, exportable with the document.
The signature is the lawyer’s. But a citation that exists and is quoted correctly can still be dead law, and finding that out takes a citator the product either surfaces or does not.
What a complete record contains, and who can fill each line
No court has published a form, so this is a specimen rather than a template: the lines a complete disclosure record would need to carry to answer the strict version of the order. Two of them belong to the filer and always will. The other six are product lines, and beside each one is the index record that says how many vendors publish enough for the product to fill it. Read the right hand column as the market answering the court.
Counts are of vendors whose published material supports the line, on the date shown against each record. A product that keeps the information and does not export it scores on line one and not on line two, which is the difference between a partial record and an exportable one.
Vendors that export the record
Exportable disclosure recordClearbrief export a per document record covering the model used, the sources retrieved and the human verification, which is the artifact a standing order is asking for. 91 vendors produce part of that record, short of a document level export: Alexi, Amplified, Aracor AI, AscentAI, AttiFin AI, Bloomberg Law, CaseMark, Casepoint, Checkbox, Claren, Clio, CoCounsel Legal, Compliance Intelligence, Corlytics, Corsearch, Counsel Stack, CUBE, DataGrail, DataGuard, Dazychain, DecoverAI, DeepIP, Definely, Descrybe, DigitalOwl, DISCO, Docket Alarm, Dodonai, Eve, EvenUp, Everlaw, Exterro, Filevine, FinregE, GC AI, Genie AI, Harvey, Hona, Huski.ai, InPractice, IP Author, IPRally, Ironclad, Jhana.ai, Jimini AI, Josef, LawPro.ai, LawX, Leah, LegalClerk.ai, LEGALFLY, LegalVIEW BillAnalyzer, Legalyze, Legartis, Lexis+ AI, MarqVision, MyCase, Neos, Nextpoint, Norm Ai, Noxtua, OneTrust, Onspring, Patlytics, PatSnap, Paxton AI, Pre/Dicta, ProPlaintiff, ProVision, Regology, Relativity, Reveal, Securiti, SimplyConvert, Sirion, SmartDepo, Smith.ai, Solve Intelligence, SpotDraft, Steno, Supio, Tavrn, Tonkean LegalWorks, Transcend, TrialView, UniCourt, Vincent AI, Vixio, Wexler AI, Wordsmith and Workday Contract Lifecycle Management. 1 publish guidance or a template with nothing in the product to fill it from, and 71 publish nothing located on the subject.
Part of the record
Partial recordSome elements of the record are available from the product, short of a per document export. A filer working from one of these assembles the disclosure from what the product logs and fills the rest by hand.
- AlexiLegal Research
- AmplifiedIP & Patents
- Aracor AIContract Review & Drafting
- AscentAIRegulatory & Compliance Counsel
- AttiFin AIGeneral Legal Assistants
- Bloomberg LawLegal Research
- CaseMarkLitigation & eDiscovery
- CasepointLitigation & eDiscovery
- CheckboxLegal Ops & Spend
- ClarenContract Review & Drafting
- ClioIntake & Client Development
- CoCounsel LegalGeneral Legal Assistants
- Compliance IntelligenceRegulatory & Compliance Counsel
- CorlyticsRegulatory & Compliance Counsel
- CorsearchIP & Patents
- Counsel StackLegal Research
- CUBERegulatory & Compliance Counsel
- DataGrailRegulatory & Compliance Counsel
- DataGuardRegulatory & Compliance Counsel
- DazychainLegal Ops & Spend
- DecoverAILitigation & eDiscovery
- DeepIPIP & Patents
- DefinelyContract Review & Drafting
- DescrybeLegal Research
- DigitalOwlPlaintiff & Claims AI
- DISCOLitigation & eDiscovery
- Docket AlarmLegal Research
- DodonaiLitigation & eDiscovery
- EvePlaintiff & Claims AI
- EvenUpPlaintiff & Claims AI
- EverlawLitigation & eDiscovery
- ExterroLitigation & eDiscovery
- FilevinePlaintiff & Claims AI
- FinregERegulatory & Compliance Counsel
- GC AIGeneral Legal Assistants
- Genie AIGeneral Legal Assistants
- HarveyGeneral Legal Assistants
- HonaIntake & Client Development
- Huski.aiIP & Patents
- InPracticePlaintiff & Claims AI
- IP AuthorIP & Patents
- IPRallyIP & Patents
- IroncladContract Review & Drafting
- Jhana.aiLegal Research
- Jimini AIGeneral Legal Assistants
- JosefLegal Ops & Spend
- LawPro.aiPlaintiff & Claims AI
- LawXLegal Ops & Spend
- LeahContract Review & Drafting
- LegalClerk.aiIntake & Client Development
- LEGALFLYGeneral Legal Assistants
- LegalVIEW BillAnalyzerLegal Ops & Spend
- LegalyzePlaintiff & Claims AI
- LegartisContract Review & Drafting
- Lexis+ AILegal Research
- MarqVisionIP & Patents
- MyCaseIntake & Client Development
- NeosPlaintiff & Claims AI
- NextpointLitigation & eDiscovery
- Norm AiRegulatory & Compliance Counsel
- NoxtuaGeneral Legal Assistants
- OneTrustRegulatory & Compliance Counsel
- OnspringRegulatory & Compliance Counsel
- PatlyticsIP & Patents
- PatSnapIP & Patents
- Paxton AIGeneral Legal Assistants
- Pre/DictaLegal Research
- ProPlaintiffPlaintiff & Claims AI
- ProVisionLegal Ops & Spend
- RegologyRegulatory & Compliance Counsel
- RelativityLitigation & eDiscovery
- RevealLitigation & eDiscovery
- SecuritiRegulatory & Compliance Counsel
- SimplyConvertIntake & Client Development
- SirionContract Review & Drafting
- SmartDepoLitigation & eDiscovery
- Smith.aiIntake & Client Development
- Solve IntelligenceIP & Patents
- SpotDraftContract Review & Drafting
- StenoLitigation & eDiscovery
- SupioPlaintiff & Claims AI
- TavrnPlaintiff & Claims AI
- Tonkean LegalWorksLegal Ops & Spend
- TranscendRegulatory & Compliance Counsel
- TrialViewLitigation & eDiscovery
- UniCourtLegal Research
- Vincent AILegal Research
- VixioRegulatory & Compliance Counsel
- Wexler AILitigation & eDiscovery
- WordsmithGeneral Legal Assistants
- Workday Contract Lifecycle ManagementContract Review & Drafting
The whole field, on one signal
The order is the same in every case. What changes is the afternoon. The table sets out the four tiers the index records on this signal, how many vendors sit in each, and what the same task, a disclosure due with a brief, looks like when worked from each of them.
A signal records what public sources say on the date shown. It is not a grade and it is not a recommendation. Where a signal reads Not addressed, it means the index did not locate the material in public sources on that date, which is a statement about disclosure rather than about the product.
| Tier | What it records | What the filer does | Vendors |
|---|---|---|---|
| Exportable record | Per document export covering model used, sources retrieved and human verification. | Opens the export, reads it, signs the certification, attaches both. The verification still has to have happened. The record of it is already written. | 1 |
| Partial record | Some elements available, short of a document level export. | Pulls what the product logs, works out which passages it covers, and fills the gaps from the draft history by hand. | 91 |
| Guidance or template only | Disclosure guidance or a template published, no product support behind it. | Has been told what to write and given nothing to write it from. Every field is reconstructed, with the template as a reminder of what is missing. | 1 |
| Not addressed | Nothing located on court disclosure or verification certification. | Reconstructs from memory which passages, which model, which sources and who checked, and certifies the result. The one tier where the honest answer to line two might be that nobody knows. | 71 |
| Total | Vendors carrying this signal | 164 | |
Does the record prove the citations were verified?
Checking a citation is three checks, not one. The case exists. It says what the brief says it says. And it is still good law, meaning nothing since has vacated, reversed or limited it. A lawyer does the first two by opening the opinion. The third takes a citator, and whether the product surfaces one is recorded separately in this index as Good Law Verification. Crossing the two records is where the certification gets pointed. Of the 92 vendors with any court disclosure support, 14 also surface subsequent history on the authority they cite: AscentAI, Bloomberg Law, CoCounsel Legal, Compliance Intelligence, Corlytics, Corsearch, CUBE, Descrybe, FinregE, Huski.ai, Lexis+ AI, Paxton AI, Vincent AI and Vixio. 78 keep a record of the work while leaving the currency of the law unchecked, which produces a disclosure that certifies a verification stopping one step short. And 1 vendors run a citator with no disclosure record at all, so the check happens and nothing survives to show a court that it did.
Across the whole index, 3 vendors surface a licensed citator inline, 12 compute their own treatment signal with the method described, 2 instruct the reader to verify without performing the check, and 147 of 164 publish nothing on whether authority is checked for subsequent history.
A record of the work and a check on the law
Licensed citator, surfaced inlineHas output from these products already reached a court record?
The orders exist because of what happened before them. In 2023 a federal court in New York sanctioned the lawyers responsible for a brief that cited cases which did not exist, invented by a general purpose chatbot and filed without anyone opening them. Within days of that story breaking, a federal judge in Texas issued the first standing order requiring every filer to certify either that generative AI had not been used or that a human had checked its work, and the public trackers of decisions involving fabricated citations now run to hundreds of entries. The index records, for each product, whether a public court record exists involving its output, and it records what the record says rather than what anyone concludes from it. Of 164 vendors, 163 have no court record located as of the date shown, 1 appear in a record whose findings address the filer's failure to verify, 0 appear in a record whose findings address the product's own output, and 0 have published a substantive response to a record. The join a buyer actually wants is the next one: of the 1 vendors that appear in any court record, 1 now offer court disclosure support at some tier, and 0 do not.
| What the record says | Vendors | With disclosure support |
|---|---|---|
| None located as of the date shown | 163 | 91 |
| Findings address the filer’s conduct | 1 | 1 |
| Findings address the product’s output | 0 | 0 |
| Vendor has responded publicly | 0 | 0 |
| Total | 164 | 92 |
This is the one record in the index that can reflect badly on a named company, and it is bounded on purpose. It is rendered here as counts and not as a list. A recorded value describes what a court record says and never what the index concludes from it. An adverse value requires a citation to the deciding court and the date, distinguishes a filer who did not check from a product that misrepresented its own grounding, and is sent to the vendor before it publishes. Nothing located is the most common value and it is a statement about the public record, not a finding about the product. The detail, with the citations, sits on each vendor’s profile.
What the index cannot tell you
Whether you have to disclose. Orders vary by judge, by court and by local rule, they keep changing, and some courts have declined to issue one. Whether a given record satisfies a given order is a question for that court. Nothing here is legal advice. A vendor publishing nothing about court disclosure is a statement about that vendor’s disclosure and not about anyone’s compliance, and a vendor that exports a record has not thereby made any particular filing accurate.
The records reach only as far as public material, and an absence is dated: not located in public sources on the date shown, redated the day the vendor publishes. The reason the published position still matters is the one that runs through this whole index. A certification is a sworn statement, and the evidence behind a sworn statement should exist before the statement does, in a form that can be produced when a court asks to see it. The products that keep that record have understood what the orders are for.
Every record behind this page carries a source basis and a verification date. Standards and limits are on the methodology page. The obligations this sits inside are on what the bar rules require before a lawyer uses AI on client matters, whether the citations were right in the first place is on which AI legal research tools publish their hallucination or accuracy rates, the same record on the invoice is on how should a law firm bill for AI assisted work, and the complete vendor set is in the directory.