Food Safety, Health and Licensing

HACCP Plans: When Restaurants Need One

When a restaurant needs a HACCP plan or variance, such as sous vide, curing, acidified rice or vacuum packing, and how to write and run one.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. HACCP in a restaurant: required plan or good habit?
  2. Processes that need a variance
  3. Sous vide and cook-chill: plan required, variance not always
  4. Quick decision guide
  5. The seven HACCP principles
  6. What the plan document must contain
  7. Example: a sous vide short rib program
  8. Why plans get sent back
  9. Keeping the plan alive
  10. Frequently asked questions
  11. References
Food Safety, Health and Licensing: HACCP Plans: When Restaurants Need OneArticle coverFOOD SAFETY, HEALTH AND LICENSINGHACCP Plans: WhenRestaurants Need OneAva for RestaurantsInsightsFood Safety, Health and Licensing: HACCP Plans: When Restaurants Need OneArticle coverFOOD SAFETY, HEALTH AND LICENSINGHACCP Plans: WhenRestaurants Need OneAva for Restaurants

Key takeaways

  • Most restaurants do not need a formal HACCP plan; the Food Code requires one when a variance is needed or for reduced-oxygen packaging such as sous vide[1].
  • Variances cover processes such as curing, smoking to preserve, acidifying rice so it is not TCS, and live shellfish tanks[1].
  • Sous vide food held at 41°F or below must be used within 7 days, or within 30 days if cooled to 34°F within 48 hours[1].
  • A plan follows the seven HACCP principles and must include flow diagrams, critical limits, monitoring, corrective actions and records[1].

HACCP in a restaurant: required plan or good habit?

HACCP stands for Hazard Analysis and Critical Control Point. It is a way of identifying the steps in a process where something can go wrong, setting a measurable limit for each, and checking that the limit is met every time. Every restaurant uses HACCP thinking already: the cooking temperature for chicken and the two-hour cooling checkpoint are critical limits in all but name.

A formal, written HACCP plan submitted to your health department is a different matter. Under the FDA Food Code, a restaurant must submit a HACCP plan for approval before starting an activity that requires one, which happens in three situations: when another law requires it, when a variance is required, or when the regulator decides a method needs a variance based on plans, an inspection or a request. A plan is also required before reduced-oxygen packaging without a variance[1]. If you do none of those things, you do not need a formal plan, though the structure is still useful.

Processes that need a variance

A variance is written permission from the regulatory authority to depart from a Food Code requirement, backed by evidence that the food will still be safe. The 2022 Food Code lists the processes that require one[1]:

Restaurant processes that require a variance under the 2022 Food Code
ProcessRestaurant exampleWhy it is special
Smoking food to preserve itHouse-smoked salmon held for daysSmoke for flavor is fine; smoke as preservation is not a standard control
Curing foodHouse-cured guanciale, bresaola, salamiRelies on salt, nitrite and drying instead of temperature
Additives or vinegar to preserve or to make food non-TCSAcidified sushi rice held at room temperatureSafety depends on hitting a target acidity every batch
Reduced-oxygen packaging outside the code's conditionsVacuum-packed fish, or cook-chill bags sold to other businessesCan allow Clostridium botulinum and Listeria to grow
Live molluscan shellfish display tankOyster or lobster tank for guests to choose fromWater quality and shellfish source must be controlled
Custom processing animals for personal useProcessing a hunter's deerNot from an approved source for sale
Sprouting seeds or beansHouse-grown sproutsSprouts are a known outbreak risk
Other methods the regulator decides need oneFermentation programs, novel low-temperature cookingThe inspector has discretion

The Food Code also allows a variance from standard cooking temperatures, for example serving a raw or undercooked dish to order, where a HACCP plan documents scientific data showing that a lower time and temperature still produces safe food[1]. Most restaurants serving rare burgers or raw fish use the consumer advisory route instead.

Sous vide and cook-chill: plan required, variance not always

Sous vide is the case most chefs ask about. Under the 2022 Food Code, a restaurant can package TCS food using a cook-chill or sous vide process without a variance, but only if it gives the regulator a HACCP plan before starting and follows strict conditions[1]. The main ones:

  • The food is prepared and eaten on the premises, or within the same business, and the packaged product is not sold to another business or to consumers.
  • It is cooked to the standard Food Code temperatures and times.
  • It is sealed in a package with an oxygen barrier before cooking, or immediately after cooking before it drops below 135°F.
  • It is cooled to 41°F in the sealed bag within the normal cooling limits, then either held at 41°F or below and used within 7 days, or cooled to 34°F within 48 hours and used within 30 days of packaging, or frozen.
  • It is held in refrigeration equipped with electronic monitoring of temperature.
Maximum shelf life for sous vide or cook-chill food in the 2022 Food CodePackaged on premises, cooked and cooled to code, no variance
Maximum shelf life for sous vide or cook-chill food in the 2022 Food CodeComparison. Held at 41°F or below: 7 days; Cooled to 34°F within 48 hours: 30 days.7 daysHeld at 41°F or belowHeld at 41°F or below: 7 days30 daysCooled to 34°F within 48 hoursCooled to 34°F within 48 hours: 30 daysMaximum shelf life for sous vide or cook-chill food in the 2022 Food CodeComparison. Held at 41°F or below: 7 days; Cooled to 34°F within 48 hours: 30 days.7 daysHeld at 41°F or belowHeld at 41°F or below: 7 days30 daysCooled to 34°F within 48 hoursCooled to 34°F within 48 hours: 30 days

Source: US Food and Drug Administration, 2022[1]

Show the data
Holding optionDays
Held at 41°F or below7 days
Cooled to 34°F within 48 hours30 days

Local rules can add to this. New York City's inspection scoring, for example, treats refrigeration used for a reduced-oxygen packaging HACCP plan that lacks an electronic system continuously monitoring time and temperature as a serious violation, scored at 10 or 28 points depending on the condition[2].

Quick decision guide

Run through these questions for every menu item and prep process. A single yes means you should talk to your health department before you start, not after an inspector asks.

  1. Do we seal TCS food in vacuum bags, under modified atmosphere, or by any other method that removes oxygen?
  2. Do we cure, dry-age for preservation, ferment, or smoke anything to make it last rather than for flavor?
  3. Do we add vinegar, acid, salt or another additive so that a food can be held without refrigeration?
  4. Do we keep live shellfish in a tank for display or sale?
  5. Do we sprout seeds or beans, or serve a raw or undercooked dish that is not covered by a consumer advisory?
  6. Do we sell anything we package to another business, such as a sister restaurant run as a separate company?
  7. Has an inspector ever told us that a process needs review?

If every answer is no, you need sound standard procedures rather than a formal plan. Keep your cooking, cooling and holding logs and train staff on them; that is HACCP thinking without the submission.

The seven HACCP principles

Every HACCP plan follows the seven principles defined by the National Advisory Committee on Microbiological Criteria for Foods, which the Food Code annex explains[1]. In restaurant terms:

  1. 1. Conduct a hazard analysis

    List the hazards in the process: pathogens that survive cooking, toxin formation in sealed bags, parasites in raw fish, physical hazards such as bone fragments.

  2. 2. Determine critical control points

    Pick the steps where you can prevent or reduce each hazard: cooking, cooling, cold holding, acidifying.

  3. 3. Set critical limits

    Give each control point a number you can measure, such as a core temperature and time, a pH or a maximum holding temperature.

  4. 4. Set monitoring procedures

    Say who measures, with what, and how often: for example, the cook probes every bag in the bath.

  5. 5. Set corrective actions

    Say what happens when a limit is missed: re-cook, discard, hold for evaluation.

  6. 6. Set verification procedures

    Say how a manager checks the system works: reviewing logs weekly, calibrating thermometers and pH meters.

  7. 7. Keep records

    Keep the logs, calibration records and training records that prove the plan is followed.

What the plan document must contain

The Food Code sets out what a submitted HACCP plan must include[1]. Use it as your table of contents:

  1. General information: business name, address and contact details.
  2. The categories of TCS food the plan covers.
  3. A flow diagram for each food or category, showing every step and marking the critical control points.
  4. Ingredients, recipes, materials and equipment, with the procedures that address the safety concerns.
  5. A critical control point summary: each control point, its hazards, critical limits, monitoring method and frequency, corrective actions, verification by the person in charge, and records kept.
  6. Supporting documents: a training plan for staff and supervisors, blank copies of each record form, and any scientific data the regulator asks for.
  7. Anything else the regulatory authority requires.

Before you write a word, call your health department. Ask whether they have a template, what supporting data they expect, and how long review takes. Many will review a draft.

Example: a sous vide short rib program

Example: a fictional bistro wants to cook short ribs sous vide in batches, chill them in the bag and finish them to order over five days. Its draft critical control point summary looks like this.

Example critical control points for a sous vide program, fictional restaurant
StepHazardCritical limitMonitoringCorrective action
ReceivingPathogen growth in warm productBeef at 41°F or below on arrivalProbe one case per deliveryReject delivery
SealingContamination; poor sealIntact seal, bag labeled with dateVisual check of every bagRe-bag or discard
CookingPathogen survivalTime and temperature meeting the Food Code roast chartProbe a sample bag per batch; log bath temperatureContinue cooking until limit met
CoolingSpore-forming bacteria growth135°F to 70°F in 2 hours; 41°F within 6 hoursProbe sample bags at both checkpointsDiscard batch
Cold holdingGrowth during storage41°F or below; use within 7 daysContinuous electronic monitoring; daily reviewDiscard bags past date or out of range

In this example, the bistro attaches its cooling log, its labeling format, its thermometer calibration record and a one-page training sheet, then submits the plan before running the first batch. The point of the exercise is not paperwork. Writing the limits down forced the kitchen to buy a second circulator so that bath temperature never dropped when a new batch went in.

Why plans get sent back

Health departments return many first drafts. The reasons are predictable, so check for them before you submit.

  • Critical limits written as words, such as cook thoroughly, instead of numbers with units and times.
  • Monitoring that does not say who checks, with what instrument, and how often.
  • Corrective actions that end in notify manager without saying what the manager does with the food.
  • No calibration records for thermometers or pH meters used to monitor critical limits.
  • Flow diagrams copied from a template that do not match how your kitchen actually works.
  • No blank record forms attached, even though they are a required supporting document.

Keeping the plan alive

Approved plans fail when the people who wrote them leave. Build the plan into daily work: put the critical limits on the station, keep the logs where the work happens, and make plan training part of onboarding for any cook who touches the process. Review the plan whenever the recipe, equipment or supplier changes, and at least once a year.

Cooling is the most common weak point in specialized processes, as in ordinary cooking: CDC counted 504 restaurant outbreaks over a decade caused by hot food cooled too slowly[3]. The standard cooling method is covered in cooling food safely: the two-stage rule, holding limits in temperature danger zone and time controls, and labeling in date marking and FIFO in restaurants. FDA issued a 2026 Food Code edition[4], so confirm the version and HACCP rules your health department enforces before you submit.

Frequently asked questions

Do all restaurants need a HACCP plan?

No. Under the Food Code a formal plan is required when a variance is needed, when the regulator or another law requires one, or before reduced-oxygen packaging such as sous vide without a variance[1].

Does sous vide need a variance?

Not always. The 2022 Food Code allows on-premises sous vide and cook-chill without a variance if you submit a HACCP plan first and meet its cooking, cooling, holding and monitoring conditions[1]. Local rules may differ.

What is the difference between a HACCP plan and a variance?

A variance is permission to depart from a code requirement. A HACCP plan is the document that shows how you will control the hazards. Most variances require a HACCP plan to support them.

How long does approval take?

It varies by health department. Ask before you start, submit early, and do not run the process until you have written approval.

References

  1. US Food and Drug Administration (2022). FDA Food Code 2022 (opens in a new tab) ↑

  2. NYC Department of Health and Mental Hygiene (2025). Rules of the City of New York, Title 24, Chapter 23: Food Service Establishment Inspection Procedures (opens in a new tab) ↑

  3. Centers for Disease Control and Prevention (2026). Food Cooling (opens in a new tab) ↑

  4. US Food and Drug Administration (2026). FDA Food Code (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo