Fresh-cut produce is eaten raw, so the plan has no kill step to lean on. Washing takes off soil and lowers what's on the surface. It doesn't make a contaminated head of lettuce safe. A fresh-cut plan is built from four things that each do part of the job. Growers you've approved, because safety starts in the field. Wash water with a measured sanitizer, which keeps the water from spreading one bad head through the whole batch. Cold: once leafy greens, tomatoes or melons are cut, the FDA Food Code treats them as food that needs temperature control, held at 41°F or below. And a clean, cold cutting room that's swabbed for Listeria, because the product goes out ready to eat. Below are the hazards, the points, a week's log, and a worksheet.
The short version
- No kill step. Each control only lowers the risk, so all of them have to work.
- Buy from approved growers, and record every lot.
- Sanitizer in the wash water at its label strength, measured through the run.
- Cut leafy greens, cut tomatoes and cut melons stay at 41°F or below.
- Swab the cutting room for Listeria on a schedule.
- TaroStack records which grower's lot went into which bag, with a date on each. More below.
The hazards
| Hazard | Where it comes from | Where it's controlled |
|---|---|---|
| E. coli, Salmonella, Listeria on produce | Irrigation water, animals, soil, harvest crews | Approved growers; washing lowers it |
| Spread in the wash | One contaminated head in a tank of water | Sanitizer strength; water changed on schedule |
| Listeria in the plant | Drains, cutters, belts, spinners | Sanitation; swabbing |
| Growth after cutting | Cut surfaces at warm temperatures | 41°F or below from cutting to the customer |
| Blade fragments, stones | Cutters; the field | Blade checks; sorting; metal detection |
| Undeclared allergens | Dressings, nuts or cheese in salad kits | Label check; changeover cleaning |
Whole, uncut produce is a different product with different rules. The moment it's cut, it's a ready-to-eat food made in a plant.
The control points
A made-up processor cutting romaine, melon and salad mixes for restaurants. Its limits are its own where they go beyond the code.
| CCP | Limit | Checked | If it's missed |
|---|---|---|---|
| 1 Receiving | From an approved grower; lot recorded; cut or chilled product at 41°F or below | Each delivery | Refused, or held |
| 2 Wash water | Sanitizer at the strength on its label, measured with its test kit; water changed on schedule | Every 30 minutes | Water corrected; product since the last good reading washed again or held |
| 3 Cold | Product at 41°F or below in the cutting room, at packing and in the cooler | Each hour in the room; cooler twice a day | Chilled at once; thrown away if the time warm isn't known |
| 4 Label and date | Each bag carries its product's label, a lot code and a use-by date | First and last bag of each run | Held and relabeled |
Wash water is the point people get wrong. The sanitizer isn't there to disinfect the lettuce. It's there to keep the water clean, so that what washes off one head doesn't land on the next thousand. Soil and juice use the sanitizer up, which is why it's measured every half hour and not once in the morning. Use a wash chemical approved for produce, at the strength its label gives, with the test kit made for it.
Melons. Scrub and wash the whole melon before the knife touches it. The blade carries whatever is on the rind into the flesh.
The room. Keep the cutting room cold. Take cutters, belts and spinners apart to clean them, and swab them and the floors and drains around them for Listeria on a schedule. FDA's rule asks for environmental monitoring, under a written procedure, where a pathogen in the plant could reach a ready-to-eat food. A program is in environmental monitoring program template.
"Washed" on the label. Decide what your label tells the customer, and be able to stand behind it. If the bag says the product is washed and ready to eat, your wash, your room and your swabs are what make that true.
A week's log
| Day | Check | Reading | Limit | OK? |
|---|---|---|---|---|
| Mon 7:00 | Romaine, lot from Field 6, receiving | 38°F | 41°F or below | Yes |
| Mon 8:30 | Wash tank 1, sanitizer | In range | Label strength | Yes |
| Mon 9:00 | Wash tank 1, sanitizer | Below range | Label strength | NO: act |
| Mon 11:00 | Cutting room, product | 39°F | 41°F or below | Yes |
| Thu | Swabs, 8 sites, Listeria species | All negative | Yes |
At 9:00 on Monday the sanitizer in tank 1 read below its range: the dosing pump's tube had come out of the drum. The romaine washed since the 8:30 reading, about 90 pounds, was held under its code and washed again in tank 2. Half-hourly readings are why it was 90 pounds and not a morning's work.
This is general information, not legal advice. Approving growers is covered in supplier approval program template, salads made in a kitchen in HACCP plan for salads, and the cold limits in hot and cold holding temperatures.
Get the worksheet
Download the fresh-cut produce HACCP worksheet. Three sheets and a read-me: the hazard analysis from the grower to the bag, 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 grower calls on Wednesday: Monday's romaine came from a field that's now under an advisory. Which bags did that lot go into, which restaurants have them, and how many are still in the cooler? Fresh-cut produce is eaten within days, so the answer is needed within the hour. The receiving log says "romaine, 12 cases".
How TaroStack does it
TaroStack records the grower's lot and follows it into the bag.
Receiving records each grower's lot, with its date.
Each run is a batch with a lot code and a use-by date, and lot labels print with both. The batch notes which grower's lots it used, automatically.
Your checks are fields on the batch record: sanitizer reading, product temperature, label checked, initials.
Oldest first. Stock goes out first-expired-first-out by default, with an alert before a date arrives.
One report for a recall: which bags used the lot, which restaurants got them, and what's still in the cooler. Starting a recall holds the rest.
| The grower's call | Receiving log | In TaroStack |
|---|---|---|
| Which bags used Monday's romaine | "Romaine, 12 cases" | The batches that used the lot |
| Which restaurants have them | Delivery sheets | One report |
| Bags still in the cooler | Count | Stock by lot, on hold |
| The wash readings for that run | A clipboard | On the batch record |
TaroStack doesn't measure sanitizer or temperature, and it doesn't swab. 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.
