banner-why-daymark.jpg

Information Technology Navigator

Tips, Advice & Insights from Technology Pros

Legal Hold 101: Data Retention and Destruction

Posted by Steve O'Neill, Esq.

Wed, Oct 14, 2015


Every gambler knows
That the secret to survivin'
Is knowin' what to throw away
And knowin' what to keep
'Cause every hand's a winner
And every hand's a loser
And the best that you can hope for is to die
In your sleep

- The Gambler lyrics © Sony/ATV Music Publishing LLC

Some of the more frequent questions asked of eDiscovery attorneys when teaming with IT professionals on archiving and other retention policy projects, relate to the timing, scope and especially the release of legal holds. Misconceptions about “Legal Hold” abound, many of them (unfortunately) coming from litigation attorneys stuck in the paper document past or those who do not understand data systems architecture. One common source of overbroad Legal Hold retention is the misapprehension of the risk of severe judicial sanctions for the destruction (aka spoliation) of evidence.

Too many attorneys take what they consider to be the safe route and continue to advise enterprises to keep too much for too long. As Kenny Rogers’ Grammy award-winning song reminds us, risk can cut both ways. Not only does an overbroad legal hold increase the cost of data storage and maintenance, it increases the cost of legal review of held documents, and may result in retaining “smoking gun” documents that could have been legitimately deleted before or between legal holds. You’ve gotta know when to fold ‘em too!

“Misconceptions about “Legal Hold” abound, many of them (unfortunately) coming from litigation attorneys stuck in the paper document past or those who do not understand data systems architecture.”


Legal hold is a term that has developed over the last fifteen or so years. It is also commonly known as litigation hold. “The use of a ‘litigation hold’ as a means to satisfy preservation obligations was popularized by the 2003 decision in Zubulake v. UBS Warburg (Zubulake IV). The court suggested that ‘[o]nce a party reasonably anticipates litigation, it must suspend its routine document retention/destruction policy and put in place a ‘litigation hold’.’” (The Sedona Conference Commentary on Legal Holds: The Trigger and the Process, 2010) (“Sedona Commentary”) The Sedona Conference is an organization that has been at the forefront of developing standards and best practices to defensibly manage the ever growing explosion of what is now defined by the federal courts as Electronically Stored Information (“ESI”). (See www.thesedonaconference.org) Early recommendations and guidelines published by The Sedona Conference were so influential that their concept of eDiscovery “proportionality” was incorporated in the upcoming December 1, 2015 changes to the Federal Rules of Civil Procedure (“FRCP”).


Legal Hold 101

The need for a Legal Hold arises out of the duty to preserve information for legal purposes – litigation, government investigation, or audit. The 2007 Sedona Commentary described it in two simple sentences:

The duty to preserve information includes an obligation to identify, locate, and maintain, information that is relevant to specific, predictable, and identifiable litigation. When preservation of electronically stored information (“ESI”) is required, the duty to preserve supersedes records management policies that would otherwise result in the destruction of ESI. A “legal hold” program defines the processes by which information is identified, preserved, and maintained when it has been determined that a duty to preserve has arisen. - Sedona Commentary, 2007 Public Comment Version, p.1

The Sedona Guidelines for Managing Information & Records in the Electronic Age provide an excellent reference point for organizations seeking to develop or improve their legal hold program. Guideline No. 5 states:

An organization’s policies and procedures must mandate the suspension of ordinary destruction practices and procedures as necessary to comply with preservation obligations related to actual or reasonably anticipated litigation, government investigation or audit.

a. An organization must recognize that suspending the normal disposition of electronic information and records may be necessary in certain circumstances.

b. An organization’s information and records management program should anticipate circumstances that will trigger the suspension of normal destruction procedures.

c. An organization should identify persons with authority to suspend normal destruction procedures and impose a legal hold.

d. An organization’s information and records management procedures should recognize and may describe the process for suspending normal records and information destruction and identify the individuals responsible for implementing a legal hold.

e. Legal holds and procedures should be appropriately tailored to the circumstances.

f. Effectively communicating notice of a legal hold should be an essential component of an organization’s information and records management program.

g. Documenting the steps taken to implement a legal hold may be beneficial.

h. If an organization takes reasonable steps to implement a legal hold, it should not be held responsible for the acts of an individual acting outside the scope of authority and/or in a manner inconsistent with the legal hold notice.

i. Legal holds are exceptions to ordinary retention practices and when the exigency underlying the hold no longer exists (i.e., there is no continuing duty to preserve the information), organizations are free to lift the legal hold. The Sedona Guidelines: Best Practice Guidelines & Commentary for Managing Information & Records in the Electronic Age, (2nd Ed., 2007)


Three Key Takeaways on Legal Hold

The key takeaways from these Guidelines are:

  1. The assumption as a fact that it is legally defensible for organizations to automatically destroy data/documents at the end of their information life cycle and that Legal Holds are an exception to normal document retention/destruction policies.
  2. Legal Holds should be tailored to the circumstances, i.e., not over-broad.
  3. When the underlying trigger for the hold no longer exists (according to legal counsel), the organization can (and should) lift the Legal Hold and take steps to dispose of held documents as if they were never impacted by a Legal Hold.

“Legal Holds should be tailored to the circumstances, i.e., not over-broad.”


The growing knowledge-base of best practices, industry standards, updated court rules intended to limit sanctions and case law all lead to defensible solutions for carving back the scope and length of legal holds, as well as the ability to release documents and records back into their normal retention/destruction schedules.

Legal Hold policies and procedures can be implemented using currently existing technology for archiving and document management. These technologies can reach most unstructured information within the enterprise including email, SharePoint, file shares, PST files and many cloud computing solutions.

With a robust system and procedures in place to implement Legal Hold, unneeded documents and data (not covered by Legal Hold) can be automatically disposed of according to the organization’s records retention schedule – taking the gamble out of Legal Hold.

Download Steve's whitepaper, C-Level Guide to Covering Your Information Governance Assets, to learn how to create a legally defensible automated deletion / destruction policy.

info-governance-c-level-guide