There Is No Federal Heat Standard Yet. Seven States Have Their Own, and They Don't Agree.

A logistics operator with distribution centers in California, Texas, and Ohio asks a reasonable question after a heat-related incident at the Sacramento facility: is our heat policy compliant everywhere we operate? The honest answer is that "our heat policy" is not one thing to be compliant or non-compliant. California has an enforceable indoor and outdoor heat standard with specific temperature triggers. Texas and Ohio have no state heat standard at all, which means those two sites are governed by whatever OSHA can support under the General Duty Clause — a real basis for a citation, but not a rule with a published trigger. A single written policy applied identically across all three locations is either over-built for two of them or under-built for the third, and there is no way to know which without checking site by site.

The federal rule that isn't a rule yet

OSHA published a proposed standard, Heat Injury and Illness Prevention in Outdoor and Indoor Work Settings, in the Federal Register on August 30, 2024. An informal public hearing ran from June 16 through July 2, 2025, and the post-hearing comment period closed on October 30, 2025. Following a regulatory freeze that began in January 2025, the rulemaking has stalled, and as of this writing OSHA has not set a target date for a final rule. For a multi-site operator, that means there is no federal heat standard to build a single national program against — only the General Duty Clause, which requires OSHA to prove a recognized hazard and a feasible means of correction after the fact, rather than a program built around a published trigger in advance.

OSHA has not stepped back from heat enforcement while the rule sits idle. The agency renewed its Heat National Emphasis Program on April 10, 2026, for a five-year term, directing inspectors to prioritize proactive inspections across 55 high-risk industries on any day the National Weather Service issues a heat advisory for that area. The NEP is a national enforcement priority, not a standard with its own compliance requirements, but it changes the odds: a site in a targeted industry, in a region under a heat advisory, is measurably more likely to see an inspector show up than the same site was five years ago.

Seven states didn't wait

While the federal rule sits in limbo, seven states have adopted their own enforceable heat illness standards: California, Colorado, Maryland, Minnesota, Nevada, Oregon, and Washington. None of them share the same scope, and that variation is the actual operational problem for a company with sites in more than one of them.

California's standard is the most comprehensive of the seven, covering both indoor workplaces (with the program activating at an 82°F indoor heat index) and outdoor workplaces (activating at 80°F), with additional high-heat procedures required above 95°F in specified high-hazard industries. Maryland's Heat Stress Standard, codified at COMAR 09.12.32 and in effect since September 30, 2024, applies to all workplaces, indoor and outdoor, once the heat index reaches 80°F — a single trigger with no separate high-heat tier. Colorado took the opposite approach on scope: its standard, amended effective January 1, 2026, applies only to agricultural employers, activates at 80°F, moves to mandatory ten-minute rest breaks every two hours at 95°F, and carries a hard calendar deadline requiring annual training to be completed by April 20 each year — a requirement with a fixed date rather than a rolling one. Washington's standard covers outdoor heat exposure only. Minnesota's covers indoor heat exposure only. Oregon and Nevada, like California, cover both indoor and outdoor work.

Read across those seven states, there is no pattern a national policy can quietly absorb. A company that writes one heat program calibrated to California's dual indoor-outdoor structure will over-apply it in Washington, where the state has never regulated indoor heat exposure at all. A company that models its program on Colorado's agricultural-only standard has built something that doesn't extend to its distribution centers, which is a different sector entirely. And a company operating only in states without their own standard is not exempt from anything — it is relying entirely on the General Duty Clause, the least specific enforcement basis of any option on this list.

Why "one heat policy" is the wrong artifact

The instinct to write a single corporate heat policy and roll it out everywhere comes from a reasonable place: consistency is usually the right answer for a multi-site safety program, and heat is exactly the kind of hazard that seems like it should have one answer. But heat illness prevention is regulated per jurisdiction, not per company, in a way that some other hazards are not. A lockout/tagout program can be genuinely uniform across every site because 29 CFR 1910.147 applies the same way everywhere. A heat program cannot be genuinely uniform, because a fourth of the states an operator might be in have no standard, and the states that do have one disagree with each other on trigger temperature, on whether indoor exposure counts, and on which industries face the strictest tier.

The workable structure is a shared framework with site-specific activation. Every location gets the same underlying elements — monitoring, water access, shade or cooling, training, an acclimatization protocol for new and returning workers, and an emergency response plan for heat stroke — because those are sound practice regardless of jurisdiction and defensible under the General Duty Clause even where no specific standard applies. What has to be site-specific is the trigger: the temperature at which the program activates, whether it activates for indoor exposure at all, and what the high-heat tier requires once activated. A site in Maryland needs one trigger. A site in California needs two, with different numbers for indoor and outdoor. A site in Texas needs a program built to satisfy a general-duty inspector's judgment about what a "recognized hazard" required, which is a different exercise entirely.

What corporate can actually verify

For a safety function overseeing multiple sites, the useful question isn't "do we have a heat policy" — every site probably does. It's whether each site's policy has the correct trigger for its jurisdiction, whether the indoor/outdoor scope matches what that state actually regulates, and whether a site in a state with no standard has documented the general-duty basis for its program rather than assuming the corporate template covers it. That's an audit question with a clear answer per site, even though the answer isn't the same answer everywhere.

Consistency, in this specific case, means every site is verifiably using the standard that actually applies to it — not that every site is using the same number.

There's a second wrinkle worth building into the audit: state standards are not static. Colorado's rule only reached its current form on January 1, 2026, and Maryland's has been in force since late 2024 — both recent enough that a site opened or acquired before those effective dates may be running a program written against an older baseline. An acquisition brings its own history here too. A company that buys a facility in a state with a heat standard inherits whatever heat program that site had, correct or not, and "we've always done it this way" is not a defense that transfers with the deed. The integration checklist for a newly acquired site should include a heat-standard check for its state, on the same footing as the safety-record review any acquisition already gets.

Our Heat Index Tracker & Action Plan gives a site a consistent format for logging daily conditions and the actions triggered at each threshold; the sheet is the same at every location, but the trigger temperatures entered on it have to come from whichever standard — state or, absent one, General Duty Clause practice — actually governs that site.