A founder opens a customer file, scans three messages and says, “That is ready to send.” A virtual assistant watching the demonstration can record the clicks. The harder task is discovering what made the file ready, which message mattered and what would have stopped the founder sending it.
That is where a VA can help turn experience into a useful standard operating procedure. The work involves interviewing, drafting and testing, with the responsible owner approving the rules. Business.gov.au distinguishes a procedure’s detailed task instructions from higher-level policies. Keeping that distinction clear prevents the person documenting a process from accidentally deciding company policy. Business.gov.au’s procedure guidance provides a useful starting point.
Start with one authorised demonstration
Choose a narrow task with a recognisable beginning and result: preparing a proposal for approval, for example. “Document everything I do” is too broad to produce a usable first procedure.
Ask the founder or an authorised process representative to demonstrate it. Confirm who can explain current practice and who has authority to approve the final procedure; they may be different people.
Use fictional training records or a carefully prepared example with unnecessary customer information removed. Close unrelated tabs, disable distracting notifications and keep credentials out of screenshots. Agree who can access the material, where it belongs and when the original recording will be removed under the business’s retention arrangements.
Obtain participants’ permission before recording and confirm any proposed AI transcription. If recording is not approved, use agreed written notes. The OAIC’s AI meeting-minutes guidance highlights necessary collection and recommends seeking consent as best practice given uncertainty about meeting content. The responsible owner should check applicable recording and privacy requirements rather than assume permission alone settles them. Read the OAIC guidance.
Ask why, then examine an awkward case
Let the demonstrator complete an ordinary example, then revisit the decision points. Useful questions include:
- What told you this information was trustworthy?
- Why did you check that field before continuing?
- What missing information would make you stop?
- Which decision can the VA make, and which needs approval?
- What evidence tells the next person the task is finished?
Follow with an awkward example. Suppose a customer requests Friday delivery, while the internal schedule has no confirmed date. The founder might know from experience that sales staff sometimes treat requested dates as commitments. A screen recording alone will not explain that distinction.
Ask the owner to define the approved response. The draft might require the VA to flag the discrepancy and request scheduling confirmation. It should not authorise a delivery promise merely because the founder made one during an exceptional demonstration.
Keep an unanswered-question list. Label each point as confirmed practice, an owner decision still needed or a possible improvement. Do not silently turn a proposed improvement into an instruction.
Turn the demonstration into a working draft
Use the notes to build a procedure someone can follow without replaying the entire session. This fictional proposal-preparation example shows the information to capture:
| Element | What the draft records |
|---|---|
| Trigger | Sales lead assigns a proposal-preparation task. |
| Inputs | Approved scope, current pricing source and customer request. |
| Action | Prepare the draft using the approved template; compare it with the supplied scope. |
| Decision | Is each required input present and consistent? Follow the owner-approved branch for missing or conflicting details. |
| Evidence | Save the draft link, input references and review status in the job record. |
| Escalation | Send unresolved scope, pricing or timing questions to the nominated owner; leave the proposal unsent. |
Replace vague directions such as “check everything” with observable checks and an accepted result. Show where an input comes from and how the learner recognises the current approved version. Include screenshots only where they explain something text cannot explain clearly.
The VA can own the drafting and question register. The process owner approves decision rules and authority limits. Our hybrid team organisation guide explores how those responsibilities fit into the wider team.
Give AI a limited drafting job
An approved AI tool can help organise approved notes into headings, identify repeated instructions or suggest questions to ask the demonstrator. Keep its assignment specific: structure the supplied material and mark gaps without inventing rules, deadlines, approval limits or customer promises.
Give every unresolved point a visible label such as “Owner confirmation required”. Compare the draft with the source notes, especially negative instructions and exceptions. A polished sentence still needs a traceable basis.
Do not treat a publicly available chatbot as a default destination for recordings or customer records. The OAIC recommends, as best practice, avoiding personal information—particularly sensitive information—in publicly available AI chatbots. Choose the tool and permitted information before starting the exercise, using the OAIC’s product-selection guidance.
Test with someone who missed the demonstration
Give a second learner the draft and approved training examples. Ask them to work through both the ordinary case and the awkward case while the author observes without supplying missing instructions.
Record where the learner pauses, chooses the wrong branch or cannot locate evidence. These observations reveal what the document still assumes. Check the resulting work, not simply whether every numbered step was ticked.
Keep the exercise within authorised training arrangements. Use drafts or a suitable test environment when sending, approving or changing a live record would create consequences. An instruction to stop and escalate should be tested as deliberately as an instruction to continue.
Resolve questions and release an approved version
Send the owner a short review pack: the procedure, unresolved decisions and learner-test findings. Obtain explicit answers, update the affected instructions and repeat the relevant test. If a policy question remains unresolved, define an approved stopping point rather than guessing the answer.
Record the approver, version and effective date, then show the team where the approved copy lives. For ongoing updates, use the approach in our solar operations playbook.
A useful first SOP makes the founder’s reasoning available at the moment somebody needs it. If your team needs support interviewing process owners, drafting procedures and organising review, talk to Nexus Group Global.
