Talk through a process you have explained a hundred times. We ask the questions people usually skip, like what good looks like and what to do when it varies. Twenty minutes later you have a Word document someone else can actually follow.
Steps at the click by click level, your pet peeves written in as warnings, and every section editable before you download it
Talk it through
Dictate or type, with suggestions to tap
The it depends moments
Written out as rules anyone can follow
A Word doc to hand over
Editable first, then yours to download
Who this is for
Business owners, team leads, and operations managers who have explained the same process out loud more times than they can count. It works when you do it. The part that goes missing when someone else picks it up is never the steps, it is the judgement you make without noticing.
It works when you do it
The problem
Most SOPs list the actions and skip the standard. They say what to click, not what good looks like, when to make an exception, or who picks it up next. So people follow one once, hit something the document does not cover, and come back to you. This tool asks the questions that fill those gaps.
What you get
Steps written at the click by click level
The it depends moments written out as decision rules
Watch-out warnings built from the pet peeves you list
Quality standards and a clear done state
Voice dictation if you would rather talk than type
A review step where you can edit every section before it exports
A Word document to download, and a copy in your inbox
Anyone can list steps. What makes a process safe to hand over is knowing what to do when the situation is not the standard one. We ask you for those moments directly and write them in as rules, which is the part that lets someone else run it without checking in with you.
Most SOPs fail because they capture the steps and miss the standard. Here is the order that works for small expert businesses, and the order this tool follows when it builds the document for you.
Most free SOP templates online are a list of numbered steps and a header for the date. That is a checklist, not an SOP. A real SOP template carries enough context for someone else to make decisions the way you would.
The fields this generator produces, and the fields your own template should include:
Your VA does the task correctly but not the way you would do it. Every time.
You wrote a process doc once. It is eighteen months old and three versions behind.
The same question gets asked every week. You answer it slightly differently each time.
You delegated the task, then spent more time fixing the output than doing it yourself.
There are "it depends" moments in every process that only you know how to navigate.
You stopped writing SOPs because the last one took longer than just doing the work.
The problem is not the SOP. The problem is the SOP never captured how you think.
Decision logic built in
The "it depends" moments are captured as conditional paths, not footnotes.
Your pet peeves as warnings
The things that irritate you become highlighted callouts your team cannot miss.
Quality standards, not just steps
What "done properly" looks like is defined. Not assumed. Not implied.
Handoff points mapped
Where responsibility changes hands. Who passes what to whom. No gaps.
Voice-to-text capture
Talk through your process instead of typing. The AI structures what you say.
A Word document you can hand over
Formatted, editable before it exports, and a copy lands in your inbox.
This tool fixes all three. It captures how you think, not just what you do.
The long version
A standard operating procedure is a written record of how one piece of work gets done to your standard, by someone who is not you. Most templates you can download online record the clicks and stop there. That is why they get read once and never opened again.
The reason a process survives in your head is not the sequence. It is the judgement sitting underneath it. You know which client gets the phone call instead of the email. You know the invoice goes out before the file, not after. None of that is written anywhere, so the work comes back to you every time.
An SOP earns its place when it carries the decisions as well as the steps. That is the gap this tool is built to close.
Take a common one, sending a client their monthly report. Here is the difference between a template and a procedure someone can actually run.
The template version
Prepare the monthly report and send it to the client.
The procedure version
Trigger: the second business day of the month. Owner: the account coordinator. Open the reporting folder, duplicate last month's file, rename it to client code plus month. Pull the figures from the dashboard, not from email. Good looks like: one page, plain language summary at the top, no unexplained variances. It depends: if a variance is over 15 per cent, the report goes to Sarah for a read before it goes out. Warning: never send on a Friday afternoon, questions land over the weekend and nobody is there to answer them.
Around twenty minutes per procedure using this tool, because you talk it through rather than write it. Writing the same document from a blank template usually takes an afternoon and still misses the judgement calls.
Then the procedure records the decision rules rather than a fixed sequence. If the work genuinely changes every time, the problem is upstream in the process design, and the Lazy Process Designer is the better starting point.
Yes. Every section is editable on screen first, and your edits carry into the final Word document rather than being overwritten by the generated draft.
A Word document you can hand over, store in your own drive, and edit later. No account, no locked platform, no export fee.
No. Start with the work that interrupts you most often and the work that only you can currently do. Those two lists cover most of what is holding a business to one person.
Use this first when the process itself is broken. Documenting a bad process just makes the bad process official.
Use this when you are not sure which procedures matter most. It shows you where clients actually feel the friction.
Use this to work out which tasks should leave you first, before you write a single procedure.
Documenting a bad process just makes the bad process official. The Lazy Process Designer redesigns the process. Then you come here to lock it in. Together they form a complete system.
Redesign a Process FirstEnter your details to start. We will send a copy of your results to your email so you never lose them.