Inktrail
Log in
Business Operations

How to Write an SOP

Create clear Standard Operating Procedures your team will actually follow. Learn the best format, writing style, and how to keep SOPs current.

6 steps

  1. Define the purpose and scope

    State in one or two sentences what this SOP covers and why it exists. Specify which team, role, or situation it applies to. A clear scope prevents the SOP from being misapplied and helps readers know immediately whether it is relevant to them.

  2. Identify the process owner

    Every SOP needs a named owner — the person responsible for keeping it current and answering questions. Without ownership, SOPs become stale and ignored. Include the owner's name, role, and the date the SOP was last reviewed.

    Pro tip

    Set a calendar reminder to review the SOP every 6 months.

  3. List required inputs and prerequisites

    Before the steps begin, list everything the reader needs: access, tools, data, approvals, or prior steps that must be completed. A reader who gets halfway through and finds a missing prerequisite will lose confidence in the entire document.

  4. Write the steps in numbered sequence

    Break the process into discrete, numbered steps. Each step should describe one action, written in the imperative voice ("Open the dashboard," not "You should open the dashboard"). Aim for 5–15 steps per SOP; if you have more, consider splitting into sub-procedures.

    Pro tip

    Use screenshots or short screen recordings for any step involving software. Visuals cut support requests dramatically.

  5. Add decision points and exceptions

    For steps that branch based on a condition ("If X, do Y; if Z, do W"), use a simple decision tree or if/else table. Document the most common exceptions and edge cases explicitly so readers do not have to guess.

  6. Specify the expected output

    End the SOP by describing what "done" looks like. What has been created, updated, approved, or notified? A clear output definition makes the SOP verifiable and helps readers know when to stop.

Start with a free AI template

Use Inktrail's AI to generate a customised write an sop in seconds. Refine, design, and publish — all on one surface.

Browse free templates

Frequently asked questions

What is the difference between an SOP and a process map?

An SOP is a written, step-by-step document describing how to complete a specific task. A process map is a visual diagram showing how steps connect across a workflow or between teams. Both are useful — SOPs for individual execution, process maps for systemic understanding.

How detailed should an SOP be?

Write for the least experienced person who will ever use it. If a new hire could follow the SOP without asking questions, it is detailed enough. If your most senior employee would be offended by its simplicity, it is probably about right.

What format is best for SOPs?

Numbered lists are the standard format for most SOPs. Use headers to separate sections (purpose, prerequisites, steps, output). Avoid paragraphs for the main steps — they are harder to follow under pressure.

How do I get my team to follow SOPs?

Involve the team in writing the SOP. People follow processes they helped create. Keep SOPs short and easy to find. Review them together when things go wrong instead of blaming individuals.