Many plants.
One account of what is locked out.
A corporate safety lead has a different problem from a plant safety lead. Not "is this machine isolated" but "are eleven sites running the same program, and can I prove it in one place when the auditor asks". Setyr keeps each site's data genuinely separate, then reads across all of them for the people whose job spans the whole estate.
Each site owns its own data.
Every site is a separate, isolated data store — not a filter on a shared table. A site's procedures, equipment, locks and records belong to that site, and one plant cannot read another's. That is the boundary the whole product is built on, and it is why a site keeps working on its own terms while the estate is read above it.
Procedures are authored per site, against that site's equipment. A plant is never blocked waiting on corporate, and corporate never edits a procedure out from under a crew mid-shift.
Single sign-on through your own identity provider, so joiners and leavers are handled where you already handle them rather than site by site.
Customer-level administrators and roles are managed once, above the sites, rather than repeated in every plant's user list.
A live board that tells you what it could not see.
The cross-site lockout board shows what is locked out right now across every site you have access to. The part worth pausing on is the honesty: it reports how many sites answered and how many did not. A dashboard that silently drops an unreachable site tells you the estate is quiet when it is actually unknown — which is worse than no dashboard, because you will believe it.
The same applies to anything run across the estate. A periodic-review report that reached nine of eleven sites says so on its face, rather than reading as a complete answer.
The questions an auditor asks, across every site at once.
These are the same records a single site produces for itself — read across the estate rather than gathered by email the week before an inspection.
Which procedures are due, overdue or reviewed, at every site. The thing you are looking for is the plant that has quietly stopped reviewing.
Who is trained for what, by site. Authorized-employee training is the requirement most often missing when an inspector asks for it in writing.
The lockout record itself, exportable as PDF, so an inspection at one plant does not become a scramble across eleven.
A report builder covers the questions those three do not: build it once, save it, and have it delivered on a schedule to the people who need it — rather than depending on someone remembering to run it.
Per site, and the discount is published too.
Sites four to nine are 10% off, sites ten and up are 15% off, on either plan. That is the entire schedule — there is not a different one for people who negotiate hard. Users are unlimited on every site, so bringing two hundred contractors on for a turnaround does not change the bill.
The estate-wide board, saved and scheduled reports, and the report builder are Professional Plus. A single plant proving the program to itself does not need them; an estate does.
Start with one site.
Nobody rolls out eleven plants at once, and we would not advise it. Prove the program at one site, then add the rest — each keeps its own data, and the estate view appears as soon as there is an estate.