Preparing a 30(b)(6) Witness on ESI Preservation

The notice comes with an attachment, and the attachment is the problem. Twenty-two topics, and topics nine through nineteen have nothing to do with the merits: your document retention policies, the date the litigation hold issued, the systems placed on hold, the custodians identified, the sources not collected, and the reasons for each. This is discovery about discovery, and the witness who answers it speaks for the company.

Counsel who have never sat through one tend to treat it as a procedural formality delegated to whoever is available. It is closer to the opposite. A corporate designee's testimony on preservation is frequently the evidentiary foundation for the spoliation motion that follows, and it is assembled from your own witness's answers.

What the notice usually demands

ESI topics have converged on a recognizable set. Expect some version of:

• Document retention and destruction policies, including auto-delete settings and their configuration history.
• When the company first anticipated litigation, and who made that determination.
• The litigation hold: its date, its recipients, its scope, its text, and how compliance was monitored.
• The company's data sources and where responsive information resides.
• Custodian identification, including who was considered and not selected.
• Collection methodology, search terms, and any use of technology-assisted review.
• Data known to be lost, deleted, or unavailable, and the circumstances.

Two things about that list are worth noticing. The topics are not merits topics, so the witness who knows the case best is often the wrong witness. And the last item is written by someone who already suspects an answer.

Negotiate the topics before you designate anyone

Since December 2020, Rule 30(b)(6) has required the serving party and the organization to confer in good faith about the matters for examination, before or promptly after service. That obligation is leverage, and it is routinely underused.

The topics worth pushing back on share a shape: they are unbounded in time, unbounded in scope, or written to require the witness to have memorized documents. "All document retention policies" across a company with two decades of history is not a topic a human being can prepare for. "The retention policies applicable to the six custodial email accounts at issue, from January 2023 forward" is.

Three moves that tend to work:

• Bound every topic by time and system. Most over-broad topics are conceded to a reasonable scope once the other side has to articulate why they need 2011.
• Split operational topics from legal ones. A topic that asks why counsel scoped the hold as they did is aimed at privileged territory. Reach an understanding about the line before the deposition, not during it, and confirm it in writing.
• Offer substitutes. A stipulation, a written interrogatory response, or a declaration will often satisfy a topic more cheaply than a designee. Opposing counsel who refuses every substitute is telling you what the deposition is really for.

What you cannot do is designate a witness, let them fail, and then argue the topic was too broad. Courts hear that argument after the fact and are rarely persuaded by it.

The testimony binds the company

This is the part that surprises people. A 30(b)(6) designee is not giving personal recollection. The witness is speaking for the organization, and the organization's obligation runs to information known or reasonably available to it, not to whatever the designee happens to remember.

Courts have enforced that obligation firmly. In Great American Insurance v. Vegas Construction Co., 251 F.R.D. 534 (D. Nev. 2008), the court held that the duty to prepare a designee extends beyond matters personally known to the witness, that a corporation no longer employing anyone with knowledge of the events is not thereby relieved of the duty, and that preparation must draw on documents, former employees, and other available sources. The designee there had not read the notice in full and had done nothing to prepare. The court awarded expenses and ordered a further deposition.

The consequences reach past the deposition. In QBE Insurance v. Jorda Enterprises, Inc., 277 F.R.D. 676 (S.D. Fla. 2012), a case where the ESI and document-retention topics were sought precisely because the opposing party was advancing a spoliation theory, the court precluded the corporation from taking positions at trial, including through testimony and exhibits, on issues its designee had been unable to address. The opinion also collects the rule that a designee's legitimate lack-of-knowledge answer is itself the corporation's answer, and that the corporation will not later be permitted to change it by introducing contrary evidence at trial.

Read that against a preservation record. If your designee cannot say when the hold issued, the company has testified that it does not know when its hold issued — and it may be stuck with that when the Rule 37(e) motion arrives six weeks later.

Choosing the designee

The instinct is to send the general counsel, because the GC knows the answers. That is usually the wrong call. The GC's knowledge of preservation decisions is bound up with privileged deliberations, which turns every answer into a waiver assessment made under time pressure, in a chair, on the record. It also converts your senior legal officer into a fact witness in a case they are supposed to be supervising.

The opposite instinct fails differently. The IT director can describe retention settings and mailbox holds with precision and has no idea when litigation was first anticipated, who decided to exclude the sales team's phones, or what the notice said. Roughly half the topics are legal-process topics and half are technical, which is why the single-designee reflex breaks down.

Rule 30(b)(6) is more flexible than most parties use it. The rule does not require the "most knowledgeable" person, does not require the designee to have personal knowledge, and does not limit the designee to the organization's own employees — points the court in QBE made at length while noting that lawyers demand a "person most knowledgeable" the rule has never mentioned. What the rule requires is a designee prepared on the designated matters.

In practice, the workable answers are usually one of these. Designate two or three witnesses and allocate the topics between them explicitly, in writing, before the deposition. Or designate the person who actually administered the hold — often a litigation support manager, discovery counsel, or paralegal supervisor — and educate them on the technical topics from the systems team. Whoever it is, they need authority to speak for the company and enough distance from the underlying strategy that privilege is not in play on every third question.

How preparation actually works

Preparation for this deposition is not a two-hour session the day before. It is the assembly of three artifacts, and the witness sessions come after they exist.

The preservation timeline. A single dated chronology: the trigger event, the trigger determination and who made it, the hold notice and its distribution, acknowledgements, re-issuances, deletion suspensions with their ticket numbers, custodian additions, collections, and departures. The witness should be able to walk it forward and backward. Nearly every damaging answer in these depositions is a date the witness could not supply.

The data map. What systems exist, what lives in each, what the retention setting is, and which were placed on hold. If your organization maintains a current data map, this is a review exercise. If it does not, the deposition will discover that, and the discovery will happen in front of a court reporter.

The not-collected list. The most important document and the one nobody prepares. For every source in scope that was not collected, one line: the source, the decision, the decision-maker, the date, and the reason. Preservation choices are defensible; unexplained preservation choices are not. A witness who can say "we excluded the archived 2019 file share because the parties agreed in the ESI protocol that the relevant period began in 2021, and here is that paragraph" has closed a line of questioning. A witness who says "I'm not sure why that wasn't collected" has opened one.

Only then do you run the sessions, and the sessions should include a genuine cross-examination by someone who did not build the timeline.

The 30(b)(6) ESI questions that catch unprepared witnesses

Experienced examiners work a short list, because it works. Your designee should have heard each of these before the deposition:

• "When did the company first anticipate this litigation?" The answer sets the preservation clock, and a date later than the documents support is worse than an unhelpful date that the documents support.
• "What did the hold notice actually say?" Not its gist. Its scope, its data types, its instructions. If the notice never named mobile messaging, the follow-up is already drafted.
• "Who decided to exclude that source?" A named decision-maker with a stated reason is a proportionality judgment. A shrug is an unexplained gap.
• "How do you know the auto-delete was actually turned off?" This separates instruction from verification. Many companies asked; fewer confirmed.
• "Which custodians never acknowledged the hold, and what did you do about it?" Acknowledgement gaps are ordinary. Unaddressed acknowledgement gaps are not.
• "What happened to the data of the four custodians who left during this case?" Departed-employee accounts are where preservation programs most often fail quietly.
• "Is the company aware of any responsive data that no longer exists?" The setup for everything that follows, and the answer has to be accurate.

None of these are trick questions. They are the questions a competent adversary asks because the answers are usually available to a prepared witness and usually not available to an unprepared one.

"I don't know" and "the company has no record" are not the same answer

This distinction deserves its own drilling, because witnesses collapse the two constantly and the difference is substantial.

"I don't know" is a statement about the witness. It tells the examiner that the designee was not prepared on a noticed topic, which is a Rule 30(b)(6) failure attributable to the company. It supports a motion to compel a further deposition at your client's expense, and in the right circumstances it supports preclusion — the QBE outcome.

"The company has no record of that" is a statement about the organization, and it is a legitimate answer when it is true and when the search behind it was real. The follow-up will be immediate and should be welcome: what did you do to find out? The answer needs to be specific. "I reviewed the hold file, the ticketing system, and the retention configuration history, and interviewed the two administrators who managed that system in 2024" is a defensible answer that closes a topic.

The trap in between is the confident guess. A designee who estimates a hold date to avoid looking unprepared has bound the company to an estimate that opposing counsel will compare against the documents. Being wrong is materially worse than being incomplete, because the record then contains a corporate statement that turned out to be false, and that fact becomes an argument about candor rather than about preservation.

What a Rule 30(b)(6) ESI deposition is really testing

A 30(b)(6) deposition on ESI is a compliance audit conducted by an adversary, on the record, with no opportunity to go back and fix what it finds. The witness is the interface, but the thing being examined is the program behind them.

Which is why the preparation window is the wrong place to discover that the trigger date was never written down, that nobody confirmed the auto-delete suspension, or that the reason a source was excluded lives only in a former colleague's memory. A hold process that generates dated records as it runs makes this deposition a retrieval exercise. Without one, preparation becomes an investigation of your own client, on a schedule set by the other side, with the answers due under oath.

If a notice with ESI topics is already on your desk, start with the not-collected list — it is the artifact most likely to be missing and the one the examiner will press hardest. If one is not, the same list is worth building for every active matter, while it can still be assembled calmly.