OSHA lockout separates shutdown from energy isolation

Shutdown is only one step in the sequence

Section 1910.147 establishes minimum performance requirements for controlling hazardous energy during covered servicing and maintenance. Its application sequence distinguishes preparing for shutdown, shutting equipment down, isolating energy sources, applying lockout or tagout devices, controlling stored or residual energy, and verifying isolation. A normal stop control may halt motion without isolating every energy source or preventing reaccumulation.

That distinction should appear in digital procedures. An equipment record can identify energy types and isolating devices, but the active work record must preserve which procedure and revision applied, who was authorized, which steps were completed, what stored energy was addressed, how isolation was verified, and what exceptions or changes occurred. A checked box without the underlying context is weak evidence.

Roles determine who may act

The rule differentiates authorized employees who perform lockout or tagout from affected employees who operate or use the equipment or work in the area, and it assigns training and notification obligations accordingly. It also addresses other employees whose work may be in the area. A general training completion does not by itself establish authorization for a particular procedure or task.

Buyers can test whether a system connects current role, training, equipment, procedure, shift, and work authorization at the moment of use. The workflow should handle reassignment, contractor participation, group lockout, shift changes, absent employees, and notification before application and after removal. Site policy and competent human judgment remain essential; software cannot infer safe authority from a directory entry alone.

Verification and inspection are different evidence

Before covered work begins, the authorized employee must verify that isolation and deenergization have been accomplished. When stored energy can reaccumulate to a hazardous level, verification must continue until the work is complete or the possibility no longer exists. This is task evidence tied to the machine's condition, not merely a statement that a standard procedure was selected.

The rule separately requires periodic inspection of the energy-control procedure at least annually, performed by an authorized employee other than the employees using the procedure being inspected. The inspection must correct deviations or inadequacies and be certified with identified information. A platform should not treat annual inspection, routine work verification, and training as interchangeable records.

Changes should trigger a controlled review

OSHA requires retraining when job assignments, machines, equipment, processes, or energy-control procedures change in ways that present a new hazard, and when inspection or other evidence reveals gaps in knowledge or use. That creates a change-management dependency. Equipment modification, line reconfiguration, new energy source, procedure revision, or observed deviation needs a path to affected records and people.

A production-like test can introduce a procedure revision during an open work order, a worker with expired authorization, an unexpected stored-energy condition, and a shift transfer. Ask the provider to show the safe stop, escalation, notification, retained history, and reporting. The source sets regulatory requirements; it does not validate a specific procedure, device, training program, or software configuration.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Safety Operations Standard will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.