To turn verbal instructions into a useful written procedure, identify the starting point, extract the actions in order, and add a way to check each result. Keep unresolved details visible. Then ask someone to follow the draft without relying on your memory of the explanation.
The goal is not a shorter transcript. It is a guide a reader can use after the person demonstrating the task has left. This method is for ordinary work such as preparing a document or organizing presentation materials, not safety-critical procedures.
Start with the outcome and starting conditions
A walkthrough may begin halfway through a task: the right folder is already open, the correct version is selected, and the speaker knows which files to ignore. A later reader may have none of that context.
Before writing steps, complete this short header:
- Outcome: What should exist or be true when the procedure is complete?
- Starting point: Where should the reader begin, and which materials must already be available?
- Scope: Which ordinary situation does this guide cover, and which variations need separate instructions?
- Status: Is this a draft, checked walkthrough, or guide that needs an update?
For example, “prepare the slides” is too broad. “Create a PDF review copy of the workshop slides in the designated Review folder” gives the reader a visible destination. It does not yet explain how to get there.
Separate actions from the speaker's commentary
Read your notes or the transcript once for meaning before numbering anything. Mark actions, conditions, background explanations, and unanswered questions separately. An aside about last month's workshop should not become a required step. A correction such as “actually, use the Review folder” needs to replace the earlier direction in the draft.
If your source includes an available recording, return to the relevant moment when the wording is unclear. Spoken references such as “this one” may still be impossible to resolve from audio alone. Ask for the missing object or location instead of inventing it.
Keep task assignments elsewhere. “Taylor will prepare the review copy on Friday” belongs in a task record; the procedure explains how anyone assigned that job should do it. Our meeting action-item guide covers the separate assignment workflow.
Use an action, check, branch, and source card
For each numbered step, draft four short fields:
- Action: Where does the reader act, what do they do, and to which object?
- Check: What visible result tells them the step worked?
- Branch or question: Is the step conditional, optional, or waiting on clarification?
- Source: Which passage, demonstration moment, or later clarification supports it?
The source field can stay in working notes while the final guide shows only what the reader needs. Do not remove an unresolved question just to make the layout cleaner.
Google's procedure-writing guidance recommends giving context and prerequisites before the steps, generally using one action per step, and putting location before action and action before result. Use those principles to edit the extracted instructions; the four-field card here is our editorial template, not a Google standard.
Microsoft's instruction-writing guidance also emphasizes numbered procedures, concise task headings, and including actions that actually complete the process. A guide that stops at “prepare to export” has not yet told the reader how to finish.
Worked example: prepare workshop slides for review
This example is fictional. It is not a customer account, a Recolx internal procedure, or output from a Recolx product.
Imagine this spoken explanation:
“Start with the workshop deck I marked for review. Make a copy first. Take out the exercise-answer slides from the copy, then export it as a PDF. Check that the answers are gone and the diagrams are readable. Put the PDF in the Review folder. If a diagram is clipped, go back and fix that slide before exporting again. Use our usual file name.”
Do not turn “our usual file name” into a guessed naming rule. Here is a more useful draft:
- Outcome: A checked PDF review copy, without the exercise-answer slides, in the Review folder.
- Starting point: The deck identified by the presenter, access to the Review folder, and confirmation of which slides contain exercise answers.
- Open question: Ask the presenter for the required file name before completing the final placement step.
- Duplicate the identified workshop deck. Check that you are editing the copy and that the source deck remains unchanged.
- In the copy, remove the identified exercise-answer slides. Check the slide list against the presenter's clarification. Do not guess which slides count as answers.
- Export the edited copy as a PDF. Open the exported file to confirm that a reviewable PDF was created.
- Review the PDF. Confirm that the answer slides are absent and the diagrams are readable. If a diagram is clipped, correct the copy, export again, and repeat this check.
- Use the confirmed file name and place the checked PDF in the Review folder. Open it from that folder to confirm you placed the intended version there. Keep this step pending until the naming question is resolved.
The draft deliberately avoids naming software buttons that the explanation never identified. If the intended reader needs exact export controls, ask which application and version they use, observe that part of the walkthrough, and add the verified steps.
Test the guide without supplying the missing context
Give the draft and its stated starting materials to a colleague who did not write it. Ask them to describe or perform this ordinary task using the guide. Note where they ask “which file?”, “where?”, or “how do I know it worked?” Those questions identify details the document has not yet supplied.
Revise the affected step, then check it again. Record who checked the guide, when, and under which conditions. If the naming question is still open, keep the status as a draft rather than calling the procedure verified.
Store the checked guide with a link to its source notes. Our meeting knowledge-base guide covers organizing and finding those records later.
Common questions
Should every sentence become a step?
No. Keep required actions in the procedure, useful explanations beside the relevant action, and unrelated discussion outside it. Preserve conditions that change what the reader should do.
What if the demonstration and spoken instructions disagree?
Record the mismatch and ask the demonstrator which method applies. Do not quietly choose the version that sounds more polished.
Does this require a recording or a particular app?
No. You can work from ordinary written notes and follow-up questions. If you are also comparing capture options, consult the current Recolx Tap product page separately; this guide does not assume any device can automatically produce a verified procedure.
Try it on one small walkthrough
Choose a task you expect to repeat. Write its outcome and starting point, build the action-and-check steps, and leave unresolved details labeled. The useful finish line is a reader who can follow the guide and recognize the result, not simply a transcript with numbers added.
