Before FSMA 204 asks for your records, it asks for your plan

Most of FSMA 204 is a data problem. Lot codes moving between companies, key data elements attached to events, records that have to line up across a supply chain you don't control. That part takes systems, and time, and probably a few arguments with a co-packer.

One part isn't a data problem. It's a document. And it's the piece of the rule you could finish before the end of the week.

The Food Traceability Rule requires covered businesses to establish and maintain a written traceability plan (21 CFR 1.1315). Five components, all of them describing how your operation already works. No new software required to write it. No lot codes to redesign. It's a description of your own practices, on paper, signed and dated.

It also happens to be the document that reveals whether the rest of your compliance story holds together. Writing it honestly is a diagnostic.

01First: are you actually covered by FSMA 204?

The rule applies to businesses that manufacture, process, pack, or hold foods on the Food Traceability List: 23 food categories including leafy greens, fresh-cut produce, shell eggs, nut butters, soft cheeses, and a range of seafood. If nothing you touch is on that list, none of this applies to you.

Check before you write. FDA maintains an interactive exemption tool that walks you through it with yes/no questions, and the list itself is published on the Food Traceability Final Rule page. Both are linked at the bottom of this post.

And yes, the compliance date moved to July 20, 2028. We wrote about why that's runway, not relief. The plan is the part of the rule that doesn't benefit from waiting, because it costs you an afternoon.

02The five parts of a traceability plan

Part one: recordkeeping procedures, format, and location

A description of your recordkeeping procedures, including the format and location of the records.

This is the first sentence most producers write and then stare at. Because the honest answer is often: CCP logs in a binder by the fill station, ingredient CoAs in a Google Drive folder, receiving records in a spreadsheet Jill maintains, shipping records in the accounting system.

That's a real answer. It's also a written record of your own fragility. Four locations, four formats, four ways for a record to go missing, and you've now documented all of it for an inspector.

Part two: how you identify Food Traceability List foods

A procedure for recognizing which of the foods you make, buy, or store are on the Food Traceability List.

FDA's own example from a distribution center shows what this looks like done well. Their plan doesn't say "we monitor the FTL." It says they review all new products against FDA's Food Traceability List before adding them to their product lists, and flag identified FTL foods in their warehouse management system. A trigger, a comparison, a flag. Specific enough that someone new could run it.

Part three: how you assign traceability lot codes

Your method for assigning lot codes, where that applies to your operation.

Note the qualifier. Traceability lot codes get assigned at specific moments: initially packing a raw agricultural commodity, first land-based receiving of seafood, or transforming an FTL food. If you're turning ingredients into a finished product, that's you.

The FDA example again gets concrete, describing a code built from the supplier's name or number, the purchase order number, the SKU, and the date of receipt. Boring. Reproducible. Exactly right.

Part four: a named point of contact

A statement identifying a person to contact with questions about your records.

One line. A name, a title, a phone number. FDA's example plan reads like a business card entry. Don't overthink this one, but do put a real person there, and update it when they leave.

Part five: farm maps, if you grow or raise

If you're a grower, a map showing field locations with geographic coordinates. Eggs are excluded. If you don't farm, write "not applicable" and move on.

03What FDA's example traceability plans get right

In March 2025, FDA published example traceability plans for processors, distribution centers, seafood facilities, and aquaculture farms. They take about twenty minutes to read, and the lesson in them is consistent.

The good examples aren't longer. They're more specific. They name systems. They name people. They describe the trigger that starts a procedure and the artifact it produces. Where the rule says "procedures for maintaining records," the example says which gateway an advance shipping notice goes to and which department gets the email if it doesn't.

A plan that restates the regulation back at the regulator proves nothing. A plan that describes your actual Tuesday proves everything.

04The two clauses people miss

Your plan has to stay current. The rule requires you to update it as needed so it reflects your current practices. A plan written in 2026 that describes a workflow you abandoned in 2027 does nothing but document the distance between what you say and what you do.

You also have to keep the old versions. Previous plans must be retained for 2 years after you update. So don't overwrite it. Version it.

Separately, traceability records themselves are held for 2 years from the date you created or obtained them.

05Where the plan meets the 24-hour sortable spreadsheet rule

Part one matters more than it looks, and here's the reason.

When FDA requests traceability information during an outbreak or a recall, records have to be available within 24 hours of the request. For the traceability information specifically, that generally means an electronic sortable spreadsheet, inside that same 24 hours (21 CFR 1.1455). Smaller entities get alternative formats: farms averaging under $250,000 in annual sales, retail establishments and restaurants under $1 million, and other persons under $1 million.

Now go back and read your own part one out loud. Binder by the fill station, Drive folder, Jill's spreadsheet, accounting system.

Twenty-four hours is not very long to merge four systems into one sortable file while also managing the actual recall. That's the gap the plan exposes, and it isn't hypothetical. You just wrote it down about yourself.

This is the practical case against running compliance on spreadsheets. Plenty of producers keep careful ones. The problem is that a spreadsheet can hold records without proving the chain, and under time pressure the reconstruction work lands on the person who has the least room for it. We've written about tracing an ingredient lot back to its supplier and tracing a flagged lot forward to buyers. The 24-hour clock demands both directions, from one place.

06How to write your traceability plan this week

An afternoon, honestly spent:

1. Confirm whether anything you handle is on the Food Traceability List.
2. Walk your floor and write down where every record actually lives, in what format, and who maintains it. Don't clean it up. Write the real answer.
3. Write your FTL identification procedure as a trigger and an action, not an intention.
4. Document your lot code format, the actual string, with an example.
5. Name your point of contact.
6. Date it, version it, and set a calendar reminder to review it.

Then read part one again and ask whether you'd want to defend it with a 24-hour clock running.

If the answer is no, you've learned the most useful thing this document has to teach, and you have until July 2028 to change the answer. That's plenty of time, right up until it isn't.

References

• 21 CFR 1.1315, eCFR Title 21, Part 1, Subpart S. Traceability plan requirements: the five required components, the obligation to keep the plan current, and 2-year retention of superseded plans.
• 21 CFR 1.1455, eCFR Title 21, Part 1, Subpart S. Records maintenance and availability: acceptable record formats, 24-hour availability on FDA request, the electronic sortable spreadsheet requirement, alternative formats for smaller entities, and 2-year record retention.
• FDA, FSMA Final Rule on Requirements for Additional Traceability Records for Certain Foods. Compliance date of July 20, 2028; Food Traceability List; interactive exemption tool.
• FDA, The FDA Food Traceability Rule At-A-Glance, March 2025.
• FDA, Traceability Plan Example (distribution center), March 2025.
• Federal Register, Requirements for Additional Traceability Records for Certain Foods: Compliance Date Extension, August 7, 2025.