Manufacturing
Illustrative data package: a co-packer's run and changeover records
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
A co-packer dataset example shows how a contract food manufacturer's own operating records could be packaged for licensing: schedule versions, changeovers, run lots and hold-and-release decisions, joined by line and lot. This example is illustrative. The rule: license the plant's sequencing and food safety decisions, and keep brand recipes and brand identity out.
Key takeaways
- Saved schedule versions with a reason for each change are the planning record most plants throw away.
- Changeover records gain value when the plan, the time taken and the verification result sit together.
- Brands are described by masked codes, product family and allergen profile, never by name or recipe.
- The co-manufacturing agreement decides which brands' records can be considered at all.
What does a co-packer's run and changeover package contain?#
A co-packer's run and changeover package contains the records that show how a contract manufacturer sequenced brand orders on shared lines, changed lines over between products and allergens, ran each lot and decided whether to hold or release it. Together they describe planning and food safety decisions made under real constraints.
This page builds an illustrative package from a fictional plant. It is a template a co-packer owner can compare with their own ERP, scheduling files and QA logs before deciding whether a data license is worth exploring. Four record families make up the core.
- Schedule: planned runs by line and shift, each saved version and the reason for every change.
- Changeover: the type of changeover, its steps, start and end times, verification results and sign-offs.
- Run: masked lot codes, line speed, downtime events with reasons, waste and rework.
- Hold and release: holds placed, the trigger, the tests run and the final disposition.
Illustrative: the plant behind the example#
Illustrative: Cedar Hollow Packing is a fictional co-packer that hot-fills sauces, dressings and marinades for brand customers on several shared bottling lines. Some products contain milk, egg, soy or wheat and others are allergen-free, so the order in which products run drives most planning decisions.
The plant runs a food ERP for orders, lots and inventory. Planners keep the weekly schedule in a spreadsheet and, unusually, save every version with a note on why it changed. Operators record downtime reasons on line tablets, sanitation crews complete paper changeover checklists that are scanned each night, and QA logs every hold and release in the quality system.
The owner's question was whether the plant's own operating records could be licensed while every brand customer's recipes and identity stayed private. The rest of this page follows that decision.
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
The manifest, file by file#
The manifest names each file, what a single row means, its key fields and the files it links to. Line and lot are the spine of the package, and a masked brand code replaces every customer name.
| File | One row is | Key fields | Links to |
|---|---|---|---|
| schedule_versions | One planned run in one saved version | Line, product family code, allergen profile, planned start, planned quantity, version note | Order ID, line |
| schedule_changes | One change between versions | Run moved, added or cut; reason category; free-text reason; requester role | Schedule version |
| changeover_events | One changeover between two runs | From and to product family, allergen transition, changeover type, start, end, crew role | Line, preceding and following run |
| changeover_checks | One verification check | Check type such as visual, swab or allergen test; result; retest; sign-off role | Changeover event |
| run_lots | One production lot | Masked lot code, line, actual start and end, quantity packed, waste by cause | Order ID, changeover event |
| downtime_events | One stop on a line | Reason code, operator note, length of stop, recovery action | Run lot |
| holds | One hold placed on a lot | Trigger, tests ordered, disposition such as release, rework or destroy, approver role | Run lot |
| brand_codes | One masked brand customer | Masked code, product families, allergen profiles; no names | All files |
Changeover records: where the planning decisions show#
Changeover records show the cost of every sequencing choice, which is why they sit at the center of this package. Running an allergen-free dressing after an egg-based one typically calls for a full wet clean and verification, while the reverse order may need far less, and experienced planners build schedules around that difference.
What makes the records useful outside the plant is the pairing of plan and result. The schedule shows what the planner intended, the changeover event shows what it actually took, and the verification check shows whether the line passed the first time.
| Changeover type | What the record captures | Outcome field that matters |
|---|---|---|
| Same product, new lot | Lot change, code date and label check, line clearance sign-off | Time to first good unit |
| Same allergen profile, new product | Flush or dry clean steps, label and packaging swap | Restart time and first-run waste |
| Allergen to allergen-free | Full wet clean, inspection, swab or allergen test | Pass on first test or retest required |
| Package format change | Filler and capper parts swapped, settings changed | Adjustment time and early-run rejects |
| Sanitation after a hold | Extra cleaning and investigation notes | Release decision and any repeat hold |
Hold and release: how each lot's story ends#
Hold and release records close each lot's story by showing why product was stopped, what was tested and who decided its fate. For a model developer they are compact decision records: a trigger, evidence, a disposition and an approver.
In the fictional plant, holds fall into a few families: a label or code date error found at end of line, a failed fill weight check, a temperature deviation during hot fill, and an inconclusive allergen verification result. Each hold links to its lot, and through the lot to the changeover that came before it.
That link matters. When a hold traces back to a rushed changeover on a tight schedule, the package holds the full chain from planning pressure to food safety outcome. Holds tied to a recall, a regulatory inspection or a consumer complaint are reviewed separately and usually excluded.
What stays out: brand recipes and brand identity#
Brand recipes stay out of the package, along with anything that would identify a brand customer or its products. Formulas, ingredient specifications and process specifications supplied by the brand usually belong to the brand or are confidential under the co-manufacturing agreement, and none of them is needed to show how the plant runs.
What remains is described with masked codes: a product family, a package format and an allergen profile. That is enough to study sequencing, because the decisions turn on allergen transitions and format changes, not on the recipe. Where a small brand portfolio would let a reader guess the brand, preparation coarsens or drops those fields.
The co-manufacturing agreement decides the edges. Some agreements treat every production record for a brand's products as the brand's confidential information, while others leave the co-packer's line, sanitation and scheduling records alone, so counsel reviews each one and excludes brands with restrictive terms.
How SourceX approaches a co-packer package#
SourceX approaches a co-packer package through the SourceX five-step transaction, starting at Supply with a metadata-only fit check: which systems hold schedules, changeovers, runs and holds, and for how many years. No recipes, lot files or scans are requested at that stage.
The plant's sequencing know-how is itself confidential. Under the Defend Trade Secrets Act, information is a trade secret only if its owner takes reasonable measures to keep it secret, which is one reason licensed operating records travel under strict confidentiality, use and access terms.
Rights review focuses on co-manufacturing agreements, Preparation removes brand identifiers and personal details, and the co-packer approves the final manifest before Delivery. The SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and the release authorization, and the co-packer keeps ownership of records that are licensed, not sold.
Frequently asked questions
Are scanned paper changeover checklists usable?
Yes, when each scan can be tied to a line, a date and the runs on either side. The fields that matter, such as start and end times, check results and sign-off roles, are transcribed into structured rows. The scans stay with the plant as evidence and are rarely delivered themselves.
Do brand customers have to consent?
It depends on each co-manufacturing agreement and its confidentiality and data clauses. Some agreements require consent for any use of information related to the brand's products, while others cover only recipes and specifications. Counsel reviews them brand by brand, and some co-packers notify brands even where consent is not required.
Can an allergen profile reveal a brand's recipe?
On its own, an allergen profile reveals far less than a recipe. Combined with a product family, a package size and a small customer list, it could point to one brand. Preparation checks for those combinations and coarsens or removes fields wherever a single brand could be recognized.
Do food safety rules limit what can be licensed?
Food safety rules such as FSMA mainly govern how records are kept and made available to regulators, and other laws or certification schemes may also apply. Records tied to inspections, recalls or complaints are more sensitive and usually excluded. Specific obligations are assessed deal by deal with counsel.
How much schedule history does a package need?
There is no fixed minimum. Longer history helps because seasonal products, new brands and line changes appear, but a shorter period with saved schedule versions and linked changeovers can be more useful than years of final schedules alone. The coverage note states the period included.
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
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.