A traceability procedure is the written version of something you may already do: how each delivery gets a lot number, how a batch record ties those lots to what you made, how a shipping record ties what you made to who received it, and how you test that the chain holds. Auditors and wholesale buyers ask for it in writing because a procedure in someone's head leaves with that person. It doesn't need to be long. It needs to be true: an auditor reads the procedure, then picks a bag off the shelf and checks the records against what you wrote. Below are eleven sections with what to write in each, an example for a made-up granola maker, the trace exercise that proves it, and the file.
The short version
- Write what you actually do, not what sounds thorough.
- Three records carry it: receiving, the batch record, and shipping.
- Every delivery has a lot number. If the supplier gives none, assign one.
- One batch, one finished lot, with the code printed on every unit and case.
- Test it both ways: a finished lot back to ingredients, an ingredient lot forward to customers.
- Time the test and account for the whole quantity.
- TaroStack keeps the three records linked and logs timed drills. More below.
The eleven sections
| Section | What to write |
|---|---|
| 1. Purpose | Why the procedure exists, in a sentence |
| 2. Scope | The products, ingredients, packaging and sites it covers |
| 3. Who does what | A named role for each record, and a deputy |
| 4. Lots coming in | How each delivery is identified |
| 5. Lots we make | How a finished lot is defined and coded |
| 6. Production record | What links ingredients to a finished lot |
| 7. Shipping record | What links a finished lot to a customer |
| 8. Rework and returns | How reused or returned product is traced |
| 9. Trace exercise | How often you test, in both directions, and the target |
| 10. Records kept | Where, and for how long |
| 11. Review | When the procedure is re-read, and by whom |
Your audit standard, your buyer or the law may set some of these for you: how long records are kept, how often you test, how fast a trace must be. Read what applies to you and write those numbers in. The ones in the example below are that maker's own.
The three links, in the example's words
Lots coming in (section 4). "The supplier's lot number is recorded at receiving with the date, supplier, item and quantity. If a delivery has no lot number, we assign one: the date received and the supplier's initials."
The second sentence is easy to leave out. Bulk oats from a local mill may arrive with no code at all. A lot you assign yourself is as good as the supplier's, so long as it's written on the sack and in the record.
Lots we make (sections 5 and 6). "One batch is one lot. The code is the Julian date and the batch of the day: 26322-2 is the second batch on day 322 of 2026." The batch record then lists the lot and quantity of every ingredient and every bag used. Packaging that touches food is in scope: a recalled bag is a recall. Coding is covered in julian date code format and how to create lot numbers.
Shipping (section 7). "Each invoice or delivery record shows the finished lot codes shipped, the quantity, the customer and the date." This is the link to check first. An invoice that says "4 cases granola" with no lot means a recall goes to every customer who bought granola that month.
Rework (section 8) is the trap. Broken clusters from Tuesday's batch stirred into Thursday's carry Tuesday's ingredient lots with them. Record rework as an ingredient, with its original lot code.
The trace exercise
Section 9 is where the procedure is proved. Pick a lot and trace it against the clock.
| Example | |
|---|---|
| Date | Nov 9 |
| Lot traced | Finished lot 26301-1 |
| Direction | Back to ingredients, then forward to customers |
| Minutes taken | 95 |
| Quantity made | 480 bags |
| Quantity accounted for | 476 bags |
| Accounted for | 99.2% |
| Gap found | Four sample bags given out at a market, not recorded |
Two results matter. Time: 95 minutes against this maker's own target of two hours. Quantity: 476 of 480 bags found in shipping records, stock and write-offs. The four that weren't had gone out as samples with nothing written down. That's a real gap, the exercise found it, and the fix is a line in the procedure: samples are recorded as an adjustment, with the lot.
Do it in both directions. Back answers "what went into this?" Forward answers "who has it?" A worked exercise is in food mock recall example and mock recall and traceability exercise.
What this isn't
A traceability procedure says how you keep the chain. What you do when something has gone wrong is a recall plan: see recall plan example. They're separate documents. A sheet for the records themselves is in lot tracking spreadsheet.
Get the template
Download the traceability procedure template. Two sheets and a read-me: the eleven sections with what to write and the granola maker's example beside each, and a log for trace exercises. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. Replace the example with what you do.
Where this stops working
The procedure is two pages and it's easy to write. Keeping it true is the work. It says every batch record lists every ingredient lot. On a busy Thursday the batch sheet says "oats" and nothing else, and the procedure is now describing a business that doesn't exist. The 95 minutes in the exercise was one person with a folder of batch sheets and a stack of invoices. With three times the customers it won't be 95 minutes.
How TaroStack does it
TaroStack keeps the three links the procedure describes, as part of the work.
Receiving records each delivery's lot, with its supplier, date and quantity. Scanning a supplier's GS1-128 case label fills in the lot and the use-by date.
A batch notes the lots it used, automatically. Nobody writes "oats".
What ships is recorded by lot, against the customer and the order.
Every lot is traced from the supplier's lot to the customers that got it. The recall report is one screen.
Traceability drills are timed and logged, so section 9 has a date and the minutes it took.
| The procedure says | On paper | In TaroStack |
|---|---|---|
| Every delivery has a lot | If someone wrote it | Recorded at receiving |
| The batch record lists every lot used | If someone wrote it | Noted by the batch itself |
| Shipping records show the lot | If the invoice has a line for it | Recorded with what ships |
| We test twice a year | A date in a binder | A timed drill, logged |
TaroStack doesn't write your procedure or pass an audit for you. It keeps the records the procedure promises. Lots, batches, the recall report and drills are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
