Training to SOP
Train it once and capture it, so the next new hire follows the recording instead of being trained from scratch all over again.
About an hour · PDF + Word template
Send me the guide
Enter your email and download the PDF + Word template to keep.
We'll save your email to send the occasional update worth reading. No spam, unsubscribe any time.
Your best technician knows things nobody has written down. Every time they train someone, that knowledge gets said out loud once and then evaporates, and the next new hire gets a slightly different version.
What an hour turns into
One training session becomes one written procedure. Budget about an hour: twenty to forty minutes of recording, and the rest checking what comes back. Everything the guide uses is free.
Pick the session that repeats, not the dramatic one
The instinct is to record the strange failure or the emergency. Do not. Record the thing that happens over and over.
Good candidates: something a new hire needs in their first two weeks, something you have explained more than five times this year, something that gets done differently depending on who does it, and something where a mistake costs a callback.
Pick one procedure, not a whole day. A single job start to finish is plenty. Trying to capture how we do maintenance produces a transcript nobody can turn into anything useful.
Tell them you are recording, and say why
Say it out loud before you start and get a yes. This is not only good manners. Recording laws vary by state and some require everyone in the conversation to agree, so check what applies where you work before you press record rather than after.
How you frame it changes what you get: tell them you want to write this down properly so they do not have to explain it forty more times, and so the next person gets the same version they are giving today.
People teach differently when they think a recording is about assessing them. Make it obvious the recording is aimed at the procedure, not at the person. If a customer is present, ask them too, or record only the parts where they are not.
Recording it without buying anything
The voice memo app on your phone is enough. Get the phone close to whoever is talking. A shirt pocket beats a workbench, and a workbench beats a truck seat. Shops are loud, and a distant recording of an explanation is worth nothing.
Twenty to forty minutes. Past that the transcript gets unwieldy and the useful content thins out. Keep it to one continuous file rather than stopping and restarting.
Ask the trainer to narrate. Experts do things silently because the step is obvious to them. Tell them up front to say what they are doing even when it feels stupid to say it.
The three questions an expert never volunteers
Whoever is holding the phone has a job. Ask all three out loud, during the session. They pull out the things an expert leaves unsaid, because to them those things are not worth mentioning.
What goes wrong here if you rush it? This produces the warnings that never make it into written procedures.
How do you know it is done right? This is the acceptance check, and it is the step most written SOPs are missing.
What would you tell someone doing this alone for the first time? This is where the judgment lives, and judgment is the part that walks out of the door when someone leaves.
What this does not do
It does not write your whole operations manual. It turns one session into one procedure, and doing that ten times is how a manual gets built.
It does not check that the procedure is correct. What your best technician says is what you get, including their habits. Somebody who knows the work still has to read it.
It does not keep itself current. When the method changes, the written version is wrong until it is redone. If you would rather that stayed handled, SOP Procedures does the capture and the upkeep, and the free audit will tell you where the gaps are first.
Common questions
Twenty to forty minutes. Long enough for one procedure start to finish, short enough that the transcript stays workable. Trying to capture a whole day produces something nobody turns into a procedure.
Yes, and ask for it out loud before you start. Recording laws vary by state, and some require everyone in the conversation to agree. If a customer is present on a live job, ask them too, or record only the parts they are not in.
Let it run. One continuous recording is far easier to work with than a stack of restarts, and the tangents often contain the warnings you were trying to capture. You cut in the writing, not in the recording.
It replaces starting from a blank page, which is the part that stops most people. You still read what comes back and correct it. If you want the capture and the upkeep handled for you, that is SOP Procedures.