What Action Should Management Take When a Litigation Hold Is Received to Prevent Early Disposal of Records Until the Litigation Is Resolved: A 7-Step Preservation Protocol With Suspension and Release Criteria

When a litigation hold arrives, management's job is to suspend every routine deletion process that could touch potentially relevant records, identify and lock down the custodians and systems involved, and keep that suspension intact until counsel confirms in writing that the matter is resolved. The single most common failure is not deliberate destruction; it is an automatic retention or auto-delete policy that keeps running because nobody thought to pause it.

This is general educational information, not a legal opinion. Litigation-hold rules vary by jurisdiction and venue, and the specifics of your matter control. Work with qualified local counsel before you release any hold.

Why the Arrival of a Hold Is a Management Emergency, Not a Routine Email

A litigation hold triggers what courts treat as a duty to preserve, and that duty can attach before the hold letter ever lands — sometimes the moment litigation is "reasonably anticipated." That timing gap matters for management because an auto-delete cycle that runs after the trigger date creates exposure even if the hold letter arrived last week.

The practical stakes are set by spoliation doctrine. Under the revised Federal Rule of Civil Procedure 37(e), which governs federal cases in the United States, a court can order curative measures or, if a party acted with intent to deprive, issue an adverse-inference instruction or dismiss the case outright. That rule text is public and stable; your local rules may add more.

Management's role is not to decide what is relevant. It is to stop the clock on deletion and put the right people on notice fast. The legal team scopes the matter; operations freeze the pipes. Confusing those two jobs is how records get lost.

Get a conditional right: if the hold names custodians, systems, and a date range, management can act within hours. If it is vague, the first call should be to counsel to pin down scope before any system is touched.

The Preservation Clock Starts Before the Letter: Date-of-Trigger Rules Management Misses

Most hold letters state a trigger date, but the duty can predate it. Courts generally look at when the organization reasonably anticipated litigation — a demand letter, a regulatory inquiry, or a credible internal complaint can all start the clock. Management should treat the earliest credible signal as the presumptive trigger.

That has a direct operational consequence. A retention policy that deletes email after 90 days means every day between the trigger event and the hold letter is a day of potential loss. If the gap was six weeks, management needs counsel to assess whether anything relevant aged out — and document that assessment.

Different jurisdictions treat anticipation differently. In the United States, the federal rules and circuit case law set the standard; in the United Kingdom, the Civil Procedure Rules and Practice Direction on disclosure impose a similar preservation duty once proceedings are contemplated. Confirm the standard that applies to your venue with counsel rather than assuming the U.S. rule travels.

Practical rule for management: when the first credible signal appears, start a hold log with the date, the source, and the systems touched. That log becomes your defense if anyone later questions when preservation began.

Suspend or Exempt: What to Do With Auto-Delete, Backup Rotation, and Retention Schedules

This is the heart of the answer. The most effective action management can take is to suspend or carve out every automated deletion process that touches the relevant data. That means the email retention policy, the document management system's version pruning, the backup tape rotation, and any "delete after X days" rules in collaboration tools.

Two approaches work, and the choice depends on scope and technical capability.

The verdict: use custodian exemption when the hold names people and systems precisely, and full suspension when scope is still being determined. For backups, always extend retention rather than relying on restore — many backup systems overwrite on a fixed cycle that no one monitors.

Microsoft 365, Google Workspace, and most enterprise platforms offer native preservation features — in-place holds, retention labels, or litigation-hold flags — that let you preserve without moving data. Confirm the exact feature name and behavior in your platform's current admin documentation, because interfaces change.

Management should assign one named owner to verify the suspension actually took effect. A policy change that was scheduled but not confirmed is not a suspension.

Putting Custodians on Notice: The Written Hold Notice Management Must Send and Track

A hold notice is management's instruction to individuals to stop deleting and start preserving. It should be in writing, sent promptly, and tracked for acknowledgment. The notice names the matter (by code if privileged), the categories of records, the date range, the systems covered, and the instruction not to delete, alter, or remove data.

Send it to custodians and to their managers. Managers often control shared drives and team channels that custodians forget. Include IT and records staff, because they operate the deletion systems.

Track acknowledgments in a log with names, dates, and any follow-up. If a custodian is on leave or has left the company, note the alternate preservation step — suspending their account rather than letting it be deprovisioned and wiped.

Remind custodians periodically. A single notice sent once and never repeated is weaker than a documented series of reminders, and courts have noted the difference.

The Management Action Sequence: Seven Steps From Hold Receipt to Verified Preservation

Here is the operating sequence management should run, in order, once a hold is received.

1: Log receipt and notify counsel the same day. Record the date, time, sender, and scope stated in the hold. 2: Identify custodians, systems, and date range. Pull the names, repositories, and time window from the hold; flag gaps for counsel. 3: Suspend automated deletion. Disable or exempt the relevant retention jobs, backup rotation, and auto-delete rules; record who made the change and when. 4: Apply platform preservation features. Turn on in-place holds or retention labels for the named custodians and systems. 5: Issue written hold notices. Send to custodians, managers, IT, and records staff; require acknowledgment. 6: Confirm preservation with a technical check. Have IT verify that a sample of relevant data is actually preserved and that deletion jobs are off. 7: Set a review cadence. Re-check suspensions and reminders on a scheduled interval until counsel releases the hold.

If a step fails — a deletion job restarts after a system update, or a custodian's account is deprovisioned — escalate to counsel immediately, document what was lost and when, and preserve the logs showing the failure. Courts weigh good-faith, documented remediation differently from silent loss.

Confirming the Freeze Actually Holds: Technical Verification and the Failure Modes That Break It

A suspension that was ordered is not a suspension that works. System updates, new retention policies pushed from a central console, and account lifecycle automation can all silently undo a hold. Verification is a technical check, not a policy assertion.

Three failure modes recur. First, a retention policy update overwrites the exemption. Second, a departing employee's mailbox is deprovisioned and purged on the standard schedule because HR did not know about the hold. Third, a backup rotation completes before the retention extension is applied.

Test the freeze: have IT confirm that a known relevant item — a specific email or document — is still present and not scheduled for deletion. Repeat the check after any platform change. Document each verification with a date and the person who ran it.

If a failure occurs, preserve the audit logs showing the deletion and the remediation. Counsel needs those logs to assess exposure, and they are themselves potentially relevant evidence.

Shared Drives, Mobile Devices, and Chat: The Records Managers Forget

The obvious repositories — email and document management — usually get frozen. The forgotten ones cause the losses. Team chat channels, shared drives, personal cloud accounts used for work, mobile devices, and messaging apps that auto-delete are all common gaps.

Collaboration platforms increasingly have their own retention controls, and some default to short deletion windows. Management should confirm the setting for each platform in use and not assume the enterprise email hold covers chat.

Mobile devices need a separate step: confirm whether the device is managed, whether messages are backed up, and whether the employee uses personal messaging for work. If they do, counsel should decide how to preserve, and management should not instruct employees to delete anything.

Personal cloud accounts are the hardest. Management can instruct custodians not to delete and to preserve, but technical control may be limited. Document the instruction and the custodian's response.

When the Hold Can Be Released: Counsel-Controlled Release and Post-Matter Cleanup

Management does not release a hold. Counsel does, in writing, after the matter is resolved — settlement, dismissal, judgment, or expiration of the preservation duty. Until that written release arrives, every suspension stays in place.

On release, management should reverse the steps methodically: lift platform holds, restore retention schedules, end backup extensions, and notify custodians that normal deletion may resume. Document the release date and the systems changed.

Do not release early to save storage cost. Premature release reopens the deletion risk and can look like bad faith if the matter reignites. Storage is cheaper than spoliation exposure.

Post-matter cleanup should also capture lessons: which systems were missed, which suspensions failed, and what the next hold should do differently.

Cost, Time, and the Storage Trade-Off Management Has to Budget For

Preservation has a cost, and management should budget for it rather than discover it. The main drivers are storage growth from suspended deletion, IT labor for verification, and legal review time for scoping.

Storage growth is the variable that surprises organizations. A full suspension of email deletion across a large user base can multiply retained data over months. The exact cost depends on your platform's storage pricing, which changes; confirm current rates with your provider rather than budgeting from memory.

Time is the other cost. The seven-step sequence above can run in days for a narrow hold and weeks for a broad one. The technical verification step is the one most often skipped under time pressure, and it is the one that catches silent failures.

A defensible budget line: assign an owner, a verification cadence, and a storage estimate at the start of every hold, and review them monthly until release.

Common Management Mistakes That Create Spoliation Exposure

The first mistake is assuming IT will handle it. IT operates systems; management owns the instruction to preserve and the follow-through. Without a named owner, suspensions drift.

The second is over-reliance on backups. Backups are for disaster recovery, not for preserving a specific matter, and rotation can overwrite relevant data before anyone restores it.

The third is a notice sent once. Periodic reminders and tracked acknowledgments are the documented practice courts expect.

The fourth is silence after a failure. A deletion that happens despite a hold should be escalated and documented, not quietly remediated. The log is the defense.

FAQ

How fast must management act after receiving a litigation hold? Same day for logging and notifying counsel, and within days for suspending deletion. The exact deadline depends on your venue and the hold's scope, so confirm with local counsel. The trigger date may predate the letter, which makes speed matter more.

Does an IT backup count as preservation for a litigation hold? No, not by itself. Backups rotate and can overwrite relevant data, and restoring from backup is not the same as preserving in place. Extend backup retention as a supplement to platform holds, not as a substitute.

What happens if records are deleted despite a hold? Counsel must be told immediately, and the audit logs showing the deletion and any remediation should be preserved. Under Federal Rule of Civil Procedure 37(e), a court can order curative measures, and intentional loss can lead to an adverse-inference instruction or dismissal. The outcome depends on the venue and the facts.

Can management release a litigation hold once the trial ends? Only counsel can release a hold, in writing, after the matter is fully resolved — including any appeals or related proceedings. Management's role is to keep suspensions in place until that written release arrives and then reverse them methodically.

Does a litigation hold cover chat messages and shared drives? It should, if they may contain relevant records. Chat and shared drives are commonly missed because they sit outside email retention. Confirm the retention setting for each collaboration platform in use and apply preservation features there too.

Is suspending deletion organization-wide better than exempting named custodians? Full suspension is safer when scope is unknown; custodian exemption is more efficient when the hold names people and systems precisely. Either way, verify technically that the freeze took effect. The wrong choice is assuming a policy change worked without checking.

How much does preservation cost while a hold is active? Costs come from storage growth, IT verification labor, and legal review time. Storage pricing varies by platform and changes over time, so confirm current rates with your provider. Budget an owner, a cadence, and a storage estimate at the start of every hold.

What if a custodian leaves the company during a hold? Suspend the account rather than letting standard deprovisioning purge it. Notify counsel and document the alternate preservation step. HR and IT should check the hold log before any offboarding action.

This article is general educational information, not a legal opinion or a compliance guarantee. Litigation-hold and preservation duties vary by jurisdiction, venue, and the facts of your matter. Consult qualified local counsel before suspending, releasing, or altering any preservation step, and follow your organization's records-retention and legal-hold policies.