Trade Secret Defense Checklist: A Practical Checklist

How to use this checklist

A trade secret defense is mostly a sequencing problem. The worst losses happen in the first week, and the most useful evidence (logs on rolling retention, memories, an engineer's old laptop) disappears quietly if nobody moves. Work phases 0 through 3 at once and in order. Phases 4 through 7 overlap. Phases 8 through 12 follow the docket.

The checklist assumes a federal claim under the Defend Trade Secrets Act (DTSA) with a parallel state claim. California differences are noted because they change the proof. Assign an owner and a date next to each task you adopt. Tasks that do not apply can be struck, but note why, because the reason may matter later.

For the reasoning, read Defending a Trade Secret Claim: Reverse Engineering, Independent Development, Public Disclosure, and Readily Ascertainable Information. For the narrative with sample language, use Building a Trade Secret Defense From the First Demand Letter: A Practical Guide. For the forms, go to the Trade Secret Defense Toolkit: Independent Development Records, Public Domain Charts, and Bad Faith Fee Motions.

Phase 0: Containment (first 48 hours)

• Stop casual discussion of the letter. Issue a short counsel-directed note: no chat or email about the merits, no product comparisons, no looking for old files. Privilege protects communications for legal advice under Upjohn Co. v. United States, 449 U.S. 383 (1981); it does not protect a joke in an engineering channel.
• Log the letter. Record date and manner of receipt, sender, claimed owner, statutes cited, claimed information, deadline, and other recipients. Note: Receipt may change state of mind going forward. Knowledge or "reason to know" is an element for some forms of misappropriation under 18 U.S.C. § 1839(5).
• Calendar the deadline and the likely emergency window. A letter's deadline is not binding. A TRO application could follow it, and sometimes precedes it.
• Compute a preliminary limitations date. Three years back from today under 18 U.S.C. § 1836(d). Note public launches, trade shows, and departures before that date.
• Notify insurers and check indemnities. Tender under any policy that could respond, and review vendor, customer, and investor agreements for notice duties.
• Decide who speaks to the sender. One person, normally outside counsel.

Red flag: Someone has already responded informally ("we'd be happy to look into it") or forwarded the letter with commentary. Preserve those messages, do not repeat them, and assume they will be produced.

Phase 1: Preservation

• Issue a written hold. The duty attaches when litigation is reasonably anticipated. Zubulake v. UBS Warburg LLC, 220 F.R.D. 212 (S.D.N.Y. 2003). The sanctions framework for lost electronic data is Fed. R. Civ. P. 37(e). See Litigation Hold and Evidence Preservation Checklist: A Practical Checklist.
• Lock source control. Turn on branch protection, disable force pushes, stop automatic branch deletion, and make a mirror clone with all refs. Save hashes of the mirror. Note: Ordinary rebases and squash merges destroy history that could be your best evidence. New commits may continue.
• Capture hosting provider and CI logs. Export audit logs, push events, pull request data, build logs, and artifact listings, and extend retention. Note: These are often on short rolling windows, and they are the third-party anchors for git dates.
• Suspend auto-deletion in chat, email, ticketing, and shared drives. Cover ephemeral and personal messaging used for work.
• Secure lab and plant records. Notebooks, batch records, retained samples, certificates of analysis, supplier invoices, and instrument computers.
• Pull departed-employee devices from any reimaging queue, and stop mailbox deletions.
• Preserve AI tool records. Prompt histories and assistant logs, wherever retained.
• Identify personal accounts and devices of accused people. Collect by vendor. Do not self-collect.
• Quarantine, never destroy, anything that looks like claimant material. Move custody to outside counsel or a neutral vendor, with a log, and without opening it more than necessary.
• Respond to any "return or destroy" demand in writing. State that you are preserving and will discuss a protocol.

Red flag: An engineer says "I deleted it when the letter came, to be safe." Stop, image the device immediately, consult forensic help about recovery, and treat this as a potential Rule 37(e) problem that counsel needs to manage now.

Phase 2: Representation and privilege

• Decide whether company and accused individuals can share counsel. Assess conflicts if an individual may have acted without company knowledge.
• Screen for criminal exposure. Theft of trade secrets is a federal crime under 18 U.S.C. § 1832. An individual who may have exposure needs independent advice before any interview.
• Give corporate warnings at every interview. Counsel represents the company, and the privilege belongs to the company. Upjohn.
• Retain forensic and technical consultants through counsel. Written engagement stating that the work assists counsel in giving legal advice. United States v. Kovel, 296 F.2d 918 (2d Cir. 1961). Claim work product under Fed. R. Civ. P. 26(b)(3). Note: A report shared widely, or commissioned for business reasons, may not hold. Waymo LLC v. Uber Technologies, Inc., 870 F.3d 1350 (Fed. Cir. 2017), is the reminder from a pre-acquisition forensic report. See Conducting an Internal Investigation: Scope, Privilege, and Reporting.
• Limit distribution of findings to those who need them for legal decisions. Report orally where you can.
• Consider at-issue waiver before relying on the investigation. If the plan is to tell a court you investigated, decide what you are prepared to produce.
• Plan for a Fed. R. Evid. 502(d) order at the first case management opportunity. See Privilege Clawback and Rule 502 Checklist: A Practical Checklist.

Phase 3: Fact finding

• Map access. For each former employee or contractor: dates, role, agreements signed, systems accessible, and exit paperwork.
• Map possession. Search company and collected personal sources for claimant material by name, property, watermark, and term.
• Build a dated development chronology. Start date, milestones, people, decisions, sources.
• Separate similarities by cause: copied, standard-driven, function-driven, common in the field, coincidental. The access-plus-similarity inference needs shared innovative features. Stratienko v. Cordis Corp., 429 F.3d 592 (6th Cir. 2005).
• Check for tells: identical bugs, typos, constants, or functionless ingredients. These were strong proof in Motorola Solutions, Inc. v. Hytera Communications Corp., 108 F.4th 458 (7th Cir. 2024).
• Review speed. How long did similar work take elsewhere, and how long here? Rapid arrival after a hire hurt the defense in Vermont Microsystems, Inc. v. Autodesk, Inc., 88 F.3d 142 (2d Cir. 1996), and Integrated Cash Management Services, Inc. v. Digital Transactions, Inc., 920 F.2d 171 (2d Cir. 1990).
• Collect all agreements with the claimant. NDAs, licenses, supply terms, employment and separation agreements, click-through terms.
• Classify the matter: clean, contaminated, or copied. Decide next steps accordingly. Note: If copied material is in the product, evaluate an isolated rewrite. In Computer Associates International, Inc. v. Altai, Inc., 982 F.2d 693 (2d Cir. 1992), excluding the programmer, locking away the code, and using eight unexposed programmers supported the rewritten version, but the trade secret claim on the earlier conduct still went back for a merits decision.

Red flag: Your first big commit or first good batch appears right after a hire, and nothing earlier exists. Find the explanation before anyone signs a denial. If there is none, change the strategy.

Phase 4: Responding to the letter

• Choose the response type: holding letter, denial plus identification demand, outside-counsel exchange, standstill, declaratory action, or business resolution.
• Check every factual sentence against what the investigation has confirmed.
• Demand identification and the date of first knowledge. Offer to receive identification on an outside-counsel-only basis.
• Do not attach technical or development detail. A first letter is not the place.
• Treat Fed. R. Evid. 408 as limited protection. It reaches compromise negotiations, and its uses have exceptions.
• Evaluate declaratory relief. Actual controversy under MedImmune, Inc. v. Genentech, Inc., 549 U.S. 118 (2007), and discretion under 28 U.S.C. § 2201. See Declaratory Judgment Checklist: A Practical Checklist.
• Price any tolling agreement. Limitations may be worth more than the time you get. Insulet Corp. v. EOFlow, Co., No. 25-1807 (Fed. Cir. May 28, 2026).
• Instruct the accused hire in writing not to use or disclose claimant information, and document that instruction. See Competitor Hire Trade Secret Checklist: A Practical Checklist.

Phase 5: Forcing identification

• Raise sequencing at the Rule 26(f) conference and in the scheduling proposal under Fed. R. Civ. P. 16 and Rule 26. Ask that identification precede your technical production. Note: In California state court, Code of Civil Procedure § 2019.210 requires identification before related discovery. In the Ninth Circuit, a court may not strike secrets as a sanction merely for imprecise early disclosure, and particularity is a fact question. Quintara Biosciences, Inc. v. Ruifeng Biztech, Inc., No. 23-16093 (9th Cir. Aug. 12, 2025).
• Serve a pointed interrogatory under Fed. R. Civ. P. 33 on each secret, its embodiments, and first knowledge.
• Test the identification against the standard: does it separate the secret from general knowledge in the trade? Imax Corp. v. Cinema Technologies, Inc., 152 F.3d 1161 (9th Cir. 1998). See Trade Secret Identification and Discovery Checklist: A Practical Checklist.
• For software, ask for method, not function. NEXT Payment Solutions, Inc. v. CLEAResult Consulting, Inc., No. 24-1377 (7th Cir. Jan. 13, 2026).
• Keep a version table of every identification, with dates. Repeat failures were central in Gabriel Technologies Corp. v. Qualcomm Inc., 560 F. App'x 966 (Fed. Cir. 2014).
• Notice a Rule 30(b)(6) deposition on the secret's identity. Binding definitions helped in Stutz Motor Car of America, Inc. v. Reebok International, Ltd., 909 F. Supp. 1353 (C.D. Cal. 1995).

Red flag: Your engineers ask to see the plaintiff's identification. Do not allow it until you have thought through the protective order and clean team consequences. Exposure can undermine future independent development.

Phase 6: Element-by-element screen

Is it secret?

• Search the claimant's own patents, published applications, and foreign counterparts. Disclosure in a patent ends secrecy for what it discloses. Attia v. Google LLC, 983 F.3d 420 (9th Cir. 2020); On-Line Technologies, Inc. v. Bodenseewerk Perkin-Elmer GmbH, 386 F.3d 1133 (Fed. Cir. 2004); 35 U.S.C. § 122(b).
• Search third-party and foreign patents. Ultimax Cement Mfg. Corp. v. CTS Cement Mfg. Corp., 587 F.3d 1339 (Fed. Cir. 2009).
• Search literature, standards, supplier datasheets, textbooks, public code. "Generally known in an industry" is enough. Ruckelshaus v. Monsanto Co., 467 U.S. 986 (1984).
• Check the claimant's own disclosures: marketing, talks, regulatory and government reports, prior court files. CVD, Inc. v. Raytheon Co., 769 F.2d 842 (1st Cir. 1985).
• Assess how widely any web or court disclosure was actually seen. Hoechst Diafoil Co. v. Nan Ya Plastics Corp., 174 F.3d 411 (4th Cir. 1999) (a public court file alone was not enough); Religious Technology Center v. Lerma, 908 F. Supp. 1362 (E.D. Va. 1995) (file plus Internet posting).
• Identify what a user or buyer can see. IDX Systems Corp. v. Epic Systems Corp., 285 F.3d 581 (7th Cir. 2002).
• Address the combination. Components being public does not end the matter. Minnesota Mining & Manufacturing Co. v. Pribyl, 259 F.3d 587 (7th Cir. 2001); Tewari De-Ox Systems, Inc. v. Mountain States/Rosen, L.L.C., 637 F.3d 604 (5th Cir. 2011); AvidAir Helicopter Supply, Inc. v. Rolls-Royce Corp., 663 F.3d 966 (8th Cir. 2011).
• Assign the readily ascertainable burden by forum. In the definition under 18 U.S.C. § 1839(3)(B) and most state acts. A defense in California under ABBA Rubber Co. v. Seaquist, 235 Cal. App. 3d 1 (1991), and CACI No. 4420. Note: ABBA frames the California defense around whether the defendant's knowledge actually resulted from the honest route. If it came from the plaintiff's records, this defense is weak.
• Quantify "readily." Actual time, cost, and tools from a real test, not an estimate. The estimate failed in SI Handling Systems, Inc. v. Heisley, 753 F.2d 1244 (3d Cir. 1985).

Measures and value

• Audit the claimant's protections: agreements, marking, access controls, vendor flow-downs. Expect a jury question. Rockwell Graphic Systems, Inc. v. DEV Industries, Inc., 925 F.2d 174 (7th Cir. 1991).
• Enforce NDA formalities. Marking and written confirmation terms have decided claims. Convolve, Inc. v. Compaq Computer Corp., 527 F. App'x 910 (Fed. Cir. 2013).
• Test independent economic value from secrecy. Direct Technologies, LLC v. Electronic Arts, Inc., 836 F.3d 1059 (9th Cir. 2016).

Acquisition, use, knowledge

• Walk each link in the chain of duty. Chicago Lock Co. v. Fanberg, 676 F.2d 400 (9th Cir. 1982).
• Confirm the defendant had knowledge of the secret and did more than run a product made with it. Silvaco Data Systems v. Intel Corp., 184 Cal. App. 4th 210 (2010), disapproved on another ground, Kwikset Corp. v. Superior Court, 51 Cal. 4th 310 (2011).
• Separate general skill from specific secrets. AMP Inc. v. Fleischhacker, 823 F.2d 1199 (7th Cir. 1987). But memorized information can qualify. Ed Nowogroski Insurance, Inc. v. Rucker, 971 P.2d 936 (Wash. 1999).
• Prepare for "modification is no defense." Mangren Research & Development Corp. v. National Chemical Co., 87 F.3d 937 (7th Cir. 1996).

Time, displacement, and other defenses

• Run the limitations analysis: first access, first public signs of similarity, plaintiff's first internal notice. Insulet; CMI Roadbuilding, Inc. v. Iowa Parts, Inc., 920 F.3d 560 (8th Cir. 2019). Note: Treat related secrets as one clock, where the theory is one relationship, as the Insulet panel did (a petition for rehearing en banc was filed in July 2026). Under California law, continued use is part of one claim. Cadence Design Systems, Inc. v. Avant! Corp., 29 Cal. 4th 215 (2002). For third parties, see Cypress Semiconductor Corp. v. Superior Court, 163 Cal. App. 4th 575 (2008).
• List state claims for displacement. Compare Silvaco with Burbank Grease Services, LLC v. Sokolowski, 717 N.W.2d 781 (Wis. 2006), and Angelica Textile Services, Inc. v. Park, 220 Cal. App. 4th 495 (2013). The DTSA itself displaces nothing. 18 U.S.C. § 1838.
• Check copyright preemption of the non-trade-secret counts. 17 U.S.C. § 301. See Copyright Preemption Analysis Checklist: A Practical Checklist.
• Screen § 1833(b) immunity for individuals. Confidential disclosure to counsel or government, solely to report or investigate. 18 U.S.C. § 1833(b). Also check whether the employer gave the required notice. See Unum Group v. Loftus, 220 F. Supp. 3d 143 (D. Mass. 2016).
• Screen unclean hands only where the plaintiff's misconduct relates directly to the transaction. Unilogic, Inc. v. Burroughs Corp., 10 Cal. App. 4th 612 (1992).

Phase 7: Independent development and reverse engineering proof

• Confirm the legal basis. Neither reverse engineering nor independent derivation is improper means. 18 U.S.C. § 1839(6)(B); Kewanee Oil Co. v. Bicron Corp., 416 U.S. 470 (1974); Bonito Boats, Inc. v. Thunder Craft Boats, Inc., 489 U.S. 141 (1989).
• Know the burden. The burden of production may shift, but the burden of proof stays with the plaintiff in California. Sargent Fletcher, Inc. v. Able Corp., 110 Cal. App. 4th 1658 (2003). Check your forum.
• Build a feature ledger tying each accused feature to a date, person, source, and record.
• Anchor repository dates externally. Provider logs, CI records, invoices, tickets, and customer deliveries. Commit timestamps alone are self-reported.
• Preserve failures. Reverted commits, abandoned branches, and failed batches.
• Prove clean acquisition for any teardown. Receipt, chain of custody, license terms read and analyzed. Note: A contract ban can turn a teardown into a breach, and the plaintiff may then argue improper means under 18 U.S.C. § 1839(6)(A). DVD Copy Control Ass'n v. Bunner, 116 Cal. App. 4th 241 (2004), involved that theory. See Software Interoperability and Reverse Engineering Clearance Checklist: A Practical Checklist.
• Plan admissibility. Fed. R. Evid. 901, 902, and 803(6). See Hearsay and Business Records Checklist: A Practical Checklist.
• Select witnesses who can explain the path in plain language, and who were not exposed to the claimant's identification.
• Retain a testifying expert who can meet Fed. R. Evid. 702. Have the expert test the public domain position.

Red flag: A witness can only say "that's just how you do it." Find the textbook, class notes, or earlier project that shows it, or expect the jury to infer that the source was the former employer.

Phase 8: Pleadings and Rule 11

• Decide on forum and removal. 28 U.S.C. § 1441.
• Screen Rule 12 grounds: publication on the face of the record, time bar, displaced counts, no duty. Measure under Bell Atlantic Corp. v. Twombly, 550 U.S. 544 (2007), and Ashcroft v. Iqbal, 556 U.S. 662 (2009), but expect generous treatment of well-pleaded trade secret facts. Oakwood Laboratories LLC v. Thanoo, 999 F.3d 892 (3d Cir. 2021).
• Plead limitations and all other affirmative defenses under Fed. R. Civ. P. 8(c). Also plead independent derivation and reverse engineering, without assuming the burden.
• Evaluate counterclaims under Fed. R. Civ. P. 13. Declaratory relief, contract, and in rare cases antitrust. CVD.
• Check your own Rule 11 obligations. Denials must be warranted on the evidence. Fed. R. Civ. P. 11(b).
• Consider a Rule 11 safe harbor letter or motion. Service starts 21 days. See Rule 11 Sanctions and Safe Harbor Checklist: A Practical Checklist.

Phase 9: Emergency relief

• Assemble a ready file: draft declaration, chronology, public sources, delay evidence, hardship numbers, proposed stipulation.
• If there is an ex parte seizure, comply, record everything, and seek the prompt hearing. 18 U.S.C. § 1836(b)(2).
• Challenge identification first. Insulet Corp. v. EOFlow, Co., 104 F.4th 873 (Fed. Cir. 2024); Mallet & Co. v. Lacayo, 16 F.4th 364 (3d Cir. 2021).
• Contest irreparable harm. No presumption. First Western Capital Management Co. v. Malamed, 874 F.3d 1136 (10th Cir. 2017); Faiveley Transport Malmo AB v. Wabtec Corp., 559 F.3d 110 (2d Cir. 2009). Show delay. Citibank, N.A. v. Citytrust, 756 F.2d 273 (2d Cir. 1985) (a trademark case).
• Apply employment limits. 18 U.S.C. § 1836(b)(3)(A)(i). In California, add Whyte v. Schlage Lock Co., 101 Cal. App. 4th 1443 (2002).
• Quantify the bond. Fed. R. Civ. P. 65(c).
• Propose a narrow stipulation. Specific documents, quarantine, no concession of secrecy, no restriction on existing products without proof.

Red flag: A proposed order prohibits use of "confidential information." Object. It is unworkable, overbroad, and inconsistent with Rule 65(d).

Phase 10: Discovery

• Negotiate the protective order with your own team in mind. See Protective Order and Sealing Checklist: A Practical Checklist. Consider who may see the plaintiff's list, and adopt a clean team protocol.
• Retain an outside expert early and clear that person under the order.
• Request first-awareness documents, competitive intelligence, and early legal holds.
• Request every disclosure of the claimed secret. Subpoena vendors under Fed. R. Civ. P. 45.
• Limit source code production to the identified secrets, in a controlled review environment. See Managing Discovery in a Trade Secret Case: A Practical Guide.
• Sort the plaintiff's privilege log by date. The first entry mentioning you may matter.
• Prepare your witnesses for questions about the origin of their knowledge. See Deposition Witness Preparation Checklist: A Practical Checklist.
• Obtain a Rule 502(d) order.

Phase 11: Summary judgment and experts

• Move on identification, with the plaintiff's own lists as exhibits. NEXT Payment; IDX.
• Move on public disclosure with an element-by-element chart and pin cites.
• Move on no use, with declarations and with similarity limited to innovative features. Stratienko.
• Move on limitations with the plaintiff's documents. Insulet.
• Move on displacement and contract terms where the issues are legal.
• Anticipate a Rule 56(d) request. A premature motion can be reversed. InteliClear, LLC v. ETC Global Holdings, Inc., 978 F.3d 653 (9th Cir. 2020).
• Challenge any expert whose similarity opinion ignores the public domain.

Phase 12: Trial, fees, and resolution

• Request instructions on burden, reverse engineering, independent derivation, and general skill. Sargent Fletcher.
• Seek a secret-by-secret verdict form, with limitations dates.
• Plan for sealing at trial. Protective-order rights can be waived. Littlejohn v. BIC Corp., 851 F.2d 673 (3d Cir. 1988).
• Move under Rule 50(a) on every element, including protectability. A challenge left out was forfeited in Harbor Business Compliance Corp. v. Firstbase.io, Inc., No. 25-1278 (3d Cir. Aug. 27, 2025). Renew under Rule 50(b).
• Prepare the damages defense regardless. See Trade Secret Damages and Remedies Checklist: A Practical Checklist.
• Send defect letters throughout the case. They become the fee record.
• Oppose dismissal without prejudice, or seek conditions, under Fed. R. Civ. P. 41(a)(2). Dunster Live, L.L.C. v. LoneStar Logos Management Co., 908 F.3d 948 (5th Cir. 2018).
• Calendar the fee motion. Fed. R. Civ. P. 54(d)(2), generally 14 days after judgment absent another rule or order.
• Brief the correct bad-faith standard for your forum. 18 U.S.C. § 1836(b)(3)(D); Recoop LLC v. Outliers Inc., No. 1:24-cv-01810 (S.D.N.Y. June 20, 2025) (survey); FLIR Systems, Inc. v. Parrish, 174 Cal. App. 4th 1270 (2009); Gemini Aluminum Corp. v. California Custom Shapes, Inc., 95 Cal. App. 4th 1249 (2002).
• Present persistence evidence, and address the "lost is not bad faith" line head on. Applied Predictive Technologies, Inc. v. MarketDial, Inc., No. 2:19-cv-00496 (D. Utah Mar. 25, 2025); Wilbur-Ellis Co. v. Gompert, No. 8:21-cv-00340 (D. Neb. July 22, 2025).
• In any settlement, seek no admission, a release covering future versions, a narrow description of restricted information, an end date on audits, and permission to lift the hold when appropriate.

Red flag: A settlement requires your team to certify that it "does not possess any confidential information of the claimant." Your engineers cannot give that certification without being told what the information is. Tie it to a specific list and a specific forensic process.

This checklist is a general working aid, and it does not replace advice about your own facts, contracts, and forum.

Related Documents

Related Articles

• Defending a Trade Secret Claim: Reverse Engineering, Independent Development, Public Disclosure, and Readily Ascertainable Information: the doctrine and leading cases behind these tasks.
• Identifying Trade Secrets in Litigation: Reasonable Particularity, Sequencing Discovery, and Protecting the Secret While You Sue: the law behind Phase 5.
• Litigation Holds, Spoliation, and Rule 37(e): Preserving Electronic Evidence Before It Costs You the Case: the law behind Phase 1.

Related Guides

• Building a Trade Secret Defense From the First Demand Letter: A Practical Guide: the narrative version, with sample language.
• Managing Discovery in a Trade Secret Case: A Practical Guide: detail for Phase 10.
• Proving or Defending Against Trade Secret Damages: A Practical Guide: the damages defense.

Related Checklists

• Trade Secret Identification and Discovery Checklist: A Practical Checklist: more on identification.
• Trade Secret Damages and Remedies Checklist: A Practical Checklist: remedies tasks.
• Litigation Hold and Evidence Preservation Checklist: A Practical Checklist: hold mechanics.
• Hearsay and Business Records Checklist: A Practical Checklist: admitting logs and records.
• Privilege Clawback and Rule 502 Checklist: A Practical Checklist: privilege protection in production.

Related Toolkits

• Trade Secret Defense Toolkit: Independent Development Records, Public Domain Charts, and Bad Faith Fee Motions: forms for these tasks.
• Trade Secret Litigation Toolkit: Identification Statements, Two-Tier Protective Orders, and Forensic Protocols: identification statements and protective orders.