Describe a process start to finish, and get the SOP back structured
Walk the process through once, the way you would for someone doing it tomorrow: what sets it off, who picks it up, which tools they work in, what gets approved by whom, and what happens in the cases that are not the happy path. Type it, paste the rough notes you already have, or press the microphone and talk it through. What comes back is a structured procedure, not a tidied-up copy of what you said.
What you actually get
- Walk through it in your own words, paste unstructured notes, or record your voice in the browser
- Voice is transcribed on the spot, then structured into a procedure
- Handles a paragraph or three pages of messy notes, in whatever order it comes out
- Names, tools, approvals, and exceptions you mention are carried into the steps rather than generalised away
- Output has a trigger, numbered steps, roles, and if/then decision branches
- Available on the free plan, and at /try with no account at all
How it works
Walk through it, out loud or in writing
Go through the process end to end. Name the people, the tools, the approvals, and the exceptions, and none of them has to be guessed for you. Out of order, half-finished sentences, and asides are all fine.
Sendabrief structures it
What you described is turned into numbered steps in subject-first active voice, with a trigger, the roles involved, and branching where you mentioned a decision. The specifics you gave stay specific.
Fix what it got wrong
Read it, correct anything off, then save it or send it for review. The draft is fully editable before it becomes a real SOP.
No account neededNo credit cardSee the whole SOP before you sign up
Reach for this when
- The process that only exists in one person's head, in the detail only they have
- Getting it out of someone before they go on leave, in one sitting, without them writing a document
- Turning a rambling voice note into something a team can actually follow
- Processes with approvals, handoffs, and exceptions that a recording of the screen would not show
Where this is not the right fit
- It structures what you tell it and does not invent the rest, so how complete your walkthrough is decides how complete the SOP is. This is deliberate: a confidently invented step is worse than a missing one
- Spoken input depends on transcription, so heavy background noise degrades the result
- For a click-by-click software walkthrough, the screen recording method produces better steps because it captures the actual screens
Questions
How much detail do I need to give it?
As much as you would give a new hire on their first day: what triggers the process, who does each part, which tools they use, and what happens in the awkward cases. A single line still produces a draft rather than an error, but it is a generic one, because every specific has to be guessed. The detail you put in is the editing you skip afterwards.
Will it make things up to fill gaps?
It is instructed to structure only what was actually in your input rather than inventing steps. Where a step is professionally implied but you did not state it, it is marked as implied so you can see it was inferred.
Can I just talk instead of typing?
Yes, and for a long process it is usually the faster way in: the same box takes live voice from your microphone, transcribes it, and then structures it. Talking through a procedure end to end takes a couple of minutes and produces far more detail than most people are willing to type.
What should I make sure to cover?
What triggers the process, who does each part by role, the tools and systems they work in, anything that needs approval and from whom, and what happens in the exceptions. Those are the five things people leave out, and each one is a gap you would otherwise fix in the editor.
Can I try this without signing up?
Yes. Go to /try, describe a process, and read the complete SOP before deciding whether to create an account.