SOPs 101: How to Write Standard Operating Procedures for Your Trade Business (With Examples)

"SOP" sounds like corporate jargon, but it's just a written answer to "how do we do this, every time?" Here's how to write real, usable SOPs for a plumbing, HVAC, electrical, roofing, or landscaping business — with actual examples, not theory.

If you've ever had to explain the same thing to a new hire three different times, or noticed that jobs go differently depending on which tech is running them, that's a sign your business is running on tribal knowledge instead of a system. An SOP — Standard Operating Procedure — is just the fix: a simple written document that says "here's exactly how we do this task, every time, regardless of who's doing it."

It sounds like a corporate concept, but it's just as useful for a five-truck plumbing outfit as it is for a Fortune 500 company. Here's how to actually write one.

What an SOP Is (and Isn't)

An SOP is not a giant manual nobody reads. Good SOPs are short, specific, and usable — something a new hire can actually follow on their first day without asking you ten questions.

A good SOP answers three things: what needs to happen, in what order, and what "done right" looks like. That's it. If it's longer than a page for most tasks, it's probably trying to do too much at once.

Which SOPs to Write First

You don't need fifty SOPs on day one. Start with the handful of processes that come up constantly and where inconsistency actually costs you money or reputation: how to run a job start to finish — arrival, walkthrough, doing the work, cleanup, and customer sign-off; how to handle a customer complaint — so every tech responds the same professional way, not however they personally feel that day; how to close out and invoice a job — so nothing falls through the cracks between "job done" and "invoice sent"; how to onboard a new hire — first day, first week, first 90 days; and how to handle a change in scope mid-job — which ties directly to your change order process.

Once these five are in place, you'll naturally notice the next ones worth writing — usually whatever keeps causing the same small problem more than once.

The Simple SOP Template

Here's a format that works for almost any trade task. Title: name of the task — be specific ("Closing Out a Completed Job" not just "Job Process"). Purpose: one sentence on why this matters. ("Ensures every completed job is invoiced and documented consistently so nothing gets missed.") Steps: first action, second action, third action — in the exact order they should happen. What "Done" Looks Like: a short checklist confirming the task was completed correctly — this is what makes an SOP actually useful for training and accountability, instead of just a suggestion.

A Real Example: "Closing Out a Completed Job"

Purpose: Ensures every completed job is invoiced and documented the same way, so nothing gets missed and payment goes out faster.

Steps: walk the job with the customer and confirm all work is complete and approved. Take before/after photos of the work area. Get the customer's signature (digital or paper) confirming completion. Note any change orders that were approved during the job. Send the final invoice within 24 hours, itemized and referencing the original estimate plus any approved change orders. Log the job as complete in your job tracker, including actual materials and labor time for job costing.

What "Done" Looks Like: customer signature on file, photos saved, invoice sent within 24 hours, and job logged with actual cost data. That's a complete, usable SOP. Any tech or office person could follow it without needing you to explain it in person.

Common Mistakes When Writing SOPs

Writing them too long. If a new hire has to read three pages to learn how to close out a job, they won't actually use it. Keep each SOP to what fits on one page.

Writing them once and never updating them. Your process will change as you learn — SOPs should be living documents, not something you write once and forget. Revisit them every few months, especially in year one.

Making them too vague to be useful. "Do the job well and communicate with the customer" isn't an SOP, it's a value statement. An SOP needs concrete, repeatable steps.

Keeping them in your head instead of in writing. If the only place your process exists is your own memory, the business can't run without you in the room — which limits your ability to hire, delegate, or eventually step back.

Why This Actually Matters for Your Bottom Line

SOPs aren't busywork. They're what let you hire with confidence, because a new tech can follow a written process instead of shadowing you for weeks. Deliver a consistent customer experience, regardless of which tech shows up. Catch problems faster, because when something goes wrong, you can check whether the SOP was followed rather than guessing. And eventually step back from day-to-day work, because the business runs on documented systems instead of solely on you.

The businesses that scale past "just me and a truck" are almost always the ones that wrote this stuff down before they needed to.

Skip the Blank Page

Writing SOPs from scratch is exactly the kind of task that's easy to know you should do and hard to actually sit down and finish — especially when you're busy running jobs. Our Operations Manual Bundle includes pre-written, editable SOPs for the core processes covered in this post — job close-out, customer complaints, new hire onboarding, change orders, and more — built from real time running trade business operations, so you can customize instead of starting blank.

Get the Operations Manual Bundle — $39 for the complete SOP template, technician training manual, dispatch procedures, collections procedures, phone scripts, and emergency protocols.