.webp)
%20(37).png)
Dipesh Patel is the President & CEO of DP Gayatri, partnering with OEMs and Contract Manufacturers to automate and scale operations. A seasoned management consultant and graduate of the UofM Carlson School of Management, he brings strategic leadership to a portfolio of manufacturing and automation companies delivering factory automation, contract assembly, facility relocation and expansion, and supply chain localization across the U.S. and Latin America.
Most contract manufacturing NDAs are generic mutual NDAs pulled from a template. They cover the basics: don't disclose confidential information, don't use it for other purposes, return or destroy at termination.
Those basics are necessary but not sufficient for a real contract manufacturing relationship. The generic template misses the specific ways an OEM's IP actually leaks in a CM engagement.
Generic NDAs define confidential information broadly ("any information marked confidential or that a reasonable person would understand to be confidential"). That's a starting point.
A CM-specific NDA should also enumerate: drawings and CAD files, BOMs, supplier lists, process specifications, quality specifications, work instructions, test procedures, and any tooling designs. The specificity matters at enforcement time.
Tooling built for your program often has residual value for the CM (fits similar programs, tests similar parts). NDAs should restrict use of your tooling to your program only, and should specify tool return or destruction at program end.
The single most common IP leak in CM engagements: an employee who worked on your program leaves the CM and takes knowledge to a competitor. Standard NDAs don't prevent this. NDA supplements with employee training records, exit protocols, and (where enforceable) reasonable non-solicit clauses reduce this exposure.
Your CAD files, BOMs, and process specs live on the CM's servers. If those servers are breached, your IP is exposed regardless of the NDA. The NDA should require: minimum cybersecurity standards, breach notification within a defined window, and audit rights on data handling practices.
Your CM likely uses sub-suppliers (crimp shops, plating houses, specialty machining). Each sub-supplier represents another IP exposure point. The NDA should require the CM to flow confidentiality obligations down to any sub-supplier who receives your confidential information.
"Breach of this NDA results in $100,000 per incident." Sounds strong. In practice, most courts scrutinize liquidated damages for reasonableness and won't enforce amounts that look punitive. Focus on actual damages and injunctive relief.
"Obligations survive indefinitely." Some information genuinely needs perpetual protection (trade secrets). Most doesn't. Perpetual obligations on ordinary confidential information often become unenforceable over time.
"All improvements to the confidential information become property of Disclosing Party." Aggressive but often disputed. Better to define specific improvements you want to own and let the CM keep their general manufacturing know-how.
NDAs are cheap to sign and expensive to enforce. Litigation costs run six or seven figures and takes years. Most NDA breaches never result in enforcement action because the enforcement cost exceeds the recovery.
The practical protection is: (1) work with CMs whose reputation depends on protecting their customers' IP, (2) segment critical IP so no single CM sees the full picture, (3) use NDAs as a signal of professional expectation, not a legal moat.
DPG operates two contract assembly companies. Every OEM engagement starts with an NDA, and we treat the confidentiality obligations as an operational commitment, not just legal paperwork. If you are evaluating a CM relationship and want to talk through NDA structure or IP protection, that's a fair conversation to have early.
