Here is a small test. No looking.
Opposing counsel serves a motion on you by U.S. Mail. You get an extra three days. Which Minnesota rule gives you those three days?
If you answered Rule 6.05, you answered the way most Minnesota litigators of a certain vintage would, and you have been carrying a wrong rule for more than six years. Rule 6.05 was abrogated effective January 1, 2020. The mail-service provision now lives at Rule 6.01(e):
“(e) Additional Time After Service by Mail or Service Late in Day. Whenever a party has the right or is required to do some act or take some proceedings within a prescribed period after the service of a notice or other document upon the party, and the notice or document is served upon the party by United States Mail, 3 days shall be added to the prescribed period.”
Note also what came along with the relocation, which is the part that catches people: the same rule adds a day when service is accomplished after 5:00 p.m. Minnesota time. If you learned “three days for mail” as a self-contained fact, you did not learn that.
The answer to the arithmetic barely changed. The rule you would have cited for it has not existed since the first Trump administration.
Why this particular task is different
Deadline calculation is the highest-consequence, lowest-glamour task in litigation. Nobody has ever been complimented on a deadline calculation. Getting one wrong is among the small set of errors that can end a case on its own, without any reference to the merits, and it is a leading category of legal malpractice claims for exactly that reason.
It also has a property that makes it uniquely dangerous to do from memory:
Deadline rules are the most frequently amended rules a litigator touches, and the ones a litigator is least likely to re-read.
Think about how you learned them. You learned them once, early, from a supervising lawyer or a CLE or a chart taped inside a file cabinet. You then used them hundreds of times without incident, which built exactly the confidence that stops you from looking. Nothing in your daily practice ever tells you a rule has moved. Renumbering does not throw an error. The three days are still three days; only the citation is wrong, and the citation is wrong in a brief that a judge may read.
Meanwhile the rules do move. Federal and state civil rules have both been through significant time-computation overhauls in the last fifteen years. Statutes get amended mid-year with new notice periods. Local rules and standing orders layer on top and sometimes override.
The confidence curve and the accuracy curve go in opposite directions, and nothing in ordinary practice makes them cross.
Now add an AI to it
Everything above was true before anybody had a chatbot. The technology makes it substantially worse, in a specific way.
Ask a language model to compute a deadline and it will do it, immediately, in a confident paragraph, with a rule citation. That citation will be well-formed. It will frequently be the old rule — because the old rule appears in far more text than the new one. Decades of briefs, treatises, CLE outlines, and blog posts cite Rule 6.05. Six years of material cite 6.01(e). If a model is drawing on how often a thing has been written, the abrogated rule wins on volume.
That is the whole failure mode in one sentence: a model’s fluency reflects how much has been written about a rule, not whether the rule is currently in force. Amendments are, by definition, underrepresented in everything written before them.
Combine that with a task where the answer often does not change — three days is still three days — and you get output that is right in substance, wrong in authority, and delivered with total assurance. It is not a hallucination in the Avianca sense. There is no fabricated case. There is a real rule that is no longer there.
The rule we run under
The standing instruction in this practice is blunt and it applies to every person and every system:
Never state a rule, statute, or deadline from memory. Fetch the current text from the primary source first — every time, including for rules you are certain about.
“Including for rules you are certain about” is the operative clause. Certainty is the failure mode, not the safeguard. The rules a lawyer is most confident about are the ones learned longest ago, which is precisely the population most likely to have been amended since.
Primary source means the issuing authority’s current text: the Revisor of Statutes for Minnesota statutes and court rules, the Judicial Branch for rules and orders, the official code for federal statutes. It does not mean a treatise, a CLE handout, a chart, a prior brief of your own, or a summary a model produced ten minutes ago. Those are all pointers. Verify the pointer.
The workflow
Six steps, in order, and the order matters because each one can invalidate the next.
1. Identify the triggering event and its exact date. Not “sometime last week.” The date of service, or filing, or entry, or receipt — and which of those the governing rule actually keys on, because they are not the same date and rules differ on which one starts the clock.
2. Identify how the deadline was served. Mail, e-service, personal, or a court’s own order. This determines whether anything gets added, and — see above — whether the time of day matters.
3. Fetch the governing rule text. Now, from the source. Before any arithmetic. Read the current text, including its subsections, including anything about weekends, holidays, and end-of-period. If the rule you expected has been renumbered, you will discover it here rather than in a filing.
4. Check for anything that overrides it. A scheduling order, a standing order, or the assigned judge’s own practice pointers. In this office the judge’s standing orders get pulled before any motion package is built, because they routinely override the general rules on timing, length, and format. A correctly computed deadline under the general rule is still wrong if the scheduling order shortened it.
5. Compute, and write down the chain. Trigger date, rule relied on, additions applied, weekend/holiday adjustment, result. The chain is the deliverable, not just the date. A bare date cannot be audited; a chain can be checked by somebody else in ninety seconds.
6. Calendar it where deadlines actually live, with the chain in the entry. Not in a note, not in the knowledge base, not in a chat log. The calendar of record.
If a system cannot complete step 3 — no network, no access, whatever the reason — the correct output is not a best guess. It is a refusal that says so: unverified, rule text not retrieved. An honest gap is a task on somebody’s list. A confident wrong date is a missed deadline with a paper trail suggesting somebody checked.
Two habits that catch the rest
Recompute independently rather than reviewing. When a deadline matters, have a second person or a second session compute it from the trigger date without seeing the first answer, then compare. Reviewing somebody’s arithmetic is nearly useless — you will follow their reasoning and agree with it. Independent computation catches the shared assumption, which is the thing that actually goes wrong.
Treat a renumbered rule as a live incident. If you discover that a rule you have been citing has moved, do not just fix the current document. Search your templates. The old citation is almost certainly sitting in a form file, a checklist, or a brief bank, quietly waiting to be reused. That is how a stale rule survives for six years: not because anyone chose to keep citing it, but because it was frozen into a template nobody re-reads.
The general form
There is a version of this that goes beyond deadlines, and it is the operating principle behind most of what appears in this section.
An AI assistant is extraordinarily good at retrieving, reading, comparing, and applying a rule you hand it. It is unreliable at remembering one. Those are different operations and they fail differently. The design response is not to avoid the tool; it is to arrange the work so the tool is always doing the first thing and never the second.
In practice that means the workflow fetches before it reasons, always, even when it is confident — especially when it is confident. It means “I could not retrieve the rule” is an acceptable answer and “I recall the rule provides” is not. And it means the burden of proof runs the right direction: a rule is unverified until this session has read it.
Three days is still three days. Rule 6.05 has been gone since 2020. Both things being true at once is exactly the shape of the problem.
Sources
- Minn. R. Civ. P. 6.01 (subsection (e), additional time after service by mail or service late in day); Rule 6.05 abrogated effective January 1, 2020
- Minnesota Rules of Civil Procedure, Revisor of Statutes
The rule text above was retrieved from the Revisor of Statutes for this article rather than cited from memory. This is general commentary on practice management and is not legal advice; deadlines in any actual matter depend on facts, forum, and orders specific to that case.