How to build a case law research matrix for Trade Secret Disputes

Build a trade-secret case law research matrix by separating each alleged secret, disputed legal proposition, and procedural question before collecting decisions. For every authority, record the court, governing law, posture, precise holding, factual comparison, contrary authority, and subsequent treatment. Connect each analogy to identified matter evidence rather than a general account of the dispute. The deliverable is a source-linked table showing which decisions support an argument, which weaken it, and what counsel must verify before relying on either.

When to use this workflow

Use this workflow when preparing a trade-secret pleading, injunction submission, discovery position, dispositive motion, or trial argument. It helps outside counsel and in-house teams compare decisions where secrecy controls, recipient restrictions, access, competitive use, or independent development are disputed.

Start when counsel can identify the intended submission and alleged secrets. Researching “confidential information” without those boundaries produces comparisons that may not answer the question presented. Customer pricing, source code, and manufacturing compilations need separate factual analysis.

This guide uses a US federal baseline and an October 13, 2026 research cutoff. Confirm applicable state law, controlling decisions, local rules, and case-specific orders separately; do not apply federal procedure automatically to state proceedings or arbitration. This is a research workflow, not matter-specific advice or a completed survey of governing authority.

What you need

Collect the materials that define both the legal question and its factual limits:

• Matter parameters: forum, asserted claims, governing-law positions, represented party, procedural posture, and proposed submission.
• Secret register: stable identifiers, bounded descriptions, versions, claimed owners, relevant periods, and whether the claim concerns a compilation or individual components.
• Comparison evidence: confidentiality agreements, permission histories, public disclosures, access logs, development records, and economic-value evidence, with document IDs and pinpoints.
• Research materials: statutory text, complete opinions, relevant docket orders, and subsequent-history and treatment research.
• Opposing explanations: public availability, consent, lawful acquisition, independent development, and objections to the secret’s identification.

Narrow the question before searching. Replace “Are customer lists protected?” with “How have courts applying the selected law assessed secrecy measures for pricing compilations shared with distributors?” Record contractual restrictions as facts requiring interpretation, not substitutes for the statutory elements.

Use the template

Use the Trade Secret Disputes — Case law research matrix below. You can copy this table into your working document or spreadsheet. Use one row per authority-and-proposition pair; repeat an authority when it resolves materially different questions.

Row / issue combines a research ID, secret ID, and issue: R-04 / TS-02 / reasonable measures. Authority / pin includes the full citation, direct opinion link, and supporting page or paragraph. State whether pinpoints use slip-opinion or reporter pagination.

Court / law identifies the issuing court and law applied; also note the authority’s role in the selected forum. Posture identifies what was decided and whether the court considered allegations, an injunction record, or developed evidence. Holding / limits separates the resolved proposition from dicta and unanswered questions.

Facts / record links captures similarities, differences, and matter document references. Contrary / treatment records adverse decisions, subsequent history, and the date and scope of treatment checks. Action / owner states proposed use, verification status, and responsibility for open issues. Link longer notes without removing qualifications from the row.

Step by step

1. Define the decision the research must support

Write a short scope note identifying the represented party, forum, governing-law assumptions, submission, and disputed proposition. For example: assess whether TS-01’s access restrictions support the proposed reasonable-measures argument on the present record.

Separate substantive and procedural questions. Research concerning protection of discovery material should not be grouped indiscriminately with research concerning trade-secret status. Set a cutoff date and identify excluded issues, such as damages or contractual liability, unless they affect the assigned question.

Record: the scope note, secret IDs, issue rows, cutoff, and assigned researcher.

2. Separate the statutory questions

For federal claims, § 1839(3) requires reasonable secrecy measures and actual or potential independent economic value attributable to information not being generally known or readily ascertainable through proper means by someone who could benefit economically from disclosure or use. Research those requirements separately; a confidentiality label does not establish both. See 18 U.S.C. § 1839(3).

Distinguish improper acquisition from unauthorized disclosure or use and identify the applicable knowledge conditions. Section 1839(5)–(6) also excludes reverse engineering, independent derivation, and other lawful acquisition from improper means. That exclusion does not itself decide a separate contractual claim. See § 1839(5)–(6).

Record: distinct issue rows, statutory subsections, and state-law comparison questions. Do not treat this issue list as a complete claim-elements analysis.

3. Search by governing law, posture, and disputed fact

Build searches from the issue, a distinguishing fact, and the procedural setting: reasonable measures, distributor access, and summary judgment, for example. Search compilation claims separately from claims to their individual components.

Prioritize authorities relevant to the selected forum and governing law, then expand deliberately. Explain why an out-of-jurisdiction decision is useful. Search against the intended argument: inconsistent restrictions, public distribution, authorized downloading, or independent development may expose the decisive distinction.

Record: candidate citation, court, law, posture, search rationale, and preliminary relevance. Mark unread decisions as candidates, not approved support.

4. Extract the narrow holding from the full opinion

Read the complete opinion. Identify the issue decided, accepted allegations or factual findings, evidentiary limitations, reasoning, and disposition. Distinguish the court’s conclusion from a party’s argument or a quoted earlier decision.

Do not convert pleading sufficiency into a trial-proof standard. For example, Oakwood Laboratories LLC v. Thanoo evaluated the sufficiency of allegations, not ultimate liability. Its treatment of identification and use must retain that procedural context. See the court’s opinion, slip pp. 20–28, 31–41.

Record: a narrow paraphrase, verified pinpoint, posture, and limitation. If the opinion does not decide the proposed question, change the row’s stated purpose.

5. Compare relevant facts with identified evidence

Compare mechanisms rather than labels. For secrecy, distinguish written policies from actual permissions and enforcement. For alleged use, distinguish possession from evidence showing how information affected development or commercial conduct. Mark whether each comparison rests on evidence, an allegation, or counsel’s inference.

Keep discovery authorities in a separate issue group. Federal Rule 26(b)(1) addresses nonprivileged, relevant, proportional discovery; Rule 26(c)(1)(G) permits protective restrictions for trade secrets and other confidential commercial information through the applicable motion and good-cause framework. Those provisions do not independently determine substantive trade-secret status. See Federal Rule of Civil Procedure 26.

Record: material similarities, adverse differences, source references, and missing evidence that could change the analogy.

6. Check contrary authority and subsequent treatment

Investigate subsequent history and later decisions addressing the precise proposition. Read relevant later opinions; a treatment label alone cannot explain whether the same issue was considered. Check the authority’s precedential designation and its relevance within the selected court hierarchy.

Place adverse decisions beside the proposition they challenge. Explain whether the difference concerns governing law, posture, identification, secrecy practices, or proof of conduct. Distinguish “check incomplete” from “no adverse treatment identified within the documented search.”

Record: adverse citations and pinpoints, treatment findings, search scope, actual check date, researcher, and unresolved limitations. Do not backdate a check to the research cutoff.

7. Produce a bounded recommendation

Group approved rows by issue. Identify the strongest support, strongest counterargument, and factual uncertainty most likely to change the recommendation. Write a short synthesis referencing row IDs instead of repeating every case summary.

Assign unresolved questions to further legal research or a targeted factual inquiry. A disagreement about distributor sharing may require executed recipient terms, not another broad search for confidentiality decisions.

Record: each row’s proposed use—lead support, distinguish, adverse authority, background, or further research—and an owner for every open issue. Arrange a fresh treatment check before external reliance.

Worked example

Fictional scenario: Alderline Process Systems alleges that former engineer Mira Vale supplied competitor Cobalt Works with calibration compilation TS-01 and service-pricing workbook TS-02. Counsel represents Alderline in a fictional federal action in New Jersey and is preparing an opposition to a motion to dismiss its federal trade-secret claim.

The fictional record includes a restricted-access policy, a distributor email attaching pricing material, and a download log. The executed distributor agreement, historical permissions, and Cobalt’s development records are unavailable. An existing draft alleges competitive use based only on the download. All scenario parties, documents, and events are fictional; the judicial authority below is real.

These three representative rows apply different propositions from one opinion. They are not a completed authority survey. In Oakwood, the Third Circuit found the identification allegations sufficient, rejected limiting “use” to replication, and found the combined allegations sufficient to plead use. See slip pp. 26–28, 31–36, 39–41.

The matrix changes the proposed opposition. Counsel should not present the download as equivalent to Oakwood’s combined allegations or assume replication is the only relevant conduct. TS-02 also needs separate identification and recipient-restriction research. Missing evidence remains a gap; the matrix supplies no invented allegation to fill it.

Common mistakes

• Grouping all secrets together. Separate compilation, component, version, and disclosure questions by secret ID so a technical-file analogy does not conceal a pricing-workbook weakness.
• Recording outcomes instead of holdings. Replace “plaintiff won” with the issue decided, posture, supporting facts, and limiting language.
• Equating access with misappropriation. Research acquisition, disclosure, use, consent, and knowledge separately; retain lawful-acquisition explanations.
• Hiding adverse differences. Place public distribution, permission exceptions, and missing restrictions beside the analogy, with source references.
• Approving unchecked authorities. Separate full-text verification, treatment checking, and factual comparison; completing one does not complete the others.

Final quality check

• Every substantive row identifies a secret and precise question.
• Approved propositions have complete opinions, direct links, and verified pinpoints.
• Court, governing law, precedential role, and posture are explicit.
• Holdings, allegations, factual findings, and counsel’s inferences are distinguishable.
• Comparisons cite matter records and expose adverse facts or gaps.
• Contrary-authority and treatment checks state their dates and scope.
• Open issues have owners; unverified rows remain outside approved support.
• The synthesis answers the assigned question without overstating the record.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its chronology capabilities and trial-preparation tools can support the document review and evidence analysis underlying factual comparisons. The matrix remains counsel’s work product; counsel must verify opinions, subsequent treatment, and legal conclusions. Book a demo to discuss that supporting workflow.

Frequently asked questions

Should statutes and rules appear in a case law matrix?

Yes, as labeled baseline rows. They define research questions but are not judicial holdings. Add decisions separately and distinguish discovery protection from substantive trade-secret status.

Can one decision cover several alleged secrets?

Yes. Use separate rows when the analogy differs. Restricted calibration files and externally circulated pricing information may require different comparisons even under the same opinion.

How should counsel handle a useful pleading-stage decision on summary judgment?

Identify the difference expressly. Research decisions addressing the developed evidentiary record; do not treat acceptance of allegations as a finding that comparable evidence proves the claim.

When is the matrix ready for use?

When proposed propositions and pinpoints are verified, material contrary authority is addressed, and factual dependencies are resolved or assigned. A planning row can guide investigation but should not silently become filing support.

Sources

• 18 U.S.C. § 1839, official 2024 Code text: federal definitions.
• Federal Rules of Civil Procedure: Rule 26 discovery scope and protective orders.
• Oakwood Laboratories LLC v. Thanoo, No. 19-3707, Third Circuit opinion: identification and use at the pleading stage.

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.