Northline Ops › Guides › SOP Format & Structure

SOP Format and Structure

A standard operating procedure works only if someone can pick it up and follow it without asking questions. That comes down to format and structure. This guide covers the sections every SOP should have, how to format them, the three common SOP formats and when to use each, plus a copy-ready skeleton you can fill in right now.

The sections every SOP should have

Whatever the task, a well-structured SOP carries the same handful of sections in the same order. Keep them consistent across your documents so anyone can scan a new SOP and immediately know where to look.

• Title & purpose — name the task plainly, then one sentence on why it matters. "Process a vendor invoice" tells the reader more than "Invoicing." The purpose answers why bother, which helps people make sensible calls when something unexpected comes up.
• Scope — what this SOP covers and, just as useful, what it doesn't. A line like "Covers domestic orders under $5,000; international orders use a separate SOP" stops the document from being applied to the wrong situation.
• Role responsible — the job or role that owns the task, not a person's name. Names change; roles stay. Write "Accounts payable clerk," not "Sarah."
• Tools & access needed — the logins, software, files, or physical items required before starting. Listing these up front saves the reader from stopping halfway to hunt for a password.
• Numbered steps — the action steps, in order. This is the core of the document and where most of your effort goes.
• Quality check — how the reader confirms the task was done right. A short checklist or a description of what "done correctly" looks like turns a procedure into something verifiable.
• Last-reviewed date — when the SOP was last checked against reality. Processes drift; a visible review date tells readers whether to trust the document or flag it for an update.

Formatting best practices

Good structure is only half of it. How you format the content decides whether people actually use the SOP or quietly ignore it.

• One process per document. If you find yourself writing "meanwhile, the other team..." you've started a second SOP. Split it. One document, one task, one owner.
• Use numbered steps, not paragraphs. Numbered lists let the reader track where they are and refer back ("I'm stuck on step 4"). Paragraphs hide steps inside prose and invite people to skip them.
• Start each step with an action verb. Open, Enter, Click, Select, Send, Verify. The verb tells the reader exactly what to do. "The form should be completed" is weaker than "Complete the form."
• Keep it to one or two pages. If an SOP sprawls past two pages, it's usually trying to do too much. Long documents don't get read. Trim, split, or move reference material into an appendix.
• Write for someone new. Assume the reader has never done the task. Spell out the obvious. The person who wrote it isn't the person who'll need it most.

The three common SOP formats

Not every task needs the same shape. There are three formats worth knowing, and the right one depends on how complex the task is and whether it has decision points.

1. Simple step-by-step

A plain numbered list. Best for short, linear tasks where each step follows the last with no branching — resetting a password, closing the register, sending a weekly report. Most SOPs are this format, and you should default to it unless the task forces something more.

2. Hierarchical

Numbered steps with indented sub-steps beneath them. Use it when a task is linear overall but individual steps need detail — step 3 might break into 3a, 3b, 3c. Good for procedures that are involved but still go in one direction, like onboarding a new hire or running a monthly close.

3. Flowchart

A diagram with boxes and arrows. Use it when the task has decision points — "if the payment cleared, do this; if not, do that." Flowcharts handle branching far better than a list, which is why they suit approvals, troubleshooting, and anything with an "it depends." The trade-off is they're harder to edit, so reserve them for genuinely branching work.

A copy-ready SOP skeleton

Here's a fill-in-the-blank structure you can paste into any document. Replace the bracketed prompts and delete the rest.

SOP: [Name of the task]

Purpose: [One sentence on why this task matters.]

Scope: [What this SOP covers — and what it does not.]

Role responsible: [The role that owns this task, e.g. "Account coordinator".]

Tools / access needed:
- [Login, software, file, or item #1]
- [Login, software, file, or item #2]

Steps:
1. [Action verb] [what to do].
2. [Action verb] [what to do].
3. [Action verb] [what to do].
4. [Action verb] [what to do].

Quality check:
- [How to confirm the task was done correctly #1]
- [How to confirm the task was done correctly #2]

Last reviewed: [YYYY-MM-DD]

You are an operations expert. I'll describe a task my team does.
Ask me one clarifying question at a time until you have enough
detail, then write a one-page SOP in exactly this structure:

- Title & Purpose (one sentence on why it matters)
- Scope (what it covers and what it doesn't)
- Role Responsible (a role, not a name)
- Tools / Access Needed (a bullet list)
- Steps (numbered; start each step with an action verb)
- Quality Check (a short checklist)
- Last Reviewed date

Keep it to one page and write for someone who has never done
the task before. The task is: [describe your task here].

Don't start from a blank page

Knowing the format is one thing; filling it in for every process in your business is another. The AI SOP Generator Kit gives you an editable template built on exactly this structure, a prompt pack that interviews you and drafts each SOP, and 50 worked examples to adapt — so you're editing instead of staring at a blank page.

If you've got more than a handful of processes to document, the prompt pack is the part that saves the most time. It handles the structure for you and asks the right questions, so every SOP comes out in the same consistent format without you having to remember each section.