Skip to main content
    QHSEtech

    Buyer guidance by The QHSE Standard · Updated 20 September 2026

    Permit to Work Software for Enterprise

    1,000+ employees

    Explore products tagged for permit to work and enterprise in our catalog. The size band (1,000+ employees) is a discovery filter. Evaluate the people, sites and workflows in your deployment before choosing a platform.

    Digitise high-risk permits with approvals and isolations.

    Editorial responsibility: Dimitris Mitsios (Founder of The QHSE Standard; product marketing at Tekmon) · Tekmon pays for sponsored placements on this site (disclosure) · How pages are made · LinkedIn

    What to test before shortlisting

    Use these permit to work tasks for your Enterprise evaluation. Adapt them to your operations; these are demo requests, not observed vendor results.

    Bring a real workflow

    Use a simulated job to demonstrate issue, approval, suspension, handover and cancellation of a permit.

    Evidence to retain: Show who can change each state and how dependencies and conflicting work are handled. Software approval alone is not authorisation to perform a hazardous task.

    Add your operating context

    Use two business units with different approval chains, central reporting and an identity-system change.

    Before proceeding: Check delegated administration, segregation of sensitive records, integration ownership, staged releases and full exports at contract exit.

    Record demonstrated, partial, unmet and untested requirements separately. Leave a candidate pending if an essential requirement remains untested.

    See filled-in requirements, quote and pilot examples →

    Enterprise permit to work: delegated authority, shift handover and records that outlast the job

    A permit to work is the written control that stands between a planned job and a hazard such as stored energy, a confined space or a hot process. At a single site one supervisor can know every permit on the board. In a group of 1,000 or more employees, with several sites, shift patterns and contractor firms, nobody can, so the software has to carry what people used to carry in their heads: who may issue which type of permit, which jobs overlap, which isolations are still applied and who holds the job tonight.

    The regulations below do not mention software, but they describe records an electronic system has to reproduce faithfully: a signed authorisation before work starts, a stated purpose and duration, named people, recorded isolation and test results, cancellation at the end, and retention afterwards. Treat each of these as a field or a rule to test, not as a feature claimed on a web page.

    The enterprise questions are different from the single-site ones. Can approval authority differ by site and permit type, and can a named deputy act when an issuer is absent? Can a corporate auditor sample permits across all sites without gaining the right to approve them? Does the permit link to the isolation record and the maintenance work order, or are three systems reconciled by hand?

    Field conditions also decide the outcome. Plants, tank farms and shutdown areas often have patchy coverage, and vendors usually document offline capture for incidents and inspections rather than for permit authorisation. Ask each vendor, in writing, exactly which permit steps work without a connection, and run that test on a real device in a poor-signal area before signing.

    Rules that shape this evaluation

    • 29 CFR 1910.146, permit-required confined spaces (US): the entry supervisor named on the permit signs it before entry begins; the permit identifies the space, the purpose, the date and authorised duration, the entrants by name or tracking system, the attendants, the hazards, the isolation measures, test results and rescue arrangements; duration may not exceed the time the task needs; the supervisor cancels it when the task ends or prohibited conditions arise; and cancelled permits are kept for at least one year to support review of the programme.
    • 29 CFR 1910.147, control of hazardous energy (US): energy control procedures are documented, and each is inspected at least annually by an authorised employee other than the one using it, with the machine, date, employees and inspector certified; a lock or tag is normally removed by the person who applied it; group lockout needs a designated primary responsibility and personal devices; and shift or personnel changes need specific procedures that keep the protection continuous.
    • 29 CFR 1910.119, process safety management: hot work and safe work practices (US): a hot work permit documents that fire prevention and protection requirements have been implemented, the dates authorised and the object being worked on, and is kept until the hot work is complete; separate safe work practices must cover lockout/tagout, confined space entry, opening process equipment or piping, and control over the entrance of maintenance, contractor and other support personnel.
    • Confined Spaces Regulations 1997, regulation 4 (Great Britain): no one may enter a confined space for work unless it is not reasonably practicable to do the work without entry, and entry, work and exit (other than in an emergency) must follow a system of work that makes the work safe and without risks to health, so far as is reasonably practicable.

    Summarised from the linked official texts, read on 25 September 2026. This is buyer context, not legal advice: have the responsible specialists confirm which requirements apply to your sites.

    Questions to settle for this combination

    1. Can approval authority be set by site, role and permit type, with a named deputy when an issuer is absent, and is every delegation, including who granted it and when, kept in the audit trail?
    2. Can the permit be linked to the isolation points and the maintenance work order, so that releasing the permit and releasing the isolation are checked against each other and not reconciled by hand?
    3. At shift change, can an open permit be handed to the incoming supervisor with both signatures and a timestamp, without cancelling and re-issuing it?
    4. Which permit steps (viewing an issued permit, signing on, suspending, closing) work without a connection, and what happens to a permit approved in the control room while the field device is still disconnected?
    5. Can cancelled permits, amendments and signatures be retained unaltered and exported for the longest retention period that applies in any of your jurisdictions?
    6. Can a corporate auditor sample permits across all sites with read-only access, and can contractor employees from several firms be named as entrants and checked against their qualifications?

    Which documented capabilities matter most here

    Signals in the researched records of the listed products:

    • Matched through a sourced tag or a documented capability rather than the primary category: Intelex, Cority, Enablon, Evotix, VelocityEHS, EcoOnline, Prometheus Group and Qavach.AI.
    • Offline use, as classified in the records: a documented offline workflow: Intelex, Cority, Enablon, Evotix and VelocityEHS; a partial offline workflow: EcoOnline and Qavach.AI. No classification yet for 1 of the 8.
    • A published price amount is on record for Intelex; the other 7 need a quote.

    Vendor-material signals, not test results; the commercial partner is not counted; no signal means not established.

    A demo script for this combination

    Ask each vendor to run these steps with synthetic data. They are demo requests, not observed vendor results.

    1. Configure two sites with different approval chains for the same hot work permit type, and show a deputy approving while the usual issuer is marked absent.
    2. Issue a synthetic confined space permit with named entrants, an attendant, recorded test results and a rescue arrangement, then show the system refusing to issue it while a required field is empty.
    3. Hand the open permit to a night-shift supervisor and show both signatures and the time of the handover in the record.
    4. Create an overlapping job in the same area and show what warning, if any, the system raises, and who must respond.
    5. Cancel the permit, then export the full record, including amendments and the audit trail, as a corporate auditor with read-only access.

    9 platforms for enterprise permit to work

    Tekmon pays for a sponsored placement (above); its place in this list follows the same rule as every entry. How lists are ordered

    Intelex

    EHS Management

    What the evidence covers hereVendor's own material, not a test · 2 sources, checked 3 Oct 2026

    Intelex documents a dedicated Permit to Work application covering request, review and authorisation of hazardous work, kept separate from its Permit Management application, which tracks regulatory permit renewals and thresholds. Specify which one you need, since the quote lists applications individually. Its REST API keeps each caller's platform permissions; entitlement and access design need confirming. Offline permit authorisation is not established. Vendor source, source 2, profile checked 3 October 2026.

    Tekmon

    EHS Management

    What the evidence covers hereVendor's own material, not a test · 1 source, checked 28 Sep 2026

    Tekmon documents permit requests and approval routing (the full description is on its profile). Vendor source, profile checked 28 September 2026.

    Cority

    EHS Management

    What the evidence covers hereVendor's own material, not a test · 2 sources, checked 3 Oct 2026

    Cority documents electronic permit-to-work requests, configurable approvals and monitoring of active permits that conflict with each other, as a high-hazard work control separate from its environmental permit obligations. For a multi-site group, ask whether approval chains can differ by site and permit type, and run an overlapping-job test. Its offline capture is documented for incidents, inspections and observations, so offline permit authorisation should not be assumed. Confirm the permit module is in the purchased package. Vendor source, source 2, profile checked 3 October 2026.

    Enablon

    QHSE Management

    What the evidence covers hereVendor's own material, not a test · 2 sources, checked 3 Oct 2026

    Enablon documents Control of Work applications for Permit to Work, Isolation Management and Operational Risk Assessment, plus a Simultaneous Operations application that raises risk warnings across overlapping jobs. Each application is scoped and licensed separately, and warnings are not the same as automatic conflict resolution. Offline authorisation is not established; its offline Go app covers incidents, observations and inspections. For links to other systems it describes the Enablon Hub and a development kit, which is integration tooling rather than a finished connector. Vendor source, source 2, profile checked 3 October 2026.

    Evotix

    EHS Management

    What the evidence covers hereVendor's own material, not a test · 3 sources, checked 3 Oct 2026

    Evotix documents Permit to Work, Management of Change and Lockout & Tagout as modules of its Enterprise edition (Evotix 360), which the Professional edition page does not list. Ask which edition a quote covers. The permit page describes records, approvals and linked controls; the lockout page covers procedures and field execution. Its offline mobile scope names incident and hazard reporting and safety guidance, so offline permit approval needs its own acceptance test. Vendor source, source 2, source 3, profile checked 3 October 2026.

    VelocityEHS

    EHS Management

    What the evidence covers hereVendor's own material, not a test · 1 source, checked 3 Oct 2026

    VelocityEHS documents an electronic permit-to-work product that covers permit creation, approval and tracking together with contractor qualification checks, within a separately scoped contractor safety suite. Its environmental permit library is a different capability and should not be counted. Offline use is documented for incident, near-miss and hazard capture and for downloaded checklists, so permit approvals while disconnected should be tested separately. Confirm the contracted product and configuration. Vendor source, profile checked 3 October 2026.

    EcoOnline

    EHS Management

    What the evidence covers hereVendor's own material, not a test · 2 sources, checked 3 Oct 2026

    EcoOnline documents a Permit to Work module within Control of Work, with general and specialist permit templates, sign-off by several stakeholders, attached risk assessments and method statements, handback or cancellation, and extended permits linked to the original. Its guide names hot work among the permit types it covers; check the fire-watch and re-verification fields in a demonstration. The brochure describes disconnected work as starting online and continuing after connectivity drops, and the regional product must be confirmed. Vendor source, source 2, profile checked 3 October 2026.

    Prometheus Group

    EHS Management

    What the evidence covers hereVendor's own material, not a test · 3 sources, checked 11 Oct 2026

    Prometheus Group documents ePAS electronic permit workflows with configurable approvals and templates, hazard and control visibility, specialised hot work and confined space permit configuration, isolation and lockout/tagout management with tag printing, and permit audits across departments and sites. It is described as integrated with enterprise asset management systems, which is the link an enterprise usually needs between permit and work order. Its offline mobile documentation covers work orders and operator rounds; disconnected permit approval and release are not established. Vendor source, source 2, source 3, profile checked 11 October 2026.

    Qavach.AI

    EHS Management

    What the evidence covers hereVendor's own material, not a test · 2 sources, checked 11 Oct 2026

    Qavach.AI documents permit workflows as part of its optional safety modules, with review, approval and closeout configuration, so the permit capability depends on the modules licensed. Its evidence is terminal-focused and centres on observations, incidents and actions, not on multi-site delegated authority or isolation records. Offline use is documented for observations and incidents only, and API integration is described as subject to feasibility and time-and-material fees. Vendor source, source 2, profile checked 11 October 2026.

    Compare enterprise quotes on the same scope

    For permit to work, request an itemised proposal using these five lines. A public entry price does not establish the cost of your enterprise deployment.

    Scope and commercial evidence to request from every enterprise candidate
    Cost areaScope to sendAnswer to obtain
    SubscriptionName the applications, editions, entities, sites and roles, including external users.Annual charge, minimum commitment, growth bands and renewal terms.
    Configuration and migrationList workflows, historical records, attachments, environments and acceptance checks.Fixed deliverables, exclusions, internal responsibilities and change-request rates.
    IntegrationsName each system, data direction, frequency and owner of failed transfers.Connector licences, implementation, monitoring and recurring maintenance.
    Support and trainingSpecify languages, time zones, escalation, administrator training and rollout waves.Included service level, extra support fees and training charges.
    Exit and continuityRequest a sample export of records, attachments and change history.Export assistance fees, access period and retention or deletion commitments.

    Mark missing costs as unknown and keep internal effort separate from vendor fees. Use the same contract period and growth assumptions for every proposal.

    See a worked three-year quote comparison →

    How this shortlist is assembled

    Products match the catalog's category and company-size tags and are ordered by how closely our sources document each product for the category: primary category first, then a sourced tag or documented capability, then how complete the researched profile is and whether it documents a price, a free trial and offline use, then name. Stars appear only where we hold review data for the product and never affect the order. Position in the list is not an assessment of fit or quality.

    A catalog tag does not establish a verified deployment or suitability for your workflow. Product profiles identify available vendor sources and review dates. This page does not report customer interviews or hands-on comparative testing. A labelled sponsored placement is additional to the list. The commercial partner also appears organically when it meets the same inclusion rule, with the same ordering and styling as every entry; see how lists are ordered.

    Each card's evidence row comes from the sources recorded in the product's profile. "Documents" means the vendor's own material describes the capability; it is not a test result or an assessment of fit.

    Read the editorial methodology, compare quote scope, or use the demo scorecard to record your own evidence.

    Other software categories for Enterprise

    Frequently Asked Questions

    How should Enterprise buyers choose permit to work software?
    Use two business units with different approval chains, central reporting and an identity-system change. Check delegated administration, segregation of sensitive records, integration ownership, staged releases and full exports at contract exit. Use these tasks to assess the candidates below; catalog order does not establish the best fit for your organisation.
    What is included in the price?
    Request the same scope from each vendor: applications, users and external participants, sites, implementation, migration, integrations, training and support. Record recurring charges, minimum commitments and renewal terms. Use the linked product profiles for sourced pricing conditions and the worked quote example to compare totals.
    What determines the implementation schedule?
    Identify who prepares the data, configures workflows, approves access and tests integrations. Ask for milestones and acceptance criteria tied to those dependencies. Company size alone does not establish a delivery date; agree any pilot's access, duration and cost separately.
    How are the platforms selected and ordered?
    The list matches the catalog's category and company-size tags and is ordered by how closely our sources document each product for the category, then by name; ratings, reviews and payments play no part. It is a discovery list, not a ranking or a scored comparative trial. Open each profile to inspect its sources and research coverage.
    What evidence should security and IT reviewers request?
    Have the responsible reviewers specify access controls, identity integration, hosting, retention, export and assurance requirements for the intended records. Ask for current documentation with scope and exceptions, and test your required roles. A catalog tag or certification logo does not prove the proposed configuration is suitable.