An out-of-date SOP is worse than none. Procedures drift, and nobody can say which version was in force.
Local copies win
Someone updates a step in their own copy; the master never does.
Two teams, two methods
The same process ends up running two different ways in two places.
Nobody owns it
With no named owner, nothing gets reviewed until something breaks.
No version of record
When it goes wrong, nobody can say which version was in force.
- EMBEDS
The Diagram And The Demo Video Live Inside The SOP
SOPs work better when the process diagram, the walkthrough video, and the tracker sit in the document instead of behind links. Embed them directly: Loom, YouTube, Lucidchart, Draw.io, Figma, Google Sheets, and more.
Scope rule — embeds are for SOPs and working documents. Policies that collect acknowledgment or e-signature stand on their own, because live embedded content can change after people sign.
A process video and a live diagram, embedded in the SOP itself.
- Capabilities
Owned, Current, And Acknowledged By The People Who Run It
Every SOP has an owner
A named owner and a review date keep procedures from quietly going stale. When the review comes due, the owner gets chased automatically - the system remembers, not a person.
One current version
Edits route for approval and publish as a new version; the old one is retired but kept for the record.
Acknowledged by the people who run it
Assign the SOP to the team that uses it, by the tags you define, and track who has confirmed they've read the current version.
See exactly what changed
Side-by-side version compare shows what changed between versions and when, so retraining targets the actual change.
- Proof
The proof is gathered as you go
Owner, review date, version history, and acknowledgment - recorded as the procedure changes, and exportable the moment someone asks which version was in force.
01
Named owner
Every SOP carries an accountable owner, visible on the document.
02
Review dates
Review dates are set, tracked, and chased automatically.
03
Version history & compare
Every version kept, with side-by-side and word-level compare.
04
Targeted acknowledgment
Sign-off tracked by team or location, against the current version.
05
Complete change record
Every change logged and exportable when someone asks.
- Fit
For Teams Running Repeatable Work, Especially Across Sites
Where the same procedure has to run the same way in more than one place - and someone has to be able to prove that it did.
USED FOR:
Operational procedures
Day-to-day process docs with a named owner and review date.
Quality & manufacturing
Controlled procedures, review cycles, and audit readiness.
Support runbooks
Escalation and handling steps, current for everyone on shift.
Multi-site standardisation
One procedure, targeted per location by tag.
- FAQS
Frequently asked questions
How is an SOP different from a policy here?
A policy states the rule; an SOP states how to do the task. Both get the same lifecycle: own, approve, version, acknowledge.
Can I set a review schedule?
Yes. Each SOP has a named owner and a review date, and the owner is reminded when it comes due.
How do people know a procedure changed?
They're notified and asked to acknowledge the new version, and version compare shows them exactly what changed.
Can different sites run different SOPs?
Yes. Target by team or location tags so each group sees the version that applies to them.
Keep Every SOP Current And Acknowledged
Own it, version it, embed the walkthrough, prove the sign-off.
30-day free trial · No credit card · Cancel anytime