Manufacturing
Who owns production data when you make parts to a customer's print?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
When you make parts to a customer's print, the customer usually owns the design data and the contract decides the rest, because there is generally no statutory default for production records. A practical split: drawings and specifications are the customer's, inspection results are shared, and your own process decisions are usually yours, subject to confidentiality terms.
Key takeaways
- Ownership of production data on build-to-print work is set mainly by contracts, not by a general statutory rule.
- Customer drawings, models and specifications stay the customer's, and records that reproduce them inherit the restriction.
- Inspection results and certifications on customer characteristics are usually shared or contract-defined.
- Quoting, scheduling, maintenance and internal process records are usually the manufacturer's, but confidentiality clauses can still limit disclosure.
- Owning a record and being free to disclose it are separate questions.
Who usually owns what on build-to-print work?#
On build-to-print work, the customer usually owns the design and the contract decides who controls the records produced while making the part. The design includes drawings, 3D models, specifications, customer standards and any special requirements the customer issued.
There is generally no default rule that hands production data to one side, so the answer comes from the purchase order terms, the supplier quality manual, the NDA and any master supply agreement. That makes a contract review the first step, before anyone assumes that records generated in your plant are free to use.
The three buckets of production data#
Production data on customer-print work sorts into three buckets: customer-owned, shared or contract-defined, and company-owned. The table shows where common records usually fall, but the terms for each customer can move a record from one bucket to another.
Most of the licensing interest sits in the third bucket. Quote histories, job and labor records, maintenance logs and scrap decisions describe how your plant works, and they can often be separated from the customer's design once identifiers are removed.
| Bucket | Typical records | Usual position | Licensing implication |
|---|---|---|---|
| Customer-owned | Drawings, 3D models, specifications, customer standards, tooling designs the customer paid for | Customer property, usually confidential | Excluded |
| Shared or contract-defined | First article inspection reports, PPAP packages, certificates of conformance, measurements of customer characteristics | Delivered to the customer; terms may restrict reuse | Reviewed customer by customer; often excluded or stripped of identifying detail |
| Company-owned | Quotes and cost buildups, scheduling, labor, machine maintenance, scrap and rework decisions, internal improvements | Usually the manufacturer's, subject to confidentiality | Candidate for licensing after review |
Which contract documents decide the answer#
The contract documents that decide the answer are often scattered across a customer portal, an email thread and a supplier manual signed long ago. Gather them per customer before forming a view, and note which version applied to which period of work.
Watch for work product language. Some customer terms say that anything created in performing the order belongs to the customer, which can reach inspection data, programs or reports you assumed were yours.
- Purchase order terms and conditions, including terms incorporated by reference
- Nondisclosure or confidentiality agreements, with their survival clauses
- Master supply or long-term agreements, including intellectual property clauses
- Supplier quality manuals and quality agreements
- Tooling agreements that say who paid for and owns dies, molds and fixtures
- Customer portal terms covering downloaded drawings and data
- Flowdown clauses from government or prime contracts, which may add restrictions
Gray zones: programs, setup sheets and inspection plans#
The gray zones are records you created that still embed the customer's design. CNC programs generated from a customer model, setup sheets that show critical dimensions, CMM programs and inspection plans keyed to the customer's ballooned drawing all reproduce parts of the design.
Even where you own the effort, the content may be confidential to the customer. A conservative approach treats any record that would let someone reconstruct the part as customer-restricted, and keeps only the process facts that stand apart from the geometry, such as setup times, tool life, scrap causes and machine assignments.
Customer-owned tooling sits between the buckets. The die, mold or fixture belongs to the customer, but its maintenance logs, repair notes, hit counts and changeover times are generated by your team, and they can reveal program volumes. Read the tooling agreement before treating those records as company-owned, and remove tool numbers that link back to the customer.
| Record | Embeds customer design? | Common treatment |
|---|---|---|
| CNC or CMM program | Yes, geometry and tolerances | Exclude |
| Setup sheet | Often, through dimensions and fixtures | Exclude or strip dimensions |
| Routing and operation times | Rarely | Usually licensable after review |
| Nonconformance record | Sometimes, through feature references | Remove feature detail and customer identifiers |
| Tool life and machine maintenance log | No | Usually licensable after review |
Owning a record is not the same as being free to disclose it#
Owning a record is not the same as being free to disclose it, because confidentiality clauses can cover information about the customer's program even when the record belongs to you. A scrap log is yours, but if it names the customer's part, program and volumes, sharing it may breach an NDA.
Many confidentiality clauses also reach information derived from the customer's confidential material, and they often survive after the relationship ends. Preparation usually removes customer names, part numbers and program identifiers, but counsel should confirm whether that is enough under each agreement, assessed deal by deal.
A sorting process for a mixed customer base#
A sorting process works best when it starts with customers, not systems. Most shops have a handful of customers behind much of their build-to-print work, and those customers' terms decide most of the outcome.
The tagging step is where projects slow down. If jobs, nonconformances and programs are not tied to a customer in your systems, the decision cannot be applied reliably, so fix that link before promising any scope.
- Rank customers by how much of your record history relates to their parts
- Collect the governing terms for each customer, by period of work
- Mark each customer as exclude, review, or proceed with identifiers removed
- Tag records in ERP, QMS and CAM systems by customer so the decision can be applied
- Separate attachments and programs from structured records before any export
- Record each decision, the reason and who approved it
Illustrative: an injection molder sorts its records#
Illustrative: a fictional custom injection molder makes housings and components to customer prints, mostly in molds its customers paid for. Its ERP holds quotes, jobs and labor; its quality system holds first article reports and nonconformances; its press controllers and a shared drive hold process sheets with setpoints for each part.
Counsel reviews the main customers' terms. One customer's agreement claims all work product, so every record tied to that customer is excluded. For the others, prints, first article reports and part-specific process sheets are excluded, and mold maintenance logs are held back until the tooling agreements are read. Quotes, cycle times, scrap causes and maintenance on the company's own presses are kept with customer, part and mold identifiers removed, and that narrower set goes into a licensing review.
How SourceX handles customer-print records#
SourceX handles customer-print records mainly in the Rights step of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Customer-owned material is identified and excluded first, and shared records are reviewed against each customer's terms before anything is prepared.
Each customer decision, the reason for it and who approved it are written into the SourceX Evidence Packet for the package. The manufacturer approves the final scope, and the license grants defined use rights, not ownership.
Frequently asked questions
If the contract says nothing about data, who owns it?
Silence leaves the question to general legal principles, which vary and do not always give a clear answer, so counsel should assess it. In practice, confidentiality terms often settle what you can do even when ownership is unclear, and many manufacturers simply exclude records tied to that customer's design.
Can we ask a customer for permission to license data?
Yes. Some manufacturers ask customers for written consent to use de-identified process records, especially where the relationship is long and the request is narrow. Explain exactly which records, what is removed and what the license allows. Expect some customers to decline, and plan the scope without them.
Do our own catalog parts raise the same issue?
Usually less. If you design and sell your own catalog parts, the design is yours and the data around it is generally company-owned, subject to supplier and employee terms. The build-to-print question arises when the customer supplies the design.
Are first article inspection reports ever licensable?
Sometimes, in part. The report itself usually lists the customer's characteristics, dimensions and part number, so it is typically excluded. Facts drawn from many reports, such as how often first articles passed by process or material, may be usable if no design detail survives and the customer's terms allow it.
Does removing the customer's name solve the problem?
Not always. A part's geometry, materials and tolerances can identify a program even without a name, and confidentiality terms may cover the information itself, not only who it belongs to. Removing names helps, but records that reproduce design detail are usually excluded regardless.
Should government flowdown clauses change our approach?
They can. Prime contracts and government programs may flow down data rights, export control and safeguarding requirements that restrict what can be shared. Records from those programs are generally excluded from commercial data licenses, and counsel should review any flowdown that applies.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.