How to Write a HACCP Plan for a Food Truck | GIFSQ

How to Write a HACCP Plan for a Food Truck

A food truck is a restaurant kitchen the size of a closet, on wheels, with limited water, limited power, limited refrigeration, and nowhere to hide when something goes wrong. The constraints are the hazard analysis: every limitation — water supply, holding capacity, power reliability, handwashing facilities — is a potential failure point. Food truck HACCP isn’t factory HACCP shrunk down; it’s a plan built around constraints, with backup procedures for when the constraints bite.

This guide walks the Codex 12 steps for a food truck operation — commissary prep through truck service — focused on the realities: small equipment, mobile power, water limits, and high-volume service in tiny spaces.

Step 1: The team is small — make it count

Owner/operator, lead cook, commissary contact. That’s the team. Someone with food safety training — many jurisdictions require it for mobile food operations specifically. Document roles. In a two-person operation, the plan has to be executable by two tired people at 9 p.m. — design for that.

Step 2: Describe the operation — menu, truck, commissary

Menu grouped by process category (cook-serve, cook-hold-serve, cook-chill-reheat). The truck itself described as equipment: refrigeration capacity, hot-holding equipment, water tank capacity and refill procedure, power source (generator, shore power) and backup, handwash facilities. The commissary: what gets prepped there, how it gets to the truck, transport controls. The truck’s limitations aren’t embarrassments — they’re the design inputs. Write them down honestly.

Step 3: Who eats here?

General public — walk-up customers, including children and the vulnerable. High volume, fast turnover, no relationship with the customer. Allergen communication happens at a service window in 30 seconds — the system has to work that fast.

Step 4: Diagram the truck — every inch

Commissary flow plus the truck layout: receiving/storage on the truck, prep areas, cooking equipment, holding units, handwash basin, water tanks, waste. Mark the actual workflow in the actual space — where raw meets ready-to-eat in a 2-meter kitchen is the critical design question. Walk it (it’s a short walk). Sign, date.

Step 5: Hazard analysis — the constraints are the hazards

• Biological: standard cooking/cooling/holding hazards — Salmonella, C. perfringens, S. aureus — amplified by small equipment (cooling in a tiny fridge, holding in limited units). Power failure — generator dies, refrigeration warms: this is a truck-specific hazard needing a planned response. Water supply — running out of water stops handwashing and cleaning: operational hazard with safety consequences.
• Chemical: allergens — fast service, small prep areas, shared surfaces; cleaning chemicals stored in tight quarters near food.
• Physical: metal, glass, plastic — plus equipment-shedding in a vibrating mobile kitchen.

Assess each constraint as a hazard scenario: what happens when the generator fails at noon? When the water runs out at 8 p.m.? When the fridge can’t recover between rushes? The plan needs answers before the day they happen.

Step 6: CCPs

• Cooking — final internal temperatures.
• Hot holding — ≥60 °C in the truck’s units.
• Cold holding — ≤5 °C in the truck’s refrigeration.
• Cooling — at the commissary (cooling on the truck is rarely feasible — design it out).
• Reheating — commissary-prepped items finished on the truck.

Step 7: Critical limits

• Cooking: poultry 74 °C/165 °F; ground beef 71 °C/160 °F; pork/fish 63 °C/145 °F.
• Hot holding: ≥60 °C. Cold holding: ≤5 °C.
• Cooling (commissary): 60→21 °C in 2 h, →5 °C in 6 h total.
• Reheating: 74 °C/165 °F.
• Water: minimum tank levels for operation — define the “stop service” threshold.

Step 8: Monitoring — built for speed

Cooking: probe checks per batch — the thermometer lives at the cooking station, not in a drawer. Holding: unit checks every 2 hours during service — fast, logged. Cold storage: continuous if the unit supports it, otherwise frequent checks. Water: tank level checks on a schedule. Assign by station. During a rush, monitoring has to take seconds — design the log for seconds.

Step 9: Corrective actions — including the generator

Undercooked: continue cooking or discard. Holding out of temperature: time-assess, reheat or discard per the rules. Power failure: the pre-written plan — how long can food stay safe without power (based on your validation), when to stop service, what gets discarded, who decides. Write it now, laminate it, keep it where the operator can see it. Water depleted: stop operations requiring water — which, honestly, is nearly everything. Define the threshold and the stop rule in advance.

Step 10: Verification

Thermometer calibration — ice-point checks weekly. Manager review of daily logs. Equipment checks: refrigeration pull-down tests, generator servicing per schedule, water system sanitization. Commissary verification of cooling logs. Periodic self-audit: does the plan match the actual operation? Trucks evolve — equipment gets swapped, menus change. The plan follows.

Step 11: Records — minimal and mobile

Daily truck log: holding temps, cooking spot-checks, water levels, corrective actions. Commissary cooling logs. Calibration log. Training records. One clipboard on the truck. If it can’t be done with one clipboard in a moving kitchen, simplify it until it can.

Step 12: Review — seasons, locations, equipment

Annual minimum, plus: menu changes, equipment changes (new fridge, new generator), new regular locations (power availability, water access differ by site), seasonal changes (summer heat loads the refrigeration), any incident. A truck’s operating environment changes constantly — the plan keeps up or it stops describing reality.

Things that actually work on trucks

Design cooling out of the truck. Cool at the commissary under controlled conditions, transport cold, reheat on the truck. Trying to cool properly in a truck fridge during service is a losing battle — so don’t fight it. The process design is the control.

Laminate the power-failure plan. Generator failure procedure, time limits, discard rules, who decides — on the wall, not in a binder. When the power dies at noon with a line of customers, nobody’s reading a manual. The laminated sheet gets read.

Right-size the menu. Every additional menu item multiplies cross-contamination paths, holding requirements, and allergen complexity in a tiny space. The safest truck menus are focused. Complexity is the enemy in 15 square meters.

Water discipline. Know your tank capacity, your usage rate, and your refill points. Define the minimum operating level and the stop rule. Running dry mid-service isn’t just inconvenient — it stops handwashing, and that’s a safety failure.

War stories

The generator at noon. Generator died during lunch rush — refrigeration warming, hot holding cooling, line of customers. No plan. The operator kept serving for two hours “because the food felt cold.” Felt cold isn’t a measurement. Time-temperature assessment later suggested some product had been in the danger zone for over 4 hours. A pre-written power-failure plan — time limits, discard rules, stop-service threshold — would have made the decision in two minutes. Write it before you need it.

The fridge that couldn’t recover. Small under-counter fridge, loaded with prepped product, door opening every 90 seconds during the rush. Internal temperature crept to 9 °C and stayed there. The unit was correctly sized for storage, not for service. Holding checks every 2 hours caught it — but only because the checks were actually being done. Size refrigeration for service reality, monitor through the rush, and have a backup plan (reduced menu, ice, commissary resupply).

The water ran out. Tank empty at 8 p.m., Saturday night, handwash basin dry. Service continued — “we had sanitizer.” Sanitizer doesn’t replace handwashing, and an empty water tank means the operation’s hygiene foundation is gone. The stop rule should have triggered. Define the minimum level, monitor it, honor it.

The commissary gap. Truck operation tight and disciplined — but cooling happened “at the commissary” with no logs, no verification, no defined procedure. The truck’s plan covered the truck; the food’s safety was decided in an unmonitored kitchen across town. The plan covers the whole operation — commissary cooling gets the same CCP discipline as everything else.

Allergen at the window. Thirty-second service interaction, customer mentioned an allergy, busy server nodded, kitchen didn’t get the message clearly. In a truck, the communication chain is short but fast — which means it needs to be designed: ticket marking, verbal confirmation protocol, a pause-and-verify step for allergen orders. Speed without a system is how allergen orders go wrong.

Common mistakes

Skipping the power-failure plan. The generator dies at noon and there’s no plan — so service continues on “felt cold” while product sits in the danger zone. Write the power-failure plan before you need it: time limits, discard rules, the stop-service threshold, laminated where the operator can see it.

Sizing refrigeration for storage, not service. The under-counter fridge holds temperature with the door closed but creeps to 9°C when it’s opened every 90 seconds in the rush. Size for service reality, monitor through the rush, and keep a backup plan.

Running out of water. The tank empties on a Saturday night and service continues on sanitizer — but sanitizer doesn’t replace handwashing. Define the minimum water level, monitor it, and honor the stop rule.

Leaving the commissary out of the plan. The truck is disciplined while cooling happens “at the commissary” with no logs and no verification. The plan covers the whole operation — commissary cooling gets the same CCP discipline as everything else.

Winging the allergen communication. The thirty-second window interaction, the nod, the message that never reaches the kitchen. Design it: ticket marking, verbal confirmation, a pause-and-verify step for allergen orders.

Monitoring that can’t survive the rush. The log designed for a quiet kitchen gets abandoned when the line is out the door. Design monitoring for seconds — the thermometer at the station, the log that takes moments — or it won’t happen when it matters most.

Checklist — before you call this plan done

• [ ] Team defined; food safety training documented (mobile-specific where required)
• [ ] Operation described: menu by process, truck equipment and limits, commissary role
• [ ] Truck layout diagrammed with workflow; raw/RTE separation in the small space addressed
• [ ] Hazard analysis covers constraints: power failure, water supply, small-equipment limits
• [ ] CCPs: cooking, hot/cold holding, commissary cooling, reheating
• [ ] Critical limits posted in the truck; water minimum level and stop rule defined
• [ ] Monitoring: station-assigned, seconds-fast, including water levels
• [ ] Corrective actions: power-failure plan laminated and posted; discard rules pre-decided
• [ ] Verification: calibration, equipment checks, commissary log review, periodic self-audit
• [ ] Records: one clipboard, actually completed during service
• [ ] Annual review; menu, equipment, location, or season changes trigger reassessment