One-up, one-back lot genealogy, framed the way it should be read in your office: as recall exposure, audit risk, and customer trust. See what one-up, one-back means and the three places genealogy is made or lost. Then get the full template of what to capture at each so a trace answers in minutes.
Read this first · Why this sits on your desk
Traceability is usually treated as a floor task and priced as a board risk. The day it matters, the question is not academic: which lots contain the affected material, where did every one of them go, and can you produce the answer before it becomes a wider recall or a failed audit. A plant that can trace a lot in minutes narrows the recall to the lots actually involved. A plant that cannot pulls back everything within the window and eats the cost of the doubt.
There are no invented numbers on this page. The one figure here is a public federal rule with a link. Every other input is your own: your lots, your suppliers, your customers. What this template gives you is the structure that turns those inputs into a trace you can stand behind.
Why lot genealogy is a P&L decision
Genealogy is the chain that connects a supplier lot you received to the finished lots it became and the customers those went to. When that chain is intact, a recall is surgical: you name the affected lots, name where they shipped, and stop. When the chain is broken, or lives across binders and separate systems, you cannot prove which finished lots are clean, so you pull the whole window. The difference between a targeted recall and a blanket one is decided long before the event, by whether the linking data was captured at the moment product moved.
There are three costs an owner should weigh, and none of them are hypothetical to a plant that has lived through a trace request.
Recall scope
The size of the pullback
Weak genealogy forces you to recall by time window instead of by lot. The cost is every clean unit you pull back with the affected ones.
Audit & access
Producing records on the clock
An auditor or regulator asks for lot records and expects them fast and sortable. A paper trace can meet neither reliably.
Customer trust
Staying on the line card
Large buyers increasingly require a fast, documented trace to keep you approved. Speed of trace has become a condition of the account.
What one-up, one-back actually means
One-up, one-back is the minimum shape of a usable trace. One-back means that for anything you hold, you can name the immediate source it came from: the supplier and their lot. One-up means that for anything you made, you can name the immediate destination it went to: the customer or the next facility. String enough one-up and one-back links together across a supply chain and you get full genealogy, but no single plant has to hold the whole chain. Each plant is only responsible for its own two links, clean and captured.
The reason plants fail a trace is almost never that they lack the information. It is that the information was never linked at the moment it existed. The supplier lot was on the pallet, but it was not tied to the internal lot. The batch was run, but which input lots went in was never recorded against the output. The genealogy has to be captured as product moves, because it cannot be reconstructed afterward from memory. That is why this is a template, not a policy: it names the exact link to capture at each point.
The three linking capture points
Genealogy is made or lost at three moments, when material moves across a boundary. Miss the link at any one of them and the chain breaks there. These three are free below. The full template of what to capture at each is behind the work email.
Link 01 · One-back
Receiving: tie every unit to its supplier lot
Captures: the source link
The moment an ingredient or component lot comes in the door. If the supplier lot is not tied to the internal lot or location here, the one-back link is gone before production ever starts.
Link 02 · The join
Consumption: tie inputs to the output lot
Captures: the genealogy join
The moment lots are consumed into a batch or run. This is the join that makes genealogy possible: which input lots went into which finished lot. Miss it and you can trace to your own door but not through your plant.
Link 03 · One-up
Pack: tie every finished lot to where it went
Captures: the destination link
The moment finished product is packed, coded, and shipped. If the finished lot is not tied to the customer or destination here, you can know a lot is affected and still not know where it went.
The template sections
Here is the shape of the full template. Each section is one of the three links plus the trace-out drill that proves they connect. The concrete fields to capture under each are below, sent to your work email or revealed here on this page.
01Link at receiving: the fields that hold the one-back tie
02Link at consumption: the fields that hold the genealogy join
03Link at pack: the fields that hold the one-up tie
04The trace-out drill: proving the three links connect on the clock
Full fields to capture at each link · behind the work email
Want the deeper platform view of how this runs live rather than on paper? See manufacturing traceability software, where the same one-up, one-back links are captured once, at the moment product moves, and a trace returns in seconds.
The full template
Get the full capture template.
You have seen the three links above. Enter your work email and the full template opens right here on this page, with the exact fields to capture at receiving, consumption, and pack, plus the trace-out drill. A copy goes to your inbox to hand to your quality lead.
Every field to capture at each of the three links, plain and specific
The trace-out drill that proves the links connect, timed
The one public rule that sets the standard a trace must now meet, with a link
Work email only. We use it to send the template and nothing else you did not ask for. Unsubscribe anytime.
Unlocked. The full template is open below, and a copy is on its way to your inbox. If you checked the box, a Harmony engineer will reach out to map it against your plant.
The full template. Capture the link at the moment product moves, not after.
Link 01 · Receiving
The fields that hold the one-back tie
Captured when an ingredient or component lot arrives. Every field here exists to answer one question later: what supplier lot is inside the unit I am holding.
Supplier and supplier lotWho it came from and their lot or batch code exactly as printed. This is the one-back link itself.
Item and descriptionWhat it is, in your own item code, so the lot maps to a part you consume.
Internal lot or license plateThe lot number or pallet ID you assign on receipt. This is what ties the supplier lot to everything downstream.
Quantity receivedAmount and unit, so consumption can be balanced against what came in.
Date and time receivedWhen it entered your control, for the timeline a trace has to reconstruct.
Storage locationWhere it was put away, so a hold can be found and pulled physically.
Receiving referencePO, ASN, or receipt number linking to the purchasing record and certificate of analysis.
Why this link matters most
If the supplier lot is not tied to your internal lot at receiving, the one-back link never existed. No amount of downstream discipline recovers it, because the pallet is put away, blended, or consumed and the tie is gone. This is the cheapest link to get right and the most expensive to miss.
Link 02 · Consumption
The fields that hold the genealogy join
Captured when lots are consumed into a batch or production run. This is the join, the record of which inputs became which output. Without it a trace stops at your own door.
Output lotThe finished or intermediate lot number this run produces. The thing every input lot links up to.
Input lots consumedEvery internal lot that went in, by lot number. This list is the genealogy join. One output, the set of inputs behind it.
Quantity of each inputHow much of each lot was drawn, so partial lots can be split across multiple outputs correctly.
Work order or batch referenceThe run identifier tying the consumption to the production record and its parameters.
Line, asset, or cellWhere it ran, so a contained problem can be scoped to the equipment involved.
Date, time, and shiftWhen it ran and who was on, for the timeline and for narrowing a suspect window.
Rework or regrind fed backAny reclaimed material returned to the run, by its own lot. The link most often lost, and the one that quietly widens a recall.
Why the join is the hard part
Receiving and pack are boundaries with a natural pause where someone scans. Consumption happens mid-run, at speed, which is exactly why the input-to-output link is the one most often left to memory or a paper batch sheet that is typed in later, if at all. A trace can only pass through your plant if this join was recorded as the run happened. Rework fed back in is the classic gap: it connects lots that otherwise look unrelated, and a trace that misses it understates the scope.
Link 03 · Pack
The fields that hold the one-up tie
Captured when finished product is packed, coded, and shipped. Every field here answers the other half of a trace: where did the affected lot go.
Finished lot and pack codeThe lot as it appears on the product, plus the pack or date code the customer will read back to you.
Quantity packedUnits or cases from this lot, so a recall can be reconciled against what was made and what remains.
Pallet or case IDsThe shipping units the lot was packed into, so a hold can be located in the warehouse or in transit.
Customer or destinationWho it shipped to, or the next facility. This is the one-up link itself.
Ship date and referenceWhen it left and the shipment, BOL, or order number tying it to the sales record.
Carrier or routeHow it moved, for reach when a destination has to be contacted quickly.
Why one-up decides the recall
Knowing a lot is affected is worthless if you cannot say where it went. The one-up link at pack is what converts a quality finding into a bounded action: these customers received these lots, contact them, hold the rest. When it is missing, you either recall from everyone in the window or you guess, and neither is a position you want to defend to a buyer or a regulator.
Section 04 · Trace-out
Proving the three links connect, on the clock
A template is only as good as the trace it produces. Run this drill on a real lot, timed, before you need it for real. The first honest attempt is the answer.
Pick a real finished lotChoose one at random, not a rehearsed one. Note the start time.
Trace backFrom the finished lot, list every input lot consumed, and from each, the supplier lot at receiving. If any step needs a phone call, that link is broken.
Trace forwardFrom a supplier lot, list every finished lot it went into, and from each, every customer it shipped to. This is the recall scope in miniature.
Produce it as a filePut the result into a sortable electronic spreadsheet. Note the finish time. That elapsed time is your real trace time.
The standard a trace is now measured against
What a trace is expected to take is no longer a matter of opinion. Under the FDA Food Traceability Rule, which implements section 204 of the Food Safety Modernization Act, covered firms must make required traceability records available to an authorized FDA representative within 24 hours of a request, and during an outbreak, recall, or other public health threat must provide the required information in an electronic sortable spreadsheet within that same window. A trace that lives in binders and separate systems can meet neither condition reliably. If your drill above ran long or ended in paper, that is the gap this template closes.
Source: 21 CFR 1.1455, paragraphs (c)(1) and (c)(3)(ii), FDA Food Traceability Rule.
Where capturing these links puts you
Capturing genealogy at the moment product moves is not a standalone project. It is the same foundation everything else on the floor stands on, and it maps onto the three phases every plant moves through. A plant still tracing on paper is at the start of Phase 1, whatever it has been sold. That is the most fixable position, because the work is known and unglamorous rather than experimental.
Phase 1
Lay the Data Foundation · Digitization
Every pen-and-paper record digitized at the station, including the three genealogy links, every software system connected, and all of the data unified into one live layer. The digital transformation starts here.
Phase 2
Production & Operations Scale
Factory operations turn proactive: live sensors and machine data, the AI scheduling board, predictive maintenance before failure, traces that return in seconds.
Phase 3
AI-Native Operations
Agents across the floor and the back office act on the live layer: quality signals, reports, copilots, and a trace an agent can run on demand. Humans approve.
Want to see the links captured once and a trace returned in seconds instead of a fire drill? That is what manufacturing traceability software does with this same template, live on your floor rather than on paper.
Rather have someone map these links against your plant?
The same walk is the first week of a Harmony pilot, on-site, with forward-deployed engineers tying your receiving, consumption, and pack records into one genealogy. Phase 1 first, because that is the order it has to happen in. See what the live layer looks like.
