SOPs & Process Documentation

The 14 core HVAC procedures, how to write them, and how to make the team actually use them.

Why Write It Down

An SOP-free shop runs on tribal knowledge — what's in the owner's head, what the senior tech "just knows," and whatever the newest hire picks up by watching. This works until someone leaves, gets sick, or makes a mistake nobody catches until the customer complains.

Written processes create consistency. Every tech runs the call the same way, every invoice follows the same format, every complaint gets the same escalation path. The output is predictable — which is what customers, employees, and buyers all want.

The 14 Core Procedures

An HVAC business runs on roughly 14 procedures across three categories (ToolFluency, JordanWorx). Not every shop needs all 14 on day one — but by the time you have 5+ techs, the ones you're missing will be the ones causing problems.

The service call (4 procedures)

Install & maintenance (3 procedures)

Business operations (7 procedures)

All SOPs "defer to a certified HVAC technician, EPA Section 608 rules, and applicable codes" for regulated work (ToolFluency).

SOP Format

Keep it simple. A useful SOP fits on one page and has five parts:

1. Purpose — one sentence on what this covers and why
2. Applies to — who follows this procedure (techs, CSRs, office staff)
3. Steps — numbered, specific, in order. "Check refrigerant pressure" not "ensure proper operation."
4. Quality checklist — what to verify before marking the task complete
5. Required materials — tools, forms, templates, software needed

Training Methodology: See One, Do One, Teach One

The trades version of TWI (Training Within Industry) — the 1940s methodology that Toyota adopted for production line training. It works because trades skills are physical, not theoretical.

1. See one — ride along, watch the senior tech do it, take notes
2. Do one — perform the task with the senior tech watching, getting real-time coaching
3. Teach one — explain the process to someone else. Teaching forces understanding.

This is the methodology behind ride-alongs, which every coaching org uses. New techs get 2–3 ride-alongs per week for the first 90 days, then 1 per week until they're independent. Experienced techs get 1 per month for ongoing quality assurance.

Improvement Cycles

SOPs are living documents. When a callback reveals a gap, when a customer complaint exposes a missed step, when a new tool changes the process — the SOP gets updated.

The cycle: Plan → Do → Check → Act (Deming/PDCA). In contractor language:

1. Plan: Identify the problem, decide what to change
2. Do: Update the SOP, train the team on the change
3. Check: Measure whether the change worked (callbacks down? completion time improved?)
4. Act: Keep the change or try something else

Review SOPs quarterly. If a procedure hasn't been updated in a year, either the process hasn't changed (unlikely) or nobody is reviewing it.

Where to Start

Don't try to write all 14 at once. Start with the three that cause the most problems:

1. Service call process (procedures 1–4) — directly drives callback rate, customer satisfaction, and revenue per call
2. Call booking (procedure 8) — directly drives booking rate, which is the top-of-funnel metric
3. Invoicing & collection (procedure 11) — directly drives cash flow

Add the rest over 3–6 months. Each new SOP gets introduced during a weekly team meeting, practiced on ride-alongs, and enforced through the quality checklist.