The First SOP To Write Is The One Costing You The Most. Here Is How To Find It In Five Days.

Think about yesterday. Not a good day, not a bad day. Yesterday.

How many times did somebody call, text, or flag you down in the yard with a question? Count the small ones too.

If you are like most owners doing $500,000 to $5 million, the number is around a dozen. Six minutes each, give or take.

Here is what nobody tells you about an HVAC SOP template, or a plumbing one, or any other. The blank form is the easy part. Picking which process to write first decides whether this works or dies in a folder.

Why most SOP projects die in week two

Most owners start with the SOP that is easiest to write. Truck cleanliness, the morning huddle, something tidy.

Then nothing changes. The phone rings just as much on Thursday. By week two the project is abandoned.

That is not a discipline problem. It is a selection problem. You wrote the comfortable one instead of the expensive one.

First, get your actual number

Put a real number on it before you write anything. That number is usually what makes you do the rest.

Say you log 12 a day for five working days. That is 60 interruptions, at six minutes each.

Line F is the whole point.

Ten hours a week, answering questions a written page could have answered. Not a busy season problem. Every week, forever, until something gets written down.

Run it with your own count. Eight a day is 40 interruptions, and still almost seven hours.

Big Picture: ten hours a week is the reason you cannot take a real day off. Which week were you planning to fix that?

The Repeat Question Log, five days

For five working days you log every interruption. In the moment, not from memory on Friday.

1. Monday morning, open a note on your phone. Title it "Interruption Log." That is the whole setup. Build a spreadsheet and you will quit by Wednesday.

2. One line per interruption. Who asked, what they asked, how many minutes it took.

3. Do NOT filter. Log the ones that felt reasonable. "Can I give this guy 10% off" belongs on the list even when the answer was obvious.

4. Do not fix anything yet. Start writing SOPs on Tuesday and you will never finish the log.

5. Friday afternoon, 15 minutes. Group the repeats, count them, multiply times by minutes.

Nobody has ever been trained on how to handle these situations. They have been trained to revert to asking YOU.

Score it, then apply the two overrides

Times multiplied by minutes is your weekly cost per question. Then two things jump the line.

Override 1, money. Pricing, discounts, collections, purchasing. A wrong guess there costs dollars, not minutes.

Override 2, safety and compliance. Lockout, permits, licensing, refrigerant handling, gas, confined space. First. Always. No matter what the minutes say.

Everything else, take the highest weekly minutes. Here is a plumbing shop's Friday list:

Raw minutes say start with the no show question at 40. The overrides say otherwise.

Right order: permit SOP Monday, comp authority rule second, no show protocol third. All three inside two weeks.

Pick one. Do not build a list of twenty, because you will not write twenty.

Write it in 45 minutes, seven steps

Set a timer. It is what stops you polishing a document nobody has read yet.

Step 1, name it and name the trigger. 5 minutes. "Customer Stuff" is not a name. "No Show Protocol: Customer Not Home At Arrival" is a name. Write the trigger in one sentence starting with When. If you cannot, you picked a topic, not a process.

Step 2, talk it out. 10 minutes. Open the voice memo app and walk the process out loud, like you are teaching an apprentice standing next to you. Say the obvious parts. Especially the obvious parts, because those are only obvious to you.

Step 3, cut it into observable actions. 10 minutes. Play it back and write one line per physical action. If a line has "and" in the middle, split it. Aim for 6 to 12 steps.

Step 4, run the New Hire Test. 5 minutes. Hand the draft to your least experienced person, not your best guy. Ask what they would do, and do not help. Every hesitation is a hole. Fix the line instead of explaining it, because explaining moves it back into your head.

Step 5, define done. 5 minutes. Weak: "Site is left clean." Strong: "Work area vacuumed, packaging bagged and in the truck, photo of the finished area uploaded to the job file." If a third person cannot verify it without asking whoever did it, it is an opinion.

Step 6, assign the role owner and a backup. 5 minutes. Role titles, never names. "Field Supervisor" survives turnover. "Mike" does not.

Step 7, version it, date it, file it. 5 minutes. Version 1.0, today's date, your name. Then put it where a tech in a crawlspace can pull it up on a phone in 30 seconds. A binder in your office does not count.

The verb test, in four trades

Every step starts with a verb you could film someone doing. Call. Text. Photograph. Measure. Collect. A step that starts with ensure, make sure, or handle is a wish.

That last one is the quote follow up process written as a step instead of a hope.

Four weeks, or it is just paper

I spent seven years as a licensed HVAC service technician. Nobody ever handed me a written procedure. Then eight years running operations, where the teams that scaled were the ones that had them. The difference was never the document. It was the rollout.

Week 1, you do it, they watch with a printed copy, marking anything you do that is not written down. That is version 1.1.

Week 2, they do it, you watch. Hands in your pockets. Stop them only for safety, or money leaving the business.

Week 3, they do it and you check the output against your definition of done.

Week 4, they own it. Say it out loud: "This is yours now." Handoffs that are never stated get quietly taken back by both sides.