The depth LOTO actually needs —
built in, not bolted on.
Most digital LOTO tools are a checklist with a logo. Setyr models how isolation really works: equipment with many energy sources, work that spans crews and shifts, locks that change hands, and a record that has to hold up long after the job is done.
What sets Setyr apart
These are the capabilities that separate a system built for industrial LOTO from a generic form filler. Each one reflects a real failure mode that paper — and most software — leaves open.
Guided execution, step by step
Technicians work through equipment-specific procedures on any device — each isolation point confirmed as it is locked, tagged, and verified. The procedure enforces what must happen without forcing a rigid order where the field does not support one.
A tamper-evident record
Step status is never simply overwritten. Every confirmation, and every reversal, is recorded as a new entry in an append-only history — so the completed record shows exactly what happened, in what order, and by whom. That is the artifact an auditor actually wants.
Hierarchical work orders
Real shutdowns are not flat lists. Setyr models parent and child work orders, and a parent reflects the combined isolation status of everything beneath it — so a supervisor can see at a glance whether a multi-equipment job is fully isolated, not just whether one task is done.
Group lockout
Full multi-technician and group lockout support: each worker applies and accounts for their own lock, with individual confirmation. No one is protected by someone else’s lock, and no one is left out of the record.
Person-in-charge governance
For programs that designate a person in charge of a lockout, Setyr makes the handoff explicit: the role can be assigned, accepted, declined, escalated, and signed off — each step confirmed by the individual and logged. It is opt-in per site, so programs that do not work this way never see it.
Two-person approval integrity
Where your program requires separation of duties on procedure approvals, Setyr can enforce it on the server — the same person cannot quietly fill more than one role in the approval chain. It is a per-site setting, because not every workforce is large enough to need it.
Equipment and procedures, the way they really relate
A procedure can cover many pieces of equipment, and a piece of equipment can be served by many procedures. Setyr models that many-to-many reality directly instead of forcing an artificial one-procedure-one-machine simplification.
Periodic procedure review
OSHA requires procedures to be reviewed on a schedule. Setyr tracks review due-dates per procedure, ties each review to the specific version it covers, and surfaces what is coming due — so the annual inspection is something the system manages, not something you chase.
One system for the whole LOTO lifecycle
Author
- Equipment-specific procedures with energy-source mapping
- Isolation-point sequencing with lock, tag, and verify steps
- Attach P&IDs, electrical drawings, and reference documents
- Procedure versioning and change control
Execute
- Guided, device-agnostic execution in the field
- Group and multi-technician lockouts
- Live isolation status for supervisors
- Work-permit association
Prove
- Append-only record of every step and reversal
- Periodic-review tracking for annual inspection
- Role-based access for operators, supervisors, and safety staff
- Reporting at site and enterprise level
One enterprise. Many sites. Real separation.
Setyr is multi-tenant by design. Each customer’s sites are kept in separate data stores rather than sharing one pooled database filtered by a column — so one site’s data is never one query mistake away from another’s. It is separation built into the architecture, not a setting.
Above the sites, an enterprise view rolls activity up across the whole organization: where lockouts are active, how work orders are trending, and where attention is needed — without losing the site-level detail each facility runs on day to day.
Site-level operations
Each facility runs its own equipment, procedures, work orders, and users.
Enterprise-level oversight
Cross-site reporting and activity rollups for safety leadership and admins.
Role-based access
Operators, supervisors, safety managers, and enterprise admins each see what their role requires.
Tenant isolation by design
Customer data lives in separate stores — isolation is structural, not policy.
Deliberate design choices
Records reality — doesn’t pretend to be the lock
Setyr documents what was done; it does not hold your padlock hostage to a vendor’s connected hardware. The software is the system of record, not a gatekeeper on the physical lock — which keeps your program in your control.
Works with the locks you already own
Lock binding is hardware-agnostic. There is no proprietary connected padlock to buy for every isolation point — and none of the cost, battery replacement, cold-weather fragility, or hazardous-area certification upkeep that battery-powered electronic locks carry. Setyr is the software layer on top of the safety hardware you already trust.
Flexible where programs differ
Every operation runs LOTO a little differently. Setyr uses cascading site, work-order, and procedure settings so each customer can turn on the rigor they need and leave the rest quiet — without forking the product.
See it against your equipment
We will walk through how Setyr maps to your procedures, your isolation points, and your compliance requirements — using your environment, not a canned demo.