You can automate the assembly of a permit pack and the tracking of what expires when. A system can also draft the chaser for whatever is missing, for you to check and send. You cannot automate the authorisation, and you should not want to. A permit exists to make a competent person stop and check, and a document that gets issued without anyone stopping is worse than no permit at all.
What can you automate in a permit pack, and what has to stay with a person?
Split the pack into two piles. One pile is paperwork that describes a decision. The other pile is the decision. Everything in the first pile can be assembled, checked for expiry and filed by a system, with the chasers drafted for a person to send. Everything in the second pile stays with the person whose name goes on it.
That line does not move as the system gets better. It is drawn by what the permit is for.
What is actually in the pack
On a live job, the paperwork around one permitted task usually runs to the permit itself with its start and end times, the risk assessment and method statement for that task, isolation or lock-off records, certificates for the plant and the operatives, and whatever gas test or fire watch record applies. Then the client or principal contractor adds their own requirements on top, and those are rarely the same twice.
Where the requirements come from varies. Hot works are the clearest case: the Joint Code of Practice on fire prevention on construction sites, now in its 10th edition, sets out the fire precautions for hot work, applies to contracts over 2.5 million pounds with further requirements above 20 million, and was amended in January 2023. It is not a regulation, but your insurance can make it a condition of cover. Confined space entry brings its own requirements under the Confined Spaces Regulations 1997. HSE’s guidance on permit-to-work systems sets out the principle behind all of it: the permit is the record of a formal check, with a clear issue, receipt, clearance and cancellation, not a form that travels with the job.
Whatever applies to the task has to be present and in date before anyone starts.
What a system takes off you
A permit build works like Lead qualification. Each pack is checked against your rules, and whatever is missing is named before it goes any further. Nothing reaches a worker until everything needed is there.
A build here pulls the task details out of the job record once, so nobody types the site address into every document. It drafts the permit on the form the job needs, yours or your client’s, for the person who authorises it to check and sign. It gathers the documents that belong to that task, and it names the ones that are missing rather than quietly leaving a gap. It checks certificate expiry dates before the pack goes out instead of after. It drafts the chaser for each missing piece, in your wording, for you to check and send. And it keeps the register, so you can produce any past permit it holds without opening a filing cabinet.
The time spent filling in permits is not the only cost. The other is the job that starts late because a ticket expired on Friday and nobody looked. The expiry check is there to catch that one.
What stays with a person, permanently
Three things.
The authorisation. A competent person decides the work is safe to start, and signs. A system never issues a permit on its own, whatever it has checked.
The isolation. Somebody physically verifies the state of the plant. A record that an isolation happened is not the same as an isolation, and a system only ever sees the record.
The variation. Conditions on site change. When they do, the person standing there makes the call, and the paperwork catches up afterwards.
Nothing is fully automated where a mistake costs money or safety. On permits that rule does more than protect the worker. It protects the permit, because a permit that everyone knows is issued automatically stops being a check and becomes a formality, and formalities do not stop accidents.
What will go wrong
Your clients do not all use the same permit form, and at least one of them will not accept yours. That is normal, and it is a reason to build the system around your clients’ forms rather than a standard one.
The permit register in the site office and the folder on the server will disagree about which permits are open. Finding out by how much may be the first uncomfortable thing a build like this tells you.
Somebody will keep a paper copy because they do not trust the system yet. That is reasonable, and it is why the new system runs alongside the old way until the team trusts it, not before.
And the first version will miss an edge case that your supervisor handles by instinct and has never written down. That is not a failure of the build. It is the point of the parallel run.
Worth building, or not
Permits score well on the tests in how to pick the one document to automate first, because there is a great deal of repetition in them and very little judgement in the assembly. They are a candidate if you issue them more than once a month. Less often than that, the chasing is not costing you enough to fix.
Count how many you issue a week, and how many jobs in the last quarter started late because something in the pack was missing or out of date. Bring both numbers to the free 10-minute call. If they are small, I will tell you it is not worth building. If permits fit, you leave with a rough estimate: a range for the first route.