The short answer
Standard operating procedures, or SOPs, are your written how-to steps, kept together in one library that someone looks after. Writing steps is only half the job. The library keeps them easy to find, current and trusted, so the team follows the right version every time.
Key Points
The three things to take away.
- 1
One home for every SOP
Pick one place to keep every SOP and move them all there. A shared Google Drive or OneDrive folder works, and so does a simple wiki or the help section of your field service software. Steps saved in texts, email threads and sticky notes do not count.
Set up folders that match how your business runs, such as office, sales, field work and money. Make sure crews can open the library on a phone. Put a link to it on the shop wall or in the team chat so nobody has to ask where it is.
- Choose one place for all SOPs
- Move every stray copy into it
- Sort folders by part of the business
- Test that crews can open it on a phone
- 2
A standard SOP format
Use the same layout for every SOP so people know where to look. A good layout has the name, the purpose in one line, who does it, when it happens, what is needed and short numbered steps.
Save that layout as a blank template and start every new SOP from it. Add a photo or a short phone video where words fall short. Use the same naming pattern for files, such as the area and then the task, so the list sorts itself and anyone can find a step by searching.
- Save one blank SOP template
- Include purpose, owner, timing and steps
- Use one naming pattern for every file
- Add photos or video where needed
- 3
An owner for each SOP
Give every SOP one owner by role, such as office manager or lead tech. The owner keeps it accurate, answers questions about it and makes changes when the work changes.
Pick the person who does the task or leads the people who do. Write the owner on the SOP itself and in a simple master list of all SOPs. When someone changes jobs or leaves, move their SOPs to a new owner that same week. A procedure with no owner is the first one to go out of date.
- Name one owner by role for each SOP
- Write the owner on the SOP itself
- Keep a master list of SOPs and owners
- Reassign SOPs when people leave
- 4
Versions and review dates
Mark every SOP with a version number, the date it last changed and the date it gets reviewed next. When steps change, raise the version and write one line about what changed.
Set a review schedule. Steps tied to safety, money or customer data deserve a closer look more often than simple office tasks. Put review dates on a shared calendar so they come up on their own. Keep only the current version in the main folder so nobody follows old steps by mistake.
- Add a version and last changed date
- Set a next review date on each SOP
- Put review dates on a shared calendar
- Keep only the current version in view
- 5
Training sign-off
Record who has been trained on each SOP and when. A simple sheet works, with names down one side and SOPs across the top. Mark it when a person can do the task alone and correctly.
When an SOP changes in a way that matters, retrain the people on it and mark the sheet again. This tells you who can cover for whom and shows your insurer or a customer that your team was trained. It also points to the SOPs that only one person knows.
- Keep a training sheet by person and SOP
- Sign off only when someone works alone
- Retrain after any major change
- Spot tasks only one person can do
- 6
Retire old SOPs
When a task stops, a tool is replaced or two SOPs are merged, retire the old one on purpose. Move it to an archive folder, mark it retired with the date and point to the SOP that replaced it, if any.
Do not just delete it. Some records need to show what steps were in place at the time, and your attorney or insurer may ask. Remove retired SOPs from the master list and from any links on the wall or in the team chat so nobody finds them by accident.
- Move retired SOPs to an archive folder
- Mark them retired and note the replacement
- Remove them from the master list
- Update any links that pointed to them
Mistakes to avoid
- Letting SOPs live in five places so nobody knows which copy is right.
- Writing SOPs once and never setting a date to check them again.
- Deleting old SOPs instead of archiving them with a retired date.
Common questions
What is the difference between a procedure and an SOP library?
A procedure is the steps for one task. The SOP library is the system that holds all of them in one format, with an owner and a review date for each. The library is what keeps procedures current.
What software should a small business use for SOPs?
Start with what you already have, such as a shared Google Drive or OneDrive folder. A wiki or your field service software also works. Pick the one your crews can open on a phone.
How often should SOPs be reviewed?
Review an SOP whenever the work changes and on a set schedule the rest of the time. Safety, money and customer data steps should be checked more often than simple office tasks.
Who should own an SOP?
The person who does the task or leads the people who do it. Assign it by role, not by name, so the SOP moves to the next person when someone leaves.
General information only, not legal, tax or financial advice. See the Disclaimer.