SOP Format: Structures, Sections and Examples
Choose the right SOP format for the task in front of you. Four structures compared, the standard sections explained, and short examples of each you can adapt.
The format of an SOP decides whether people can use it in the moment they need it. The same process written as a dense paragraph, a clean numbered list or a decision flowchart will get very different results. This guide covers the four formats most businesses use, when each one fits, and the sections that belong in every SOP regardless of format.
What “SOP format” means
An SOP format is the structure a standard operating procedure uses to present its information: the fixed sections that frame the task (such as purpose, scope, roles and review date) and the way the steps themselves are laid out, most often as a numbered list, a checklist, a nested hierarchy or a flowchart. Choosing a format means matching that layout to how the task is actually performed.
Two separate decisions hide inside that definition. The first is which sections the document carries. The second is how the steps are laid out. The sections are fairly standard. The step layout is where you choose.
The standard sections of an SOP
Most business SOPs carry the same core sections. Not every SOP needs every one, but leaving one out should be a decision rather than an accident.
| Section | What it contains | Required? |
|---|---|---|
| Title | A verb plus the task, e.g. “Process a customer refund” | Always |
| Purpose | One sentence on what is true when the task is done correctly | Always |
| Scope | Where the task starts and ends, and what is covered elsewhere | Always |
| Trigger and frequency | What starts the task and how often it happens | Usually |
| Roles | Who performs it and who owns the document | Always |
| Tools and access | Systems, logins and permissions needed before starting | Usually |
| Steps | The procedure itself, in the chosen format | Always |
| Definitions | Terms a new person might not know | When needed |
| Safety or compliance notes | Warnings, legal requirements, approvals | When needed |
| Related documents | SOPs that come before or after, linked policies | Usually |
| Revision history | What changed, when and by whom | Always |
| Review date | When the owner will next check it for accuracy | Always |
Two tips on the sections. Keep the header short: if the purpose, scope and roles take more space than the steps, readers will scroll past all of it. And put the revision history at the bottom, or in the tool itself if it tracks versions for you, so it does not push the steps below the fold.
The four SOP formats
1. Simple step-by-step format
A numbered list of actions performed in order. This is the default for most business tasks and the format to reach for when in doubt.
Use it when: the task follows the same path every time, has fewer than about fifteen steps, and has at most one or two decision points.
Example: Publish a blog post
- Open the approved draft in the shared content folder.
- Paste it into the website editor and apply the post template.
- Add the featured image and alt text.
- Fill in the SEO title and meta description fields.
- Preview on desktop and mobile. Fix any broken formatting.
- Schedule or publish, then paste the live URL into the content calendar.
The strength of this format is that it is fast to write and fast to follow. Its weakness is branching: once a task has several “if this, then that” paths, a flat list turns into a maze of “skip to step 9.”
2. Checklist format
A list of items to confirm, usually with checkboxes, and often without strict order. Checklists work best as a memory aid for people who already know how to do the task.
Use it when: the person performing the task is experienced, the risk is forgetting something rather than not knowing how, and the order matters less than completeness.
Example: Close the office for the day
- Coffee machine and kettle off
- Windows closed and locked
- Front door alarm set
- Outgoing mail on the reception desk
- Lights off in meeting rooms
A checklist is not a training tool. A new hire reading “Front door alarm set” still does not know the code or the sequence. A common approach is to write the full step-by-step SOP for training and attach a short checklist version for daily use.
3. Hierarchical format
A numbered list with sub-steps nested under major steps (1, 1.1, 1.2, 2, 2.1 and so on). It adds detail without losing the high-level shape of the task.
Use it when: the task is long, has distinct phases, or mixes experienced and new readers. Experienced people can scan the top level; new people read the sub-steps.
Example: Onboard a new employee (excerpt)
- Before day one
- Send the offer packet and collect signed paperwork.
- Request laptop and accounts from IT.
- Add the start date to the team calendar.
- Day one
- Welcome meeting with the manager.
- Walk through the company handbook.
- Set up email, chat and the SOP library login.
- First week
- Assign the core SOPs for the role.
- Schedule a check-in at the end of the week.
The risk with this format is depth. Once you are at 2.3.4.1, the SOP is really several SOPs and should be split. See our employee onboarding SOP template for a complete version of this one.
4. Flowchart format
A diagram of boxes and arrows, where diamonds mark decisions. Flowcharts show branching better than any text format.
Use it when: the task depends on decisions, involves hand-offs between people or teams, or you need to show where a process can go wrong.
Example: Handle a support ticket (described in text)
- Start: ticket arrives.
- Decision: is it a billing question? Yes: route to finance. No: continue.
- Decision: can front-line support solve it with an existing answer? Yes: reply and close. No: continue.
- Decision: is the customer’s service down? Yes: escalate to the on-call lead now. No: escalate to tier two within one business day.
Flowcharts have two drawbacks. They are harder to update than text, and they rarely hold enough detail to do each step. The practical answer is to use a flowchart for the decision logic and link each box to a step-by-step SOP. Our guide to process mapping shows how to draw that flowchart with the people who run the process. Our customer support escalation SOP template follows this pattern.
How to choose the right format
| Format | Best for | Weak at | Typical reader |
|---|---|---|---|
| Step-by-step | Linear tasks with few decisions | Many branches | Anyone, including new hires |
| Checklist | Routine tasks where forgetting is the risk | Teaching how | Experienced staff |
| Hierarchical | Long tasks with phases | Very deep nesting | Mixed experience levels |
| Flowchart | Decisions and hand-offs | Detailed instructions | Managers, cross-team work |
A quick way to decide:
- Does the task branch more than twice? Use a flowchart for the logic, with step-by-step SOPs behind it.
- Is it long, with clear phases? Use a hierarchical format.
- Do experienced people just need to not forget things? Use a checklist.
- Otherwise, use simple step-by-step.
Formatting rules that apply to every format
Whatever structure you choose, these habits make an SOP easier to follow:
- Start every step with a verb. “Open,” “Confirm,” “Send.”
- One action per step. Split anything with “and then” in the middle.
- Name the place. Which tool, screen, folder or field.
- Use bold sparingly for the one warning people must not miss.
- Show, do not describe, for software. A screenshot next to a step removes most “where is that button?” questions.
- Write for roles, not people. “The office manager,” not a first name.
- Keep it to one screen when possible. Long SOPs are usually two SOPs.
For software tasks, screenshots are worth the effort but tedious to capture by hand. In SOPCompass you can do the task once with the SOPCompass Capture Chrome extension, which turns each click into a step with a screenshot, or record your screen and it drafts the steps with screenshots and keeps the video. Either way you then edit the steps like any other SOP.
Where the format lives matters too
The best format in the world does not help if people cannot find the current version. A few practical points:
- Keep one copy. Duplicates in email attachments and desktop folders drift apart.
- Organize by business area, not by author or date. People look for “how we onboard a client,” not “Sam’s docs.”
- Track versions so you can see what changed and restore an earlier version if an edit was wrong.
- Make it readable while working. A reader that shows one step at a time next to the task is easier to follow than a long page.
In SOPCompass, SOPs live in a structure of Company plus five business pillars with department tags, and the follow-along reader lets someone work through a procedure one step at a time. The format guidance above works in any tool, though; a well-organized shared drive can go a long way for a small team.
Start from a template
If you want a blank structure with all the standard sections already in place, start with our standard operating procedure template. Then read how to write an SOP for your business for the method behind filling it in, and browse SOP examples from real business functions to see the formats above applied to HR, finance, sales and more.