How to inventory alleged trade secrets and access evidence for Trade Secret Disputes

Inventory alleged trade secrets by assigning each claimed item a stable identifier, bounded description, and relevant version, then linking it to evidence of secrecy, economic value, and access. Separate permissions, observed activity, and alleged acquisition, disclosure, or use. The resulting trade secret access matrix should identify what each source supports, competing explanations, and the person responsible for resolving each gap. It is an evidence map—not a determination that every confidential file is a trade secret or every download proves misappropriation.

When to use this workflow

Use this workflow when litigation counsel or an in-house team receives allegations involving a departing employee, business partner, or competitor. Claimant’s counsel can test whether defined information connects to accused conduct; defense counsel can identify overbroad descriptions, attribution problems, and lawful explanations.

Keep the scope on inventory and access evidence, not a complete discovery tracker or damages model. The deliverable should support focused collection decisions and a defensible account of what remains unproved.

This guide uses a US federal baseline. Check applicable state law, procedural requirements, arbitral rules, and case orders separately. Before circulating detailed descriptions, determine the identification and confidentiality requirements governing the proceeding. The steps below are workflow recommendations, not additional legal requirements.

What you need

Gather materials that define the claimed information and test the alleged conduct:

• Secret-defining records: identified files, database fields, process specifications, code versions, compilation descriptions, and claimed ownership records.
• Secrecy and value records: executed agreements, historical permissions, training acknowledgments, enforcement records, development records, and contemporaneous explanations of competitive value.
• Access evidence: identity-provider logs, repository audit trails, source-control history, cloud-share records, device evidence, and account-to-person mappings.
• Counterevidence: authorized assignments, public releases, recipient permissions, alternative development histories, and explanations for scheduled exports or automated activity.

Create a source register recording document IDs, custodians, collection dates, and preserved locations. For logs, add event definitions, time zone, coverage period, and known gaps. Confirm collection authority and retention risks before extraction. Where available, preserve the underlying record rather than relying exclusively on screenshots or copied excerpts.

Use the template

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

Use one row per proposition or materially distinct event, not one row per document. Several rows may share a secret ID; one source may support different issues.

“Scope / version” distinguishes the information from neighboring material. Keep the full description, claimed owner, and revision history in a linked inventory keyed to that ID. “Issue / period” identifies secrecy, value, acquisition, disclosure, use, knowledge, consent, or alleged injury and the relevant dates.

“Actor / authority” separates a person from an account and identifies the asserted permission. Keep direct observations separate from inferences and uncertainty. In “Action / owner,” record the task, responsible person, review date, and status; close an issue only with a supporting reference. Use row IDs in correspondence so revisions do not break references.

Step by step

1. Bound each alleged secret before mapping access

Replace labels such as “engineering information” with an identifiable body of information. Record the claimed owner, version, relevant period, and exclusions. Identify a claimed compilation separately from its components; evidence about one component does not necessarily address the compilation.

The federal definition requires reasonable secrecy measures and actual or potential independent economic value arising from the information not being generally known or readily ascertainable through proper means by someone who could obtain economic value from its disclosure or use. A confidentiality stamp does not establish both requirements. See 18 U.S.C. § 1839(3). (uscode.house.gov)

Record: a stable secret ID, bounded scope, source version, and unresolved ownership questions. Preserve earlier descriptions when the claimed scope changes.

2. Separate the propositions requiring evidence

Create distinct rows for the relevant propositions rather than treating access as a substitute for the entire claim. Identify which theory each acquisition, disclosure, or use row tests.

Section 1839(5) distinguishes acquisition through improper means from specified unauthorized disclosure or use, with different knowledge conditions. Section 1839(6) excludes reverse engineering, independent derivation, and other lawful acquisition from improper means. Those exclusions do not themselves resolve separate contractual restrictions. See 18 U.S.C. § 1839(5)–(6). (uscode.house.gov)

Record: the proposition, supporting and contrary sources, and “not established in reviewed materials” where proof is missing. Do not replace that qualified statement with “no evidence exists.”

3. Map repositories and establish coverage

Connect each secret ID to repositories and custodians. Manufacturing information may span laboratory notebooks, equipment settings, and vendor communications; software claims may require historical commits rather than the latest exported folder.

Ask the system custodian what each event means. Does “download” indicate a completed transfer, an initiated request, or synchronization? Check coverage across the alleged period and changes to logging settings. Preserve original timestamps alongside normalized times, documenting the conversion method.

Record: source locations, event and collection dates, coverage limitations, and the technical contact. Mark overlapping exports so duplicate records do not inflate event counts. Assign urgent preservation questions before ordinary analytical follow-up.

4. Distinguish permission, activity, and personal attribution

Compare permissions at the event date with observed activity. Current permissions cannot establish historical access without additional support. Test whether the account identifies the alleged actor: shared credentials, service accounts, delegation, and device reuse may complicate attribution.

An account-linked export does not alone establish its human initiator, contents, or destination. Match the event to the claimed version using file identifiers, manifests, hashes, or other available records—not filename resemblance alone. If those records are unavailable, state the resulting limitation.

Record: account, proposed actor, authority source, observed event, and attribution confidence with reasons. Assign missing identity, content, and destination evidence separately rather than combining them into an unsupported narrative.

5. Test secrecy and value at the relevant time

Compare written precautions with demonstrated practice. Identify who could obtain the information, whether restrictions were applied, and documented exceptions. An agreement signed after the disputed event does not itself establish earlier restrictions.

For value, seek evidence explaining why the specific information mattered because it was not generally known or readily ascertainable. Development spending supplies context but does not answer that question by itself. Include public disclosures and broad distribution alongside favorable records. Match each disclosure to the claimed version before deciding its significance.

Record: dated precautions and value evidence, exceptions, public-material comparisons, and assigned requests for missing historical records. Keep observations distinct from counsel’s legal assessment.

6. Convert gaps into focused evidence requests

Prioritize gaps capable of changing the analysis: archive contents, recipient authority, or whether similar work predated access. Specify the source, custodian, period, and proposition each follow-up would address. Keep broader request administration outside this matrix.

Federal discovery concerns nonprivileged matter relevant to claims or defenses and proportional to case needs. Rule 26(c)(1)(G) permits restrictions on disclosure of trade secrets through a protective order, subject to good cause and applicable motion requirements. Protection is not automatic merely because the inventory contains sensitive descriptions. See Federal Rule of Civil Procedure 26. (uscourts.gov)

Record: focused action, responsible lawyer or investigator, review date, and handling restrictions. Separate counsel’s impressions from any proposed external factual version.

7. Reconcile conclusions to their foundations

Have a second reviewer trace important rows to preserved sources. Verify pinpoints, log definitions, transformations, and whether a proposed witness observed the event or learned about it later.

Federal Rule of Evidence 901 requires support for finding that an item is what its proponent claims. Rule 602 generally requires support for a witness’s personal knowledge, subject to its expert-testimony exception. Authentication does not independently resolve hearsay. See Federal Rules of Evidence 901 and 602. (uscourts.gov)

Record: verification status, foundation witness or task, and disposition of open issues. Decide separately whether the matrix remains internal or needs adaptation for external use; analytical usefulness is not an admissibility determination.

Worked example

Fictional scenario: Harborlight Ceramics alleges that former process engineer Lena Vale exported kiln-calibration information before joining Northbank Materials. All parties, records, identifiers, and events below are fictional.

Counsel receives a folder labeled “secret kiln files.” Review separates TS-01—a version-four calibration compilation for Line C—from public equipment specifications stored beside it. The alleged later use rests on a brochure describing comparable output quality. No archive manifest or contemporaneous economic-value record has been supplied.

The matrix changes priorities. R01 calls for historical permissions rather than reliance on a present-day restriction. R02 directs collection toward export contents and attribution, not every employee communication. R03 prevents product similarity from becoming an unsupported assertion of use.

Counsel should open a separate economic-value row marked “not established in reviewed materials” and assign collection of contemporaneous business evidence. The absence of that evidence does not prove lack of value, but an invented valuation would conceal a material gap.

Common mistakes

• Using a folder name as the definition. Identify information, version, and exclusions; shared storage does not establish a single secret.
• Counting permission as activity. Separate entitlement from observed access and obtain historical permissions where relevant.
• Treating export as disclosure or use. Test content, actor, destination, and subsequent conduct separately.
• Discarding lawful explanations. Retain authorized assignments, automation, public material, and independent-development evidence.
• Removing uncertainty in summaries. Carry material source limitations into management reports and external drafts; brevity should not increase certainty.

Final quality check

• Each secret has an ID, bounded scope, version, period, and claimed owner.
• Compilation claims remain distinguishable from component claims.
• Material observations have verified source IDs and pinpoints.
• Timestamps, conversions, duplicates, and coverage gaps are documented.
• Permissions, activity, attribution, acquisition, disclosure, and use remain distinct.
• Contrary evidence and alternative explanations accompany supporting evidence.
• Open issues are resolved or assigned; circulation matches applicable restrictions.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, chronology, and privilege and confidentiality analysis capabilities can support this source-based inventory. Use the chronology viewer to support event analysis while counsel verifies attribution, legal significance, and missing proof. The matrix remains your work product. To discuss this workflow, book a demo.

Frequently asked questions

How specific should the alleged-secret description be?

Specific enough to distinguish the information, versions, components, and exclusions for evidence matching. Separately check governing identification requirements and case orders; the internal inventory does not substitute for a required disclosure.

Should every access event receive its own row?

Separate events when actor, authority, content, or significance differs. Group repeated events only if underlying references remain traceable and exceptions remain visible.

What if the logs have expired?

Record the missing period and the resulting inference limitation. Investigate repository history, device records, or recipient communications. Missing logs do not establish that access did or did not occur.

Can the matrix become an evidentiary summary?

Not automatically. Federal Rule of Evidence 1006 addresses summaries of voluminous admissible materials that cannot conveniently be examined in court; underlying originals or duplicates must be available to other parties at a reasonable time and place. Distinguish that use from an illustrative aid under Rule 107. See Rules 1006 and 107. (uscourts.gov)

Sources

• 18 U.S.C. § 1839: trade-secret, misappropriation, and improper-means definitions.
• 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.