The permit is the control. Not the paperwork about the control.

Then answer this from where you are sitting: which permits are live right now, and when was each one’s last gas test? A book is a fine place to write a permit down and a bad place to ask a question of. It also cannot refuse to become active when a signature is missing, which is the one thing a permit system is for.

Nor are most, and nothing here assumes otherwise. The reading is typed at the hole in a few seconds, and the platform supplies what a person standing there cannot: the time it was taken and who took it, captured automatically, and the verdict against your entry limits in words. “Oxygen 18.4% is below the 19.5% minimum.” is a sentence somebody can act on — a red square is not.

Fair, and worth being specific about rather than waving away. Ask us exactly what happens on a weak connection during the walkthrough — which parts hold locally, what syncs when, and what the record looks like in between — and hold us to a specific answer. A vendor who tells you connectivity does not matter for a permit system has not run one.

Yes, per site. The defaults on this page are 4 common ones and your entry procedure outranks every one of them. The verdict is frozen against the limits that applied at the moment of entry, so changing a limit next quarter never silently re-scores a reading somebody already made a decision on.

Captured on the hot-work type’s own fields, alongside the rest of that type’s conditions — a confined-space permit should not be asking about a fire watch, and a hot-work permit should not be asking about an attendant. Permit #28 on the register above was cancelled precisely because the fire watch could not be maintained with vehicles moving in the same bay, and that reason is on the record rather than in somebody’s memory.

Good — the signature should not happen at a desk. The area authority signs from the phone while standing at the job, reading the controls in front of them. A permit signed from an office is a signature about a description of the work rather than about the work.

No. A permit becomes active only with every required signature, the platform refuses the transition otherwise, and the API refuses it too. If that is a problem on a given day, the answer is a shorter approval path configured in advance — not a way around the one on the screen.

No, and this is the part worth checking in any product you look at. Requesting and approving are separate grants: Site Supervisors hold request only on permits, and the HSE Manager's approval grant reads "Sign — never own request". Self-approval is not a setting that can be turned on.

The holders and the issuer are notified before it does. Then somebody decides: work stops, or the permit is extended by a named person at a recorded time. What does not happen is a crew carrying on under a permit that quietly ended an hour ago, which is the state most paper systems are in most afternoons.

No. A gas test makes the work safe. An isolation makes the work safe. A permit records that somebody competent looked at the job, decided which of those were needed, and put their name to it — and afterwards it is the evidence that the decision was made before the work rather than reconstructed after it.

Yes, including on your own infrastructure. Permissions are granular — view, create, update, delete and approve are separate grants per module — and every signature is attributed in the audit trail on the site’s own clock.