Industries · 5 min read

Digital permit to work for oil and gas: sign-offs, expiry and audit

Permit to work software for oil and gas: parallel sign-offs, permits that expire with the shift, contractor checks and an audit trail regulators trust.

A digital permit to work replaces the paper permit book with a governed workflow: the right people sign off before hazardous work starts, every permit expires with its shift, and the audit trail is complete by default. For oil and gas operators, permit to work software is less about digitizing a form and more about making the safety rules impossible to skip. Here is how that looks when it runs on NeurallEmpire.

The permit book problem

• Permits live on paper or in spreadsheets, and their status lives on a whiteboard in the control room.
• Sign-offs are collected by walking the permit around, so the order of approvals depends on who is on site.
• Permits outlive their shifts because closing them depends on someone remembering.
• Contractor competence is checked against a list that may be months old.
• After an incident, reconstructing who approved what, and when, takes days.

What good looks like

Permit to work software that oil and gas safety compliance teams trust has a few properties:

• No permit becomes active until every required role has signed off.
• Validity is tied to the shift, and expiry happens on its own.
• Anyone in the control room can see every active permit by area at a glance.
• Contractors and their certifications are checked before a permit names them.
• Every change is recorded in a way auditors can verify.

How it runs on NeurallEmpire

Permit to work is a blueprint: it is configured from capabilities that ship today, not sold as a packaged product. A typical configuration looks like this:

1. A permit record with a lifecycle. Draft, requested, approved, active, suspended and closed. The record locks after approval, so the approved scope cannot be quietly edited.
2. Parallel sign-off. The area owner and the safety officer approve in parallel, and both are required before the permit becomes active. Segregation of duties stops a requester from approving their own permit.
3. Expiry on a timer. A timer on the shift calendar expires the permit at the end of its shift. An extension is a new approval, not an edited date.
4. A live board. A Kanban board of active permits by area, where moving a card runs the same rules as the form.
5. Evidence attached. Gas test readings, isolation details and site photos are stored on the permit.
6. Audit by default. Who approved what, and when, sits on the hash-chained, tamper-evident audit trail.

Contractor management uses pieces that are built and tested. Our vendor onboarding reference takes a supplier through a document check and procurement and finance approval, with bank details masked outside finance. The same case pattern onboards a contractor company, and time-bound access means a contractor's assignment lapses on its own when the engagement ends. Certificates with validity dates and reminders before they lapse follow the training and certification blueprint, so a rule can refuse a person whose certificate has expired.

Maintenance work that triggers permits lives on the same data model, as in our Service Hub field service reference.

What to know before you start

• It is a responsive web app, not an offline mobile app. Work faces with no connectivity need a coverage plan or a paper fallback that is entered afterward.
• Sign-off is an approval action, not a handwritten signature. The platform records who approved, when and under which role. It does not capture signatures; a photo of a signed sheet can be attached where a wet signature is still required.
• There are no native connectors to your EAM or ERP. Work orders and asset data flow in and out through the generated API and webhooks with replay.
• It is not a certified safety system. The platform enforces the process you define; your safety case and procedures still own the rules.

Where it connects

• Preventive maintenance software shows how planned and breakdown work orders run on the same platform.
• Compliance management software covers obligations, evidence and the audit trail behind your safety regime.
• Document approval workflows handle the procedures and method statements a permit references.
• Vendor onboarding software explains how contractor companies are verified before they reach site.
• Explore the permit to work blueprint.

Frequently asked questions

What is digital permit to work software?

Permit to work software manages the request, approval, activation and closure of permits for hazardous work. A good system enforces the required sign-offs, ties validity to the shift and keeps a complete audit trail. On NeurallEmpire it is configured as a governed application rather than bought as a fixed package.

Can a permit expire automatically at the end of a shift?

Yes. A timer on the shift calendar moves the permit to expired when its window ends. Extending the work means raising a new approval, so the record of who allowed the extension is preserved.

How are contractors checked before they are named on a permit?

Contractor companies go through an onboarding case with document checks and approvals. Individual certificates carry validity dates with reminders before they lapse, so a rule can stop an expired certificate holder from being assigned.

Want to see a permit to work configured for one of your sites? Talk to us about a pilot.