A page-line deposition summary is a short, organized outline of testimony that points to exact transcript citations (page:line) so you can find key quotes fast. Use the copy/paste template below to capture topic headings, a 1–2 sentence takeaway, and the best page-line cites for each issue. You’ll also see a worked sample and a quick method that uses transcript search plus issue tags to build your summary in less time.
Primary keyword: page-line deposition summary template.
- Key takeaways:
- Use one topic per block and keep the summary to 1–2 sentences.
- Always pair takeaways with precise citations (page:line) and short quote snippets.
- Tag testimony by “issue” (liability, notice, damages, impeachment) while you read to speed up later drafting.
- Build your first draft with transcript search (names, dates, “I don’t recall,” key exhibits) and then fill gaps by reading around each hit.
- Quality check citations before you circulate the summary.
What a page-line deposition summary is (and what it is not)
A page-line deposition summary is a structured set of topic headings with short summaries and citations formatted as page:line (for example, 45:12–46:3). It helps you brief testimony, prepare motions, plan trial outlines, or share the “what matters” with a team without sending everyone back into the full transcript.
It is not a full transcript re-write, and it is not a legal argument. If you add analysis, label it clearly as “notes” or “commentary” so it doesn’t get confused with what the witness actually said.
Free copy/paste page-line deposition summary template
Copy the template into Word, Google Docs, or your case management notes. Keep each block short and consistent so you can scan it quickly later.
Template (one witness)
CASE: [Case name / caption] WITNESS: [Name] DEPOSITION DATE: [Date] TAKEN BY: [Attorney name] TRANSCRIPT VERSION: [Rough / Final] REPORTER/VIDEOGRAPHER: [If relevant] EXHIBITS REFERENCED: [Ex. 1, Ex. 2, …] ONE-LINE WITNESS ROLE: - [Who the witness is and why they matter in 1 sentence] ISSUE TAG KEY (edit to fit your case): - LIAB = Liability - CAUS = Causation - DAM = Damages - NOTICE = Notice/knowledge - IMPEACH = Impeachment/credibility - POLICY = Policies/procedures - TIMELINE = Dates/times sequence TOPIC-BY-TOPIC SUMMARY (page:line citations) 1) TOPIC HEADING: [e.g., Background and job duties] Issue tags: [TIMELINE, POLICY] 1–2 sentence summary: - [Write the takeaway in plain language.] Key cites (page:line): - [12:4–13:22] [Short quote fragment or point] - [14:1–14:18] [Short quote fragment or point] Notes (optional): - [Follow-up, to-do, cross themes, compare to other witness] 2) TOPIC HEADING: [e.g., Events on the day of incident] Issue tags: [LIAB, NOTICE] 1–2 sentence summary: - [Takeaway] Key cites (page:line): - [22:6–23:9] [Point] - [24:10–25:2] [Point] Notes (optional): - [Exhibits mentioned, contradictions, missing details] 3) TOPIC HEADING: [e.g., Documents and communications] Issue tags: [NOTICE, IMPEACH] 1–2 sentence summary: - [Takeaway] Key cites (page:line): - [35:7–36:14] [Point] - [38:20–39:5] [Point] IMPEACHMENT / “LOCK-IN” QUOTES (quick list) - [Page:line] “…” (short quote) - [Page:line] “…” EXHIBIT CALLOUTS (optional) - Ex. [#] – [What it is] – referenced at [page:line] OPEN ITEMS / FOLLOW-UP - [Needed: doc request, interrogatory, subpoena, errata check] - [Topics to cover in another dep] CITATION CHECK - [ ] Page:line format matches the transcript. - [ ] Ranges cover the full answer (not just the question). - [ ] Spelling of names/places matches transcript.
Template (table format for faster scanning)
If you prefer a spreadsheet-style view, use this table layout in a document or spreadsheet.
| Topic | Issue tags | 1–2 sentence summary | Best cites (page:line) | Quote snippets | Notes/To-dos | |------|------------|----------------------|------------------------|---------------|--------------| | | | | | | |
Fully worked sample (fictional snippet)
The example below uses a made-up case and made-up testimony to show how the finished product looks. Replace the facts, issues, and tags to match your matter.
Fictional snippet (for context)
(Excerpted fictional testimony) 12:8 Q. What is your role at Northgate Warehouse? 12:10 A. I’m the shift supervisor for shipping, and I’m responsible for the dock schedule. 22:6 Q. When did you first learn the dock gate was sticking? 22:9 A. People mentioned it in early May, maybe May 3rd or 4th. 22:14 Q. What did you do with that information? 22:16 A. I told maintenance and I put a note in the log. 24:10 Q. Was the gate repaired before June 2? 24:12 A. No. 24:13 Q. Why not? 24:15 A. I don’t know. Maintenance said they were waiting on a part. 35:7 Q. I’m showing you Exhibit 5, the dock log. 35:10 A. Yes, that’s the log. 35:12 Q. Is this your handwriting on May 4? 35:14 A. It looks like mine. 36:2 Q. The note says “Gate sticks—hazard.” Did you write that? 36:6 A. If that’s my handwriting, yes. 38:20 Q. Did you tell anyone to keep using the gate? 38:22 A. We kept using it because it was busy. 39:1 Q. Did you put up any warning? 39:3 A. No.
Page-line summary (worked)
CASE: Rivera v. Northgate Logistics (fictional) WITNESS: Jordan Lee DEPOSITION DATE: June 20, 2026 TAKEN BY: P. Smith TRANSCRIPT VERSION: Final EXHIBITS REFERENCED: Ex. 5 (dock log) ONE-LINE WITNESS ROLE: - Shift supervisor for shipping; responsible for dock schedule and daily operations. [12:10–12:11] ISSUE TAG KEY: - LIAB, NOTICE, POLICY, TIMELINE, IMPEACH, DAM 1) TOPIC HEADING: Role and responsibilities Issue tags: [POLICY] 1–2 sentence summary: - Witness supervises shipping shift and manages the dock schedule. [12:10–12:11] Key cites (page:line): - [12:10–12:11] “shift supervisor for shipping” / responsible for “dock schedule” 2) TOPIC HEADING: First notice of the sticking dock gate Issue tags: [NOTICE, TIMELINE] 1–2 sentence summary: - Witness says people reported the gate sticking in early May (around May 3–4). [22:9–22:12] Key cites (page:line): - [22:9–22:12] Early May notice; May 3–4 estimate 3) TOPIC HEADING: Actions taken after notice Issue tags: [NOTICE, POLICY] 1–2 sentence summary: - Witness states they notified maintenance and recorded the issue in the dock log. [22:16–22:18] Key cites (page:line): - [22:16–22:18] Told maintenance; put note in the log 4) TOPIC HEADING: Repair status before incident date (June 2) Issue tags: [LIAB, NOTICE, TIMELINE] 1–2 sentence summary: - Witness testifies the gate was not repaired before June 2 and does not know why, other than maintenance “waiting on a part.” [24:12–24:17] Key cites (page:line): - [24:12] “No.” (not repaired) - [24:15–24:17] Doesn’t know; waiting on a part 5) TOPIC HEADING: Exhibit 5 (dock log) authentication Issue tags: [IMPEACH, NOTICE] 1–2 sentence summary: - Witness recognizes the dock log and says the May 4 handwriting looks like theirs; the note reads “Gate sticks—hazard.” [35:10–36:6] Key cites (page:line): - [35:10–35:11] Identifies log - [35:14] Handwriting looks like theirs - [36:2–36:6] “Gate sticks—hazard” and likely authored by witness 6) TOPIC HEADING: Continued use of the gate and lack of warnings Issue tags: [LIAB, NOTICE] 1–2 sentence summary: - Witness admits they continued using the gate due to workload and did not post a warning. [38:22–39:3] Key cites (page:line): - [38:22–38:23] Continued use because it was busy - [39:3] No warning IMPEACHMENT / “LOCK-IN” QUOTES - [24:12] “No.” (repair not done before June 2) - [39:3] “No.” (no warning) EXHIBIT CALLOUTS - Ex. 5 – Dock log – referenced at [35:7–36:6] OPEN ITEMS / FOLLOW-UP - Pull maintenance records for the “part” referenced. [24:15–24:17] - Confirm who else had access to the dock log and whether policy required warnings/signage. CITATION CHECK - Completed for key points and exhibit references.
How to write it fast: transcript search + issue tags (a practical workflow)
You can draft a strong page-line deposition summary without reading every line first, as long as you come back to confirm context around each cite. The method below focuses on speed while keeping citations accurate.
Step 1: Set your issue tags before you start
Pick 6–10 tags that match your claims and defenses, then reuse them in every witness summary. Common tags include:
- TIMELINE (dates, sequence, who knew what when)
- NOTICE (knowledge, complaints, warnings)
- LIAB (duty, breach, what they did or didn’t do)
- CAUS (cause of the event or injury)
- DAM (medical treatment, wages, limitations)
- IMPEACH (inconsistencies, “I don’t recall,” prior statements)
- DOCS/EX (documents, exhibits, authentication)
Step 2: Create a “search list” of high-yield terms
Search terms pull you to the places most summaries need, then you summarize those sections. Start with:
- All key names (parties, supervisors, witnesses, treating providers)
- Key dates and time anchors (“May 4,” “June 2,” “the next morning”)
- Event nouns (“incident,” “spill,” “gate,” “warning,” “inspection”)
- Credibility phrases (“I don’t recall,” “not sure,” “I guess,” “maybe”)
- Document markers (“Exhibit,” “email,” “text,” “log,” “policy”)
Step 3: Build your topic headings from what you find
As you jump to each search hit, write a topic heading that matches the testimony section you’re in. Keep headings plain and scannable, like:
- “Background and role”
- “Notice and complaints before the incident”
- “What happened on [date]”
- “Policies, training, and practices”
- “Documents and communications”
- “Damages and limitations” (if covered)
Step 4: For each topic, write the 1–2 sentence takeaway first
Write the takeaway in your own words, then support it with citations. Aim for a structure like:
- Takeaway: what the witness admitted, denied, or could not remember.
- Support: 2–4 best page-line cites that prove the takeaway.
Step 5: Add “best cites” and short quote snippets
Use short quote fragments (not long blocks) so your reader can preview the point. Keep each cite tight and cover the full answer, not just the question.
Step 6: Use an “issue tag pass” to avoid re-reading later
After you draft the first pass, do a quick scan for any section you labeled with the wrong tag or forgot to tag. This makes it easier to pull a cross-witness issue outline later (for example, everything tagged NOTICE across all depositions).
Step 7: Do a citation and context check before sharing
Fixing citations later costs time and trust, so do a final check:
- Open each cited page and read 5–10 lines before and after.
- Confirm speaker identity (witness vs. attorney) when the exchange is tight.
- Make sure the cite range includes qualifiers (“I think,” “not sure”) that change meaning.
- Confirm exhibit numbers match the transcript.
Pitfalls to avoid (so your summary stays usable)
- Overlong topics: If a block runs half a page, split it into two topics.
- Argument disguised as summary: Keep “what it means” in Notes, and label it.
- Cherry-picked cites: Include qualifiers and corrections that live in nearby lines.
- Unclear headings: “General questions” is not helpful; name the event or issue.
- Missing “lock-in” quotes: Pull clean admissions and denials into one list for fast motion or trial prep.
- Ignoring exhibits: Exhibit authentication and document references often matter as much as the narrative.
Common questions
- How many citations should I include per topic?
Usually 2–4 strong cites per topic works well, plus more only if the testimony changes or gets qualified. - Should I summarize in chronological order or issue order?
Use chronological order for event-heavy witnesses, and issue order for corporate or expert witnesses; you can also do both by tagging issues. - What if the witness says “I don’t recall” repeatedly?
Group those under a “Memory/lack of knowledge” topic and cite representative exchanges, then add an IMPEACH tag where helpful. - Do I need to include objections?
Include them only if they affect the answer, preserve a dispute you expect to litigate, or explain why the testimony is incomplete. - How do I handle corrections (errata) or a rough transcript?
Label the version you used and add a note to re-check key cites after the final/errata, especially on “lock-in” quotes. - Can I use this template for hearings or interviews?
Yes; keep the same structure, but adjust citation format to match the record (timecodes for audio/video, for example). - What’s the difference between a page-line summary and a depo digest?
People use the terms differently, but a “digest” often runs longer and includes more narrative, while a page-line summary stays tighter and cite-driven.
When you’re working from audio or video (or you need a clean, searchable transcript for faster searching and tagging), GoTranscript can help with the underlying record so your summaries and citations are easier to build. If you need support, consider using GoTranscript’s professional transcription services as a reliable starting point for your deposition workflow.