If you have ever trained a new hire, covered for a teammate who was out sick, or tried to remember exactly how you did something six months ago, you already understand the value of a standard operating procedure. A good SOP turns knowledge that lives in one person’s head into a clear, repeatable process anyone on your team can follow.

This guide walks through what an SOP is, why it matters, and a practical, step-by-step method for writing one – with examples and a free template you can download and use today.

What is a standard operating procedure (SOP)?

A standard operating procedure (SOP) is a documented, step-by-step set of instructions that describes how to carry out a routine task the same way every time. It captures not just the steps, but the context around them: who is responsible, what tools or access are required, and how to confirm the job was done correctly.

SOPs exist for almost any repeatable process – onboarding an employee, closing a restaurant, processing a refund, running a monthly financial report, or handling a customer complaint. The format can be a simple checklist, a numbered procedure, or a flowchart, but the goal is always the same: consistent, reliable results no matter who performs the work.

Why SOPs matter

Well-written SOPs pay for themselves quickly. Here is what they do for a team:

• Consistency. Everyone follows the same proven steps, so the outcome is predictable across shifts, locations, and people.
• Faster onboarding. New hires get up to speed by following documentation instead of interrupting a busy colleague.
• Fewer mistakes. Clear steps and quality checks reduce errors and the cost of fixing them.
• Protected knowledge. When a key person leaves or is unavailable, the process does not leave with them.
• Compliance and audit readiness. Documented procedures are essential for ISO certification, health and safety, and many regulated industries.

Types of SOP formats

Before you start writing, choose the format that fits the process:

Step-by-step (checklist or numbered list)

The most common format. Best for straightforward, linear tasks where each step follows the last – for example, “how to process a refund” or “how to close the kitchen.”

Hierarchical

A numbered procedure with sub-steps underneath each main step. Use it when steps need extra detail or branching instructions, such as a complex software or accounting workflow.

Flowchart

A visual diagram for processes with lots of decision points (“if X, do this; if Y, do that”). Ideal for troubleshooting guides or approval workflows.

How to write an SOP: step by step

Here is a repeatable method you can use for any procedure.

Step 1: Choose the process and define its scope

Pick one specific process and be clear about where it starts and ends. A tight scope – “how to onboard a new sales rep in our CRM,” not “how onboarding works” – keeps the SOP focused and useful. Write a one-sentence purpose that states the outcome the procedure guarantees.

Step 2: Identify your audience and assign an owner

Who will actually follow this SOP? A brand-new employee needs more explanation than an experienced specialist. Write for the least experienced person who will use it. Then assign an owner – the person responsible for keeping the document accurate over time.

Step 3: Gather the information

Do not write from memory. Perform the process yourself, or watch someone who does it well, and capture every step as it happens. Note the tools used, the decisions made, and the small details that are easy to forget. The most accurate SOPs are documented while the work is actually being done.

Step 4: Pick a format and start from a template

Do not start from a blank page. A template gives you a consistent structure – title block, purpose, scope, prerequisites, numbered steps, and revision history – so every SOP in your company looks and reads the same way. You can download our free SOP template in Word and use it as your starting point.

Step 5: Write clear, action-first steps

Start each step with a verb: “Open the Reports menu,” “Enter the customer ID,” “Click Save.” Keep each step to a single action, use plain language, and avoid jargon unless you define it. If a step has a condition, state it up front: “If the total does not match, recheck the currency setting.”

Step 6: Add screenshots and visuals

A screenshot at the right moment removes ambiguity that words alone cannot. Add an image for any step where the interface or physical setup matters, and place it directly beside or beneath the step it illustrates. Visuals dramatically speed up comprehension – especially for software and equipment procedures.

Step 7: Review and test with real users

Hand the draft to someone who does not already know the process and ask them to follow it exactly, without help. Wherever they get stuck, confused, or improvise, your SOP has a gap. Fix those gaps and gather feedback from stakeholders for accuracy and completeness.

Step 8: Publish, store, and keep it current

Save the finished SOP somewhere your team can find it, and set a review date. Processes change – software updates, policies shift – so an SOP is a living document. Use the revision history to track what changed, when, and why.

A short SOP example

Here is a condensed example of the step-by-step format in action:

SOP: Processing a customer refund

Purpose: Ensure every refund is processed accurately and recorded consistently.
Scope: Applies to all refunds requested through the support inbox.
Steps:

1. Open the order in the admin dashboard and confirm the customer’s identity.
2. Verify the refund is within the 30-day return window.
3. Click Issue Refund and select the original payment method.
4. Enter the refund amount and add a note with the reason.
5. Email the customer to confirm the refund and expected timing.

Quality check: Confirm the refund appears in the daily transaction report.

Common SOP mistakes to avoid

• Too much detail, or too little. Match the depth to your audience – enough to follow, not so much that it becomes unreadable.
• Vague language. “Handle the report” is not a step. “Export the report as a PDF and email it to finance” is.
• No visuals. Text-only SOPs for software or equipment leave too much room for error.
• Writing from memory. You will skip the steps that feel automatic to you but trip up everyone else.
• Set-and-forget. An SOP nobody maintains becomes wrong – and a wrong SOP is worse than none.

The faster way: turn a video into an SOP

Writing an SOP by hand is thorough but slow – drafting steps, taking and placing screenshots, and formatting can take two to four hours per document. There is a faster way.

Narratus turns a narrated video into a publication-ready SOP in minutes. You record yourself performing the task once, talking through what you are doing, and Narratus transcribes your narration, captures screenshots at exactly the right moments, and generates a formatted Word or PDF document – complete with a table of contents and your company logo. It runs in your browser, and your video never leaves your computer.

See how it works, or view pricing to get started.

SOP examples by team or industry

SOPs look a little different depending on the work. Here are common examples by department to spark ideas for your own documentation:

• IT: troubleshooting a recurring error, onboarding a device, running a security patch, or restoring from backup.
• HR: onboarding a new hire, running a performance review, or processing a leave request.
• Finance: closing the books each month, reconciling accounts, or compiling a regional sales report.
• Restaurant and food service: opening and closing checklists, food-safety handling, or cleaning schedules.
• Healthcare: patient intake, medication administration, or infection-control protocols.

For fully worked procedures in each field, see our SOP examples by industry. Whatever the department, the underlying method is the same: define the scope, write clear action-first steps, add visuals where they help, and keep the document current. The free SOP template works as a starting point for any of these.

Frequently asked questions

How long should an SOP be?

As long as it needs to be and no longer. A simple task might fit on one page; a complex workflow may run several. Focus on clarity, not length.

Who should write the SOP?

Ideally the person who performs the task, with review from a manager or stakeholder. They know the real steps, including the details that are easy to overlook.

How often should SOPs be updated?

Review each SOP at least once or twice a year, and any time the underlying process, tool, or policy changes.

What is the difference between an SOP and a work instruction?

An SOP describes an entire process from start to finish, including its purpose, scope, and who is responsible. A work instruction is narrower – it details exactly how to perform a single task or step within that process. In practice, a detailed SOP often contains work-instruction-level steps.

Should SOPs include screenshots?

For any process that involves software or physical equipment, yes. A well-placed screenshot removes ambiguity and makes the procedure far easier to follow than words alone.

Start with a template

The fastest way to write your first SOP is to start from a proven structure. Download the free SOP template, fill in your process, and you will have a professional document in far less time than starting from scratch – or let Narratus write it for you from a single recording.