A HACCP flow diagram is a list of every step a food goes through in your operation, in order, from the back door to the customer. That's all. Boxes and arrows are optional; a numbered list does the job. The FDA Food Code asks for one in a HACCP plan for each food or category, identifying each step in the process and which steps are critical control points. Its purpose is to make sure the hazard analysis doesn't skip anything: you can't control a step you forgot was there. Below is a nine-step example for a cook-chill food, and a worksheet to write your own.
The short version
- One line for each step, in the order it happens.
- Note what enters at each step: ingredients, packaging, water, ice.
- Mark the steps that are CCPs, after you've done the hazard analysis.
- Include the side roads: rework, returns, leftovers, holding between steps.
- Walk the floor with the list before you call it finished.
- TaroStack records each batch against the same steps, with your readings. More below.
An example: cook-chill chicken chili
| Step | What happens | Enters here | CCP? | Limit |
|---|---|---|---|---|
| 1 | Receive raw chicken, vegetables, dry goods | Chicken at 41°F or below | No | |
| 2 | Store: walk-in, dry storage | No | ||
| 3 | Prep: dice vegetables, portion chicken | No | ||
| 4 | Cook the chili in the kettle | Canned tomatoes, beans, spices | CCP 1 | 165°F |
| 5 | Bag hot and seal | Bags | CCP 2 | Sealed before it falls below 135°F |
| 6 | Cool the bags in an ice bath | Ice | CCP 3 | 70°F within 2 hours; 41°F within 6 in all |
| 7 | Hold in the walk-in, dated | CCP 4 | 41°F or less; 7 days | |
| 8 | Reheat for service | No | 165°F (line procedure) | |
| 9 | Hold hot and serve | No | 135°F or above (line procedure) |
Steps 1 to 3 and 8 to 9 aren't CCPs in this plan because the café's everyday procedures (receiving checks, cooler logs, line temperatures) already handle them. That's a judgment made in the hazard analysis, and another kitchen might decide differently.
How to build one
1. Write what you think happens. Start at receiving. End when the food is in a customer's hands.
2. Add what enters. Every ingredient, every package, water and ice. Each input can bring a hazard, and an ingredient added after the cook step (fresh herbs on top, say) never gets the cook's protection.
3. Add the side roads. What happens to chili left at close? Does a bag that leaks get re-bagged? Is yesterday's batch ever mixed into today's? These are the steps that cause trouble, and they're the ones left off diagrams.
4. Walk it. Take the list to the kitchen during production and watch. There's nearly always a step nobody mentioned: the pot that sits on the counter for twenty minutes before bagging, the trip across the parking lot to the second walk-in.
5. Then do the hazard analysis, step by step, and come back to mark the CCPs.
Common mistakes
| Mistake | Why it matters |
|---|---|
| Steps described as departments ("kitchen", "storage") | A hazard analysis needs actions: cook, cool, bag |
| Missing waits and transfers | Time at room temperature hides in the gaps between steps |
| One diagram for very different foods | Chili and sushi rice don't share steps. Group only foods that do |
| Drawn once and never updated | A new kettle or a new step changes the plan |
| CCPs marked before the analysis | The diagram comes first; CCPs are a result |
For a bakery, the steps change (scaling, mixing, proofing, baking, cooling, slicing, packing) and so do the hazards: allergens and metal rather than cooling. A worked bakery plan is in bakery HACCP plan. This is general information, not legal advice; whoever reviews your plan has the last word.
Get the worksheet
Download the HACCP flow diagram worksheet. The nine-step example with columns for what enters, the CCP and its limit, and a read-me. Type your own steps over it. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. The plan it belongs in is in HACCP plan template for a restaurant, and the programs behind the non-CCP steps in prerequisite programs for HACCP.
Where this stops working
The diagram describes how a batch should move. It can't show you how last Thursday's batch did move: whether step 6 took two hours or three, whether step 7's bags were dated. That's what records are for, and records kept apart from the steps drift from them.
How TaroStack does it
TaroStack lines the records up with the steps.
Steps that change the food are batches. Cooking and bagging the chili is a batch: ingredients in, bags out, with the lots used noted automatically. A sub-recipe made ahead is its own batch, feeding the next.
Each batch record carries your checks. The readings at your CCPs are fields of your own, in the order the steps happen, on a form that prints for the floor.
What entered is on the record. Every ingredient and package, with its lot. An input added late is as visible as the main ones.
Rework has a path. A leaky bag re-bagged, or leftovers used tomorrow, is recorded against the lot it came from.
| The diagram says | On paper | In TaroStack |
|---|---|---|
| What enters at each step | Listed once | Recorded on every batch |
| Readings at CCPs | A separate log | Fields on the batch record |
| Rework and leftovers | Usually missing | Recorded against their lot |
| Did this batch follow the steps? | Hard to say | Its own record |
TaroStack doesn't draw the diagram or write the plan. Recipes, batches and lots 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.
