Deposition Summary Template + 3 Worked Sample Summaries
The Short Answer
A deposition summary is a citation-keyed digest of a transcript, and there are three formats worth knowing: page-line (a table that walks the transcript in order), topical (testimony regrouped by subject), and narrative (prose that tells the testimony as a story). Below is a template you can copy, three fully worked samples of one illustrative deposition in each format, and the Claude prompts that produce each one from a transcript in a few minutes, with the verification step that makes the output usable.
One note before the samples. The deposition used throughout this post is fictional, invented for teaching purposes. The parties, witness, facts, and page:line citations are illustrative and do not describe any real case, person, or company.
The Three Formats, and When Each One Earns Its Keep
- Page-line summary. A table: page and line range on the left, a neutral condensation on the right, in transcript order. The workhorse format for motions, impeachment, and cross outlines. If you produce only one, produce this one.
- Topical summary. Testimony regrouped under subject headings with citations after each point. A fact mentioned on pages 12, 48, and 131 gets one entry. Best for comparing witnesses subject by subject.
- Narrative summary. Prose with citations in parentheses. Best for client updates, mediation statements, and briefing a colleague. Weakest for impeachment, because prose hides the gaps a table exposes.
The practical sequence: generate page-line first, verify it, and derive the other two from the verified table, so citations are checked once and reused three times.
Deposition Summary Template
Copy the header block and the table into your firm's document template. The header is the same for every format; only the body changes.
| Field | Entry |
|---|---|
| Matter | [Caption and case number] |
| Deponent | [Name, role, party affiliation] |
| Date and location | [Date; in person or remote] |
| Examining counsel | [Name and party] |
| Defending counsel | [Name and party] |
| Transcript length | [Pages; e.g. 1-142] |
| Exhibits marked | [Exhibit numbers and one-line descriptions] |
| Errata | [Received / pending / waived] |
| Summary format | [Page-line / topical / narrative] |
| Prepared by / verified by | [Name, date; verifier initials on cite spot-check] |
Page-line body:
| Page:Line | Testimony summary | Exhibit / flag |
|---|---|---|
| [p:l-p:l] | [Neutral condensation. No characterization of credibility. Quote verbatim only where the exact words matter.] | [Ex. no.; ADMISSION / INCONSISTENT / OBJECTION / FOLLOW-UP] |
Topical body: [Heading] followed by bullet points, each ending with a citation in the form (12:4-13:2).
Narrative body: paragraphs in chronological or thematic order, with a citation after each factual assertion.
The third column is the part most templates omit. A fixed flag vocabulary (ADMISSION, INCONSISTENT, OBJECTION, FOLLOW-UP) lets you filter the table later instead of rereading it.
The Illustrative Matter Used in the Samples
Fictional, for illustration only. Hartwell v. Meridian Freight Logistics, LLC, a premises-liability action: a delivery driver alleges he was struck by a forklift on a warehouse loading dock. The deponent is Daniel Okafor, the defendant's second-shift dock supervisor, deposed by plaintiff's counsel. Transcript pages 1-118. Exhibits: Ex. 4 (dock safety policy), Ex. 7 (incident report), Ex. 9 (training log). Every page:line reference is invented to match this fictional transcript.
Sample 1: Page-Line Summary
| Page:Line | Testimony summary | Exhibit / flag |
|---|---|---|
| 6:2-8:14 | Background. Okafor has been employed by Meridian for six years, the last three as second-shift dock supervisor. Supervises eight to eleven dock workers and two forklift operators per shift. | |
| 11:5-13:20 | Describes the dock layout. Confirms a painted pedestrian walkway runs along the north wall and that visiting drivers are "supposed to" stay inside it. Cannot recall when the paint was last refreshed. | FOLLOW-UP |
| 17:9-19:3 | Identifies Ex. 4 as the dock safety policy in effect on the incident date. Agrees the policy requires forklift operators to sound the horn at blind corners and to yield to pedestrians. | Ex. 4; ADMISSION |
| 22:14-24:8 | Training. Testifies new forklift operators receive a classroom session and a supervised shift. Does not know whether the operator involved, Reyes, completed the supervised shift; refers to the training log. | Ex. 9; FOLLOW-UP |
| 31:1-33:17 | Day of incident. Okafor was in the dock office when he heard shouting. Arrived at bay 6 "within a minute." Saw plaintiff on the floor near the walkway edge and the forklift stopped two to three feet away. | |
| 36:10-38:22 | States he did not see the impact. His knowledge of how it happened comes from Reyes and from two dock workers whose names he provides. | INCONSISTENT with Ex. 7 (report states supervisor "observed") |
| 41:4-43:15 | Identifies Ex. 7 as the incident report he completed that night. Agrees the word "observed" in the report is inaccurate and that he "should have written 'was informed.'" | Ex. 7; ADMISSION |
| 52:8-54:1 | Objection (form) at 52:11; witness answers. Testifies bay 6 lighting had been flagged for a burned-out fixture on a maintenance request roughly two weeks earlier; unsure whether it was repaired before the incident. | OBJECTION; FOLLOW-UP |
| 67:3-69:19 | Post-incident. Meridian repainted the walkway and installed a convex mirror at the bay 6 corner "a few weeks" after the incident. | FOLLOW-UP (subsequent remedial measure issue) |
| 88:12-90:6 | Does not know whether Reyes was disciplined. Reyes remained employed as of the deposition date. | |
| 104:2-106:15 | Defending counsel's examination. Okafor states visiting drivers are told at check-in to remain in the walkway and that plaintiff had made deliveries to the facility "many times" before. |
Sample 2: Topical Summary
Witness background and role. Six years at Meridian; second-shift dock supervisor for the last three; supervises the dock crew and two forklift operators per shift (6:2-8:14). Was in the dock office, not on the floor, at the time of the incident (31:1-33:17).
Dock layout and pedestrian walkway. A painted walkway runs along the north wall and visiting drivers are expected to stay inside it (11:5-13:20). Cannot say when the paint was last refreshed (13:8-13:20). Drivers are told at check-in to use the walkway; plaintiff was a frequent visitor (104:2-106:15).
Safety policy (Ex. 4). Authenticates Ex. 4 as the policy in effect. Agrees it requires horn use at blind corners and yielding to pedestrians (17:9-19:3).
Training (Ex. 9). Describes a classroom session plus one supervised shift for new operators. Does not know whether Reyes completed the supervised shift and defers to the training log (22:14-24:8).
The incident. Heard shouting, arrived at bay 6 within about a minute, found plaintiff on the floor near the walkway edge and the forklift stopped two to three feet away (31:1-33:17). Did not see the impact; his account is secondhand from Reyes and two named dock workers (36:10-38:22).
Incident report (Ex. 7). Authored the report that night. Concedes the report's statement that he "observed" the incident is inaccurate (41:4-43:15). Flag: inconsistency between Ex. 7 and testimony at 36:10-38:22.
Lighting at bay 6. A burned-out fixture had been flagged on a maintenance request about two weeks before; unsure whether it was repaired in time (52:8-54:1; form objection at 52:11).
Post-incident changes. Walkway repainted and a convex mirror installed at bay 6 a few weeks later (67:3-69:19). Unaware of any discipline of Reyes; Reyes still employed (88:12-90:6).
Sample 3: Narrative Summary
Daniel Okafor has worked at Meridian's warehouse for six years and has supervised the second-shift dock for the last three, overseeing the dock crew and two forklift operators each night (6:2-8:14). He described a painted pedestrian walkway along the north wall that visiting drivers are expected to use, though he could not say when it was last repainted (11:5-13:20). He authenticated the dock safety policy, Exhibit 4, and agreed it requires operators to sound the horn at blind corners and yield to pedestrians (17:9-19:3).
On the night of the incident Okafor was in the dock office. He heard shouting, reached bay 6 in about a minute, and found the plaintiff on the floor near the edge of the walkway with the forklift stopped a few feet away (31:1-33:17). He did not see the collision; what he knows of it came from the operator, Reyes, and two dock workers he named (36:10-38:22). That admission matters because the incident report he wrote that night, Exhibit 7, says he "observed" the event. Confronted with the document, he conceded the word was wrong and that he should have written that he was informed (41:4-43:15).
Two conditions at bay 6 drew follow-up. A burned-out light fixture had been reported roughly two weeks earlier, and Okafor could not say whether it had been fixed before the incident (52:8-54:1). Within a few weeks afterward, Meridian repainted the walkway and installed a convex mirror at the bay 6 corner (67:3-69:19). On training, he described a classroom session and a supervised shift for new operators but did not know whether Reyes had completed the supervised shift (22:14-24:8). He was unaware of any discipline of Reyes, who remained employed (88:12-90:6). On examination by defending counsel, he added that drivers are instructed at check-in to stay in the walkway and that the plaintiff had made many prior deliveries to the facility (104:2-106:15).
Producing Each Format With Claude
The workflow is the same for all three formats; only the format instruction changes. Use a commercial Claude plan appropriate for client material (see which Claude plan fits a law practice) and a transcript with a text layer; if the PDF is image-only, run OCR first, because citation accuracy depends on Claude reading the page and line numbers rather than guessing them.
- Attach the full transcript. Do not split it unless it is enormous; splitting breaks the regroup-by-topic step.
- Give the matter framing in two sentences. Deponent, which side you represent, and the two or three issues that matter.
- Paste the format prompt from the blocks below.
- Verify, then derive. Spot-check the page-line output, then derive the topical and narrative versions from the verified table.
The reusable prompt lives at the deposition summary generator; the broader transcript workflow is in summarize a brief or transcript. If you summarize depositions weekly, put the prompt and header template into a Claude Project; see building a reusable Claude Project for your practice.
Prompt: page-line summary
You are assisting a litigation team. Attached is the deposition transcript of [DEPONENT], [ROLE], taken [DATE] in [MATTER]. We represent [PARTY]. The issues that matter most are: [ISSUE 1], [ISSUE 2], [ISSUE 3]. Produce a page-line summary as a three-column table: Page:Line | Testimony summary | Exhibit / flag. Rules: - Walk the transcript in order. One row per discrete subject of testimony, usually one to four pages each. - Cite the actual page and line numbers printed in the transcript, in the form 12:4-13:2. Never estimate a citation. If you cannot read a page or line number, write CITE UNCERTAIN in the cell. - Summaries are neutral. Do not characterize credibility or add argument. - Quote verbatim only where the exact words matter (admissions, contradictions, key terms), inside quotation marks. - In the third column, note exhibit numbers and apply only these flags: ADMISSION, INCONSISTENT (say with what), OBJECTION (say the type), FOLLOW-UP. - Include every exhibit marked. Include every objection where the witness was instructed not to answer. - After the table, list any portion of the transcript you could not read.
Prompt: topical summary (from a verified page-line table)
Using the verified page-line summary below, produce a topical summary. Group testimony under six to ten subject headings chosen from the content. Each bullet ends with its citation(s) in parentheses. Where the witness addressed the same fact in multiple places, combine them into one bullet with all citations. Preserve every INCONSISTENT flag as an italic note under the relevant heading. Do not add any fact that is not in the table.
Prompt: narrative summary (from a verified page-line table)
Using the verified page-line summary below, write a narrative summary in three to five paragraphs of plain prose, chronological where the testimony allows. Cite after every factual assertion in the form (31:1-33:17). Neutral tone, no argument. Do not add any fact that is not in the table. Length: roughly one page.
The Verification Rule: Spot-Check the Citations
The page-line output is only as good as its citations, and a wrong citation in a motion is worse than no summary at all. The verification routine is short and non-negotiable:
- Check every ADMISSION and INCONSISTENT row against the transcript. These are the rows you will cite.
- Sample the rest. Every fifth row, or ten at random. If a sampled cite is off by more than a line or two, re-run with a cleaner transcript file and check again.
- Read the "could not read" list. Those pages are missing from your summary, not summarized badly.
- Initial the header. The "verified by" field tells the trial team, months later, that a human checked the cites.
This is also the ethics answer. A summary is work product you are responsible for; the analysis in our guide to the ABA guidance on AI applies as it would to a new paralegal's draft. AI produces the draft. You own the accuracy.
Frequently Asked Questions
Related Reading
AI Deposition Outline Generator: Build One With Claude
How to generate a deposition outline with Claude from the pleadings, key documents, and your theory of the case: foundation, topic modules ordered to lock admissions before confrontation, exhibit references, and evasive-witness follow-ups. Includes a copyable prompt and a worked example.
Case Chronology Drafting Guide: Template + Claude Workflow
How to build a case chronology from mixed sources (pleadings, records, emails, transcripts) with every entry cited, a contradictions list, a chronology table template you can copy, and the Claude workflow that drafts it in one pass.
Litigation Document Coding With AI: Objective vs Subjective
Objective coding (date, author, recipients, document type, Bates) versus subjective coding (relevance, privilege flags, issue tags), how Claude does first-pass coding into a table with NOT FOUND discipline, why privilege calls stay with a lawyer, how to QC-sample, and a copyable extraction prompt.
Get strategies like this every week
The 5-Minute Claude Briefing — one prompt, one ethics insight, one workflow strategy. Free, weekly, built for lawyers.
Subscribe Free