Manufacturing
Toll manufacturing agreements: who owns batch records and process data?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
In a toll manufacturing agreement, ownership of batch records and process data is whatever the contract says; there is no default rule. Title to materials, the duty to create records and ownership of those records are separate questions. Toll processors keep the most when the agreement separates the customer's recipe and product data from the processor's own operating know-how.
Key takeaways
- The customer usually keeps title to materials and product, but that does not decide who owns the records about making it.
- Executed batch records mix the customer's recipe with the processor's equipment, cleaning and deviation history.
- Process know-how is protected as a trade secret only if the processor takes reasonable measures to keep it secret.
- Read the definitions of confidential information, customer data and improvements before relying on any record.
- Return-or-destroy clauses at termination can erase history the processor assumed it could keep.
Why title to materials does not settle record ownership#
Title to materials does not settle record ownership because a toll agreement handles physical goods and information in different clauses. The customer typically supplies or pays for the raw materials, keeps title through processing and owns the finished product. The toll processor supplies equipment, people, permits and know-how.
Records sit between the two. A batch record describes the customer's product, but it also captures how the processor's reactors, blenders and dryers behaved, how its operators handled deviations and how its cleaning program performed. Agreements that never separate those threads leave both parties assuming they own everything.
Three questions to keep separate#
Three questions decide who controls toll processing records: who holds title to materials, who must create and keep records, and who owns and can access the records once made. The table sets out typical positions and what to check.
Silence on the last two rows is common, and it is where disputes start. Neither side's assumptions substitute for language in the agreement.
| Question | Typical position | What to check in the agreement |
|---|---|---|
| Title to raw materials and product | Customer, throughout processing | Risk of loss, yield and loss allowances |
| Duty to create records | Processor, to the customer's specification and quality agreement | Quality agreement, master batch record approval, record formats |
| Ownership of executed batch records | Varies; often customer for product data | Definitions of customer data, deliverables and confidential information |
| Access and audit rights | Customer may audit and copy records | Audit scope, notice, frequency and cost |
| Retention and return | Processor retains for a set period, then returns or destroys | Return-or-destroy clause, survival, archive copies |
| Equipment and historian data | Often unstated | Whether process data counts as customer data or processor records |
| Improvements and know-how | Often unstated or split | Improvements clause, license back, limits on use for other customers |
What a batch record contains, and whose information is in it#
A batch record contains a mix of the customer's information and the processor's own operating history. Sorting the components is the first step in deciding what each side can use.
- Master batch record or recipe: the customer's formula, quantities and specifications, usually the customer's confidential information.
- Executed batch record: actual charges, times, temperatures and operator sign-offs for a lot, mixing both parties' information.
- Deviations and investigations: what went wrong and how it was fixed, often revealing processor know-how.
- QC results and certificates of analysis: test data on the customer's product.
- Equipment and historian data: sensor readings from the processor's control systems.
- Cleaning, changeover and maintenance records: the processor's own procedures and results.
- Yield, waste and loss records: tied to commercial terms on both sides.
Protecting the processor's know-how#
A toll processor's know-how, such as how it controls an exotherm, shortens a cleaning cycle or rescues an off-spec batch, is protected mainly through contract and trade secret law. The federal definition in 18 U.S.C. 1839(3) sets two conditions: the owner must take reasonable measures to keep the information secret, and the information must draw independent economic value from not being generally known or readily ascertainable by others.
DOJ guidance says reasonable measures need not be absolute, citing examples such as limiting access on a need-to-know basis and requiring confidentiality agreements. For a processor, that means restricting who can see historian data and deviation files, marking procedures confidential and making confidentiality obligations mutual in its toll agreements.
Handing full historian exports or unredacted deviation investigations to every customer who asks can weaken that position. Provide what the quality agreement requires, in the scope it requires.
When the processor developed the process, not just ran it#
The ownership picture shifts when the toll processor developed the manufacturing process rather than simply running a recipe the customer handed over. Scale-up work, pilot batches and process development studies create new know-how, and customers who pay for that work often expect to own it.
Look for a separate development agreement or statement of work, because its IP clause may differ from the main toll agreement. A common split gives the customer the process as applied to its product, while the processor keeps general techniques for handling a class of materials or running its equipment. If no development terms exist, the records from that phase are among the most likely to be disputed later.
Clauses to find in an existing toll agreement#
Existing toll agreements usually answer more than people expect once the right clauses are read together. Pull the toll agreement, the quality agreement and any NDA, and look for these provisions.
- Definitions of confidential information, customer data, product data and deliverables.
- Ownership of improvements, including any split between product-specific and general process improvements.
- Restrictions on using knowledge gained on one customer's product for other customers.
- Record retention periods and formats under the quality agreement.
- Return-or-destroy obligations at termination, and whether archive copies may be kept.
- Audit and inspection rights, including access to electronic systems.
- Survival periods for confidentiality and use restrictions.
Illustrative: a toll blender reviews its customer agreements#
Illustrative: a fictional toll blender processes lubricant additives and specialty powders for several chemical companies. Its ERP tracks customer-owned inventory, its LIMS holds QC results, an electronic batch record system holds executed records, and a plant historian stores mixer, temperature and dust-collector data for every run.
The general counsel reads each toll and quality agreement. One customer's agreement defines all data generated in performing the services as customer data. Others treat formulas and test results as the customer's confidential information but say nothing about equipment data, cleaning records or deviations. One agreement requires return or destruction of all records at termination.
The company decides that historian data, cleaning validation and equipment-related deviation records from agreements without the broad customer-data definition can be treated as its own operating records, once formulas, product names and customer identities are removed. It adds explicit language on equipment and process data to its standard agreement for new customers, and keeps the terminated customer's records only as that agreement allows.
How SourceX handles toll processing records#
SourceX treats toll processing records as licensable only after a rights review confirms that the processor, not the customer, controls them. In the Rights step of the SourceX five-step transaction, each toll agreement and quality agreement is read for definitions, improvements and return-or-destroy clauses.
Records that clear review move to Preparation, where customer formulas, product codes, lot numbers and customer identities are removed. The SourceX Evidence Packet documents provenance, licensing rights, permitted use, the privacy record and release authorization, and the processor approves each step before anything is delivered.
Frequently asked questions
Does the customer's right to audit mean it owns the records?
No. Audit rights let the customer inspect, and often copy, records to verify quality and compliance, but access is not ownership. Read the audit clause for its scope, then check the definitions of customer data and confidential information, which decide whether the processor may use the records for anything else.
Can a toll processor use what it learns on one product for another customer?
General skill and experience usually stay with the processor, but using one customer's confidential information for another is usually restricted. Many agreements handle this through an improvements clause or a use restriction. Where the agreement is silent, have counsel review before relying on any specific record.
What should a new toll agreement say about historian data?
It should state plainly whether sensor and equipment data from the processor's systems are customer data or processor records, and what the customer may access. A common middle ground gives the customer the data needed for batch release and investigations, while the processor keeps equipment-level history with product identifiers removed.
Do return-or-destroy clauses cover electronic backups?
Often the clause does not say, which creates risk. Some clauses allow archive copies for legal or regulatory retention; others require destruction of all copies. Check how your backups and historian archives actually store customer data, and negotiate an explicit archive exception where you need one.
Is toll processing data useful for AI?
It can be, when equipment behavior, deviations and corrective actions are recorded consistently across many runs and linked to outcomes. Value depends on uniqueness, domain expertise and data cleanliness, and it falls if records cannot be separated from customer formulas. Rights come first, because a record the processor cannot license has no licensing value.
Sources
- Under 18 U.S.C. 1839(3), information qualifies as a trade secret only if the owner has taken reasonable measures to keep it secret and it derives independent economic value from not being generally known to, and not readily ascertainable through proper means by, another person who can obtain economic value from its disclosure or use. Source
- DOJ guidance states that trade secret protective measures need not be absolute but must be reasonable under the circumstances, citing examples such as advising employees of the trade secret's existence, limiting access on a need-to-know basis, requiring confidentiality agreements, and keeping documents locked. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.