- Before
- Can say who was told, but cannot say on any given day that each mailbox is still on hold.
- Now
- Opens one grid per hold with each source checked at 07:00, the people who have not acknowledged, and the leavers already caught.
A demand letter, a resigning engineer and a partial release on one hold
A competitor says two of its former engineers, hired by one of the company's subsidiaries, brought its pressure-sensor designs into a new sensor program. Its lawyers' letter arrives on a Monday morning. Here is how the hold runs, screen by screen.
A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.
- 01Wednesday morning
Each custodian and each system on one grid
eDiscovery managerThe eDiscovery manager runs 31 active holds for the group. This hold opens as a grid: 24 custodians down the side, nine systems across (mailbox, OneDrive, Teams, Slack, laptop, phone, Salesforce, PLM vault, HR file). This morning 130 of 138 sources are preserved and verified, 21 of 24 custodians have acknowledged, and one row is red: an engineer who leaves at the end of the week.
“Four disposals were scheduled on this engineer's data. The agent stopped each one on its own, under its rule, and needs two decisions.”
- 02Monday, 08:47
The letter dates the duty
Intake agentThe intake agent reads the four-page letter from the competitor's lawyers and classifies it as a demand letter that threatens suit, quoting the line that says the competitor intends to commence proceedings. It dates the duty to preserve from receipt, proposes the scope (the competitor, the new sensor program, an older product line and the two hires, from a set start date) and sets the clock to issue by Tuesday 17:00. The hold goes out at 10:14 on Tuesday, 25 hours after the letter.
Search and collection stay locked until the hold is issued.
- 03The same day
A reason for each custodian
Scoping agentFrom the letter, the complaint, the org chart and message counts, the scoping agent proposes 25 people, each with the reason and a confidence: one ran the supply negotiations with the competitor, with 412 messages to its domain. Counsel approves 21, removes three with a reason each, and keeps a former employee's archived mailbox without a notice. The agent counts messages only; no content is read before the hold.
The scoping agent does not add or remove a custodian; counsel decides.
- 04Tuesday, 10:14
A notice people understand, in their own language
Notice agentVersion 2 of the notice goes out in English, German and Spanish, in plain words: what this is, what to keep, what not to do, what IT has already done. The notice agent reminds on day 3 and day 7, escalates to the manager on day 10 and re-notices every 90 days. On this hold the median time to acknowledge is 1.1 hours; one custodian, after three reminders, has been escalated twice to their manager.
The notice agent does not edit an approved notice; a new version goes to counsel.
- 05As answers come back
Answers that change the scope
Interview agentEach custodian answers six questions when they acknowledge. One names a colleague who ran the price comparisons against the competitor, and the colleague is added a week after the notice. Another mentions a WhatsApp group with an engineer from an outside contractor. A third still has a USB drive from their time at the competitor. Each answer becomes a proposal for counsel, quoted word for word.
The interview agent does not add a source or a person itself.
- 06Each morning, 07:00
Holds checked each morning instead of assumed
Preservation agentThe preservation agent placed holds the way each system supports them: litigation and case holds in Microsoft 365, Slack's legal hold, reimage blocks on laptops, wipe blocks on phones, retention locks in the PLM vault. Each morning it confirms that each one is still present: 2,974 checks since the hold went out. Today the PLM vault timed out once and passed on retry at 07:10.
“A source counts as preserved only if it passed in the last 24 hours.”
- 07That Wednesday, 09:12
A key engineer resigns, and four disposals are already scheduled
Watch agentThe HR system records the engineer's resignation, last day Friday. The watch agent matches them to the hold, since they are named in the complaint, and finds what IT already has queued: a service-desk ticket to reimage the laptop on Friday at 17:00, an exit wipe of the phone, mailbox and OneDrive deletion 30 days after leaving, and Slack deactivation. By 09:14 the ticket is on hold, the wipe blocked, both deletions paused and Slack confirmed to keep the messages.
The watch agent may only stop a disposal. It does not delete, release or drop a custodian.
- 0809:31
Counsel keeps the engineer in the hold and approves the image
Senior litigation counselThe agent hands counsel the two decisions it may not make, with the HR event, the ticket, the complaint paragraphs and its confidence of 0.98. Counsel picks the reason code “Key custodian, keep after departure”, ticks that the decision is theirs and types their name. The mailbox is kept as an inactive mailbox under hold, and the IT preservation admin images the laptop remotely: 238 GB, SHA-256 verified.
“I have read the evidence and this decision is mine.”
- 09After the stipulation
Release only what no other hold needs
Release agentA joint stipulation withdraws the claims on the older product line. The release agent proposes releasing the six custodians held only for those claims and checks their 34 sources against 30 other open holds. Four sources of one custodian (mailbox, OneDrive, Teams and Salesforce) are still needed by a warranty claim on another matter, so they stay held. Counsel signs; retention resumes on 30 sources, and each release notice says what stays held.
A full release stays closed until a dismissal, settlement or judgment is on the docket.
- 10Ready for a motion
The reasonable-steps record, built as the hold ran
eDiscovery managerThe defensibility record has each step with its time and source: letter to hold in 25 hours, 24 of 24 custodians told in writing, 2,974 daily checks with 3 exceptions, each cured within 2 hours, 0 sources lost, and the release with its authority. A draft preservation declaration is written from the log for counsel to edit; nothing is filed until counsel approves it.
Each export is logged with who took it and why.