Ask a firm where its institutional knowledge lives and you’ll hear about people, experience, and judgment.
It lives in the form file.
Everything a firm has figured out about doing a thing right (which certificate the court wants, how the caption is laid out, which paragraph the insurer always fights over, what has to be in the signature block) is baked into the documents it copies the next time it does that thing. Not in a manual. In Motion to Compel - FORM.docx, last seriously looked at by somebody who’s since retired.
That cuts two ways, one good and one bad, and AI sharpens both.
Bad news first: templates copy mistakes perfectly
A mistake in a template doesn’t happen once. It happens every time anybody uses that template, quietly, until somebody catches it. And the whole point of a template is that nobody reads it closely, because reading it closely is the work it’s there to save you.
I’ve written elsewhere in this section about finding out that a Minnesota rule I’d cited for years had been abrogated in 2020 and its text moved. Finding out wasn’t the interesting part. What came next was: the old cite was sitting in a form file. It had been reused, correctly, dozens of times. Correctly in the sense that everybody faithfully copied what the template said. Which was wrong.
That’s the problem in a nutshell. Templates are where stale law goes to hide. A rule changes, everybody else catches up, and the template doesn’t, because nobody’s in charge of keeping a template up to date. Everybody’s in charge of copying it.
The usual suspects, roughly in order of how often I’ve found them:
- Rule and statute citations that have been renumbered, amended, or abrogated.
- Dollar thresholds (jurisdictional amounts, filing fees, statutory caps, exemption figures) that move, and that somebody typed in once.
- Deadline recitals that spell out a fixed number of days in the body of the document, and now contradict the actual current rule.
- Court names, division names, and addresses after a reorganization.
- The firm’s own name, entity type, address, and bar information, in every signature block, after any change.
- Formatting requirements (spacing, font, margins, certificate language) after a local rule amendment.
You’ll never spot any of those in ordinary use, because the document looks right. It’s always looked right.
Now the good news: a template is a spec a machine can read
Here’s the flip side.
A well-kept template is the single most valuable thing you can hand an AI assistant, because it’s a spec for getting it right that the model doesn’t have to guess at. Everything the firm knows about the right form of this document is already in there.
That gets me to the most important working rule I have on this subject, and it took an embarrassing number of bad outputs to learn:
Generation must populate the template. It must never rebuild the document.
Ask a model to “draft a motion to compel formatted for Hennepin County District Court” and you’ll get something that looks like one. The caption will look about right. The spacing will be close. The certificate will be close, and in a filing, close means wrong.
Hand it the firm’s actual template file, tell it to copy that file and fill in the fields, and that whole family of formatting errors goes away. The model didn’t get smarter. You just gave it the right answer instead of asking it to rebuild one. Now its job is filling in the parties, the facts, and the argument, which is what it’s good at.
This goes way beyond documents: if a correct version already exists, hand it over. Don’t ask a language model to rebuild it from memory. It’s the same rule as never citing a case from memory and never figuring a deadline from memory. This time it’s about form.
Keeping the form file clean
If the form file is your knowledge base, treat it like one.
1. Give every template an owner and a review date. Put both in the document: a footer field or a comment block on the first page saying who owns it and when it was last checked. A template nobody owns is a template nobody updates.
2. Review on a calendar, not when something blows up. Annually is plenty for most of them. And the review isn’t “does this look right” — it’s this: pull the current text of every rule and statute cited, confirm every dollar figure, confirm what the court currently requires, confirm the firm’s own information.
3. Keep them in version control, or at least in dated versions. You want to be able to answer “what did this template say when we filed that motion in March.” When you find a defect, that question tells you how big the problem is.
4. When you find one defect, go look for its brothers and sisters. This is the step people skip, and it’s the one that matters. A bad cite in one template is almost certainly in three others, plus a checklist, plus a brief bank. Fixing the one in front of you fixes one document. Searching fixes the pattern.
5. Once a year, run the whole set for citations, by machine. Pull every rule and statute cite out of every template, then check each one against the primary source. This is exactly what automation is for: it’s mechanical, it’s boring, it’s the kind of thing people skip, and when you skip it nothing tells you. Run the same four-pass routine you’d run on a brief.
6. Clean out placeholders properly. This one bites people over and over. Template placeholders are often colored or highlighted so you can see them while you draft. When a script fills them in instead of a person, the text changes and the formatting doesn’t, and out goes a document with the client’s name in red. Reset the character formatting when you fill it in, then render the final document and look at it before it goes anywhere.
The audit that tells you what you didn’t know
Here’s an exercise worth doing once. It reliably turns something up.
Take every template in the firm. Pull out every citation, every dollar figure, and every stated deadline. Put them in one table next to the template each came from. Then check each one against the current primary source.
You get two things out of it. The first is a list of defects to fix. The second is the interesting one: a map of what your firm believes. Every rule your templates lean on, in one list, is a surprisingly clear picture of the law your practice runs on, and of which parts of it nobody’s checked in a decade.
The first time I did a version of this, the real finding wasn’t any one error. It was how many of the cites traced back to the same handful of source documents, copied forward for years. The firm’s knowledge base was resting on a lot less than its output made it look like.
How this ties together
Three ideas from elsewhere in this section all land here, which is why I think templates are underrated.
Don’t rebuild from memory what you can just go get. Cases, rules, deadlines, and now form. One rule, four places to use it.
Hand over the structure and the errors never happen. The formatting specialist in our chain is told to copy the template file and fill it in, and never to rebuild a caption from scratch. That instruction is there because the other way produced a document that looked right and wasn’t.
When an error keeps coming back, fix where it lives. A bad cite caught in a brief is a save. The same bad cite caught in the template it came from is a fix. Always ask where the error was stored.
A firm’s forms are the documents it uses most and looks at least. Treat them like a knowledge base, not a drawer of old files. It isn’t glamorous. It’s cheap, and it’s one of the best hours you’ll spend.
General commentary on practice management. Not legal advice. No client document is described; all examples are invented. On verifying rules and citations against primary sources rather than from memory, see the related pieces in this section.