Manufacturing
Background vs foreground IP in contract manufacturing: what the CM keeps
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Contract manufacturing IP ownership turns on two definitions: background IP, which each party brings or develops outside the program, and foreground IP, which the program creates. A contract manufacturer keeps the most when the agreement assigns product-specific foreground to the customer but reserves general process improvements, and the operating records behind them, to the CM.
Key takeaways
- Background IP stays with whoever brought it; disputes almost always center on foreground and improvements.
- A broad clause giving the customer everything it pays for can reach the CM's own process improvements and records.
- A general process improvements carve-out is the clause that most protects a CM's ability to reuse operating records.
- Work made for hire covers only certain copyrightable works, so assignment and confidentiality clauses usually do the real work.
- Customer drawings, BOMs and specifications remain customer-confidential under every drafting pattern.
What are background and foreground IP in a manufacturing agreement?#
Background IP is what each party owns before the agreement or develops outside it; foreground IP is what is created in performing the agreement. For a contract manufacturer, background usually includes process know-how, test methods, fixture designs, its quality system and manufacturing software configurations. The customer's background is its product design, specifications and brand.
Foreground is where ownership gets decided. It can include product-specific tooling and test fixtures, process validations for the customer's product, design-for-manufacturing changes, and improvements to the CM's own processes discovered while building the product. How the agreement treats that last category decides what the CM walks away with.
Three drafting patterns compared#
Most contract manufacturing agreements follow one of three patterns, and each gives a different answer to whether the CM can reuse its operational records. The labels below are descriptive, not standard legal terms, and real agreements often blend them.
The split pattern is the usual middle ground in negotiated agreements. The customer-owns pattern often appears in a large customer's own master supply agreement form, and the CM-owns pattern is more common where the CM brings a proprietary process the customer cannot easily source elsewhere.
| Pattern | What the customer gets | What the CM keeps | Can the CM reuse its operating records? |
|---|---|---|---|
| Customer owns what it pays for | All foreground, often including improvements made during the program | Background only, sometimes with a narrow license back | Limited; records of program improvements may be customer property or confidential |
| Split by subject matter | Product-specific foreground: designs, product test methods, dedicated tooling | General process improvements and know-how not specific to the product | Usually yes for general process records, after customer information is removed |
| CM owns foreground, customer licensed | A license to use foreground for its product, sometimes exclusive | Ownership of foreground and background | Broadest reuse, subject to confidentiality and any exclusivity |
The general process improvements clause, element by element#
A general process improvements clause reserves to the manufacturer improvements to its own methods that are not specific to the customer's product and do not use the customer's confidential information. Clause libraries word it differently, but the stronger versions share a few elements.
The weakest versions define improvements by who paid for the engineering time. That test pulls nearly everything into foreground, because almost every process change happens while the CM is building somebody's product.
- A definition of general improvements that turns on whether the improvement applies beyond the customer's product.
- An express statement that the CM owns those improvements and may use them for other customers.
- A carve-out from the confidentiality clause for the CM's general know-how and records, with customer information excluded.
- A residuals provision for skills and general knowledge retained in employees' memories, where both parties accept one.
- A license back to the customer for any CM improvement built into the customer's product, so the customer is never blocked.
Where work made for hire language falls short#
Work made for hire language often does less than drafters expect in a manufacturing agreement. Under 17 U.S.C. 101, a work prepared by an employee within the scope of employment is a work made for hire, but a commissioned work qualifies only if it falls in listed categories, such as a contribution to a collective work, a compilation or an instructional text, and the parties expressly agree in a signed written instrument.
Process know-how, cycle-time improvements and machine parameters are not copyrightable works to begin with. Control over them is set by assignment clauses, confidentiality obligations and trade secret law. A clause calling everything the CM produces a work made for hire therefore has to be read alongside the assignment and confidentiality language, which usually carries the real weight.
Which CM records belong to whom?#
Under a split pattern, most of a CM's day-to-day operating records describe its own process and remain its records, while anything revealing the customer's product stays customer-confidential. The table shows a typical allocation; your agreements may differ.
| Record | Typical position under a split pattern | Watch for |
|---|---|---|
| Customer drawings, BOMs, specifications | Customer background and confidential | Never include in reuse or licensing |
| Work orders, routings and labor times | CM operating records | Routings that copy customer process specifications |
| Machine and line data, SPC, yields | CM operating records | Part numbers and product names embedded in the data |
| NCRs, CAPAs and root-cause analyses | Mixed: CM process findings plus customer product details | Product defect data the customer treats as confidential |
| Product-specific test methods and results | Usually customer foreground | Test fixtures the CM designed on its own initiative |
| Quoting and cost models | CM business records | Customer pricing terms under confidentiality |
Illustrative: an electronics CM sorts its customer agreements#
Illustrative: a fictional electronics contract manufacturer runs SMT and box-build lines for industrial equipment makers. Its MES records every board through placement, reflow, inspection and functional test, and its quality system holds years of NCRs and CAPAs. The CEO wants to know which of these records the company can reuse, including for licensing.
The general counsel sorts the customer agreements into the three patterns. Two large customers use their own forms, under which the customer owns everything it pays for, improvements included. Most of the rest use the CM's form, which splits product-specific foreground from general process improvements. One agreement says nothing about improvements at all.
The company treats line performance, defect-resolution and maintenance records from split-pattern customers as reusable once part numbers, board names and customer identities are removed. Records from the two customer-form agreements are excluded, and the silent agreement goes to outside counsel. At the next renewal, the CM proposes its own improvements clause to both large customers.
How to negotiate a better split at renewal#
Renewal is the practical moment to fix an unfavorable pattern, because the customer values continuity and the CM has a performance record to point to. Ask for changes a customer's lawyer can accept without a long fight.
- Propose the subject-matter test for improvements instead of a who-paid test.
- Offer a royalty-free license back for any CM improvement built into the customer's product.
- Add an express right to use de-identified operating records for internal analytics and other lawful purposes, with customer information excluded.
- Separate ownership of fixtures and test equipment the CM designed from the question of who funded the build.
- Match the confidentiality survival period to how long the information actually stays sensitive.
How SourceX reviews CM agreements before licensing#
SourceX reviews contract manufacturing agreements in the Rights step of the SourceX five-step transaction, before any record is prepared or shared. The review asks which pattern each customer agreement follows, which records are the CM's own and which confidentiality obligations still run.
Only records the CM has the right to license move on to Preparation, where customer names, part numbers and product details are removed. The SourceX Evidence Packet then documents provenance, licensing rights, permitted use, the privacy record and the CM's release authorization.
Frequently asked questions
Does paying for tooling give the customer the tool design too?
Not automatically. Paying for a tool usually buys the physical tool, while the agreement decides who owns the design and related process improvements. Many agreements give the customer the tool and leave the CM its general design methods. Read the tooling clause and the IP clause together, because different people often drafted them.
What is a residuals clause, and should a CM ask for one?
A residuals clause lets a party use general knowledge its people retain in unaided memory after working with confidential information. CMs often want one and customers often resist it as too broad. It does not permit copying documents or data, so it rarely helps with records; its value is protecting engineers' experience from later disputes.
Can a CM reuse operating records if the agreement is silent on improvements?
Silence creates uncertainty, not permission. Counsel will look at the confidentiality clause, any assignment language and how the parties have behaved. Treat records from silent agreements as excluded until they are reviewed, and ask the customer for written clarification at the next renewal.
Do these rules change for export-controlled work?
Yes. Under ITAR, technical data includes blueprints, drawings, plans, instructions and documentation required to produce defense articles, and that data is restricted whoever owns it. Export-controlled and defense programs sit outside SourceX licensing entirely, and regulated customers in other sectors often add their own record and audit controls.
Who owns data generated by the CM's machines?
Usually the CM as operator of the equipment, subject to customer confidentiality over product information in the data and to the equipment maker's software terms. Some equipment and software vendors claim rights to machine data under their service agreements, so check both the customer agreement and the vendor contracts.
Sources
- 17 U.S.C. 101 defines a work made for hire as a work prepared by an employee within the scope of employment, or a specially ordered or commissioned work in listed categories, such as a contribution to a collective work, a compilation or an instructional text, if the parties expressly agree in a signed written instrument. Source
- 22 CFR 120.33(a)(1) defines ITAR technical data to include information required for the production and manufacture of defense articles, including blueprints, drawings, photographs, plans, instructions or documentation. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.