How to Turn an SOP Into a Training Lesson

An SOP records a process. A lesson changes what someone does on the next shift. So you do not convert the whole document. Take the step that causes mistakes, check it against how a skilled person works, and make it short enough to learn before a shift and use during it.

Do not start with the whole manual. Ask your managers which mistakes they fix every week and which questions new hires keep asking. Pick the procedure behind the most common one. A narrow task, like balancing the register at night, is easier to teach and test than a broad topic like customer service.

• It happens often, so a new hire will do it soon.
• Getting it wrong costs money, time or a customer.
• Someone on your team clearly does it right.

SOPs drift. The written version says one thing, and the person who does it right does something a little different, usually for a good reason. Record a short voice interview with that person. Ask them to walk through the task out loud, name the steps people skip and say what they check before moving on. Keep the SOP and the recording as your sources.

• What do you do first, and why?
• Where do new people usually go wrong?
• What changed since the SOP was written?

Each piece has its own job. The lesson teaches the why and the how. The job aid is the short version used during the task. The check proves the person can apply it to a real situation.

• Lesson: the steps, the reason for each and the usual mistake, with photos or video if the task is physical.
• Job aid: the steps only, in the order people do them, short enough to read at the station.
• Check: a few scenario questions, such as what to do when the card reader fails in the middle of a sale.

Assign the lesson before the shift where the task happens, and put the job aid where the work is done. Then have a manager or a strong peer watch the first real attempt. The check shows whether the person understood the lesson. The attempt shows whether the lesson matches the job.

• Note where the new hire paused or asked for help.
• Note any step done differently from the job aid or the check.

If the new hire made the mistake the lesson was meant to prevent, look at the lesson first. Maybe a step was missing, the job aid was too long or the check asked the wrong thing. Update the source, redraft, approve and assign the new version. If the skilled person's way beats the written SOP, update the SOP too. EPA guidance on writing SOPs makes the same point: an SOP stays useful only while it is current, so it should be updated and re-approved whenever the procedure changes.

A fictional plumbing company has a written SOP for the end-of-job walkthrough with the customer. New technicians often skip parts of it, and callbacks follow.

• The service manager picks the walkthrough because it drives repeat visits.
• The lead technician records a short voice walk-through and adds a step the SOP never had: run the water again and check under the sink.
• Elvina turns the SOP and the recording into a lesson, a phone-sized job aid and a check with three scenario questions, and the manager approves them.
• On the first ride-along, the new technician forgets the photo of the finished work, so the manager moves that step to the top of the job aid.

Elvina drafts the lesson, job aid and check from your sources; your manager assigns them on the Learning Platform and sees who completed what. A person chooses the procedure, confirms the steps with the expert, approves every version and watches the first attempt. If you would rather not draft it yourself, our team can do it on the platform today while Elvina takes over each step as it is confirmed.

Public sources, checked on the date shown.

• EPA's guidance on preparing SOPs says SOPs must remain current to be useful and should be updated and re-approved whenever procedures change. Source: https://www.epa.gov/sites/default/files/2015-06/documents/g6-final.pdf (checked 2026-10-05).