A permit is not a form. It is an operating state defining who works, where, when and under what conditions. Weak status, roles or isolation turns documentation into false assurance.
Applied case · Hot work near live operations
- Challenge
- The permit was valid on paper, but isolation status and nearby work conflicts were not visible at activation.
- Response
- Request, review and issue roles were separated, and activation was tied to field, gas and isolation verification.
- Outcome
- Work start became an evidence-gated decision with a visible trail for suspension, restart and closeout.
Start with a verifiable request
The request must define task, location, duration, people, equipment, permit type and linked documents before review.
- Link the permit to RAMS and real boundaries.
- Define isolation, gas, barrier and emergency conditions.
- Escalate conflicts with other work before issue.
Separate authority and responsibility
Role segregation prevents one person preparing, approving and activating work without independent challenge. The decision, owner and time must remain visible.
- Requester, reviewer, issuer, performer and monitor.
- No activation before field verification.
- No silent extension beyond validity.
Close the control cycle
Closeout confirms work stop, removal of people and tools, isolation release or transfer, reinstatement and updated asset or interface status.
- Record suspension, restart and change.
- Verify closeout in the field.
- Keep an auditable time trail.
What must be visible before acceptance?
- Link the permit to RAMS and real boundaries.
- Define isolation, gas, barrier and emergency conditions.
- Escalate conflicts with other work before issue.
- Requester, reviewer, issuer, performer and monitor.
- No activation before field verification.
- No silent extension beyond validity.
- Record suspension, restart and change.
- Verify closeout in the field.
- Keep an auditable time trail.