Guide
FSIS Appendix A: the Cook Bible for Ready-to-Eat Meat & Poultry
FSIS Compliance Guideline Appendix A is the validated science behind every cooked ready-to-eat meat and poultry product in the United States. It specifies the time-temperature combinations that deliver a 6.5-log reduction of Salmonella in beef and pork (7-log in poultry), plus the humidity and come-up-time conditions that make those combinations actually work. Get Appendix A wrong and the lethality CCP is invalid — every lot produced under the bad schedule is potentially adulterated. This guide walks the current (2021) Appendix A, the common deviations, and what the IIC verifies on the cook record.
Start free trial Free trial, no credit card, onboard in days, not months.
Salmonella performance standard — 6.5 log beef/pork, 7 log poultry
Appendix A's anchor is the FSIS performance standard for cooked RTE meat: a 6.5-log10 reduction of Salmonella in fully-cooked beef or pork products (9 CFR 318.17/319.81), and a 7-log10 reduction in fully-cooked poultry (9 CFR 381.150). Appendix A provides validated time-temperature combinations that achieve that reduction. Any schedule shorter or cooler than Appendix A must be scientifically validated to equal the same reduction, with documented challenge studies and a process-authority letter on file.
The time-temperature tables — and the humidity requirement that gets missed
Appendix A's table A.1 pairs internal product temperatures (e.g. 145°F / 62.8°C, 155°F / 68.3°C, 160°F / 71.1°C) with minimum dwell times (e.g. 4 minutes at 145°F, 17 seconds at 158°F). What gets missed: tables A.2 and humidity. The validated combinations assume relative humidity ≥90% (or moist-heat conditions) during the lethality window. Dry oven schedules without humidity injection or a moist-heat phase do not deliver the predicted log reduction. The 2021 update made this explicit; many older plans still rely on dry-cook schedules and are technically out of compliance.
Come-up time and the 2021 update
FSIS's 2021 Appendix A revision tightened the come-up-time expectation — the time from chilled to lethality temperature. Slow come-up in low-humidity ovens can allow Salmonella to adapt thermally and resist the lethality phase. The current guideline expects come-up to be characterised and either bounded (e.g. ≤2 hours) or compensated for in the dwell. Plans citing the 1999 Appendix A often don't address come-up time and need updating.
Cook deviations and the corrective-action chain
A cook deviation (dwell too short, temperature too low, humidity below set point) is a CCP failure under 9 CFR 417.3. The corrective actions: identify the cause, fix it, evaluate the affected product, and document. The implicated product is on hold until disposition — a recook to bring it to the schedule, reformulation, diversion to non-RTE use, or condemnation. Releasing a deviation lot without a process-authority disposition is a Direct food safety NR.
Validation — Appendix A vs scientifically equivalent
Two valid paths to a lethality CCP: (1) operate within Appendix A's tables with the humidity and come-up conditions met (safe harbour); or (2) operate a schedule outside Appendix A backed by scientific validation — challenge studies (often inoculated pack studies at an accredited lab), predictive microbiology modelling, or a process-authority letter citing peer-reviewed validation. Path 2 is more work but allows shorter schedules for some products (e.g. cured/cooked sausages, fermented products) where Appendix A is conservative.
A 30-day Appendix A refresh path
Days 1–5: list all RTE cooked products and their current cook schedules. Days 6–10: map each schedule to the current (2021) Appendix A table — verify time, temperature, humidity, come-up. Days 11–15: identify gaps (humidity not recorded, come-up uncharacterised, schedule outside Appendix A without validation). Days 16–25: instrument oven humidity capture, update SOPs, and rewrite the lethality CCP records. Days 26–30: validation review with the process authority, IIC walk-through and update the HACCP plan reassessment record.
Standards covered in this guide
Each standard, retailer code or assurance scheme referenced above has its own deep-dive page with scope, audit detail and common pitfalls.
Where this lives in V5 Ultimate
The clauses above aren't theoretical — every one maps to a shipped module and an industry profile. Jump to the parts of the product that turn this guide into evidence on a Monday morning.
Modules that do the work
Industries this hits hardest
Frequently asked
What's the difference between Appendix A 1999 and 2021?
The 2021 update made humidity and come-up time explicit requirements rather than implicit assumptions, tightened the moist-heat expectation, and updated the validated table to current science. Schedules citing the 1999 version remain conservative for time-temperature but often miss the humidity and come-up requirements that the 2021 version makes explicit.
Do I have to use Appendix A?
No — but if you deviate, you must scientifically validate that your schedule achieves the 6.5-log (beef/pork) or 7-log (poultry) Salmonella reduction. Validation is usually an inoculated-pack challenge study at an accredited lab plus a process-authority letter. Appendix A is the safe harbour; most plants use it directly.
How is humidity recorded?
Either by a relative-humidity probe inside the oven logging continuously through the lethality phase, or by a validated moist-heat protocol (steam injection at a documented set point and duration). The cook record should show the humidity profile alongside time-temperature, not just the air temperature.
What happens to a deviation lot?
It goes on hold. Disposition options under 9 CFR 417.3: recook to the Appendix A schedule, reformulation, diversion to a non-RTE use (cooked-only-as-an-ingredient), or condemnation. A process-authority must sign the disposition; releasing as RTE without re-meeting the lethality is a Direct food safety NR and a potential recall.
See it on your shop floor.
Free trial, no credit card, onboard in days, not months.
Related reading
Spot something off? .