A permit workflow is often drawn as a simple sequence: request, review, approve, issue, close. In real operations, the important part is not the labels. The important part is what each step proves before the next step is allowed.
If the request is weak, review becomes guesswork. If review is rushed, preparation becomes field improvisation. If preparation is disconnected from LOTOTO or documents, issue becomes a signature without control. If closing is treated as a formality, the organization loses the moment where the work is returned to operations.
Request: define the job clearly
The request should make the work understandable before risk review starts. It should describe the job, location, asset or area, timing, requester, executing party, methods, tools, and expected conditions.
This is where many permit problems begin. A request that says "maintenance on pump" may be enough to recognize the asset, but not enough to understand whether the work involves opening the system, hot work, lifting, cleaning, confined space entry, or interaction with nearby operations.
The better the request, the less the site depends on informal explanation later.
Review and approve: decide what control is needed
Review is where the organization decides what the permit requires. Which hazards apply? Which controls are mandatory? Does the job need a TRA? Which approval route fits the risk? Which documents should be used? Are there competence requirements? Does the affected area create extra constraints?
This step should not be a generic approval ritual. It should use the job context to produce consistent permit decisions. Vinkey's model supports this by keeping risk logic, measures, documents, and role-based approvals close to the permit instead of leaving each reviewer to rebuild the same reasoning manually.
Prepare: make the conditions real
Preparation turns the reviewed permit into something that can be issued in the field. Measures need to be understood. Documents may need to be available. Barriers may need to be placed. Equipment may need to be isolated. LOTOTO plans may need to be prepared and verified. Simultaneous operations may need another look because the site can change between approval and issue.
Preparation is where a permit becomes more than permission. It becomes a controlled setup for work.
Issue, revoke, and close
Issue is the field decision that the work may start under the stated conditions. It should happen only when the required controls and isolations are ready and the people involved understand the limits of the permit.
Revocation matters because conditions can change. Weather changes. Production restarts. A nearby permit is issued. A control is removed. A contractor team changes. The permit workflow needs a traceable way to stop work when the basis for issue no longer holds.
Closing is not just archiving. It confirms that the permit-controlled work is finished, the field condition is understood, and any required return-to-operation step has been handled.
The Vinkey view
Vinkey connects the permit workflow to the operating reality around the job. Request, review, preparation, issue, revoke, and close are not separate administrative moments. They are control points around work that can affect people, assets, production, quality, reliability, and site continuity.
That is the difference between a digital permit and a Permit to Work model. A digital permit records the approval. A Permit to Work model helps the organization decide whether the work is ready to proceed, as described in what Permit to Work is in industrial operations.