The Litigation Hold and Who Must Receive It

The hold notice is the point at which a legal conclusion becomes an operational instruction. Someone has decided that litigation is anticipated; the notice tells named people what that means for the files on their laptops and the messages in their mailboxes. It is a short document, rarely more than two pages, and it is examined line by line whenever evidence goes missing.

What the notice actually does

A hold does two things that nothing else in the process does. It communicates a specific instruction to the individuals who hold relevant material, and it creates a record that the instruction was given. Neither is required by rule. Rule 37(e) asks only whether reasonable steps were taken, and a hold is the ordinary way of demonstrating that they were.

The instruction is negative rather than positive. Custodians are told to stop routine destruction, not to gather material and send it anywhere. Collection is a separate exercise conducted under controlled conditions, and asking employees to forward copies of their own files tends to produce altered metadata and incomplete sets. The notice should make that division explicit so that a well-meaning recipient does not begin sorting files.

The second function matters more than it appears. An organization defending its preservation effort has to describe what it did, and a documented notice with a distribution list answers most of that question at once. Without one, the defense rests on recollection, which does not survive cross-examination well.

Identifying who must receive it

Custodian identification is the step most often criticized, because a person left off the list keeps deleting. The starting point is the people who participated in the events underlying the dispute, but the list rarely stops there. Supervisors who reviewed decisions, assistants who kept calendars, and departed employees whose accounts still exist all hold material that a narrow list misses.

The list is not fixed at the outset. Discovery routinely reveals a team nobody thought of, and courts have treated the failure to add custodians once their relevance became obvious as a distinct failure. Revisiting the list at intervals is part of maintaining the hold, and the revision history is itself useful evidence of diligence.

What a notice needs to contain

There is no prescribed form, and a notice loaded with legal recitation is less effective than a plain one. What recipients need is the subject matter in terms they recognize, the categories and date ranges involved, the systems it covers, and an unambiguous statement that ordinary deletion stops. A named contact for questions prevents individual guesswork about edge cases.

The most common defect is abstraction. A notice referring to "all documents relating to the matter" gives an employee no way to decide whether a particular thread is covered. Naming projects, products, accounts and counterparties converts the instruction into something a person can apply without judgment calls, and it narrows the argument later about what the notice reasonably conveyed.

Format matters for the same reason. A notice buried in a long attachment sent to a distribution list competes with everything else in a mailbox. Organizations that treat the hold as an operational instruction rather than a legal memorandum — short, direct, sent from a name recipients recognize — generally get better compliance, and compliance is the only thing the reasonable-steps test measures.

Overbreadth carries its own cost. A notice that sweeps in every system and every employee is easy to write and impossible to maintain, and it invites the argument that the organization never seriously considered scope. Where a hold has to be broad at the outset because the dispute is not yet defined, narrowing it in a documented second round is better than leaving an unworkable instruction in place indefinitely.

Reminders, confirmation and supervision

A hold issued once and never mentioned again decays. People change roles, new employees join a project already under hold, and the original instruction is forgotten within a matter of months. Periodic reissue to the current custodian list is the ordinary answer, and it also forces a review of whether the list is still accurate.

Reissue is also the mechanism by which a hold keeps pace with a case. Claims are amended, new parties appear, and a dispute that began as a contract argument acquires an employment component. Each of those changes the categories that matter, and a notice that still describes the original dispute understates what is now relevant.

Acknowledgment tracking serves a related purpose. Requiring recipients to confirm receipt converts an assumption into a record, and the small number who never respond are exactly the ones worth contacting directly. Courts have not required acknowledgment as such, but they have drawn adverse conclusions where an organization could not say whether a custodian ever read the notice.

Supervision by counsel closes the loop. The reasonable-steps inquiry looks at whether anyone verified that the instruction produced the intended result — that deletion actually stopped, that the departing employee's laptop was not reimaged, that the shared drive was not archived and purged. Verification is also the natural moment to begin a controlled collection of the material now frozen in place.

Proving the hold in a later dispute

When preservation is challenged, the organization is usually examined through a deposition of a designated representative under Rule 30(b)(6). The witness is asked when the duty was recognized, who decided the scope, which custodians were identified and on what basis, and what was done to confirm compliance. Those are questions about process, and they are answered from records or not at all.

The material that answers them is the distribution list, the acknowledgment log, the administrator ticket suspending retention, and the revision history of the custodian list. Whether the notice itself must be produced varies, but the surrounding facts are generally discoverable regardless. An organization that can lay out the sequence from the point litigation became foreseeable to the last reminder is defending a documented process; one that cannot is defending a recollection. The same records govern the far less examined question of when the hold is allowed to end.