Quick test. No peeking.
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 said Rule 6.05, you answered the way most Minnesota litigators of a certain vintage would, and you’ve been carrying a wrong rule for more than six years. Rule 6.05 was abrogated effective January 1, 2020. The mail-service provision lives at Rule 6.01(e) now:
“(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.”
And here’s the part that trips people up: something came along for the ride. The same rule adds a day when service happens after 5:00 p.m. Minnesota time. If you learned “three days for mail” as a stand-alone fact, you never learned that.
The math barely changed. The rule you’d have cited for it hasn’t existed since the first Trump administration.
Why deadlines are different
Deadline calculation is the highest-stakes, least glamorous job in litigation. Nobody has ever gotten a compliment on a deadline calculation. Blow one and you’re in the small club of mistakes that can end a case all by themselves, no matter how good the merits are, and that’s exactly why it’s a leading category of legal malpractice claims.
And it’s especially dangerous to do from memory, for one reason:
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. Once, early, from a supervising lawyer or a CLE or a chart taped inside a file cabinet. Then you used them hundreds of times without a hitch, which built exactly the kind of confidence that keeps you from looking. Nothing in your daily practice tells you a rule moved. Renumbering doesn’t throw an error. The three days are still three days. Only the citation’s wrong, and it’s wrong in a brief a judge may read.
Meanwhile the rules keep moving. Federal and state civil rules have both had major time-computation overhauls in the last fifteen years. Statutes get amended mid-year with new notice periods. Local rules and standing orders pile on top and sometimes override.
Your confidence goes up every year. Your accuracy doesn’t. Nothing in ordinary practice ever forces you to notice.
Now add an AI
All of that was true before anybody had a chatbot. AI makes it a lot worse, and in a very particular way.
Ask a language model to compute a deadline and it’ll do it on the spot, in a confident paragraph, with a rule citation. The citation will look right. A lot of the time it’ll be the old rule, because the old rule shows up 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 going by how often something’s been written down, the abrogated rule wins on volume.
That’s the whole problem 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.
Put that together with a job where the answer often stays the same — three days is still three days — and you get output that’s right on substance, wrong on authority, and delivered with total confidence. This isn’t a hallucination in the Avianca sense. Nobody made up a case. It’s a real rule that just isn’t there anymore.
The rule we run under
The standing instruction in this practice is blunt, and it covers 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 clause that does the work. Certainty is the problem. It doesn’t protect you. The rules you’re most sure of are the ones you learned longest ago, and those are exactly the ones most likely to have been amended since.
Primary source means the current text from whoever issues it: the Revisor of Statutes for Minnesota statutes and court rules, the Judicial Branch for rules and orders, the official code for federal statutes. A treatise doesn’t count. Neither does a CLE handout, a chart, your own old brief, or a summary a model spit out ten minutes ago. Those are all pointers. Check the pointer.
How to actually do it
Six steps, in order. The order matters, because each step can blow up the next one.
1. Pin down the triggering event and its exact date. Not “sometime last week.” The date of service, or filing, or entry, or receipt — and which one the governing rule actually keys on, because those aren’t the same date and rules differ on which one starts the clock.
2. Figure out how it was served. Mail, e-service, personal, or a court’s own order. That decides whether anything gets added, and, as you just saw, whether the time of day matters.
3. Pull the governing rule text. Now, from the source. Before you do any math. Read the current text, subsections and all, including anything on weekends, holidays, and end-of-period. If the rule you expected got renumbered, you’ll find out here instead of in a filing.
4. Look 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 gets built, because they routinely override the general rules on timing, length, and format. A deadline you computed perfectly under the general rule is still wrong if the scheduling order shortened it.
5. Do the math and write down every link in the chain. Trigger date, rule relied on, additions applied, weekend/holiday adjustment, result. The chain is what you’re delivering, not just the date. Nobody can audit a bare date. Somebody else can check a chain in ninety seconds.
6. Put it on the calendar 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 can’t finish step 3 — no network, no access, whatever the reason — the right output isn’t a best guess. It’s a flat refusal that says so: unverified, rule text not retrieved. An honest gap becomes a task on somebody’s list. A confident wrong date is a missed deadline with a paper trail that makes it look like somebody checked.
Two habits that catch the rest
Recompute from scratch instead of 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 math is close to useless. You’ll follow their reasoning and nod along. Computing it fresh catches the shared assumption, and that’s the thing that actually goes wrong.
Treat a renumbered rule like a fire. If you find out a rule you’ve been citing has moved, don’t just fix the document in front of you. Search your templates. The old citation is almost certainly sitting in a form file, a checklist, or a brief bank, waiting to get reused. That’s how a stale rule hangs on for six years. Nobody decided to keep citing it. It got frozen into a template nobody re-reads.
The bigger lesson
This goes well past deadlines, and it’s the idea behind most of what shows up in this section.
An AI assistant is terrific at finding, reading, comparing, and applying a rule you hand it. It’s unreliable at remembering one. Those are two different jobs and they break in different ways. You don’t fix that by ditching the tool. You set up the work so the tool is always doing the first job and never the second.
In practice, the workflow fetches before it reasons, every time, even when it’s confident — especially when it’s confident. “I could not retrieve the rule” is an acceptable answer. “I recall the rule provides” isn’t. And the burden of proof runs the right way: 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 are true at once, and that’s the whole trap.
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.