A deposition under Federal Rule of Civil Procedure 30(b)(6) directed at a company's electronically stored information (ESI) is one of the most consequential—and most underestimated—events in modern litigation. The organization, not the witness, is on the record, and the testimony binds the company. When the noticed topics reach into data architecture, preservation efforts, and collection methodology, an unprepared designee can manufacture admissions about spoliation, gaps in legal holds, or flawed search protocols that opposing counsel will replay for the rest of the case. Selecting and preparing the right witness is therefore a strategic exercise, not a clerical one.
Scope the Notice Before You Pick the Witness
Preparation begins with the notice itself. Rule 30(b)(6) requires the requesting party to describe the matters for examination "with reasonable particularity," and the responding organization must designate one or more people to testify about information "known or reasonably available" to it. Litigators should read each topic line by line and translate vague phrasing—"the company's document retention practices," "all efforts to preserve relevant data"—into the concrete systems, custodians, and time periods it actually implicates.
This reading drives two early decisions. First, whether to negotiate or object. Overbroad ESI topics, topics that demand a witness recite every server configuration, or topics that intrude on privileged collection strategy are candidates for a meet-and-confer or a protective order. The amended Rule expressly obligates the parties to confer in good faith about the matters for examination, and that conference is the place to narrow scope before a witness ever sits down. Second, the topic map tells you how many designees you need. A single person rarely understands IT infrastructure, records management, and the litigation hold equally well, and there is no requirement to force everything onto one set of shoulders.
Choose a Knowledgeable Designee, Not Just a Convenient One
The instinct to designate the most senior IT executive, or conversely the most articulate paralegal, often backfires. The right designee is the person who can speak credibly to the specific topics—or who can be educated to do so within the time available. For ESI testimony that usually means someone fluent in the company's email environment, file shares, collaboration platforms, mobile and messaging tools, backup and archiving systems, and the lifecycle of data through retention and deletion.
Just as important is the witness's relationship to the preservation effort. A designee who personally issued or monitored the litigation hold can testify from knowledge about when the duty to preserve attached, who received hold notices, and how compliance was tracked. Where no single person holds that knowledge, counsel must assemble it and prepare the witness to testify on the organization's behalf. The witness need not have personal involvement in every fact, but the company must make a conscientious, good-faith effort to educate the designee so the testimony genuinely reflects what the organization knows.
Prepare on Architecture, Preservation, and Collection
Effective preparation is substantive and rehearsed. Walk the designee through the data ecosystem until they can describe, in plain language, where relevant ESI lives and how it moves. Cover the systems in scope, retention schedules, auto-deletion settings, and any auto-archiving that might have affected potentially relevant material.
On preservation, the witness should be ready to explain the timeline: when litigation became reasonably anticipated, when holds issued, their scope, how they were communicated and reaffirmed, and what was done to suspend routine deletion. On collection, prepare them to describe who collected what, the tools and methods used, whether collection was forensically sound and defensible, and how completeness was verified—without volunteering privileged strategy or attorney work product. Run a mock examination so the designee learns to answer only the question asked, to say "I don't know but the company would have to determine that" when appropriate, and to resist the temptation to speculate or to defend the company argumentatively.
Avoid the Common Pitfalls
The recurring failures are predictable. Designees guess at technical details and create false admissions; they conflate personal knowledge with the company's position; they over-answer and open new lines of inquiry; or they were never genuinely educated, exposing the organization to a motion that the designation was inadequate. Counsel should also avoid designating a witness who cannot keep privilege and facts separate, and should confirm before the deposition that every noticed topic has a prepared, knowledgeable voice behind it.
How Law & Forensics Helps
Law & Forensics works alongside litigation teams to make 30(b)(6) ESI testimony defensible. Our forensic and e-discovery experts map the data environment, pressure-test preservation and collection narratives, identify and remediate gaps before the deposition, and prepare designees to testify accurately about complex technical systems—so the testimony that binds your client is the testimony you intended.