What Action Should Management Take When a Litigation Hold Is Received to Prevent Early Disposal of Records Until the Litigation Is Resolved

Management should suspend all routine destruction immediately, issue a written hold notice to every custodian and IT system owner, and confirm compliance in writing before any retention schedule runs. The hold overrides existing deletion policies from the moment litigation is reasonably anticipated, not when the complaint arrives. Early disposal after that point can trigger spoliation sanctions, adverse inference instructions, and in severe cases default judgment.

The Spoliation Mechanism

A litigation hold works by converting a discretionary retention policy into a mandatory preservation duty. The trigger is not the lawsuit itself but reasonable anticipation of litigation. Once that trigger fires, any deletion of potentially relevant records becomes a legal risk, even under a routine schedule the company followed for years.

The technical problem is that modern deletion is automated and fast. A standard Microsoft 365 retention policy purges email after 30 to 90 days. Voicemail, chat channels, and mobile device backups often expire within 7 to 30 days. A company that takes two weeks to draft a hold notice may already have lost entire custodial mailboxes.

Spoliation carries a second, less obvious cost: the duty to preserve extends to metadata. File creation timestamps, revision histories, and sender-recipient logs often determine whether a document is authentic or was altered. Deleting the metadata while preserving the underlying file can be treated as destruction.

Plainly: the hold must freeze the records and the information about the records, not just the visible content.

Quantified Context

Sanctions for early disposal are not hypothetical. Courts have ordered adverse inference instructions (the jury is told to assume the destroyed records were unfavorable), monetary penalties, and case-ending dismissals. Under Federal Rule of Civil Procedure 37(e), a court may impose curative measures or, on a finding of intent to deprive, an adverse inference or dismissal.

The volume is the operational challenge. A mid-size organization with 500 custodians may hold millions of emails, thousands of chat threads, and hundreds of gigabytes of shared-drive data per year. Manual preservation at that scale fails; the hold must be enforced through system-level controls such as retention-hold flags, legal-hold mailboxes, and immutability rules on backup storage.

Statutory retention floors also intersect with holds. Employment records, tax records, and regulated industry records have minimum retention periods that already exceed typical email policies. A 3-year tax retention floor or a 7-year employment record floor means some categories survive longer regardless of the hold.

Edge Cases and Counterintuitive Detail

The most counterintuitive point: a hold can be legally defective even when every document survives. If the hold notice was vague, if it was never acknowledged, or if it failed to reach a custodian on leave, courts have treated the preservation effort as inadequate. Preservation is judged by the reasonableness of the process, not only by the outcome.

Other edge cases:

The duty can attach before any claim is filed, sometimes when a demand letter or internal investigation begins. Third-party records, including vendor and cloud provider data, may be under the company's control even when stored by another entity. Off-channel communications on personal devices create preservation gaps if not addressed at hold issuance. Departing employees often trigger the fastest data loss; exit workflows can wipe devices within days. Backup tapes are usually exempt from routine hold if inaccessible, but a known accessible backup must be held. The hold overrides a scheduled purge, but it does not always override a vendor's independent retention limit.

Misconceptions

A common misconception is that IT can "just stop the deletion job." In practice, holds must be applied at the individual custodian or repository level, and system archives may have independent cycles. Another is that only the litigation department needs to know; sales, HR, and field staff often hold the most damaging records and are the last to receive notice.

A third misconception is that a hold is permanent. Courts generally expect holds to be lifted once litigation is resolved, and holding data indefinitely raises cost and privacy exposure under data-minimization obligations.

Practical Action Sequence

The following steps reduce early disposal risk and create a defensible record.

Issue a written hold within 24 to 48 hours of the trigger, identifying the matter, the custodians, and the data categories. Route the notice to IT and records management simultaneously, with a hard stop on purges ordered in writing. Obtain signed acknowledgment from every custodian, with escalation for non-responders. Apply system-level holds on mailboxes, shared drives, chat, and endpoint backups; test that deletion is blocked. Suspend auto-delete for departing employees and migrate their data to a preservation repository. Document every action with a timestamped log; the log is the proof of reasonableness.

Comparison: Preservation Controls

Timeline: What Should Happen When

Limitations and Reconciliation

Preservation standards vary by jurisdiction, and no single rule tells a company exactly how long to hold data. Two thresholds commonly conflict: statutory minimum retention (often 3, 5, or 7 years) and the litigation hold, which lasts until the matter resolves. When they conflict, the longer period controls.

The cost of over-holding (privacy, storage, e-discovery scope) and under-holding (sanctions) are both real; the defensible position is to hold narrowly defined categories by custodian and matter, document the reasoning, and revisit scope as the case develops. Retention schedules should be audited annually so that holds are applied to known repositories rather than guessed at.

This article is general educational information, not legal advice, and does not create an attorney-client relationship. Preservation duties depend on jurisdiction, matter type, and facts; consult a qualified local attorney before acting or refraining from action on a specific hold.