Permit-to-work software: authorisation, isolation and handover

Rules that define what a permit record must hold

Where a legal text prescribes permit content, use it as the minimum field list for the demo, then add your own procedure's requirements. The texts below were checked on 24 September 2026; check which apply to your sites.

• 29 CFR 1910.146 (US permit-required confined spaces): Paragraph (f) lists what the entry permit must identify, including the space, purpose, date and authorized duration, entrants, attendants, the entry supervisor, hazards, isolation and control measures, acceptable entry conditions, initial and periodic test results with the tester and time, rescue services, communication, equipment, and any additional permits such as hot work. The entry supervisor cancels the permit when the work is complete or a condition not allowed by the permit arises, and cancelled permits are retained for at least one year (paragraph (e)).
• 29 CFR 1910.147 (US control of hazardous energy): Covers servicing and maintenance where unexpected energization or release of stored energy could cause injury. Energy control procedures are inspected at least annually by an authorized employee other than those using the procedure (paragraph (c)(6)). The standard excludes, among others, construction, electric-utility generation, transmission and distribution installations, electrical hazards covered by Subpart S, and oil and gas well drilling and servicing, so confirm which isolation rule applies before configuring the isolation record.
• Directive 1999/92/EC (EU explosive atmospheres at work): Where the explosion protection document (Article 8) requires it, work in hazardous places follows written instructions and a system of permits to work is applied for hazardous activities and for activities that may interact with other work to cause hazards; permits are issued by a person with responsibility for this function (Annex II, Part A, point 1.2).
• HSE HSG250 (Great Britain permit-to-work guidance): Guidance, not law, for the petroleum, chemical and allied industries (2005) that places the permit within planning, competence, risk assessment and review.

A platform that stores these fields does not make a permit compliant. Ask the vendor to show a permit that cannot be issued while a required field, test result or cross-referenced permit is missing.

A different exception test for each qualifying product

These proposed tasks follow the same complete product list and order as the rule above. They test the boundary suggested by each documented scope; they are not observed results or assurances that a control will pass.

• Safetymint

  Permit module linked to task risk and isolation records.

  Demo task: Suspend a permit while a second user is disconnected; reconnect and show which status governs further approval and work.

  Scope source

• Sitemate

  Hot works permit system

  Demo task: Demonstrate the documented hot works permit system with a rejected approval and a changed work condition.

  Scope source

• IAMTech iPermit

  Industrial permits sharing isolation certificates.

  Demo task: Link two permits to one isolation, hand back only one job and demonstrate the remaining restriction on restoration. Resolve version-specific offline claims separately.

  Scope source

• GOARC

  Permit and LOTO applications within control of work.

  Demo task: Change an isolation after permit approval and show the required authorization sequence and the status visible to the next shift.

  Scope source

• Pisys Permit to Work

  Permit board with linked isolation records and plot plans.

  Demo task: Use the plot plan to identify overlapping jobs, hand back one permit without clearing their shared isolation, then make the Maximo or API handoff unavailable and show which status remains authoritative.

  Scope source

• Prometheus Group

  ePAS electronic permitting alongside separately scoped maintenance and barrier tools.

  Demo task: Change the source work order after ePAS approval; show how the mismatch reaches the permit issuer and who decides whether reauthorization is required.

  Scope source

• Rapid Global

  Hot work permit issuing

  Demo task: Demonstrate the documented hot work permit issuing with a rejected approval and a changed work condition.

  Scope source

• Sphera Control of Work

  Dedicated Control of Work with staged isolation plans.

  Demo task: Move between two work stages with different isolation points; demonstrate the approvals and dependent permits required before each point is restored.

  Scope source

• Intelex

  A named hazardous-work application, distinct from regulatory permit tracking.

  Demo task: Submit a hot-work request with incomplete supporting evidence, reject it and demonstrate the permissions required to resubmit and authorize it.

  Scope source

• Tekmon

  Configured work requests with job and location-based routing.

  Demo task: Change the job location after routing, remove a required risk assessment and show who must reassess and approve the revised request.

  Scope source

• Cority

  CorityOne work permits cover configurable approvals and conflict monitoring.

  Demo task: Create overlapping work at one location, change one approval route and show how the coordinator resolves the conflict before authorization.

  Scope source

• Enablon

  Control of Work with separately named permit, isolation and operational-risk applications.

  Demo task: Carry a changed risk assessment into a live permit and show which application controls suspension, reapproval and the isolation handoff.

  Scope source

• Evotix

  Enterprise lists permits and isolation; Professional entitlement cannot be inferred.

  Demo task: Use the quoted Enterprise modules to suspend a permit, preserve its linked isolation and transfer responsibility to the incoming shift.

  Scope source

• VelocityEHS

  Electronic permits connected to contractor qualification checks.

  Demo task: Let a contractor qualification expire after the request is approved; demonstrate the warning or gate and the person authorized to resolve it.

  Scope source

• BizzMine

  Hazardous substances, work permits, management of change and lockout tagout

  Demo task: Demonstrate the documented hazardous substances, work permits, management of change and lockout tagout with a rejected approval and a changed work condition.

  Scope source

• CORE-EHS

  CORE e-PTW is a named product within a wider EHS portfolio.

  Demo task: Attempt to authorize a job with an incomplete isolation check, then close it with missing hand-back evidence and inspect both outcomes.

  Scope source

• EcoOnline

  Permit to work and contractor control

  Demo task: Demonstrate the documented permit to work and contractor control with a rejected approval and a changed work condition.

  Scope source

• Qavach.AI

  Permit review and closeout belong to the optional safety-module scope.

  Demo task: Use the quoted safety module to delegate an unavailable approver, refuse an unauthorized approval and retrieve the final closeout history.

  Scope source

• Salus

  Forms, JHAs, permits, inspections and corrective actions

  Demo task: Demonstrate the documented forms, jhas, permits, inspections and corrective actions with a rejected approval and a changed work condition.

  Scope source

• SMS360

  Work permits

  Demo task: Demonstrate the documented work permits with a rejected approval and a changed work condition.

  Scope source

• TenForce

  Permit to work with isolation and simultaneous operations

  Demo task: Demonstrate the documented permit to work with isolation and simultaneous operations with a rejected approval and a changed work condition.

  Scope source

Tasks revised 28 September 2026 from the existing profile evidence. Pisys's current API and Maximo material was rechecked on that date; the other sources retain their profile research dates. General mobile access does not establish disconnected authorization.

A permit from request to close

The figure walks one permit through request, risk review, isolation, issue, work, suspension, handback and close, with the loop that sends a suspended permit back for review.

Run this proposed demonstration

1. Request a permit for a defined job, location and time window.
2. Demonstrate roles, supporting records and a rejected approval.
3. Introduce competing work and show how a coordinator receives the conflict.
4. Suspend or change the work and trace the authorization history.
5. Verify closure, exports and the current status seen by each role.

Record the proposed production plan, application, version, role, evidence and unresolved limitation. These exercises are evaluation suggestions, not tests performed by this site.

Plan the digital rollout and its acceptance evidence

Configure the workflow around the agreed operating procedure, then test exceptions and handovers before replacing existing paper or spreadsheet arrangements.

1. Map requester, issuer, performing authority and coordinator responsibilities for your process.
2. Agree status transitions, permissions, required evidence and a fallback.
3. Configure a representative scenario and test denied access and incomplete evidence.
4. Test changed conditions, shift handover and an unavailable approver.
5. Approve rollout only after the responsible team accepts the evidence and support arrangements.

These are rollout checks for your own configuration, not tests performed by this site.

Sources and evaluation limits

Guide revised 28 September 2026. Each listed product line carries its source, and each linked profile lists its vendor sources with their check dates. The editorial methodology separates vendor documentation from observed results. No performance score is assigned. AI-assisted explanations may be incomplete; confirm primary documentation and the agreed operating procedure.