Summarizing a 30(b)(6) Deposition: 4 Things to Track

When a party notices a corporation, agency, or other entity for deposition, the organization does not send whoever happened to be there. It designates a person to speak for it on the matters the notice describes, and that person's answers are the organization's answers. That is what makes a 30(b)(6) deposition different from any individual deposition, and it is why summarizing one the same way you would summarize a fact witness misses the point. The document is a record of what the company committed to, topic by topic.

Here is the grounding. Under Federal Rule of Civil Procedure 30(b)(6), the notice or subpoena must describe the matters for examination with reasonable particularity, and the organization designates one or more people to testify about information known or reasonably available to it. Their testimony represents the organization, not just their own recollection. A deposition summary condenses that testimony into a shorter, organized document with references back to the page and line, and for a corporate representative deposition, it has to be organized around the matters the notice actually listed.

Track 1: organize it by noticed topic, not just by page

A 30(b)(6) notice is a list of matters, and the deposition exists to cover them. So the most useful thing a summary can do is show each noticed matter with the testimony that answered it gathered in one place, cited to the page and line. Questioning rarely follows the notice in order, and a single topic can surface three times across a long transcript, so a page-by-page summary leaves the team reassembling it themselves. Organizing by matter is the same discipline behind a summary built to fit the type of deponent, applied to the entity deposition: the format follows how the testimony will be used.

Track 2: who is speaking, the company or the person

A designee answers in two registers, and the summary should keep them apart. Some answers are the organization's position on a noticed matter. Others are the individual's own knowledge, or the limits of it, offered in passing. Those are not the same thing, and conflating them changes what the deposition means. A summary that notes when the witness is stating the company's position, cited, and when they are speaking only for themselves, lets the team rely on the binding answers without mistaking a personal aside for a corporate commitment.

Track 3: the topics the designee could not answer

On an individual deposition, an "I do not know" is one witness reaching the edge of memory. On a 30(b)(6), a designee who cannot answer a noticed matter is a different kind of event, because the organization was supposed to prepare someone who could. Whether that gap matters is for the attorney to decide, but the summary has to make it visible: here is the noticed topic, and here is where the designee could not speak to it, cited. That is why capturing the answers that are not really answers matters even more here than on a fact witness.

Track 4: the binding positions, cited

The reason a corporate representative deposition is worth taking is that the answers commit the entity. When the designee states the company's position on a matter, that answer can be used against the organization later, so the summary should capture each binding position plainly and tie it to the page and line it came from. A summary built this way lets the team find the company's own words on a topic in seconds, the same way a summary built to lead back to the exact testimony supports every other use of the record.

Where the entity deposition needs a human read

Organizing a 30(b)(6) transcript by topic is a place AI helps and still needs a reviewer. A tool can group testimony under headings and attach page-line references faster than a person reading straight through. What it cannot reliably do is match scattered answers to the exact matter in the notice, tell a binding corporate position from a personal aside, or recognize when a designee has quietly failed to cover a noticed topic. Those calls take a reviewer who has the notice in hand and reads the testimony against it. The tool sorts the transcript; the reviewer maps it to what the deposition was actually noticed to cover.

One boundary holds this together. A deposition summary organizes the testimony by matter, cites it to the page and line, separates the company's position from personal knowledge, and flags where a noticed topic went unanswered. It does not decide whether the designee was adequately prepared, whether a gap warrants a motion, or what any admission proves. Those are the attorney's calls and the court's. The summary makes the entity's testimony traceable and usable; the strategy built on it belongs to counsel.

A corporate representative deposition is the organization speaking on the record, one noticed matter at a time. A summary that tracks it that way, by topic, by who is speaking, by what went unanswered, and by what binds, is what turns a long entity transcript into something a team can actually work from.

A 30(b)(6) deposition is the company on the record, and its summary has to reflect that. Organize it by the noticed matters, not just the page order, so every topic has its coverage in one place. Keep the company's position separate from the witness's own knowledge. Flag the noticed topics the designee could not answer, because that gap is a finding. And capture the binding positions, cited, since those are the answers that commit the entity. Track those four, and a long corporate transcript becomes a document the team can actually use.

Want a 30(b)(6) deposition summarized by the matters that were noticed, with the binding positions cited to the line? Partner with LezDo TechMed, or estimate a summary to see how it is handled. For the full method behind it, see our guide to drafting a deposition summary.