Tyler TechnologiesCase and Records Management
The Docket Read as Part of the Work
This connector is not prebuilt. It would be built to your requirement on the REST API path the platform already uses, with scope and effort agreed per engagement. Tyler Odyssey is the court case management system of record in many US state and county courts, holding the docket, filings, parties and hearing calendar. Its distinguishing feature for this purpose is the calendar: a court's work is driven by dates, and evidence that cannot be found before a date is evidence that failed.
What you can do together
- Keep an exhibit attached to its case through identifiers rather than through re-keying.
- Read the docket from a workflow to assemble what a hearing needs.
- Find every case a party appears in, which the docket can answer and a folder cannot.
- Map sealed and public status at the document level, not the case level.
How it connects
Evidence would transfer with the case identifiers that make it findable later, so an exhibit and the media behind it stay connected instead of being re-keyed by a clerk. A workflow could then read the docket, which is where the value concentrates: assembling what a hearing needs, checking whether a filing deadline has passed, or finding every case a party appears in, which is a question the docket can answer and a folder structure cannot.
An engagement would settle who may see what. A court's records are public in part and sealed in part, and the boundary runs through individual documents rather than whole cases, so an integration that keys only on case number will eventually expose something sealed. That mapping is the work.
Odyssey stays the case system of record. The docket, filings and calendar stay there, and nothing is written back unless a step is scoped for it. Whether a disposition changes retention on attached media is agreed rather than assumed.
Tyler TechnologiesCase and Records Management
A scenario
- ScopingThe engagement would map public and sealed status at document level and settle retention on disposition.
- SetupThe connection is configured once against the Odyssey API with case identifiers mapped to attributes.
- FilingAn exhibit and its media attach to the case under the agreed access mapping.
- A hearing weekA workflow reads the calendar and assembles what each listed matter needs, flagging one where a deadline has passed.
- A sealed documentIt is reachable only by those entitled, because the mapping was at document level rather than case level.
What stays where
Odyssey remains the case system of record
Docket, filings, parties and calendar stay there.
Sealed status runs through documents, not cases
Keying access on case number alone is what eventually exposes something sealed.
Retention on disposition is decided
A court schedule and an evidence schedule are rarely the same document.
Processing runs where you deploy the platform
Shared or dedicated SaaS, your own cloud, on premises, or air-gapped.
Products and solutions
Next step
See it on your own Tyler Technologies instance.
We will show the connection made, the data moving and the output, then size it for your deployment.
Contact VIDIZMO
sales@vidizmo.ai
+1 571-969-2180
vidizmo.ai