The Growth Room
← All guides

HVAC SOPs: How to Build an Operations Manual (With Templates) (2026)

How to write HVAC standard operating procedures: which 12 SOPs to write first, a one-page template, a sample SOP, and how to keep your team actually using them.

Most small HVAC shops run on the owner's memory. The owner knows how a call should be booked, what a tech should say at the door, which parts go back on the truck, and how the deposit gets to the bank. When the owner is on a job, on vacation, or sick, the shop runs on guesses. That's when calls get booked wrong, invoices go out late, and the same callback happens twice.

A standard operating procedure (SOP) is just a written answer to "how do we do this here?" An operations manual is a set of those answers kept in one place. You don't need a binder of 200 pages. You need a dozen short, one-page SOPs for the jobs that happen every day and cost you money when they go wrong.

This guide covers why SOPs matter for a 1–15 truck shop, which ones to write first, a one-page template, how to write them without losing a month, where to store them, how to keep them in use, and a filled-in sample. Nothing here is legal, tax, or safety advice. Check safety and employment rules with your insurance carrier, accountant, and a local attorney.

Why write SOPs at all

  • You stop being the bottleneck. If every question comes to you, you can't sell, plan, or take a day off. Written steps answer the routine questions so people only call you for the unusual ones.
  • Training gets faster and more even. A new hire can read the SOP, watch it done, then do it with the checklist in hand. Every trainer teaches the same way.
  • Customers get the same experience every time. Same greeting, same shoe covers, same options presented, same follow-up. That consistency is what earns reviews and repeat work.
  • Mistakes become fixable. When something goes wrong, you can ask "did we follow the SOP?" If yes, fix the SOP. If no, fix the training. Without a written process, it's just blame.
  • The business is worth more. A buyer or a future manager is buying a system, not a person. A shop that runs on written processes is easier to hand off. See the HVAC business valuation calculator for how buyers look at a shop.

Which SOPs to write first

Start with the processes that happen every day, touch the customer or the cash, and break most often. Here are 12 that cover most of a service shop's week. Write them roughly in this order.

  1. Call booking. Greeting, what to ask, how to set expectations on price and arrival window, and how to book into the right slot. Pair this with the call booking rate and CSR guide.
  2. Dispatch. How jobs get assigned, who gets emergencies, how to handle a running-late tech, and when to call the customer. The HVAC dispatch and scheduling guide covers the decisions behind this one.
  3. Service call: arrival and diagnosis. Call-ahead, parking, greeting, shoe covers, listening to the customer, the inspection steps, and what gets photographed.
  4. Service call: presenting options. How findings are explained, how options are shown, and what happens if the customer wants to think about it. If you use tiered options, link to your good-better-best pricing approach.
  5. Install day. Pre-job confirmation, material check, floor protection, removal and disposal, startup and commissioning steps, cleanup, and the customer walkthrough.
  6. Job close-out and invoicing. Notes, photos, parts used, invoice created and sent or paid on site, and the job marked complete the same day. The cash flow and getting paid guide covers why same-day invoicing matters.
  7. Callbacks. How a callback is booked, who goes, what gets recorded, and how the cause is reviewed. See how to reduce HVAC callbacks.
  8. Truck stock restock. The standard stock list, when and how parts are restocked, and who checks it.
  9. New-hire onboarding. Paperwork, truck, logins, ride-alongs, and check-ins. The 90-day tech onboarding plan is already most of this SOP.
  10. Maintenance agreement visit. The checklist for the tune-up, what gets recorded, how the next visit gets scheduled, and how renewals are handled. See the maintenance agreements guide.
  11. Cash and check handling, deposits. Who can collect, how payment is recorded, where checks and cash go, and when deposits are made. Two people should touch cash, not one.
  12. End of day. Open jobs updated, time entered, truck restock list sent, tomorrow's first job confirmed, and anything unsold logged for follow-up (see the unsold estimates follow-up playbook).

Later additions: estimate follow-up, warranty claims, supply house ordering, refrigerant tracking, vehicle inspections, accounts receivable follow-up, and the weekly numbers review.

The one-page SOP template

Every SOP uses the same six parts. If it doesn't fit on one page, split it into two SOPs.

SOP: [Name] · Version: [#] · Last reviewed: [date]

  • Purpose: One or two sentences: why this process exists and what goes wrong without it.
  • Owner: The role (not a person's name) responsible for keeping this SOP accurate and making sure it's followed. Example: Service Manager.
  • Trigger: What starts this process. Example: "Phone rings" or "Tech marks job complete."
  • Steps: Numbered, one action per step, each starting with a verb. Note who does it if it changes hands. Link to scripts, forms, or videos rather than pasting them in.
  • Done when: The test that proves it's finished. Example: "Invoice sent, payment recorded, job status = Complete, photos attached."
  • Checklist: The 5–10 items someone ticks off in the field or at the desk. This is the part people actually use day to day.

A few rules that keep SOPs usable:

  • Name roles, not people. "CSR" or "Lead Tech," so the SOP survives staff changes.
  • Start every step with a verb. "Confirm," "Photograph," "Send."
  • Put the checklist on the phone or truck. The steps explain; the checklist gets used.
  • Version and date every SOP. When you change it, bump the version and tell the team.

How to write them without losing a month

Record your best person doing it. Don't write from a blank page. Ride along with the tech who does the job best, or sit next to the CSR who books the most calls. Record video or audio (with their permission and the customer's, where required), or just take notes. Ask "why do you do it that way?" as you go. The best tech's habits are your first draft.

Write the checklist first. List the 5–10 things that must happen for the job to be done right. That's the core of the SOP. Then add the numbered steps only where the checklist needs explaining.

Keep the first draft rough. Write it in 30–45 minutes. A rough SOP that exists beats a perfect one that's still in your head.

Test it with someone who didn't write it. Hand it to a newer tech or CSR and have them follow it exactly. Every place they get stuck or ask a question is a gap to fix.

One SOP a week. At that pace you'll have the 12 above in about three months, without taking time away from running the shop. Some owners have each lead tech or CSR draft the SOP for their own area and then review it together.

Where to store them

Pick one place and put everything there. What matters is that anyone can find the current version from their phone in under a minute.

  • A shared drive folder (one document per SOP, a simple index document on top). Cheap and easy to start.
  • Your field service software. Many platforms let you attach checklists or forms to job types, so the maintenance checklist opens on every maintenance job. This is the best way to make checklists get used. The field service software comparison covers what to look for.
  • A wiki or knowledge-base tool if you grow past 20–30 SOPs and want search and version history.
  • Printed copies of the key checklists in each truck and at the office desk, marked with the version number so old copies are easy to spot.

Whatever you choose, keep one master copy. Two versions of the same SOP is worse than none.

How to keep SOPs used (not just written)

Most operations manuals die in a folder. These habits keep them alive.

Train from them. Every new hire goes through the SOPs for their role in their first weeks, and signs off on each one after doing it with a trainer watching. Build this into your onboarding plan.

Review on a schedule. Each SOP owner reviews their SOPs at least once a year, and right away when something changes: new software, new equipment, new pricing, or a mistake that the SOP didn't prevent. Put the review dates on a calendar.

Audit a few jobs every week. Pick two or three completed jobs and check them against the checklist: photos attached, notes complete, invoice sent, options presented. Do the same for a few recorded calls against the booking SOP. Share what you find as coaching, not punishment.

Fix the SOP, not just the person. When a mistake happens, ask whether the SOP was clear. If three people make the same mistake, the SOP is the problem.

Talk about one SOP per team meeting. Five minutes: what's working, what's confusing, what should change. The people doing the work will improve the process faster than you can.

Tie it to pay and reviews where it makes sense. If your pay plan has quality measures, the SOP checklist is a fair way to measure them. See the tech pay plan calculator and the commission and spiff pay plans guide.

Sample SOP: Job close-out and invoicing

This is an example to adapt. Change the steps to match your software and payment process.

SOP: Job Close-Out & Invoicing · Version: 1 · Last reviewed: [date]

Purpose: Make sure every completed job is documented, invoiced, and paid or scheduled for payment the same day, so we get paid faster and callbacks have a record.

Owner: Service Manager (office side: Office Manager)

Trigger: Tech finishes the work on site and is ready to leave.

Steps:

  1. Test the system and confirm it's running as expected before packing up.
  2. Take "after" photos: equipment, data plate, work area, any parts replaced.
  3. Enter job notes: what you found, what you did, readings taken, and any recommendations the customer declined.
  4. Add every part and material used to the job so truck stock and job cost are accurate.
  5. Review the invoice with the customer: work done, price, warranty terms.
  6. Collect payment on site per the payment SOP, or confirm the approved billing terms (for example, commercial net terms) are on the account.
  7. Send the invoice or receipt by email, or by text only if the customer has agreed to receive texts.
  8. Log any declined options as an open estimate for follow-up.
  9. Mark the job Complete in the software before driving to the next call.
  10. Office: check all jobs marked Complete by end of day. Any missing notes, photos, or payment go back to the tech the same day.

Done when: Job status = Complete, photos and notes attached, parts entered, invoice sent, and payment recorded or approved terms on file.

Checklist (tech):

Once this SOP is in place, the job profit calculator and the days sales outstanding calculator are good ways to check whether it's working: cleaner job costs and faster payment.

Quick-win checklist

Borrow a checklist

The best SOP is often one another shop already wrote for the same problem; swap yours in the Growth Room Discord.