Walk-In Cooler Temperature Log Fields and Cold-Holding Data by State

Template Formats in Development

The formats below identify the planned layouts for this field specification, mapped to the fields in Table 5 below. Files are not yet available for download. The field specification, jurisdiction data, and methodology on this page are complete and verified.

Source: Indianapolis Commercial Refrigeration Research, compiled 21 July 2026.

Source: Indianapolis Commercial Refrigeration Research, compiled 21 July 2026.

What temperature should a walk-in cooler be?

41°F is the figure in the FDA Food Code (§3-501.16) for TCS (time/temperature control for safety) food. It isn't universal. New York State's rule sets 45°F outside New York City; New York City sets 41°F. California sets 41°F with statutory exceptions at 45°F for six product categories. 40°F is widely repeated online but isn't the Code number — it's either a conservative operating target or an error.

41°F is also a limit on food temperature, not a required thermostat setting. Set the equipment low enough that product stays under the limit under real operating conditions — door traffic, delivery loads, and the warmest part of the unit all push product temperatures higher than the ambient reading.

Cold-holding limits: all 51 jurisdictions

The table below shows which Food Code edition each state agency held in FDA's snapshot as of 31 December 2024, and the cold-holding limit that edition carries. Limits are labeled as Verified (we read the jurisdiction's own regulation), Derived (limit comes from the adopted edition — 43 rows), or Unverified (pre-2005 edition or no adoption on record — 5 rows). This is not a legal lookup.

Source: U.S. Food and Drug Administration, "Adoption of the FDA Food Code by State and Territorial Agencies — 2024 Annual Report" (published 9 December 2025), Table 7. https://www.fda.gov/media/107543/download

Source: Indianapolis Commercial Refrigeration Research, reading jurisdiction regulations directly. Verified 21 July 2026. Amber rows: limit diverges from the edition's default 41°F. Blue row: rule changed since FDA's 31 December 2024 snapshot.

Source: Compiled by Indianapolis Commercial Refrigeration Research from FDA, "Adoption of the FDA Food Code by State and Territorial Agencies — 2024 Annual Report" (Table 7), snapshot as of 31 December 2024, with cold-holding limits read directly from jurisdiction regulations where marked Verified. Edition ages are calendar-year differences from 2026. Last verified 21 July 2026.

Row counts: 43 Derived, 5 Unverified, 3 Verified. Unverified jurisdictions (limit cell empty): Louisiana, Maryland, New Jersey, South Dakota, Vermont. Their agencies sit on pre-2005 editions; we'd rather leave those cells empty than fill them with a guess.

Where a state splits oversight across multiple agencies, this roll-up follows FDA's own convention and counts the most recent edition any agency holds. Georgia's Department of Agriculture (retail food stores) is on 2017 while the Department of Public Health (restaurants) is on 2013. Florida has three agencies. New York splits oversight by establishment type. The New York State Department of Health maintains Part 14 for food service establishments, and local health departments issue permits and enforce those rules outside New York City. The Department of Agriculture and Markets licenses and inspects many retail food stores. The FDA report's agency-level snapshot should not be read as a complete description of current restaurant regulation.

How we built the dataset

We assembled it from one federal primary source and a set of jurisdiction regulations, and the arithmetic is reproducible from the same public PDF. FDA's report lists 64 state agencies rather than 51 jurisdictions, because 12 states split retail food oversight across multiple agencies. We rolled agencies up using FDA's own stated tie-break rule, then checked the result against four totals FDA published independently.

1. We downloaded FDA's Adoption of the FDA Food Code by State and Territorial Agencies Responsible for the Oversight of Restaurants and/or Retail Food Stores — 2024 Annual Report (published 9 December 2025; the most recent edition available on 18 July 2026) and transcribed Table 7 — all 64 state agencies, with edition adopted, adoption method, oversight scope and effective year.
2. We rolled 64 agencies into 51 jurisdictions using the rule FDA states in its own report: where a state has multiple agencies, the state is counted at the most recent edition any of its agencies adopted. Where two agencies tie on the newest edition with different effective years, the roll-up shows the earlier year.
3. We checked the roll-up against FDA's published totals. Our table produces 7 jurisdictions on the 2022 edition, 24 on 2017 or newer, 36 on 2013 or newer, and 50 with some adoption on record. All four match FDA's own published figures. That check validates the totals and the tie-break logic. It does not prove every individual row was transcribed correctly — compensating errors could cancel out — so row-level confidence requires comparing our agency file against FDA's Table 7 directly. We have not yet published the transcribed agency-level file. Until it is available, readers can verify this roll-up against FDA Table 7 directly.
4. We computed two figures FDA does not publish: the age of each adopted edition and the years since each adoption took effect, both as calendar-year differences from 2026. Median edition age is 13 years; mean is 12.7. The longest-standing listed adoption is South Dakota's, effective in 1997 — 29 years, on the 1995 Food Code.
5. We then read the actual regulations for New York State, New York City, California and Indiana, and cited the section for each. Those rows are marked Verified. Every other row is Derived or Unverified, and labeled as such.

Indianapolis Commercial Refrigeration Research is the reference library of Indianapolis Commercial Refrigeration, a publisher and commercial refrigeration service-request platform. We do not perform refrigeration service ourselves, we are not a law firm, and we are not a health department. This page is educational reference material. For a decision that carries consequences, read your own jurisdiction's rule and talk to your regulatory authority.

Should your log record air temperature or product temperature?

Use separate, clearly labeled columns for the in-unit reading and for any product reading your food safety plan calls for. The Food Code's 41°F limit applies to food (§3-501.16). The device required inside the unit measures the air, or a simulated product, in the warmest part of the unit (§4-204.112(A)). Those are different measurements with different permitted accuracies.

Source: FDA Food Code (2022, 10th edition), sections as cited. https://www.fda.gov/food/fda-food-code/food-code-2022

If an ambient device and a food probe were exposed to the same true temperature and each erred at its permitted limit in opposite directions, their displayed readings could differ by 5°F — ±3°F plus ±2°F — while both instruments remained within the Code's accuracy specifications. That is our own worst-case illustration, not a requirement stated anywhere in the Code.

Instrument accuracy is not compliance. A wall gauge displaying 40°F is consistent with an actual ambient temperature anywhere from 37°F to 43°F within the permitted band. The display alone doesn't establish that the food met the applicable limit.

The sensor belongs in the warmest part of the unit. The Code says warmest part. It does not say where that is; that depends on the box, the airflow and the door. A gauge relocated somewhere convenient is measuring the wrong air.

Every field a walk-in cooler temperature log should carry, and why

This is the specification the templates are built from: each field, and the provision or operational reason behind it. In the public templates we reviewed for this page on 18 July 2026, we did not find this complete field-to-source mapping published anywhere. The Basis column distinguishes three different kinds of justification, because conflating them is how templates end up implying that every field they contain is legally mandated.

Source: Indianapolis Commercial Refrigeration Research, mapped to FDA Food Code sections as cited. Compiled 21 July 2026.

What public temperature log templates actually contain

We downloaded and read the publicly available templates below on 18 July 2026 and recorded only the fields we could confirm from the files themselves. This is a factual field-coverage record of a small corpus — two third-party forms plus our own — not a market survey and not a ranking.

Source: Files downloaded and read by Indianapolis Commercial Refrigeration Research, 21 July 2026. "Could not confirm" means field labels were not recoverable from the extractable text of the file we downloaded — a limit of our method, not a statement about the template. Nebraska Department of Education: https://www.education.ne.gov/ns/NSLP/HACCP/TempLogs/Refrig.pdf · StateFoodSafety: statefoodsafety.com

One finding worth pulling out: the Nebraska Department of Education's refrigeration log instructs that the log be kept for a minimum of one year, and that the manager review, initial and date it each working day. That is one program's requirement for its own form, not a universal legal minimum. It records air temperature only.

Are walk-in cooler temperature logs required by law?

Usually not by the Food Code itself. The FDA Food Code contains no general provision requiring routine recording of walk-in cooler temperatures. It requires the holding temperature (§3-501.16) and the measuring devices (§4-204.112). Recordkeeping obligations attach to specific circumstances — and most often, to something that isn't the Food Code.

Source: FDA Food Code (2022) sections as cited; Indiana Department of Health 410 IAC 7-26; Nebraska Department of Education NSLP HACCP refrigeration log. Verified 21 July 2026. This table lists only requirements we read directly; it is not exhaustive.

Most template pages imply logging is universally mandated. It isn't — and that makes the log's design matter more, not less. A log kept voluntarily, with corrective actions actually written in, is evidence of active managerial control. A log kept as a ritual — three weeks of identical 38°F entries in the same pen, no excursion ever recorded — tells an inspector something specific about the kitchen.

How often should walk-in cooler temperatures be checked?

The Food Code sets no monitoring frequency for a walk-in cooler. Use the interval required by your food safety plan, your regulatory authority, or any program or audit standard that applies to you. Where nothing specifies one, frequency should follow risk.

The inputs that should drive it: how much TCS product the unit holds, how often the door opens, how reliable the unit has been, whether the operation serves a highly susceptible population, and what your plan or authority says. As one documented benchmark, the Nebraska Department of Education's school nutrition form requires manager verification each working day.

The planned template layouts include twice-daily and three-times-daily variants rather than presenting either as universal, because the Code doesn't make one universal.

On continuous monitoring: networked sensors log far more often than any person will and catch overnight failures nobody was present for. They don't produce a probe reading of actual product, and they don't produce the corrective-action record, which is the part a reviewer reads first. Continuous data plus a corrective-action log is a strong record. Continuous data alone is a graph.

What to record when a reading is out of range

Record the facts and let the plan make the decision. Log the reading, the time you found it, the product and quantity affected, what you did, any service ticket number, when the unit returned to range, who decided the disposition, and the manager's review. The job is to make the event reconstructible a year later by someone who wasn't there.

Here is what that looks like in a real public record. A December 2025 Indiana retail food inspection report cites an operator under 410 IAC 7-26-213 — a priority violation — noting that a glass-door cooler measured 44°F, three degrees too warm, and that TCS foods should be moved to a different cooler until the unit maintains 41°F. The same report separately cites the section governing device accuracy, recording a prep cooler thermometer displaying 15°F when the measured temperature was 34°F, with the instruction to replace the thermometer. A 19-degree discrepancy establishes that the instrument was inaccurate — which is exactly why the calibration field and the product-temperature column exist.

Source: 410 IAC 7-26-213, 475, 476 (Indiana Retail Food Establishment Sanitation Requirements). Inspection findings quoted from a published Indiana local health department inspection report, December 2025.

What the log must never do: print a disposition rule. No template should say "discard above X°F." Time, temperature, product type and the food safety plan all bear on that call, and a form can't weigh them.

Thermometer accuracy and calibration

A food temperature measuring device scaled in Fahrenheit must be accurate to ±2°F (§4-203.11(B)). The ambient-air device in the unit only has to be accurate to ±3°F (§4-203.12(B)). Food thermometers must be calibrated according to manufacturer specification, as often as necessary to keep them accurate (§4-502.11(B)). The Code sets no calibration interval.

Because there's no prescribed interval, the calibration confirmation field is doing real work: it turns "we calibrate sometimes" into a dated record. A common practice is checking against an ice-point slurry at 32°F, but the governing instruction is the manufacturer's specification, not a convention.

An unreliable instrument produces an unreliable record, and no amount of neat handwriting fixes that.

How long should you keep temperature logs?

The Food Code sets no general retention period for routine walk-in temperature records, because it doesn't generally require them. Where records are required, the retention period comes from whatever requires them — the HACCP plan, the local rule, the program, the contract or the audit standard.

The one documented anchor we verified: the Nebraska Department of Education's refrigeration log, used in the National School Lunch Program, instructs a minimum of one year for that record. That's one program's requirement for its own form.

If nothing in your situation specifies a period, the requirement lives in whichever document imposed the log in the first place. Start there.

What Indiana's 2025 code change shows about federal summaries

FDA's most recent published adoption report lists the Indiana State Department of Health at the 2001 Food Code, effective 2004. Indiana repealed 410 IAC 7-24 and brought 410 IAC 7-26 into effect on 16 April 2025, with the department stating it would not cite violations under new provisions until 1 January 2026.

We started our jurisdiction verification with Indiana because it's where we work, and it turned out to be the most instructive row in the table.

Under the old rule, Indiana's cold-holding provision (410 IAC 7-24-187) carried the pre-2005 structure: 41°F, or 45°F in existing refrigeration equipment not capable of holding 41°F, provided that equipment was upgraded or replaced by 29 April 2010. That transitional allowance expired long ago. 410 IAC 7-26 replaced it with TCS food terminology, the priority / priority foundation / CORE violation scheme, and the correction deadlines described above.

Two points of precision. First, FDA's report was published on 9 December 2025 — after Indiana's new rule took effect — but the report expressly covers the period ending 31 December 2024. Indiana's April 2025 change fell outside its reporting window. That's a snapshot working as designed, not an error. Second, the Indiana Department of Health states that 410 IAC 7-26 is based on the 2022 FDA model Food Code, so the Indiana row identifies the adopted edition as 2022.

The practical takeaway stands: FDA's snapshot no longer describes every agency's current position. Indiana has changed since the reporting period, and FDA itself flags Hawaii and Virginia as having completed rulemakings with effective dates after it. If the number matters to you, read the jurisdiction's rule.

Sources: Indiana Department of Health, 410 IAC 7-26, effective 16 April 2025; IDOH operator notice on 7-26 adoption; IDOH "Top Changes At-a-Glance," 15 April 2025; 410 IAC 7-24-187 (repealed); FDA 2024 Adoption Report, Table 7 and pp. 3–4.

Limitations

Stated plainly, because a reference that hides its soft spots isn't one.

• Three of 51 jurisdictions are verified against their own regulation. New York, California and Indiana. Of the rest, 43 are Derived and 5 are Unverified. Treat a Derived row as a pointer to the right rule, not as the rule.
• Five jurisdictions have no limit in the table at all — Louisiana, Maryland, New Jersey, South Dakota and Vermont. Their agencies sit on a pre-2005 edition or have no adoption on record, and we'd rather leave a cell empty than fill it with a guess.
• Derived rows assume states adopt provisions unmodified. Many don't. FDA found 61.3% of adopting agencies had implemented at least one provision less stringently than the edition they adopted.
• The federal source is a snapshot dated 31 December 2024. One row has changed since; two more are flagged as pending.
• The roll-up can hide sector splits. In multi-agency states, the restaurant regulator and the retail-store regulator may sit on different editions. Use the agency-level file for that.
• Edition ages are calendar-year differences, not elapsed durations from exact publication dates.
• The 5°F instrument figure is our arithmetic, not a Code provision. It adds two separately permitted tolerances under a worst-case assumption.
• The template comparison covers three files. Two third-party forms plus ours. It supports no conclusion about the wider market.
• This is educational reference material, not legal advice and not a food safety plan. Indianapolis Commercial Refrigeration is a publisher and service-request platform; we don't perform refrigeration service, and we're not a law firm or a health department. For a decision with consequences, read your jurisdiction's rule and talk to your regulatory authority.

Frequently asked questions

What temperature should a walk-in cooler be?

Under the FDA Food Code, TCS food must be held at 41°F or below (§3-501.16), subject to that section's exceptions. That's a limit on the food, not a setting for the box — set the equipment low enough that product stays under the limit under real load. Confirm the limit that applies where you operate; it isn't 41°F everywhere.

Is 40°F or 41°F the right number?

41°F is the Food Code figure. 40°F is widely repeated online but isn't the Code number — it's either a conservative operating target or an error. New York State's rule sets 45°F outside New York City; New York City sets 41°F; California sets 41°F with statutory exceptions at 45°F for six product categories.

Should I record air temperature or food temperature?

Use separate, clearly labeled columns. The 41°F limit applies to food. The device required inside the unit measures air or a simulated product in the warmest part, and only has to be accurate to ±3°F, versus ±2°F for a food probe. An unlabeled single column can't show which measurement it holds.

Are temperature logs legally required?

The FDA Food Code contains no general provision requiring routine walk-in cooler logging. Recordkeeping attaches to approved HACCP plans and variances (§§8-103.12, 8-201.14), and most requirements reach operators through local rules, school nutrition programs or audit standards rather than through the Food Code itself.

How often should temperatures be checked?

The Food Code sets no frequency for a walk-in. Use whatever your food safety plan, regulatory authority or applicable program requires. Where nothing specifies one, let product risk, door traffic and equipment reliability drive it.

What do I write when the cooler is out of range?

The reading, the time found, the product and quantity affected, the action taken, any service ticket number, the time the unit returned to range, the disposition decision and who made it, and the manager's review. Correction windows can be short — Indiana's rule caps the agreed correction period for a priority violation at 72 hours.

Can this template decide whether food must be discarded?

No, and it's designed not to. It records facts. Disposition belongs to the operator under their food safety plan and their regulatory authority, and the log records who made the call.

How long should I keep temperature logs?

There's no general Food Code retention period. The Nebraska Department of Education's school nutrition form instructs a minimum of one year for that record. Otherwise the period comes from whatever required the log — the HACCP plan, the local rule, the program or the audit standard.

Why is there no freezer temperature in the Food Code?

The Code requires covered frozen food to remain frozen but doesn't state a general numeric freezer holding limit the way it states 41°F for cold holding. A freezer target on a log should be labeled as a quality or program target rather than a Code requirement.

Primary sources

• U.S. Food and Drug Administration — FDA Food Code 2022
• U.S. Food and Drug Administration — Adoption of the FDA Food Code by State and Territorial Agencies, 2024 Annual Report
• New York State Department of Health — 10 NYCRR §14-1.40
• New York City Department of Health and Mental Hygiene — Health Code Article 81
• California Health and Safety Code — §113996
• Indiana Department of Health — Food Protection: Laws, Rules and Regulations (410 IAC 7-26)
• Nebraska Department of Education — Refrigeration Log, NSLP HACCP materials