# Court Docket, Deadline Management, and Litigation Timeline

## Purpose

The Court Docket provides a centralized view of court dates, litigation deadlines, filing activity, service dates, decisions, reminders, and escalations for an existing litigation case.

It does not replace Calendar, Tasks, Hearings & Proceedings, Court E-Filing, Documents, Service of Process, or Orders & Rulings. Those modules remain the authoritative source for their records. The docket consolidates their important dates and adds structured litigation deadline management.

The same litigation workspace also includes a **Timeline** tab. The Timeline consolidates completed and historical litigation activity from the existing modules into one chronological view. It does not copy or replace the original business records.

## Permissions and Matter Access

| Activity | Required permission |
| --- | --- |
| View the Court Docket | View Court Docket (`docket_read`) and access to the linked matter |
| Create a managed deadline | Create Court Docket Entries (`docket_create`) |
| Edit deadline metadata or responsibility | Update Court Docket Entries (`docket_update`) |
| Change a deadline date | Reschedule Court Deadlines (`docket_reschedule`) |
| Start, complete, or cancel a deadline | Complete Court Deadlines (`docket_complete`) |
| Change reminder schedules and escalation settings | Configure Court Docket Reminders (`docket_configure_reminders`) |
| Acknowledge deadline escalations | Acknowledge Court Docket Escalations (`docket_acknowledge_escalations`) |

Creating an actionable task also requires permission to create tasks. Linked documents, filings, hearings, pleadings, orders, and service records remain subject to their own module permissions.

Every docket request respects the existing matter-level restrictions. Having a docket permission does not grant access to a litigation case or matter that the signed-in user cannot otherwise access.

### Timeline Access

The Timeline uses the existing Litigation and Matter access controls. A user must have **View Litigation** permission (`litigation_read`) and access to the linked matter.

Source-specific permissions continue to apply:

- evidence and exhibit events require **View Evidence** (`evidence_read`);
- witness events require **View Witnesses** (`witness_read`);
- court deadline and escalation events require **View Court Docket** (`docket_read`); and
- related document information appears only when the user can view that document.

The Timeline does not allow broader access to confidential witness, evidence, document, or matter information.

## Open the Court Docket

1. Open **Practice > Litigation**.
2. Select the litigation case title or case number.
3. Select the **Court docket** tab.

The tab is visible only when the signed-in user has **View Court Docket** permission.

## Open the Consolidated Litigation Timeline

1. Open **Practice > Litigation**.
2. Select the litigation case title or case number.
3. Select the **Timeline** tab.

The Timeline is a read-only view. Create, edit, reschedule, complete, or otherwise manage a record in its original workspace tab.

## Understand the Timeline

The Timeline combines material case events from existing authoritative records.

| Timeline category | Examples |
| --- | --- |
| Matter Lifecycle | Matter activation, status changes, closure, and reopening. |
| Litigation | Case registration, pleadings, court filings, hearings, service of process, orders, rulings, and judgments. |
| Evidence | Evidence registration, evidence status changes, exhibit designation, submission, admission, rejection, or withdrawal. |
| Witness | Material witness status changes, hearing appearances, and examinations. |
| Court Docket | Deadline creation, rescheduling, completion, overdue events, cancellation, task synchronization, and significant escalations. |
| Legal Team | Lead lawyer and team assignments, approved or rejected reassignments, and completed handovers. |

Routine HR activity and technical audit events are not displayed merely because they exist. The Timeline focuses on events that materially affect the litigation case.

### Event Information

Each Timeline entry can show:

- the date and time the event occurred;
- the date and time it was recorded, when different;
- the event category and type;
- title and available summary;
- current or resulting status;
- responsible user, where recorded;
- source module and source record identifier; and
- an authorized related document reference, where available.

Select the event title to open its details modal.

### Occurrence Date and Recorded Date

The Timeline orders an event using its actual occurrence date where the source record provides one. For example:

- a pleading uses its filing or preparation date;
- a hearing uses its scheduled or actual hearing date from Calendar;
- a decision uses its decision date;
- served process uses its service date;
- evidence uses its registration date; and
- an examination uses its examination date.

The **Recorded** value identifies when the information was entered into the system. It may differ from the occurrence date. The system does not replace a known historical event date with the record creation timestamp.

When events have the same timestamp, the Timeline applies a stable secondary order so pagination remains consistent.

## Upcoming Events

Future activity is displayed separately under **Upcoming events** instead of being mixed into the historical chronology.

Upcoming events can include:

- scheduled court hearings;
- open managed court deadlines;
- pending service deadlines; and
- scheduled witness appearances.

Select an upcoming event to open its authoritative workspace tab. Completing, cancelling, or rescheduling the source record updates how it appears the next time the Timeline loads.

## Search and Filter the Timeline

Use the Timeline controls to filter by:

- words in an event title or description;
- event category;
- event type;
- responsible lawyer;
- court hearing;
- pleading or filing type; and
- occurrence date range.

Select **Newest first** or **Oldest first** to change chronological order. Use the pagination controls below the event list to move between result pages.

Filters apply only to the historical event list. The **Upcoming events** section remains a separate forward-looking view.

## View Timeline Event Details

Select an event title to review:

- occurrence and recorded dates;
- category and event type;
- responsible user;
- event status;
- source module and source identifier;
- authorized related document; and
- the available event description.

The details modal is for review only. It does not provide edit or status buttons.

## Open the Original Source Record

Select **Open source** on an event card or **Open source record** in the details modal.

The system opens the relevant litigation workspace tab and includes the source record identifier in the page address. Examples include:

- **Pleadings & applications** for a pleading;
- **Hearings & proceedings** for a hearing;
- **Orders & rulings** for a decision;
- **Service of process** for a service event;
- **Evidence & exhibits** for evidence or exhibit activity;
- **Witnesses** for appearance or examination activity;
- **Court docket** for deadline activity; and
- **Overview** for matter lifecycle or legal-team activity.

The original module remains responsible for authorization and modification. If the source is no longer available or your permissions have changed, the system must not expose restricted information through the Timeline.

## Timeline Confidentiality and Data Integrity

- Timeline retrieval enforces litigation and matter authorization on the backend.
- Evidence, witness, docket, and document information is included only when the signed-in user has the corresponding access.
- Search and filtering operate only on the events the user is authorized to receive.
- Event identifiers remain tied to the original source records.
- Duplicate timeline entries with the same stable event identifier are removed.
- Source record changes are reflected when the Timeline is reloaded.
- The Timeline does not create a separate timeline table or duplicate litigation business records.

The Timeline is distinct from the technical audit log. Displaying a business event does not create another audit entry, and loading the Timeline does not modify historical records.

## Understand the Dashboard

The summary cards show:

- **Upcoming hearings** — future active hearings from Hearings & Proceedings and Calendar;
- **Upcoming deadlines** — open managed deadlines that have not expired;
- **Overdue** — open deadlines whose applicable date and time have passed;
- **Critical** — open deadlines marked with critical priority;
- **Unassigned** — open deadlines without a responsible team member; and
- **Awaiting completion** — all deadlines that are neither completed nor cancelled.

These figures are limited to the current litigation case and the signed-in user's access.

## Managed Deadlines and Source Records

The workspace separates two types of information.

### Managed Court Deadlines

These are structured deadline records created in the Court Docket. They can include:

- statutory limitation deadlines;
- court filing deadlines;
- court-ordered compliance deadlines;
- service-of-process deadlines;
- appeal deadlines;
- response and submission deadlines; and
- other court-related deadlines.

Managed deadlines support responsibility, priority, controlled status changes, rescheduling history, reminders, escalation, supporting documents, and optional task integration.

### Authoritative Source Records

The lower section of the workspace displays existing:

- court hearings;
- orders, rulings, and judgments;
- service dates; and
- court e-filings.

These entries are read from their original modules. The docket does not create duplicate calendar events, hearings, decisions, service records, or filings.

To change a hearing date, update it under **Hearings & proceedings**. To change filing information, use **Documents & e-filing**. The docket reflects the authorized source-record change.

## Search and Filter

Use the controls above the managed deadline table to filter by:

- docket reference, title, description, court, or legal basis;
- deadline type;
- court or tribunal;
- priority;
- status;
- responsible team member; and
- date range.

The matter and litigation case are already determined by the current workspace. Use the pagination controls below the table to move between result pages.

## Listing Actions

| Action | Purpose |
| --- | --- |
| Select the first column | Open the complete deadline details modal. |
| Eye | Open deadline details, history, reminders, and escalations. |
| Pencil | Edit deadline metadata and linked records. |
| Calendar | Reschedule the deadline with a reason. |
| Refresh | Update the deadline status. |
| Bell | Configure the reminder schedule and escalation. |

Each action opens only its relevant form. Selecting an action icon does not also open the details modal.

## Add a Manual Deadline

Use a manual deadline when the applicable date has already been determined or an automatic calculation is inappropriate.

1. Open the **Court docket** tab.
2. Select **Add deadline**.
3. Select the deadline type.
4. Enter a descriptive title.
5. Enter the court or tribunal where applicable.
6. Select the responsible matter team member.
7. Select the priority.
8. Choose **Manual** as the calculation mode.
9. Enter the deadline date and time.
10. Confirm the applicable time zone.
11. Enter the source or legal basis.
12. Link relevant hearings, pleadings, orders, service records, e-filings, tasks, or documents.
13. Select a reminder schedule.
14. Enable or disable escalation.
15. Select **Create deadline**.

The system generates a reference such as `DCK-HCCS-2026-001-0001` and assigns **Upcoming** or **Overdue** according to the applicable date and time.

## Add a Calculated Limitation Deadline

Calculated deadlines require an identified legal or configured rule. The system does not contain hardcoded statutory limitation periods.

1. Select **Add deadline**.
2. Choose **Statutory limitation** or the appropriate deadline type.
3. Choose **Calculated** as the calculation mode.
4. Enter the triggering date and time.
5. Enter the limitation period value.
6. Select days, weeks, months, or years.
7. Enter the legal rule or configuration reference.
8. Enter the rule version.
9. Confirm the time zone.
10. Review the remaining responsibility, priority, link, reminder, and escalation fields.
11. Select **Create deadline**.

The docket preserves:

- the triggering date;
- the period value and unit;
- the rule reference;
- the rule version;
- the calculated deadline;
- the calculation timestamp; and
- confirmation information where provided.

Changes to a configuration do not silently recalculate a previously confirmed deadline. Use the controlled rescheduling action when an adjustment is authorized.

## Priority Levels

| Priority | Typical use |
| --- | --- |
| Low | Informational or low-impact dates. |
| Normal | Routine litigation deadlines. |
| High | Important deadlines requiring close monitoring. |
| Critical | Limitation, appeal, or other dates where delay presents substantial risk. |

Critical priority does not change the legal meaning of a deadline. It affects dashboard visibility and can trigger an approaching-deadline escalation.

## Assign Responsibility

The responsible person must be the matter's assigned attorney or an active or approved member of its legal team.

An unassigned deadline remains visible and can trigger an escalation. Assign responsibility as soon as the appropriate lawyer is known.

Changing responsibility through the docket records the previous user, new user, responsible user making the change, and timestamp. If a task is linked, the task assignee is synchronized.

## Link Existing Records

A deadline may reference existing:

- hearings or proceedings;
- pleadings or applications;
- court orders, rulings, or judgments;
- service-of-process records;
- court e-filings;
- tasks; and
- supporting documents.

The linked record must belong to the same litigation case or matter. Linking does not copy or replace it.

### Filing Deadlines

Link a filing deadline to the relevant pleading or e-filing where available. A prepared or uploaded document does not complete a filing deadline automatically. The e-filing source record separately shows its actual submission date and filing status.

### Court-Ordered Deadlines

Link the relevant order or ruling and supporting document. Enter the compliance requirement in the title, description, or source basis so the responsible lawyer understands the required action.

### Service Deadlines

Link the applicable service-of-process record. Service status remains managed under **Service of process** and is displayed as a source record in the docket.

## Task Integration

### Link an Existing Task

Select an existing matter task while creating the deadline. The task must belong to the same matter.

### Create an Actionable Task

Select **Create an actionable deadline task** when the deadline requires work that should be tracked through Task Management. A responsible team member is required.

The generated task reuses the deadline title, description, priority, assignee, date, and time.

### Synchronization Rules

- Starting a linked task changes the managed deadline to **In Progress**.
- Completing a linked task completes the managed deadline and records history.
- Cancelling a linked task cancels the managed deadline and preserves the cancellation reason.
- Authorized task reassignment updates the docket responsibility and history.
- Docket rescheduling updates the linked task date and time.
- Docket completion or cancellation updates the linked task.

A linked task's due date cannot be changed from Task Management. Use the docket's calendar action so the system requires a rescheduling reason and preserves the previous deadline.

Generic task editing also cannot bypass the dedicated completion or cancellation actions.

## Reminder Schedules

Select the bell icon to configure reminders. Users select a named schedule rather than entering minute values.

| Schedule | Reminders sent |
| --- | --- |
| Light | 3 days before and on the deadline day. |
| Standard | 7 days before, 1 day before, and on the deadline day. |
| Early Notice | 14 days before, 3 days before, and on the deadline day. |
| Frequent | 14, 7, 3, and 1 day before, plus the deadline day. |

**Standard** is the recommended default for routine deadlines. Use **Frequent** only for genuinely critical dates to avoid unnecessary notification volume.

Reminders are sent to relevant users through the existing notification infrastructure. The system records each deadline, recipient, and reminder interval so retrying the processor does not generate an identical reminder twice.

When a deadline is rescheduled, new pending reminders are based on the updated deadline. Previously delivered reminder history remains available.

## Deadline Escalation

When escalation is enabled, the system can escalate:

- an overdue deadline;
- a critical approaching deadline that is still **Upcoming**;
- a deadline without a responsible lawyer; or
- repeated reminders that remain unacknowledged.

Escalation recipients are determined using the responsible lawyer, matter attorney, and relevant lead assignment. The system does not create a separate workflow or duplicate team assignments.

### Acknowledge an Escalation

1. Select the eye icon for the deadline.
2. Find the escalation under **Reminder and escalation history**.
3. Select **Acknowledge**.

The system records the acknowledgement user and time. Acknowledgement confirms that the escalation was seen; it does not complete, cancel, or reschedule the deadline.

## Update Deadline Status

Select the refresh icon to choose an allowed next status.

| Current status | Allowed next statuses |
| --- | --- |
| Upcoming | In Progress, Completed, Cancelled |
| In Progress | Upcoming, Completed, Cancelled |
| Overdue | In Progress, Completed, Cancelled |
| Completed | Final |
| Cancelled | Final |

Cancellation requires a reason. Completion records the responsible user and completion timestamp.

The system determines **Overdue** from the applicable deadline and completion information. An overdue deadline is not automatically cancelled.

## Reschedule a Deadline

1. Select the calendar icon in the deadline's **Actions** column.
2. Enter the new date and time.
3. Enter the reason for modification.
4. Select the supporting court order or document where applicable.
5. Select **Save**.

The system records:

- the previous deadline;
- the updated deadline;
- the reason;
- the responsible user;
- the modification timestamp; and
- the supporting document.

If another user changed the deadline after you opened the form, the system rejects the stale update. Refresh the docket, review the latest values, and try again.

Completed or cancelled deadlines cannot be rescheduled through ordinary actions.

## View Deadline Details and History

Select the first column or eye icon to open the details modal.

The modal shows:

- deadline type, priority, status, date, time zone, court, and responsibility;
- calculation inputs and preserved rule information;
- linked task, pleading, order, filing, and document;
- chronological creation, status, rescheduling, responsibility, and synchronization history; and
- delivered reminders, escalation conditions, recipients, and acknowledgements.

The eye-icon modal is intended for review. Editing, rescheduling, status, and reminder configuration remain explicit table actions.

## Source Record List and Calendar Views

Use **List** to review source records in a table. Use **Calendar** to group managed deadlines and source records by month.

The docket identifies a hearing scheduling conflict when an attendee has another active calendar event that overlaps the hearing. The warning does not automatically move either event. Review and reschedule the authoritative calendar or hearing record where appropriate.

## Reassignment and Controlled Handover

Open docket deadlines participate in lawyer workload calculations and HR-impact reviews.

During an approved reassignment:

- open deadlines appear in the controlled handover checklist;
- the outgoing lawyer remains responsible during the handover;
- the incoming lawyer can review transferred responsibilities according to matter access; and
- responsibility changes only when the handover is finalized.

When finalization succeeds, open deadlines assigned to the outgoing lawyer transfer to the incoming lawyer. Linked task assignments transfer at the same time, and the docket records a **Handover Reassigned** history event.

Completed and cancelled deadlines remain historical and are not reassigned.

## Matter Closure and Archiving

Closing or archiving a matter does not delete its docket, reminder, escalation, or history records. Historical visibility continues to follow matter permissions and lifecycle restrictions.

Operational changes to closed or archived matters remain subject to the existing Matter Lifecycle controls.

## Audit and History

The existing audit logging infrastructure records sensitive docket operations, including:

- deadline creation and metadata updates;
- responsibility changes;
- status transitions;
- completion and cancellation;
- rescheduling;
- reminder configuration changes;
- task synchronization;
- handover responsibility transfer; and
- reminder and escalation delivery or acknowledgement.

Ordinary editing does not overwrite chronological deadline history.

## Common Issues

### The Timeline Tab or an Event Is Missing

Confirm that you have **View Litigation** permission and access to the linked matter. Evidence, witness, docket, and related document events also require their corresponding source-module permissions.

Confirm that the source record belongs to the current litigation case. Future hearings, deadlines, service dates, and witness appearances may appear under **Upcoming events** rather than in historical results. Clear the Timeline filters and reload the workspace after updating a source record.

### The Court Docket Tab Is Missing

Confirm that you have **View Court Docket** permission and access to the litigation case's linked matter.

### A Responsible Lawyer Is Not Available

The person must be the matter attorney or an active or approved matter team member. Complete the existing team assignment process before assigning the deadline.

### A Hearing, Filing, Pleading, Order, Service Record, Task, or Document Is Missing

Confirm that the record:

- already exists in its source module;
- belongs to the same matter or litigation case;
- is visible to your user account; and
- has not been removed or restricted.

Refresh the litigation workspace after creating the source record.

### The Deadline Is Immediately Overdue

Review the entered date, time, and time zone. A manual or calculated deadline earlier than the current time is correctly classified as overdue.

### The Task Due Date Cannot Be Edited

The task is linked to a managed court deadline. Use the calendar icon in the Court Docket to reschedule it with a reason. The linked task updates automatically.

### A Status Is Not Offered

Only valid next statuses appear. Completed and cancelled deadlines are final through ordinary actions.

### A Reminder Was Not Duplicated After Retrying

This is expected. Reminder and escalation processing is idempotent and prevents the same notification for the same recipient, deadline, date, and trigger from being delivered twice.

### A Reschedule Is Rejected as Stale

Another user changed the deadline after your form was opened. Refresh the docket and review the new version before resubmitting.

## Recommended Operating Sequence

1. Record hearings, pleadings, orders, service activity, filings, and documents in their existing modules.
2. Create the managed deadline and link the relevant source records.
3. Assign an eligible responsible team member.
4. Select a proportionate reminder schedule, normally **Standard**.
5. Create or link a task when actionable work is required.
6. Review dashboard warnings for critical, overdue, unassigned, or conflicting records.
7. Start and complete work through the docket or linked task workflow.
8. Reschedule only with an authorized reason and supporting document where applicable.
9. Acknowledge escalations after review.
10. Use controlled handover when responsibility must move between lawyers.
11. Review the **Timeline** for the consolidated historical progression and use **Open source** for record-level work.

This process keeps the Court Docket centralized while preserving Calendar, Tasks, E-Filing, Documents, Hearings, and Matter Management as the authoritative modules for their own records.