π GEM Resource Hub Β· π Library Β· π About RocketLevel Β· π Playbooks Β· πΊοΈ What's Your Market Worth? Β· π Book a Call
<aside> π
Get your own copy
Make one copy per process. Name the file after the process, not after the person who runs it today.
</aside>
The blank behind Document Your Business: Writing SOPs People Actually Use. That page tells you which process to write first and how to get it used. This is the page you write it on.
<aside> π
Who this is for. Owners and managers who want a process done the same way no matter who is on the truck or at the desk. Write it with the person in your shop who does the job best.
</aside>
<aside> β οΈ
Reviewed October 2026. OSHA standards change, and some states run their own plans. Confirm with your state agency or a safety advisor before you rely on this list.
When not to use this template. Some safety programs have to be written, and OSHA spells out what goes in them. Those will not fit on one page, so do not build them here:
Build those from the standard with your safety advisor. The OSHA Programs a Restoration Shop Actually Needs shows which ones your work triggers. A one-page SOP can still remind a crew what order to do things in. It cannot stand in for the program.
</aside>
Every standard operating procedure (SOP) in the shop uses the same eight parts in the same order, so anyone who has read one can find their way around the next.
Under the eight parts sit two tables: a sign-off table for everyone trained on this version, and a change history.
<aside> π
Keep every old version. Date and number each version, and never overwrite the last one. If a job is ever questioned, the version that matters is the one that was in force on the day of the job, not the one in the binder today.
</aside>