How to organize witness statements and document references for Trade Secret Disputes

Organize trade-secret witness evidence around each alleged secret and the precise proposition a witness can support—not around interview order or document volume. Assign stable secret and witness identifiers, distinguish firsthand observations from inference, and link material statements to pinpoint sources. Record corroboration, contradictions, missing evidence, and verification tasks in a witness evidence matrix. The resulting deliverable is a source-linked record counsel can use to assess proof, select exhibits, prepare witness questions, and identify assertions that are not ready for a declaration or deposition outline.

When to use this workflow

Use this workflow when litigation counsel or an in-house team receives competing accounts of employee access, departing personnel’s file transfers, disputed product development, or disclosure to a business partner. It is particularly useful before drafting declarations or preparing depositions, when a plausible narrative must become discrete propositions supported by identifiable witnesses and documents.

This is an evidence-organization guide, not a complete collection or discovery plan. The legal baseline is US federal law. Check applicable state trade-secret law, controlling decisions, local rules, and case-specific orders; state proceedings and arbitration have different requirements. Assess contractual permissions against the actual agreement, governing law, and facts.

What you need

Gather the current alleged-secret descriptions, pleadings, witness accounts, and referenced documents. Include unfavorable material rather than limiting the starting set to the client’s preferred narrative.

Assemble:

• A secret register identifying each claimed secret’s boundaries, version, claimed owner, relevant period, and compilation or component status.
• A witness roster identifying stable witness IDs, roles, employment periods, repositories used, and likely sources of knowledge.
• Interview notes, signed statements, recordings where available, and deposition transcripts, with dates and provenance.
• Executed confidentiality agreements, permission records, training acknowledgments, and evidence of actual security practices.
• Source-control history, access logs, messages, file-transfer records, and relevant development documents.
• Confidentiality orders, handling protocols, and a stable document-ID convention.

Distinguish the original source, review copy, and counsel’s summary. A document title alone is unreliable when several versions exist.

Use the template

The companion template is Trade Secret Disputes — Witness evidence matrix. You can copy this table into your working document or spreadsheet.

Use one row for one material proposition about one alleged secret. Assign permanent row identifiers so outlines and updates remain traceable after sorting.

“Witness / basis” distinguishes direct observation, information received from others, technical interpretation, and counsel’s inference. “Statement cite” identifies the interview record and paragraph, transcript page and line, or recording timestamp. “Document cite” identifies the exact document version and page, clause, worksheet cells, or log event.

“Support / conflict” explains what the sources establish. “Gap / status” records uncertainty and verification status, not a legal conclusion. “Action / owner” identifies the next task and responsible person. Record intended use in the status field; keep restricted legal assessments separately linked from factual extracts intended for wider circulation.

Step by step

1. Bound the alleged secret before mapping witnesses

Assign each alleged secret an identifier linked to the secret register. Avoid descriptions such as “all engineering information.” Specify the asserted version, period, and combination of information. If the theory concerns a compilation, do not treat evidence that one component was public as resolving the whole compilation’s status.

The federal definition requires reasonable secrecy measures and actual or potential independent economic value from information not generally known or readily ascertainable through proper means by someone who could obtain economic value from its disclosure or use. A confidentiality label alone establishes neither requirement. See 18 U.S.C. § 1839(3). (uscode.house.gov)

Record: the secret ID and bounded proposition. If scope remains disputed, identify competing descriptions and assign clarification.

2. Break each account into testable propositions

Split narratives into statements about secrecy, economic value, acquisition, disclosure, use, knowledge, consent, and alleged injury. A witness saying an engineer “took our process” may mean an observed download, a colleague’s report, or an inference from a competitor’s launch.

Federal law distinguishes improper acquisition from unauthorized disclosure or use, with specified knowledge conditions. It excludes reverse engineering, independent derivation, and other lawful acquisition from improper means. Access alone is not the complete inquiry. Those exclusions do not resolve separate contractual restrictions. See 18 U.S.C. § 1839(5)–(6). (uscode.house.gov)

Record: separate proposition rows and alternative explanations. Do not merge an observed transfer and inferred disclosure into one established fact.

3. Capture provenance and the witness’s knowledge basis

Identify who made the statement, when, to whom, and in what form. Distinguish an unsigned interview summary from a witness-approved statement or sworn testimony. Preserve earlier versions and corrections rather than overwriting them.

Ask what the witness saw, heard, administered, or created. For technical interpretations, identify the records examined and assumptions used. Federal Rule of Evidence 602 generally requires support for personal knowledge; it excepts expert testimony under Rule 703. Rule 901 addresses authentication. Neither authentication nor personal knowledge alone resolves hearsay. See Federal Rules of Evidence, Rules 602 and 901. (uscourts.gov)

Record: witness ID, statement pinpoint, knowledge basis, and any need for another foundation witness. Attribute secondhand information to its identified source where possible.

4. Link documents at the proposition level

Attach references supporting or challenging the specific proposition. For an agreement, identify the executed version and clause. For access evidence, identify the account, event, time zone, and log coverage. For a spreadsheet, include worksheet and cell range alongside the document ID.

Compare permissions with actual activity. A download event alone does not establish the human operator, archive contents, or subsequent disclosure. Check shared credentials, service accounts, and whether the file version matches the alleged secret. Preserve the original timestamp and explain any conversion used in the matrix.

Record: the exact source location and its narrow significance. If attribution is unresolved, write “account activity; operator unconfirmed,” not an established attribution to an individual.

5. Reconcile corroboration, contradictions, and time

Compare material statements with contemporaneous records and other accounts. Separate event date, document-creation date, and collection date. If a witness recalls a spring meeting but the located calendar entry is in summer, retain both and investigate whether there were two meetings.

Test secrecy evidence against actual practice. Written restrictions may coexist with broad permissions or approved external disclosures. An exception may also have a documented, limited purpose. Keep those facts visible without deciding their legal effect through a status label.

Record: direct, partial, conflicting, or absent support, followed by the reason. Identify whether a document genuinely contradicts the witness or merely covers a different period or version.

6. Turn gaps into focused verification tasks

Replace “needs more evidence” with an answerable question: Who approved the recipient list? Which repository version existed on the transfer date? Who can explain the access configuration? Identify the likely source and responsible reviewer.

If discovery is needed, connect the proposed request to that proposition. Federal Rule 26(b)(1) limits discovery to nonprivileged, relevant, proportional matters. Rule 26(c)(1)(G) permits protective orders restricting trade-secret disclosure, subject to good cause and applicable motion requirements. Sensitive subject matter does not automatically create court-ordered protection. See Federal Rules of Civil Procedure, Rule 26. (uscourts.gov)

Record: the question, proposed source, handling restriction, and owner. Keep this task focused on resolving the evidentiary gap rather than duplicating the discovery tracker.

7. Prepare a verified version for its intended use

Reopen each material source before preparing a witness extract. Distinguish the witness’s knowledge from counsel’s synthesis. Retain contrary references and turn unresolved rows into questions rather than scripting certainty. Flag proposed declaration assertions requiring witness confirmation.

An internal matrix is not automatically an admissible summary. Federal Rule 1006 concerns summaries of voluminous admissible materials that cannot conveniently be examined in court and requires access to underlying originals or duplicates. Illustrative aids require separate consideration under Rule 107. See Federal Rules of Evidence, Rules 1006 and 107. (uscourts.gov)

Record: intended use, verification status, and outstanding foundation or approval issues. Preserve the verified version and its source references when creating later working extracts.

Worked example

Fictional scenario: Larchwell Robotics alleges that departing engineer Mara Vale disclosed its version 4 sensor-calibration sequence to rival Northmere Systems. Counsel assigns TS-01 to that bounded sequence. Operations manager Elena Voss describes restricted access; systems administrator Daniel Orr identifies an archive download; former project lead Priya Sen recalls approving a supplier disclosure.

All parties, documents, identifiers, and events are fictional. The permission snapshot postdates Vale’s departure. No rival development records or recipient-side transfer evidence have been supplied. Chen and Malik are assigned reviewers.

The matrix changes the immediate declaration decision. Counsel should not assert that Vale disclosed the complete sequence based on the download record. Orr can explain the recorded account activity and its limits; operator attribution and archive contents remain separate questions.

Voss’s account needs historical verification because the later snapshot neither proves nor disproves earlier restrictions. Sen’s account may explain authorized supplier access, but the missing attachment prevents comparison with TS-01. Her approval also does not establish what was transmitted or what the recipient could later disclose. Counsel assigns those gaps before characterizing supplier access as decisive adverse evidence or irrelevant background.

Common mistakes

• Using one row per witness. Split accounts by proposition and secret ID so observation and inference remain distinct.
• Treating “confidential” as the complete analysis. Connect labels to actual precautions and separately identify economic-value evidence.
• Equating account activity with competitive use. Treat attribution, contents, destination, and later use as distinct questions.
• Citing a document family without the attachment. Identify the precise supporting item and flag missing attachments.
• Replacing an inconvenient account with a corrected one. Preserve both versions, the explanation, and remaining conflicts.
• Circulating counsel’s impressions with factual extracts. Separate assessments from source-linked facts and check audience restrictions before distribution.

Final quality check

• Every row maps to a bounded secret and one material proposition.
• Each statement has provenance, a pinpoint, and an identified knowledge basis.
• Document references reopen to the correct version, page, clause, cell, or event.
• Material dates, time zones, attribution, and log coverage are checked.
• Contrary evidence and plausible alternative explanations remain visible.
• Open issues are resolved or assigned to a named owner with a concrete task.
• The audience, handling restrictions, and intended evidentiary use are identified.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, privilege and confidentiality analysis, chronology, and deposition preparation capabilities can support this work while counsel verifies sources and legal significance. The chronology viewer and trial preparation capabilities are relevant to organizing the record. The matrix remains counsel’s work product, not a promised dedicated module. To discuss this workflow, book a demo.

Frequently asked questions

Should each witness have a separate matrix?

Maintain a proposition-level master matrix and create witness-specific extracts. This keeps conflicting accounts connected while supporting focused preparation. Retain stable row IDs across extracts.

How should counsel record an unsigned interview note?

Identify it as an interview note, name its preparer, and record the interview date and pinpoint. Distinguish paraphrases from verbatim passages; do not imply witness approval that has not occurred.

What if the alleged secret changes during the dispute?

Version the secret register and reassess affected rows. Preserve earlier mappings so readers can distinguish a changed secret description from changed testimony. Recheck whether existing documents address the revised version.

Can the matrix become an exhibit?

Potentially, but accurate references alone are insufficient. Decide whether it is an internal aid, illustrative aid, or proposed evidentiary summary. Separately assess applicable requirements, underlying evidence, and any proposed disclosure of counsel’s assessments.

Sources

• 18 U.S.C. § 1839: federal definitions of trade secret, misappropriation, and improper means.
• Federal Rules of Civil Procedure: Rule 26 discovery scope and protective orders.
• Federal Rules of Evidence: Rules 602, 901, 1006, and 107.

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.