Permit to Work and Site Compliance Software for Construction

Construction compliance is generated at the point of work and consumed somewhere else entirely. A permit is issued at seven in the morning at a site gate; the question about it arrives weeks later from a client, an insurer or an investigating officer.

The paperwork usually exists. What is missing is the ability to find it — which revision of the method statement was signed, who was inducted before they went on site, whether the excavator’s inspection was still in date on the day of the lift.

The distinction that makes the rest of it work

An obligation is a rule: this must happen, at this cadence, evidenced this way, owned by this function, applicable under these conditions. An occurrence is one instance of it: this obligation, this project, this period, this due date, this evidence, this state.

Keeping them in separate registers is not a technicality. A single project generates hundreds of daily checks, a dozen monthly filings and a handful of quarterly and half-yearly submissions in a year, so the occurrences outnumber the rules by orders of magnitude, and the occurrences are what the site actually manages. Products that conflate the two cannot update a rule without rewriting history, which is why a spreadsheet that starts as an obligation list becomes unusable the first time the requirement changes.

The second consequence is that applicability is computed rather than ticked. Many obligations apply only above a threshold — a headcount, a site area, a structure height, a particular process being present — so an organisation’s obligation list is a rule that produces a list evaluated against its current state. Hire past a threshold and a set of new duties begins to apply immediately, with deadlines that may already have started running.

What a permit to work actually has to record

A permit to work is a written authorisation that a specific high-risk activity may proceed, under stated conditions, for a stated period. The usual families are hot work, work at height, confined space, excavation, electrical isolation and lifting, and each carries its own precondition list — a gas test before confined space entry, harness anchor points identified before work at height, isolation locked and tagged before electrical work.

What makes it auditable is that it is a state machine and not a form. Requested, approved, active, suspended, closed — with a named person at each transition, the conditions attached at approval, and the closure recorded rather than assumed. An open permit at the end of a shift is a live finding, and a permit register that cannot answer what is open right now is a filing cabinet.

The approval step is also where authority has to be real. The person who can approve a permit is not the person who requested it, and that distinction needs to be enforced by the system rather than by convention, because the pressure to self-approve is highest exactly when the work is most urgent.

Method statements, competency and induction

A risk assessment and method statement — RAMS, in British practice — describes how a specific activity will be carried out and what controls apply. It only works when the operatives doing the work have signed the revision that is current.

Versioning is the whole mechanism. A revision is issued, previous sign-offs against the superseded version stop counting, and the people working that activity are prompted to review what now applies. Without that, the sign-off sheet slowly stops describing the document on site, and the discrepancy is discovered by an investigation rather than by a manager.

Around it sits the competency layer, which is a set of dated facts about people:

• Site induction, completed on joining and repeated when the site or the phase changes
• Trade competency for the restricted activities — work at height, crane and hoist operation, structural erection, pile driving, work in compressed air
• Competency cards and licences held per operative, each with an issuer and an expiry
• Toolbox talks, which are daily or weekly evidence that the briefing actually happened
• Contractor-level evidence: the firm’s own licence, its insurance, and the induction of its people

Each of those is a credential with a date, and the operational question is always the same one: is this person, today, cleared for the thing they are about to do.

Plant, lifting gear and the inspection that takes a machine off site

Lifting appliances and lifting gear require periodic thorough examination by a competent person, and the certificate is what makes the crane usable. So do hoists, and by extension the fire extinguishers, the electrical protection and the calibrated instruments that a site depends on.

The pattern is identical to the credential one: an asset, a certificate kind, an issuer, a validity period, and a reminder window long enough to actually book the examination. Thirty days is a workable lead time for an annual thorough examination; a licence renewal that requires an authority to act needs sixty or ninety. The window is a property of the obligation, not a global setting, because the consequence of missing each one is different.

The failing state matters too. A certificate that has lapsed should mark the asset unserviceable rather than merely appear on a list, because the list is read by the office and the asset is used by the site.

Why the register goes stale, and what to do about it

Registers are compiled once, from the statutes and approval regimes in force at the time, and then the law moves. In India the older construction-specific statutes have been consolidated into the labour codes, which is exactly the kind of change that leaves a hand-maintained register citing instruments that no longer exist — and nobody discovers it until an inspection.

The structural answer is to record, against every obligation, the instrument and clause it comes from. Then a legislative change is a query rather than a re-read of the whole register, and an entry a site manager challenges can be traced to its source instead of defended by seniority.

Due dates need the same treatment. A deadline is an anchor event, an offset, a direction and a unit — and all four vary. Some notices run in hours from an incident, some in days from a change of particulars, and a commencement notice runs backwards from an event, so being late is discovered by the event happening rather than by a date passing. Model it as a date column somebody types and every one of those rules lives in a head.

What evidence has to carry to be worth anything

A photograph of a checklist proves that a checklist was photographed. Evidence that survives a challenge carries the capture time from the device rather than the upload time, the location and its accuracy, whether the device was offline at the moment of capture, and which version of the form was being answered.

Three facts also have to stay separate: the claim that the thing was done, the artefact that supports it, and the verification by somebody with authority who looked and agreed. Collapsing them into an upload is how a system ends up reporting compliance because a file exists.

Then the corrective action loop has to be one loop, whatever raised it. A failed inspection row raises a finding automatically, carrying the question that failed, its severity and the evidence attached; the finding is assigned, actioned with proof, verified by someone other than the person who actioned it, and closed. Each transition is an appended event rather than an edit, so a closed finding still shows what happened, and history cannot be tidied.

When this is not the right fit

If you run one site with a dozen people and a site manager who knows everyone, a permit book and a folder is workable and will stay workable. The threshold is usually subcontractors: the moment the people on site are employed by firms you do not control, competency and induction stop being things you can hold in mind.

This is also not a project controls system. It does not plan the works, manage the programme, value the interim application or run procurement, and a firm whose actual bottleneck is programme slippage should buy for that instead.

And no software makes a register correct. It can hold obligations, compute occurrences, chase owners and keep the evidence, but somebody with domain knowledge has to decide what the obligations are and review them when the law moves. A vendor claiming otherwise is selling a content subscription and should be asked when it was last updated and against what.