Owner Talks, Assistant Writes: Where the Procedures Came From
About three in ten owners we mapped with handed over a recording or a voice note, and the new assistant wrote the procedure. What they handed over.
15 October 2026
Earlier this year, about three in ten owners we mapped work with had no time to write procedures. They handed over something else: a recorded walkthrough, a set of screen recordings, or a process talked through out loud, sometimes from the car. The new assistant wrote the procedure from it.
The material varied. Some of it was made for the purpose, and some of it already existed.
What owners handed over
- A recorded walkthrough. One owner with no capacity to write documentation recorded a walkthrough, and the procedure was written from it within one to two days.
- Voice, while driving. One owner talked ideas through by voice while driving, and the assistant turned them into written policies.
- A short video for each task. In one session nothing could be shown live, so the owner agreed to record a short video for each task instead.
- Screen recordings to fill gaps. For tasks the live session did not cover, one owner offered short screen recordings to fill the gaps.
- Training videos made for someone else. A long multi-step process already existed as training videos made for a previous person. Those videos became the source for the written procedure.
Moving the writing to the person who will follow it
Our reading of why this pattern shows up: writing is the slow part of documentation, and it is the part that gets skipped. Turning a recording into written steps can sit with the person who will follow those steps, which leaves the owner with the part only they can do, explaining the work.
Material that already exists counts
The training videos in the last example were made for a previous person, for a different purpose, and still became the source for the new procedure.
Any recording made to train someone earlier is raw material a new assistant can write from.
Policies as well as procedures
The voice notes recorded while driving were ideas, and the assistant turned them into written policies. A procedure says how a task is done. A policy says what the business does in a situation, such as how to respond to a type of request.
A voice note is a quick way to get a policy out of the owner’s head and to someone who will write it down.
Three questions before the first week
- Which of your tasks already exist on video? Old training recordings, or screen shares from a previous handover.
- Which tasks can’t be shown live? Anything that happens at a time or place a session cannot reach can be recorded on the day instead.
- Which decisions do you explain better out loud? Those are candidates for a voice note the assistant turns into a policy.
Recording what can’t be shown live
When we map a role with an owner before a new hire starts, a task that cannot be shown live can be covered by a short recording, and the new hire writes the procedure from it. We have covered turning a recorded walkthrough into a reference document before.
You can see how that setup works. If you have no time to write procedures and want to hand work over anyway, book a Role Plan call.
Ready to build
your back office?
Book a call with Dusty. We work out the first role to hire, and afterwards you get your Role Plan in writing.
Related articles

Clean-Up Comes Before the Daily Routine
In about one in four roles we mapped this year, the first task was clearing a backlog before any daily routine could start. What that backlog looked like.

The Signal That Lets an Owner Step Back
An owner stepped back from a remote role and had no regular view of what was done. The setup behind it, and the signal agreed for the new role.

The Chasing Inside the Admin You Hand Over
In about one in three businesses we map with, a large share of the admin handed to a remote hire is chasing people. What gets chased, and the rules it runs on.