How to Write SOPs for a Roofing Company

Every roofing company runs on standard operating procedures. In most of them the procedures live in one person's head, which means the company can only be as consistent as that person's memory and only as large as their attention. Writing SOPs for a roofing company is how the work becomes repeatable by somebody other than you.

The short answer: write a standard operating procedure for every repeatable task, starting with the ones that interrupt you most often. Keep each one short enough that a two-week hire can follow it, and automate whatever the procedure reveals can be automated.

Key Takeaways

• SOPs turn work that lives in your head into work the company owns.
• Start with the tasks that interrupt you most, not with a complete manual.
• Write for someone who started two weeks ago.
• Every procedure you write shows you something that could be automated.
• SOPs are the Operations pillar of the SOG Method — the part that removes you.

Why this is the pillar that frees you

In the SOG Method, Operations is defined as the systems and processes that let a business function without constant oversight. Written procedures are the concrete form of that. Service keeps customers, Growth brings work in, and Operations is the part that decides whether you can leave for a week.

The reason owners resist is understandable. Writing it down feels slower than doing it, and for the first hour it is. The return arrives the third time somebody follows the procedure without asking you anything.

What should have an SOP?

Anything repeatable. In a roofing company that usually means:

• The inspection and documentation process
• How a job gets scheduled and who confirms it
• Material ordering and delivery coordination
• The supplement process, start to finish
• Warranty and callback handling
• Onboarding a new hire in their first week
• The weekly close-out: what gets recorded and where

If two people would do it differently, it needs one.

How to write one that gets used

Four rules. The first one is about where to start, and the other three are about who you are writing for.

Start with what interrupts you

Do not begin with a binder. For one week, note every question that came to you. The three questions that came most often are your first three procedures, and they will buy back the most time immediately.

Write for a two-week hire

Assume no context. Name the tool, name the person, name the next step. A procedure that assumes the reader already knows the unwritten part is the thing you are trying to replace.

Keep it short enough to follow on a phone

Most of your team will read this standing on a driveway. A one-page checklist that gets followed beats a five-page document that gets ignored.

Show it, where showing is faster

Flowcharts are underused in construction. A well-made chart communicates a process faster than dense paragraphs, and it makes gaps obvious in a way prose hides. Map the department at a high level first — the key roles, processes and responsibilities — then break each step into the detail a new hire needs.

Macro chart vs micro chart vs SOP

| | Macro chart | Micro chart | SOP |
|---|---|---|---|
| Scope | A whole department | One process | One task |
| Answers | Who owns what | What order it happens in | Exactly how to do it |
| Audience | Owner and managers | Anyone learning the process | The person doing the task today |
| Best used for | Seeing the business whole | Training new hires | Day-to-day consistency |

The objection every owner has

"My jobs are all different." They are not, and the belief is what keeps the work trapped in your head. The roof is different. The sequence of inspecting it, documenting it, ordering for it, scheduling it and closing it out is close to identical every time, and the parts that genuinely vary are decisions — which is exactly what you want your experienced people spending their attention on instead of remembering which form goes where.

A procedure does not tell a crew lead how to judge a roof. It tells them what to do once they have.

Then automate what the procedure exposes

Writing a procedure almost always reveals steps that no human needs to do. Automate wherever possible — CRM entry, scheduling, follow-up sequences. The order matters: automate a documented process and you get leverage; automate an undocumented one and you get a faster version of a mess.

That is why SOPs come before an automation project rather than after. Our guide on where profit leaks on a roofing job is a good place to look for which processes are actually costing you.

A four-week plan

1. Week one: log every question that comes to you. Write nothing yet.
2. Week two: write the top three as one-page checklists.
3. Week three: hand them to the person who does the task and have them follow it exactly, then fix what was wrong.
4. Week four: map one department as a macro chart and see which processes have no procedure behind them.

Step three is the one nobody skips twice. The first draft of a procedure is always missing the step you did not know you were doing.

Get the playbook

Operations and the SOG Method are a full chapter of the *Roofing Secrets Black Book*, alongside macro and micro charts, KPIs per role and the shift from operator to owner.

Get the Roofing Secrets Black Book at roofingsecretsblackbook.com.