If you recognise the following:

HV / LV

SAP / AP

SFT

LOA

CP

PTW

SSoW

RAMS

LOTO

…then you’re operating in real control-of-work environments.

And you already know something important.

Permits aren’t forms.

They’re safety systems.

This is where most ePermit systems fall apart

There are a growing number of platforms now offering “ePermits”.

Digital forms.

Mobile approvals.

Electronic signatures.

That works perfectly well for low-complexity permit workflows.

But serious control-of-work environments are different.

At this level, permits are not about administration.

They are about:

1. Energy isolation
2. Sequencing
3. Authorisation
4. Responsibility
5. Operational control

And that changes everything.

Real permit systems control work

In HV and complex operational environments:

1. Roles matter
2. Switching sequences matter
3. Boundaries matter
4. Dependencies matter
5. Authorisations matter

You are not simply issuing a permit.

You are controlling risk across multiple teams, assets, and energy sources.

That requires much more than a digital workflow.

This is the difference most vendors don’t understand

Many systems are designed to:

1. Raise permits
2. Route approvals
3. Capture signatures

That’s administration.

It’s not control-of-work.

Because once you move into:

1. High Voltage operations
2. Sanction for Test
3. Limitation of Access
4. Switching programmes
5. Isolation boundaries
6. Multiple authorised roles

…the system itself needs to actively enforce process.

Not rely on people remembering it.

Simplicity is not always safer

There’s a strong push right now to simplify safety systems.

Fewer steps.

Faster approvals.

Reduced friction.

That sounds good… until you’re dealing with HV operations.

Because complexity in these environments is not a flaw.

It exists because the risk exists.

If a system oversimplifies control-of-work, it doesn’t remove complexity.

It removes protection.

What a real ePermit system needs to do

A true ePermit platform should:

1. Support HV permit structures properly
2. Handle Sanction for Test and Limitation of Access workflows
3. Enforce role-based permissions and authorisations
4. Manage sequencing and dependencies
5. Provide live visibility of active permits and boundaries
6. Maintain full auditability and operational traceability

Not through workarounds.

As core functionality.

This is where experience matters

At dulann, we’ve now issued more than 100,000 ePermits across Europe.

Not in demos.

Not in test environments.

In live operational settings supporting critical infrastructure in:

1. Data centres
2. Pharma
3. Advanced manufacturing

The world-class M&E contractors we work with generate more than €2M in combined annual revenue.

That matters.

Because systems that work for simple permit requests often fall apart when exposed to real control-of-work complexity.

And there’s a huge difference between digitising permits and understanding permit operations.

How dulann approaches ePermitting

At dulann, ePermitting is designed as a control system, not a digital form builder.

That means:

1. Support for HV operations
2. Structured workflows for SFT and LOA
3. Role-driven authorisation structures
4. Real operational sequencing
5. Full visibility and traceability across the permit lifecycle

Because in these environments, permits are not paperwork.

They are part of the safety system itself.

The bottom line

Not all ePermit systems are permit systems.

Some improve administration.

Some digitise paperwork.

Very few genuinely support control-of-work at this level.

And if your system can’t handle HV, Sanction for Test, and Limitation of Access…

…it’s probably not a permit system.

Question for operations and safety leaders:

Does your ePermit platform actively control work… or simply record that a permit existed?

If this language is familiar to you, we should talk.

At dulann, we work with organisations operating in complex, high-risk environments where permits are far more than forms.