Prefer to write it yourself? The editor is built for that.
Sometimes you know exactly what the SOP should say and you just want to write it. The manual path involves no AI at all: a title and an optional description, trigger, and team assignment opens an empty draft, and you write every step yourself in a proper editor.
What you actually get
- Zero AI. Nothing is generated, suggested, or rewritten
- Rich text: bold, numbered and bulleted lists, and callout boxes for warnings and exceptions
- Inline screenshots and links to related documents
- Regular steps and decision steps, where each answer routes to a specific later step
- Available on every plan, including the free tier
How it works
Open an empty draft
Give it a title, and optionally a description, a trigger, and a team. That is the whole setup.
Write the steps
Add regular steps, or decision steps that branch. A branch can point forward or backward, which is what makes a rejection and rework loop expressible rather than approximated.
Send it through the same pipeline
Manual SOPs get the same duplicate detection, review and approval gate, version history, and scheduled re-verification as generated ones.
No account neededNo credit cardSee the whole SOP before you sign up
Reach for this when
- A process you know cold and can write faster than you can explain
- Compliance or safety procedures where exact wording matters and nothing should be paraphrased
- Correcting or rewriting an SOP that a generated draft got structurally wrong
- Teams that want the governance layer without using AI at all
Where this is not the right fit
- It is writing, so it takes as long as writing takes. The other four methods exist because that is usually the bottleneck
- No AI assistance on this path, by design. If you want a draft to start from, use one of the other methods and edit the result
Questions
Is any AI involved in the manual path?
None. Nothing is generated, suggested, or rewritten. You write every step.
Can I do if/then branching?
Yes. A decision step asks a question and each answer routes to a specific later step, including an earlier one, which is how a rejection and rework loop is represented properly.
Do manually written SOPs get the review workflow?
Yes. Approval, version history, duplicate detection, and scheduled re-verification all work the same regardless of how the SOP was created.
Is manual writing available on the free plan?
Yes. All five creation methods are available on every plan, including the free one.