Prepare a trade-secret document collection checklist by linking each alleged secret to the people, systems, and records that can establish—or undermine—secrecy, economic value, acquisition, disclosure, and use. Define collection boundaries, record preservation risks and access authority, and specify how each source will be collected and verified. The deliverable is a source-level checklist showing what counsel needs, why it matters, who is responsible, what has been collected, and which gaps remain. Keep collection status separate from privilege review and production readiness.
Use this workflow when an employee departure, suspected transfer, competing product, demand letter, or discovery request requires counsel to collect evidence concerning alleged trade secrets. It serves claimant and defense teams: both need unfavorable documents and lawful explanations, not merely records supporting the initial account.
The scope is collection planning and verification, not a complete discovery response or forensic investigation. The legal references use a US federal baseline; they do not govern every state-court dispute or arbitration. Check applicable state law, controlling decisions, local rules, and case-specific orders. The collection controls below are practical recommendations, not universal legal requirements. Collection from personal devices, shared accounts, or third parties requires a separate authority assessment.
Start with a preliminary description of the alleged information, not simply a business label such as “our technology.” Assemble:
Separate source facts from interview recollections. A manager’s assertion that a repository was restricted is a lead; historical permissions and access activity are collection targets that can test it. Likewise, development spending may identify useful value records, but counsel should seek evidence explaining the claimed commercial benefit of secrecy rather than treating cost alone as the answer.
The companion template is Trade Secret Disputes — Document collection checklist. Copy this table into your working document or spreadsheet. Use one row per bounded source and collection task; split rows when authority, retention risk, or method differs.
| Item / secret ID | Evidence target | Custodian / source | Scope / dates | Risk / authority | Method / verification | Evidence refs | Status / owner / action |
|---|---|---|---|---|---|---|---|
“Evidence target” states the proposition being tested, such as historical secrecy measures or possible independent derivation. “Scope / dates” identifies folders, channels, accounts, versions, and time boundaries rather than merely saying “all relevant documents.”
Record retention concerns and authorized-access grounds in “Risk / authority.” Link detailed instructions, inventories, and verification results in “Method / verification.” “Evidence refs” should resolve to stable document IDs, pages, repository paths, commits, or log rows. Before collection, use an existing source reference if available; do not invent a collected-document identifier.
The last field names an accountable owner and next action. Use distinct statuses such as proposed, authorized, collected, verified, and blocked. Add action dates and their source where timing matters. A verified collection can still await privilege or confidentiality review. Keep the secret’s substantive description in a restricted record rather than reproducing it throughout the checklist.
Assign stable identifiers such as TS-01 and TS-02. Record the claimed information’s boundaries, version, owner, and relevant period in a restricted companion description. Distinguish a claimed compilation from its components: public components and a claimed confidential arrangement may require different evidence. Collect ownership or licensing records where entitlement to the information is disputed.
The federal definition requires reasonable secrecy measures and actual or potential independent economic value 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 label alone does not establish both requirements. See 18 U.S.C. § 1839(3).
Record: secret ID, evidence target, and bounded-description reference. Assign unresolved definition questions rather than using them to justify unlimited technical collection.
For each secret, identify records addressing secrecy, value, acquisition, disclosure, use, knowledge, and consent. Include potential counterevidence: public releases, licensed disclosures, earlier development work, or instructions authorizing a transfer. Link each target to a factual question, not a predetermined conclusion.
Section 1839 distinguishes improper acquisition from unauthorized disclosure or use, subject to specified knowledge conditions. It excludes reverse engineering, independent derivation, and other lawful acquisition from improper means. Those exclusions do not determine separate contractual restrictions. See 18 U.S.C. § 1839(5)–(6).
Record: the proposition and competing explanation in separate rows where they require different sources. Do not treat access logs alone as proof of competitive use; identify what additional records could test that inference.
Interview business and technical personnel about where relevant records actually reside. Distinguish mailboxes from shared repositories, identity-provider logs, service accounts, removable media, and personal messaging. Ask who administered permissions and whether historical configurations remain available.
Prioritize sources vulnerable to overwrite or loss of access. Confirm actual retention settings with the system owner, and connect urgent risks to the preservation process before waiting for routine collection approval. Record who confirmed the setting and when. For unavailable systems, identify backups, exports, or recipient copies without treating them as equivalent evidence.
Record: custodian, system owner, account identifiers, coverage dates, retention risk, and responsible person. Assign unknown retention settings for prompt technical confirmation; “unknown” is not evidence that the records are safe.
Define folders, channels, versions, devices, and date ranges. Explain why repository history or a targeted collection fits the disputed conduct. Cross-reference overlapping request identifiers rather than duplicating extraction. A narrow search should not exclude earlier versions needed to test independent development or permission changes.
In federal litigation, 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 the applicable motion and good-cause showing. These provisions do not supply blanket permission to access another person’s device. See Federal Rule of Civil Procedure 26.
Record: scope rationale, authorization basis, restrictions, and unresolved approvals. Identify personal-device and nonparty sources requiring separate instructions. Discovery scope and collection access are related decisions, not interchangeable permissions.
Give source-specific instructions. For source code, identify repositories, branches, commits, and associated history. For cloud shares, distinguish contents from permissions and activity logs. For messaging, identify participants, channels, attachments, and surrounding context. Ask whether the proposed export omits deleted items, historical versions, or other requested information.
Have technical personnel document method, collector, collection date, source location, time zone, and transformations. Retain an unchanged collected copy and document later processing separately. Decide whether specialist assistance is needed before device examination or unfamiliar extraction. Restrict sensitive material and route potentially privileged records for separate review.
Record: approved method, collector, destination reference, handling restrictions, and verification plan. These controls do not imply that one method satisfies every evidentiary requirement.
Compare the delivered inventory with the instructions. Test representative files for readability, attachments, version information, and timestamps. Check whether logs span the requested period and whether gaps reflect retention, export limitations, or unresolved error. Document sampling boundaries rather than implying that every item was examined.
Preserve account attribution and distinguish individual users from shared credentials or service accounts. Retain information supporting later authentication: Federal Rule of Evidence 901(a) requires evidence supporting a finding that an item is what its proponent claims. Authentication does not independently resolve hearsay. See Federal Rule of Evidence 901.
Record: inventory references, source pinpoints, verification results, exceptions, and corrective instructions. Mark a source verified only against the scope actually checked, with the verifier and verification date identifiable.
Review unresolved rows with counsel and the technical owner. Distinguish material not collected, unreadable material, unavailable historical records, and collected material awaiting review. Each condition needs a different response. Preserve superseded instructions so later reviewers can understand why scope changed.
For collection supporting a federal party production request, maintain a linked request tracker. Rule 34(b)(2)(B)–(C) requires specific objections and disclosure of whether responsive materials are withheld on an objection. Internal collection status does not satisfy that response obligation; nonparty subpoenas require separate analysis. See Federal Rule of Civil Procedure 34.
Record: accepted scope, gap, owner, next decision, and handoff reference. “Collection complete” should mean completion of the stated task, not completion of privilege review, production, or the investigation.
Fictional scenario: All parties, records, and identifiers below are fictional. Alder Circuit Labs alleges that a departing engineer transferred TS-01, a calibration-parameter compilation, before joining Brookline Instruments. Counsel represents Alder. The initial packet contains a transfer alert, a signed confidentiality agreement, and a product manager’s assertion that the compilation was restricted.
Counsel defines TS-01 as the compilation in repository release R7, not every engineering file. The alert identifies a service account rather than the engineer’s account. Alder also supplied some calibration data to a distributor. No recipient-device evidence is available, and the distributor’s actual attachments have not been compared with R7.
| Item / secret ID | Evidence target | Custodian / source | Scope / dates | Risk / authority | Method / verification | Evidence refs | Status / owner / action |
|---|---|---|---|---|---|---|---|
| C01 / TS-01 | Historical restrictions and exceptions | IT / repository | R7 permissions during alleged transfer period | Historical coverage unknown; internal access approved | Current export received; history outstanding | ALD-002, permissions tab | Partial / IT lead / retrieve history; present settings do not prove past restrictions |
| C02 / TS-01 | Transfer attribution | Security / activity logs | Alert day and adjacent activity | Retention unconfirmed; internal access approved | Alert preserved; raw events and mapping outstanding | ALD-003, row 18 | Open / security lead / obtain mapping; individual attribution unresolved |
| C03 / TS-01 | Authorized disclosure scope | Sales / distributor folder | R7-related sends and attachments | Folder access approved; archive coverage unknown | Inventory received; attachment comparison pending | ALD-004, inventory item 9 | Open / counsel / compare files with R7; consent and disclosure scope unresolved |
The checklist changes the immediate decision. Instead of expanding every employee mailbox, counsel prioritizes historical permissions, attribution, and authorized-disclosure records. The signed agreement, ALD-001, supplies a confidentiality-obligation lead but does not fill the historical access gap.
The alert supports investigating a reported transfer, not concluding that the engineer acquired or used TS-01. Distributor sharing could involve different data, restricted disclosure, or a material exception; the inventory alone cannot resolve those alternatives. Counsel therefore keeps these issues open without inventing recipient evidence or abandoning other collection targets.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. After authorized collection, counsel can use document review, privilege and confidentiality analysis, and evidence analysis to examine the record. The chronology viewer supports organizing relevant events, while trial preparation capabilities support later litigation work. The checklist remains counsel’s work product; access authority, technical verification, and legal conclusions require human judgment. Book a demo to discuss review of a trade-secret collection.
Use a bounded description and restricted reference where practical. Give collectors enough information to identify the correct material without reproducing sensitive code, formulas, or parameters throughout an operational tracker. Restrict access to the detailed description separately.
Not automatically. Identify versions relevant to ownership, secrecy measures, alleged access, and independent development. Record why additional history is needed or excluded. Revisit that decision when evidence changes the relevant period or reveals a different version was transferred.
Record the anticipated evidence, but do not instruct extraction until counsel resolves authority and scope. Identify company-side records that can be collected separately. Do not assume employment history or a confidentiality agreement itself authorizes device access.
Close a defined task with a documented exception, not an assertion that the evidence was collected. Record confirmed coverage, the supporting technical account, substitute sources considered, and counsel’s next decision. Keep a material unresolved investigation issue open separately.
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.