Swap the Facts, Not the Document

Every defense attorney we talk to describes drafting the same way. Pull up the last good motion. Keep the legal sections. Swap in the new facts. File.

We wrote about why the legal sections stay stable. In high-volume practice, the arguments are already correct for the new case. There is nothing to re-reason through.

That is half the reason the copy-paste workflow persists. The other half nobody talks about: the old motion is not just correct text. It is a working Microsoft Word document. And working Word documents are structurally hard to recreate.

The Table of Authorities Problem

Open any motion your firm has filed and look at the Table of Authorities. Every citation in that list is a Word field code, not plain text. The TOA is built by scanning the document for marked citations and pulling them into a generated table.

Paste content from a chatbot into a blank Word doc and the TOA is empty. Not because the citations are wrong (although they definitely could be). It's because none of them are tagged. To rebuild a working TOA, you have to manually mark every citation in the body of the document, then regenerate the table. On a motion with thirty or forty citations, that alone takes longer than the AI saved.

Any attorney who has fought with the Mark Citation dialog knows this. Any attorney who has not is going to find out the first time they try to drop an AI draft into a real motion.

It Is Not Just the TOA

The TOA is the most dramatic example, but it is not the only piece of infrastructure in a filed motion that lives as structure, not text:

• Heading styles that nest correctly for the Table of Contents
• Caption layout with firm-specific conventions (line breaks, spacing, the "X" markers some firms place in the caption block)
• Signature blocks tied to a specific attorney
• Footer pagination and page numbering
• Justification, font, and spacing that match the rest of the firm's filings

None of this comes out of a text model. All of it lives in the existing Word file, encoded as styles, fields, and document properties.

Drafting Is Really Three Jobs

Once you see the Word infrastructure clearly, the job of drafting a motion separates into three distinct pieces:

1. The legal sections. In high-volume practice, these are already correct from the last motion. Do not touch them.
2. The Word infrastructure. The TOA field codes, the heading styles, the caption, the signature block. Already correct from the last motion. Do not touch that either.
3. The facts. Dates, exhibit letters, NYSCEF doc numbers, party names, bill amounts, payment timelines. The only thing that actually changes case to case.

Two of the three jobs were already done by the last motion, for free. The third is the one that scales linearly with caseload, and it is the only piece that actually needs the new case file.

The copy-paste-old-motion workflow has always understood this, implicitly. It is not a shortcut. It is a precise description of what the work actually is.

Why a Chatbot Fails Even If the Writing Is Perfect

A chatbot inverts all three jobs.

It regenerates the legal sections. Dangerous, because now every citation has to be verified, and unnecessary, because the arguments were already right. We have written separately about why that failure mode is really a workflow problem.

It produces plain text. Plain text destroys the Word infrastructure. Paste it into a blank doc and the TOA is empty, the headings are unstyled, the caption is gone. Paste it into your old template and you spend the next hour reconciling whatever structure the chatbot produced against whatever structure your template expected.

And it still does not solve the facts problem. The chatbot does not know which paragraph of which affidavit contains the assignor's date of service. It did not read the exhibits. That work, the only work that actually needed help, is still waiting for you.

Even if the prose is flawless, the reformatting tax wipes out the time savings. This is why the workflow never actually changed.

What About Word Plugins?

There is a second class of tool worth naming directly. Word plugins that put a chat interface inside the document itself and edit the underlying file in place. For certain kinds of work they are genuinely useful.

High-volume motion drafting is not that kind of work, for two reasons.

The first is technical. A Word document, under the hood, is not plain text. It is WordXML, a verbose markup format that encodes every style, field, table cell, and paragraph property as structured tags. Language models have a limited amount of "brainpower" to spend on any given task, and when a model has to read and edit WordXML directly, a big chunk of that "brainpower" goes to parsing the document structure instead of thinking about your motion. The same model that writes cleanly in a regular chat gets noticeably worse the moment it has to work inside a Word file.

The second is workflow. Even if the plugin handled WordXML perfectly, a high-volume attorney is still rewriting the same paragraphs over and over. Every new motion needs the same caption updated, the same preliminary statement rewritten, the same exhibit references swapped. Doing that through a chat, one prompt at a time, with the attorney pointing the model at each section and explaining where the new facts go, is not faster than opening the old motion and using Find and Replace. In many cases it is slower.

Word plugins shine when the document is unique. A new brief on a novel question. A contract being negotiated clause by clause. Anything where the attorney actually needs to reason through the writing with help. That is the opposite of high-volume motion practice, where the writing was already done months ago and the only thing changing is the facts.

What a Tool Would Have to Do

To take "swap out the facts" literally, a tool cannot produce text and hand it to you. It has to produce a Word document that already has your firm's TOA field codes, heading styles, caption, and signature block, because those came from your own filed work, not from a model. The only thing it touches is the facts: pulling them out of the new case file and dropping them into the right paragraphs, referencing the right exhibits, in the right format.

That is what DocketDrafter does. Setup starts from .docx files your firm has actually filed. The TOA fields, heading styles, caption conventions, and signature blocks come straight from those files. When a new case comes in, the system reads the new exhibits, pulls out the facts, and drops them into an already-correct document. The legal sections do not move. The infrastructure does not move. The output is the same Word document your firm would have filed anyway, without the hours of manual assembly and the copy-paste errors that come with it.

And because the only thing the system touches is the facts, we show you exactly what it touched. Every case-specific section in the review screen is highlighted so you can see at a glance which sentences came from the new case file and which are legal boilerplate you have already approved. If something looks wrong, you know exactly where to look.

The Point

"Swap out the facts" is exactly what defense attorneys have been describing for years. It was never the shortcut people assumed it was. It was a precise description of what the job actually is, in a practice area where the arguments do not change and the Word infrastructure does not either.