A HACCP plan is written in twelve steps, and the order matters. The first five are preparation: gather the people, describe the product, say who eats it, draw the process, and walk the drawing on the floor. The other seven are the HACCP principles: analyze the hazards, find the critical control points, set a limit for each, decide how it's monitored, decide what happens when it's missed, verify, and keep records. Most bad plans are bad for one reason: someone started at step seven, filling in a template's CCP table, without the five steps that tell you what your CCPs are. A plan for a simple product is a few pages. Below is each step with what you do and what you end up holding, a worked example for a made-up soup maker, and a file to work in.
The short version
- Don't start with a template's CCP table. Start with your own process, on paper.
- A flow diagram you've walked on the floor is the foundation.
- Hazard analysis first. CCPs come out of it; you don't pick them.
- A critical limit is a number with a source.
- Decide the corrective action before the bad day.
- A plan without records isn't a plan. Keep the forms short enough to fill in.
- TaroStack keeps the plan's records with the batch they belong to. More below.
Steps 1 to 5: prepare
| Step | What you do | What you end up with |
|---|---|---|
| 1 Gather the team | Name who writes the plan and who knows the process | A list of names and roles |
| 2 Describe the product | What it is, what's in it, packing, storage, shelf life | A product description |
| 3 Say who eats it, and how | Ready to eat or cooked first? The public, or people at higher risk? | An intended use statement |
| 4 Draw the flow diagram | Every step, receiving to delivery, as boxes and arrows | A flow diagram |
| 5 Walk it | Take the diagram onto the floor during production and correct it | A verified diagram, signed and dated |
The team can be two people. What matters is that one of them does the job every day. The cook knows the soup sometimes waits in the kettle; the owner doesn't.
The description decides the hazards. "Refrigerated, ready to reheat, seven days" is a different plan from "frozen, cook before eating".
Walking the diagram is the step people skip, and the one that finds things. In the example, the walk found that on busy days soup sat in the kettle before it was filled. A box was added, and that box turned out to matter. How to draw one is in HACCP flow diagram example.
Step 6: analyze the hazards
Go down the flow diagram one box at a time. At each, ask what could get into the food or grow in it.
| Kind | Examples |
|---|---|
| Biological | Salmonella on raw chicken; Listeria in a cold wet room; spores that survive cooking and grow as food cools |
| Chemical | Allergens (the commonest); cleaning chemicals; too much of an additive |
| Physical | Metal, glass, bone, hard plastic |
For each hazard write three things: is it reasonably likely to happen here, why or why not, and what controls it. A hazard controlled by an everyday program (handwashing, cleaning, pest control) is noted and left to that program: see prerequisite programs for HACCP. What's left is the short list that needs a control point. A table for this is in hazard analysis template.
Step 7: find the critical control points
A CCP is a step where a control is essential and nothing later will catch a failure. Cooking is one if nothing is cooked again. Receiving usually isn't, because cooking comes after. For the soup: cook, chill, label, cold storage. Four. A plan with fifteen CCPs has confused control points with good practice, and none of the fifteen will be monitored properly.
Step 8: set critical limits
A limit is a number, measured, with a source: a regulation, a food code, a process authority's letter, a published study.
| CCP | Critical limit | Source |
|---|---|---|
| Cook | 165°F | FDA Food Code |
| Chill | 135°F to 70°F in 2 hours; to 41°F in 6 in all | FDA Food Code |
| Label | Matches the recipe's allergens | Allergen labeling law |
| Cold storage | 41°F or below | FDA Food Code |
"Cook thoroughly" isn't a limit. Common ones are collected in critical limits for CCPs.
Steps 9 and 10: monitoring and corrective action
Monitoring answers four questions for each CCP: what is measured, how, how often, and by whom. "Probe each kettle, by the cook" is a monitoring procedure. "Check temperatures" isn't.
Corrective action is decided now, not on the day. It has two halves: what happens to the product, and what happens about the cause.
| A limit is missed | The product | The cause |
|---|---|---|
| Chill: 104°F at 2 hours | Reheat to 165°F once and chill faster, or discard | The pot was too deep: use shallow pans |
| Label: wrong label on a run | Hold, relabel; recall any that left | One product on the bench at a time |
Steps 11 and 12: verify, and keep records
Verification is checking the checker: thermometers calibrated, someone reviewing and signing the logs, the monitoring watched now and then, and the whole plan reassessed at least once a year and whenever the product, process or equipment changes. Proving the limits themselves work is validation: see HACCP validation template.
Records are made at the time, with the real reading and initials. Design the forms last, and make them short: a log nobody fills in is worse than a simpler one that's complete. Examples are in HACCP record keeping form example, and how long to keep them in how long should HACCP records be kept.
Which rule you're writing to
The twelve steps are the same everywhere. What the finished plan must contain, and who must write it, depends on the rule that covers you: USDA's for meat and poultry, FDA's for seafood and juice, FDA's food safety plan for most other makers, your health department's code for a restaurant with a special process. Some require the writer to be trained. Find your row in who needs a HACCP plan before you start, and read that rule's list of contents. This is general information, not legal advice.
Get the worksheet
Download the twelve steps worksheet. Each step with what you do, what you end up with, and the soup maker's example beside it. Replace the last column with your own. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
Writing the plan is a week's work, once. Step 12 is every day for ever. The cooking log, the chilling log, the label log and the cooler log are four clipboards, and none of them says which chicken went into which kettle or which shop got the tubs. When step 10 happens for real (a recalled ingredient, a complaint), the plan is in the binder and the answers are scattered.
How TaroStack does it
TaroStack keeps step 12's records attached to the batch.
Each kettle is a batch. Recording it takes the ingredients from stock and notes which lots were consumed, automatically.
Your monitoring is fields on the batch record: cooking temperature, the two chilling readings, label checked, initials, and a sign-off for the weekly review. The form prints with your own checklist.
A corrective action can be a hold. The batch stays out of what you can sell until someone releases it.
Allergens on Growth. With allergen tracking on, a batch can't start if its label leaves out an allergen its ingredients contain.
One report for a recall, and a timed, logged drill for verification.
| The step | Binder and clipboards | In TaroStack |
|---|---|---|
| 9 Monitoring | Four log sheets | Fields on each batch |
| 10 Corrective action: hold the product | A sign | On hold: not for sale |
| 11 Verification: review and sign | Initials on a sheet | A sign-off on the batch record |
| 12 Records: which lots, which customers | Batch sheets and invoices | On the batch; one report |
TaroStack doesn't write your HACCP plan or decide your limits. Lots, batches and recalls are on every plan, from $9.99 a month; allergen tracking starts at Growth, $39 a month. 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.
