Legal and Compliance

Do Lawyers Have to Verify AI Output? California's Rule

Increasingly, yes. On May 5, 2026, California's State Bar proposed that lawyers independently review and verify AI output used in client work. Connecticut and New York moved to the same standard of independent checking.

Do Lawyers Have to Verify AI Output? California's Rule

On May 5, 2026, the California State Bar's ethics committee proposed a new comment to Rule 1.1 (Competence). It would require lawyers to independently review and verify AI output used in client work. Connecticut's Rules Committee proposed a parallel requirement weeks earlier. New York's Uniform Court System Part 161 takes effect June 1 with the same standard of independent checking. Three states proposed or enforced much the same duty to verify AI output, all within 30 days. That looks less like a coincidence and more like a cascade.

The rule leaves a working question open: what does 'independent verification' mean? Pasting a draft back into the same model's API and asking 'is this correct?' does not qualify. This post walks through the proposed text and the spread of the rule across states. It covers the enforcement record that prompted it. And it shows what an objective standard for 'independent' looks like in practice.

The California rule asks for an independent, active check of any AI output in client work

The California State Bar circulated a redline, a marked-up draft, in April 2026. The proposed comment to Rule 1.1 (Competence) is short. It reads: 'When using technology, including AI, a lawyer must independently review and verify any output used in representing a client.' That is the whole comment. It sits in the proposed amended rules redline. The Newsroom of the California Courts confirmed it on May 5, 2026. Five other ethics changes on AI came with it, covering disclosure, confidentiality, candor and supervision.

Three things matter about the wording.

The duty is independent

The rule does not say 'review the AI output.' A lawyer already has a competence duty to review their work product. The new word is 'independent,' and that word carries the change.

The duty is affirmative

The rule does not say 'do not rely uncritically on AI.' It says 'review and verify.' That is an action, and it leaves a record. A lawyer asked 'did you verify this independently?' needs a better answer than 'I read it again.'

The duty applies to any output used in representing a client

It does not say 'AI-generated citations' or 'filings.' It says outputs. That word covers research summaries, deposition prep memos, draft contract clauses and witness questions. It covers anything that travels from the model into client work.

Bob Ambrogi's LawNext walkthrough sent the exact 'independently review and verify' language to the bar and to in-house lawyers. Every California lawyer with an AI workflow now has that language on their desk.

Re-reading an AI draft is not independent verification

The rule does not say what 'independent' means, yet the answer is the working core of the duty. Consider two workflows.

Workflow A

A lawyer drafts a brief with Claude, then pastes the draft back into Claude. The lawyer asks: 'Are these citations accurate? Are these arguments correctly stated?' Claude replies with confidence that everything looks fine. The lawyer files.

Workflow B

A lawyer drafts a brief with Claude, then pulls the citations into Westlaw. The lawyer confirms each one exists, says what is claimed and is still good law. Then GPT and Gemini are asked to pull the supporting passages from the actual sources on their own. The lawyer files only when the pulls from the different vendors agree.

Workflow A is what most lawyers describe when they say 'I checked the AI output.' Workflow B is what the proposed rule actually requires. The difference is in the structure. In Workflow A, the same probability distribution that produced the draft grades the draft. That distribution is the spread of answers the model finds likely. Workflow B brings in sources of error that do not line up with the first. That is the architectural reason independence has working meaning.

Here is why this matters for the duty. In April 2026 the Northern District of California fined a managing partner for failing to supervise a junior. The junior's AI-fabricated citations had reached a filing (Bloomberg Law, April 29 2026). The court did not fault the AI tool. It faulted the supervision chain. Verification is now part of supervision. 'I read it again' is not a defense. 'We ran it through cross-vendor consensus' is.

A practical playbook published April 24 by Unite.ai proposes evidence-linked outputs. Each one carries traceable sources, the reviewer's identity, timestamps, and the model name and version. That framework is what defensible verification looks like as a paper trail. It does not name the mechanism, but one thing follows anyway. A paper trail of the same model checking itself is not evidence of independence.

Notice the pattern. Workflow B is just Workflow A with a second probability distribution checking the first. That is what TrueStandard does. Paste your draft, and four frontier models check it in parallel in 60 seconds, with every disagreement shown.

California, Connecticut and New York moved within a month

Three states moved in the same 30-day window.

California (May 5, 2026)

A proposed Rule 1.1 comment requiring independent verification of AI output, plus five related ethics changes. See the Cal Bar redline PDF.

Connecticut (April 23, 2026)

The Rules Committee proposed changes to the practice book. Attorneys and people representing themselves would have to independently verify all citations and authorities produced by generative AI. One law firm's view is that this fits long-standing duties rather than adding new ones (Day Pitney via Law360).

New York (effective June 1, 2026)

UCS Part 161 is already adopted. It requires attorneys who used AI to 'carefully review papers and independently ensure no fabricated material.' Local courts are posting compliance guidance now (master rule, Kings County local).

The eDiscovery Today May 6 roundup treats the spread across states as the story, more than any one rule. Three states acted nearly in parallel with much the same language. That is how a national standard gets written without a federal rule. The next 90 days will produce more state proposals. Firms watching the spread are already adjusting their internal QA before the rules take effect.

California is writing the rule as AI sanctions grow

The enforcement record already exists, and it is growing. The sanction record on AI citations reads like a timeline of the rule being written. In the same window the proposal was being drafted:

Pa. attorney

$5,000 sanction plus AI-ethics training for an AI-generated case citation. Judge 'appalled' by repeated bogus citations (Law360, April 20 2026).

Sullivan and Cromwell

Apologized to Bankruptcy Judge Martin Glenn (SDNY) for AI-introduced errors in a Chapter 15 filing. Opposing counsel flagged the errors (Reuters, April 21 2026).

Georgia Supreme Court

Sanctioned an Asst. DA for fake AI-generated citations in a murder appeal (Law360, May 5 2026).

California State Bar

Brought discipline charges against several lawyers for filings with fake AI citations. One faces a probationary suspension (LA Times, April 13 2026).

Court order in deposition

Barred a deponent with no lawyer from using ChatGPT to answer deposition questions. It also rejected the privilege claim, because no attorney was involved (EDRM, April 27 2026).

Delaware Chancery $250M earn-out dispute

Cited a CEO's ChatGPT records in the judicial opinion. AI chats are now part of the evidentiary record (Alston Privacy, April 28 2026).

Five jurisdictions sanctioned five different practitioners in 30 days, for versions of the same failure. At that point the rule writes itself. The California proposal is not new. It writes down what judges have been doing case by case.

Asking ChatGPT to fact-check itself does not count as independent

The rule's own word, 'independently,' rules it out. The reason lies in the structure. A single AI model checking its own output is a closed loop. The model that produced the hallucination is the same probability distribution now asked to judge it. Asking the same model whether its output is correct asks the source of the error to grade itself.

The April 2026 Microsoft Research DELEGATE-52 benchmark measured this directly. Frontier models corrupt an average of 25% of document content over 20-step workflows. Those models are Gemini 3.1 Pro, Claude 4.6 Opus and GPT 5.4. The paper finds that 'agentic tool use did not measurably reduce corruption.' Adding more steps with the same vendor makes the failure worse rather than catching it.

A Purdue preprint came out at the same time: No Free Lunch: Fundamental Limits of Learning Non-Hallucinating Generative Models. It proves a stronger statement. Learning never to hallucinate is statistically impossible from training data alone, no matter how clean the corpus, the body of training text.

So single-vendor checking cannot, in principle, be the main defense. Independent verification, in the sense the California rule uses, needs a source of error that does not line up with the first. In practice that means a different vendor: a model from another provider, with a different training run and different alignment. Multi-vendor consensus is the only design where 'independent' has a working meaning.

Notice the pattern. Same vendor checking same vendor is the same probability distribution grading itself. TrueStandard does it differently. Paste your draft, and four frontier models from different labs check it in parallel in 60 seconds, with every disagreement shown.

A defensible AI workflow has five parts, starting with a second vendor

Five elements, drawn from the Unite.ai defensible-LLM-outputs playbook and the supervisor-sanction precedent in NorCal.

Multi-vendor verification

Run claims through models from at least two different vendors. The record of the check includes the disagreements, not just the consensus.

Recorded model identity and version

The log records which models were used, at what version and on what date. This is the audit trail a regulator or judge can ask to see.

Reviewer identity

A named person signs off on the verified output. The signature links the AI workflow to the lawyer's professional duty.

Risk-stratified gates

Not every output needs the same depth of check. Citations and statistical claims get the closest look, and style edits do not.

Privilege segregation

Public-tier consumer chatbots are not privileged, and enterprise tiers with confidentiality terms are different. The April 2026 US v. Heppner analysis shows the line being drawn case by case.

The Anthropic legal demo on April 23, 2026 drew over 20,000 registrants (Florida Bar coverage). The same week, Freshfields announced a firm-wide Claude deployment. That pace of adoption explains why the rule is being written now. Lawyers are using AI faster than the standards to govern that use exist.

Other licensed professions will likely face the same duty

The rule is written for lawyers, but the reasoning carries over to any profession with a competence duty. That includes licensed accountants, financial advisors, medical writers and regulatory affairs consultants. It also includes compliance officers and due-diligence analysts. Here are three ripple effects we predict in the next 6 to 12 months.

State medical and accounting boards will copy the language

The 'competence' duty exists in nearly every professional code, and the verification gap is the same. Expect parallel rules in 2026 and 2027.

Enterprise procurement criteria will shift

Compliance teams at regulated employers will want proof that a vendor can check across vendors before they approve AI workflows. The 'approved AI tools list' at most large firms does not address independent checking today. It will have to.

Insurance pricing will follow the docket

Professional liability insurers price what is in the claims data. The PA, NorCal, GA and CA disciplinary record is now that data. Premiums will reflect verification practice within 12 to 18 months.

For independent professionals, a practical version of the rule already applies. Think freelance journalists, newsletter writers and solo consultants. For them it is a market reality, not a regulatory duty. The cost of an unverified AI claim comes at once, and it lands on your name. The question is the same, and so is the design answer.

Harvey, Legora and Claude draft the work; none checks across vendors by default

How these tools differ was the most-discussed question on r/legaltech this month. The post 'Lawyer here - how are Legora and Harvey differentiated from Claude' hit 49 upvotes and 106 comments (thread). Here is our honest read:

Vertical legal AI tools: Harvey, Legora, Spellbook, Ivo, Wordsmith

They wrap AI models in legal-specific design, integrations, prompt libraries and source citations. They are workflow products. Their checking usually relies on one vendor, often Claude or GPT under the hood.

General-purpose LLM access: Claude, GPT, Gemini Word add-ins

Built into the documents lawyers work in. Cheaper and broader, but with no legal-specific guardrails.

Multi-vendor verification (TrueStandard category)

Adds a layer that checks claims across vendors, whichever tool produced the draft. The check is vendor-neutral by design.

The 'moat' question is the wrong one. The right one is this: which layer of the stack holds the regulator's duty of 'independent verification'? It cannot be the drafting layer, because that layer produces the output. It cannot be a same-vendor self-check, which fails the independence test. It has to be a verification layer that crosses vendors. That layer is not yet a default in Harvey, Legora or Claude, and that is the gap the rule is going to expose.

A documented check across vendors reduces supervisor liability

Look at what the NorCal supervision sanction decided. The court did not punish the junior lawyer who pasted in the AI-fabricated citation. It punished the supervising partner for not having a process that would catch it. We see three working consequences for managing partners and content team leads.

The check has to be in the workflow, not in the lawyer's head

'We trust our associates to check AI output' is no longer a process. A recorded step that leaves a record is. That means a check report or a log of where the models disagreed.

The artifact has to be vendor-independent

A log showing 'Claude was asked to fact-check the Claude draft' proves the absence of independence, not its presence.

The check has to be reproducible

If a regulator asks 'show your work,' the answer needs to be replayable: same input, same model panel, same disagreement output.

Together, these three make the checking step defensible. The answer is no longer that the firm trusted the associate. The supervisor can now say: 'our firm has a documented multi-vendor verification process and the artifact is in the file.'

Notice the pattern. A defensible record is one that is independent of any one vendor, can be repeated, and shows where models disagree. That is what TrueStandard produces. Paste your draft, and four frontier models check it in parallel in 60 seconds. Every disagreement comes back with the model name, version and timestamp logged for the file.

Frequently Asked Questions

When does the California rule take effect?

The proposal was released May 5, 2026 for public comment. Final adoption follows the comment period and Bar approval. New York's Part 161 is already adopted, effective June 1, 2026. Connecticut's proposal is pending.

Does the rule apply to lawyers in other states using AI on California matters?

Which state's ethics rules apply usually turns on two things: where the lawyer is admitted, and where the matter is handled. Multi-state firms usually follow the strictest standard. In practice, if California's rule passes, large firms will adopt it as a default. That spares them separate AI workflows for each state.

What about confidential client data? Can I use a multi-vendor verification tool with privileged content?

Privilege analysis depends on the vendor's terms. Public-tier consumer chatbots usually do not preserve privilege. Enterprise tiers with confidentiality terms are different. The April 2026 US v. Heppner ruling shows public-Claude chats not treated as privileged. TrueStandard's enterprise terms include explicit no-training-on-content commitments, see truestandard.ai/security.

Is there a federal rule equivalent to the California proposal?

Not yet. The Federal Judicial Conference has not issued a verification rule. Individual federal judges have issued standing orders that require disclosure of AI use on filings. For now, the spread of state rules is the working standard. A federal rule may follow within 12 to 24 months.

How does this connect to the Lancet study on fabricated medical references?

The Lancet study (May 7, 2026) audited 2.5M biomedical papers. It recorded a 12-fold rise in fabricated references since 2023. Medical writers, regulatory affairs staff and IRB-reviewing physicians face the same duty, parallel to the one California is writing down for lawyers. Any profession with a competence duty has a verification problem, and the same architecture solves it.

Keep reading

Is AI accurate for your field?

The failure modes change by profession. These break down what AI gets wrong in specific fields, with the incidents and the checks that catch them.

Make Verification Defensible

The California rule asks for a record, not a feeling. TrueStandard runs your draft through four frontier models in 60 seconds. You get a record you can reproduce of where they agree and where they do not.

TrueStandard is for writers who publish AI-assisted drafts. Paid plans check every claim and citation across four AI models before you hit publish.

Free: one check a day, no signup. Pro is $20 a month for 250 drafts.

Start Verifying →