A frozen vegetable plant has one hot step and a long cold, wet line after it, and the plan is about both. Blanching can kill what came in from the field, if its time and temperature have been shown to do that for your vegetable and cut. Then the vegetables travel through cooling water, over belts and into a freezer, and that stretch is where Listeria lives: it likes cold, damp equipment, and freezing doesn't kill it. So the plan has a control point at the blancher, sanitation and swabbing for everything after it, metal detection, and one decision that shapes the rest: is your product ready to eat? Customers do eat frozen vegetables without cooking them. Below are the hazards, the points, a week's log, and a worksheet.
The short version
- Blanching is a kill step only if it's been validated for your vegetable, cut, time and temperature.
- Everything after the blancher is a clean zone. Treat it as one.
- Freezing stops Listeria growing. It doesn't kill it.
- Swab the line for Listeria on a schedule, and act on a positive.
- Decide whether the bag is ready to eat, and make the label say so.
- TaroStack keeps each run as a lot, with its checks and its customers. More below.
The hazards
| Hazard | Where it comes from | Where it's controlled |
|---|---|---|
| Salmonella, E. coli, Listeria on raw vegetables | Field, harvest, transport | Approved growers; blanching |
| Listeria in the plant | Drains, belts, flumes and freezers after the blancher | Sanitation; separation of raw and blanched sides; swabbing |
| Growth while warm | Vegetables waiting between blancher and freezer | Fast cooling and freezing |
| Stones, wood, metal | Field and equipment | Washing, sorting, metal detection |
| Undeclared allergens | Sauces, seasonings or breading on the same line | Changeover cleaning; label check |
The control points
A made-up plant freezing cut corn and green beans. Its limits are its own.
| CCP | Limit | Checked | If it's missed |
|---|---|---|---|
| 1 Blanching | Water at 190°F or above, belt speed giving at least 2 minutes | Temperature and belt speed, each 30 minutes | Product since the last good check held; blanched again or destroyed |
| 2 Cooling water | Antimicrobial at its label strength; water changed on schedule | Each hour | Water remade; product since the last check held |
| 3 Freezing | Core at 0°F or below when it leaves the freezer | Each hour | Held and refrozen, or destroyed if it was warm for long |
| 4 Metal detection | Detector on and rejecting its test pieces | Start, hourly, each product change, end | Everything since the last good check held and re-passed |
Validating the blanch. A blancher is usually set to stop enzymes so the vegetables keep their color. Whether that same setting kills pathogens depends on the vegetable, the size of the cut and how thick the bed is on the belt. Have a process authority or your extension service confirm your time and temperature, and keep the letter. Until then the blanch is a quality step, and the plan can't count on it.
After the blancher. This is the part that makes or breaks a frozen vegetable plan. People and equipment don't cross from the raw side to the blanched side without a change of coat, a boot wash and clean hands. Belts, flumes and the freezer are cleaned and sanitized on a schedule that takes them apart. Drains get attention every day. The program is in sanitation SOP template.
Swabbing. FDA's rule asks for environmental monitoring where a pathogen in the plant could contaminate a ready-to-eat food, under a written procedure that names the organism, the sites, how many and how often, the lab, and what happens on a positive. Swab food-contact surfaces and the floors, drains and frames near them. Looking hard and finding it is the system working. A program is in environmental monitoring program template.
Ready to eat, or not. If your label says "cook thoroughly" and gives instructions, those instructions are part of your safety case, and they should be ones that actually get the vegetable hot enough. They don't excuse the plant from keeping Listeria out. If you sell vegetables people will plainly eat thawed, such as peas, corn or edamame for salads, plan for them as ready to eat.
A week's log
| Day | Check | Reading | Limit | OK? |
|---|---|---|---|---|
| Mon 9:00 | Blancher, corn | 194°F, 2 min 10 s | 190°F, 2 minutes | Yes |
| Mon 9:30 | Blancher, corn | 186°F, 2 min 10 s | 190°F, 2 minutes | NO: act |
| Mon 10:00 | Freezer exit, core | −4°F | 0°F or below | Yes |
| Wed | Swabs, 10 sites, Listeria species | 1 positive: drain by the freezer infeed | None on food-contact surfaces | Act |
| Fri | Re-swab, the drain and 5 sites around it | All negative | Yes |
At 9:30 on Monday the blancher read 186°F: a steam valve was sticking. The corn that had gone through since 9:00 was held under its code and run through again once the water was back at 194°F. Wednesday's positive was a floor drain, not a surface that touches food. The drain and the area were stripped, scrubbed and sanitized, and the re-swabs on Friday were clean. No product was held, because nothing that touches food had tested positive.
This is general information, not legal advice. The detector's checks are in metal detector CCP, and writing the plan in how to write a HACCP plan.
Get the worksheet
Download the frozen vegetable HACCP worksheet. Three sheets and a read-me: the hazard analysis from the field to the freezer, the plan with its four control points, and a monitoring log. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
A swab from the packing belt comes back positive on a Thursday. The belt was last swabbed clean nine days ago. Everything packed on that line since then is in question: which codes, how many cases of each, and which of them are in your freezer and which in a distributor's? The swab log has the date. It doesn't have the cases.
How TaroStack does it
TaroStack ties each day's run to a code, and each code to where it went.
Each run is a batch with a lot code, and lot labels print with it. Your checks are fields on the batch record: blancher temperature, belt speed, freezer exit, detector check, initials.
Put lots on hold while a result is pending, and they're kept out of what you can sell.
The batch notes which grower's lots it used, automatically.
One report for a recall: which customers got each lot, how many cases, and what's still in your freezer. Starting a recall holds the rest.
| The positive swab | Paper | In TaroStack |
|---|---|---|
| Codes packed since the last clean swab | The production diary | The batches between two dates |
| Cases still in the freezer | Count the racks | Stock by lot |
| Keeping them from shipping | Tape across the bay | On hold |
| Who has the rest | Bills of lading | One report |
TaroStack doesn't swab, test or validate a blanch. Recipes, batches, lots and recalls are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes, with allergen tracking). 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.
