--- title: "Litigation Docket Deadline Management With AI Agents | Kylon" description: "How a docketing team computes court-day deadlines, absorbs stays, lifts and extension orders, and keeps calendars current in one Kylon room, with every date approved." url: "https://kylon.io/use-cases/litigation-docket-deadlines" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Litigation Docketing: Court Deadlines That Hold Up Through Stays and Extension Orders Use Case8 min read # Litigation Docketing: Court Deadlines That Hold Up Through Stays and Extension Orders Docket entries, court-day deadlines, calendar confirmations and clerk replies run through one Kylon room. Agents work the SharePoint docket list and the court orders in Outlook, and the docketing manager approves every date before it reaches a calendar. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## 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 People - Docketing manager Owns the deadline policy, approves every computed date before it reaches a calendar and signs the cycle close-out - Docket clerks Keep the draft log, watch for new court notices and send each reply to a court clerk once it reads right - Responsible attorneys Confirm how a stay, lift or extension order applies to their matters when the wording leaves room for doubt Agents - AdaDeadline coordinator Reads every entry on the docket list, applies the deadline policy and the court-day count, proposes each disposition and log code, and creates calendar confirmations once they are approved SharePointOutlookGoogle CalendarGoogle Drive - MycoLog reviewer Checks the clerks' draft log line by line against the approved dispositions and lists every code, date or scope call that disagrees Google DriveSharePoint - FinClerk correspondence Drafts exactly one reply per court clerk thread naming the held entry, and posts approved calendar changes for the matter teams [Gmail](https://kylon.io/integrations/gmail) [Slack](https://kylon.io/integrations/slack) 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. ```mermaid flowchart TD first["Ada checks scope, then proposes a
log code and court-day deadline"] ok1["Docketing manager approves
before any confirmation is created"] cal["Ada puts approved deadlines
on Google Calendar"] reply["Fin drafts one reply per clerk
thread, naming the held entry"] send["Docket clerk sends each reply"] log["Myco checks the clerks' draft log
against the approved dispositions"] fixlog["Docket clerk corrects the log,
docketing manager confirms"] rule["Ada recomputes affected deadlines
and recreates stale confirmations"] orders["Ada re-derives the entries it moves
and notes the order on each row"] okrule["Docketing manager approves each
deletion and each new event"] attorney["Responsible attorney confirms,
docketing manager approves"] close["Ada counts by log code and matter
from the list as it stands"] sign["Docketing manager signs the close-out"] first --> ok1 --> cal & reply reply --> send cal & send --> log log --> fixlog fixlog -->|revised count| rule fixlog -->|court order| orders rule --> okrule --> close orders --> attorney --> close close --> sign class first,cal,reply,log,rule,orders,close agent class ok1,send,fixlog,okrule,attorney,sign person classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | First pass | Each entry is checked for scope first, then given a log code and a court-day deadline in the policy's order | Ada, from the SharePoint list, the Outlook orders and the hearing calendar | The docketing manager approves before any confirmation is created | | Confirmations and clerk replies | Approved deadlines go on Google Calendar, and each clerk thread gets one reply naming the entry being held | Ada for the calendar, Fin for the replies | A docket clerk sends each reply | | Draft log review | The clerks' draft log is compared with the approved dispositions, code by code and date by date | Myco | The clerk corrects the log and the manager confirms | | Rule-day revision | Deadlines counted under the old day count are recomputed, and each stale confirmation is deleted and created again with the corrected date | Ada | The docketing manager approves each deletion and each new event | | Stay lifted | Held entries in the matter are re-derived from the date of the lift order | Ada, then Fin for the clerk replies | The responsible attorney confirms how the order reads | | Extension orders | Only the entries each order names move, with a note on the row citing the order | Ada | The docketing manager approves the new dates | | Close-out | Counts by log code and by matter are taken from the SharePoint list as it stands | Ada, checked by Myco | The docketing manager signs the close-out | Stages of a docketing cycle. Matters, entries and dates in this example are illustrative. ## 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](https://kylon.io/integrations/gmail) - Google Calendar - Google Drive - Outlook - SharePoint - [Slack](https://kylon.io/integrations/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. Set-up prompt Set up our litigation docketing desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Gmail, Google Calendar, Google Drive, Outlook, SharePoint and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the docketing manager, the docket clerks who send each court clerk reply, and the responsible attorneys who read unclear stay and extension orders. Help me invite them to this Room. 3. Build a Docket Desk App with Entry, Matter, Deadline and Status, one record per entry. Fill it from the SharePoint docket list and the orders in the Outlook mailbox. 4. Check each entry for scope first, then apply our deadline policy and court-day count from Google Drive and the hearing calendar in Google Calendar. Propose a log code and deadline for each. List every entry that fails a check, lands on a court holiday, or still carries a stale confirmation beside a corrected one. 5. Draft one calendar confirmation per approved deadline and one reply per clerk thread in Gmail naming the held entry. The docketing manager approves every computed date before it reaches a calendar. A docket clerk sends each reply. 6. Write our rules and who approves what into this Room's guideline so every entry follows the same path. 7. After one clean cycle, offer to turn the daily check for unconfirmed entries within the threshold we set into an Automation. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Records Retention: A Disposition Cycle Where Every Date Traces to Its Source Each quarter, every in-scope Box record is dispositioned against the retention schedule, its classification, open legal holds and its own closure date in one Kylon room. Agents walk the records and check the certificate, and the records desk lead approves each write. Legal & IPCompliance & risk ](https://kylon.io/use-cases/records-retention)[ ### Brand Abuse Takedowns: Lookalike Domains and Fake Accounts Handled by Policy Reports of lookalike domains and impersonating accounts are classified under the takedown policy in one Kylon room, using evidence from X and LinkedIn. Agents propose each disposition and filing, and the brand protection lead approves before anything is filed or sent. Legal & IPCompliance & risk ](https://kylon.io/use-cases/brand-abuse-takedowns)