Lockout tagout training tracking under OSHA 1910.147 across plants: authorized vs affected employees, retraining triggers, and audit-ready records.
Got an LMS decision on your plate?
45-minute call. Plain-English audit. Fixed-price quote if there's a fit, or a "no" if there isn't. No deck. No pitch.
How to track OSHA training in an LMS so an inspector's records request takes minutes, not a panicked week of spreadsheets.
The features that matter for a manufacturing LMS — safety compliance, skills matrices, and shift-friendly delivery.
What an audit-ready training record actually contains, how long to keep it by standard, and why immutability is the whole point.
Lockout tagout training is a perennial OSHA compliance challenge, and across multiple plants it gets harder fast: different machines, different roles, and different retraining clocks at every site. The short answer to "how do I track it" is that you need to track training by role (authorized vs. affected vs. other), tie each record to the energy-control procedures it covers, and capture the retraining triggers that OSHA 1910.147 spells out. This post walks through how to do that defensibly across a multi-site operation.
It's a standard-specific companion to the broader OSHA training tracking guide and the manufacturing training playbook.
OSHA 1910.147 distinguishes three groups, and your records have to distinguish them too. Tracking everyone as one "LOTO trained" bucket is the most common reason a program fails an audit.
The standard requires that authorized and affected employees know their roles, so your platform has to map a person's role at a specific plant to the right training path. A maintenance technician at one plant may be authorized on equipment that doesn't even exist at another site.
Generic LOTO awareness training is not the same as being trained on your machine-specific procedures. OSHA expects authorized employees to be trained on the procedures for the equipment they service.
That means a defensible record links a completion to:
When procedures change at a single line in a single plant, you should be able to see exactly which authorized employees now need retraining on that procedure — without combing through spreadsheets at each site.
1910.147 names specific events that require retraining. A multi-site program lives or dies on whether the system flags these automatically instead of relying on a site manager to remember.
That last one ties to a separate 1910.147 obligation: the periodic inspection of energy-control procedures, required at least annually. The inspection itself generates a record, and its findings can trigger retraining. Your tracking system should treat the inspection as a scheduled, owned task with its own evidence trail — not a loose PDF in someone's email.
A single plant can almost get away with a binder. Across plants, four problems compound:
Different equipment, different procedures. The same job title carries different energy-control obligations at different sites. Your training paths have to be plant-aware.
Different clocks. Periodic inspections, procedure updates, and new-hire onboarding all run on local schedules. A corporate-level view that rolls these up is the only way an EHS director sees the real picture.
Transfers and contractors. When an employee moves between plants, their authorized status doesn't automatically carry — it depends on the equipment at the new site. Outside personnel under your LOTO program have to be informed of your procedures, and that has to be recorded too.
Audit on a deadline. When an OSHA compliance officer asks for proof that the authorized employees servicing a specific machine were trained on its procedure, you're on a clock. Pulling that per-machine, per-plant view should take minutes.
For operationally complex, multi-location manufacturers, this is exactly the case for owning a platform built to your equipment and sites rather than forcing your reality into per-seat SaaS. See how we approach this for enterprise operators.
Before your next audit or internal review, confirm you can produce each of these on demand:
If any of these require exporting raw data and rebuilding it by hand, the data may exist but it isn't audit-ready. You can pressure-test your current state with our audit-readiness check.
Lockout tagout training tracking isn't a single checkbox — it's role-based paths, machine-specific procedures, named retraining triggers, and annual inspections, multiplied across every plant you run. The goal is a system where a procedure change at one line automatically surfaces exactly who needs retraining, and where an auditor's request becomes a few clicks instead of a fire drill.