Litigation Docketing: Court Deadlines That Hold Up Through Stays and Extension Orders

Every court order moves a date, and the dates live in four places

A docketing cycle looks tidy on paper. Each entry on the docket list has a trigger date, the deadline policy says how many court days follow it, weekends and court holidays drop out of the count, and a stayed matter holds its deadlines until the court says otherwise. Applying that to forty entries is careful work. Keeping it right while new orders keep arriving is the hard part.

The docket list sits in SharePoint, court orders land in the docketing mailbox in Outlook, hearings and deadline confirmations live on Google Calendar, and the court-day rules are a document in Google Drive. Courtroom clerks' scheduling threads come in through Gmail. When a stay is entered or a local rule changes a day count, a docket clerk re-derives dates by hand and edits events one at a time, and an old date can survive on an attorney's calendar for weeks.

Who works in the room

The docketing office keeps one Kylon room, and Ada is its default agent, so a message about a deadline or a new order reaches Ada without anyone naming it. A question about the draft log goes to Myco, because checking the log is its specialty. When Ada finishes a set of dispositions, it opens a thread for Fin whose first message lists the held entries and the clerk threads they answer. Ada reads Outlook and SharePoint through a lasting grant the docketing manager approved for this room, while Fin drafts in Gmail as the clerk it is working for, checked on every call.

From first pass to close-out

The deadline policy, the court holiday list and the order in which log codes apply sit in a Google Drive folder and in the room guidelines, so every agent counts days the same way. Each stage ends with a person.

Orders that move the count

Mid-cycle changes arrive as documents and messages, not clean data. An attorney posts in Slack that the judge lifted the stay from the bench this morning, hours before the written order reaches Outlook. Ada treats the written order as the source, marks the affected entries for review until it lands, then writes a short note on each SharePoint row saying which order moved it. The run history keeps every step, so the question of why a hearing left the calendar always has an answer.

A revised day count is the change most likely to leave something stale. The team's convention is to delete the old confirmation and create a new one rather than edit it, so every attendee receives the corrected date as a fresh invitation and nobody keeps the old one. Only entries the revision touches are recomputed, and the thread shows each old date beside the new one. A daily automation has Ada look for entries within five court days of their deadline that still lack a confirmation and post them in the room.

What the checks catch

• An entry handled by another docketing office, or one that never made the docket list, coded out of scope before anyone asks whether it is a duplicate
• The same order received twice, once from the court's electronic notice and once as a courtesy copy, coded duplicate only after the scope check
• A deadline counted in calendar days where the rule says court days, or one that lands on a court holiday
• A confirmation from before the rule-day revision still sitting on an attorney's calendar next to the corrected one
• A clerk thread with two draft replies, or a reply that names the wrong entry

What stays with people

• Approving every computed deadline before it is placed on a calendar
• Sending each reply to a court clerk, which Fin prepares as a draft in Gmail
• Reading a stay, lift or extension order whose scope is unclear
• Signing the close-out for the cycle

Integrations in this workflow

Kylon is not a docketing system and does not replace one. It works across the lists, mailboxes and calendars the docketing office already runs, and keeps the handoffs between them in one place.

• Gmail
• Google Calendar
• Google Drive
• Outlook
• SharePoint
• Slack

• SharePoint holds the docket list, with each entry's matter, docketing office, trigger date and log code
• Outlook is the docketing mailbox where court orders arrive, including stays, lifts and extensions
• Google Calendar carries hearings and every approved deadline confirmation
• Gmail holds the court clerk threads, and each reply goes out as a draft a docket clerk sends
• Google Drive keeps the deadline policy, the court holiday list and the clerks' draft log
• Slack is where attorneys and paralegals post what happened in court before the written order arrives

Where to start

Pick one docketing office and one month of entries. Connect the SharePoint list that holds the docket, give the room a lasting grant on the Outlook mailbox where orders land, and write the rule that matters most in the room guidelines: an agent may compute and propose deadlines, and the docketing manager approves every date before it reaches a calendar.

“The court still sets the dates. The room makes sure each order moves only the entries it names, and that the old date leaves the calendar when the new one arrives.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.