← Back to Restoration Services Modules
Restoration Services Guide
Writing Down How Your Business Runs
Master the core concepts of writing down how your business runs tailored specifically for the Restoration Services industry.
💡 Core Concepts & Executive Briefing
Understanding Brain-Dumping and SOPs
Restoration businesses run on repeatable steps: how you take initial details, how you assess the damage, how you set equipment, how you communicate with the homeowner and adjuster, and how you close out the job with photos and documentation. That repeatability comes from Standard Operating Procedures (SOPs).
Think of SOPs like the step-by-step playbook your crew follows on every water loss, fire loss, or mold remediation job. When your processes are written down, the work quality stays consistent whether you’re on-site or not. The big goal: create a system where a trained technician or office coordinator can be about 80% effective on day one by following your SOPs—without waiting for you to explain everything.
The Importance of Brain-Dumping
Brain-dumping is the process of getting the knowledge in your head onto paper (or a document system) so others can use it. In restoration, you likely know details that can’t be guessed:
- what “good” looks like during a moisture reading
- how to word an email so the homeowner understands the plan
- which photos to capture for drying and containment
- how to keep notes clean for insurance review
If that knowledge stays in your head, your business growth is capped by your availability. You can’t scale past how many jobs you can personally manage. Brain-dumping fixes that by turning your experience into training material.
Creating Effective SOPs
Write SOPs using three parts:
1. Why: Start with the purpose.
- Example: “Why we document initial readings” is to protect the claim, guide the drying plan, and keep the job moving.
2. What: List the exact steps.
- Example: “What we do at intake” includes confirming loss type, collecting address and contact info, checking for safety hazards, and setting expectations.
3. Outcome: Describe what “done” looks like.
- Example: “Outcome” could be: complete photo set uploaded, initial moisture readings recorded, equipment placed correctly, and customer expectations stated.
For restoration, an SOP outcome should be observable. A job isn’t “handled”—it’s handled when the documentation and job-site setup meet your standard.
Organizing Your SOPs
Store SOPs in one centralized, easy-to-search location. Your “SOP vault” should be the first place your team looks, not the last.
If you’re using a shared drive or knowledge base, structure it by loss type and role, such as:
- Water Damage
- Intake Coordinator SOP
- Tech SOP: Initial Inspection & Moisture Readings
- Tech SOP: Daily Monitoring
- Mold Remediation
- Containment Setup SOP
- Clearance/Closeout Documentation SOP
- Fire & Smoke
- Soot Cleaning Steps SOP
- Odor Treatment Monitoring SOP
When a tech or estimator needs an answer during a job, they shouldn’t have to text you “How do we do this part?” They should be able to search and follow the correct SOP.
The Loom-First Approach
Writing long documents is slow. A faster method that still creates quality SOPs is the Loom-first approach:
- Record yourself performing a task.
- Capture your screen while you show how you enter data, upload photos, or fill out forms.
- Add a quick voiceover explaining the “why” behind key steps.
In restoration, Loom is especially useful for:
- uploading the initial photo set to your job folder
- capturing moisture meter readings and labeling them correctly
- setting up a drying log and entering equipment data
- writing the “customer plan” email and checklist
Your videos become training material for new hires and a reference for your current team.
Building a Culture of Self-Reliance
To make SOPs stick, train your team to check the SOP vault before asking you. This doesn’t mean they never ask questions. It means they come prepared: “I checked the SOP, and I’m unsure about this specific step.”
When someone skips the SOP, quality usually drops silently. In restoration, that shows up as:
- missing photos
- inconsistent equipment logs
- weak claim-ready notes
- confusion with homeowner expectations
A strong SOP culture protects your reputation and speeds up approvals.
When you brain-dump and document your restoration workflow, you build an operation that doesn’t collapse when you’re at a different job, in a meeting, or taking time off. It becomes easier to train, easier to delegate, and easier to scale.
⚠️ The Industry Trap
The “I’ll just tell them” trap hits hard in restoration. Say your lead tech trains a new hire by talking them through moisture readings and photo angles on the first job. It feels fast—until that tech quits or gets pulled to another loss.
Now the new hire is on-site with a water loss, and they start improvising: different photo coverage, notes that don’t match your standard, and equipment placed “close enough.” Weeks later, you’re stuck fixing documentation after the claim is already in review. The problem isn’t effort—it’s that your process was trapped in your voice, not in your SOPs.
Now the new hire is on-site with a water loss, and they start improvising: different photo coverage, notes that don’t match your standard, and equipment placed “close enough.” Weeks later, you’re stuck fixing documentation after the claim is already in review. The problem isn’t effort—it’s that your process was trapped in your voice, not in your SOPs.
📊 The Core KPI
Core SOPs Search-Ready: Track the percent of your core restoration workflows that are documented and stored in one searchable SOP vault. Formula: (Number of core SOPs completed and properly labeled ÷ Total core SOPs you defined) × 100%. Target: 100% for intake, initial inspection, equipment setup, daily monitoring/logging, and job closeout documentation.
🛑 The Bottleneck
Your bottleneck is usually “clarity.” In restoration, delegation fails when the next person doesn’t know your standard for the work. Maybe they can do tasks, but they can’t consistently produce the same results: correct readings, the right equipment sequence, and claim-ready documentation.
So every job turns into a small emergency where you’re the decision-maker and the quality gate. You end up doing rework—adding missing photos, rewriting notes, or correcting equipment/log mistakes—because nobody else has your documented playbook.
Once the SOPs exist, you can delegate with confidence. Until then, you’re stuck as the only person who “knows how it should be done,” and your schedule limits growth.
So every job turns into a small emergency where you’re the decision-maker and the quality gate. You end up doing rework—adding missing photos, rewriting notes, or correcting equipment/log mistakes—because nobody else has your documented playbook.
Once the SOPs exist, you can delegate with confidence. Until then, you’re stuck as the only person who “knows how it should be done,” and your schedule limits growth.
✅ Action Items
1) Brain-dump your core restoration steps: intake, initial inspection, drying/mold equipment setup, daily monitoring/logging, and closeout documentation. For each, list what you check, what you photograph, and what you write down.
2) Build Loom videos for the highest-friction tasks first—usually photo uploads, moisture/meter readings, and how you label and store documentation by job folder. Keep videos short (5–12 minutes) and record the workflow exactly.
3) Turn Loom into SOPs using a consistent template: **Why**, **Steps**, **Outcome checklist** (what must be present when “done”). Add the exact location names your team should use (example: “Job Folder > Photos > Initial > Hallway”).
4) Centralize everything in one searchable SOP vault. Name folders by loss type and role, and make sure every job template links back to the correct SOP.
5) Require self-reliance: before texting you, team members must check the vault and document what SOP step they followed (or where it doesn’t fit the situation). Update SOPs after real job feedback.
2) Build Loom videos for the highest-friction tasks first—usually photo uploads, moisture/meter readings, and how you label and store documentation by job folder. Keep videos short (5–12 minutes) and record the workflow exactly.
3) Turn Loom into SOPs using a consistent template: **Why**, **Steps**, **Outcome checklist** (what must be present when “done”). Add the exact location names your team should use (example: “Job Folder > Photos > Initial > Hallway”).
4) Centralize everything in one searchable SOP vault. Name folders by loss type and role, and make sure every job template links back to the correct SOP.
5) Require self-reliance: before texting you, team members must check the vault and document what SOP step they followed (or where it doesn’t fit the situation). Update SOPs after real job feedback.
Ready to scale your Restoration Services business?
Unlock the full Modern Marks Curriculum and join hundreds of other founders.