The Pre-Filing Checklist That Keeps AI-Assisted Briefs Out of the Sanctions Column

A sanctions order, a public reprimand, a mandatory CLE, and a client who now Googles your name and finds a story about fake case citations. That's the going rate for filing a brief with hallucinated authorities, and the docket of lawyers who have paid it keeps growing. Bloomberg Law has been chronicling new sanctions rulings against attorneys who filed AI-generated citations without checking them, and the pace isn't slowing.

The uncomfortable part: most of these sanctions were preventable in about twenty minutes of work. The lawyers who got hit weren't short on database access. They skipped a verification step they already owed the court.

The Signature Is What the Court Punishes

Rule 11 doesn't care which tool drafted your brief. When you sign a filing, you certify to the court that the legal contentions are warranted by existing law and that the factual contentions have evidentiary support. The text of Rule 11 hasn't been amended for the arrival of large language models, and courts have made clear they don't intend to grade AI-assisted work on a curve.

Every sanctioned lawyer in the growing docket signed something they hadn't verified. The model gave them a plausible-looking citation, and they pasted it in. The judge pulled the reporter and found nothing there. Courts punish the signature, not the software.

Why "I'll Just Cite-Check It" Keeps Failing

The obvious fix is the one every firm reaches for first: tell associates to cite-check anything an AI touched. It sounds airtight. In practice it breaks down for the same handful of reasons that show up over and over in the sanctions orders.

• The reviewer trusts the drafter. When a senior partner hands down a draft, the junior assumes the citations were already run. When a junior hands one up, the partner assumes the junior ran them. Nobody pulled the case.
• The hallucination reads like real law. Fabricated citations mimic the format, the reporter, and a plausible year. A skim confirms the shape of the case, not its existence.
• Deadline pressure collapses the check. At 11 p.m. the night before filing, "verify every cite" becomes "spot-check a few and move on." The unchecked ones are the ones that surface at the show-cause hearing.

That's why the same category of mistake keeps surfacing in different courtrooms. The fix isn't "try harder next time." It's a workflow that removes the room for the mistake.

Build the Verification Workflow Into the File, Not the Reviewer's Head

Firms that have absorbed AI into litigation without collecting sanctions treat verification as a documented step in the matter file, with a name attached, before anything gets filed. A workable version has four moving parts:

1. Flag the AI-assisted sections. The drafter marks every passage that came from or was shaped by a model, so the verifier knows exactly what to pull.
2. Pull every cite from a primary source. Each case, statute, and quotation is opened in a live database and matched word-for-word against the brief, not just confirmed to exist.
3. Log the check with a name and a timestamp. A short verification memo in the matter file records who checked what, when, and against which source.
4. Second-signature before filing. A lawyer other than the drafter confirms the verification memo is complete and initials the file.

None of these steps require expensive software. They require someone to own each step and a file that shows they did. That combination is what a Rule 11 inquiry, or a Baker Botts competence analysis under Model Rule 1.1, will actually ask about.

Where the Tooling Earns Its Keep

General consumer chatbots are the wrong instrument for citation work, and the news coverage of what happened when lawyers trusted what happened when lawyers trusted AI output output has been making that point since the first sanction landed. Legal-specific systems that retrieve from a live case database, expose the source document alongside the answer, and log every query into an audit trail give the verifier something concrete to check against. A private deployment inside the firm also keeps client material out of a public model's training pipeline, which is a separate Rule 1.6 problem worth solving before the Rule 11 one bites.

The tool isn't the safeguard; the workflow is. But the right tool makes the workflow cheap enough that associates will actually run it under deadline pressure, which is when the shortcuts happen.

The Signature Is Still Yours

The through-line in every sanctioned brief is the same. A lawyer trusted an output they hadn't verified, signed a document that said they had, and discovered too late that the court reads the signature literally. A verification workflow you can point to, with names and timestamps, is now part of practicing competently. Build it before your next filing, not after your first show-cause order.