Digital Work Permits: From Paper to a Working System

Why a paper permit is no longer enough

A paper permit fails not at the moment of issue, but between the stages. The sheet travels from the issuer to the people who coordinate, then to the person who authorises, to the work area and back to the office. Only whoever holds it at that moment knows its current status. Everyone else at the site, including security and the dispatcher, usually sees only what someone managed to copy into the register.

An analysis of 106 permits from a continuous-operation plant, collected over 9 weeks, shows the scale of the problem even in a mid-sized company: 20 contractor firms, 43 hot work permits and 40 permits for work at height. In 44 of the 106 permits the location pointed to a building or a general line instead of a specific machine. With data of this quality it is hard to answer a simple auditor's question: who worked where, and on what basis, on a given day.

The second problem is enforcing the sequence. Paper accepts signatures in any order, even before a measurement or a safeguard has been completed. A system can refuse to move to the next phase until the blocking action has been confirmed. This is the main value of digitisation: the rules come from the configured procedure, not from the memory of the participants.

Stage 1: inventory of forms and procedures

The first stage does not require any software. Collect every form currently used to authorise work: general permits, work orders, safeguarding cards, contractor staff lists and statements confirming that hazards have been explained. For each one, record who issues it, who signs it, how many copies circulate and where it is archived.

The goal is a list of the work types that actually occur, not the ones listed in the instruction. In practice the same form is often used for hot work, work at height and confined space entry, although each requires different safeguards. Split them into types and subtypes, because the configuration of tasks, risks and required qualifications depends on it.

• A list of all forms that authorise work, with the owner of each one.
• A list of the especially hazardous work types present at the site, with subtypes.
• A list of the competences required for each work type (for example work at height certification or electrical qualifications).
• Archiving locations and document retention periods.

Stage 2: workflow and permit phases

An electronic permit passes through three phases: preparation, main work and closure. Each phase is a list of tasks assigned to roles. In the preparation phase the issuer describes the task, the location and the time window, and the system checks the dates and the qualifications of the assigned workers when the permit is created and opened. In the main work phase the contractor carries out the tasks, and in the closure phase the dismantling of the work zone and the restoration of the site are confirmed.

Draw the workflow on a board before you configure anything in the system. For each transition between phases, state who approves it and which conditions must be met. Approving or rejecting especially hazardous work should belong to a user on the site's side, not the contractor's. This is one of the rules the system enforces in code.

The one-to-one mapping rule

Do not change the safe work organisation instruction just because the medium changes. Map the current forms and the order of signatures, and introduce improvements in a second step, after the pilot. This way the health and safety and operations teams do not need to re-approve the procedure, and the risk of resistance from the workforce falls.

Stage 3: roles and responsibilities

A digital workflow forces a clarity that paper never required. Every task has an assigned role: issuer, coordinator, authoriser, team leader, fire watch for hot work, and the person who takes back the work area. A role is tied to an account, to permissions and, where needed, to qualifications. The system does not replace the works manager or the authorising person; it only makes sure their decisions are recorded in the agreed order.

At sites with many contractors, prepare a matrix: who may issue each work type, who may coordinate it and who may authorise it. For hot work, it is also worth recording the observation duty after the work ends: the system enforces a two-stage observation period (1 h and 4 h), and closure is blocked until at least three hours of monitoring have passed.

• A role matrix: who issues, coordinates, authorises and closes each work type.
• Deputies for holidays and shift changes, so the workflow does not stall.
• A clear split between roles on the site's side and on the contractor's side.

Stage 4: register and audit evidence

A permit register is not an archive of scans but a database in which every action has an author and a timestamp. When the permit is an electronic document, the PDF printout is generated from the data, not the other way round. The site has a live view of who is working where, and after an incident it can reconstruct the course of events from issue to closure.

At this stage, decide which reports you will need: a list of permits open today, permits of a given company in a given period, hot work in a selected area. The analysis of 106 permits showed that 82% were issued between 6:00 and 10:00, and 62 fell on Tuesday and Wednesday. Patterns like this let you schedule approvers and security staff where the load is greatest.

A digital register supports meeting the requirement to document work authorisations and provides evidence for internal, external and insurance audits. It does not, however, replace the responsibility of the people who make the decisions.

Stage 5: the pilot

A pilot is run in one area or for one work type, in parallel with paper for an agreed period. A good scope is one department and the two or three contractor firms with the largest share of permits. In the analysed plant, the four largest firms generated 63% of permits, so including them in the pilot gives the fastest feedback.

Measure three indicators: the time from issue to authorisation, the share of permits with a general location, and the number of permits closed after the deadline. After the pilot period, switch off paper for the covered area and extend the scope. Set the exit criterion for parallel running in advance, because without it two workflows can coexist for years.

Illustrative cycle time calculation

The calculation below illustrates an order of magnitude and is not the result of a measurement at a specific site. It assumes 400 permits a month and three time-consuming areas: issue and coordination, on-site authorisation, and closure with re-entry into the register. On paper this totals 60 minutes of site staff time per permit, in a digital workflow 26 minutes. A difference of 34 minutes at a rate of PLN 95 per hour gives about PLN 21,500 a month, or about PLN 258,000 a year. The value depends on the number of permits and on how the workflow looks today, so each site should calculate it on its own data.