Permit-to-Work Software for High-Risk Construction

Permit-to-work software for high-risk construction activities is a digital system that defines which hazardous work requires authorisation, routes each permit through the right reviews, records the controls and isolations required, and maintains a live, auditable record of who approved what, where and when. It is used for activities such as hot work, confined-space entry, lifting, excavation, work at height, electrical isolation and work near live services. It does not replace a risk assessment or method statement; under the UK HSE’s HSG250 guidance, a permit-to-work system is an additional control layer within a formal safe system of work.

What Permit-To-Work Software For High-Risk Construction Activities Means in Practice

A permit-to-work system controls the authorisation and execution of a defined task during a defined period and in a defined location. A sound permit states the work scope, hazards, precautions, isolations, responsible people, validity period, handover requirements and closure conditions. Software applies that process through structured forms, role-based approvals, mandatory fields, notifications and an audit trail.

The distinction matters. A permit is not a shortened risk assessment, a generic checklist or permission to start work without field verification. HSE HSG250 describes PTW as a formal recorded process for work considered high-risk and makes clear that it should not be treated as a substitute for risk assessment. The permit should reference the relevant risk assessment, JSA/JHA, method statement, drawings and isolation information.

On a construction project, the scope may include welding and grinding, entry into a confined space, crane lifting, critical work at height, energisation or de-energisation, excavation near existing services, tie-ins and work inside an operational facility. The exact threshold should be set by the project’s risk profile, applicable regulation and the owner’s HSE standards.

For an owner or PMC, the important question is not simply whether a contractor has completed a form. It is whether every relevant high-risk activity is visible, correctly authorised, coordinated with simultaneous operations, and closed with evidence that the controls were removed or left in a known safe state.

Why This Matters for HSE Directors & Site Safety Managers

High-risk activities are disproportionately represented in serious construction incidents. In Great Britain, falls from height accounted for 40 of 135 work-related fatalities in 2022–2023, or 30%, according to HSE statistics published in July 2023. In US construction, falls, slips and trips represented 379 of 1,008 fatalities in 2021, or 37%, according to the Construction Chart Book, 7th edition, published in 2023.

Struck-by incidents account for about 15% of non-fatal construction injuries and 8–10% of fatalities in US construction, according to CPWR’s June 2022 data bulletin. OSHA identifies falls, struck-by, electrocution and caught-in/between incidents as the construction Fatal Four; together, these account for over 60% of US construction worker deaths each year, according to OSHA’s commonly used statistics.

These figures do not establish a universal return on investment for digital PTW. They do establish why work authorisation, isolation and supervision need more than an informal exchange between a foreman and an HSE representative.

HSE Directors also operate across contractor boundaries. UK CDM 2015 places duties on clients and principal contractors to plan, manage and monitor construction work, including coordination of high-risk activities. In the US, OSHA’s multi-employer citation policy considers whether a controlling employer could reasonably have been expected to prevent or detect and abate hazards created by others.

ISO 45001:2018 requires operational controls for OH&S risks, management of contractor activities and documented information as evidence of implementation. A controlled PTW process can support those requirements, but digital software is not itself a regulatory mandate. The value for an HSE leader is practical: one view of active permits, consistent approval rules, traceable decisions and evidence that contractors worked within the agreed control framework.

What should an owner see each morning? At minimum, the active permits by site and zone, the work type, validity period, responsible contractor, approving roles, associated isolations, unresolved conflicts and permits approaching expiry or closure. A portfolio view should also show repeated deviations, concentration of high-risk work and differences in contractor performance.

The Traditional/Manual Approach — and Where It Breaks Down

In a manual process, a contractor supervisor completes a paper form or PDF, an area owner or operations representative reviews it, HSE may check specific permit types, and the permit holder accepts the conditions. The active permit may then be logged on a spreadsheet or displayed on a whiteboard. At shift change, people rely on a handover conversation and the paperwork kept in a site office.

The Energy Institute’s 2021 guidance notes that PTW is often implemented with paper forms and manual control, with risks including illegibility, loss and unauthorised changes. HSE HSG250 identifies recurring weaknesses around responsibilities, coordination, monitoring and handover.

The failure is often not the paper itself. It is the absence of a reliable control around the paper. A permit can be signed without an adequate risk assessment, an isolation can be assumed rather than verified, or a permit can remain open after the work has changed. HSE incident investigations, including the BP Grangemouth major accident investigation, identify failure to follow PTW systems as a common immediate cause in process industries.

SIMOPS creates another weakness. Hot work near flammable storage, lifting over an occupied area, or excavation near live utilities cannot be assessed by reading each permit in isolation. The risk sits in the relationship between location, timing and activity. A spreadsheet may list all three permits without showing their conflict.

Why do permit-to-work systems fail at shift change? The incoming team may receive an incomplete handover, conditions may have changed, or the permit may not be revalidated. The result is a record that looks complete while the worksite no longer matches the authorisation.

Step-by-Step Framework

The following framework can be implemented before selecting software. It treats PTW as a governed operational process and as data about whether critical controls are present and functioning.

Step 1 — Assess current state

Start with the work, not the application. List the activities that require a permit or equivalent control: hot work, confined-space entry, lifting, work at height, electrical isolation, excavation, work near services and work in live facilities. Compare the list with the project risk register, applicable regulatory guidance and the owner’s standards.

Map the current sequence for each permit type. Who requests it? Who checks the risk assessment? Who verifies isolations? Who issues it? Who accepts it? Who can suspend, extend, revalidate or close it? Include weekend work, remote areas and small contractor packages, where bypasses often become visible.

Record a baseline, even if the first data set is manual. Track the average number of permits by type, request-to-issue time, issue-to-close time, permits returned for rework, PTW-related audit findings, near misses and work started without a valid permit. Note which contractors use different forms or approval chains.

Step 2 — Define standards, templates & governance

Write the PTW policy before digitising it. Define the work categories, the relationship between PTW and risk assessments or method statements, validity and extension rules, suspension triggers, shift handover requirements and closure evidence.

Each permit should capture a unique ID, work description, location or zone, date and time, hazards, controls, required isolations, verification checks, work team, permit holder, issuer, approver, validity period, handover and closure. Category-specific templates should add relevant checks. A confined-space permit may require entry and rescue information; an excavation permit may require service information; an electrical permit may require isolation and energisation status. The exact checks should follow the project’s approved procedure.

Create an authorisation matrix. A contractor supervisor may request a permit. A trained permit issuer may review and issue it. An area owner may authorise work affecting operations. HSE may review selected categories. The permit holder accepts the conditions and controls the work team. Isolation work and verification should be assigned to authorised roles rather than inferred from a signature.

Governance should also define who owns the templates, who audits permits, how contractor exceptions are handled and how changes are approved. The risk register should remain connected to PTW so recurring control failures can become formal mitigation actions rather than isolated observations. A centralised safety and HSE workflow can support that connection when the owner wants project teams and contractors working from a common environment.

Step 3 — Select & implement supporting technology

Evaluate technology against the approved process. Look for configurable permit types and approval routes, role-based access, competency checks, location or zone coding, mobile field use, offline capability where required, notifications, version history and a searchable audit trail.

SIMOPS should be assessed explicitly. The system should make it possible to compare active permits by time and location and to escalate combinations that require review. Mature PTW tools in process industries describe capabilities such as isolation management, plant visualisation, competency checks and real-time SIMOPS views. Construction teams should decide which of these controls are necessary for their site rather than assuming that a digital form provides them automatically.

Integration matters when the permit depends on other project information. Link the permit to the relevant method statement, drawing, risk assessment, schedule activity, inspection or isolation record. For owners, a CDE reduces the need to reconcile separate contractor registers. A risk register and mitigation workflow such as Zepth’s risk and mitigation capability can provide a place to record repeated PTW failures and assign follow-up actions.

Run a limited pilot. One site or two permit categories, such as hot work and confined space, is enough to test templates, approval times, field connectivity, contractor adoption and handover. Do not transfer every paper field into software without checking whether it supports a decision. The Energy Institute cautions that poor implementation can transfer bad habits into a digital system.

Step 4 — Roll out, train and monitor adoption

Training must cover the process and the interface. Permit issuers and approvers need detailed instruction on risk review, authorisation, suspension, revalidation and closure. Permit holders need to understand the conditions they accept. The wider workforce needs to know when a permit is required and how to challenge work that does not match the permit.

Contractor onboarding should be contractual and operational. Issue a PTW playbook with permit categories, role definitions, approval routes, validity rules and examples of acceptable control descriptions. Clarify who can stop work, revoke a permit or escalate an unresolved conflict.

Monitor adoption during the first weeks. Compare digital permits with paper permits, review time to issue, record system errors and inspect whether people are using the correct permit type. Toolbox talks and an HSE champion for each crew create a practical feedback loop. Early process friction should be resolved without weakening the control.

Step 5 — Measure impact against baseline KPIs

There is no universal global target for PTW performance. Set targets against the project’s risk profile, regulatory context and baseline. Track both whether the process is being used and whether it is producing useful control information.

• Coverage: the percentage of identified high-risk work conducted under an approved permit.
• Compliance: PTW-related non-conformances, near misses, breached conditions and work started without a valid permit.
• Quality: the percentage of permits passing audit without major findings, plus rejection and rework rates.
• Timeliness: request-to-issue and issue-to-close times by permit type, including extensions and overdue closures.
• Coordination: conflicting permits identified and resolved before work starts.
• Competency: coverage of current training for permit issuers, approvers and holders.
• Outcomes: trends in high-risk incidents and near misses, interpreted alongside other controls rather than attributed to PTW alone.

Review the data at project and portfolio level. Repeated returns because isolations are incomplete may indicate a planning or interface problem. A high volume of very short permits may warrant field assurance. Concentration of high-risk work in a zone may require schedule coordination or a design review. PTW becomes more useful when it informs the risk register, look-ahead planning and owner governance.

Common Mistakes to Avoid

Treating PTW as a form. Digitising a signature page without defining authority, verification, handover and closure creates electronic box-ticking. The process must specify the decision each field supports.

Launching with excessive complexity. Too many permit types, long checklists and overlapping approvals can encourage workarounds. Start with the risks and categories that matter most, then expand after the pilot.

Designing without contractors. Contractors know how work is planned, sequenced and supervised in the field. Excluding them can produce inaccurate descriptions and impractical approval routes. Involve representatives while testing templates.

Assuming a signature proves a control. A permit should identify who verified the isolation or field condition and when. HSE guidance treats competence and monitoring as essential parts of a PTW system.

Ignoring SIMOPS. A collection of individually complete permits can still create an unsafe combination. Use zones, time windows and coordination reviews to assess the work together.

Separating PTW from planning and risk. If the permit is disconnected from the look-ahead schedule, drawings and risk register, teams discover interfaces late. Link the records that the issuer needs to make a sound decision.

Measuring activity but not control. Counting permits does not show whether the controls were suitable or followed. Pair volume with audit findings, deviations, near misses, conflicts and closure quality.

How AI-Native Platforms Like Zepth Change This Workflow

An AI-native approach places permit data in the project’s common data environment rather than treating it as an isolated form. The owner defines the minimum standards and contractor workflows; project teams submit, review and close permits in one controlled space; HSE leaders see the portfolio pattern instead of reconciling separate spreadsheets.

AI should assist, not authorise consequential work independently. A practical system can review free-text descriptions for missing hazards or controls, normalise inconsistent terminology and surface relevant references. It can flag unusual patterns such as repeated extensions, unusually fast issue-and-close cycles or a concentration of permits in one zone. The responsible human still reviews and signs off the decision.

For an owner, the connection between PTW, project controls and risk is as important as the permit screen. Zepth is built around a common data environment, with Zepth Core for safety and HSE operations, project controls and site information, while Zepth AI operates across the platform as the intelligence layer. PTW records can be governed alongside contractor submissions, site records and the project risk process, so repeated control failures can be escalated rather than lost in an HSE folder.

The owner-side use case is straightforward: define the required permit standards, require contractors to report through the same environment, and give HSE leadership a consistent view of work authorisation across projects. Zepth does not charge per seat or per collaborator and does not price on construction volume, which supports broad participation across owner, PMC and contractor teams. Commercial terms for a specific deployment are available on request.

AI can highlight a weak or generic control, but it should not decide that work is safe. Zepth AI supports review and analysis; a designated issuer, area owner, HSE reviewer or permit holder remains responsible for the consequential approval. This preserves the accountability required by a credible PTW system.

For teams developing their operating model, the practical sequence is to baseline the current process, standardise roles and templates, pilot the workflow, train every affected role, and then compare the same KPIs over time. A platform is useful when it makes those controls easier to execute and easier for the owner to assure.

Book a walkthrough of the Zepth platform to discuss how an owner-controlled CDE can support contractor reporting, safety workflows and portfolio risk visibility. You can also subscribe to Zepth Insights and download the related permit-to-work framework and checklist for use in your next process review.

FAQ