1. Document Automation
  2. Features
  3. Deadlines and events
Feature · Deadlines and events

Deadlines and events

Assign due work and keep completion evidence beside the matter.

OverviewDeadline register
Document Automation · Deadlines and events

Deadline register

Matter deadlines

New
Deadline typeDue atCompleted atCourt receiptMatterOwner
DT-70604 Oct07 OctCR-455MTT-32086
DT-10515 Oct15 OctCR-776MTT-68016
DT-68405 Oct06 OctCR-695MTT-23822
DT-56109 Oct10 OctCR-557MTT-20407
DT-76606 Oct10 OctCR-140MTT-91300
6 of 6 records
DT-706Matter deadlines · MD-63397
Due at04 Oct
Completed at07 Oct
Court receiptCR-455
MatterMTT-32086
Example screen with sample data

What you can do

Put due work in matter context

A matter deadline identifies the type of obligation, its due date and the team member who owns it. When work is complete, the completion date and court receipt provide the checkable outcome. The deadline points back to the matter, so the owner can review its subject and current state before acting.

Matter events record the dated history around a case: a hearing, filing, review, decision or communication. An event may carry a due date, an occurrence date, an external receipt and a document revision. These details help the team tell planned activity from something that occurred. A filing event with a due date is not the same as a completed filing with a receipt.

How the work is organized

  • Assigned obligation. Give the deadline a type, due date, matter and owner.
  • Completion evidence. Record completion and the receipt when the external action produces one.
  • Dated history. Add events for the milestones and communications that explain the work.

What to agree during setup

Agree who enters deadlines, who verifies their completion and what kind of receipt is sufficient for each obligation. Define the handoff when an owner is unavailable. A due date should remain visible to the new owner, and the matter should keep the prior event history. The team should decide when an event is useful alongside a deadline, such as when a hearing generates a filing requirement.

Confirm how dates and time zones are handled for organizations working across jurisdictions. The App Administrator maintains organization and member time zones, while the legal team remains responsible for confirming the actual deadline. A dashboard can draw attention to approaching dates, but the responsible person must inspect the matter and external confirmation.

Check the handoff on an actual case

An attorney has a filing due for an active matter. The coordinator enters the deadline with its owner and due date, then records a filing event when the submission occurs. The external receipt is attached to the event and the deadline is marked complete with its receipt. Another authorized reviewer can now see the due date, occurrence and completion evidence in the same matter context.

Run the case again without an external receipt. The owner should see that the work still needs verification even if the event says it was filed. The team can contact the court or its filing service before calling the obligation complete. This check prevents a typed completion date from standing in for the external result.

What your team sees

  • Deadline register — Inspect due work and its completion evidence.
  • My deadlines — Review obligations assigned to the current owner.

Follow the work through

What it keeps track of

Data model
Matter deadlines
Court and contract deadlines with verified completion receipts.
Matter events
Dated matter milestones, filings, hearings and communications.
Matters
Legal or contract matters with lifecycle, owner and agreed fee.
Team members
Internal staff with organizations, roles and platform identities.

Who uses it

Permissions
Matter Coordinator
, Supervising Attorney, Auditor.

Set up Document Automation your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started