The HACCP plan summary is the page of a HACCP plan that people actually use. Everything before it, the product description, the flow diagram and the hazard analysis, is the reasoning. The summary is the result: a table with one row for each critical control point and seven columns. The HACCP guidelines published on FDA's site list what it holds: the hazard of concern, the critical limits, monitoring, corrective actions, verification and records, with a note of who does each and how often. A cook can work from it, a supervisor can check against it, and an auditor can read it in a minute. Below is each column and what belongs in it, an example row built on the guidelines' own example, and the file.
The short version
- One row for each critical control point, and only for those.
- Seven columns: CCP, hazard, critical limit, monitoring, corrective action, verification, records.
- Monitoring says what, how, how often and who.
- A critical limit is a number you can measure, taken from a rule or a validated process.
- The corrective action covers the product as well as the cause.
- It comes after the hazard analysis, not instead of it.
- TaroStack keeps the batch and lot records the last column points to. More below.
Where the table comes from
The HACCP Principles & Application Guidelines set out seven principles. Under the seventh, record keeping, they list what a HACCP system's records should include, and one item is a "HACCP Plan Summary Table that includes information for":
| The guidelines' list | Column in the table |
|---|---|
| Steps in the process that are CCPs | CCP |
| The hazard(s) of concern | Hazards |
| Critical limits | Critical limit(s) |
| Monitoring | Monitoring |
| Corrective actions | Corrective actions |
| Verification procedures and schedule | Verification |
| Record-keeping procedures | Records |
For monitoring, corrective actions, verification and records, the guidelines add that "a brief summary of position responsible for performing the activity and the procedures and frequency should be provided."
These are guidelines, first adopted in 1997. The rules that bind you depend on what you make. For meat and poultry, 9 CFR 417.2 says what a HACCP plan must contain. Who needs a plan at all is in who needs a HACCP plan.
An example row
The hazard and the critical limit here are the guidelines' own example, cooked beef patties. The other cells are made up to show what a filled-in row looks like.
| Column | Example |
|---|---|
| CCP | Cooking |
| Hazard | Enteric pathogens, such as Salmonella and verotoxigenic E. coli |
| Critical limit | A minimum internal temperature of 155°F for 16 seconds |
| Monitoring | What: internal temperature of patties leaving the oven. How: a calibrated probe thermometer. How often: five patties every 30 minutes. Who: the oven operator |
| Corrective action | Hold everything cooked since the last good check. Recook or discard it. Find and fix the cause, and record what was done |
| Verification | The supervisor reviews the cooking log daily. The thermometer is checked each shift |
| Records | Cooking log, corrective action log, thermometer check log |
Don't copy the 155°F. It's a figure from the guidelines' illustration. Your critical limit comes from the rule, guidance or process authority that applies to your product today: see critical limits for CCPs.
Column by column
CCP. Only the steps your hazard analysis found to be critical. The guidelines define a critical control point as a step at which control can be applied and is essential to prevent or eliminate a food safety hazard or reduce it to an acceptable level. A plan with fifteen rows may have mistaken good practice for CCPs. Cleaning, pest control and training belong in prerequisite programs.
Hazard. Name it: Salmonella, metal fragments, undeclared milk. "Bacteria" isn't an entry.
Critical limit. A number that separates safe from not safe, that someone can measure while the product is still in front of them. The guidelines' example shows two ways to set it for the same patty: limits on oven temperature, belt speed and patty thickness in one plant, or the internal temperature itself in another.
Monitoring. Four things: what is measured, how, how often, and who. "Check temperature" answers none of them.
Corrective action. Written before it's needed. It has to say what happens to the product made since the last good reading, as well as how the cause is fixed.
Verification. The checks on the checking: a daily review of the log, the thermometer's own check, and a periodic look at whether the plan still fits the process. See HACCP validation template.
Records. The names of the logs where the proof is. If a row lists a log that doesn't exist, the plan describes a plant you don't have. Forms are in HACCP record keeping form example.
What comes before it
The summary is the last table, not the first. The guidelines show the one that comes before, the hazard analysis summary, with these columns: step, potential hazards, justification, whether the hazard is addressed in the plan, and control measures. Each "yes" there that turns out to be a critical control point becomes a row here. The whole sequence is in how to write a HACCP plan, with a blank in hazard analysis template.
Get the table
Download the HACCP plan summary table. Two sheets and a read-me: the seven-column summary with the example row and room for yours, and the hazard analysis table that comes before it. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
The table is one page, and it promises a lot of paper. Every row names logs, and every log has to exist, filled in, for every day you ran. The corrective action says "hold everything since the last good check". To do that you have to know what was made since then and where it is now. On a line that packs into cases and ships the same afternoon, that's a question about lots, and the cooking log can't answer it.
How TaroStack does it
TaroStack keeps the records that sit behind the last column.
Each batch is a lot, with the time it was made and what went into it.
Batch records carry your own checklist fields, so a check your plan requires is recorded with the batch it belongs to.
A lot can be put on hold while a corrective action is decided.
What ships is recorded by lot, so "where is it now" has an answer.
Every lot is traced from the supplier's lot to the customers that got it.
| The plan says | On paper | In TaroStack |
|---|---|---|
| Record the check with the batch | A separate log sheet | A field on the batch |
| Hold product since the last good check | Find the pallets | Put the lots on hold |
| Know where affected product went | Shipping papers | The recall report |
| Keep records for each lot | Binders | With the lot |
TaroStack doesn't write your HACCP plan, set critical limits or take temperatures. It keeps the records. Lots, batches, holds and the recall report 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.
