How to prepare a deposition outline from case documents for Trade Secret Disputes

Prepare a trade-secret deposition outline by mapping each alleged secret to the witness’s knowledge, relevant documents, and factual propositions the examination should test. Separate secrecy and economic value from acquisition, disclosure, use, knowledge, and consent. Build exhibit-linked questions that establish foundation, test competing explanations, and identify missing evidence. The deliverable is a witness-specific outline with pinpoint citations, anticipated admissions labeled as hypotheses, contradiction branches, handling restrictions, and assigned follow-up—not a chronological document dump or a script that assumes misappropriation.

When to use this workflow

Use this workflow when litigation counsel has a defined witness, a working identification of the alleged secrets, and enough case documents to select exhibits. It suits examinations of departing employees, technical managers, information-security personnel, recipient-company employees, and organizational designees. In-house teams can identify systems and business context while distinguishing internal assumptions from evidence.

The scope is preparation of the examination outline and exhibit plan, not the entire discovery process. This guide uses a US federal baseline. For a particular matter, check applicable state substantive law, controlling decisions, procedural rules, and case-specific orders; do not carry federal procedures into state court or arbitration without checking them. The steps below are workflow recommendations, not prescribed testimony or conclusions about trade-secret status.

What you need

Assemble a witness-specific packet:

• Claims and secret definitions: operative pleadings, relevant contentions or disclosures, secret identifiers, versions, claimed ownership, and relevant periods.
• Witness scope: deposition notice, organizational topics where applicable, responsibilities, prior testimony, and appropriately handled interview records.
• Technical evidence: access logs, repository history, file versions, permissions, device evidence, and explanations of system fields and time zones.
• Secrecy and value evidence: executed confidentiality agreements, training, actual access practices, offboarding records, development records, and evidence of commercial advantage.
• Conduct and competing explanations: recipient communications, product-development records, public materials, authorized-transfer evidence, and independent-development records.
• Handling constraints: protective orders, confidentiality designations, privilege decisions, production identifiers, and unresolved production gaps.

Separate counsel’s impressions from source-supported facts. Flag incomplete families, missing attachments, and unreliable text extraction before drafting questions.

Use the template

The Trade Secret Disputes — Deposition outline is a working outline index. You can copy this table into your working document or spreadsheet and place the full question sequence beneath each numbered row. It is a work product you create, not a promised download.

Use stable references such as R01 so question blocks remain connected after reordering. “Witness basis” distinguishes personal involvement, system familiarity, organizational preparation, and inference. The exhibit field should identify a production ID and page, message, worksheet cell, or log event—not merely a filename. Add version, relevant period, and handling restrictions where necessary.

An “admission to test” is a hypothesis. The conflict field captures contrary evidence and uncertainty; the final field assigns the next question or preparation task. Keep provisional exhibit labels separate from numbers assigned during the deposition.

Step by step

1. Fix the witness scope and secret boundaries

Identify what this witness can explain about each secret. Distinguish a source-code version from later revisions, a pricing model from its inputs, and a claimed compilation from publicly available components. Avoid using “technical information” as the boundary for an entire examination.

For a federal organizational deposition, map the outline to the noticed topics. Rule 30(b)(6) requires topics described with reasonable particularity, good-faith conferral, and designee testimony about information known or reasonably available to the organization. It is not simply an employee’s memory test. See Federal Rule of Civil Procedure 30(b)(6). (uscourts.gov)

Record: secret ID, version, relevant period, witness capacity, and topic reference in the first three fields. Assign ambiguous boundaries for counsel’s resolution.

2. Turn disputed propositions into factual objectives

Create separate objectives for secrecy measures and economic value. Section 1839(3) requires reasonable secrecy measures and actual or potential independent economic value from information not being generally known or readily ascertainable through proper means by someone who could obtain economic value from its disclosure or use. See 18 U.S.C. § 1839(3). (govinfo.gov)

Translate those requirements into questions about the particular information: who had access, how exceptions worked, what training occurred, and what advantage secrecy provided. Compare written policy with actual practice. Ask how development effort relates to competitive advantage rather than treating cost or a confidentiality stamp as sufficient proof.

Record: one bounded objective per row and a testable proposed admission, such as “external sharing of version 4.2 required approval during this period.”

3. Separate acquisition, disclosure, and use

Build distinct paths for how information was obtained, where it went, and what anyone did with it. Section 1839 distinguishes acquisition through improper means from unauthorized disclosure or use, with specified knowledge conditions. Reverse engineering, independent derivation, and other lawful acquisition are excluded from improper means. See 18 U.S.C. § 1839(5)–(6). (govinfo.gov)

A download event should prompt questions about attribution, purpose, destination, authorization, and subsequent handling—not an assumed admission of competitive use. Explore independent-development and public-source explanations raised by the documents. Analyze any separate contractual restriction under its actual language and governing law rather than assuming the statutory exclusions decide it.

Record: the conduct being tested, supporting exhibit, knowledge and consent questions, and competing explanation. Avoid a combined objective such as “accessed and misused.”

4. Select exhibits and draft foundation questions

Choose the smallest exhibit set that can test each objective. Verify complete threads, attachments, file versions, timestamps, and the relationship between native data and the displayed exhibit. For logs, identify who can explain event labels, coverage, and shared or service accounts.

Draft foundation before merits questions: “Do you recognize this repository?” “What does this field record?” “Were you responsible for these permissions?” Federal Rules of Evidence 901 and 602 provide authentication and personal-knowledge frameworks for anticipated evidentiary use; they are not a complete statement of deposition scope. Authentication also leaves hearsay questions unresolved. See Rules 901 and 602. (uscourts.gov)

Record: exhibit pinpoint, witness basis, foundation sequence, and any need for another technical witness. Do not ask an employee to validate forensic work they did not observe or understand.

5. Build question branches around contradictions

For each topic, obtain the witness’s account, clarify dates and participants, establish document context, and test the disputed proposition. Draft branches for agreement, denial, lack of recollection, and lack of knowledge. Ask what supports an answer and who else has relevant knowledge.

Identify the precise conflict. Approval for a customer demonstration may contradict a blanket denial of sharing authority without authorizing disclosure of an underlying parameter file. Ask what approval covered, which materials were included, and what restrictions accompanied it. Do not characterize every inconsistency as dishonesty.

Record: competing sources, the distinction to resolve, and follow-up questions for material answers. Keep adverse exhibits in the relevant question block rather than a separate folder counsel may overlook.

6. Apply handling restrictions and assign gaps

Review proposed exhibits for privilege and confidentiality restrictions. Federal discovery concerns nonprivileged, relevant, proportional matters. Rule 26(c)(1)(G) permits restrictions on trade-secret disclosure through the applicable protective-order process and good-cause showing. See Federal Rule of Civil Procedure 26. (uscourts.gov)

Read the actual order for restrictions affecting attendees, exhibit access, and testimony. A confidentiality designation alone does not answer every handling question. Separate privileged preparation material from the exhibit set and resolve uncertain status before use.

Record: restrictions, missing evidence, responsible reviewer, and fallback question. If a log’s meaning remains unresolved, ask who administers the system rather than supplying an unsupported interpretation in the question.

7. Rehearse the outline against the sources

Have another reviewer trace major questions to the cited documents. Check surrounding text, document completeness, and whether the witness can answer. Reconcile event dates, document dates, and time zones without silently turning uncertainty into precision.

Rehearse aloud. Put essential identity, boundaries, authorization, and conduct questions before optional detail. Link the exhibit index to row IDs and distinguish factual questions from counsel’s argumentative summaries. An expected admission should remain useful even if the witness rejects it: the branch should identify the competing account and its sources.

Record: readiness, unresolved tasks, and express decisions to defer issues in the follow-up field. The outline should show what counsel will ask, why, and what follows an unexpected answer.

Worked example

Fictional scenario: Calder Process Systems alleges that former engineer Mira Senn transferred a restricted calibration file to competitor Alderline Instruments. Counsel is preparing Senn’s individual deposition. TS-01 is calibration file version 4.2, not all Calder engineering information.

The packet includes a permissions report, a maintenance record identifying Senn’s role, an export event associated with her account, a demonstration-approval email, and an Alderline test note listing her as a participant. It lacks destination-device evidence and the approval email’s referenced attachment. All parties, records, identifiers, and facts are fictional.

R01 narrows the authorization question to materials actually approved. R02 prevents counsel from presenting account association as proven personal action or external transfer. R03 tests derivation instead of equating similarity with use. None supplies the missing attachment, destination, or source of settings. Counsel can pursue focused admissions while preserving authorized-transfer and independent-source explanations for further testing.

Common mistakes

• Using an undefined secret. Tie each question block to a bounded version or compilation so answers concern the same information.
• Equating permission with activity. Compare access rights with event evidence and test account attribution separately.
• Treating export as disclosure or use. Ask about destination, recipient, authority, and subsequent conduct independently.
• Ignoring permission exceptions. Read demonstration approvals and outside access alongside confidentiality policies; examine their actual scope.
• Demanding unsupported technical foundations. Ask what the witness knows and identify another witness for unresolved methodology.
• Writing only favorable branches. Include adverse exhibits and useful follow-ups after denial, uncertainty, or failed recollection.

Final quality check

• Every topic identifies the alleged secret and relevant version or period.
• Every material factual premise has a verified pinpoint or an explicit unsupported label.
• Witness capacity and organizational-topic boundaries are clear.
• Exhibits are complete enough for the proposed questions, with missing material identified.
• Acquisition, disclosure, use, knowledge, and consent are separated where relevant.
• Contrary evidence and lawful-source explanations receive meaningful questions.
• Exhibit handling follows actual orders and resolved privilege decisions.
• Open issues have an owner and fallback, or an express decision to defer them.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its deposition preparation capabilities support work with case documents alongside document review, privilege and confidentiality analysis, and evidence analysis. The chronology viewer supports examination of event sequences. Counsel should verify source references, select exhibits, and determine question strategy. To discuss this trade-secret outline workflow, book a demo.

Frequently asked questions

Should the outline follow document chronology?

Use chronology within topics where sequence matters, especially permissions, departure, export, and recipient development. Organize the overall outline around factual objectives so a date-by-date recitation does not obscure missing proof.

How should an organizational outline differ?

Map question blocks to noticed topics and ask about preparation and information sources. Distinguish personal involvement from information gathered for organizational testimony; do not frame every question as a test of personal recollection.

What if the technical record is incomplete?

Identify the gap and ask which system recorded the event, who administers it, and what other records could explain it. Do not supply a destination, identity, or technical meaning absent from the evidence.

Should counsel ask whether information is a trade secret?

The answer may reveal the witness’s understanding, but the label should not replace factual examination. Prioritize information boundaries, actual secrecy practices, economic advantage, sources, authorization, and conduct. Evaluate those answers under applicable law.

Sources

• 18 U.S.C. § 1839: federal definitions of trade secret, misappropriation, and improper means.
• Federal Rules of Civil Procedure: Rules 26 and 30(b)(6).
• Federal Rules of Evidence: Rules 602 and 901.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.