A procedure you can run, not just a page you can read
Every company that writes SOPs discovers the same two holes: nobody follows the document while doing the job, and nobody can prove anyone read it. A wiki solves neither. A procedure here can be run as a tracked instance, and a document can require an acknowledgement that is recorded rather than assumed.
Documents built from blocks
A block editor rather than a text box, so a procedure has structure — and the reader is a separate, lighter surface from the editor.
- A library of documents with a block-based editor
- The reader loads without the editor, because most people only ever read
- Structure that a run can step through, not a wall of prose
Run the SOP, don't just open it
A run is an instance of the procedure being performed. That is the difference between a document about how the job is done and a record that the job was done that way.
- Start a run from the document and work through it
- Each run is its own record rather than an edit to the source
- The procedure stays a living document while the runs stay history
Acknowledgements, so "they were told" is a record
"My Reading" is each person's own list of what they need to acknowledge. Read receipts on policy are the half most internal wikis skip, and the half that matters when it counts.
- A per-person reading list rather than a broadcast nobody tracked
- Acknowledgement recorded against the person and the document
- Answers "who has actually seen the new policy" with a list, not a guess
What Knowledge & SOPs runs on
Hold this on its own, or add the modules beside it when you want them — they share one login and one set of records. See the module library and pricing.
- Knowledge & SOPs
- Projects
- HR
- Business Tools (free)
- Field Service
Questions buyers ask
How is this different from a wiki?
Two things a wiki does not do: a procedure can be RUN as a tracked instance while the work happens, and a document can require an acknowledgement that is recorded per person. A wiki tells you what the policy is; neither of those tells you it was followed or seen.
Can we see who has read a policy?
Yes — acknowledgements are recorded against the person and the document, and each person has their own "My Reading" list. That is the question people actually need answered after a policy change, and assuming the answer is how it goes wrong.
Can an SOP be attached to the work it describes?
Jobs carry a checklist through their Project bucket, and SOP runs are their own records in Knowledge. They are related surfaces rather than one merged thing today — we would rather describe the seam than pretend it is seamless.
Can we buy this on its own?
Yes. Knowledge & SOPs is its own module. It composes with HR and Projects when you hold them, and if you do not, you will not see their screens.
See it running
Create an account, or tell us how you work today and we'll show you what Knowledge & SOPs looks like on your data.