FSMA 204 traceability comes down to one deliverable: when FDA asks, you hand over an electronic sortable spreadsheet covering the foods and dates they name, within 24 hours. The record that makes that possible is not a report you run at the end. It is a lot code that stays with the food through every step in your plant, with a short list of facts recorded at each point where food is received, made into something else, or shipped out. None of what follows is legal advice. The rule text and a compliance professional govern what applies to you. I spent a morning this spring on a soft cheese line an hour south of Atlanta. The quality manager had the binder, the receiving logs, the batch sheets, all of it. She was not worried about having the records. She was worried about the Saturday she would get the call, because the person who knows which tote fed which vat on a short-staffed second shift does not work weekends, and that fact is only in his head. That is the problem. Almost every plant I talk to has the data. Very few can put it in one sortable place without someone assembling it by hand. What FSMA 204 traceability actually asks for FSMA 204 is the FDA food traceability rule written under section 204 of the Food Safety Modernization Act, and it applies to foods on the Food Traceability List. Three pieces, in plain terms. A list. The rule applies to foods on the Food Traceability List. Leafy greens, soft and semi-soft cheeses, shell eggs, nut butters, certain seafood, fresh-cut fruits and vegetables, ready-to-eat deli salads. If you make, pack, or hold one of those, the rule applies to you, subject to the exemptions it lists. Check those against your own products. Events. At specific moments the rule calls critical tracking events, you keep records. For a plant, the ones that matter most are receiving, transformation, and shipping. Upstream there are others: harvesting, cooling, initial packing, first land-based receiving for seafood. Facts. At each of those events you keep a defined set of data the rule calls key data elements. The traceability lot code and where it came from. The product description. The quantity and unit of measure. The location that shipped and the location that received. The date. The reference document type and number that ties the entry back to a real document in your system. Plus a written traceability plan that says how you assign lot codes and who to call. That is FSMA 204 compliance in operational terms. The compliance date has moved once already, so confirm the current one against the rule rather than against the last webinar you sat through. The traceability lot code is where plants get stuck Everything depends on one field. A lot code gets created when a lot gets created, which in a plant usually means transformation: you took in four supplier lots and produced something that is none of them. The new thing gets a new code. The rule wants the link between the new code and the four that went into it. Most plants have both halves. The receiving side is in the ERP because somebody has to pay for the ingredients. The output side is in the production record because somebody has to report yield. The link between them is on a batch sheet, and often only in the head of the operator who wrote it. That is survivable right up to the moment the request is for eleven days of production across two shifts, and it has to arrive as one spreadsheet you can sort by lot code. Then the link has to exist as data, not as something one person remembers. The 24-hour drill you can run this week Testing your FSMA 204 traceability record does not need a project or a budget. It needs one afternoon and one awkward lot. Pick the lot. One listed product, made last month, on a day with something wrong in it: a rework, a split pallet, a supplier substitution, a line changeover mid-batch. Not your clean lot. Your ugly one. Start a clock. An actual timer. The number is the point of the exercise. Build the columns. For every receiving, transformation, and shipping event that lot touched: traceability lot code, lot code source, product description, quantity and unit, location, date, reference document type and number. Mark every manual step. Every time somebody has to ask another person, open a binder, retype a number, or make a judgment call about what a field means, put a note in the row. Stop the clock and read your notes. The elapsed time tells you where you stand. The notes are your project plan, in priority order, written by your own plant. The manual steps are what the drill tells you, not the elapsed hours. A plant that takes six hours because two people were in a meeting is fine. A plant that takes ninety minutes but needed one specific person to interpret a batch sheet has a problem the clock did not show, because that person will eventually be on vacation. Why a spreadsheet template is not enough Anyone can build a spreadsheet template. The hard part is that a template assumes your systems already agree on what a lot is. Your operation runs on real things and real actions. Totes, vats, pallets, cases, lots. Receive, blend, cook, pack, hold, ship. When a lot exists in your records as a lot, with its inputs and outputs attached, the trace is one search. When it only exists as rows that a person has to interpret, the trace is a research project, and 24 hours is not enough time for research. Why the 24-hour deadline is not the real risk The 24 hours is not the risk. Your customers move faster than FDA does. A retailer who hears there may be a problem with your product will make a decision about your product long before your records are due, and the size of what they pull off the shelf depends entirely on how precisely you can say what is affected. Precision is what matters. A plant that can name four lots pulls four lots. A plant that can only name a production date pulls everything. Same food, same event, same rule. Different record.