VIDIZMO integration brief · Thomson Reuters Case Center · vidizmo.ai/integrations/catalog/thomson-reuters-case-center

Integrations / Thomson Reuters Case Center

Thomson Reuters Case Center

Export hearing bundles to Case Center for presentation. Visit website

Thomson Reuters Case Center is the digital evidence bundle and presentation system used in courtrooms, notably across UK and Commonwealth jurisdictions.

Material is exported into the bundle a hearing runs from, so what is presented in court is the governed copy and its retention is still tracked.

Built Once, and Available Again on Request

Open as a two-page brief

The Case Center connection is available on request. Authorization and an export-media workflow already exist and are re-enabled for an engagement, which is less work than building a connector from nothing.

How it connects

Case Center is the digital evidence bundle and presentation system used in courtrooms, notably across UK and Commonwealth jurisdictions. Material would be exported into the bundle a hearing runs from, so what is presented in court is the governed copy rather than a file someone carried in, and its retention continues to be tracked on the library side.

The existing implementation covers Case Center authorization and an export-media workflow. What an engagement establishes is whether that implementation still matches the current Case Center interface, since it has not been maintained as a supported integration, and what verification a court-facing path requires before it is relied on. That verification is the substance of the work rather than a formality: material presented in a hearing is the worst place to discover a format or authorization change.

Case Center stays the presentation system and the bundle stays its record. The library holds the governed copy, its retention and its custody record, and the export is what connects the two.

What you can do together

  • Present the governed copy in the hearing rather than a file copied out and carried in.
  • Keep retention and the custody record tracked on the library side while the bundle is used in court.
  • Re-enable an existing implementation per engagement rather than commissioning one.
  • Verify the path against the current Case Center interface before a hearing depends on it.

A scenario

  1. ScopingThe engagement would confirm whether the existing implementation matches the current Case Center interface and agree the verification required.
  2. Re-enablementCase Center authorization and the export-media workflow are enabled for the authority.
  3. VerificationA non-live bundle is exported and checked end to end before any hearing relies on it.
  4. A hearingThe exhibits in the bundle are the governed copies, with retention still tracked in the library.
  5. AfterwardsThe custody record shows what was exported, when, and by whom.

What stays where

It is built but not currently supported

The code exists; it is not offered as a standard integration today, and re-enabling it is per engagement.

Verification comes before reliance

The implementation has not been maintained, so it is checked against the current interface first.

Case Center remains the presentation system

The bundle and the hearing stay there.

The library keeps retention and custody

The governed copy, its schedule and its record stay on this side.

Products and solutions

Next step

See it on your own Thomson Reuters Case Center instance. We will show the connection made, the data moving and the output, then size it for your deployment.

Request a demonstration  or write to sales@vidizmo.ai

sales@vidizmo.ai  ·  vidizmo.ai/integrations/catalog/thomson-reuters-case-center

Not what you need?

We build it

Send us your API documentation and we build, test and maintain the connector, at no development cost to you.

Request this integration

Bring an MCP server

If the system publishes a Model Context Protocol server, AI Intelligence Hub connects to it as a client with configuration alone.

Define a REST endpoint

Describe your endpoint and it becomes a node in an agent workflow, without waiting on our roadmap.