Skip to main content
    QHSEtech
    Updated 21 September 2026
    Work authorization buying guide

    Confined space management software: check what the permit is connected to

    A permit displays an attached gas-test record, an isolation reference and two authorized names. Can the reviewer establish that the test belongs to this space, the isolation version is current and the entry record still accounts for both people? Use those connections to evaluate software, rather than treating a completed form as evidence that entry is safe.

    Jump to the 5 products

    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

    Sources checked 21 September 2026. These are documented application scopes and proposed demos, not hands-on product testing or an entry/rescue procedure. Existing profiles retain their separately dated commercial evidence. Evaluation methodology.

    TekmonAd

    Explore its published safety, quality and maintenance workflows. Confirm modules and pricing in a scoped proposal.

    Separate four records before comparing systems

    RecordQuestion it supportsWhat it does not establish alone
    Work authorizationWhich space, task, conditions, people and document versions were reviewed?A digital signature does not establish that current physical conditions match the authorized basis.
    Atmospheric test or monitoring dataWhat was observed, where, when, by whom and with which configured instrument?A value without context or a last-known display does not establish present conditions throughout a space.
    Entry and exit recordWho is recorded as inside, and how was each transition confirmed?A location dot, silent device or authorization list alone does not establish entry or exit.
    Response arrangements and event historyWho receives information, owns the next action and records the outcome?An uploaded plan or notification acknowledgement does not establish practical response capability.

    Documented confined-space scopes to investigate

    Connected gas monitoring and permit or control-of-work applications are different purchases: one supplies readings and alerts, the other organizes work authorization. Identify which part of the workflow you need and how the records will meet.

    Cards here are admitted by permit applications that configure confined-space entry, by gas-testing rules inside a permit, or by connected gas detection. The capability printed on each card says which of these it is, and none of them by itself shows an entry roster or a rescue arrangement.

    The cards open the broader profiles and their existing price/connectivity evidence. It does not establish an equivalent confined-space package, native integration between these products or inclusion of monitoring services.

    Ordered by how closely our sources document this process, not by quality. Sponsored placements are labelled. How lists are ordered

    Same rule for every product: tagged “Permit to Work”, “Permits to Work (PTW)”, “Control of Work” or “Industrial Safety” or assigned primary category “EHS Management” or “Lone Worker Safety”, with a sourced confined-space entry or gas monitoring capability in its record, or one the vendor stated to us, labelled as vendor-stated. 5 qualify.

    Demo case: the attachment exists, but it belongs to another space

    Run this as a tabletop software demonstration using fictional records, with no actual confined-space entry. Draft permit PTW-017 concerns SPACE-017 and JOB-017. The attached TEST-017 report identifies SPACE-018. Ask the reviewer to return the request with the mismatch recorded. Keep the original attachment and correction history; an uploaded file is not enough to satisfy the evidence requirement.

    Next, supply correctly matched evidence and demonstrate the configured authorization process. The reviewed permit version references isolation plan ISO-017 revision 1. Introduce revision 2 and show which permits still rely on revision 1, who must assess the effect and how the resulting decision is recorded. Do not overwrite the earlier authorization basis or treat a synchronized new file as automatic reauthorization.

    At simulated handback, E-017 has a confirmed exit while E-018 has no confirmed exit record. A related device has stopped communicating. Keep E-018 unresolved under the site's accountability procedure; device silence does not establish an exit. Demonstrate how verified information later resolves the record without inventing an exit time or silently clearing the roster.

    Review the identity and version of each linked record

    Synthetic recordDeliberate challengeEvidence to retain
    PTW-017 / SPACE-017 / JOB-017A draft has every attachment field completedThe request, task, space, reviewer decision and reason for return.
    TEST-017 / SPACE-018Attached test belongs to a different spaceOriginal report, incorrect link, correction and review of the replacement evidence.
    ISO-017 revision 1 → revision 2Previously reviewed permit still references revision 1Historical basis, affected records and the authorized decision about the change.
    E-017 / confirmed exitA recorded transition has supporting confirmationIdentity, event time, recorder and confirmation method.
    E-018 / exit unconfirmedRelated device stops communicatingUnresolved entry status, last-known data and assigned follow-up; no inferred exit.
    JOB-017 / maintenance completionThe work order is marked completeSeparate permit handback, entry-accountability review and any outstanding actions.

    A displayed reading needs a timestamp and a purpose

    Blackline's sensor-readings documentation describes updates at communication intervals and sensor events. Its confined-space page distinguishes pre-entry and work-stage readings. Preserve these meanings rather than presenting every received value as continuously current.

    For the demo, retain the device/sensor configuration, space and location, observation time, server receipt time, units, sampling context and relevant instrument checks. Separate an attached test report, a manually entered result and a connected instrument feed. Ask how missing context, stale data and corrections are exposed to the responsible user.

    Then disconnect the proposed connection in a controlled test. Establish what the instrument, local user and remote team each know. Data returning later should not erase the gap or create retrospective evidence that someone received an alert at the time. The demonstration does not assign an acceptable sampling interval or gas concentration.

    Name the people behind authorization and response

    Blackline's monitoring-service description refers to a response protocol supplied by the customer. Confirm whether that service is in the proposal and who performs each subsequent action. Remote notification is a different scope from a site's rescue arrangements.

    Demonstrate the permissions and record ownership for requesters, testers, reviewers, attendants or other locally defined roles, contractors and response contacts. At a shift change, preserve the original authorization and the handover to the current responsible people. A training record or account role alone should not be presented as proof of authorization for this specific work.

    For Great Britain, HSE's legislation overview separates avoiding entry, a safe system of work where entry is unavoidable, and emergency arrangements before work. Its introduction emphasizes assessment of the particular space and task. Use the applicable jurisdiction and competent site assessment to define the software brief; a product purchase does not establish compliance or rescue capability.

    Six demonstrations before accepting the proposed workflow

    1

    Reject the wrong-space attachment

    Attach TEST-017 for SPACE-018 to the SPACE-017 request. Demonstrate the check, reviewer return, corrected evidence and preserved history.

    2

    Review a changed authorization basis

    Introduce ISO-017 revision 2. Identify affected permits, required review and the resulting authorization state without rewriting the earlier decision.

    3

    Distinguish current and last-known readings

    Compare manual results, reports and a connected feed. Interrupt the connection and retain observation time, receipt time, context and visible gaps.

    4

    Reconcile entry status without guessing

    Keep E-018's exit unconfirmed when a device goes quiet. Record how the responsible person verifies and resolves the status, including any uncertain timing.

    5

    Hand over roles and response ownership

    Change the responsible shift roles and simulate an alert routing failure. Show current contacts, acknowledgement and follow-up separately from proof of response capability.

    6

    Close and export separate records

    Complete JOB-017 while permit handback or accountability review remains unresolved. Export versions, tests, entry history, decisions and open actions with the appropriate permissions.

    Specify the integration and operating scope in the quote

    Name the permit/control-of-work application, monitoring portal, device models/sensors and any third-party entry or remote-monitoring system.
    Document identifiers, data direction, mapping ownership, timestamps and failure handling for every proposed connection.
    Confirm the workflow supported by each mobile app: capture, review, authorization, suspension, current-status display and later reconciliation.
    Separate hardware, connectivity, monitoring hours, response service, contractor access, configuration, validation responsibilities and support costs.
    Demonstrate retention, export and post-contract access for the complete record, including attachments, superseded versions and unresolved events.

    Choose the purchasing scope first

    Use Control of Work to explore linked permits, isolations and job coordination. Keep connected gas monitoring and entry-accountability requirements explicit in the proposed workflow.

    Browse Control of Work applications

    Sources and limits of this guide

    7 sources

    Vendor sources establish documented scope, not tested configuration or universal integration. HSE sources supply Great Britain context. The demo records are fictional; no entry classification, gas limit, test frequency, rescue technique or authorization to enter is supplied. Product profiles keep their separate research dates.

    Software categories to explore

    Use this Process to define the work, then explore these software types. Confirm the exact workflow and module with each vendor.

    See all software categories

    Related Guides

    Permit-to-work applicationsIsolation and lockout recordsPPE issue, inspection and replacementShift handoverEmergency response coordination

    More related guides

    Frequently Asked Questions

    Does a digital entry permit prove the space is safe?
    No. It records an authorization and its evidence. The responsible team must assess the actual space, task, conditions and applicable procedure. An attachment or signature alone does not establish current physical conditions.
    Are permit software and connected gas monitoring the same purchase?
    No. This guide separates authorization applications from connected readings and alert services. Require a named integration, matching identifiers, data ownership and tested failure handling before treating them as one workflow.
    Can a location dot or silent wearable establish who is inside?
    Not by itself. Define how the entry/exit record is confirmed. In the fictional exercise, a device loses communication while an exit remains unconfirmed; the system must retain the uncertainty until the responsible person resolves it.
    What happens when an isolation document changes?
    The demo should identify permits that still depend on the earlier version and record the required review and decision. Preserve the original authorization basis. A newly synchronized document should not silently rewrite or reauthorize the work.
    Does a monitoring service provide rescue capability?
    Do not infer that from alert delivery or acknowledgement. Confirm the purchased service, customer response protocol, site responsibilities and separate emergency arrangements for the actual work.
    Can confined-space approvals work offline?
    Check the exact application and state transition. Offline form capture, local instrument alarms, remote receipt and permit authorization are separate functions. A generic mobile claim does not establish the complete disconnected workflow.