When a Senior Engineer Leaves a Foshan Appliance Manufacturer

A senior engineer leaves a Foshan appliance manufacturer after twelve years and joins a competitor. Within months, the competitor launches a product using a manufacturing process that looks unusually similar to the former employer’s internal method. The engineer had access to drawings, testing parameters, supplier specifications and cost data. Before departure, system logs show a large download from the engineering repository. Management wants an injunction and damages for trade-secret theft. The 2025 Anti-Unfair Competition Law, effective from October 15, 2025, defines trade secrets as non-public commercial information with commercial value that is subject to corresponding confidentiality measures, and prohibits improper acquisition, disclosure and use.^[1] The law also addresses conduct by former employees and third parties who know or should know of misappropriation. The download is important, but it is not the case by itself. The manufacturer needs to identify the secret, prove that it was actually secret, show the measures used to protect it, connect the engineer to the information and establish misuse or a legally sufficient basis for the court to draw the relevant inference.

The specific problem#

Defining the secret and confidentiality measures#

Trade-secret claims fail when the plaintiff describes the protected information at an abstract level. An appliance manufacturer may have thousands of drawings and specifications. Some are public in patents, product manuals or supplier catalogs. Others are ordinary industry standards. The litigation team needs a secret-point schedule that separates genuinely non-public information from general engineering knowledge. A useful schedule can identify a particular process window, tolerance combination, unreleased design configuration, supplier treatment specification, testing sequence or cost model. Each secret point should be linked to a document or controlled repository. The company also needs to explain why the information has commercial value. That may be because it reduces scrap, shortens cycle time, improves performance, lowers cost or allows a product to pass a customer requirement. Overclaiming is dangerous. If the plaintiff labels an entire engineering database secret, the defendant can attack the claim by showing public or generic material inside it. Precision improves both legal analysis and judicial confidentiality management. The Anti-Unfair Competition Law requires corresponding confidentiality measures.^[1] A company cannot create secrecy retroactively by stamping “confidential” on files after litigation begins.

The evidence should show how the information was controlled in ordinary business. Relevant measures may include role-based access, confidentiality clauses, internal classifications, restricted repositories, download controls, supplier NDAs, device policies, physical access limits and exit procedures. The measures need to match the information’s importance. A highly valuable process shared freely through an unrestricted group chat creates a harder case than a controlled engineering file accessible only to a defined project team. The employer also needs to prove that the engineer was subject to the relevant obligations. Employment contract provisions, confidentiality agreements, handbook acknowledgments and project-specific notices can establish that context. A strong protection system is not one with the longest NDA. It is one where the company can show that sensitive information was identified, access was limited and employees understood the restrictions. System logs can be powerful, especially when a departing employee downloads unusual volumes of data. The company needs to preserve the original logs, device records, repository history, email forwarding and removable-media information through a lawful investigation process.

Timing matters. A large download two days before resignation is more probative if the files correspond to the later competing product. A routine backup six months earlier may have a different explanation. The employer needs to avoid assuming that every downloaded file was misused. The analysis needs to connect access to the claimed secret points. HR records can provide context, including resignation notice, discussions about future employment and the employee’s assigned projects. Engineering records can show which information the employee actually worked with. The investigation should also identify whether the employee used personal cloud storage or messaging applications, but evidence collection needs to comply with applicable privacy and data rules. The case becomes stronger when the access timeline and the competitor’s development timeline align. Trade-secret protection cannot prevent an engineer from using ordinary professional knowledge acquired through years of work. That distinction is central to a fair case. The employer needs to separate protectable information from the engineer’s general skills, memory, training and industry understanding. An experienced engineer may know that a certain manufacturing method is commonly effective without relying on confidential documents.

The defendant may argue independent development. The competitor’s R&D records, prior projects and hiring rationale can therefore matter. The plaintiff’s strongest position is not that the engineer “knows too much.” It is that the engineer or competitor used identifiable non-public information obtained through a protected relationship. This distinction also affects non-compete strategy. A trade-secret case should not be used as a substitute for an unenforceable or expired restraint on competition.

Access, employee mobility and third-party use#

The 2025 law extends trade-secret liability to third parties who know or should know that an employee, former employee or other person has engaged in prohibited conduct and still obtain, disclose or use the secret.^[1] That makes the competitor’s onboarding process relevant. If the new employer immediately asks the engineer to recreate a former employer’s confidential drawings, the facts look very different from a company that instructs the hire not to bring third-party materials and documents an independent development process. The plaintiff needs to look for evidence linking management to the alleged misuse: project assignments, file transfers, communications, rapid development and access to the former employer’s documents. The defendant may respond with clean-room evidence, independent design records and compliance instructions. For manufacturing companies hiring experienced personnel, a documented onboarding process can reduce both actual misuse and later suspicion. The same product may involve both patent rights and trade secrets, but the claims protect different things. A patent is public and protects the claimed invention within its legal scope. A trade secret protects non-public information.

If the company patented the exact process parameter it now calls secret, the public disclosure may undermine secrecy. On the other hand, a patent may cover the broad technical concept while confidential know-how covers implementation details. Before filing, counsel needs to build two separate maps: one for patent claims and accused features, another for secret points and access evidence. The litigation team should also assess patent validity and whether the competitor designed around the registered right. A disciplined combined strategy can be powerful. An undisciplined one can create contradictions. Management often wants an immediate injunction after discovering suspicious downloads. The legal team needs to identify the urgent harm: imminent product launch, threatened disclosure at a trade show, continued access to a repository, or transfer of sensitive files to third parties. Evidence preservation may be as important as conduct restraint. Management can secure its own systems first by revoking access, preserving devices and changing credentials. It should also identify which external suppliers or accounts the former employee could access.

Court applications need a focused evidentiary package. A broad allegation that “the engineer can damage us because he knows our secrets” is weaker than proof of a specific secret, suspicious access and a competing product about to launch. Applicant security and potential wrongful-measure risk should also be assessed where required. Assume a Foshan appliance manufacturer developed a confidential heat-treatment window that reduces compressor failure rates. The parameter is not disclosed in its patents. Access is limited to six engineers and two approved suppliers under confidentiality agreements. A senior engineer downloads the process file and supplier test results shortly before joining a competitor. Four months later, the competitor launches a compressor line with unusually similar performance and instructs one of the same suppliers to use the same treatment range. The company’s case can focus on the defined heat-treatment window and test protocol, existing access controls, the engineer’s download history, supplier evidence and the competitor’s rapid adoption. It should avoid claiming unrelated drawings or general compressor knowledge. The competitor, in turn, may try to prove independent development or public industry knowledge.

A narrow evidence-driven case is more persuasive than a broad accusation based on employee movement.

Patent overlap and emergency remedies#

The company can begin damages analysis early. Possible evidence can include lost sales, price erosion, avoided R&D cost, defendant profit, licensing value and other legally recognized measures depending on the facts and relief sought. The finance team should identify when the competitor entered the market and which customers were affected. If the secret saves production cost rather than creates a unique product feature, the damages theory may focus on the economic advantage gained through misuse. The claimant should preserve R&D budgets, testing records and cost improvements that demonstrate value. Punitive or enhanced remedies require careful statutory analysis and evidence of the relevant misconduct; they should not be assumed simply because management views the conduct as deliberate. A realistic damages model also supports settlement. A trade-secret dispute usually reveals weaknesses that existed before the employee resigned. Manufacturers can improve future protection by connecting HR, IT, legal and engineering processes. When a key employee resigns, the company can review recent access, disable accounts at the correct time, recover devices, remind the employee of confidentiality obligations and identify projects requiring knowledge transfer.

The process should be risk-based. Routine exits do not require forensic investigation. High-risk departures involving core technical staff may justify enhanced preservation and review under lawful internal policies. Supplier access should be reviewed at the same time if the employee managed external technical relationships. The objective is not surveillance for its own sake. It is to preserve business continuity and evidence around genuinely sensitive information. A former engineer may not reproduce a process internally. The engineer can instead instruct a familiar supplier to make a component using confidential parameters. That makes supplier evidence central. The former employer should identify which suppliers received the secret, under what confidentiality terms and whether the competing company later contacted them. Purchase orders, technical instructions, sample requests and supplier witness evidence can connect the new product to the protected information. The company needs to also review whether its supplier contract allowed the supplier to reuse general manufacturing knowledge. A supplier that developed its own process before the disputed project may have legitimate background know-how. The litigation team should therefore distinguish customer-provided secret information from supplier-created methods.

This avoids turning an employee case into an overbroad claim against the whole supply chain.

Damages, forensic limits and governance#

Digital evidence can be compelling, but internal investigations must be conducted lawfully. The company should rely on policies and system authority that permit legitimate business review. Personal information unrelated to the investigation should not be collected indiscriminately. Where a company device contains both work and personal material, the investigation protocol should minimize irrelevant access. External forensic providers should operate under clear instructions covering scope, preservation and confidentiality. Counsel needs to document why particular accounts or devices were examined. This discipline strengthens evidentiary credibility and reduces the risk that the investigation itself creates privacy or employment disputes. The goal is targeted preservation of business evidence, not retrospective surveillance of an employee’s entire digital life. A company may have both a non-compete agreement and confidentiality obligations with the departing engineer. They serve different purposes. A non-compete restricts specified competitive activity subject to legal conditions. Trade-secret law restricts improper use of protected information regardless of whether the employee works for a competitor. Interpretation II on labor disputes provides current judicial guidance on non-compete issues.^[2]

Management can assess whether the non-compete is enforceable, appropriately scoped and supported by required compensation. If it is not, the company can not attempt to use a weak trade-secret allegation simply to achieve the same restraint. Conversely, expiration of a non-compete does not authorize theft or use of trade secrets. Keeping the theories distinct improves both employment and IP litigation. Trade-secret compliance becomes more effective when management prioritizes. Not every internal document requires the same protection. The company can classify information by economic importance, ease of replication and access risk. Core process formulas, unreleased product architecture, customer pricing strategy and supplier specifications may receive higher controls than routine operational documents. That classification helps IT design access, HR manage departures and legal prove corresponding confidentiality measures. It also reduces friction. Employees are more likely to follow controls that are targeted and understandable than a system that labels every email “top secret.” The trade-secret register should be reviewed periodically because information loses or gains sensitivity as products enter the market.

A practical governance system creates better litigation evidence because the company can show that its protection choices were deliberate.

Cross-border evidence and settlement design#

Foreign-invested manufacturers may store engineering information on regional or global servers. The China subsidiary can face a trade-secret dispute even though the relevant files are owned or controlled by an overseas parent. Before litigation, the group should identify which entity owns the information, which entity granted access to the employee and who suffered the commercial harm. Intercompany licenses and confidentiality arrangements can support that chain. Cross-border collection of forensic evidence may also require data-law analysis. The legal team can plan how necessary records can be lawfully accessed, preserved and produced. A strong technical case can be weakened if the plaintiff cannot explain why it has standing to enforce information created and stored elsewhere in the group. Management may attribute every lost order to the competitor’s use of the secret. The damages file should distinguish customers actually exposed to the competing product from general market decline. Sales communications, bid history, pricing and launch dates can help connect loss to the alleged misuse. Where a customer chose the competitor for unrelated reasons, that loss should not be included simply to increase damages.

A narrower but well-supported commercial model is more credible. The same discipline applies to avoided R&D cost. The claimant needs evidence of the work and expense required to develop the secret, not an arbitrary estimate. A practical resolution may require the competitor to delete specified files, stop using defined process parameters and certify that a redesigned product was developed independently. The parties can use an independent expert where disclosure between competitors would be commercially sensitive. The settlement should not try to prevent the engineer from using general professional skills. Technical specificity makes compliance easier to verify. It also reduces the chance that the settlement becomes an indirect non-compete broader than the actual trade-secret rights. For manufacturing disputes, a well-designed technical settlement can preserve legitimate competition while protecting the information that gave rise to the case.

Case analysis and enforcement decision#

Companies often focus entirely on their own logs. The defendant’s public materials can also matter. Patent filings, recruitment advertisements, product launch dates, supplier announcements and technical marketing may reveal when the competing project began and which capabilities the competitor claimed to possess. A timeline showing that the competitor had already been developing the technology for years can weaken the former employer’s inference of misuse. A sudden launch immediately after the engineer’s arrival can support closer investigation but still requires technical proof. The claimant should preserve public evidence neutrally rather than select only materials that support its preferred story. A case is stronger when the company has tested alternative explanations before filing. A settlement can resolve the immediate competitor dispute without fixing the underlying control gap. The manufacturer should review why the engineer had access to particular repositories, whether supplier restrictions were sufficient and whether key know-how was documented in a way that supports continuity after personnel changes. The legal team can use the case to improve classification, access review and exit procedures. This is not an admission that the company’s earlier measures were legally inadequate.

It is a governance response to the practical lessons revealed by the incident. Over time, better systems reduce both the probability of loss and the cost of proving what happened. Not every suspicious departure justifies immediate litigation. The company needs to compare the strength of the secret definition, evidence of access, evidence of use, commercial harm and urgency. A focused warning letter may be appropriate where the evidence is strong enough to require preservation but not yet strong enough for court action. In other cases, silent evidence collection is preferable before alerting the new employer. Management should also consider whether the most important result is damages, product redesign, return of information or protection of a customer relationship. That objective determines the remedy and the settlement position. A disciplined decision process reduces the risk that anger over an employee departure drives a weak case.

Management can also decide how it will communicate with customers and suppliers if the dispute becomes public. An accusation against a former engineer can affect the new employer, shared suppliers and customers who use both companies. External statements should remain factual and avoid asserting liability before a court has determined it. Sales teams should not pressure customers to choose sides or circulate forensic allegations casually. At the same time, key customers may need reassurance if the disputed information relates to product quality, safety or exclusivity. A coordinated communications plan protects the litigation record and commercial relationships. It also reduces the risk that inconsistent public statements are later used to challenge the company’s description of what information was secret or how serious the alleged misuse was.

Conclusion#

The 2025 Anti-Unfair Competition Law gives companies a strong statutory framework for trade-secret protection, but litigation still depends on disciplined facts.^[1] For a Foshan manufacturer, the core proof is a chain: a precisely defined secret, real confidentiality measures, employee access, suspicious acquisition or use, and a commercial connection to the competing product. A departing engineer is allowed to take skill and experience. The legal case becomes compelling only when the company can show that identifiable protected information crossed the line with the employee or was knowingly used by the new employer.

Legal and regulatory sources#

^[1] Anti-Unfair Competition Law of the People’s Republic of China (2025 Revision), especially the trade-secret provisions and evidentiary rules — [official source](https://www.npc.gov.cn/npc/c2/c30834/202506/t20250627_446247.html) ^[2] Patent Law of the People’s Republic of China — [official source](https://www.npc.gov.cn/npc/c2/c30834/202011/t20201119_308800.html)

General legal information only; not legal advice for a particular employee departure or IP dispute.