Skip to content
Code Colonies

Industries · Guide

Moving permit to work and HSE incident reporting off paper

Paper permits and incident forms slow work down and hide risk. A practical guide for oil and gas operators on digitising permit to work and HSE reporting without weakening control.

Code Colonies Technology Division · · 4 min read

Key takeaways

  • Digitise your existing permit process first, then improve it
  • Offline use, intrinsically safe devices and clear isolation records are non negotiable
  • Near miss reporting rises when reporting takes two minutes

Why paper permits are still everywhere

On many refineries, terminals, gas processing plants and drilling sites, a hot work permit is still a carbonless triplicate form. One copy goes to the control room, one stays at the job, one goes back to the issuer. It works, mostly. But nobody can see at a glance how many permits are open across the site, which ones overlap in the same area, or whether an isolation was removed before the permit was closed.

Incident reporting has the same problem. A near miss gets written in a site logbook, typed up later, and reaches the HSE manager days after it happened, if it reaches them at all.

Moving both off paper is less about apps and more about keeping the control you already have while making the risk visible.

What to do first

  • Map your current permit types, roles and sign offs exactly as they are today, including the local habits that never made it into the procedure.
  • Build the digital workflow to match, with offline mobile use at the job site and a live board in the control room.
  • Link permits to isolations and to each other, so conflicts show up before work starts.
  • Make incident and near miss reporting a two minute task from a phone, with photos and location.
  • Run paper and digital side by side on one unit before you switch the whole site.

Start with the process you already follow

Your permit system is shaped by your own procedures, by OISD-STD-105 on work permit systems if you operate in India's oil and gas sector, and by your company or joint venture partner's standards. Do not let software redesign it for you.

Write down, for each permit type, who requests, who issues, who accepts, who does the gas test, what isolations are needed and what closure looks like. Common types include:

  • Hot work, such as welding, grinding and cutting
  • Cold work
  • Confined space entry
  • Electrical isolation and energy isolation, often with lockout and tagout
  • Work at height
  • Excavation

You will find gaps between the written procedure and what happens on night shift. Decide which version is right before you put either into software.

What the digital system has to do

At the job site

  • Work offline. Plant areas often have poor signal. The app must let the issuer and the performer sign, record gas test readings and attach photos without a connection, then sync when back in range.
  • Run on suitable devices. In classified hazardous areas you need devices certified for the zone. Budget for them early; they cost several times a normal handset.
  • Show the permit clearly. A large, simple summary of the job, hazards, controls and validity time that the crew can read in sunlight.

In the control room

  • A live permit board. Every open permit on a plot plan or unit list, colour coded by type and status.
  • Conflict checks. Two hot work jobs in the same area, or a hot work permit near a line that another permit has just opened. Simultaneous operations need someone to look at them together, and the system should prompt that.
  • Isolation tracking. Each isolation point, who applied the lock, who verified it, and which permits depend on it. A permit should not close while its isolations are still in place, and an isolation should not be removed while a permit depends on it.

Afterwards

  • A full record of every signature, time and change, kept for as long as your retention policy says.
  • Reports on permit volumes, overdue closures and suspended permits by unit and contractor.

Incident and near miss reporting

People do not report near misses when reporting is slow, or when it feels like it will get someone into trouble.

  • Let anyone, including contract workers, report from a phone or a shared kiosk in a few taps: what happened, where, a photo, and whether anyone was hurt.
  • Allow reports in Hindi, Gujarati or the local language, and voice notes for people who prefer to speak.
  • Route each report by severity. A first aid case goes to the area supervisor. A lost time injury or a dangerous occurrence alerts the HSE head and site manager straight away.
  • Track investigation, root cause and corrective actions to closure, with owners and due dates.
  • Keep the data you need for statutory reporting to the regulators that apply to your site.

Rollout that keeps the site safe

  1. Pilot one unit or one contractor package for four to six weeks with paper running in parallel.
  2. Train issuers and performers on the job, not in a classroom, and keep a quick reference card in each language.
  3. Review every mismatch between the paper and digital permits during the pilot. Each one is either a software fix or a process question.
  4. Switch unit by unit, with a clear fallback to paper if the system is down.

A realistic timeline for a single site is six to ten weeks from mapping to full use. Multi site rollouts take longer, mostly because each site has its own habits.

When to buy and when to build

Several established permit to work products exist and suit large operators with standard processes. A custom build makes sense when you need tight integration with your own maintenance system, plant historian or contractor management, when your permits follow local practices a product handles badly, or when you need local language support the product lacks. Whichever route you take, the mapping work in the first step is the same, and it is where most of the value comes from.

Have a question about this guide? Write to us or ask Colony, our AI guide.

Start a conversation

Tell us what you are trying to build.

Share the problem in a short call. You leave with a clear view of the approach, the team and the cost.

Or get a ballpark proposal in two minutes

A specialist replies within one working day. The first conversation is free.

Chat with the Code Colonies team on WhatsApp