The 40 Minutes Before the Work Starts

It is 6:20 in the morning. A tradesperson is standing outside vessel 7B on a planned shutdown. The job is welding on a fixed pipe inside the tank. They know the work. They have done it before. But today someone has asked a reasonable question: which permits apply?

Hot work. Almost certainly. Confined space. Probably. Isolation permit attached. Maybe. A JSA referenced somewhere in the procedure. Almost definitely.

The permit framework is split across eight documents stored across three different intranet locations. The document names changed three times in the last five years. The system is thorough. It is also genuinely difficult to navigate with gloves on, under time pressure, at the start of a shift.

Finding the right permits, the right pages, the right sign-off chain: that is a 40 minute job. Before a single weld is struck.

Multiply that across every shift, every job, every site. You start to see the real cost.

And then there is the other scenario. The one nobody wants to talk about but everybody knows happens. Someone skips a step. Not because they are reckless. Because they are tired, they have done the job a hundred times, and the answer was buried in a document that last got updated during a different safety regime. That is the incident report nobody wants to write.

What Actually Fails Today

The permit-to-work framework on a regulated site is one of the most documented things in the industry. Confined space. Hot work. Working at heights. Energised electrical. Isolation. Chemical handling. Lifting and rigging. Excavation. Each category has its own procedure, its own form, its own approval chain.

The documentation is not the problem. The access is.

A worker on shift cannot reasonably hold eight frameworks in their head while also doing their job. They can’t efficiently cross-reference three intranet locations on a mobile device with limited connectivity while standing next to a vessel they need to enter. And they definitely can’t do that at speed, with confidence, in a way that creates a clear compliance record.

So what happens in practice? One of three things.

The experienced worker relies on memory and misses a step that changed in the last procedure update. The newer worker spends 40 minutes finding the answer and the shift runs behind. Or someone calls a supervisor, who also isn’t sure, who calls someone else, and by the time the answer comes back the crew has already made a decision and moved on.

None of those outcomes are what the permit system was designed to produce.

The regulator is not going to simplify the framework. The work is not going to get less complex. But what you can change is how a worker on shift, with gloves on, finds the right answer in the right second.

How the Genie Handles It

A Help Genie genie reads the permit framework and site procedures directly from your documentation. Upload the PDFs, the intranet exports, the procedure manuals. The genie builds its knowledge base from the actual documents your site uses.

Then the worker asks a real question. Not a menu selection. Not a search keyword. A question the way a human asks it.

“I’m welding on a fixed pipe inside vessel 7B during a planned shutdown. What permits do I need?”

The genie answers in seconds. It names the applicable permits. It references the relevant clauses by number. It lists the form IDs. It describes the sign-off chain: who approves what, in what order, before work can start.

The worker doesn’t have to know which document governs this exact scenario. They don’t have to know what the document was called before it was renamed. They just ask the question they have and get the answer they need.

Step One: The Worker Asks

The genie is accessible via phone, a QR code on the site noticeboard, or a web link. No app download required. No login. Just a question.

The worker describes the job in plain language. The genie listens and identifies the work type, location, and conditions from that description.

Step Two: The Genie Cross-References the Framework

The genie checks the knowledge base against the described scenario. It identifies which permit categories apply, flags any that are conditional on site conditions or job duration, and notes any co-dependencies. Confined space permits that require hot work permits to be in place first, for example, are handled in the right sequence.

It does not guess. It answers from the documents. If the documents have gaps or contradictions, the genie surfaces that rather than papering over it.

Step Three: The Answer Lands

Six seconds. The worker gets the permit list, the clause references, the form numbers, and the approval chain. If they need more detail on any step, they ask. The genie goes deeper.

The conversation is logged. The timestamp is recorded. Who asked, what they asked, what the genie answered. That record exists whether or not the supervisor was available, whether or not a phone call was made, whether or not anyone wrote anything down.

Step Four: The Record Is Kept

Compliance is what you can prove. The genie keeps the proof.

Every conversation is captured. Site managers and safety teams can see what was asked, when, and what answer was given. If the framework changes, the knowledge base is updated and the genie answers from the new version. Workers always get the current answer, not the one someone memorised two years ago.

What This Changes on the Ground

The time saving is real. A question that took 30-40 minutes to answer through document searching or phone chains can be answered in under a minute. Across a busy shutdown with dozens of permit queries per shift, that compounds fast.

But the bigger shift is behavioural. When the right answer is genuinely easy to get, workers get the right answer. The friction that leads to skipped steps or reliance on memory disappears. The system stops working against the people it is designed to protect.

Sites that reduce permit confusion also reduce the back-and-forth between workers and supervisors on questions that should have clear answers. Supervisors spend less time fielding calls they shouldn’t need to field. Workers spend less time waiting.

And the compliance record improves not because anyone is auditing harder, but because the right steps are actually being followed, and the genie is logging that they were.

For smaller operations where there isn’t a dedicated safety officer on every shift, the benefit is even more pronounced. A permit to work for small business situations often means one or two people carrying safety knowledge that should be embedded in a system, not in a person. A genie puts that knowledge somewhere accessible to everyone, at any hour.

Industry estimates suggest permit-related delays and errors contribute to somewhere between 20-35% of non-conformance incidents on regulated worksites. Most of those aren’t about workers not caring about safety. They’re about workers not being able to access the right information fast enough. That’s a solvable problem.

What the Genie Doesn’t Do

The genie doesn’t sign the permits. It doesn’t replace the authorised person who has to approve the work. It doesn’t make the decision that the job is safe to proceed.

What it does is make sure that when the authorised person arrives, the worker already knows what they’re asking for, has the right forms, and can describe the sign-off chain correctly. That conversation is shorter, sharper, and less likely to miss something.

The framework stays. The rigour stays. What changes is the 40 minutes of friction in the middle.

A Note on the Framework Itself

The permit to work system exists because confined space entry kills people. Hot work without the right controls starts fires. Working at heights without isolation procedures ends careers. The documentation is not bureaucracy for its own sake. It is a body of knowledge built from incidents that actually happened.

The problem was never the framework. It was always the gap between what the framework requires and what a worker on shift can practically access and apply.

That gap is where a voice AI genie belongs.

---

If your site is running permit frameworks across multiple work types and the access problem sounds familiar, the right starting point is a site-specific genie built from your actual documents.

Visit /explore to see how a genie is set up, or check the /trades page to see how voice AI is being used across trades and field operations.

Stop letting document navigation decide whether work happens safely.