skills/legal/deposition-errata-sheet/SKILL.md
Guides the FRCP 30(e) errata sheet process — submitting corrections for your witness and challenging improper opposing corrections. Covers change permissibility, jurisdictional splits, errata formatting, motions to strike, and impeachment use. Use when reviewing a deposition transcript for corrections, responding to an opposing errata sheet, or preparing cross-examination on changed testimony.
npx skillsauth add casemark/skills deposition-errata-sheetInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Manages the FRCP 30(e) errata process: submitting corrections for your witness or challenging an opposing witness's improper changes.
| View | Rule | Key Cases | |------|------|-----------| | Permissive | Form and substance allowed; original preserved; addressed on cross | Greenway v. Int'l Paper Co., 144 F.R.D. 322 (W.D. La. 1992) | | Restrictive | Only transcription errors; substantive changes may be stricken | Various district courts | | Intermediate (majority) | Substantive changes permitted but contradictory ones disregarded; reasons scrutinized; usable for impeachment | Hambleton Bros. Lumber v. Balkin, 397 F.3d 1217 (9th Cir. 2005); Burns v. Bd. of Cty. Comm'rs, 330 F.3d 1275 (10th Cir. 2003) |
Always verify controlling precedent before submitting or challenging errata.
| Category | Examples | Permissible? | |----------|----------|--------------| | Typographical error | Name misspelled, number wrong | Yes | | Technical/industry term | Acronym expanded wrong, jargon misheard | Yes | | Obvious mishearing | "I didn't" vs. "I did"; audio confirms | Yes | | Witness cut off | Answer incomplete in transcript | Yes | | Substantive clarification | "What I meant was..." | Scrutinized | | Memory refreshed post-depo | Reviewed docs, recalls differently | Scrutinized | | Complete reversal | "Yes" to "No" | Improper | | Adding new facts | Facts not discussed at deposition | Improper | | Damage control | Changing harmful admissions | Improper |
Before correcting, ask:
ERRATA SHEET
Case: [CASE NAME AND NUMBER]
Deponent: [NAME]
Deposition Date: [DATE]
Review Date: [DATE]
I have reviewed the transcript of my deposition and request the
following corrections:
Page Line Reads Should Read Reason
---- ---- -------------------- -------------------- --------------------
Subject to the corrections noted above, I affirm the transcript
is a true and accurate record of my testimony.
I declare under penalty of perjury that the foregoing is true
and correct.
Executed on _____________, at ________________.
_________________________________
[DEPONENT SIGNATURE / PRINTED NAME]
| Option | When to Use | Approach | |--------|-------------|----------| | Motion to Strike | Restrictive jurisdiction; substantive changes | Argue changes exceed 30(e) scope; request reliance on original | | Opposition to Reliance | Opposing party cites changed testimony in briefing | Attach original excerpt; argue changes are pretextual | | Impeachment at Trial | Preserve credibility attack | Use original answer, then expose the change and timing |
Q: At your deposition you testified [ORIGINAL ANSWER], correct?
Q: You gave that answer under oath?
Q: After the deposition you submitted an errata sheet changing that answer?
Q: You changed [N] answers total in your errata sheet?
Q: Every single change benefited your case, didn't it?
Use during deposition to limit errata abuse:
development
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
tools
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
development
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
testing
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.