Skip to content
Gustry

Free template · Operations

SOP Template

A standard operating procedure template gives you a fixed structure for writing down a repeatable task: what the procedure covers, who owns it, what is needed before starting, the numbered steps, and how you know the work was done correctly. Fill it in once for a job you repeat weekly and anyone on your team can run that job the same way.

Updated August 2026

What to include in your SOP Template

  • Procedure title written as the task, for example "Close out a residential cleaning job"
  • Purpose in one or two sentences: what this procedure prevents or guarantees
  • Scope: where it applies and where it explicitly does not
  • Owner and approver, by role rather than by person's name
  • Version number, effective date and next review date
  • Prerequisites: access, tools, materials, information needed before step one
  • Numbered steps in the order they happen, one action per step
  • Decision points written as if/then, so the reader knows what to do when reality differs
  • Quality checks and the definition of done
  • Escalation path when something blocks the step
  • Change log noting what changed and when

Practical guidance

How detailed should an SOP be?

Write to the least experienced person who will realistically perform the task. If a new hire in week one has to guess, add a step. If an experienced tech would find it patronizing and the consequence of a mistake is small, compress it. Screenshots and photos beat adjectives for anything involving software or physical setup.

Naming and versioning

Use a predictable file name so procedures sort themselves: area, task, version. For example OPS-Close-Out-Residential-Job-v1.2. Keep one live version and archive the rest. A short change log at the bottom of the document is enough for most small teams; you do not need document management software.

Keeping SOPs alive

  • Set a review date on every procedure, six or twelve months out.
  • Update the SOP as part of fixing an incident, not as a separate project.
  • Ask new hires to flag anything unclear in their first month; they are your best reviewers.
  • Track which procedures exist in one simple index so gaps are visible.

How to use this template

  1. 1Pick the task that costs you the most rework or the most questions this month.
  2. 2Do the task once with the template open and write each step as you perform it.
  3. 3Keep every step to a single action starting with a verb. Split anything with an "and" in it.
  4. 4Give the draft to someone who has never done the task and watch them follow it without help.
  5. 5Fix the steps where they hesitated, then set an owner and a review date.
  6. 6Store it where the work happens: shared drive folder, job app or a printed sheet at the station.

Filled-in example

Example

Filled-in example: weekly equipment check (landscaping crew)

  • Purpose: Prevent mid-route breakdowns and keep warranty claims valid.
  • Owner: Crew Lead. Approver: Operations Manager. Version 1.2, review March 2026.
  • Prerequisites: Fuel log, torque wrench, blade gauge, checklist clipboard in the trailer.
  • 1. Park the trailer on level ground and chock the wheels.
  • 2. Check mower blade edge against the gauge. If wear exceeds 3 mm, replace before the first job.
  • 3. Record engine hours for each unit in the fuel log.
  • 4. Top up fuel and two-stroke mix; note quantities used.
  • 5. Photograph any damage and send it to the Operations Manager the same day.
  • Done when: every unit has an entry for the week and no open damage report is unassigned.

Common mistakes

  • Writing narrative paragraphs instead of numbered actions, so the reader has to interpret rather than follow.
  • Documenting the ideal version of the process nobody actually uses.
  • Assigning the procedure to a person instead of a role, which breaks the moment they leave.
  • Skipping the definition of done, which leaves quality to opinion.
  • Publishing once and never reviewing, so the SOP quietly becomes fiction.

Frequently asked questions

What is the difference between an SOP and a checklist?
An SOP explains how a task is performed, including context, decisions and quality standards. A checklist is the short field version used while doing the work. Most teams need both: the SOP to train, the checklist to execute.
How long should an SOP be?
Most operational procedures fit on one to three pages. If yours runs longer, it is usually two procedures joined together, or it contains training material that belongs in a separate reference document.
Do I need special software for SOPs?
No. A shared drive folder with consistent file names works for most businesses under 50 people. Software helps when you need approvals and read receipts across multiple locations.
Who should write the SOP?
The person who does the task, with an editor who does not. The doer supplies accuracy, the editor removes assumed knowledge.
Free template

Employee Onboarding Checklist

An employee onboarding checklist tracks everything that has to happen from the moment an offer is accepted through the first 90 days: paperwork, equipment, access, introductions, training and check-ins.

Open Free template

New Hire Checklist

A new hire checklist is the short setup list a manager works through so a new employee arrives to a working desk, van or account on day one.

Open Free template

Meeting Notes Template

A meeting notes template captures the three things that matter after a meeting: what was decided, what happens next, and who owns each action by when.

Open Guide

How to Write an SOP

To write an SOP, pick one repeatable task, perform it while recording each action, then write those actions as numbered single-verb steps with an owner, prerequisites, decision points and a definition of done.

Open