Business & Revenue OpsFree
SOP From Your Screen Recording
The steps as described, plus the list of decisions your expert made without saying so, written out for them to answer.
You have a Loom of your warehouse lead walking through the returns process, recorded the week before she went on leave. Every tool ranking for this needs something else: a browser extension, installed, running, while somebody performs the task again live. Scribe captures your actions in real time and titles the guide from your clicks and keypresses. None of that helps with a recording that already exists, or with an expert who has already left, or with a process that never happened on a screen at all.
And a click stream is the easy half. It records that she opened the carrier portal and never why she chose that carrier, which is the judgement that took four years to acquire. Watch any walkthrough and the expert says it depends, or you'll know when you see it, or usually, and moves straight on. Those phrases are the procedure. Everything either side of them is data entry that anybody in the building could have described.
So two artifacts come back rather than one. The SOP in a house format, written from what was actually said and nothing more. And a sheet of every decision the speaker made without stating the rule, each phrased as a question they can answer in one sentence, ranked by what goes wrong if somebody guesses. The finished procedure then belongs in a governed SOP library, and a procedure with nobody left to record is a blank-page job instead. Which process to record first is a key-person ranking question.
The phrases that hide a whole procedure
Experts do not withhold their reasoning deliberately. They compress it, because after four years the decision does not feel like a decision. So it surfaces as a filler phrase and the transcript records it as one. It depends. You'll know. Usually. If it looks wrong. Whichever makes sense. I just check. The rule of thumb. Each of those is a rule the speaker holds and has never written down, and a click capture records the click that followed it while losing the rule entirely.
Written out properly, each one becomes four things: the condition being tested, the threshold that decides it, the default when nothing is obvious, and who to ask when the default does not fit. Dana's whichever makes sense turns out to be freight above 40 kilos, air under, and a named account that always goes air regardless. That is a rule anybody can follow. Written as she said it, the new person picks a carrier at random and finds out in six weeks.
The reason this matters more than the step list is that the step list is checkable and the rules are not. A new joiner following twelve mechanical steps gets stuck visibly and asks. A new joiner applying the wrong carrier rule produces work that looks correct. So the decisions sheet goes back to the expert while they are still reachable, and EPA's guidance on preparing procedures asks a draft to be tested by somebody other than the writer before anybody relies on it.
How it works
Send the transcript
A Loom or Zoom auto-transcript, meeting notes, or a rough recording somebody made on a phone.
Split doing from deciding
Mechanical actions become steps. Anything that turned on judgement becomes a row in the decisions sheet.
Write both artifacts
The procedure in your format, and the open questions with the speaker's own words quoted beside each.
Send the questions back
The expert answers in sentences, the rules go into the steps, and the sheet empties as it closes.
What you get
- The SOP in a house format, written only from what the recording actually says
- A decisions sheet, one row per judgement the speaker made without stating the rule
- The exact phrase they used, quoted, so they can recognise their own reasoning
- Each decision phrased as a question answerable in one sentence, not a research task
- The steps ordered as performed, with the inputs and outputs each one needs
- The flow as described, including the branches the walkthrough mentioned and skipped
Common questions
Do I need to install anything or re-record the process?
No, and that is the difference. Scribe, Tango and Guidde all capture live through an extension while somebody performs the task again, so an existing recording is unusable to them. This works from what you already have: a Loom link, a Zoom or Teams auto-transcript, meeting notes, or a phone video of somebody at a machine.
The auto-transcript is a mess. Does that matter?
Very little. Auto-transcripts mangle system names, split acronyms into letters and drop punctuation, and none of that hides a procedure. The one thing worth telling us is any term the transcript consistently gets wrong, because a name repeated forty times incorrectly is the only error that survives into the finished document.
What if the expert never explains why they do something?
That is the expected case and the reason the decisions sheet exists. Nobody narrates their own judgement after four years of doing the job; it compresses into it depends, or usually, or you'll know. Each of those becomes a row with the phrase quoted, what is missing from it, and one question they can answer in a sentence.
Will it invent the steps it did not hear?
No. Anything not in the recording is a gap in the sheet rather than a plausible sentence in the document. A walkthrough that skipped the exception path produces an SOP whose exception section names what was not covered, because a confidently written step nobody described is worse than an obvious hole.
Can it document a physical process rather than a screen?
Yes, and those benefit most, because no click recorder can see them at all. A phone video of somebody changing a filter, a voice memo walking through an inspection, notes from following an installer for a morning. The output is the same: steps as described, and the judgement calls surfaced as questions.
What do I do with the finished SOP?
Put it somewhere that knows whether it is still current. A single procedure in a shared drive is how the next person inherits four documents with the same title, so the finished document belongs in a register naming one version in force, which is what the SOP library pack installs. The rest sit in the template library.
How long a recording can it handle?
A full session. Walkthroughs run long because the expert keeps remembering exceptions halfway through an unrelated step, and those asides are the most valuable content in the recording. Send the whole thing rather than the part that looked on topic, including the digressions and the part where somebody interrupted.
SOP From Your Screen Recording
Fill in the form and your workspace opens with the work already underway.