Friday, 17:55: The Court Deadline Nobody Had Docketed

Friday, 17:55

Miriam has been a legal assistant at the firm for eleven years, and she has a habit nobody asked her for. On Friday evenings, before she logs off, she opens the beA messages of the past three weeks in RA-MICRO and scrolls. Not the unread ones. The read ones, the ones already filed and marked done.

The firm is invented for this story: sixteen lawyers in Leipzig, mostly commercial and construction litigation, a few hundred live matters, and every piece of court mail arriving through beA, the electronic mailbox every German lawyer has. The way the order goes missing is not invented.

At 17:55 she stops at a message from the Landgericht Leipzig in a construction dispute. It has two attachments: the plaintiff's 22-page brief, and behind it a two-page order from the court. The message is filed as "Schriftsatz Gegenseite z. K.", the other side's brief, for information. There is no deadline in the calendar.

She opens the order. In its second paragraph the court gives the defendant, their client, the chance to respond to the brief binnen drei Wochen, within three weeks of service. The acknowledgment of receipt was submitted on a Monday, and the three weeks run from that day. The period ends this coming Monday.

She calls Jonas, the associate responsible for the matter. He is at his daughter's handball match and picks up on the fourth ring. Then she calls Katrin, the partner. Jonas spends Saturday and most of Sunday on a response to 22 pages, and it goes out through beA on Monday afternoon. The client never hears about it.

That is the good version. It is good because one person scrolls through filed mail on Friday evenings out of habit, and Katrin knows that is not a system.

Three weeks back: one message, two files

When Katrin tells me the story on a video call the following week, she does not start with the calendar. She shares her screen and walks the message backwards, and each document looks harmless on its own.

The message. It arrives on a Thursday at 16:12, one of about thirty that day. Lena, who is covering for a colleague on holiday, opens it, sees 22 pages of the other side's arguments, and files it the way such briefs are filed. The order is the second PDF. She never opens it, because nothing in the message says that it matters more than the brief.

The acknowledgment. On Monday morning Jonas submits the acknowledgments of receipt that have piled up, fourteen of them, from a list that shows the court, the reference and a subject line. Submitting one sets the date of service, and it is his own declaration, exactly as it should be. The list does not show what is inside.

The calendar. Every evening a lawyer checks the day's new deadline entries against the documents behind them. The firm does this properly. But the check only covers what was typed.

That is the whole failure, and Katrin has already seen it before I say it: the four-eyes principle checks entries. It has nothing to say about an entry that was never made. The weak point is not the counting of days. It is the reading.

Open the order, not the calendar

So I ask her to open the order again and leave it on screen while we talk. Then I ask how much court mail comes in (around 150 documents a week), how RA-MICRO gets it (it fetches beA with the firm's own credentials), and whether they use its deadline calculator. They do, and it counts correctly.

That answer settles the scope. If counting days were the problem, Katrin would not need me, because she already pays for software that counts. What the firm lacks is a reader in front of the calculator: something that opens every document the day it arrives, notices that a two-page order sets a period, and puts that period in front of the right lawyer with the sentence it came from.

And I tell her the one rule I will not bend, before she asks: the model never sets a date. Language models misread dates, and now and then they invent them. In a docketing system that is not a quality problem. It is a malpractice problem. So the model reads, ordinary code counts, and a lawyer decides. Every step of the build belongs to exactly one of those three.

Read by a model, counted by code, confirmed by Jonas

The workflow picks up each beA message after RA-MICRO has fetched it; it never logs into beA itself. The model classifies every document in the message (judgment, order, hearing notice, forwarded brief) and extracts the court, the reference, the parties and every period or date the court sets, each with its source sentence. Periods come back as written, as "drei Wochen", never as a date. The extraction is a list, not a single field, because one order can set a period, schedule a hearing and ask for a document at once.

Everything after that is code. Here is the order Lena filed, as the workflow would handle it:

Two decisions in that table carry most of the safety. The provisional date counts from the day of receipt, which can only be earlier than the real one, so any error falls on the early side. And holidays come from the court's location, not the firm's. The full design, including the flow and the six ways a system like this gets a deadline wrong, is in the blueprint for court deadline docketing.

A year of court mail, run again

Nothing goes live on Katrin's word or mine. The first real test is a replay: a year of the firm's past beA messages runs through the reading and the rules, in date order, and every computed deadline is compared with what the firm actually entered. The rule for the replay is simple. Every difference gets an explanation, and each explanation is one of two things: a rule I fix, or an entry in the old calendar that was wrong.

The replay finds the Leipzig order on the day it arrived. It also finds two things nobody expected.

The first is in the old calendar. In a matter before the Landgericht Berlin, a period ended on the Day of Prayer and Repentance, the Wednesday in November that is a public holiday in Saxony and in no other state. Someone in the Leipzig office shifted the entry to Thursday, because for them it was a holiday. Before a Berlin court it is an ordinary working day, so the calendar was a day late. The brief happened to go out on the Tuesday, and nobody ever knew. The rules module applies the holidays at the court's location, and the difference shows up on the first run.

The second is mine. My first matching rule paired the court and the reference. In the replay, text recognition misreads one digit on a scanned order, and the misread reference belongs to an old, closed matter at the same court against the same property developer. The firm acts for several subcontractors against that developer, so the developer's name agreeing proves nothing. From then on, a document matches only an open matter, and only if the court, the reference and the client's own name all agree. Anything short of one clean match goes to a legal assistant with nothing entered. A deadline filed in the wrong matter is a deadline missed in the right one.

Then comes a parallel run: for several weeks the workflow computes live court mail into a separate log while the assistants docket by hand, and the differences are reviewed every morning. Only then do proposals appear in RA-MICRO. The replay is an evaluation set in the sense of the LLM evaluation guide, with the firm's own court mail as the test data.

What only a lawyer can click

The workflow proposes. It never confirms, and a few things it never touches.

• The acknowledgment of receipt stays Jonas's. It is his declaration of when the document was served, so the workflow reads the date from it and never submits one.
• Each entry is confirmed on its own. If an order sets a period and a hearing, Jonas confirms two entries. Confirming one never quietly confirms the other.
• Extensions and moved hearings go to a person. A new order supersedes the old entry instead of adding a second one, with the history kept. Deadline types that cannot be extended at all, the Notfristen, are marked as such in the rules table, so nobody treats an extension request as a safety net for them.
• Unconfirmed means unconfirmed. A proposal nobody has confirmed by the firm's set time escalates to the deputy and to Sabine, the office manager. A court document left unprocessed for an hour raises an alert of its own, because a pipeline that fails silently is worse than none.
• The rules belong to Katrin. The table of deadline types and the holiday calendar are owned by a named partner, changed only through review, and every change runs against the replay before it goes live.

Every deadline keeps its trail: the document, the sentence, the trigger, each step of the computation, and who confirmed it and when. If the firm's deadline control is ever questioned, that trail is the answer. And if the partners will not send client documents to an external model, the reading runs on a private model hosted in the EU and nothing else in the design changes.

Another Friday, 17:55

Lena still files briefs for information, and she is still right to. But the two-page order behind the brief no longer depends on anyone opening it: on the Thursday it arrives, Jonas has a proposal waiting in RA-MICRO with the court's sentence beside it, marked provisional until he submits the acknowledgment. The evening check now covers what the court sent, not only what someone typed.

Miriam still scrolls on Friday evenings. What she scrolls is shorter: the documents the workflow could not match, the types it does not know, and the proposals someone corrected that week, each of which becomes a new test case. Her habit has become the exceptions queue, which is where eleven years of judgment belongs.

Before your firm builds anything

If your bottleneck is counting days, use what you already pay for. RA-MICRO, Advoware and DATEV Anwalt all include deadline calculators and beA integration, and in the US, rules engines such as CompuLaw compute deadlines from court rule sets. A build earns its cost where the reading is the bottleneck: a high volume of court mail, several practice areas with their own deadline types, or offices on different systems that no single vendor covers.

For one jurisdiction, the main document types and one case system, it usually fits the multi-step tier of AI workflow automation, replay included. The full blueprint has the flow, the failure modes and the rollout stages, and the reasoning behind who confirms what is in human-in-the-loop design.

Frequently asked questions