Before you learned to drive a car, somebody handed you a little book and made you learn the rules of the road. Stop at the red light. Stay on your side of the road. Yield here. Don’t pass there. Know what the signs mean.

Then you got behind the wheel of an actual car, and everything changed. Knowing the rules was one thing. Using them to get from your house to Walmart and back again — preferably without killing anyone — was something entirely different.

This is kind of the same thing. You’ve already learned the seven HACCP (Hazard Analysis Critical Control Point) principles in HACCP: Find the Point That Matters — what they are, what they mean, and how they fit together. Now we’re getting behind the wheel. We are going to take one food and use those seven principles to build an actual working HACCP plan — from your house to Walmart and back again, so to speak.

Our food is chili. A pot of chili doesn’t look dangerous. It looks like lunch. But chili gives us something unusually useful because one batch can travel through nearly every major stage in a kitchen. Raw ingredients are prepped. The chili is cooked. It may sit in hot holding through service. Leftovers are cooled. Tomorrow they may be reheated, held again, and served.

That means we can follow one food through the operation and make the decisions HACCP requires along the way. We aren’t asking “What are the seven principles?” anymore. We’re asking “What hazards matter in this chili? Where can we control them? What limits do we set? Who checks them? What happens if something fails? And how do we know the whole plan is actually working?”

That is the difference between knowing HACCP and using HACCP.

You cannot personally stand over one pot of chili from the moment the beef hits the pan until somebody serves the last bowl the next day. You have a kitchen to run. HACCP makes that possible by forcing the important decisions to happen before the shift gets ugly. This time, we’re going to make those decisions.

---

Quick Recall

You already know the seven HACCP principles and the larger idea of Active Managerial Control — finding risks before they turn into somebody’s bad day.

You also already know every temperature and time used in this lesson. There is no new food-safety clock hiding in here. So this time, don’t read the seven principles as seven vocabulary words. Read them as seven decisions that build one working plan.

---

Why Chili Specifically?

Some foods barely move through the kitchen before they reach the guest. A salad may be prepped and served cold. A hamburger may be prepped, cooked, and served right away.

Chili can take the long way around: PREP → COOK → HOLD → COOL → REHEAT → SERVE

One important distinction before we build the plan: we are not saying that every ordinary pot of chili automatically requires a formal regulatory HACCP plan. We are using chili because its full journey makes the logic of HACCP easy to see. A real operation builds its plan around its food, its equipment, and its process.

All of this is what makes chili such a useful HACCP teaching example: we can watch one food move through several stages and decide where hazards matter, where they can actually be controlled, and what the plan needs to do about them. To get you ready for the journey, here’s an overview of what’s coming:

---

Building a HACCP Plan

Principle 1: Conduct a Hazard Analysis

The decision: Before you can protect a food, you have to decide what could actually hurt someone.

Start by following the chili. Raw ground beef and vegetables are prepped. The batch is cooked. It moves into hot holding for lunch. Whatever is left gets cooled. Tomorrow it may be reheated and served again.

Now ask where significant biological hazards could enter, survive, or grow.

If the ground beef is undercooked, disease-causing organisms may survive. Then the chili moves into hot holding. If it sits too cool during service, bacteria can grow even though the batch was cooked correctly.

Cooling creates another problem. Cooking does not make every biological concern disappear forever. Spore-forming bacteria such as Clostridium perfringens can survive cooking and then grow rapidly when a large batch of cooked food spends too long cooling through warm temperatures. A deep stockpot of chili is practically built to create that problem. The outside cools while the center hangs onto heat.

The next day, reheating matters too. If cooled chili is only warmed partway before it goes back into hot holding, organisms that survived or grew after cooking may still be there.

Prep and service still matter, but a step having food-safety rules does not automatically make that step a critical control point. HACCP is not asking us to circle every place where something could go wrong. It is asking which hazards actually matter in this process and where the kitchen has to control them.

Those are the hazards this plan is going to control. That is Principle 1 doing its job.

---

Principle 2: Determine Critical Control Points

The decision: Where in this process can we actually control the hazards we just identified?

A critical control point, or CCP, is not simply a place where something could go wrong. It is a point where control is essential to prevent, eliminate, or reduce an identified hazard to a safe level.

For this chili plan, the hazard analysis points us to four CCPs:

• Cooking — where we control pathogens that may be present in the raw ground beef.
• Hot Holding — where we control bacterial growth while the cooked chili waits for service.
• Cooling — where we control bacterial growth while the cooked chili moves back down to refrigeration temperature.
• Reheating for Hot Holding — where we control pathogens before previously cooked and cooled chili goes back into hot holding.

Prep and service still have to be done correctly. But for this chili plan, these are the four places where control becomes critical. Change the food, the equipment, or the process and the CCPs may change too. HACCP does not come with one universal list that every kitchen copies.

---

Principle 3: Establish Critical Limits

The decision: What has to happen for each CCP to stay under control?

A critical limit is the line the kitchen is not allowed to cross. On one side, the process is under control. On the other, somebody has to act.

• For the Cooking CCP, that line is 155°F for 17 seconds. The chili has to reach it before it can move on.
• For the Hot Holding CCP, the line is 135°F or higher while the chili waits for service.
• For the Cooling CCP, the line comes in two stages: the chili has to cool from 135°F to 70°F within 2 hours, then from 70°F to 41°F or below within the next 4 hours.
• For the Reheating for Hot Holding CCP, previously cooked and cooled chili has to reach 165°F for 15 seconds within 2 hours before it goes back into hot holding.

That gives us 6 hours total for cooling, but the first 2 hours still matter on their own. If the chili is above 70°F when that first checkpoint arrives, you cannot borrow time from the next four hours and call it good. Now everybody knows exactly where “safe enough” stops and corrective action begins.

---

Principle 4: Establish Monitoring Procedures

The decision: How are we going to know whether the critical limit is actually being met?

A critical limit is useless if nobody checks it. Monitoring is the part of HACCP that turns the numbers on the page into something the kitchen actually does. In practical terms, it answers a few basic questions: Who is checking? When are they checking? What are they checking for? And what gets written down?

Take the chili. When the batch finishes cooking, somebody has to put a calibrated thermometer into it and confirm 155°F for 17 seconds before it leaves the stove. Not “it looks hot.” Not “it’s bubbling.” We need a number.

Then the chili moves into hot holding. Now the question changes. The chili is already cooked; the problem is letting it sit too cool for too long. So the employee responsible for the station checks it at least every 2 hours and confirms that it is still 135°F or higher. That two-hour schedule matters because it gives the kitchen time to fix the problem if the temperature starts slipping.

Cooling is where the clock gets bossy. The employee records when cooling begins, and two hours later there is one very important question: Did the chili reach 70°F? If yes, keep cooling. It now has the remaining four hours to reach 41°F or below. If not, the plan has already told us we have a problem.

The next day, reheating creates another checkpoint. Start the clock, heat the chili, and use a calibrated thermometer to confirm that it reaches 165°F for 15 seconds within 2 hours before it goes back into hot holding.

That is very different from writing, “The line cook will check the chili while it is cooking, holding, cooling, and reheating.” That may sound responsible, but it does not tell the cook enough to actually run the plan.

A useful monitoring procedure tells us who checks, what they use, when they check, what limit they are checking against, and what gets recorded. It should be specific enough that another trained employee could pick up the plan and know exactly what to do.

---

Principle 5: Identify Corrective Actions

The decision: What happens when the food crosses the line?

This is where HACCP earns its keep. You do not wait until something goes wrong and then start debating what everybody thinks you should do. The response gets decided while the kitchen is calm, before anybody is tired, rushed, or trying to save a batch they do not want to throw away.

Take the chili. If it has not reached 155°F for 17 seconds, the answer is easy: keep cooking. It does not move to hot holding, and it does not get served, until it hits the critical limit.

Hot holding gives us a little more room to act because we are checking every two hours. If the chili drops below 135°F, reheat it to 165°F for 15 seconds and put it back into hot holding. If nobody knows how long it has been below the limit, discard it. “Heat it back up sometime” is not a corrective action.

Cooling is where the decision gets more expensive. If the two-hour checkpoint arrives and the chili is still above 70°F, the plan has already made the call: reheat it to 165°F for 15 seconds and restart the cooling process using a method that can actually cool it fast enough, or discard it. That might mean shallow pans, an ice-water bath, smaller portions, or another approved cooling method. What it does not mean is putting the same deep stockpot back into the walk-in and hoping this time goes better.

The next day, reheating has its own line in the sand. If the chili does not reach 165°F for 15 seconds within 2 hours, discard it. It does not go into hot holding just because dinner service is starting.

That is the point of corrective action: the decision gets made before the failure, not during it.

---

Principle 6: Verify That the System Works

The decision: Is the plan actually working the way we thought it would?

Monitoring tells us what happened to a single pot of chili. Verification steps back and asks, “Is the system we are using to cook, cool, reheat, hold, and serve our chili actually safe?”

Maybe every cooking temperature has been perfect for a month, but the cooling log shows the same corrective action three nights every week. That pattern tells us something. The problem may not be three different cooks forgetting how to cool chili. The problem may be that the kitchen keeps trying to cool twenty quarts of it in a deep stockpot that simply cannot lose heat fast enough.

That is where verification comes in. The manager backs up and looks at the whole pattern. Are the same failures showing up again and again? Are the cooling methods actually working? Is the equipment doing what the plan assumes it can do?

Verification also means checking the tools we rely on. If the thermometer used for monitoring is five degrees off, a beautiful temperature log is still wrong.

So monitoring asks, “Did this pot stay under control?” Verification asks, “Is the system we built keeping all the pots safe?”

---

Principle 7: Establish Procedures for Recordkeeping and Documentation

The decision: What do we write down so we know what actually happened?

If nobody records the temperatures, times, and corrective actions, then later we are guessing. Let’s hold on to our chili example. The record should tell us all the basics: which batch was cooked, on what day and at what time, who checked it, what the temperatures were, when they were checked, and — if something went wrong — what did we do?

All this matters because there is something about a busy restaurant that creates fuzzy memories. When you make 14 batches of chili a week, you are NOT going to remember exactly what happened to one particular pot three Tuesdays ago.

Think about the stuff you cook all the time. After a while, you barely think about it anymore. Your hands know what to grab, where to stand, what comes next. You could practically make it in your sleep — and after enough years in a kitchen, you may actually have nightmares about making it in your sleep. That repetition is great for getting fast at your job. It is terrible for remembering one particular batch two weeks later.

If somebody asks about a particular batch of chili that was prepped, cooked, and served a couple of weeks ago, you will probably “remember” that it was fine. Not because you are lying. Because you have cooked fifteen other pots, completed hundreds of other tasks, and clocked in and out ten times since then. All those shifts are starting to blend together.

If you kept a log? Now you don’t have to remember. You can prove that this particular batch was 78°F at the two-hour cooling checkpoint and had to be reheated. Records also help with verification. One log tells us what happened to one pot. A stack of logs can show us whether the same problem keeps happening again and again.

Repeated kitchen tasks disappear when you clock out. The record doesn’t.

---

The Chili Plan, All Seven Principles at a Glance

We have been building this plan one decision at a time. Now let’s put the whole thing in one place. The hazard analysis gave us four problems to control:

• Pathogens surviving inadequate cooking
• Bacterial growth during improper hot holding
• Bacterial growth during slow cooling
• Pathogens surviving inadequate reheating before hot holding

From there, the plan identified Cooking, Hot Holding, Cooling, and Reheating for Hot Holding as the four CCPs we are building around.

Then the manager backs up and looks at the whole thing. Are the same failures showing up again and again? Are the cooking, holding, cooling, and reheating procedures actually working? Can we trust the thermometers? That is verification. And somebody has to write it down: which batch, who checked it, temperatures, times, corrective actions, and manager review.

That is HACCP in working clothes. Not seven vocabulary words. One food, one process, and seven decisions that all connect to each other.

---

Closing Side Work

TL;DR — What You Actually Need to Remember

The seven HACCP principles are not seven vocabulary words sitting in separate boxes. They are one connected chain of decisions. Figure out what could go wrong. Decide where you can control it. Set the line. Check it. Decide what happens when somebody misses it.

After that, back up and make sure the whole system is actually working, then keep the records that prove what happened. For our chili, that chain led us to Cooking, Hot Holding, Cooling, and Reheating for Hot Holding as the four CCPs. Another food, another kitchen, or another process could send the plan somewhere else.

A hazard is what could hurt someone. A CCP is where you control that hazard. Monitoring asks, “Did this pot stay under control?” Verification asks, “Is the system we built keeping all the pots safe?” And corrective actions are decided before the kitchen puts you under pressure.

---

In the Weeds: Everything Can’t Be a CCP

Chef’s Explanation

The Exec finally spotted the problem: the team has started treating every food-safety concern as a critical control point. HACCP does not work that way.

The team needs to back up and do the hazard analysis first. What hazards are reasonably likely to matter for this particular salad and this particular process? What controls already exist through purchasing, sanitation, employee practices, equipment, and standard operating procedures? Only after sorting that out can they decide which steps are truly critical control points.

Cooking the chicken is an obvious place to look because raw chicken can carry pathogens and cooking is where the operation can control them. Cooling the cooked chicken also deserves serious attention because the chicken is being chilled for later cold service and bacterial growth during improper cooling is a real hazard.

Washing lettuce matters. Clean cutting boards matter. The salad spinner matters. The toss bowl matters. Clean plates matter. Condensate dripping onto a food-contact surface absolutely matters. But “this could make somebody sick” is not the definition of a CCP. Many of those problems should be controlled through sanitation, equipment maintenance, employee practices, and other food-safety procedures rather than by turning every step into its own HACCP checkpoint.

And if you caught the shell eggs, good. Fresh Caesar dressing made with untreated raw shell eggs creates a separate food-safety problem. The cleaner solution is to change the ingredient and use pasteurized eggs or pasteurized egg product rather than simply adding another CCP to an already ridiculous board.

HACCP is not a list of everything that can go wrong. It is a system for identifying the hazards that matter most, finding where control is critical, and building a plan around those points.

---

Key Terms to Know

• HACCP (Hazard Analysis Critical Control Point) — a food safety system built around identifying real hazards in a specific food and controlling them at the exact points in the process where control is possible.
• Hazard analysis — the process of identifying biological, chemical, or physical hazards that are reasonably likely to occur in a specific food or process.
• Critical control point (CCP) — a point in the process where control can be applied to prevent, eliminate, or reduce an identified hazard to a safe level.
• Critical limit — the specific measurable requirement that must be met at a CCP.
• Monitoring — checking whether a critical limit is being met during the process according to a planned procedure.
• Corrective action — the predetermined action taken when monitoring shows that a critical limit has not been met.
• Verification — periodically confirming that the HACCP system and its controls are working as intended.
• Recordkeeping and documentation — maintaining the records that show monitoring, corrective actions, verification, and other parts of the plan were actually completed.
• Clostridium perfringens — a spore-forming bacterium associated with foods such as meat, poultry, gravies, and large batches of cooked food; it can grow rapidly when cooked food is cooled too slowly.