A court deadline rarely just stops mattering quietly. It gets vacated by an order. It gets continued to a new date. The case settles. Or, occasionally, the AI extracted something the LAA judges to be wrong. Each of these is a different event with a different consequence, and a docketing system that lumps them together — or worse, deletes the row and pretends nothing happened — leaves the firm with no defensible record of why a date that used to be live isn’t live anymore.
DockItFlo treats every retirement as a first-class action with its own visual treatment, audit chain, and calendar consequence. The Removed Dates table on the Review Queue is the single place where every retired deadline lives, and a glance at the row tells the LAA what happened. This article walks through the four ways a deadline is retired, what each one does to the firm’s data and to the attorney’s connected calendar, and why the distinctions matter day-to-day.
Four reasons a deadline is retired
From the LAA’s perspective, every retired deadline falls into one of four buckets. Each bucket has its own pill, its own row treatment, and its own downstream behavior on the connected calendar.
The first three states all carry a strikethrough because the underlying event no longer matters — either it was cancelled by the court, replaced by a new event, or rendered moot by the case closing. The fourth state has no strikethrough because, in the LAA’s judgment, the event never existed to begin with: the AI made an extraction error and pulled a date out of the notice that didn’t belong on a calendar at all.
The split also matters for the attorney’s connected calendar. The first three states (vacated, superseded, case-closed) cover events that were already pushed to the lawyer’s Outlook or Google Calendar; DockItFlo updates those events in place with a strikethrough body and a [VACATED] or [CHANGED] title prefix so they stay visible but unambiguously marked off-calendar. The fourth state — AI-error rejections — is different: the LAA caught the bad extraction during review, so it never reached the connected calendar to begin with. Nothing needs to be updated externally; the audit trail in DockItFlo is the only record.
1. Vacated by court order
A vacate happens when the court explicitly cancels a previously calendared event — a hearing taken off calendar, a deadline stricken, an order set aside. DockItFlo’s AI agent detects vacate language in incoming notices, flags the affected event with a red Vacated pill, and routes it to the review queue with a single Confirm Vacate action. On confirmation, the original event stays in the database with a supersession pointer to the vacating notice, and the activity log captures the full chain: original notice, vacating notice, who confirmed, when.
For the deeper walkthrough of detection and the review modal, see When a court vacates a deadline: how DockItFlo handles vacated dates.
2. Changed to a new date
A date change happens when the court issues an order continuing or resetting a previously calendared event to a new date. The AI agent flags the new notice as a date change candidate, and the LAA reviews the old and new dates side by side. Confirming the change supersedes the prior deadline; choosing “Confirm Separate Deadlines” instead keeps both events on the calendar as independent items.
When supersession is confirmed, the prior deadline appears in the Removed Dates table with a strikethrough and a Superseded pill, and the new deadline becomes the live obligation. The lawyer’s connected calendar gets two updates: the original event is marked in place with a [CHANGED] prefix and strikethrough, and the new event is added at the new date. For the full walkthrough of detection, the side-by-side review modal, and the cross-checking flow against the original notice, see When a court moves a deadline: how DockItFlo handles docket date changes.
3. Case settled or dismissed
When a firm administrator marks a case as Settled or Dismissed in DockItFlo, every pending deadline on that case is automatically retired. This is a deliberate cascade designed to clear the live deadline list of work that no longer needs attention — once a case is resolved, the open hearings and discovery deadlines on that case are usually moot, and treating them as live invites confusion or wasted attorney time.
The cascade is silent on confirmed events that have already happened, and respects MDL relationships: if the parent case in a consolidation settles, the cascade fans out to every consolidated child case’s pending deadlines as well. Each rejected row appears in the Removed Dates table with a slate-tinted strikethrough and a Case settled or Case dismissed pill, so the LAA can tell at a glance that these came off the calendar because the case closed, not because the AI was wrong or the court vacated something.
The case status itself is preserved, and a status banner renders across the docket inbox, the Case Master tab, and the case detail surfaces. Any new ECF notice arriving on a settled case still flows in normally and is held for review — the cascade applies only to deadlines that were pending when the status changed. This matters for the post-settlement filings (notice of attorney’s fees, lodestar verification deadlines, motion to enforce settlement) that often arrive in the weeks after a case closes.
4. Rejected by the LAA as an AI error
Occasionally the AI extracts a date that doesn’t belong on a calendar at all — a date inside a quoted email signature, a hypothetical example in a brief, a reference date that the AI mistakenly classified as a deadline. The LAA can remove these directly from the review queue with a single click; the row drops into the Removed Dates table with no strikethrough and a gray Rejected (AI error) pill.
The lack of a strikethrough is intentional. A strikethrough implies an event that used to exist and no longer does — appropriate for vacated or superseded deadlines. AI errors are different: there was never a real deadline to strike through. The plain-text row with a clear pill keeps the LAA’s mental model clean and the audit trail honest.
Every removal logs an entry on the source notice (who removed, when, the original event details), and a firm administrator can restore any removed row with a single click. Restoration sends the row back to the Confirmed list and logs a corresponding restore event, so the full back-and-forth is preserved if the LAA changes their mind.
What happens in DockItFlo
Whichever path retires a deadline, the same set of changes propagates across DockItFlo:
- The Calendar tab. The in-app Calendar tab on the Review Queue surfaces the firm’s live deadline set; retired deadlines are marked with their pill so the LAA can scan upcoming work without confusing a struck-through hearing for an active obligation. The lawyer’s connected calendar is updated separately (see below).
- The Docket Inbox. The notice that produced the deadline stays in the inbox with its original confirmation status. Retiring a deadline doesn’t retire the notice — the notice itself is the firm’s record of what the court sent.
- The Case Master tab. Any retired deadline carries the appropriate pill on the Case Master surface alongside other deadlines from the same notice, so the LAA reading the notice in context sees which deadlines are still live and which are not.
- The Review Queue’s Removed Dates table. Every retired deadline lives here with the row treatment matching its retirement reason. Firm admins and super admins can restore any row.
- The case activity log. Every retirement writes an event to
notice_eventstied to the source notice and the affected extracted date, with the actor, timestamp, and reason. The activity log on the review modal opened from Case Master reads back through this chain.
What happens on the attorney’s calendar
The behavior on the attorney’s connected Outlook or Google Calendar depends on whether the deadline was ever there in the first place. Three of the four retirement paths apply to events that were previously pushed; the fourth (AI error) describes a row that was caught at review before any push happened.
Court-driven retirements stay on the calendar with strikethrough. When a vacate, supersession, or case-closed cascade retires a deadline that’s already on the lawyer’s connected calendar, DockItFlo updates that calendar event in place — never deleting it. The update applies a [VACATED], [CHANGED], or case-status title prefix, a strikethrough body note, and a status set to cancelled (Google) or marked as free time (Outlook). The event remains visible on the attorney’s calendar so any external reference still resolves — email threads, meeting invites, attorney notes, links from the firm’s document management system — but the prefix and strikethrough leave no doubt that the event is no longer a live obligation.
This deletion-avoidance is a deliberate design choice and a direct response to attorney feedback. Calendar events are referenced from many places outside the calendar; deleting the underlying event silently breaks every one of those references. Marking the event as retired preserves the references while making the change unambiguous.
AI-error rejections never reach the connected calendar. When the LAA removes an extraction in the review queue as an AI error, the date never gets pushed in the first place. There is no calendar event to update, and adding one with a "removed" marker would be misleading. The audit trail inside DockItFlo (the activity log on the source notice) retains the full record, but the lawyer’s calendar is unaffected.
The activity log entries on the source notice link directly to the case’s document library and to the original ECF notice, so any time an attorney or auditor needs to retrace why a calendar event was retired, the chain is one click away.
Why the distinctions matter
It would be simpler to lump every retired deadline into a single “Removed” bucket with a generic strikethrough. DockItFlo doesn’t, for three reasons.
LAA velocity. A legal administrative assistant processing forty notices on a Thursday afternoon needs to recognize at a glance whether a row in Removed Dates is a court action she should brief the attorney on (vacated, date-changed), a case-management consequence she should mention to the partner (case settled), or an AI cleanup item the firm should track for prompt-tuning purposes (rejected as AI error). The pill and the strikethrough are not decorative — they communicate the appropriate next action.
Lawyer trust. An attorney scanning their own calendar for a meeting they vaguely remember should be able to tell whether the meeting was cancelled by the court, moved to a new date, or rendered moot by the case closing. The marker on the calendar event — preserved with strikethrough and a title prefix rather than deleted — carries that information without requiring the attorney to open the notice or contact the LAA.
Audit defensibility. Deadline management is professional responsibility work. After the fact, a firm needs to show exactly what happened to any deadline, when, why, and who decided. The four-state taxonomy keeps the record clean and queryable: a search across the activity log can pull every vacate, every date change, every case-cascade retirement, and every AI-error rejection separately. This is the foundation of a defensible docketing record.
What DockItFlo does
DockItFlo distinguishes four reasons a deadline is retired — vacated by the court, changed to a new date, retired because the case closed, or rejected by the LAA as an AI error — and treats each one with its own visual pill, row treatment, and calendar consequence. The Removed Dates table on the Review Queue is the single source of truth for retired deadlines, with a Restore option for firm admins. Court-driven retirements stay visible on the attorney’s connected calendar with strikethrough and a title prefix; AI-error rejections never reach the calendar in the first place. The full chain — original notice, retirement action, actor, timestamp — lives in the case activity log.
Frequently asked questions
What happens to a date in DockItFlo when the court changes it?
The new ECF notice is flagged as a date change candidate in the review queue. The LAA reviews the old and new dates side by side and confirms either a supersession (replace) or two separate deadlines (keep both). On supersession, the original deadline moves to the Removed Dates table with a strikethrough and a Superseded pill, and the new deadline becomes the live obligation. The connected attorney calendar gets two updates: the original event is marked in place with a [CHANGED] prefix and strikethrough (it is preserved on the calendar so any external reference still resolves), and the new event is added at the new date. The full chain is in the case activity log.
What happens when the court vacates a hearing or deadline?
The vacate is detected automatically and flagged with a red Vacated pill in the review queue. On confirmation, the original event stays in the database with a supersession pointer to the vacating notice, the Removed Dates table renders the row with a strikethrough and a Vacated pill, and the connected calendar event is updated in place with a [VACATED] prefix and a cancelled status. The event is preserved on the lawyer’s calendar — never deleted — so any external reference still resolves.
What happens to pending deadlines when a case settles?
When a firm admin marks a case Settled or Dismissed, every pending deadline on that case is auto-retired and moved to the Removed Dates table with a slate-tinted strikethrough and a Case settled or Case dismissed pill. The cascade fans out across MDL consolidations — if a parent case settles, the consolidated children’s pending deadlines are retired too. Confirmed events that were previously pushed to the lawyer’s calendar are marked in place with the case-status note, not deleted. New ECF notices arriving on a settled case still flow in for review (post-settlement attorney’s fees notices, for example).
What does “Rejected (AI error)” mean on a Removed Dates row?
It means the LAA judged the AI’s extraction to be incorrect — the date didn’t represent a real deadline at all. AI errors render with no strikethrough because there was never a real event to strike through, and they never reach the lawyer’s connected calendar because the LAA caught the bad extraction during review, before any push happened. The plain-text row with a gray Rejected (AI error) pill keeps the LAA’s mental model clean and signals to the firm that the row is a candidate for AI prompt tuning rather than a court-driven retirement.
Can a retired date be restored?
Yes. Firm admins and super admins can restore any row from the Removed Dates table with a single click. The row returns to the Confirmed list, and a corresponding restore event is logged on the source notice. Restoration is admin-gated by design — an LAA can retire a date in one click, but bringing it back requires a second pair of eyes to keep the audit trail clean.
Are retired dates ever deleted from the database?
No. Retirement is always a soft action: the row is marked with the actor, timestamp, and reason, never dropped. The full chain — original ECF notice, retirement action, restore (if any) — is preserved permanently in the case activity log. After the fact, the firm can show exactly what happened to any deadline and why.