Back to Blog
Blog

How do you build a mobile first permit workflow for people moving around a rig?

How do you build a mobile first permit workflow for people moving around a rig?

On a rig, the people who request, check and approve permits are almost never sitting at a desk, which is why permits that need a computer end up waiting…

On a rig, the people who request, check and approve permits are almost never sitting at a desk, which is why permits that need a computer end up waiting until someone walks back to the office. A performing authority may be on the drill floor, the area authority may be in the middle of a round on another deck and the gas tester may be handling several jobs at once, so every trip back to a shared computer adds delay and pulls people away from the work they are supervising.

Designing for mobile means the whole workflow, from raising the permit to gas testing to approval and closeout, can be done on a phone or tablet wherever the person is. That is different from making a desktop form open on a phone, since a form built for a large screen with dozens of fields on one page becomes almost unusable on a small one, especially for someone wearing gloves, standing in wind or rain and trying to keep an eye on what is happening around them.

A mobile first workflow also means short screens, simple inputs, offline support for areas with poor signal and notifications that reach the next approver as soon as it is their turn. In practice the best permit screens ask one group of related questions at a time, use picklists and toggles instead of free text where possible, let the gas tester enter readings at the location and keep working when the device drops out of coverage below deck, syncing once it reconnects.

Hardware and environment matter as much as screen design on a rig, since devices may need to be rated for hazardous areas, readable in bright sunlight and charged and assigned at the start of each shift. It is worth agreeing early which roles carry devices, how permits are handed over at crew change and what happens if a device fails partway through a job, so the mobile workflow does not depend on everything going perfectly.

Permit to Work in Interface sits in the mobile app for this reason, since the permit should move at the same pace as the people working on it. When the permit travels with the people raising, testing and approving it, the time between someone being ready to start and the permit being ready to work under gets shorter, and the record of who did what and when is captured where it happened rather than reconstructed later from memory.