Legal Holds and Preservation

What This Solves

Spoliation sanctions are one of the most damaging outcomes in civil litigation: adverse inference instructions, case-dispositive penalties, and cost-shifting awards that dwarf the original cost of proper preservation. The central question under FRCP Rule 37(e) is whether the party took reasonable steps to preserve ESI once litigation was reasonably anticipated. Reasonable steps require more than sending an email to a few custodians and hoping for the best.

GDF works with counsel to design hold programs that are documented, tracked, and verifiable. We manage the technical side: preservation-in-place configurations, custodian notification systems, acknowledgment tracking, reminder workflows, and preservation verification. Counsel retains full authority over scope decisions and legal strategy. GDF's role is to ensure that the technical preservation record can withstand challenge.

The Legal Framework

FRCP Rule 26(f) requires parties to discuss preservation of ESI early in the case, including issues about what needs to be preserved and the form of any preservation obligations. That conference often occurs before the litigation hold is finalized, and the positions taken there can define what "reasonable steps" means for the rest of the matter.

Rule 37(e) provides the framework for what happens when ESI is not preserved. Courts examine whether the ESI should have been preserved, whether reasonable steps were taken, and whether the information can be restored or replaced. Where loss is found to be intentional, courts may give an adverse inference instruction or dismiss claims. Even unintentional loss carries risk. A documented, well-managed hold program is the factual foundation for any argument that the producing party acted reasonably.

GDF's preservation documentation is designed with that analysis in mind from the start: who was notified, when, through what system, whether they acknowledged, whether reminders were sent, what technical measures were put in place, and what the audit log shows.

Preservation-in-Place for Cloud Platforms

For Microsoft 365 environments, GDF configures in-place holds and compliance policies through Microsoft Purview to preserve Exchange Online mailboxes, Teams messages, SharePoint sites, and OneDrive content for identified custodians. These holds operate at the system level: even if a custodian deletes a message, the data is retained in the compliance store until the hold is released.

Google Workspace preservation uses Vault holds tied to specific accounts, organizational units, and date ranges. Slack data can be preserved through Enterprise Grid administrative settings or third-party connectors. For platforms without native hold functionality, GDF coordinates with counsel on alternative preservation measures, which may include custodial collection, suspension of deletion policies, or backup preservation, depending on what the platform supports and what the risk profile requires.

Our Process

Custodian Tracking and Ongoing Management

Legal holds are not one-time events. As a matter develops, custodians are added, removed, or depart the organization. New data sources are identified. Scope expands or narrows. GDF maintains the hold as a living program, updating custodian lists, issuing supplemental notices when scope changes, and documenting each modification with a dated change log.

Employee departures require particular attention. When a custodian under hold leaves the organization, GDF coordinates with IT to preserve their accounts, disable auto-deletion of their email and documents, and capture any device or account data before access is terminated. Departing custodian protocols are documented and can be produced if the adequacy of preservation is later challenged.

Defensible Audit Trails

The audit trail GDF produces for each hold program includes: the trigger date and basis for the hold; a complete list of custodians notified, with timestamps; acknowledgment status for each custodian; a log of all reminders issued; technical hold configurations and confirmation screenshots; scope change documentation; verification records; and the final release record. Every entry is date-stamped and attributed.

This documentation is structured to support a declaration by GDF's expert if preservation adequacy is challenged in motion practice. Courts expect producing parties to explain not just that a hold existed, but how it worked. GDF's records answer those questions directly.

Deliverables

GDF delivers the following at the conclusion of or during a hold engagement:

• Hold Notice Template: a plain-language notice drafted for the specific matter, suitable for counsel review before issuance
• Custodian Master Log: a running record of every custodian under hold, their notification and acknowledgment status, and any supplemental communications
• Preservation Configuration Report: technical documentation of all system-level holds and their scope
• Acknowledgment Tracking Report: a summary of all acknowledgments, reminders, escalations, and non-responses by date
• Verification Memoranda: dated records of each preservation verification check and any remediation actions taken
• Hold Modification Log: documentation of every scope change, custodian addition, or custodian removal with dates and reasons
• Release Record: a formal record of hold termination, confirming that collection obligations were satisfied before holds were lifted