Litigation Hold and Product History Chronology demo
Custodians found from the product's own records, mailboxes saved before deletion, and a cited chronology for counsel. 1:27
What the demo shows
Litigation hold for device makers: custodians from product records and a cited chronology
Agents read the records of a powered surgical table in eight systems (4,201,000 items) and find 46 custodians from who actually signed them, against 12 named by the first, org-chart hold. Nine have left; three of their mailboxes were due for deletion the next week. Litigation counsel signs the scope, the eDiscovery manager suspends the deletions and sends 37 notices, the records manager applies each system hold, and a paralegal reviews a 46-event chronology that counsel signs for outside counsel. Complaint and device report files stay with the complaint handling unit and are never read.
Transcript
- Litigation Hold and Product History Chronology finds and holds everyone behind a device's history.
- For litigation counsel. This surgical table claim's first hold named twelve people, from an org chart.
- Agents read eight systems: forty-six custodians, nine departed, three mailboxes deleting next week.
- Complaint files stay behind the fence, with the complaint unit, never read.
- The eDiscovery manager excludes two weak names, with a reason, and sends the scope.
- Counsel reads the scope and departures herself, then signs with her own password.
- The three deletions are suspended at once, and thirty-seven hold notices go out.
- Every chronology event cites the record behind it.
- Every signature is on the audit trail, and counsel alone decides privilege.
- Thirty-four missed custodians are now in scope, saving an estimated hundred fifty hours per matter.
- Built on Botminds: agents, data, screens and governance on one platform.
The narration as written for the film. Captions are on the player.