Building a Trade Secret Defense From the First Demand Letter: A Practical Guide

Suppose a robotics integrator called Kestwick Automation gets a letter on a Friday at 4:40 in the afternoon. It says that Kestwick's new vision-alignment module uses trade secrets of Brennerton Controls, where two Kestwick engineers used to work. By 4:52 the vice president of engineering has forwarded it to a chat channel with the comment "lol, ours is way better than theirs anyway, does anyone still have the old Brennerton docs to compare?" Three engineers react with a laughing emoji. One replies that he thinks he still has a folder somewhere and will take a look over the weekend.

In twelve minutes the company has created a discoverable admission about comparing the products, a possible instruction to access the very documents at issue, and a preservation problem if that engineer decides to tidy up his folder. None of it required bad intent. It was just how people behave when they are confident they did nothing wrong.

Most trade secret defenses are won or lost on records created under this kind of pressure. This guide is the sequence for doing it properly. For the doctrine behind each step, read the companion article, Defending a Trade Secret Claim: Reverse Engineering, Independent Development, Public Disclosure, and Readily Ascertainable Information. For forms you can copy, use the Trade Secret Defense Toolkit: Independent Development Records, Public Domain Charts, and Bad Faith Fee Motions. For the general overview of both sides of a federal case, see Trade Secret Misappropriation Litigation Under the Defend Trade Secrets Act: A Practical Guide.

The short answer

• Hour one: stop talking, preserve, and call counsel. A demand letter usually triggers the duty to preserve. Everything said about it afterward in chat or email outside of a privileged channel may become an exhibit.
• Week one: learn the facts under privilege before you state any facts. Have counsel direct the investigation, retain the forensic and technical consultants, and interview people with proper warnings. Decide early whether the company and the accused employee can share a lawyer.
• Do not destroy "their" documents, even if asked to. Quarantine them with a neutral or outside counsel. Deletion turns a bad fact into a sanctions motion.
• Answer the letter carefully, and usually briefly. Deny only what you know to be untrue, ask what the claimed secret is, and propose a protected way to exchange information.
• Make identification the first battle. Your public domain chart, your independent development comparison, and your expert all depend on it, and the plaintiff's failure to do it well is often its largest weakness.
• Build the proof before you need it. Find third-party anchored development records and public sources during the first month, when logs still exist and people still remember.
• Prepare for an emergency motion now. The party that has a declarant, a chronology, a proposed narrow stipulation, and evidence of the plaintiff's delay on the day the TRO papers arrive has a real chance of avoiding a damaging order.
• Preserve every element at every stage. A sufficiency argument left out of a Rule 50(a) motion can be forfeited, and a fee claim can vanish if the plaintiff dismisses without prejudice.

Step 1: The first 48 hours

Who: general counsel or the owner, outside counsel, and IT. Output: a short written hold, a contained circle of people, a calendar.

Stop the conversation

Tell the people who know about the letter, orally and then in one short written note from counsel, to stop discussing the merits in email or chat, not to go looking at any old documents, and to direct all questions to counsel. Do not ask anyone to compare products yet. Do not tell people they "did nothing wrong." You do not know that yet, and if you turn out to be wrong, the sentence will read badly.

Read the letter for what it actually says

Note who it comes from, whose secret is claimed, what is identified (usually very little), what deadline is set, what the statutes are, who else received a copy (customers, investors, or your employee), and any "return or destroy" demand. Then calendar the deadline as a business fact. A letter's deadline has no legal force on its own, but a plaintiff may seek emergency relief soon after it passes, and sometimes before.

Identify exposure outside the company

Check for insurance and tender early. Commercial general liability policies often exclude intellectual property claims, but other coverage may respond to some allegations, and late notice is an avoidable problem. Check indemnities in vendor and customer contracts. Check loan covenants and investor notice obligations. If a sale or financing is pending, bring in deal counsel at once.

Decide who represents whom

This is where small companies take the worst shortcuts. The company and the accused engineer may have the same defense today and opposite interests next month, for instance if a forensic review shows that the engineer took files without the company's knowledge. If the facts are unknown, the safest approach is often separate counsel for the individual, with the company advancing fees where its documents and law allow, and a written common interest agreement.

Trade secret theft is also a federal crime under 18 U.S.C. § 1832. Where the allegations involve deliberate copying by an individual, that person needs advice about the Fifth Amendment before giving any statement. A company lawyer cannot give that advice.

Step 2: Issue a hold that fits how engineers really work

Who: counsel drafts, IT executes, a named engineering lead confirms. Timing: immediately, then revisit monthly.

The duty arises when litigation is reasonably anticipated. Zubulake v. UBS Warburg LLC, 220 F.R.D. 212 (S.D.N.Y. 2003). Under Rule 37(e), lost electronically stored information can lead to curative measures on a showing of prejudice and, if a party acted with intent to deprive, to an adverse inference or dismissal. The doctrine is covered in Litigation Holds, Spoliation, and Rule 37(e): Preserving Electronic Evidence Before It Costs You the Case and the tasks in Litigation Hold and Evidence Preservation Checklist: A Practical Checklist. What follows are the system-specific points that generic hold notices miss.

Sample hold language for technical staff:

Effective now, do not delete, overwrite, rebase, squash, force-push, or otherwise alter any repository, branch, build record, lab record, or message relating to [project]. Do not open, search, copy, move, or delete any documents from [former employer], in any location, including personal accounts or devices. If you think you may have such material, do nothing with it and call [counsel] today. Keep working normally on new commits. This notice is not a suggestion that anyone did anything wrong.

The instruction not to open is as important as the instruction not to delete. Opening a file after a demand letter changes its last-accessed metadata and may create new "use." Self-collection by the accused engineer is the classic error. Have a vendor do it.

The "return or destroy" demand

Demand letters frequently insist that you immediately return or destroy all material. Do not destroy anything. Reply that you are preserving as the law requires, that any such material located will be segregated with outside counsel or a neutral vendor, and that you will discuss a protocol for its return and remediation. Deleting at the plaintiff's demand has not reliably protected anyone, because the plaintiff can still argue you destroyed evidence of how much you took and what you did with it.

Step 3: Find out what happened, under privilege

Who: outside counsel directs; a forensic vendor and technical consultant report to counsel. Timing: a first answer in one to three weeks; continuing thereafter.

Structure the privilege first

Corporate privilege covers communications with employees at any level to secure legal advice. Upjohn Co. v. United States, 449 U.S. 383 (1981). The privilege belongs to the company, which is why each interview starts with a warning that counsel represents the company and that the company may choose to waive. Consultants can come within the privilege when they help counsel understand the facts. United States v. Kovel, 296 F.2d 918 (2d Cir. 1961). Work product covers materials prepared in anticipation of litigation under Rule 26(b)(3).

These protections are easy to lose. Retain the consultant through counsel. Separate this engagement from any ordinary security vendor work, and do not share the output with business people. Do not circulate conclusions in email. The cautionary example is Waymo LLC v. Uber Technologies, Inc., 870 F.3d 1350 (Fed. Cir. 2017), where a forensic firm hired before an acquisition to investigate former Waymo employees produced a report that the district court ordered disclosed over claims of privilege, and the Federal Circuit declined to disturb the order. MC Law's Conducting an Internal Investigation: Scope, Privilege, and Reporting and the data breach materials on forensic report privilege in Data Breach Class Actions: Article III Standing, Negligence Claims, and Forensic Report Privilege go further. Get a Fed. R. Evid. 502(d) order once in litigation, for the reasons in Rule 502 and Inadvertent Production: Waiver, Clawback Agreements, and Why Every Case Needs a 502(d) Order.

Also think ahead about at-issue waiver. If you later plan to tell a jury "we investigated and found nothing," you may open the investigation to discovery. Some companies run two tracks: a privileged assessment and a separately documented business remediation they are prepared to disclose.

What you need to learn

1. Access. Who came from the plaintiff, when, in what role, with what agreements? What did they actually have access to?
2. Possession. Is any plaintiff-origin material on company systems, personal accounts, or devices? Use searches for file names, hashes if you have them, document properties, watermarks, and terms.
3. Development chronology. When did the accused work begin, who did it, and what was the source of each key decision? Was anything done before the hire or after?
4. Similarity. At a high level, why would someone think these are alike? Are the similarities dictated by function or standards?
5. Plaintiff's disclosures. What did the plaintiff give you, under what NDA, with what markings?
6. Public record. What did the plaintiff publish, patent, sell, or present?
7. Plaintiff's knowledge. When and how might it first have noticed? (Launches, trade shows, former employee reports, customer conversations.)

Three possible answers

At the end of the first pass, sort the matter honestly.

Green: clean record. Development predates or is independent of the hires, no plaintiff material is present, and the similarities are explainable. Move toward a firm denial and an identification demand.

Yellow: contamination without use, or unknown use. Someone has files, but evidence suggests they were not opened or did not feed the product. Quarantine, wall off the person from the project where feasible, and prepare a careful statement that does not overclaim.

Red: actual use of plaintiff material. Move at once to a remediation decision and to a realistic settlement posture. A rewrite on the model of Computer Associates International, Inc. v. Altai, Inc., 982 F.2d 693 (2d Cir. 1992), involved excluding the programmer, locking up the copied code, and using eight programmers with no exposure to the earlier version. It took six months and limited ongoing exposure, but it did not dispose of the claims for the earlier conduct. Keep the original code as evidence. In federal court, Fed. R. Evid. 407 on subsequent remedial measures may offer some protection from use of the rewrite as proof of culpability, though its application to this setting should be researched for your forum and its limits respected.

Step 4: Decide how to respond to the letter

Who: counsel with the decision-maker. Timing: usually within the stated deadline or a short agreed extension.

The options

A declaratory action requires a real controversy under MedImmune, Inc. v. Genentech, Inc., 549 U.S. 118 (2007), and 28 U.S.C. § 2201 leaves the court with discretion. See Filing or Defending a Declaratory Judgment Action: A Practical Guide. It is useful where venue is important, and AvidAir Helicopter Supply, Inc. v. Rolls-Royce Corp., 663 F.3d 966 (8th Cir. 2011), shows both the tactic and its risk: the accused party sued first for a declaration and ended up losing on the trade secret claims.

Drafting principles

Say nothing false, and nothing you might have to retract. Factual statements in the letter can be used as admissions. Statements of compromise have only limited protection under Fed. R. Evid. 408, and marking a letter "Rule 408" does not protect a factual statement made outside a real compromise negotiation. Do not attach your development history to a first letter.

Sample core paragraphs:

[Company] takes intellectual property obligations seriously, and has taken steps to preserve relevant information. Your letter does not identify any specific information that [Claimant] contends is a trade secret. It describes categories that appear to include information that is generally known in the industry or disclosed in [Claimant's] own publications. So that we may evaluate your contention, please identify with reasonable particularity each claimed trade secret, the basis for your belief that [Company] acquired, used, or disclosed it, and the date on which [Claimant] first learned of the facts on which it relies. We are prepared to receive that identification on an outside-counsel-only basis under a suitable agreement.

Based on the information available to us, [Company] denies that it has misappropriated any [Claimant] trade secret. [Use only if true after the investigation.]

Asking for the date of first knowledge is deliberate. It is easy to ignore and awkward to answer, and either result may be useful later. For more on letter strategy generally, see Responding to a Cease and Desist Letter: A Practical Guide.

If the letter went to your employee or your new hire

Expect a parallel letter reminding the individual of their obligations. Do not ignore it. An employer on notice has a different state of mind going forward under 18 U.S.C. § 1839(5). Take the prompt steps described in Onboarding a Competitor's Employee Without Importing Its Secrets: A Practical Guide and consider a written reminder to the employee not to use or disclose former employer information. Use the certification forms in the Lateral Hire Toolkit: Candidate Certifications, Onboarding Instructions, and Cease-and-Desist Responses.

Step 5: Force identification

Who: outside counsel. Timing: in the first letter, in the Rule 26(f) conference, and in your first interrogatories.

Without a defined secret, your team cannot prepare anything rigorous, and the plaintiff keeps the option of redefining the target after it reads your source code. MC Law's Trade Secret Litigation Toolkit: Identification Statements, Two-Tier Protective Orders, and Forensic Protocols and Trade Secret Identification and Discovery Checklist: A Practical Checklist have the forms. Here is the sequence from the defense chair.

In California state court. Code of Civil Procedure § 2019.210 requires identification with reasonable particularity before discovery relating to the secret begins.

In federal court. Rely on Rule 26 and Rule 16 case management authority and on decisions such as DeRubeis v. Witten Technologies, Inc., 244 F.R.D. 676 (N.D. Ga. 2007). Be realistic about the limits. Quintara Biosciences, Inc. v. Ruifeng Biztech, Inc., No. 23-16093 (9th Cir. Aug. 12, 2025), says that a DTSA plaintiff need not identify with particularity from the outset and that striking secrets on that ground was an abuse of discretion. Ask for sequencing, not dismissal. Quintara does not stop a court from ordering sensible disclosure as case management, and the plaintiff still has to identify at summary judgment and trial.

Language for the Rule 26(f) report:

Defendant proposes that within 30 days of entry of a protective order, and before Defendant's production of source code or technical documents, Plaintiff shall serve a statement identifying with reasonable particularity each trade secret it contends was misappropriated. Plaintiff may amend only for good cause shown, and promptly after the basis for amendment becomes known.

An early interrogatory under Rule 33:

For each trade secret you contend was misappropriated, describe it with sufficient particularity to separate it from general knowledge in the trade and from the knowledge of persons skilled in the trade; identify each document embodying it; state the date you first contended it was misappropriated and the date you first learned of facts suggesting it; and state each measure taken to protect it.

Track the changes. Keep a one-page table of each version of the plaintiff's identification, with the date. In Gabriel Technologies Corp. v. Qualcomm Inc., 560 F. App'x 966 (Fed. Cir. 2014), seven failed attempts became a central fact in a large fee award.

Use the corporate deposition. A Rule 30(b)(6) topic on the identity of each secret binds the plaintiff in a practical way. In Stutz Motor Car of America, Inc. v. Reebok International, Ltd., 909 F. Supp. 1353 (C.D. Cal. 1995), the designee's description of the secret as the air bladder and only the air bladder helped dispose of the case.

Step 6: Assemble the independent development file

Who: a lead engineer or chemist who was not accused, working under counsel; a forensic examiner; later, a testifying expert. Timing: start immediately; first version in 30 days.

The file's job is to let a stranger reconstruct where each accused feature came from. Build it as a chronology, feature by feature, once you know the claimed secret. Until then, build it around whatever the plaintiff has pointed to.

Evidence, ranked by how hard it is to fake

1. Records in third parties' hands. Hosting provider logs, supplier invoices, outside lab reports, patent filings, customer deliveries, emails received by outsiders, contract developer invoices.
2. Systems outside the developer's control. Build servers, ticketing systems, and shared drives with server-side version history.
3. Repository contents. Commits and branches, once tied to the above by hash and date. Author dates in git are supplied by the local machine, so they need that tie-in.
4. Contemporaneous personal records. Notebooks, whiteboard photos, personal notes.
5. Later recollection. Useful for explaining the above. Weak standing alone.

What the record should show

• The problem as your team understood it, and alternatives considered.
• Dead ends and failures, including test results that got better slowly.
• Sources: textbooks, open source projects, supplier application notes, consultant advice. Keep copies.
• Who made each decision, and what they had seen before.
• Differences from the plaintiff's approach, particularly on features the plaintiff calls innovative. Stratienko v. Cordis Corp., 429 F.3d 592 (6th Cir. 2005), turned on the plaintiff's failure to identify which innovative features the two products shared.

Plan for the rejoinder that differences are not a defense where the substance is derived from the secret. Mangren Research & Development Corp. v. National Chemical Co., 87 F.3d 937 (7th Cir. 1996).

Reverse engineering, if you did it

Collect the proof of clean acquisition (a retail receipt, or a distributor invoice), the license terms that came with the product, the analysis records, and the time and cost. Have someone read those terms now, not when a plaintiff quotes them to you. A breach of an express restriction can be characterized as improper means. If a teardown has not happened and you are considering one now, get clearance first using Software Interoperability and Reverse Engineering Clearance Checklist: A Practical Checklist, and keep the accused engineers off it.

Do not retroactively paper a reverse engineering story. A retained expert's estimate that it could have been done got little respect in SI Handling Systems, Inc. v. Heisley, 753 F.2d 1244 (3d Cir. 1985).

Admissibility planning

Most of this comes in through a custodian and a knowledgeable engineer. Plan on Fed. R. Evid. 901 for authentication, Rule 902 for certified electronic records and hash-verified copies, and Rule 803(6) for regularly kept records. See Laying the Foundation for Business Records and Defeating Hearsay Objections: A Practical Guide and the certification forms in Business Records Toolkit: Rule 902 Certifications, Foundation Scripts, and Hearsay Response Charts.

Public domain map

In parallel, have someone who knows the field collect the literature. Search the plaintiff's own patents and published applications (including foreign counterparts and file histories), its marketing, its technical papers and conference talks, its regulatory filings, its old websites through web archives, its public code repositories, and its court filings in other cases. Then look at third-party patents, textbooks, standards, supplier datasheets, and competitors' products. Record where each item was found and when, for authentication and to show how accessible it actually is.

The public domain map becomes a column in a chart against each claimed element once the plaintiff identifies. The Federal Circuit's statement in Ultimax Cement Mfg. Corp. v. CTS Cement Mfg. Corp., 587 F.3d 1339 (Fed. Cir. 2009), that a foreign patent is generally known, is reason to search abroad. Tewari De-Ox Systems, Inc. v. Mountain States/Rosen, L.L.C., 637 F.3d 604 (5th Cir. 2011), is a reason to address combinations, not only components.

Step 7: The complaint, the answer, and Rule 11

Who: outside counsel. Timing: answer or motion under Rule 12, generally 21 days after service, unless extended or waived.

Removal and forum

If the case is in state court with a DTSA count, removal under 28 U.S.C. § 1441 is generally available, and 28 U.S.C. § 1367 may bring along the state claims. Consider whether you actually want to leave. California state court gives you § 2019.210 as of right. Federal court gives you Twombly and Iqbal pleading scrutiny and the patent preemption and limitations case law you may prefer.

What a Rule 12 motion can do

Be selective. Courts rarely dismiss for inadequately pleaded reasonable measures or use. Oakwood Laboratories LLC v. Thanoo, 999 F.3d 892 (3d Cir. 2021), vacated a dismissal after reading the pleading requirements generously. Good targets include:

• Published secret. Attia v. Google LLC, 983 F.3d 420 (9th Cir. 2020), affirmed dismissal on the pleadings where publication in patent applications was apparent.
• Time bar on the face of the complaint.
• Displaced state tort counts. Silvaco Data Systems v. Intel Corp., 184 Cal. App. 4th 210 (2010), disapproved on another ground by Kwikset Corp. v. Superior Court, 51 Cal. 4th 310 (2011), is the California starting point. The extra counts often add settlement pressure, so removing them has value.
• No improper means shown on the plaintiff's own theory, such as a chain of duties that does not exist, as in Chicago Lock Co. v. Fanberg, 676 F.2d 400 (9th Cir. 1982).
• Individual defendants with no alleged personal act.

The answer

Under Rule 8, deny what you can deny, and plead limitations and any other affirmative defense. Plead reverse engineering and independent derivation too, while noting they are not your burden. The California rule in Sargent Fletcher, Inc. v. Able Corp., 110 Cal. App. 4th 1658 (2003), is that they are not affirmative defenses, but pleading them eliminates a waiver fight elsewhere. In California, plead readily ascertainable as a defense. Consider counterclaims under Rule 13: a declaration of no misappropriation, contract claims, and in the rare case with real facts, an antitrust theory like the one in CVD, Inc. v. Raytheon Co., 769 F.2d 842 (1st Cir. 1985).

Rule 11, both directions

Your own signature matters. Rule 11(b) requires that denials be warranted on the evidence, or reasonably based on belief or lack of information. If the investigation is unfinished, plead accordingly. Do not sign "Defendant developed all accused technology independently" on an engineer's word alone.

Against the plaintiff, a Rule 11 motion must be served and not filed for 21 days, which makes it a useful, formal notice. Use it sparingly and only with specifics: for example, when the plaintiff's own patent discloses what it now calls secret. The motion's value is often the record it creates for a later fee request. Courts dislike tactical sanctions motions, and in Recoop LLC v. Outliers Inc., No. 1:24-cv-01810 (S.D.N.Y. June 20, 2025), a Rule 11 request failed for procedural reasons and a fee request also failed. For the law on the safe harbor, see Rule 11 and Inherent-Power Sanctions: The Safe Harbor, Fee Awards, and Attorney Conduct and Rule 11 Sanctions and Safe Harbor Checklist: A Practical Checklist.

Step 8: Oppose the TRO or preliminary injunction

Who: counsel; engineering lead and one business witness as declarants; expert if time allows. Timing: days. Prepare before you are served.

Prepare a "go bag"

Keep a folder ready from week two: a fact declaration in draft, the chronology, key public sources, the customer and employee impact of any possible order, the evidence of the plaintiff's delay, a proposed stipulation, and a bond calculation. Consider contacting the plaintiff's counsel to ask for notice of any TRO application, and write the request down.

Ex parte seizure

The DTSA allows civil seizure only in extraordinary circumstances, with a narrow order, a hearing, security, and a damages remedy for wrongful seizure. 18 U.S.C. § 1836(b)(2). If you are served with one, call counsel, do not obstruct, keep a detailed record of what is taken, and move promptly for the hearing the statute provides. These orders are uncommon, but the remedy is one more reason to show you are preserving evidence, because the applicant must show that you would otherwise destroy, move, or hide it.

The opposition's structure

The test is the familiar four-factor one of Winter v. Natural Resources Defense Council, Inc., 555 U.S. 7 (2008), and Rule 65 applies. See Preliminary Injunctions and Temporary Restraining Orders: Emergency Relief in Federal Court for the general law. For a trade secret defendant, the order of attack usually looks like this:

1. No identified secret. Insulet Corp. v. EOFlow, Co., 104 F.4th 873 (Fed. Cir. 2024), reversed an injunction that swept in "any and all Confidential Information," requiring likely success on at least one specifically defined secret. Mallet & Co. v. Lacayo, 16 F.4th 364 (3d Cir. 2021), vacated an injunction for failing to say what the secrets were, and tied the problem to Rule 65(d)'s specificity requirement. If the plaintiff's motion uses categories, say so on page one.

2. Limitations and delay. Insulet's first appeal also faulted the trial court for skipping limitations. Delay undercuts urgency generally, as the Second Circuit held in a trademark case, Citibank, N.A. v. Citytrust, 756 F.2d 273 (2d Cir. 1985). Your chronology of launches, trade shows, and public statements goes here.

3. No irreparable harm. There is no presumption under the DTSA, which only permits injunctions. First Western Capital Management Co. v. Malamed, 874 F.3d 1136 (10th Cir. 2017), so held in reversing an injunction. See also eBay Inc. v. MercExchange, L.L.C., 547 U.S. 388 (2006). Faiveley Transport Malmo AB v. Wabtec Corp., 559 F.3d 110 (2d Cir. 2009), explains that a defendant using a secret in its own business, without spreading it, generally causes harm that money can repair. Say, in a sworn declaration if true, that you have no plan to publish or disclose. Beware of contract clauses in which an employee or vendor stipulated to irreparable harm. Address them directly.

4. Merits. Lead with whatever you have strongest: published patents, independent development dates. Keep it tight, and do not reveal your confidential technical detail on the public docket. Request leave to file under seal, and remember that 18 U.S.C. § 1835 directs courts to protect claimed secrets during proceedings. See Negotiating a Protective Order and Filing Under Seal: A Practical Guide.

5. Employment limits. An injunction may not "prevent a person from entering into an employment relationship," and any conditions must be based on evidence of threatened misappropriation "and not merely on the information the person knows." 18 U.S.C. § 1836(b)(3)(A)(i). The same subparagraph bars relief that conflicts with applicable state law prohibiting restraints on lawful trade. In California, cite Whyte v. Schlage Lock Co., 101 Cal. App. 4th 1443 (2002). In a jurisdiction following PepsiCo, Inc. v. Redmond, 54 F.3d 1262 (7th Cir. 1995), expect more argument about threatened misuse, and see Hiring From a Competitor: Inevitable Disclosure, Employee Raiding, and the New Employer's Trade Secret Exposure.

6. Balance of hardships, public interest, and bond. Give numbers. What would a shipment halt cost? How many employees and customers? Rule 65(c) requires security, and it has teeth: ABBA Rubber Co. v. Seaquist, 235 Cal. App. 3d 1 (1991), reversed a preliminary injunction under California's rule for vagueness and an inadequate undertaking. A company wrongfully enjoined generally cannot recover beyond the bond, so the bond amount matters more than people assume.

Offer something narrow

Judges like reasonable alternatives. A stipulation not to use or disclose specifically identified documents, a forensic quarantine, and a preservation order often give the plaintiff what it legitimately needs and defuse the emergency. Make sure the stipulation does not concede that anything is a secret, and that it does not restrict your existing product. Trade Secret Remedies Toolkit: Damages Models, Head Start Analyses, and Injunction Briefing has injunction briefing materials.

Step 9: Discovery, including the trap for your own engineers

Who: counsel, e-discovery vendor, expert. Timing: per the scheduling order. Most issues are discussed in Managing Discovery in a Trade Secret Case: A Practical Guide, and only defense-specific points follow.

The attorneys' eyes only problem

Here is a dilemma many clients do not see coming. When the plaintiff finally identifies its secrets, it will designate that list as attorneys' eyes only. Your engineers will not be allowed to see it. Two things follow.

First, you will need outside technical help, because your lawyers cannot evaluate a chemical or software identification alone. Retain an independent expert early, and clear that person under the protective order.

Second, keeping your engineers away from the plaintiff's list is in your interest. If they see it, the plaintiff will argue that any later development is contaminated, and your independent development story gets harder with each new release. Ask for a provision allowing a small number of designated in-house people to see a redacted or high-level description, if that is truly necessary to prepare, and wall them off from development. A written clean team protocol is in the Trade Secret Defense Toolkit: Independent Development Records, Public Domain Charts, and Bad Faith Fee Motions. For protective order negotiation generally, see Obtaining and Defending a Protective Order: A Practical Guide.

What to demand from the plaintiff

• First-awareness documents: competitive intelligence, trade show reports, sales team notes, internal escalations to legal, forensic engagements. Insulet turned on these.
• Every disclosure of the claimed secret: NDAs, marking, confirmation letters, vendor access, publications, regulatory submissions. Convolve, Inc. v. Compaq Computer Corp., 527 F. App'x 910 (Fed. Cir. 2013), shows why.
• Development cost and value evidence, which is relevant to both the merits and damages. Direct Technologies, LLC v. Electronic Arts, Inc., 836 F.3d 1059 (9th Cir. 2016), was decided on the absence of value in secrecy.
• Security policies and audits, and instances when they were ignored.
• Prior litigation by the plaintiff about the same technology, including what it filed publicly.
• Third-party subpoenas under Rule 45 to former vendors, contract manufacturers, and competitors.

What your side will have to produce

Expect source code requests, forensic imaging of devices, and depositions of every engineer. Limit source code production to a review environment, tie scope to the identified secret, and ask for a neutral forensic protocol over personal accounts. Prepare your engineers carefully and properly using Preparing a Witness for Deposition: What Is Proper, What Is Coaching, and What the Other Side Can Discover. They will be asked about things they vaguely recall from their old job, and "I do not recall where I learned that" is a hard answer for a jury to accept. If the honest answer is "from the textbook on my shelf," help them find the textbook before the deposition.

Step 10: Summary judgment

Who: counsel; experts. Timing: per the schedule, usually after expert discovery.

Summary judgment under Rule 56 is where most of the defense's preparation pays off. Courts vary on whether a question is one of law, but the common view is that secrecy and reasonable measures are usually questions of fact. Pick arguments that fit that reality:

1. Identification failure. NEXT Payment Solutions, Inc. v. CLEAResult Consulting, Inc., No. 24-1377 (7th Cir. Jan. 13, 2026); IDX Systems Corp. v. Epic Systems Corp., 285 F.3d 581 (7th Cir. 2002); AMP Inc. v. Fleischhacker, 823 F.2d 1199 (7th Cir. 1987). Show the court the plaintiff's own list.
2. Public disclosure. Use the chart. Tie each element to a pin cite in the public source. On-Line Technologies, Inc. v. Bodenseewerk Perkin-Elmer GmbH, 386 F.3d 1133 (Fed. Cir. 2004), requires a plaintiff who claims more than the patent disclosed to come forward with evidence.
3. No evidence of use. The plaintiff must show similarity in the secret features. Stratienko accepts declarations from your own employees, despite their interest.
4. Time bar. Insulet Corp. v. EOFlow, Co., No. 25-1807 (Fed. Cir. May 28, 2026); CMI Roadbuilding, Inc. v. Iowa Parts, Inc., 920 F.3d 560 (8th Cir. 2019). Insulet petitioned for rehearing en banc in July 2026, so check the docket.
5. Displacement and contract terms. Often purely legal.

The plaintiff may ask for delay under Rule 56(d). In InteliClear, LLC v. ETC Global Holdings, Inc., 978 F.3d 653 (9th Cir. 2020), the Ninth Circuit reversed summary judgment granted before discovery, so an early motion needs a realistic record. Expert testimony will need to clear Fed. R. Evid. 702, and the plaintiff's expert may be vulnerable if the opinion on similarity skips the public domain. General guidance is in Summary Judgment Under Rule 56: Winning and Surviving Before Trial and Summary Judgment Motion Checklist: A Practical Checklist.

Step 11: Trial and verdict

Who: trial team. Timing: pretrial order through post-trial motions.

Theme. Trade secret juries decide stories. Yours should be concrete: here is the whiteboard photo, here are the nineteen failed prototypes, here is the invoice for the resin, here is the handbook on the shelf. Avoid sneering at the plaintiff's investment. Jurors respect it. Say instead that the law protects the honest race.

Burdens and instructions. Request instructions that the plaintiff retains the burden on use, as in Sargent Fletcher, and resist burden-shifting language. In California, use CACI No. 4420 for readily ascertainable, and be ready for the defense to fall on you. Ask for instructions on general skill and knowledge, on the lawfulness of reverse engineering and independent derivation under 18 U.S.C. § 1839(6)(B), and on what information was disclosed before the first alleged use.

Verdict form. Require findings secret by secret: existence, misappropriation, willfulness, and damages. A general verdict makes post-trial challenges harder, and damages may be impossible to separate if one secret falls. On limitations, ask for specific dates. The Federal Circuit's Insulet decision treated related secrets as one claim despite an instruction to consider them separately, so preserve your objection to the instruction as well.

Rule 50(a). Move on every element, for every secret, and on limitations. Harbor Business Compliance Corp. v. Firstbase.io, Inc., No. 25-1278 (3d Cir. Aug. 27, 2025), found a defendant had forfeited its sufficiency challenge to protectability because its pre-verdict motion addressed only misappropriation, in a case with an $11 million trade secret award. Then renew under Rule 50(b). Insulet shows that judgment as a matter of law can undo a verdict after a five-week trial.

Sealing at trial. Ask for a plan ahead of time. Confidentiality protections granted in discovery do not automatically continue when documents go into evidence in open court. Littlejohn v. BIC Corp., 851 F.2d 673 (3d Cir. 1988). Your own technical information is at stake.

Damages. Have a damages defense ready, even if your position is that nothing was taken. Proving or Defending Against Trade Secret Damages: A Practical Guide and the Trade Secret Remedies Toolkit: Damages Models, Head Start Analyses, and Injunction Briefing cover the models.

Step 12: Fee motions

Who: counsel. Timing: generally within 14 days after judgment under Rule 54(d)(2), unless a statute or court order says otherwise, with state analogues differing. Calendar this before judgment enters. See Missed Federal Deadlines: Rule 6, Excusable Neglect, and the Deadlines a Court Cannot Excuse for what happens if you do not.

Are you the prevailing party?

A defendant can prevail without a merits win, CRST Van Expedited, Inc. v. EEOC, 578 U.S. 419 (2016), but the case must be resolved in its favor. A dismissal without prejudice does not count in the Fifth Circuit. Dunster Live, L.L.C. v. LoneStar Logos Management Co., 908 F.3d 948 (5th Cir. 2018). When a plaintiff moves to dismiss under Rule 41(a)(2), ask the court to make dismissal with prejudice or condition it on fees. If the plaintiff files a notice of dismissal before you have answered or moved for summary judgment, you may have no such chance, which is another reason to answer early if you have a strong fee case.

Proving bad faith

Under 18 U.S.C. § 1836(b)(3)(D), bad faith "may be established by circumstantial evidence." The formulation differs by circuit, as Recoop catalogs, so draft to your court's version. The usual test is objective speciousness plus subjective bad faith, as in Gemini Aluminum Corp. v. California Custom Shapes, Inc., 95 Cal. App. 4th 1249 (2002), and FLIR Systems, Inc. v. Parrish, 174 Cal. App. 4th 1270 (2009).

Know the counterexamples, because the plaintiff will. An adverse merits ruling does not establish bad faith. Wilbur-Ellis Co. v. Gompert, No. 8:21-cv-00340 (D. Neb. July 22, 2025). A real suspicion of downloads can defeat the motion despite a failed identification. Double Eagle Alloys, Inc. v. Hooper, No. 4:19-cv-00243 (N.D. Okla. Nov. 19, 2024). A claim can be specious, and fees still denied, without subjective bad faith. Dental Health Services Inc. v. Miller, No. 2:23-cv-00383 (W.D. Wash. Oct. 22, 2024). A settlement demand before suit is not itself evidence of bad faith. Gorovenko v. Activate Clean Energy LLC, No. 24-5840 (9th Cir. Oct. 14, 2025).

Build it from day one

The fee motion is built by your earlier letters. Each should state the defect, attach the evidence, and ask the plaintiff to withdraw. Keep time records good enough to apportion between trade secret counts and others, and expect a reasonableness fight. In Applied Predictive, the defense had spent 10,260 hours over six years and was awarded $2,807,755.79, an award that was on appeal as of late 2026.

Costs and trade-offs

Numbers depend on the court, the technology, and how much the plaintiff wants to spend, so treat any quote skeptically and ask for a phased budget. A few honest observations:

• The expensive items are forensics, source code review, experts, and emergency motions. A case with two experts and a preliminary injunction hearing is not cheap, even for a small plaintiff's claim.
• Early investment is the bargain. A focused month of privileged fact finding often determines whether to fight or settle, and the same work becomes your summary judgment record.
• The fee statute is not a budget. Plan on not recovering. Treat any fee award as upside.
• A business deal may beat winning. Licensing, a design-around with a release, or a cross-supply arrangement can be worth more than a defense verdict three years away, especially for a young company whose investors do not like open litigation.
• Settlement terms need care. Expect requests for certifications, forensic audits, and deletion after preservation is lifted. Try for no admission, mutual releases covering future versions, narrowly described restricted information, and a clear end date on any monitoring.

Common mistakes

1. Comparing products casually after the letter arrives. Do this only under counsel's direction, by people who are not accused, and in a way that does not expose them to the plaintiff's material.
2. Letting the accused engineer collect his own documents. Even with good intentions, this destroys metadata and credibility.
3. Deleting "their" files. The instinct is honorable, and the result is a spoliation motion.
4. Saying "we built it independently" before you know. One bad folder can turn a confident letter into impeachment.
5. Relying on "it could have been reverse engineered." If you did not do it, this is an argument about whether a secret exists, not an account of what you did, and it needs real data.
6. Showing that every component is public and stopping there. The plaintiff will claim the combination, under authorities like Minnesota Mining & Manufacturing Co. v. Pribyl, 259 F.3d 587 (7th Cir. 2001).
7. Rewriting git history to make the repository tidy. Even an innocent cleanup looks terrible after a hold should have been in place.
8. Treating the reasonable measures argument as the main event. It is usually a jury issue, and Rockwell Graphic Systems, Inc. v. DEV Industries, Inc., 925 F.2d 174 (7th Cir. 1991), is why.
9. Forgetting about limitations until the eve of summary judgment. Plaintiffs' early awareness is found in discovery. If you do not ask, you do not find it.
10. Letting your engineers read the plaintiff's identification. See Step 9.
11. Giving a tolling agreement away for free. After Insulet, time can be the case. Ask for something in return.
12. Ignoring the contract. The tort may be weak and the NDA or employment covenant strong. Displacement rarely reaches contract claims. Angelica Textile Services, Inc. v. Park, 220 Cal. App. 4th 495 (2013).
13. Using a fee threat as a bluff. Vague threats carry no weight. A specific letter identifying the defect, with evidence, is what later supports a motion.
14. Skipping an element in the Rule 50(a) motion. See Harbor.

Two worked examples

The account manager and the customer list

Suppose Dana Oyelaran spends nine years selling filters for Pellworth HVAC Supply, then joins a small competitor, Ardley Air. Within three months, a dozen Pellworth customers have moved. Pellworth's lawyer writes to both Dana and Ardley, claiming its customer list, pricing, and renewal dates as secrets.

First week. Ardley's counsel recommends separate counsel for Dana, which Ardley agrees to pay for. A hold goes out, and Dana's personal phone and email are imaged by a vendor. The image shows she forwarded a spreadsheet to herself on her last day. She says she wanted it to prove her commissions.

Sorting the claim. Customer identities in this trade are visible: contractors advertise, and building permits are public. Under the DTSA and most state statutes, the plaintiff bears the problem of "readily ascertainable." If this were California, ABBA Rubber would shift the analysis. Dana would have to show that her knowledge came from an honest process and not from Pellworth's records, and the spreadsheet makes that difficult. Memory will not save her: "The form of information, whether written or memorized, is immaterial." Ed Nowogroski Insurance, Inc. v. Rucker, 971 P.2d 936 (Wash. 1999). Pricing and renewal dates are more plausibly secret than names.

The response. Dana's lawyer quarantines the spreadsheet with a vendor and tells Pellworth that it has been segregated, that it was not shared with Ardley, and that she will discuss return under a protocol. That is true only if the image and interviews support it, so they check first. Ardley issues Dana a written instruction not to use or disclose Pellworth information and documents how the twelve customers were approached. Dana's general relationships and industry knowledge fall on the employee's side of the line in AMP. If Dana handed the spreadsheet to counsel solely to pursue a wage claim, 18 U.S.C. § 1833(b) may be relevant, but a mix of purposes would be a problem under the statute's "solely" language, as the decision in Unum Group v. Loftus, 220 F. Supp. 3d 143 (D. Mass. 2016), illustrates at the pleading stage. Ask, too, whether Pellworth's employment agreement contained the required notice.

Likely resolution. Pellworth has an emotional case and a real spreadsheet. Ardley has a good story about most customers. Injunction odds drop if the spreadsheet is locked away and Ardley stipulates narrowly. A business resolution with a short non-solicitation of specified accounts and no admission may be better than two years of litigation over filters.

The molder and the NDA

Suppose Sorrel Point Molding bids on a medical housing for a device maker, Halden Devices. It signs Halden's NDA and receives drawings. Halden awards the job elsewhere. A year later Sorrel launches its own line of housings, and Halden sends a demand: Sorrel has used the snap-fit geometry and gating design it saw in the bid package.

Week one. Counsel pulls the NDA. It covers written information "marked confidential" and requires oral disclosures to be confirmed within thirty days. The drawings carry a legend. Two site-visit conversations about gate placement do not have any follow-up writing. Under Convolve, those conversations may fall outside the NDA, although a court will read the actual words and any tort duty separately. The NDA also excludes independently developed and publicly available information. Sorrel's bid team and its design team overlapped by one person, which is the access story Halden will use.

Building the record. Sorrel's mold-flow simulation files carry server timestamps, and its tool shop's invoices date the gating trials. A 2014 handbook on snap-fit design contains the same geometry family. Halden's own patent, published eighteen months after filing, shows the snap-fit but says nothing about gate location. The chart therefore splits. Snap-fit is public under On-Line Technologies. Gating may be secret, but the gating is also driven by material flow, and Sorrel's simulations show the path to it. Sorrel also checks when Halden's sales team first handled a Sorrel sample, because the launch was public.

The response and the plan. Counsel writes a measured denial, asks for identification, and proposes outside-counsel review. Halden sues, and asks for an injunction. Sorrel opposes by pointing to its public launch, nine months before the motion, and to a declaration on the cost of a shutdown. It offers a stipulation that the one overlapping employee will work on nothing related to Halden's product, without conceding anything. The court denies the injunction. Discovery shows that Halden gave the same drawings to four vendors, three of whom signed nothing. By summary judgment, the case has narrowed to gating, and it settles with no payment and a mutual release. Had Halden kept going in the face of those facts, Sorrel's letters would have supported a fee request.

If you are on the other side

Plaintiffs should read this guide as a list of what is coming. Before you send a demand, identify the secret specifically enough to survive NEXT Payment. Run the public record yourself, including your own patents. Find out when your company first noticed the competitor, and calculate three years from that date, because Insulet will be cited against you. Write a letter that a judge will think was reasonable, since a demand letter that overclaims can become Exhibit A to a fee motion (see Writing a Demand Letter: The Basics). If discovery proves you wrong, withdraw the affected claims promptly. Hark'n and Applied Predictive both contrast persistence with the plaintiff in an earlier Utah case that withdrew claims and avoided fees.

Practical notes for the owner of a small company

You may be reading this without a legal department. Three things are within your control today. Keep your records, even the embarrassing ones. Ask new hires, in writing, to bring nothing from old jobs, and keep the signed form. Write down the reasons for technical decisions as you make them, and keep the failed experiments. If a letter arrives, the sequence above is what to ask your lawyer about, and any lawyer who suggests quickly deleting anything is one you should question. UpLaw (uplaw.us) has the cases cited here if you want to read them yourself.

This guide is general information, and your own dispute may turn on a contract clause or a state rule not covered here, so get advice on your specific facts. If you are facing this now, MC Law would be glad to talk through the first steps with you.

Related Documents

Related Articles

• Defending a Trade Secret Claim: Reverse Engineering, Independent Development, Public Disclosure, and Readily Ascertainable Information: the doctrine behind each step, with the leading cases read closely.
• Identifying Trade Secrets in Litigation: Reasonable Particularity, Sequencing Discovery, and Protecting the Secret While You Sue: the identification fight from both sides.
• Litigation Holds, Spoliation, and Rule 37(e): Preserving Electronic Evidence Before It Costs You the Case: the law of the preservation duty.
• Conducting an Internal Investigation: Scope, Privilege, and Reporting: scope, privilege, and reporting in depth.
• Preliminary Injunctions and Temporary Restraining Orders: Emergency Relief in Federal Court: emergency relief in federal court generally.
• Hiring From a Competitor: Inevitable Disclosure, Employee Raiding, and the New Employer's Trade Secret Exposure: new employer exposure and inevitable disclosure.
• Rule 502 and Inadvertent Production: Waiver, Clawback Agreements, and Why Every Case Needs a 502(d) Order: protecting privilege in production.
• Preparing a Witness for Deposition: What Is Proper, What Is Coaching, and What the Other Side Can Discover: proper preparation of accused engineers.
• Data Breach Class Actions: Article III Standing, Negligence Claims, and Forensic Report Privilege: forensic report privilege in a neighboring setting.

Related Guides

• Trade Secret Misappropriation Litigation Under the Defend Trade Secrets Act: A Practical Guide: the broader DTSA litigation road map.
• Managing Discovery in a Trade Secret Case: A Practical Guide: forensic protocols and source code discovery.
• Proving or Defending Against Trade Secret Damages: A Practical Guide: preparing the damages defense.
• Onboarding a Competitor's Employee Without Importing Its Secrets: A Practical Guide: preventive steps for new hires.
• Filing or Defending a Declaratory Judgment Action: A Practical Guide: the declaratory route.
• Responding to a Cease and Desist Letter: A Practical Guide: general letter strategy.

Related Checklists

• Trade Secret Defense Checklist: A Practical Checklist: phase-by-phase tasks mirroring this guide.
• Litigation Hold and Evidence Preservation Checklist: A Practical Checklist: hold mechanics.
• Rule 11 Sanctions and Safe Harbor Checklist: A Practical Checklist: the safe harbor process.

Related Toolkits

• Trade Secret Defense Toolkit: Independent Development Records, Public Domain Charts, and Bad Faith Fee Motions: the letters, records, charts, and motion outlines this guide refers to.
• Trade Secret Litigation Toolkit: Identification Statements, Two-Tier Protective Orders, and Forensic Protocols: identification and protective order forms.
• Trade Secret Remedies Toolkit: Damages Models, Head Start Analyses, and Injunction Briefing: damages models and injunction briefing.
• Business Records Toolkit: Rule 902 Certifications, Foundation Scripts, and Hearsay Response Charts: certifications for development records.