The Platform · № 03
Every shop says safety comes first. This is the part that makes it true on a Tuesday afternoon when nobody's watching.
Gate A · Start
The button does nothing. Software that merely warns is software that gets clicked through at 7am in the rain.
Gate B · Closeout
A second gate at the other end, for shops that need the work signed out as well as in — including a two-signature mode where the tech and a safety approver must both sign before the job releases.
Hazard items live in a library and group into named sets — one for work at height, one for confined space, one for a routine service call. The dispatcher picks the set when the job is created, so a tech sees the checklist for this work rather than a generic list they learn to tap through.
Items can carry the standard they come from, so a line reads 29 CFR 1910.28 instead of "be careful up there." Your sets are built with you during setup.
The one that starts with "I did do the walkaround." Each item was ticked by a named person, at a time, in a place. Not "the crew" — the person.
Which cuts both ways, and should: a tech who did do it has proof, and that is worth as much to them as it is to you.
The named person and the role they held at the time.
Each item individually, as it was ticked, in the order it was ticked — not one lump "acknowledged" flag at the end.
The server's clock, not the phone's. A phone clock can be changed by the person holding it.
Coordinates at the moment of signing, to six decimal places.
The device and the network it came from.
The signature itself, stored as it was drawn.
At completion the whole filled checklist is also frozen as a snapshot, so the historical record survives any later edit to the underlying checklist template.
Each entry is sealed to the one before it with a keyed hash. The log is a chain, not a pile of rows — pull one out and the links either side stop matching.
It lives in the application and never in the database. So someone who reaches your records — a stolen backup, a bad actor with database access — still cannot forge an entry or soften one that already exists.
On request the system recomputes the entire chain end to end and names the first row that doesn't match, and whether it was edited, deleted or inserted.
Chaining isn't a setting. A switch that turned it off would leave unchained gaps that break verification later, so it runs for every event on every instance.
Plainly
We are not your safety consultant, and this is not a compliance certificate. Your hazard analysis, your safety program and your obligations under the law stay yours. We don't write them, we don't review them, and we don't approve them. If you need someone to build your program, that's a safety professional, not a software vendor.
It is called a Safety Gate, not a Compliance Gate, deliberately. Nothing here certifies you as compliant with OSHA or anyone else. A checklist item can cite a standard because you put that standard on it — that's your citation, not our legal opinion.
Whether the record helps you is not ours to promise. We built it to be the kind of record that holds up: contemporaneous, attributed, located, and tamper-evident. What weight it carries in a specific dispute is a question for your own counsel and your carrier. Any vendor who tells you their software makes you "legally protected" is selling you something they cannot deliver.
A gate can be switched off. You own the instance; an owner can turn the module off or take a job out of its scope. It stops the crew, not you — and the log records that too.
What software can honestly do is two things, and it does both: stop the work until the checklist is signed, and keep a record afterwards that nobody can edit without it showing. The record is the product. The compliance is yours.
We'll show you the gate refusing to open, then sign it and walk the audit trail — and then break a row in the log on purpose so you can watch verification catch it.
Email: [email protected] · included at $149/mo
