These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Court Case Management
- Data model and import order
The tables behind Court Case Management
Court Case Management ships with 14 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 14
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Matters:
Matters links the owning Organizations record, assigned team members owner and matter types definition.
Deadlines:
Matter deadlines belongs to a source matter and an assigned team member.
Events and evidence:
Matter events has a parent matter; record attachments has a source matter and verifier.
Independent review:
Review decisions links the source matter, its revision and reviewer.
Execution and history:
Operation receipts and execution attempts link to Matters; operation steps links to a receipt; state history links transitions and actors to the matter.
Configuration:
Organizations owns matter types and team members; source mappings belongs to a matter type.
Every table, by feature
- Matters7
- Deadlines5
- Events and evidence5
- Independent review5
- Execution and history7
- Organizations and types5
- Shared and settings1
- Matters
Matters, cases and filings opened for a client engagement.
Linked to Organizations, Team members, Matter types - Matter types
Published matter types, practice areas and engagement definitions offered by an organization.
Linked to Organizations - Matter events
Observation-level event, document and line detail captured against a matter.
Linked to Matters - Matter deadlines
Assigned court deadlines, corrections and outstanding filings for a matter.
Linked to Matters, Team members - Record attachments
Uploaded and verified supporting documents and source evidence.
Linked to Matters, Team members - Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Matters, Team members - State history
Immutable workflow-written status transition history for each matter.
Linked to Matters, Team members
- Matter deadlines
Assigned court deadlines, corrections and outstanding filings for a matter.
Linked to Matters, Team members - Matters
Matters, cases and filings opened for a client engagement.
Linked to Organizations, Team members, Matter types - Team members
Attorneys, coordinators, reviewers and assigned team members.
Linked to Organizations - State history
Immutable workflow-written status transition history for each matter.
Linked to Matters, Team members - Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Matters, Team members
- Matter events
Observation-level event, document and line detail captured against a matter.
Linked to Matters - Record attachments
Uploaded and verified supporting documents and source evidence.
Linked to Matters, Team members - Matters
Matters, cases and filings opened for a client engagement.
Linked to Organizations, Team members, Matter types - Team members
Attorneys, coordinators, reviewers and assigned team members.
Linked to Organizations - Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Matters, Team members
- Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Matters, Team members - Matters
Matters, cases and filings opened for a client engagement.
Linked to Organizations, Team members, Matter types - Matter events
Observation-level event, document and line detail captured against a matter.
Linked to Matters - Record attachments
Uploaded and verified supporting documents and source evidence.
Linked to Matters, Team members - State history
Immutable workflow-written status transition history for each matter.
Linked to Matters, Team members
- Operation receipts
Workflow-maintained execution runs with operation key, input hash and persisted result reference.
Linked to Matters - Operation steps
Ordered steps inside an operation run with input, output and external receipt state.
Linked to Operation receipts - Execution attempts
Each recorded attempt to execute an approved action for a matter.
Linked to Matters - State history
Immutable workflow-written status transition history for each matter.
Linked to Matters, Team members - Matters
Matters, cases and filings opened for a client engagement.
Linked to Organizations, Team members, Matter types - Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Matters, Team members - Matter deadlines
Assigned court deadlines, corrections and outstanding filings for a matter.
Linked to Matters, Team members
- Organizations
Courts, legal departments and firms that own matters and case work.
- Team members
Attorneys, coordinators, reviewers and assigned team members.
Linked to Organizations - Matter types
Published matter types, practice areas and engagement definitions offered by an organization.
Linked to Organizations - Source mappings
Reviewed field mappings and transform rules between source payloads and target fields.
Linked to Matter types - Matters
Matters, cases and filings opened for a client engagement.
Linked to Organizations, Team members, Matter types
Keys and references
Use the case number as the recognizable business key while preserving each record’s own identifier. Keep source event IDs and external references when moving data from another system. The decision’s source revision and the receipt’s source revision should identify the same approved work before delivery. Retain the operation key and input hash so a repeated execution can be reconciled with its earlier attempt.
A saved list such as My matters is a view of Matters. It does not add another table or another owner of the case data. Keep the relationship from every deadline, event, attachment, decision and state transition to its actual source matter.
Migration order
- Load Organizations and authorized Users, then team members and active matter types.
- Review source mappings for any imported case data before loading Matters with numbers, owners and opening dates.
- Load matter events, record attachments and matter deadlines with their source links and identifiers.
- Bring forward review decisions and state history with the correct source revisions; reconcile operation receipts, steps and attempts separately.
- Compare a representative case from intake through completion, including a returned revision and a corrected delivery.
Set up Court Case Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.