🏠 GEM Resource Hub · 📚 Library · 📘 About RocketLevel · 📘 Playbooks · 🗺️ What's Your Market Worth? · 📅 Book a Call
A resource from RocketLevel for restoration company owners and ops leaders, backed by decades of experience in the trade. About a 6 minute read.
Ask a growing restoration owner why a job went sideways and the answer is often the same: the person did it their own way because there was no agreed way. The knowledge of how your company runs a water loss, bills a job, or handles a customer call lives in a few people's heads, which means quality swings with who showed up and the owner can never fully step away. Standard operating procedures (SOPs) are how you move that knowledge out of memory and into a system. Plenty of SOPs get written once and never opened again. The ones that get used are short, written with the person who does the job, and kept current.
When the process lives in your head, every new hire learns by watching, every result depends on who did the work, and you're both the bottleneck and the single point of failure. A documented business is the opposite: consistent results regardless of who is on the job, faster and cheaper training, and an owner who can be out for a week without the wheels coming off. It's also worth more at sale, because a buyer is paying for a system that runs without you. Write It Down: The SOPs That Make You Sellable covers what a buyer checks.
Don't try to document everything; you'll burn out and quit. Start with the five to ten processes where inconsistency costs you the most, usually the same ones for restoration shops: the first customer call and intake, the water-loss mitigation process, job documentation for the file, billing and collections, and the job closeout. Pick the one that bites you most often and write that first.
There is one exception. A short list of written programs is not yours to prioritize, because OSHA requires them in writing whether or not they are on your top five.
| Written program | What triggers it | Where the rule sits, and what it adds |
|---|---|---|
| Respiratory protection program | You put anyone in a respirator, including on a mold or sewage job | 1910.134(c)(1), plus medical evaluation before fit testing at (e)(1) and fit testing before use at (f)(2). |
| Hazard communication program | You bring hazardous chemicals onto a job site | 1910.1200(e). The employer deadline to update workplace labeling, the program, and training is November 20, 2026 for substances and May 19, 2028 for mixtures. |
| Exposure control plan | Your crews touch blood or other potentially infectious material on trauma work | 1910.1030(c), reviewed and updated at least annually. |
| Permit-required confined space program | Anyone enters a permit-required confined space | 1926 Subpart AA for construction work, not the general industry standard at 1910.146. |
Notes on the table above:
Write those regardless of where they rank on your pain list, because an inspector asking for one does not care how busy you were.
<aside> ⚠️
Do not hand anyone a tight-fitting respirator before the medical evaluation and the fit test are done. 1910.134 puts the medical evaluation at (e)(1) and the fit test before first use at (f)(2), and the respirator itself is chosen against the hazard under the written program, not grabbed off the truck. An SOP can remind the crew of the order. It cannot pick the respirator. Selection belongs to the program administrator 1910.134(c)(3) requires you to designate, working from the standard.
</aside>
The SOPs nobody follows are usually written for the office instead of the field tech. Keep it short and concrete. Name the purpose in a sentence, say who it is for, then give the actual steps in plain, active language: "the tech photographs every affected room before extraction," not "documentation should be performed." Use a checklist where a checklist fits. Add a photo or a screenshot where it helps. If the person who does the job can't follow it on their phone between tasks, it's too long or too vague.
The fastest way to write an SOP that works, and to get it actually used, is to write it with the person who already does the task well. Have them walk you through how they do it, capture the steps, and you have both a good SOP and a team member who is bought in because it's their process on the page. Then test it: have someone else follow it and fix what is unclear before you roll it out.