Two-way smoke communication that counts
Every smoke rule requires communication in both directions. A screenshot in a group chat is not that.
California, Oregon, and Washington all require two-way communication during a smoke event. The outbound half is easy: tell the crew the current number and the protective measures. The inbound half is the one that gets missed: employees have to be able to report worsening conditions and symptoms without fear of reprisal, and somebody has to be listening.
Takeaways
- Build a communication system that satisfies both directions.
- Write a log note that shows communication happened rather than that it was possible.
- Handle lone workers, who need a different mechanism.
- Understand why the no-reprisal element is part of the requirement.
Both directions, explicitly
Building a system that works on a job site
Lone workers need a different mechanism
What to write on the log
Why no reprisal is in the rule
Frequently asked questions
- Does a group text satisfy two-way communication? It can, if the crew can reply, the replies go to someone who acts, and everyone can read the language used. What fails is a broadcast-only channel or a thread nobody monitors.
- How often do I have to update the crew? When conditions change materially, and at the start of the shift. Smoke moves, so a single morning update is not enough on an active fire day.
- Who has to receive the reports? Someone with authority to act: a supervisor, foreman, or safety lead who can move the crew, hand out respirators, or stop work. A reporting channel to someone who cannot act does not help.
- Do I need to log every conversation? No, but log the substance: the number communicated, what the crew was told, and anything reported back with what you did about it. That is a short note, not a transcript.