Write the SOP. Skip the Bloody Binder.

Your crew does not need a 94-page monument to your good intentions.

They need to know what to do, what good looks like, and who to call when the normal process stops making sense.

That is an SOP. The binder is optional. Usually, it’s the problem.

An SOP is one agreed way to do one job

SOP stands for standard operating procedure. In plain English: these are the steps we use to get this task done correctly, every time.

Not an employee handbook. Not a job description. Not “use your initiative,” dressed up with a company logo.

A useful SOP covers one repeatable task:

• Open the shop before the first customer arrives.
• Check in a new gym member.
• Send an estimate after a site visit.
• Close out a completed service job.

“Run the service department” is not one task. Neither is “handle customers.” Those are buckets containing dozens of tasks, exceptions, and opportunities for expensive improvisation.

Keep each SOP to one page. If it needs six pages, narrow the task or link to separate technical instructions. Don’t shrink the font until your plumber needs a microscope.

One page is a usability rule, not permission to leave out required safety procedures or compliance records.

Start with the mistake that keeps charging you rent

Don’t document everything alphabetically. Start with a frequent task that creates rework, delays, customer complaints, or repeated questions.

Here’s an illustrative example.

Four technicians each lose 15 minutes a day hunting for missing job information. That’s one hour across the crew each day. Over five days, it’s five hours.

At a loaded labor cost of $40 an hour—including wages, payroll taxes, and benefits—that’s $200 of paid time a week. Across 50 working weeks, it’s $10,000 of labor capacity spent playing detective.

That does not mean an SOP magically deposits $10,000 in your bank account. If payroll stays the same, you’ve recovered time, not cash. You improve net profit only if that time produces useful work, reduces overtime, or avoids another expense.

But wasted field time still puts pressure on labor percentage and gross margin. Before blaming pricing, check whether the crew spends half the afternoon reconstructing what happened yesterday.

Pick the task with the clearest recurring cost. Fix that first.

Build the page around the actual work

Watch a competent employee do the task. Ask them where people get stuck and what they check automatically.

Then write the page together. Your best employee knows details you won’t remember from behind a desk.

Use this structure:

• Task: A specific name beginning with a verb.
• Owner: The role responsible for completing it.
• Start: The event that triggers the procedure.
• Steps: Short actions, in the order they happen.
• Done: The evidence that the task is complete.
• Exception: When to stop and who decides what happens next.
• Maintainer and date: Who updates the page, and when it last changed.

Write observable instructions. “Provide excellent service” is useless. “Show the customer the completed work and ask whether anything remains unresolved” tells someone what to do.

Use the button names from your actual software. Add a screenshot if finding the right field is the hard part. Cut any sentence that doesn’t help someone complete the task.

Here’s what a usable SOP looks like

This example is for a service business that collects payment after completing an authorized job. Adapt it to your actual payment terms and systems.

Task: Close out a completed service job

Owner: Assigned technician.

Start: The work and required technical checks are complete, before leaving the property.

• Compare completed work with the approved scope. If they differ, stop and call the service manager before issuing the invoice.
• Attach the required completion photos to the job record. Follow company privacy rules; avoid people and unrelated personal belongings.
• Record what was completed, any required readings, and any unresolved issue in the job notes.
• Show the customer the completed work. Explain any operating or care instructions relevant to the job.
• Check the invoice against the approved work and payment terms. Collect payment through the approved system if due. Never write card details in job notes.
• Send the invoice or receipt through the system and confirm the destination address with the customer.
• Select the correct final status: completed and paid, completed with payment pending, or follow-up required.

Done: Photos, notes, invoice, and payment status are saved. Any follow-up has a named owner and due date.

Exception: For a dispute, absent customer, payment failure, or system outage, contact the service manager. Don’t invent a discount or mark an unpaid job paid.

Maintainer: Service manager. Last updated: [date].

That page supports cash flow and prevents the sloppy handoffs that turn into bad reviews. It doesn’t attempt to teach the entire trade.

Test it before calling it finished

Hand the page to someone who didn’t write it. Have them perform the task while you watch.

Don’t narrate. Every rescue you provide reveals a missing or unclear instruction.

Then test it on five real jobs. That’s a practical starting target, not an industry benchmark. Check whether the records are complete and whether exceptions reach the right person.

Put the SOP where the task happens: inside the job template, beside the workstation, or behind a clearly labeled mobile link. One current version. Archive the old one.

When turnover happens, the next hire should inherit instructions, not office folklore. When people skip a step, check whether it’s unclear, inaccessible, or genuinely unnecessary before declaring everyone lazy.

Monday morning: fix one repeat offender

Pick one recurring mistake. Spend 20 minutes watching the task. Draft one page with the employee doing it.

Test it that afternoon. Name its maintainer. Check the next five completed jobs.

Don’t build a library. Make one annoying, expensive problem stop happening.