Operations workflow
Turn voice notes into a usable SOP
The person who knows the process is usually the person with no time to document it. Talking through a task takes four minutes; writing it up takes an afternoon, which is why it never happens. This guide covers recording the walkthrough properly, converting the transcript into a numbered procedure, and the test that decides whether the SOP is finished: someone else runs it without asking you a question.
Watch the 15-second walkthrough
Video coming soon
The 15-second walkthrough for this guide has not been published yet. The written tutorial below is complete and stands on its own — the video repeats it, it does not replace it.
The full narration is in the script section.
What you start with
- The recording you transcribe
- A four-minute voice note walking through monthly invoicing, recorded while actually doing it, including the two places you paused to check something.
- The context you add
- Who performs the task, which systems and logins are involved, and what triggers it - a date, a request, or an upstream handover.
- The finish line you define
- What 'done' means in observable terms: the file saved to a named folder, the ticket closed, the confirmation email sent.
Handling sensitive information
Voice notes recorded at your desk pick up more than the task: passwords read aloud, customer names, colleagues talking nearby. Read the transcript before pasting it anywhere, remove credentials and personal data, and check whether your transcription tool retains audio. Never narrate a password or an API key into a recording you intend to process.
The process, step by step
Step 1
Narrate while you work, not from memory
Recall skips steps that habit has made invisible - the login, the filter you always apply, the file you always rename. Recording while you do the task once captures those automatically.
Step 2
Say the decisions out loud
Every time you make a judgement call, say why. 'If the amount is over five hundred I send it to Priya first' is the sentence that turns a step list into a procedure someone else can actually run.
Step 3
Convert the transcript into numbered steps with checks
Ask for numbered actions, the decision points as if-then lines, and a short verification list at the end. Prose is unusable at 4pm on a busy Friday; numbered steps are.
Step 4
Test it on someone who has never done the task
Give them the SOP and no help. Every question they ask is a missing step - add it in their words, not yours. Two rounds of this usually produces a document that survives your absence.
How to review the result
- Can a competent newcomer follow it without asking you anything?
- Are the decision points written as if-then rules rather than 'use your judgement'?
- Does every step name the exact system, screen or file rather than 'the usual place'?
- Is there a definition of done that someone can verify without you?
- Have the exceptions you mentioned in passing survived the summarisation, or did they get smoothed away?
Limits and boundaries
- A transcript-derived SOP inherits every gap in the recording. If you skipped a step while narrating, it will not appear.
- Models tend to tidy away the awkward exceptions, which are usually the steps most worth documenting. Read specifically for those.
- This does not replace controlled documentation where compliance, safety or audit requirements apply; the resulting draft still needs your organisation's approval process.
- An SOP goes stale when the underlying tool changes. It needs an owner and a review date, which is a management decision, not an AI output.
Video script (not published yet)
The complete narration written for the 15-second walkthrough. It is published here so the wording is readable while the video is still in production.
- 00:00:00.000 → 00:00:03.500Record yourself doing the task once, narrating each step out loud as you go.
- 00:00:03.500 → 00:00:07.700Paste the transcript in and name the role, the tools used and the trigger that starts the process.
- 00:00:07.700 → 00:00:11.600You get numbered steps, the decision points, and a list of what to check before you call it done.
- 00:00:11.600 → 00:00:15.000Then hand it to someone who has never done the task. Their questions are your missing steps.
How AI was used to make this page
This page and the 15-second video script were drafted with AI assistance and then edited and fact-checked by a human before publication. The invoicing walkthrough is an illustrative example, not a transcript of a real company process.
Prompts used in this workflow
Each one is a one-time purchase with lifetime access.
Voice Notes to SOP Workflow
A five-stage playbook that turns a rambled description of how something is done into a written SOP, an exception table, a working checklist, and a training handoff someone else can actually follow.
SOP Writer (Standard Operating Procedures)
Turn how-you-do-things into documents anyone can follow — so the business runs without you explaining.
Job Handover Document Builder
Leaving, covering, or delegating a role — a handover so complete the phone doesn't ring on day one.