Hiring From a Competitor: Inevitable Disclosure, Employee Raiding, and the New Employer's Trade Secret Exposure

On a call with a headhunter working for XP Power, a senior engineer still on Comet Technologies' payroll offered a "crew" that could supply a "turnkey" product design. The headhunter recorded the call and sent it straight to XP's chief executive and other senior executives with a note: "please keep this recording strictly confidential. You will see why." The Ninth Circuit later called that recording a "proverbial smoking gun." The engineer and two colleagues arrived at XP with thousands of confidential files, and, in the court's telling, delivered complete designs and a development plan in just nine days. A jury returned a $40 million verdict, the district court added more than $17 million in fees, and on July 14, 2026 the Ninth Circuit threw all of it out on an instruction error and ordered a new trial. See Comet Technologies USA, Inc. v. XP Power, LLC, No. 23-15709 (9th Cir. July 14, 2026).

That one case holds most of this subject. Recruiting the engineers was never the problem. The law actively protects it. The exposure came from what the recruits offered, what executives heard, what happened in those nine days, and years of litigation that followed.

MC Law's existing materials mostly look at this from the side of the company losing someone, as in the Employee Departure Trade Secret Protection Checklist: A Practical Checklist. This article takes the other chair: the company about to hire a star from a rival, who turns up on Monday with a personal laptop, a Google Drive, and a head full of knowledge. The practical sequence is in Onboarding a Competitor's Employee Without Importing Its Secrets: A Practical Guide, the task list in Competitor Hire Trade Secret Checklist: A Practical Checklist, and the working papers in Lateral Hire Toolkit: Candidate Certifications, Onboarding Instructions, and Cease-and-Desist Responses.

The short answer

• Hiring a competitor's at-will employee is lawful. In California's words, "one commits no actionable wrong by merely soliciting or hiring the at-will employee of another." Reeves v. Hanlon, 33 Cal. 4th 1140 (2004). Most states agree, with variations.
• A new employer's trade secret liability runs on knowledge, and "reason to know" counts. Under 18 U.S.C. § 1839(5), a company that acquires or uses a secret it had reason to know came through a breach is a misappropriator. A company that never asks where the fast new process came from can be charged with what a question would have revealed.
• Many courts also impose vicarious liability. The majority view lets a plaintiff reach the employer through respondeat superior, the doctrine holding employers liable for employees' torts within the scope of employment, even if management knew nothing. Indiana is the notable exception.
• Inevitable disclosure is alive but shrinking. It survives in some form in states such as Illinois and Pennsylvania, is disfavored in New York, and is rejected in California, Maryland, and elsewhere. The federal statute forbids an injunction that stops someone from taking a job, and requires that any conditions rest on "evidence of threatened misappropriation and not merely on the information the person knows." 18 U.S.C. § 1836(b)(3)(A)(i).
• Candor drives outcomes more than doctrine. In PepsiCo, Whyte, and Bimbo Bakeries, courts cared a great deal about whether the employee was straight about the move and what was copied on the way out.
• Certifications help but do not immunize. Quaker, Hostess, and Language Services Associates all had signed acknowledgments. All three still faced serious claims.
• Noncompetes are a state law problem. The FTC's rule was set aside in 2024, the agency abandoned its appeals in September 2025, and it removed the rule from the Code of Federal Regulations effective February 12, 2026. Meanwhile, states are moving in opposite directions: California and Washington toward prohibition, Florida toward stronger enforcement.
• Raiding liability needs something beyond the raid. An independently wrongful act, a breach of fiduciary duty, a term contract, or stolen information usually supplies it.
• Destroying evidence is the fastest way to lose. A company that "cleans up" after discovering contamination may convert a defensible case into terminating sanctions, as WeRide Corp. v. Huang, No. 5:18-cv-07233 (N.D. Cal. Apr. 24, 2020) shows.
• Plaintiffs have clocks too. After Insulet Corp. v. EOFlow, Co., No. 25-1807 (Fed. Cir. May 28, 2026), a former employer who knows about access through departed staff and sees a similar product may have three years from that knowledge and no more.

Why the law protects the hire itself

Trade secret law serves two masters, and the opinions say so. The Supreme Court grounded state trade secret protection in "the maintenance of standards of commercial ethics and the encouragement of invention" in Kewanee Oil Co. v. Bicron Corp., 416 U.S. 470 (1974). But the same body of law has always refused to treat an employee's accumulated ability as the employer's property. In PepsiCo, Inc. v. Redmond, 54 F.3d 1262 (7th Cir. 1995), the very case that launched modern inevitable disclosure, the Seventh Circuit wrote that "trade secret law does not provide a reserve clause for solicitous employers," a reference to the rule that once bound baseball players to their teams for life.

There are three reasons the balance sits where it does.

First, labor markets depend on it. A worker who cannot use what she has learned cannot sell her labor at a fair price, and a company that cannot hire experienced people cannot enter a market. The Ohio court in the 1963 space suit case, B.F. Goodrich Co. v. Wohlgemuth, 117 Ohio App. 493 (1963), put it directly while enjoining disclosure: the manager of Goodrich's pressure suit department "had the right to take employment in a competitive business, and to use his knowledge (other than trade secrets) and experience, for the benefit of his new employer."

Second, there is an economic argument that gained force with time. Ronald Gilson's well-known article, The Legal Infrastructure of High Technology Industrial Districts: Silicon Valley, Route 128, and Covenants Not to Compete, 74 N.Y.U. L. Rev. 575 (1999), argued that California's refusal to enforce noncompetes helped explain why knowledge spilled so productively across Silicon Valley firms. Whatever one makes of the causal story, it now colors how judges and legislators talk about this area.

Third, the secret and the skill are hard to separate, so overbroad remedies would sweep up legitimate competition. The Third Circuit acknowledged that the line "may often be difficult to draw," adding that the plaintiff "has to provide something better than sweeping generalities." Mallet & Co. v. Lacayo, 16 F.4th 364 (3d Cir. 2021). The Restatement (Third) of Unfair Competition addresses the employee problem in section 42, and the Restatement of Employment Law treats it in Chapter 8. Both draw the same basic distinction between general skill and particular confidential information.

So the starting point is permissive. As the Western District of Washington put it in dismissing a claim against the aircraft company that recruited a rival's employees, "merely recruiting another company's employees does not meet the knowledge requirement for trade secret misappropriation." Bombardier Inc. v. Mitsubishi Aircraft Corp., 383 F. Supp. 3d 1169 (W.D. Wash. 2019). The District of Arizona quoted that line in February 2026, declining "to make an inference that Apex will inevitably rely on purported trade secrets purely on account of employing Plaintiffs' former staff." Bureau Veritas Technical Assessments LLC v. Brosa, No. 2:25-cv-02339 (D. Ariz. Feb. 18, 2026).

For the wider doctrine of what counts as a secret, see Protection of Trade Secrets and Trade Secret Misappropriation Litigation Under the Defend Trade Secrets Act: A Practical Guide.

Six ways a hiring employer gets sued

The last row deserves one more sentence. After Van Buren v. United States, 593 U.S. 374 (2021), an employee who was authorized to reach a file and misused it is usually outside the Computer Fraud and Abuse Act, 18 U.S.C. § 1030, so these claims now mostly appear where someone logged in after access ended. The sibling series on that statute is The Computer Fraud and Abuse Act After Van Buren: Gates, Insiders, Scrapers, and the Loss Requirement.

How the misappropriation statutes reach the new employer

The text

The federal definition follows the Uniform Trade Secrets Act closely. 18 U.S.C. § 1839(5)(A) covers "acquisition of a trade secret of another by a person who knows or has reason to know that the trade secret was acquired by improper means." Section 1839(5)(B) covers disclosure or use without consent by someone who, at the time, "knew or had reason to know" the knowledge was "derived from or through a person who had used improper means" or "who owed a duty" to the owner. "Improper means" includes "breach or inducement of a breach of a duty to maintain secrecy," and excludes reverse engineering and independent derivation under section 1839(6).

Read that from the hiring company's side. Three points follow.

Acquisition alone can be enough. A company that knowingly takes in stolen files need not use them. The Third Circuit has confirmed that improper acquisition, disclosure, or use may each independently establish misappropriation, in Oakwood Laboratories LLC v. Thanoo, 999 F.3d 892 (3d Cir. 2021).

"Use" is broad. Oakwood quotes the formulation that use includes "relying on the trade secret to assist or accelerate research or development," and it holds that a plaintiff can suffer harm from losing the exclusivity of a secret before any competing product launches. A new hire's offhand "don't bother testing that formulation, it fails" can be use of negative know-how, meaning knowledge of what does not work.

The state of mind is measured at the time of use. That matters a great deal. A company innocent on Monday may be on notice by Friday. From the moment the company has reason to know, continuing to use the material is a new problem, even if the original intake was innocent. For that reason, what a company does after a cease-and-desist letter or an internal discovery often matters more than what it did before.

Constructive notice, or the question nobody asked

The classic case is 44 years old and could have been decided last week. In Rohm & Haas Co. v. Adco Chemical Co., 689 F.2d 424 (3d Cir. 1982), a small paint chemical company had been trying without success to copy two Rohm & Haas products. Its president heard of a former Rohm & Haas technician looking for work and hired him after one interview. During his first week, working alone, the technician replicated the product in the lab. The first entry in the notebook he kept for his new employer was the complete Rohm & Haas process. The Third Circuit, in a passage later quoted by the Second Circuit, wrote: "Defendants never asked where the 'Harvey process' had come from. Defendants therefore were charged 'with whatever knowledge such inquiry would have led to.'"

That is the constructive notice rule. The Restatement (First) of Torts section 757, comment l, framed it as whether a reasonable person "would be put on inquiry" and whether inquiry pursued with reasonable diligence would have disclosed the breach. See Computer Associates International, Inc. v. Altai, Inc., 982 F.2d 693 (2d Cir. 1992).

Modern courts apply the same reasoning to speed. In WeRide Corp. v. Kun Huang, 379 F. Supp. 3d 834 (N.D. Cal. 2019), an autonomous vehicle startup showed a video of a car performing five advanced functions ten weeks after its new vice president of technology left WeRide. The court accepted expert testimony that independent development in that time was not possible and held that the company's other engineers "should have realized" outside technology had arrived with him. "The implausibly fast development of technology can contribute to finding misappropriation," Judge Davila wrote.

The defense has authority of its own, though, and it should be used. In CAE Integrated, L.L.C. v. Moov Technologies, Inc., 44 F.4th 257 (5th Cir. 2022), the Fifth Circuit affirmed denial of an injunction against a used semiconductor equipment seller whose new head of sales had verified he held no prior employer data and who had waited out his noncompete. Moov's commercial success after he arrived did not support an inference that it was using CAE's secrets. In Free Country Ltd. v. Drennen, 235 F. Supp. 3d 559 (S.D.N.Y. 2016), Judge Rakoff refused a temporary restraining order even though the departing employee had moved a substantial quantity of files to his Dropbox shortly before resigning, because the record did not show improper use.

What knowledge does not reach

Two limits are worth knowing.

General warnings are not knowledge. In Bombardier, the plaintiff had complained to the recruiters, but its requests to stop recruiting identified no specific secret and merely recited a code of ethics. The court held that was not enough to show the recipient knew or had reason to know of actual misappropriation. A cease-and-desist letter that names files and devices is very different from one that reminds a company about confidentiality in general.

Running a product is not always using the secret inside. In Silvaco Data Systems v. Intel Corp., 184 Cal. App. 4th 210 (2010), Silvaco accused Intel of misappropriation because Intel kept running software from a vendor adjudged to have stolen Silvaco's source code, even after hearing the accusation. The court held that executing compiled, machine-readable code is not "use" of the underlying source code, because the user never has access to the source. The opinion, disapproved on an unrelated point in Kwikset Corp. v. Superior Court, 51 Cal. 4th 310 (2011), rests on how compilation works: source is what a human reads, and the compiled binary reveals what a program does, not how it was written. The holding offers comfort to a downstream customer. It offers none to a company whose engineers read the source.

Vicarious liability, where innocence stops helping

Suppose management knew nothing. Under a majority of decisions, that may not matter. Washington's Court of Appeals held that "one may violate the UTSA vicariously and be held responsible for such violation," and did so against a future employer in Thola v. Henschell, 140 Wash. App. 70 (2007). In Language Line Services, Inc. v. Language Services Associates, Inc., 944 F. Supp. 2d 775 (N.D. Cal. 2013), the employer argued that blame rested with two "rogue" salespeople and that it had made them sign acknowledgments that they held no prior employer secrets. The court answered that the majority view is that the uniform act does not preempt respondeat superior. An earlier federal decision reasoned that respondeat superior is not a competing cause of action at all, only a way of allocating liability. Newport News Industrial v. Dynamic Testing, Inc., 130 F. Supp. 2d 745 (E.D. Va. 2001).

Bombardier shows how the pieces fit under the DTSA. One defendant, the aircraft maker's American affiliate, had only recruited and was dismissed for lack of knowledge. Another, an engineering firm that actually employed the former Bombardier engineers, also lacked knowledge, and the court refused to impute its employees' knowledge to it. But the firm stayed in the case anyway, because the employees' conduct was plausibly within the scope of employment and meant to benefit the firm, "though the employer may forbid it."

Three cautions apply.

• Minnesota adds foreseeability. Hagen v. Burmeister & Associates, Inc., 633 N.W.2d 497 (Minn. 2001) assumes, as the intermediate appellate court had held in an earlier round, that an employer can be vicariously liable under the uniform act, then rejects liability because the plaintiff offered no evidence that trade secret misappropriation was a foreseeable hazard in the insurance business.
• Indiana rejects the theory. Infinity Products, Inc. v. Quandt, 810 N.E.2d 1028 (Ind. 2004) relied on Indiana's unusually broad displacement clause to hold that the employer could not be liable through respondeat superior, leaving only direct liability based on the company's own knowledge.
• Punishment may need more. In Language Line, the employer invoked the California rule that an employer owes exemplary damages only if it authorized or ratified the conduct or was itself guilty of oppression, fraud, or malice. The DTSA contains no express vicarious liability clause, and we found no circuit decision squarely resolving its application in this setting, though district courts commonly assume or hold that it applies.

Why a signed certification is only half a defense

A certification does real work: it shows the employer did not want the information, it supports a "no reason to know" argument, and it sets up discipline. But judges have seen it many times.

Quaker's new hire signed a confidentiality agreement with Quaker, and Quaker had a code of ethics prohibiting "illegal or improper acts to acquire a competitor's trade secrets." The injunction issued anyway. Hostess had its new executive sign a form saying it wanted no "information or 'know-how' related to the manufacturing of Thomas brand products." The Third Circuit affirmed an injunction anyway. The value of the paper depends on behavior around it: role design, supervision, IT controls, and a real answer when something surfaces.

Inevitable disclosure, from space suits to muffins

The idea and where it came from

The inevitable disclosure doctrine lets a trade secret owner obtain an injunction, sometimes against the new job, without proving that the employee has taken or used anything, on the theory that the new duties will inevitably cause reliance on old secrets. The roots are older than the name. Goodrich in 1963 found that disclosure was "seriously threatened" when the manager of Goodrich's space suit department left for its competitor International Latex, and it enjoined disclosure while leaving the man free to take the job.

PepsiCo, read closely

William Redmond ran PepsiCo's California business unit, with more than $500 million in annual revenue. He knew the strategic plan, the annual operating plan, the "pricing architecture," and market-specific "attack plans." Quaker, through a former PepsiCo colleague, courted him for a senior Gatorade job. He accepted on November 8, 1994, and the same day told PepsiCo's human resources head he had an offer he had not accepted. PepsiCo sued eight days later.

The Seventh Circuit, applying the Illinois Trade Secrets Act, held "a plaintiff may prove a claim of trade secret misappropriation by demonstrating that defendant's new employment will inevitably lead him to rely on the plaintiff's trade secrets." It affirmed an order barring Redmond from the job through May 1995 and permanently barring disclosure. People quote the playbook line ("a coach, one of whose players has left, playbook in hand, to join the opposing team before the big game"), but four other features of the opinion matter more.

1. Mere similarity was not enough. The court reaffirmed that a similar job at a competitor does not make disclosure inevitable, citing AMP Inc. v. Fleischhacker, 823 F.2d 1199 (7th Cir. 1987). What moved it was evidence of particularized, current plans whose value would still exist during the competitive year ahead.
2. The kind of secret mattered. Quaker would not copy PepsiCo's plans. It would anticipate them. Quaker's point that its distribution system differed therefore did not answer the claim.
3. The court coupled inevitability with distrust. The trial judge found "out and out lies" and held Redmond "could not be trusted." The Seventh Circuit said the facts "do not ineluctably dictate" that conclusion, then deferred. It also described those findings as the one place the trial judge had not simply adopted PepsiCo's proposed text, which increased its confidence in them.
4. The remedy was short. Roughly five months, which fit the shelf life of the plans. The court said a permanent bar would have made the defendants' argument stronger.

The Federal Judicial Center's Trade Secret Case Management Judicial Guide (Menell et al., 2023) draws a useful line here. In its "benign form," inevitable disclosure is an application of threatened misappropriation in which the employee's behavior justifies distrust. In its "more controversial form," it is decoupled from behavior and rests on the abstract risk of similar roles at close competitors. Much of the case law makes more sense when sorted that way.

Bimbo Bakeries: the probabilistic version

Bimbo Bakeries USA, Inc. v. Botticella, 613 F.3d 102 (3d Cir. 2010) is the best modern example of what persuades a court. Botticella was one of only seven people who knew everything needed to replicate Thomas' English Muffins. He accepted a Hostess job in October 2009, kept going to confidential meetings for three months without telling anyone, and never signed a post-employment noncompete. A forensic examiner found twelve files accessed within thirteen seconds on his last day, minutes after he told Bimbo where he was going, a pattern "inconsistent with an ordinary usage" of opening and reading files. Three external storage devices had been attached. Among the files were cost structures and plant closure plans, along with a slide deck titled "Safety Short-Wet Floors," which suggests copying by folder and not by selection.

The Third Circuit held that Pennsylvania law does not require that disclosure be inevitable or that the new job be "virtually impossible" to perform without disclosure. The question is "sufficient likelihood, or substantial threat." It rejected a proposed limit to technical secrets. It also relied heavily on conduct, while acknowledging in a footnote that "a human mind does not function like a computer from which, through an electronic process, materials may be deleted."

Practitioners sometimes overlook two facts. The injunction was short, lasting until a trial about two months out, and Botticella stayed on the Bimbo payroll through eleven weeks of accrued vacation. Both helped the balance of hardships, and the court still warned that even a temporary injunction against pursuing a livelihood "operates as a severe restriction."

Whyte and the states that say no

The strongest rejection came from California. J. Douglas Whyte, Schlage's vice president of sales, handled The Home Depot, which accounted for 38 percent of Schlage's sales. Kwikset's president said Whyte "was killing my team" and asked what it would take to get him. Whyte took the job on June 3, 2000, attended confidential Home Depot meetings for Schlage on June 5, and resigned on June 14. The Court of Appeal agreed the facts were "strikingly similar" to PepsiCo. Then it rejected the doctrine entirely in Whyte v. Schlage Lock Co., 101 Cal. App. 4th 1443 (2002): the doctrine "creates an after-the-fact covenant not to compete restricting employee mobility," its "chief ill" is that it binds an employee who never agreed to it, and "our rejection of the inevitable disclosure doctrine is complete."

California plaintiffs who ignore Whyte can pay for it. In FLIR Systems, Inc. v. Parrish, 174 Cal. App. 4th 1270 (2009), the court upheld $1,352,000 in fees and $289,216.78 in costs against a company whose claim rested on inevitable disclosure and lacked evidence of actual or threatened misuse. That said, California judges can do something short of an injunction. In Bayer Corp. v. Roche Molecular Systems, Inc., 72 F. Supp. 2d 1111 (N.D. Cal. 1999), Judge Alsup denied the injunction against a marketing manager who moved to a competitor but ordered periodic discovery to monitor whether confidential information was being misused, an underused middle ground.

Here is where things stand in a sample of jurisdictions.

Treat the table as a starting point. In most states the answer comes from a handful of intermediate or federal decisions, and it can move. A useful research starting place is the annotation Applicability of "Inevitable Disclosure" Doctrine Barring Employment of Competitor's Former Employee, 36 A.L.R.6th 537, and Brandy Treadway's survey, cited in Bimbo Bakeries, at 55 SMU L. Rev. 621 (2002).

EarthWeb remains the most quoted guide in New York: "in its purest form, the inevitable disclosure doctrine treads an exceedingly narrow path through judicially disfavored territory," and "[a]bsent evidence of actual misappropriation by an employee, the doctrine should be applied in only the rarest of cases." Its factors are whether the employers are direct competitors offering very similar products, whether the new position is nearly identical so that the employee could not be expected to perform without using the secrets, and whether the secrets are highly valuable to both. Note the bind that creates for a hiring company, because the closer it recruits to the same job, the better the claim.

What Congress did in 2016

The Defend Trade Secrets Act of 2016 allows an injunction against actual or threatened misappropriation, but an order may not:

"(I) prevent a person from entering into an employment relationship, and that conditions placed on such employment shall be based on evidence of threatened misappropriation and not merely on the information the person knows; or (II) otherwise conflict with an applicable State law prohibiting restraints on the practice of a lawful profession, trade, or business." 18 U.S.C. § 1836(b)(3)(A)(i)

Subsection (I) is awkwardly drafted, but its message is clear enough. A federal court may not rest a job restriction on what the person knows. Conditions need evidence. Subsection (II) brings California's and Minnesota's policies, and Washington's from mid-2027, into federal cases arising there.

How far does that go? Three positions have emerged.

• Foreclosed under the DTSA. An Indiana federal court in 2025 repeated the Illinois formulation that while inevitable disclosure "can be a viable theory under state law, it appears to be foreclosed for claims under the DTSA," and found no support under Indiana law either. WCG Clinical.
• Available at the pleading stage on thin facts, and dangerous later. One Illinois court let a complaint proceed on the theory and later, in Molon Motor & Coil Corp. v. Nidec Motor Corp., No. 1:16-cv-03545 (N.D. Ill. Nov. 30, 2020), granted fees in part after the claim collapsed: "It is one thing to rely on inevitable disclosure at the pleading stage," the court wrote. There, weak reliance on the doctrine combined with an unexplained three-year delay and no evidence of harm supported a bad faith finding.
• Threatened misappropriation on real evidence. Most careful courts read the statute to permit conditions (no work on a named product, a firewall, a reporting obligation) when conduct supplies evidence of a threat.

The state route is still open. The DTSA does not preempt state law, under 18 U.S.C. § 1838, and the Judicial Guide notes that a trade secret owner may still invoke the doctrine in states that recognize it. Expect a Pennsylvania or Illinois plaintiff to plead both.

Noncompetes and the state of play as of November 2026

A valid noncompete changes everything for the hiring company, because it supplies the contract that an interference claim needs and the restriction that a trade secret claim may not. So the first question about any lateral candidate is whether one binds her and whether it is enforceable where it counts.

The FTC rule is gone

The FTC published its Non-Compete Clause Rule on May 7, 2024. In Ryan LLC v. Federal Trade Commission, 746 F. Supp. 3d 369 (N.D. Tex. 2024), decided August 20, 2024, the court held the agency had exceeded its authority and that the rule was arbitrary and capricious, and set it aside with nationwide effect. On September 5, 2025, the Commission voted 3-1 to dismiss its appeals in the Fifth and Eleventh Circuits and accede to vacatur. It then removed 16 C.F.R. Part 910 from the Code of Federal Regulations, effective February 12, 2026. See 91 Fed. Reg. 6,507 (Feb. 12, 2026). Older commentary, including parts of MC Law's Non-Compete Agreements Under Siege: FTC Rulemaking and State Law Developments, should be read with that date in mind. The agency may still bring individual actions under section 5 of the FTC Act, but no federal rule voids these agreements.

The states are splitting further

California is the far pole. Business and Professions Code section 16600 voids noncompetes, and Edwards v. Arthur Andersen LLP, 44 Cal. 4th 937 (2008) rejected any "narrow restraint" exception, while expressly leaving open the so-called trade secret exception. AMN Healthcare, Inc. v. Aya Healthcare Services, Inc., 28 Cal. App. 5th 923 (2018) extended the reasoning to an employee nonsolicitation clause. Since January 1, 2024, Cal. Bus. & Prof. Code § 16600.5 has provided that a void covenant is "unenforceable regardless of where and when the contract was signed," that attempting to enforce one is a civil violation, and that an employee may sue for damages, injunction, and fees. That builds on Application Group, Inc. v. Hunter Group, Inc., 61 Cal. App. 4th 881 (1998), which applied California law to a Maryland resident recruited to work for a California employer. Whether section 16600.5 can bind a court in another state, or reach an out-of-state employer, is unresolved, and the Full Faith and Credit and choice-of-law fights have only begun.

Washington will join the ban group on June 30, 2027. Engrossed Substitute House Bill 1155, signed March 23, 2026 (Laws of 2026, ch. 149), voids noncompetes regardless of when they were signed, leaving nonsolicitation agreements within a limited definition. Minnesota has barred new noncompetes since July 1, 2023 (Minn. Stat. § 181.988), and North Dakota and Oklahoma have long-standing statutory limits.

Florida went the other way. The CHOICE Act (ch. 2025-213, Laws of Florida) allows covered noncompete and garden leave agreements of up to four years with higher-paid employees, and directs courts to preliminarily enjoin the employee and any new employer on certain showings, subject to narrow defenses. A company recruiting a Florida-based senior employee needs to read this statute first. Other states sit in between: Massachusetts (Mass. Gen. Laws ch. 149, § 24L), Illinois (820 ILCS 90), Colorado (Colo. Rev. Stat. § 8-2-113), and Virginia each impose wage thresholds, notice rules, or both, and Virginia and Tennessee both reportedly added new limits in 2026. New York still has no statute. A bill passed the state senate in June 2026 but is not law. Check any state's current law before relying on a summary, including this one.

What this means when your candidate has a covenant

Most states let a company defend by attacking the covenant. Texas held in Juliette Fowler Homes, Inc. v. Welch Associates, Inc., 793 S.W.2d 660 (Tex. 1990) that a covenant that is an unreasonable restraint will not support tortious interference. In New York, a court may enforce part of a covenant: Estee Lauder Companies Inc. v. Batra, 430 F. Supp. 2d 158 (S.D.N.Y. 2006) cut a twelve-month term to five, and applied New York law over a California-based executive's objection. International Business Machines Corp. v. Papermaster, 2008 WL 4974508 (S.D.N.Y. Nov. 21, 2008), involving a senior IBM chip executive bound for Apple, is often cited as an example of inevitable disclosure arguments being used in support of a written covenant. A year later the same court denied IBM an injunction against an executive going to Dell after a hearing that raised doubts about whether the covenant had even been properly executed. International Business Machines Corp. v. Johnson, 629 F. Supp. 2d 321 (S.D.N.Y. 2009).

Where the candidate has a real covenant in a state that enforces it, the options are a carve-out in the job, a wait, a negotiated waiver, or a declaratory judgment action under 28 U.S.C. § 2201, with the usual race to the courthouse risk. For covenants arising in other settings see Restrictive Covenants in Business Sales, Franchises, and Partnerships.

Employee raiding and tortious interference

A short history

The tort has an operatic origin, literally. In Lumley v. Gye, 118 Eng. Rep. 749 (Q.B. 1853), the operator of Covent Garden lured the soprano Johanna Wagner away from a rival theater while she was under contract, and the court held he could be liable for inducing the breach. American law took this up and then spent 170 years trying to fit it around competition.

The at-will line

The Restatement (Second) of Torts section 768 gives the core rule. A competitor may divert a prospective relationship, including an at-will arrangement, by fair means. It may not induce breach of a contract that is not terminable at will. That is the main reason a term employment contract or valid covenant changes the analysis.

Reeves is the leading modern statement. A California law firm sued two lawyers who left abruptly, printed confidential information on 2,200 clients from a password-protected database, persuaded employees to join them, and, in one defendant's case, intentionally erased extensive computer files. The Supreme Court held that inducing an at-will employee to leave can be actionable only if the defendant "engaged in an independently wrongful act," one "proscribed by some constitutional, statutory, regulatory, common law, or other determinable legal standard." Simply offering a better deal is not one. The court found the required wrongfulness in conduct such as misusing the confidential client data, and it affirmed liability. Ixchel Pharma, LLC v. Biogen, Inc., 9 Cal. 5th 1130 (2020) extended the independent wrongfulness requirement to all at-will contracts and applied a rule of reason to business-to-business restraints under section 16600.

New York is less forgiving about existing contracts. White Plains Coat & Apron Co. v. Cintas Corp., 8 N.Y.3d 422 (2007) held that "a generalized economic interest in soliciting business for profit" is no defense to interference with an existing contract. A competitor cannot use the mere fact of competition as its justification. For the general tort, see Tortious Interference and Unfair Competition Claims Between Businesses.

When a lift-out becomes a raid

A lift-out, in which a team moves together, is common in law, finance, sales, and engineering, and it is also where liability concentrates. The danger comes before resignation. An employee may prepare to compete, but she may not recruit colleagues for the rival or exploit her position while still on the payroll.

Bancroft-Whitney Co. v. Glen, 64 Cal. 2d 327 (1966) is the classic. The court held that mere preparation to compete is not a breach, but a course of conduct by a corporate president to deliver his colleagues to a competitor is, and the new employer that cooperated and received the benefits cannot disclaim the burden. New York's Duane Jones Co. v. Burke, 306 N.Y. 172 (1954) is the original mass exodus case, with senior advertising employees plotting a mass resignation and client transfer and paying for the resulting destruction of the business.

Notice the structure: the hiring company's liability is derivative. It rises with its participation. So a company should watch for the following:

• Who recruited whom, and when. After resignation is much safer than before.
• Who holds the list. A list of "the people we should bring" from a current employee, with salaries and performance ratings, can itself be confidential information.
• Internal messages. "We could gut their Chicago office" reads badly later. The opinion in PepsiCo made something of the fact that all three candidates interviewed for the role came from the same competitor, although the court acknowledged the benign explanation that the hiring manager knew they were good.

Do not solve this with a no-hire pact

When a dispute ends, parties often want a mutual promise not to hire one another's people. That instinct invites an antitrust problem under 15 U.S.C. § 1. Naked no-poach agreements have drawn DOJ prosecution, and the Seventh Circuit in Deslandes v. McDonald's USA, LLC, 81 F.4th 699 (7th Cir. 2023) refused to accept at the pleading stage that a franchise no-poach clause was ancillary and therefore safe. The DOJ and FTC issued Antitrust Guidelines for Business Activities Affecting Workers in January 2025, replacing the 2016 HR guidance, but their ongoing status under the present leadership should be checked. A narrowly drafted settlement term limited to named individuals and a short period, with antitrust counsel looking at it, is a safer shape.

What contamination actually looks like

Abstract rules hide how these cases actually develop. Here are the fact patterns the reported decisions keep repeating.

Altai: the template for doing it right after doing it wrong

Altai is usually taught as a software copyright case, but it is also the best account of remediation in the reports. Altai's Williams recruited an old friend from Computer Associates to help port a scheduling product. He did not know that his friend had brought CA's source code. About 30 percent of the resulting component was copied. The offices were adjacent, and they spoke many times a day, yet the trial court accepted that nobody but the programmer knew.

When the complaint arrived, Williams took action on advice of counsel without ever looking at the CA code himself. The programmer "was entirely excluded from the process, and his copy of the ADAPTER code was locked away." Eight programmers who had nothing to do with the old version rewrote the component from a functional description in about six months, and Altai shipped the new version as a free upgrade. The Second Circuit said Altai "acted responsibly" but "copyright infringement had occurred," affirmed that the rewrite did not infringe, and sent the trade secret claim back for consideration of constructive notice. Clean-room rewriting did not erase the past. It did end the future, and that was the whole point. The architecture of the fix (isolate the source, lock it up, wall off the tainted person, use fresh engineers, work from a functional spec) is still the model.

Motorola: what deliberate looks like

At the other end sits Motorola Solutions, Inc. v. Hytera Communications Corp., 108 F.4th 458 (7th Cir. 2024), which opens by calling the case "a large and blatant theft." Hytera's chief executive courted a Motorola engineer in Malaysia, with stock later worth about $2.5 million. Two more followed, one secretly on Hytera's payroll while still at Motorola, downloading documents "in response to specific requests from Hytera about unresolved issues" with its radios. More than 10,000 technical documents came out of Motorola's ClearCase and COMPASS databases. Some engineers swapped the Motorola logo for a Hytera logo. Proof included "minor coding errors" appearing in the same spots in both code bases.

Hytera did not even contest liability on appeal. The Seventh Circuit affirmed $135.8 million in DTSA compensatory damages and $271.6 million in exemplary damages (the statutory maximum of two times), and held the DTSA reaches foreign conduct where an act in furtherance occurred in the United States. For the damages framework, see Trade Secret Damages and Remedies: Unjust Enrichment, Reasonable Royalties, Injunctions, and Exemplary Awards.

Waymo: the diligence report nobody could keep private

Everyone remembers the self-driving dispute. Lawyers should remember Waymo LLC v. Uber Technologies, Inc., 870 F.3d 1350 (Fed. Cir. 2017). Before acquiring the startup founded by Waymo's former engineer, counsel for Uber and the startup jointly hired a forensic firm to investigate employees who had come from Waymo. Waymo sought the resulting report. The courts held there was no privilege for the employee's disclosures and that the common interest doctrine did not apply, because Uber and the engineer were adverse in that exercise. The work product protection Uber might have had was waived when it shared the report with its adversaries. The Federal Circuit stressed the fact-specific nature of the ruling. Still, the lesson is general: a pre-hire or pre-deal forensic review may be discoverable, and may be exactly what proves knowledge. If you investigate, structure it deliberately under Upjohn Co. v. United States, 449 U.S. 383 (1981), keep the report with counsel, and assume a judge might read it.

The allegations that started that case are summarized in Waymo LLC v. Uber Technologies, Inc., 256 F. Supp. 3d 1059 (N.D. Cal. 2017): 9.7 gigabytes of files downloaded in late 2015, followed by departure and a competing venture. Judge Alsup's preliminary injunction order is reported at 2017 WL 2123560 (N.D. Cal. May 11, 2017).

Kolon and WeRide: the cover-up costs more

Days after DuPont sued, employees of Kolon began deleting. A forensic review found 17,811 files and email items deleted after February 1, 2009, and the court found intentional, bad faith spoliation, imposing fees and an adverse inference instruction while declining to enter default judgment. The former DuPont employee at the center of the case, the court noted, eventually pleaded guilty to theft of trade secrets and obstruction. That the $919.9 million verdict was later vacated on evidentiary grounds in E.I. DuPont de Nemours & Co. v. Kolon Industries, Inc., 564 F. App'x 710 (4th Cir. 2014) does not change the point about the spoliation sanction, or about how much the fight cost.

WeRide is worse. After a cease-and-desist letter and a hold notice, the company did not turn off an email auto-delete function for months, destroying everything older than three months. It told the court about it the night before a hearing. It kept wiping departing employees' laptops under an exit policy. Weeks after the injunction, the man who later became its chief executive told the company it "better try" a chat app with ephemeral messages, which he liked because it was "more secure." The new vice president traded in his personal MacBook at an Apple store on the same day WeRide sent a cease-and-desist letter to that executive, and later altered source code on his company laptop in violation of the injunction. The court entered terminating sanctions under Fed. R. Civ. P. 37(b) and 37(e) and shifted fees. See Litigation Holds, Spoliation, and Rule 37(e): Preserving Electronic Evidence Before It Costs You the Case for the general law.

What actually happens on the machines

Lawyers who treat "he took files" as a single event miss most of the evidence. Each channel leaves different traces, on different computers, owned by different people.

USB and external drives

When a USB mass storage device is attached to a Windows computer, the operating system writes a record to the registry under the USBSTOR key, including a device identifier and usually a serial number, and logs first installation in a text file (setupapi.dev.log). That is how the WeRide court knew about "the '566 Device." Windows also creates shortcut (LNK) files and jump list entries when a user opens files, which can record the path and volume serial number of a removable drive. Shellbag entries record which folders a user viewed in Explorer.

NTFS timestamps tell a story too. A copied file usually keeps its last-modified time and receives a new created time on the destination volume, so a created date later than the modified date is the classic sign of a copy. Mass access creates patterns, which is why twelve files touched in thirteen seconds in Bimbo Bakeries meant something. Note how careful the expert there was: he could say the pattern was consistent with copying, but not determine conclusively that files had been copied. An honest forensic report often contains that kind of limit, and defense counsel should look for it. On macOS, comparable evidence lives in FSEvents records, unified logs, and Spotlight metadata, though with shorter retention.

Cloud sync, personal email, and source control

Consumer cloud services are the leading modern channel, and they create an evidence asymmetry. The former employer may see an upload in its own logs or from its endpoint agent, but it cannot see the destination account. The new employer cannot lawfully look in the employee's personal account without consent, because unauthorized access to stored communications is its own federal problem under 18 U.S.C. § 2701. Only the employee can give consent, or a court can order production.

Sync creates innocent accumulation, too. CAE Integrated is a useful study. The employee's Google Drive was synced to a folder on a personal MacBook he had also used for work. When the company moved those files during cleanup, they went to the Drive's trash, and weeks later he found and restored them. Files move in ways people do not intend, and a "delete" in a sync client may simply propagate or sit in trash for some period. Google Drive and OneDrive also keep local databases and logs recording what synced, which forensic examiners can read after the visible files are gone.

For software, source control adds its own trail. A Git clone copies the entire history of a repository to the local machine, so the "one file" an engineer wanted may arrive with everything else. Servers may log clone and fetch events. On the receiving side, commit timestamps, author fields, comments, internal project names, and copyright headers can reveal origin. Motorola's repeating coding errors show why plaintiffs' experts hunt for accidents and not design choices, because two engineers solving the same problem may produce similar logic, but they rarely produce the same mistake. Aleynikov shows the older version of this: a Goldman programmer encrypted and uploaded more than 500,000 lines of code to a server in Germany just before his going-away party, and joined a Chicago startup. The Second Circuit reversed his federal conviction on statutory grounds in United States v. Aleynikov, 676 F.3d 71 (2d Cir. 2012), Congress amended the statute within months, and today 18 U.S.C. § 1832 reaches trade secrets related to a product or service used in or intended for use in commerce. Organizations face fines of up to the greater of $5 million or three times the value of the secret. For more on distributed work and cloud exposure, see Trade Secrets in the Age of Remote Work and Cloud Computing.

What a hiring company's controls can and cannot do

Data loss prevention, or DLP, is software that watches for sensitive content moving across endpoints, email, and cloud. A former employer uses it to spot exits. A hiring company has a harder problem: it cannot fingerprint a competitor's documents it has never seen, and it should not try to acquire them for that purpose. It can do the following:

• Block the door. Disable USB mass storage on managed machines by default. Prohibit personal cloud sync clients. Do not let personal laptops join the corporate network or repositories.
• Look for strangers. Set keyword rules for the former employer's name, domain, internal project names supplied by the employee, and legends such as "Confidential" in uploads to company systems. Scan new commits for foreign copyright headers.
• Log what arrives. Keep first-90-day logs for new lateral hires with higher access to design repositories.
• Exchange hashes through counsel. A cryptographic hash is a fixed-length fingerprint of a file that reveals nothing about content. After a demand, the former employer's counsel can provide hash values, and a neutral vendor can search for matches without either company seeing the other's data. A hash match proves identity, though a mismatch proves little, because changing a single byte changes the hash.

Monitoring raises employee privacy and state notice issues, including electronic monitoring notice statutes in some states, so the policy should be written down in advance and applied evenly. Building a Trade Secret Protection Program from Scratch covers the general program, and generative AI adds a new channel, covered in Trade Secrets and Generative AI: Reasonable Measures, Prompt Leakage, and Vendor Terms.

How the former employer sees it: the other side of the table

A hiring company negotiates better when it understands the plaintiff's problems, and a plaintiff who understands them sues more carefully. In 2024, 2025, and 2026, the appellate courts tightened the screws on plaintiffs in several specific ways.

Identify the secret. In Mallet, Synova hired two Mallet employees, and they helped bring baking release agents to market quickly. The trial court enjoined the defendants from competing. The Third Circuit vacated because the order did not identify with specificity what was secret, which also failed Fed. R. Civ. P. 65(d). Insulet Corp. v. EOFlow, Co., 104 F.4th 873 (Fed. Cir. 2024) reversed an injunction for failing to do "a tailored analysis as to what specific information actually constituted a trade secret," failing to address limitations, and mishandling irreparable harm and the public interest. InteliClear, LLC v. ETC Global Holdings, Inc., 978 F.3d 653 (9th Cir. 2020) says the plaintiff must identify secrets with sufficient particularity. By contrast, Quintara Biosciences, Inc. v. Ruifeng Biztech, Inc., 149 F.4th 1081 (9th Cir. 2025) held that the DTSA itself has no California-style requirement to identify with reasonable particularity before discovery starts. Timing is more flexible under federal law than the substance. Identifying Trade Secrets in Litigation: Reasonable Particularity, Sequencing Discovery, and Protecting the Secret While You Sue covers this in depth.

Carry the burden. Comet arose from a procedural choice. Comet dismissed its California claims during trial, leaving only the DTSA. California treats "readily ascertainable" as a defense. The federal statute writes "not being readily ascertainable through proper means" into the definition of a trade secret in 18 U.S.C. § 1839(3), so the plaintiff must prove it. Giving the defendant the burden was reversible error. Judge Bumatay dissented from the order of a new trial. In a separate concurrence, Judge Hamilton addressed remedies, including why a damages award and an injunction may coexist under the DTSA.

Mind the clock. Insulet II is the most consequential new case for this subject. A jury found that EOFlow misappropriated four Insulet secrets and awarded $170,000,015 in compensatory and $282,000,005 in exemplary damages, reduced by the district court to $25.8 million and $33.6 million in light of an overlapping permanent injunction. Over Judge Prost's dissent, the Federal Circuit ordered judgment for EOFlow because the three-year limit in 18 U.S.C. § 1836(d) had run. Declining to choose between an inquiry notice standard and the stricter discovery rule, the majority held that knowledge of access through former employees and similarity in the competitor's product is enough to plead a claim, citing Harbor Business Compliance Corp. v. Firstbase.io, Inc., 152 F.4th 516 (3d Cir. 2025) among others, and so starts the clock. Insulet staff had seen EOFlow's clear-cased devices at 2018 and 2019 trade shows and visited its website twenty times, with four former employees already there. A continuing misappropriation is a single claim, so related secrets generally accrue with the first misappropriation, and the majority also concluded that the period had run as to each of the four. The verdict fell. Judge Prost warned that the ruling encourages plaintiffs "to race to the courthouse." Whether other circuits follow is open, and because the court exercised patent-based jurisdiction, regional circuits are not bound. See also Cadence Design Systems, Inc. v. Avant! Corp., 29 Cal. 4th 215 (2002) on the single claim concept.

Mind the bad faith provision. 18 U.S.C. § 1836(b)(3)(D) allows fees for a claim made in bad faith, "which may be established by circumstantial evidence." FLIR and Molon are the warnings. Rule 11 applies too: Fed. R. Civ. P. 11.

Be careful of what a letter can do. An overbroad cease-and-desist that names no secrets does little to create knowledge, as Bombardier shows, and in California may itself raise issues under section 16600.5 if it threatens to enforce a void covenant. Writing a Demand Letter: The Basics and Drafting a Demand Letter: A Practical Checklist cover the basic craft.

Worked hypotheticals

These are invented to show how the rules combine. Any resemblance to real companies is accidental.

Hypothetical 1: the insurance producer with a good memory

Suppose Dana, a commercial insurance producer at Pell & Harlan, a regional brokerage in Ohio, moves to a rival in Indiana. She has a two-year customer nonsolicitation clause, takes no documents, and on her first day writes out 40 client names, renewal dates, and premium levels from memory for her new manager.

"She didn't take anything" is a weak answer in many states. Washington held in Ed Nowogroski Insurance, Inc. v. Rucker, 137 Wash. 2d 427 (1999) that the form of the information does not control, and Ohio reached the same conclusion on customer lists in Al Minor & Associates, Inc. v. Martin, 117 Ohio St. 3d 58 (2008). The new manager, on seeing a list of renewal dates, has reason to ask where it came from, so the new employer is at direct risk. If the claim is brought under Indiana law, Infinity Products removes respondeat superior but leaves liability based on what the company itself knew, and the manager's knowledge is a strong route to that. Under Minnesota law, Hagen would make foreseeability the battleground.

The better plan would have been simple: Dana announces her new job publicly, as permitted, works from public directories and her own general reputation, and steers clear of covered accounts for the period. Her manager should have refused the list and called counsel, not filed it.

Hypothetical 2: the engineer whose Drive syncs itself

Suppose Kestrel Valley Sensors, a Pittsburgh company, hires Ravi from Ostrander Controls in Massachusetts. He signs a certification. In week three an engineer on his team sees a calibration spreadsheet on Ravi's screen bearing Ostrander's logo. Ravi explains that his personal Drive syncs to his personal laptop and that he opened it "just to check a number." Nothing has been reported to management, and Ostrander has not sent a letter.

Start with knowledge: the moment the colleague tells a manager, the company likely has reason to know, and it may already have vicarious exposure in Pennsylvania if the number went into Kestrel's work. Next is preservation: litigation is now arguably reasonably foreseeable under Micron Technology, Inc. v. Rambus Inc., 645 F.3d 1311 (Fed. Cir. 2011), so a duty attaches even without any demand. See also Silvestri v. General Motors Corp., 271 F.3d 583 (4th Cir. 2001). Nobody should tell Ravi to delete the file, which is the instinct everyone will have. Counsel should stop use, take Ravi off the affected calibration work, retain a forensic vendor, and advise Ravi to get his own lawyer, because his interests and the company's may diverge in the way Waymo illustrates. After imaging, the company can plan return or remediation, ideally with Ostrander's agreement. A voluntary disclosure to Ostrander is a judgment call, with benefits in good faith and damage control and costs in inviting a lawsuit. Under Bimbo Bakeries, Pennsylvania courts can move quickly when a court sees copying and concealment, so a forthright approach often does better.

Hypothetical 3: the lift-out across state lines

Suppose Quillon Data, an Austin software company, wants to hire four Seattle engineers from a rival. Each signed a one-year noncompete, governed by the former employer's chosen state law, before 2026. If the move happens after June 30, 2027, Washington's new statute would void those covenants regardless of when signed. Before then, current Washington law (RCW 49.62) sets a compensation floor and limits, and it restricts out-of-state forum and choice-of-law terms for Washington-based workers. If the engineers relocate to Austin, Texas law may apply, in which case Juliette Fowler supplies the defense if the covenant is unreasonable.

The bigger danger is one of the four acting as the recruiter while still employed, which falls squarely under Bancroft-Whitney type reasoning in most states, and collecting names and salaries of colleagues. Have each engineer deal with Quillon separately. Keep compensation information flowing from candidates about themselves only. Do not take a team proposal or roadmap as the sales pitch. Note Comet: an offer of a ready-made "crew" with a "turnkey" design is the sentence your outside counsel never wants to read in an email.

Exposure in numbers

The headlines are big, but the appellate record is more complicated. Motorola stands at $407.4 million on the DTSA claims. Insulet went from $452 million at verdict to about $59 million after the district court's adjustment to nothing on appeal. Comet's judgment of more than $57 million was reversed and awaits retrial. The $919.9 million verdict in Kolon was vacated on appeal.

Those reversals do not mean the risk is small. Injunctions can be worse than damages. A permanent order in Insulet reached any product developed using the secrets, worldwide, until reversed. Fees run to seven and eight figures. Founders and engineers can face personal judgments, and Insulet's judgment was joint and several with the chief executive before reversal. Criminal exposure exists under 18 U.S.C. § 1832, including for one who "receives, buys, or possesses" a secret knowing it was stolen. The DTSA's employee immunity notice under 18 U.S.C. § 1833(b) also affects what the former employer may recover against an individual if its agreement lacks the required notice. For models and proof, see Proving or Defending Against Trade Secret Damages: A Practical Guide.

What remains unsettled

• The scope of the DTSA employment limit. No circuit has given a definitive reading of "evidence of threatened misappropriation" in section 1836(b)(3)(A)(i)(I). The treatment of inevitable disclosure as "foreclosed" comes from district courts.
• Respondeat superior under the DTSA. Commonly applied, but no controlling circuit authority resolves whether it fits a statute with a scienter element, or the limits on exemplary damages against an innocent employer.
• Accrual after Insulet II. Whether inquiry notice or the discovery standard of Merck & Co. v. Reynolds, 559 U.S. 633 (2010) governs, and whether access plus similarity should be the test elsewhere, remains open outside the Federal Circuit's reasoning, and even there a dissent challenged the framework.
• The reach of Cal. Bus. & Prof. Code § 16600.5 against out-of-state employers and judgments.
• The two-track remedy question. Whether unjust enrichment damages and an injunction overlap, a question Judge Hamilton's Comet concurrence takes up while discussing a Fifth Circuit decision involving Tata Consultancy, is not settled.
• Federal competition policy. The FTC has left rulemaking behind, but the status of the 2025 labor guidelines and the shape of case-by-case enforcement are subject to change.

What to do with all this on Monday

If you are about to hire, three things matter more than anything else in this article. Learn what paper binds the candidate and in which states. Design the job and the first 90 days so the secrets are not needed, and be able to show that. Tell the candidate, in writing and aloud, to leave everything behind, and then check the door. If something comes through anyway, freeze it, do not erase it, and call counsel the same day.

If you are the one losing the employee, get the forensics early, name the secrets specifically, write to the new employer with facts, and calendar the three-year clock from the moment you see a similar product and know where your people went. Trade Secret Litigation Toolkit: Identification Statements, Two-Tier Protective Orders, and Forensic Protocols has forms, and Preliminary Injunctions and Temporary Restraining Orders: Emergency Relief in Federal Court addresses emergency relief. Getting Into or Staying Out of Federal Court: A Practical Guide to Jurisdiction and Removal addresses the forum question.

This article is general information and is not legal advice for a specific situation. If a hire or a demand letter has landed on your desk, a short conversation with counsel early usually costs far less than either side of the cases above.

Related Documents

Related Articles

• Protection of Trade Secrets: the foundation doctrine of what qualifies as a secret.
• Non-Compete Agreements Under Siege: FTC Rulemaking and State Law Developments: background on the FTC rulemaking, to be read with the February 2026 removal in mind.
• Tortious Interference and Unfair Competition Claims Between Businesses: the general tort behind raiding claims.
• Identifying Trade Secrets in Litigation: Reasonable Particularity, Sequencing Discovery, and Protecting the Secret While You Sue: how plaintiffs must define what they claim was taken.
• Trade Secret Damages and Remedies: Unjust Enrichment, Reasonable Royalties, Injunctions, and Exemplary Awards: the money and injunction side.
• Litigation Holds, Spoliation, and Rule 37(e): Preserving Electronic Evidence Before It Costs You the Case: the preservation law behind the WeRide sanctions.
• Trade Secrets in the Age of Remote Work and Cloud Computing: how cloud and remote work change exfiltration.
• Restrictive Covenants in Business Sales, Franchises, and Partnerships: covenants outside the employment setting.
• The Computer Fraud and Abuse Act After Van Buren: Gates, Insiders, Scrapers, and the Loss Requirement: why Van Buren narrowed the computer access claim that used to accompany these cases.

Related Guides

• Onboarding a Competitor's Employee Without Importing Its Secrets: A Practical Guide: the sequenced practical companion to this article.
• Trade Secret Misappropriation Litigation Under the Defend Trade Secrets Act: A Practical Guide: how a federal case proceeds once filed.
• Responding to a Cease and Desist Letter: A Practical Guide: responding to a demand in general.
• Managing Discovery in a Trade Secret Case: A Practical Guide: discovery once a dispute is in court.
• Getting Into or Staying Out of Federal Court: A Practical Guide to Jurisdiction and Removal: forum and removal choices when state and federal claims are combined.

Related Checklists

• Competitor Hire Trade Secret Checklist: A Practical Checklist: the desk version of hiring, onboarding, and dispute tasks.
• Employee Departure Trade Secret Protection Checklist: A Practical Checklist: the mirror image for the company losing the employee.
• Litigation Hold and Evidence Preservation Checklist: A Practical Checklist: the steps for issuing and managing a hold.
• Preliminary Injunction and TRO Application Checklist: A Practical Checklist: the emergency relief task list.

Related Toolkits

• Lateral Hire Toolkit: Candidate Certifications, Onboarding Instructions, and Cease-and-Desist Responses: certifications, memos, quarantine protocols, and letters ready to adapt.
• Trade Secret Litigation Toolkit: Identification Statements, Two-Tier Protective Orders, and Forensic Protocols: identification statements and forensic protocols for filed cases.
• Trade Secret Remedies Toolkit: Damages Models, Head Start Analyses, and Injunction Briefing: head start analyses and injunction briefing.
• Computer Access Dispute Toolkit: Access Revocation Letters, Loss Worksheets, and Pleading Outlines: access revocation and related forms.