Stop calling a PDF a smoke protection program.

Version a smoke protection plan and attach the communication note and respirator checklist inspectors ask for. RestShade watches smoke at every site, keeps the daily record, and applies the tier that day requires. Most days you do nothing. When smoke crosses, it flags the site and pings the right people.

The problem

A plan without a log is a brochure. Smoke season produces a lot of group texts and almost no records.

How RestShade helps

RestShade versions the written smoke plan and pairs it with the daily reading, the note describing what you told the crew, and the respirator step for that tier.

What you walk away with

A versioned smoke plan you can produce on request
A dated reading and communication note for each smoke day
Clear separation between voluntary N95s and required respirator use

What RestShade handles

State triggers built in for California, Oregon, and Washington
Two-way communication note stored with the reading
Respirator plan kept next to the smoke plan
Smoke training in English and Spanish with acknowledgments

How it works

RestShade versions your smoke plan Communication methods, controls, and respirator steps become a written plan with version history.
Air quality is watched at every site State-specific PM2.5 and AQI thresholds evaluate in the background.
Smoke days become dated records Reading, communication note, duties, and training status land in one packet.

Frequently asked questions

Do the triggers differ by state? Yes, substantially. Washington starts at PM2.5 20.5, Oregon at 35.5, and California at AQI 151. RestShade applies the pack for the site state.
What goes in the communication note? The reading you shared, the protective measures available, and how workers can report symptoms or worsening air.
Is a respirator plan separate from the smoke plan? RestShade keeps a written respirator plan alongside the smoke plan, because required use brings obligations the smoke plan does not cover.