How FDA Food Code rules shape prep steps for US ghost kitchens

What to take away

How the Food Code reaches your kitchen

The FDA writes the Food Code. Your county health department enforces whatever version your state adopted, and that adopted text is what an inspector reads off a clipboard.

Some states adopt by reference, so the current edition applies unless the state says otherwise. Others write their own retail food rules and borrow from the model. The Food Code 2022 is the current baseline for cooling, date marking and bare-hand contact.

A shared kitchen adds a layer. The facility operator may hold the permit while each brand inside must still follow the same food safety plan. Inspectors ask for brand-level records even when the facility permit is current.

The FDA Food Code page explains how state and local agencies adopt the model and what that means for the person running the line.

Adoption drives training too. ServSafe teaches the adopted code, not the model text. If your state amended a cooling time or a date-marking rule, your course should reflect the amendment.

New owners mapping permits can use a ghost kitchen compliance checklist to separate facility duties from brand duties before the first inspection.

Cooling clocks that set your cook schedule

Cooked food goes from 135°F to 70°F within two hours, then to 41°F or below within four more, six hours total. Those two clocks decide when you can batch cook.

A 20-quart pot of chili cannot sit on the counter while orders go out. It needs an ice bath, a blast chiller or shallow pans inside the two-hour window.

Cold holding at 41°F or below is the second limit. A prep table running at 45°F is a violation even when the food was cooked safely.

Cooling methods that survive a dinner rush

A kitchen that cooks once for lunch and once for dinner can cool between services. A kitchen cooking to order has less room and may need to cool components ahead and reheat to 165°F for hot holding.

Reheating is not a reset. Food that was cooked, cooled and reheated keeps its original date mark. The seven-day clock starts at prep, not at the second heat.

Rice, beans and pasta are the usual cooling violations. Cook them in batches small enough to cool inside the two-hour window.

Stock planning should account for cooling capacity, not just shelf space. A walk-in full of hot pans cools nothing, which is why ghost kitchen stock control starts with how fast you can chill.

Date marking on a multi-brand prep table

Date marking applies to ready-to-eat food that needs time or temperature control and is held more than 24 hours. The label shows the date by which the food must be sold, eaten or thrown out.

The limit is seven days at 41°F or below, and day one is the day you cooked it. A sauce made Monday is discarded by Sunday, even if it still smells fine.

Some states allow four days for certain items or for food prepared in a facility that also handles raw animal food. Check your adopted code before you set a house rule.

What belongs on the label

A compliant label usually carries the brand name, the item, the prep date and the discard date. If the item is a major allergen, the label says so.

Multi-brand tables create the trap. A container of diced chicken may belong to three brands, so the label must name which brand owns it and when it was prepped.

Color-coded lids and day dots help, but they do not replace a written date. Inspectors read dates, not colors.

A mislabeled container is a food safety risk and a customer complaint, so the packaging routine should include a check that the label matches the brand ticket.

Freezing and thawing

Freezing pauses the seven-day clock only if the food was frozen before the clock ran out. Label the freeze date and the date it left the freezer.

Once thawed, the food gets the days it had left. Frozen on day three, it has four days after thawing.

Thaw under refrigeration at 41°F or below, under running water at 70°F or below, or as part of cooking. Counter thawing is not allowed.

Bare-hand contact at the assembly line

Bare-hand contact restrictions apply to ready-to-eat food: salads, garnishes, cooked proteins, sushi, bread and ice. The Food Code allows few exceptions, mostly where the food is cooked again later.

Gloves are not a substitute for handwashing. Wash before gloves go on and after they come off, and change them when they tear, when you switch tasks or when you touch a non-food surface.

Setting up the line

A compliant line has a hand sink within reach, gloves in easy dispensers, and tongs or scoops for every ready-to-eat item. The sink needs soap, paper towels and warm water.

Single-use gloves should fit. Loose gloves slow the line and tear more often, so keep several sizes at the station.

Utensils need a home. A tong left on a cutting board is contaminated, so use a clean holder or a sanitizer bucket between uses.

If a cook touches a phone, a cooler handle or a trash lid, the gloves come off. That is the rule most often missed during a rush.

Training beats signage here. A ghost kitchen license requirements program should drill the glove-change triggers until they are automatic.

Four states, four rulebooks

California adopts the model through the California Retail Food Code, with state amendments and county add-ons. It tends to be strict on handwashing, glove use and food handler cards.

Texas adopts it through the Texas Food Establishment Rules, run by the Department of State Health Services. Large cities add their own health department rules on top.

New York runs its own sanitary code and food safety program. The state health department's Food Safety page is where operators check state-level adoption.

Florida splits adoption between the Department of Business and Professional Regulation and the Department of Agriculture. Rules differ by what you sell and where you sell it.

Federal notices can also change labeling and safety obligations. The Federal Register health and public welfare section carries them.

Licensing follows the same patchwork. A permit that works in Austin may not transfer to Los Angeles, which is why ghost kitchen licensing has to be checked city by city.

Before you sign a lease

Ask the local health department which code edition it enforces. Ask whether the shared kitchen permit covers your brand or whether you need your own.

Ask for the last inspection report at the address. A shared kitchen with repeat cooling violations is a risk to every brand inside it.

Turning code into a daily prep routine

A prep routine should translate code language into line-level actions that work during a rush, not a binder that stays closed.

Start with cooling. Write the cooling start time on the pan and set a timer for the two-hour mark. If the food is not below 70°F, move it to a faster method.

Set the date-marking station next. Labels, markers and day dots go beside the prep table, and nothing enters the walk-in without a date.

Then set the line. Gloves, tongs and a hand sink within reach, a sanitizer bucket for utensils, and a trash can you can open without a gloved hand.

Finish with close-down. Temperatures logged, dates verified, expired food discarded, surfaces sanitized.

Daily prep checklist

Worked example: a Tuesday dinner rush

Three brands share one kitchen. At 2 p.m. a cook makes 10 quarts of tomato sauce, splits it into two shallow pans, and ice-baths it to 70°F by 3:30 and 41°F by 5.

Both pans get a prep date and a discard date seven days out. At 6 p.m. the line uses tongs for pasta and gloves for salads. A cook answers the phone and changes gloves before returning.

At close the manager logs cooler temperatures and checks the walk-in for unlabeled containers. The sauce is dated, the line is clean, and the records match what an inspector would see.

The routine is the same in Phoenix or Tampa. What changes is the adopted code edition and the local add-ons.

Records that hold up at inspection

Inspectors look for records that match what they see. If the cooler reads 38°F but the log shows 41°F all week, the log is not credible.

Corrective actions matter. If a cooler fails, the log should show what happened to the food: moved, cooled or discarded.

Training records should name the person and the date. ServSafe certificates expire, so track renewal dates.

Not every state requires a written food safety plan, but a shared kitchen benefits from one. It shows how brands divide responsibility for cooling, dating and glove use.

Fix a violation and document the fix. Repeat violations cost more than the first and can put the facility permit at risk.

The economics are simple. A ghost kitchen runs on thin margins and fast turns, and a closure stops revenue for every brand in the building.

Common questions

Does the FDA Food Code apply directly to my ghost kitchen?

No. It is a model code that applies once your state or local health department adopts it, often with amendments. Confirm the enforced edition with your county health authority before you write any prep rule.

How long can I hold cooked food before discarding it?

Seven days at 41°F or below, counting the prep day as day one. Some states allow shorter periods for certain items, so check the adopted code rather than assuming the model text.

Can I use bare hands if I wear gloves?

Gloves are allowed for ready-to-eat food, but hands must be washed before gloves go on and after they come off. Change gloves when they tear, when you switch tasks or when you touch a non-food surface.

Do I need a separate permit for each brand in a shared kitchen?

That depends on the state and city. Some shared kitchens hold one permit that covers the brands inside, while others require each brand to hold its own. Ask your local health department which applies to you.