Technical methods and scope

Hold Support From Examiners Who Collect What Holds Protect

Global Digital Forensics has practiced since 1992, and our legal hold support grew out of a simple observation from the collection side of the practice: by the time a collection is scheduled, the records that matter have often already been lost to a retention policy nobody thought to pause. Our examiners have collected from the systems that holds are meant to protect, and they have explained in deposition what survived and what did not. That experience shapes how we plan and verify a hold.

Rule 37(e) addresses electronically stored information that should have been preserved and was lost, and the reasonable steps a party took are what the court examines. We document the technical preservation steps, the verification and any gaps, so the organization can show the court a dated record of reasonable steps rather than a description of good intentions.

The engagement is scoped in writing: which notification, acknowledgment tracking, reminder, escalation and configuration tasks GDF performs and which the client’s administrators perform. That clarity matters later, because the record identifies who did each thing and when, and a hold that nobody owned is the hold that fails.

Preserve in Place Across Microsoft 365, Google Workspace and Messaging

Where the client’s license supports it, Microsoft 365 can hold identified mailboxes, Teams conversations, SharePoint sites and OneDrive accounts in place, and Google Workspace can hold accounts and organizational units for defined dates. We coordinate the configuration with the tenant owner, confirm what the policy actually covers for each data type and timing, and verify the effect so the record reflects the hold as applied rather than as intended.

Messaging and collaboration platforms vary. Some offer administrative retention controls, some require an approved export or connector and some offer nothing suitable. Where a platform cannot hold data natively, counsel can approve an alternative such as a targeted collection, a change to the deletion policy or preservation of an existing backup, and the record explains why that route was chosen for that source. Phones, laptops and file shares usually need preservation steps outside the tenant altogether, which is where our mobile and endpoint collection practice joins the hold.

Keep the Hold Current as the Case Moves

Custodians are added as the case develops, removed as claims narrow and lost when people leave. The agreed program updates notices and records each addition, removal and departure with a dated reason, showing how preservation followed the developing matter rather than a snapshot from the day the first notice went out.

A departing custodian is the moment a hold most often fails. We coordinate with the legal team and IT on account retention, deletion settings and the capture of the device or account records the hold requires before the account is disabled or the laptop is wiped and reissued. The action record documents how that custodian’s sources were handled, which is precisely the question that gets asked a year later.

If a custodian is leaving this week or a retention cycle is about to run, call before it does. We will tell you which sources are at risk and what can be done today.

Get a Free Consultation Call (800) 868-8189

A Dated Record of Every Notice, Hold and Check

The audit record connects the trigger date and its legal basis to the notified custodians and timestamps, the acknowledgment status, the reminders and escalations, the configured holds with their settings and screenshots, the scope changes, the verification checks and the release. Material entries are dated and attributed to the responsible person, so the sequence can be examined by anyone who needs to test it.

That record supports counsel’s account of how preservation operated and can inform an expert declaration when one is needed. It ties instructions to system settings, settings to verification and verification to exceptions, which is a far stronger position than pointing to the fact that a notice once existed.

Your Hold Records and Verification Reports

The hold package begins with a matter specific notice template prepared for counsel’s review before issuance and a custodian log that records who was notified, who acknowledged and what supplemental communications followed. The configuration report identifies each technical hold, its settings and the sources it covers, and the tracking report records acknowledgments, reminders, escalations and unanswered notices by date.

Verification memoranda document the dated checks and any corrective steps, the modification log records scope changes and custodian additions or removals with dates and reasons, and the release record documents the authorized termination, the affected sources, the collection status and any overlapping hold or retention obligation checked before settings changed.

Describe the custodians and the platforms involved and we will set out in writing which of these records the engagement would produce.