Standard Operating Procedure Template
Draw the procedure as numbered steps with its checks and exceptions, and keep each step's detail, expected result and fix one click behind it.
Free forever on the Personal plan
Standard operating procedures: an example
Numbered and in order
Every step numbered on one page, so nobody skips one.
Checks built in
Each step says what to expect, and what to do when it does not happen.
Exceptions linked
When a check fails, the SOP links straight to the guide that fixes it.
The basics
What is a standard operating procedure?
A standard operating procedure (SOP) is a documented, step-by-step way to carry out a routine task the same way every time: opening a store, setting up a device, running a month-end job. It says who does it, when, what they need, each step in order and what a good result looks like.
SOPs fail when they are long documents nobody reads at the moment they are needed. Showing the procedure as a short numbered flow, with the detail behind each step and the exceptions marked, makes it usable in the middle of the task.
In Blueprintr an SOP is a diagram of the steps with a stratum behind each one, and a link to the troubleshooting guide or runbook wherever the procedure can fail.
Why Blueprintr
Procedures people follow at the moment of use
The steps on one diagram, the detail behind each.
Steps, checks and branches
Draw numbered steps as boxes, checks as diamonds and the exception paths in red, with flowchart and BPMN shapes when you need them.
VellumDetail behind every step
Give each step a stratum with what to do, the result to expect and what to do if it does not appear, with tables, warnings and images.
StratumLinked to the fix
Link each failure path to the troubleshooting guide or runbook that handles it, so the reader never has to search mid-task.
A library of procedures
On the Team plan, collect SOPs in a folium with a page tree, search, page comments and change requests.
FoliumReviewed before it changes
On team-owned blueprints, require approval before an edit to a published SOP is merged, so nobody follows an unreviewed step.
A version people can trust
Each publish keeps a snapshot, so you can show what the procedure said on any date. On the Team plan you can compare versions.
How to
How to write an SOP in Blueprintr
Create a blueprint
Sign up free and create a blueprint named with the SOP's number and title.
List the steps
Add a numbered box for each step, in the order they are done.
Add the checks
Add a diamond wherever the procedure can branch, with the path for each answer.
Write each step
Right-click each step and add a stratum with the detail, the expected result and the fix.
Publish and review
Publish it where staff will find it, and set a date to review it.
FAQ
Questions about standard operating procedures
Is this SOP template free?
Yes. The Vellum editor, flowchart shapes and strata are on the free Personal plan. SOP libraries in a folium and approval workflows are part of the Team plan.
What should a standard operating procedure include?
Its purpose and scope, who does it and when, what to have ready, numbered steps, the result to expect after each, what to do when something fails, and an owner, version and review date.
What is the difference between an SOP and a runbook?
An SOP is for routine, planned work done the same way every time. A runbook is for handling a known event, such as an outage or an alert, and usually branches on what the person on call finds.
How often should SOPs be reviewed?
At least once a year, and whenever the process or the systems behind it change. Record the review date and the reviewer in the SOP, so readers can see it is current.
Can staff read SOPs without a Blueprintr account?
Yes, if you publish them as public or unlisted. For internal procedures, keep them private and share them with your organisation, so staff sign in with their own accounts.
Can I build a library of SOPs?
Yes. File them in portfolios on any plan, or on the Team plan collect them in a folium with a page tree, search and page comments.