Cal/OSHA's outdoor heat regulation doesn't care about averages — it cares about specific shifts on specific sites. What the regulation compels, what the per-shift record has to capture, and where a heat complaint actually goes.
The Central Valley hits 100 degrees by mid-June most years. The Inland Empire gets there earlier. The North Coast does it less often, but does it. Cal/OSHA §3395 doesn't care about averages, regional norms, or what the forecast said. It cares whether the temperature on a specific worksite on a specific shift crossed the regulatory threshold — and whether the employer's required protections were in place when it did.
This post is about §3395 in operating terms — what the regulation compels, what the per-shift record has to capture, and where a heat complaint actually goes when an employee makes one.
The regulation applies to all outdoor places of employment in California. Some obligations run at all times; others are keyed to temperature.
Regardless of temperature: the employer must provide fresh, suitably cool drinking water (one quart per employee per hour minimum), train all employees and supervisors on heat-illness recognition and response, and maintain a written Heat Illness Prevention Plan accessible to employees on-site.
At 80°F outdoor temperature: shade becomes a standing obligation — structures sufficient to accommodate the employees on break, located as close as practicable to the work.
At 95°F outdoor temperature: additional high-heat obligations attach:
Acclimatization periods are required for new employees and for any employee returning after a heat-illness event or extended absence.
Each requirement is independently verifiable. The Cal/OSHA inspector who shows up after an employee complaint will look for documentation that the requirements were met for the shifts in question — not the season, not the year, the shifts.
It is tempting to run a short chain here — a safety-order violation is unlawful under §1198, §1198 is a Labor Code section, therefore heat findings behave like meal-and-rest findings. It is a common chain, it turns up in vendor materials across this category, and it does not survive the statute.
Labor Code §2699.3(b)(2)(A) puts a gate in the way. Where the Division of Occupational Safety and Health issues a citation on the noticed condition, the subdivision provides that the employee "may not commence an action pursuant to Section 2699," and the same result follows where a court orders the Division to issue one. On that branch, the matter is an enforcement matter. It is not an aggrieved-employee penalty matter.
The gate is a gate, not a wall. If the Division does not inspect, §2699.3(c) supplies a pathway instead. Which branch a particular set of facts takes is a legal question about that employer, that notice, and that condition — your counsel's to answer, not a website's and not ours.
What that leaves is the more durable point, and the one that does not depend on how any of this resolves: the §3395 written plan and training documentation are not something you build in order to buy a position. You owe them already. The written plan, the training documentation, the high-heat procedures — the regulation compels all of them whether or not anyone helps you keep them. There is no lawful posture in which they do not exist, which means there is no marginal downside to keeping them well.
Where the record does work on the enforcement side, it works on classification rather than on penalty arithmetic. Labor Code §6432(b)(1) directs the Division, before issuing a serious violation, to consider evidence the employer provides about its training, its procedures for discovering and correcting hazards, and its supervision. Section 6432(c) lets an employer rebut the presumption that it knew of the condition. Both provisions are addressed to documents. An employer holding a dated per-shift record is inside the conversation §6432 describes. An employer without one is outside it, arguing from recollection.
Be clear about where this next part comes from. Section 3395 compels the written plan, the training, and the high-heat procedures. It does not compel a per-shift log, and anyone who tells you it does — including a vendor — has read a best practice back into the regulation. What follows is our practice, adopted because §6432(b)(1) points the Division at documents before it classifies a violation as serious, and because recollection is a poor exhibit three years later.
On that basis, the record we build carries, per shift on a triggering day:
We keep it per shift, per site, per day the threshold was crossed. The HIPP is the compelled document, and it establishes the policy. It does not establish that the policy held on the shift someone later asks about. Nothing obliges an employer to close that gap. It is simply the gap every heat complaint lands in.
Three failure modes recur:
The HIPP exists, the per-shift record doesn't. Most established firms have a written Heat Illness Prevention Plan, often produced from a template by an HR consultant or a trade-association resource. The plan is fine. The per-shift evidence that the plan was implemented isn't there, or exists only in a foreman's notebook that hasn't been digitized.
The training was annual, the documentation wasn't. Cal/OSHA requires training before exposure to outdoor heat — usually at hire and at the start of each heat season. Employers do the training; many don't retain per-employee completion records in a form that survives a records request three years later.
The acclimatization period is ad hoc. Cal/OSHA's standard requires close observation of new employees for the first 14 days of exposure to high-heat conditions. Most field foremen are doing this informally; few firms have a documented acclimatization protocol with a per-employee record of close observation during that window.
Only one of the three is a gap in a record the employer was already obliged to keep: the training documentation, which runs through the IIPP at 8 CCR 3203(b)(2). The other two are gaps in evidence rather than gaps in compliance — a smaller problem right up until the day someone asks the employer to prove a particular shift. The cure for all three is the same: structured per-shift capture tied to the existing timekeeping system, with the foreman or supervisor as the per-shift signatory — and, more to the point, a correction field alongside the finding. A record that says the water ran out and stops there is a record of a violation. A record that says the water ran out, names who was sent for more, and closes the item is something else. Neither the regulation nor §6432 asks whether the response succeeded. They ask whether there was one.
MicroForensics treats §3395 as a first-class capture surface for construction operators. On any shift where the recorded temperature at the worksite crosses the 80°F or 95°F thresholds, the platform routes a per-shift confirmation to the foreman covering water, shade, rest provision, pre-shift meetings, and any incident response. Anything answered as an exception opens an item, and the item stays open until someone enters what was done about it. The output is a dated per-shift record of what the crew was given and what was done when the plan didn't hold. Section 3395 compels the written plan, the training, and the high-heat procedures; it does not require a per-shift log. We build one anyway, because §6432(b)(1) directs the Division to weigh training, hazard procedures, supervision, and safety communication before classifying a violation as serious, and because an inspector or a records request asks for something more specific than a plan. That is a classification argument, not a logging requirement. Assume everything we generate is produced in discovery. That is why the correction field is mandatory.
Bilingual where the crew composition requires it. Integrated with the timekeeping platform the firm already runs. No new app for the foremen — the attestation routes via SMS or a short web link the foreman opens at the end of the shift.
Three operational habits, in priority order:
Capture the temperature at the worksite, per shift, on every day the forecast says you'll cross 80°F. A foreman's reading on a calibrated thermometer is sufficient; the regulation doesn't require sensor infrastructure. The record is the point.
Document the pre-shift high-heat meeting on 95°F+ days. A list of attendees and a one-line topic summary. The meeting is short and the record is short.
Build acclimatization tracking into your onboarding workflow. New employees in heat-exposed roles get close observation for 14 days. Document who observed them, on which shifts, and any responses to early-heat-stress signs.
The work is operational, not technological. It can be done on paper. The reason it usually isn't done is that the foremen who would produce the record don't have a workflow that asks them to. MicroForensics is one way to add that workflow without making the foremen learn new software; the same outcome can be reached with a one-page paper form and a folder, if the paper-form-and-folder process is actually run.
If you'd like a walk-through against your current §3395 posture, the discovery call is the right starting point.