The knowledge that lives in one person's head is the knowledge you lose when they are away.
Versions without ceremony
Every save steps the version number. There is no approval workflow to configure — just a visible signal that a procedure is not the one someone read last month.
Plain text on purpose
Procedures that are hard to edit do not get updated, and a procedure that is out of date is worse than none.
Frequently asked questions
- How does versioning work?
- Each procedure carries a version number that increments on every save, alongside the date it was last updated. It is a signal that something changed, not a full revision history.
- What should I write an SOP for first?
- The thing you explain most often. If you have described the same process out loud three times this month, that is the one.
- Can my team see them?
- Procedures belong to the account that wrote them. Team-wide sharing is on the roadmap rather than built today.