The best way to create an SOP for a task is to watch the person who does it best, write the steps in order for the newest person on the team, add the tools and screenshots they'll need, test it with someone who's never done the task, and give it an owner who keeps it current. Trainual is Business Operations & SOP Software that turns company knowledge into employee performance, with Training, Operations, and Performance in one place, so the SOPs you write get followed, not filed.
If you've explained the same task three times this month, you already know why you need an SOP. What usually stops people is the blank page: where to start, how much detail to include, and what a good one looks like. This guide gives you a seven-step method, a fill-in template, and a worked example you can copy for any task.
It works for a 25-person team writing its first SOP and for a 99-person team standardizing its tenth. For the full background on what SOPs are, see what is an SOP.
Updated November 2026.
Key takeaways
- Start from the doing, not the writing. Watch or record the task first; write second.
- Write for the newest person on the team, with full tool names, menu paths, and decision points.
- Test it on someone who's never done the task. If they can't follow it, add detail.
- Give it an owner. An SOP without an owner is out of date within a quarter.
What an SOP for a task needs
Every useful SOP answers five questions for the person doing the work:
- What is the task, and what starts it?
- Who owns it, and when was it last checked?
- What are the steps, in order, with the tools named?
- What changes when something's different? The exceptions and judgment calls.
- What does done look like? A check the person can make themselves.
If a document doesn't answer all five, it's notes, not an SOP.
How to write an SOP for any task in 7 steps
- Pick the task. Choose something that happens at least weekly and gets done differently depending on who does it. Those SOPs pay back fastest.
- Watch the person who does it best. Sit with them, or record them doing it on screen. Ask them to talk through each step and why.
- Write the steps in order. One action per step, starting with a verb: "Open," "Select," "Copy," "Send."
- Name every tool and template. "Use the usual template" isn't a step. "Select the Client Monthly V3 template" is.
- Add the decision points. Where does the task change? Write "If [this], then [do that]" for each exception.
- Test it with someone new. Hand it to someone who's never done the task. Wherever they stop or ask a question, add detail.
- Assign an owner and a review date. The owner keeps it current and updates it when the work changes.
The difference between a step that gets followed and one that doesn't is usually specificity:
For more on writing steps people follow, see how to write a SOP that people actually use.
A fill-in SOP template
Copy this structure for any task. The example column shows a filled-in version.
Prefer to start from something prebuilt? Trainual's process templates cover common tasks across hiring, onboarding, customer service, and more.
Example: an SOP for sending a client invoice
Here's what a short, complete SOP looks like:
Send a monthly client invoice (V2). Owner: billing coordinator. Last reviewed: March 2026.
Purpose: clients get an accurate invoice on the same day each month.
Trigger: the first workday of the month.
- Open QuickBooks and go to Sales, then Invoices.
- Click Create invoice and select the "Client Monthly V3" template.
- Copy the billing contact and PO number from the client's record in the CRM.
- Add this month's line items from the client's service log.
- Compare the total with last month's invoice. If it differs by 10% or more, send it to the account manager for approval before continuing.
- Click Send, and attach a copy of the sent invoice to the client's CRM record.
Done when: the invoice shows Sent in QuickBooks and a copy is saved in the CRM.
That's an SOP a new hire can follow on day three, without asking anyone.
Which SOP format to use
Match the format to the task:
- Step-by-step list: most tasks, especially ones done on a computer.
- Checklist: tasks people already know but must not skip steps on, like opening or closing procedures.
- Flowchart: tasks with several branches, like escalations or approvals.
- Video or screen recording: physical tasks or software with many clicks, ideally paired with written steps.
Standardizing tasks at a 50-person company
At around 50 people, the problem shifts from "we have no SOPs" to "everyone does this differently." Standardizing is mostly about consistency:
- Pick five tasks that happen often and get done differently by different people.
- Use one template for all of them, so every SOP looks and reads the same.
- Assign each SOP by role, so the right people learn it and new hires get it automatically.
- Give each one an owner and a review date.
- Add five more once the first five are being followed.
For a starting list, see the 10 SOPs every growing team needs.
How to get your team to use the SOPs you write
A well-written SOP still fails if nobody opens it. Four habits make the difference:
- Put SOPs where people already look. If finding the SOP takes longer than guessing, people will guess.
- Assign them, don't just share them. A link in Slack is easy to ignore; an assigned SOP with a due date isn't.
- Answer questions with the SOP. When someone asks how to do a task, reply with a link instead of the answer. Within a few weeks, people check the SOP first.
- Fix it when someone finds a gap. The fastest way to lose trust in SOPs is to leave a known mistake in one. Make it easy to flag, and have the owner update it the same week.
The goal is a team that treats the SOP as the answer, not as paperwork. For the deeper reasons SOPs get ignored, see why SOPs fail.
Common SOP mistakes
- Writing for experts. Shorthand and assumed knowledge leave new hires stuck.
- Skipping the exceptions. The routine steps are easy; the judgment calls are where mistakes happen.
- Covering several tasks in one SOP. Split it so each task has its own SOP and owner.
- Never testing it. An untested SOP usually has a missing step.
- No owner. Nobody updates it, and it quietly goes out of date. See how to keep SOP documentation updated.
How to write and roll out SOPs in Trainual
Writing the SOP is half the job. The other half is getting it to the right people and keeping it current.
Training: write SOPs faster and get them learned.
- A first draft in minutes. AI-powered SOP creation turns a rough description, a recording transcript, or existing notes into a structured draft. Bulk import brings up to 50 existing files in at once.
- One current version. Process documentation with version history keeps every change tracked.
- Answers on demand. A searchable knowledge base and the AI assistant answer questions around the clock, using your company's own information in Trainual.
Operations: assign it and keep it owned.
- Assigned by role. Roles and responsibilities decide who learns each SOP, so new hires get it automatically.
- Owners with reminders. Each SOP has an owner who gets reminders to review and verify it.
Performance: know it's being followed.
- Completion by person. Training paths with knowledge checks show who has learned each SOP.
- Expectations from the role. In Performance, reviews draw on the responsibilities and SOPs each role owns.
Together, that's the loop:
- Train: so everyone knows how work should be done.
- Operate: so everyone knows what needs to happen today.
- Perform: so everyone knows what's expected and how knowledge turns into better work.
Writing SOPs pays off quickly. Ironsmith Fire went from the top 10% to the top 1% after documenting its processes, and High 5 Plumbing cut training from seven hours to 90 minutes.
Quick wins to start this week
Quick win #1: Pick the task you explain most often
That's your first SOP.
Quick win #2: Record the person who does it best
Fifteen minutes on screen is enough for a first draft.
Quick win #3: Write it with the template above
Fill in every row, including decision points and the definition of done.
Quick win #4: Test it on someone new
Add detail wherever they get stuck.
Quick win #5: Name the owner and set a review date
Put the review on the owner's calendar.
Ready to see how Trainual works?
👉 Book a demo and see how Trainual helps you write SOPs faster, assign them by role, and keep them current.
Want a sneak peek?
👉 Read customer stories from teams who documented their processes and stopped answering the same questions.
Frequently asked questions
What is the best way to create an SOP for a task or job?
Watch the person who does the task best, write the steps in order for the newest person on the team, add the tools and screenshots they'll need, test it with someone who has never done the task, and give it an owner who keeps it current.
What should an SOP include?
A title and version, an owner and review date, a one-line purpose, the trigger that starts the task, the tools used, numbered steps, decision points for exceptions, and a definition of done.
How long should an SOP be?
As long as it takes for someone new to follow it without asking questions, and no longer. Most single-task SOPs fit on one to two pages. If it runs much longer, it probably covers more than one task and should be split.
Who should write an SOP?
The person who does the task best should draft it or be recorded doing it, and a named owner should keep it current. A manager who doesn't do the task usually leaves out the details that matter.
How do you standardize tasks at a 50-person company?
Pick the five tasks that happen most often and get done differently by different people, write one SOP for each using the same template, assign them by role, and give each an owner and a review date. Add the next five once those are being followed.
What's the difference between an SOP and a checklist?
A checklist lists what to do; an SOP explains how to do it, including the tools, the order, and what to do when something's different. Many SOPs include a short checklist for people who already know the task.
Can AI write an SOP?
AI can draft one quickly from a rough description, a recording, or existing notes, but someone who does the task needs to check it. In Trainual, AI-powered SOP creation turns rough input into a structured first draft to review and refine.
How often should SOPs be updated?
Review each SOP at least once a quarter, and update it right away whenever a tool, regulation, or role changes or someone reports a step that's wrong.




