The same steps, copied into every SOP
Every procedure borrows steps from another, so you keep the same how-to in a dozen places. You find out which copy you forgot to update from the person who followed it.
One Step, Many SOPs
Resetting a client login shows up in onboarding, offboarding, and the monthly audit. One procedure, three copies, three schedules to drift on.
Drift Is Silent
Nothing tells you a copy has gone stale. It reads as correct until the tool it describes has moved on.
A guide you write once, embedded where it belongs
A guide is the step-by-step. An SOP is the procedure that embeds it. You write it once, and there is only ever one of it.
Guides Inside SOPs
Build the procedure as an SOP and drop in the guides it depends on. The steps render in place, always showing the version you keep.
One Source, Everywhere
Change the guide and every SOP that embeds it is current. No hunting, no second copy to remember.
Capture The Steps
Record a process with the capture extension while you do it. Each click becomes a step with the screenshot already attached, so the guide exists before you would have finished writing it.
One library behind every client you serve
Your account holds the whole body of work — organized, not scattered across a folder per client.
Account To Hub
The hierarchy runs Account, Hub, Section, Category, Guide or SOP. Your operations live in one place and publish out to the hubs that need them.
Shared Across Clients
A guide written for one client's work can serve the next. Reuse the step, keep the single source, and let each SOP stay current on its own.
Ready to write it once?
Capture a process, publish it as a help center under your own name or a client's, and answer the repeat questions from what you published.