Preparing a Technical Expert Witness for Deposition: Common Practices

Why Technical Expert Deposition Preparation Matters for Software Cases

Technical expert deposition preparation is one of the highest-leverage activities in an IP litigation workflow, because an expert’s deposition testimony can resurface at trial, in Daubert briefing, and in impeachment exhibits long after the transcript is signed. Under FRCP 26(a)(2)(B), a testifying expert’s written report discloses the opinions the expert will offer and the bases for them, which gives examining counsel both a roadmap for questioning and a boundary the questioning will repeatedly test. For software matters, where the record often includes source code review logs, version histories, and technical assumptions supplied by counsel, the preparation process carries added texture. This article surveys practices that practitioners commonly use when preparing a software expert witness for deposition: how sessions are structured around the report, which cross-examination themes recur, how experts commonly handle difficult question forms, what Rule 26(b)(4) protects, and why prior publications and testimony receive a fresh review. The frame throughout is descriptive, not prescriptive; the mix of practices varies by case, forum, and expert.

Key Takeaways for IP Litigation Firms

• Practitioners commonly anchor expert witness deposition preparation to the six disclosure categories of the FRCP 26(a)(2)(B) expert report, since the report defines both the scope of direct testimony and the terrain for cross-examination.
• Recurring cross-examination themes in software expert depositions include scope-of-review challenges, assumption probing, prior testimony consistency, Daubert-style methodology questioning, and compensation inquiries.
• The 2010 amendments to Rule 26(b)(4) extended work-product protection to draft reports and most attorney-expert communications, subject to three enumerated exceptions that deposition questioning frequently tests.
• Rule 37(c)(1) can limit trial use of undisclosed opinions, which is why practitioners often rehearse how an expert will respond when a question exceeds the analysis performed.
• Courts permit impeachment with prior inconsistent statements, so preparation commonly includes review of the expert’s publications, blog posts, and earlier transcripts.

Who This Article Is For

This article is written for IP litigation partners, associates, and litigation support professionals who retain and prepare software development expert witnesses in software patent, trade secret, and copyright matters. In-house counsel managing outside litigation teams, as well as case managers coordinating source code review procedures and expert disclosure deadlines, will also find the procedural framing useful.

Structuring Sessions Around the FRCP 26(a)(2)(B) Expert Report

The expert report is the natural spine for preparation because Rule 26(a)(2)(B) requires it to contain six categories of information: all opinions and their bases, the facts or data considered, exhibits, the expert’s qualifications, a list of cases in which the expert testified in the previous four years, and compensation. Practitioners commonly walk the expert through the four corners of that document, treating each disclosed opinion as its own module.

Restating Opinions and Their Bases

A common exercise asks the expert to restate each opinion and its basis in the expert’s own words, without reading from the report. The goal practitioners describe is fluency: an expert who can explain a doctrine-of-equivalents analysis or a source code tracing methodology conversationally is better positioned to answer follow-up questions that depart from the report’s exact phrasing.

Reviewing the Materials-Considered List

The “facts or data considered” disclosure receives particular attention in software cases. Scope-of-review questions frequently reference specific repositories, code versions, commits, or documents, and they probe both what the expert examined and what the expert did not examine. Preparation sessions commonly include a line-by-line review of this list so the expert can answer such questions accurately and without hesitation.

Session Cadence and Mock Questioning

Some practitioners schedule multiple shorter sessions rather than a single marathon, particularly for first-time witnesses. Session design often depends on case complexity, the expert’s prior deposition experience, and the time remaining before the deposition date, which itself reflects earlier decisions about when to engage a software expert witness in patent litigation. Many firms also use mock questioning, with a second attorney playing opposing counsel, to simulate the pace and pressure of the real examination.

Recurring Cross-Examination Themes in Software Expert Depositions

Examining counsel in software matters tend to return to a familiar set of expert witness cross-examination themes, and broader expert witness trends in software patent litigation help explain which themes recur, so preparation sessions commonly rehearse each one.

Scope-of-Review Challenges

Questions in this category isolate what the expert reviewed: which source code versions, which repositories, which commits, which technical documents. The mirror-image questions, about what was not reviewed, aim to suggest gaps. Experts who have kept careful review logs during source code inspections are typically able to answer these questions with precision.

Assumption Probing

Counsel often isolate the assumptions an expert relied on, such as facts provided by retaining counsel, hypothetical infringement scenarios, or damages inputs, and then test what happens to the opinion if an assumption changes. Preparation commonly includes cataloging each assumption and discussing how the expert will distinguish assumptions from independent conclusions.

Prior Testimony Consistency

The Rule 26(a)(2)(B)(v) list of prior cases gives opposing counsel a roadmap to order transcripts, and questions comparing current opinions with earlier testimony are routine. Preparation sessions commonly surface these comparisons in advance.

Methodology Questioning Under Daubert and Rule 702

In Daubert v. Merrell Dow Pharmaceuticals, the Supreme Court identified factors courts may consider when assessing expert methodology, including testability, error rates, peer review, and general acceptance. Federal Rule of Evidence 702, amended effective December 1, 2023, clarifies that the proponent must demonstrate that admissibility requirements are more likely than not satisfied. Examining counsel often probe these areas at deposition to build a record for later Daubert briefing, so preparation frequently includes rehearsing methodology questions in Daubert’s vocabulary.

Compensation and Engagement History

Rule 26(a)(2)(B)(vi) makes compensation a required disclosure, and questions about fees, engagement frequency, and the proportion of work performed for plaintiffs versus defendants are generally permitted. Practitioners commonly prepare experts to answer these questions directly and without defensiveness.

How Experts Commonly Handle Hypotheticals, Compound Questions, and Beyond-the-Report Requests

Beyond thematic content, preparation addresses question forms that recur across depositions.

Hypotheticals

Common practices include asking counsel to clarify the assumed facts before answering, and clearly distinguishing between disclosed opinions and answers given on hypothetical premises. Experts often flag on the record that an answer assumes the facts stated in the question, which keeps the transcript from blurring hypothetical answers into affirmative opinions.

Compound and Ambiguous Questions

When a question embeds multiple questions, practitioners describe two common approaches: requesting that the question be broken apart, or answering one embedded question at a time while identifying which part is being answered. Objections to form are typically preserved on the record, and many experts are prepared to pause briefly before answering so counsel has the opportunity to object.

Requests to Opine Beyond the Report

A recurring tension practitioners identify involves questions that invite opinions not disclosed in the report. Under Rule 37(c)(1), a party that fails to disclose information required by Rule 26(a) is generally not allowed to use that information at trial unless the failure was substantially justified or harmless. Because of this, a common practice is for the expert to note when a question exceeds the analysis performed, rather than improvising a new opinion on the record. Experts also commonly ask for documents to be shown rather than testifying from memory about their contents, a habit that reduces transcript errors about exhibits.None of these practices is framed by practitioners as the single correct approach; they are patterns that recur because the rules themselves shape what a clean transcript looks like.

Rule 26(b)(4) Draft Report Protection and Documentation Habits

The 2010 amendments to FRCP 26(b)(4) reshaped expert discovery. Rule 26(b)(4)(B) extends work-product protection to drafts of expert reports, and Rule 26(b)(4)(C) protects most attorney-expert communications. The attorney-expert communication privilege created by these provisions is subject to three enumerated exceptions, covering communications that:

1. 1. Relate to the expert’s compensation.
   2. Identify facts or data provided by counsel that the expert considered in forming opinions.
   3. Identify assumptions provided by counsel that the expert relied on.

In light of these rules, practitioners commonly adopt documentation habits such as tracking which materials were provided by counsel versus independently gathered, and maintaining a running materials-considered log throughout the engagement. Deposition questioning frequently tests the boundaries of these protections, so preparation sessions commonly rehearse how the expert will respond to questions touching protected communications, including when to pause for a privilege objection.Counsel should also note that state court and ITC practice can differ from the federal framework, so practitioners commonly confirm the applicable rules for the forum before preparation begins. The committee notes accompanying the 2010 amendments, available through the U.S. Courts rules archive, provide the drafting history.

Reviewing Prior Publications, Blog Posts, and Earlier Testimony

Courts permit impeachment of a witness with prior inconsistent statements, and for experts this reaches published articles, blog posts, conference talks, and testimony in earlier matters. Expert witness impeachment with prior testimony is a standard cross-examination tool, and the Rule 26(a)(2)(B)(v) disclosure of the past four years of cases gives opposing counsel a starting point for ordering transcripts.A common preparation practice is compiling the expert’s publication history and prior transcripts, then reviewing any passages that touch the technologies or methodologies at issue in the current matter. Where an apparent tension exists between a prior statement and a current opinion, preparation sessions commonly have the expert articulate the factual or contextual distinctions: different accused products, different claim constructions, different data sets, or evolved technical standards.Many testifying experts adopt careful, descriptive writing habits in their public content precisely because published statements can surface in cross-examination years later. Neutral resources such as the Federal Judicial Center’s Reference Manual on Scientific Evidence illustrate how courts approach expert testimony issues and are sometimes used as background reading during preparation.

Building a Repeatable Technical Expert Deposition Preparation Workflow

Effective technical expert deposition preparation, as practitioners commonly describe it, rests on five pillars: session structure anchored to the FRCP 26(a)(2)(B) report, recognition of recurring cross-examination themes, rehearsed question-handling practices, awareness of Rule 26(b)(4) protections and their exceptions, and a fresh review of prior publications and testimony. The right mix varies with case posture, forum rules, and the expert’s experience level, which is why many firms treat preparation as a workflow to be tailored rather than a fixed checklist. IP litigation teams planning upcoming software expert engagements, deposition preparation timelines, or source code review scoping can schedule a 20-minute consultation to discuss how a testifying software expert can support the matter.