Digitise permits to work without reducing them to signatures

The permit is part of a safe system of work

A maintenance permit is approved on a phone, but the job changes after the team reaches the equipment. The original record still appears active, and another contractor begins related work nearby. The application has captured signatures while losing the conditions those signatures were meant to authorise.

A pharma permit-to-work system should preserve the scope and operating controls established by the site's competent safety and engineering personnel. It should make changes and conflicts visible, connect the relevant checks and support a controlled handback. It cannot establish physical safety merely by collecting completed fields.

UK HSE guidance highlights related permits, simultaneous activities, plant handover and the risks of moving to an electronic permit system. It is a useful design reference, not a replacement for applicable Indian or state requirements and the site's approved procedures. HSE permit-to-work guidance.

Define the job boundary precisely

Identify the equipment or area, intended work, responsible team, authorising roles and validity conditions. The description should be specific enough for a supervisor to recognise when the actual job has changed. “Maintenance in production” is too broad to support that decision.

Link the applicable risk assessment, work instructions and required prerequisite evidence. The competent site team determines the controls for the particular hazards and work. A generic digital template should not prescribe hazardous-work steps or substitute for that assessment.

Use controlled asset and area identifiers. A permit attached to the wrong pump or room can appear complete while authorising the wrong context. Where a location has several similar assets, the interface should help users confirm identity using the site's established method.

Record checks without pretending the screen performs them

The workflow can require confirmation of site-defined prerequisites and identify who performed each check. It should preserve the relevant evidence and timing. A preselected checkbox or copied approval from a previous job can weaken the meaning of that confirmation.

Design the interface with the people who issue and use permits. Labels should describe the actual decision and required evidence. Avoid long, repetitive forms that encourage users to select every option without considering the task-specific conditions.

Where evidence is captured electronically, preserve its relationship to the permit and time of the check. A photograph can support context but is not necessarily sufficient proof of a technical condition. The site's procedure should define what evidence is appropriate and who may accept it.

Worked example of a mid-shift scope change

Consider an illustrative permit for a defined maintenance activity on one asset during a morning shift. During the job, the contractor discovers that additional work outside the authorised scope is needed. The site's approved procedure requires suspension and reassessment before that changed work begins.

The mobile workflow records the scope-change event, identifies the current permit and makes its suspended state visible to the relevant teams. It routes the revised work description to the competent authorisers. The original scope and approvals remain in the history.

The reassessment considers the changed work and any related activities under the site's safety process. The application can show other active permits in the area, but the responsible people determine whether the combination is permissible and which controls are required. It should not calculate a generic “safe to proceed” score.

If revised permission is granted, the system records the new scope, conditions, authority and effective period. If it is not granted, the work remains suspended. A user should not be able to continue by editing the original description after approval while retaining the appearance of unchanged permission.

This example demonstrates a workflow control. It deliberately does not provide technical instructions for hazardous work; those depend on the actual task, site and competent assessment.

Coordinate simultaneous and dependent work

Provide an area and asset view of relevant active, suspended and planned permits. Link permits that depend on one another or share controls under the site's process. A simple list sorted by creation time may hide work occurring on connected equipment.

Show the owner and current state of related work. If one permit is suspended or its conditions change, identify the other permits requiring review. The dependency rules should be defined and assessed with the safety and engineering teams, not inferred solely from matching location text.

Avoid assuming that two individually approved jobs are safe together. The coordination process needs to consider their interaction. The digital system should make that review easier and preserve the resulting decision.

Plan shift handover and contractor readiness

Specify how responsibility transfers when work continues across shifts. The incoming authorised people need the current scope, conditions, outstanding work and relevant evidence. A permit remaining visible on a screen does not establish that the handover occurred.

The shift skill-coverage guide helps identify whether the required authorised roles are available. The contractor-onboarding guide addresses task readiness, sponsorship and time-bounded access.

Keep these records connected without assuming one proves the others. A contractor's site badge does not authorise a specific job, and a permit does not replace the required competence or access checks for the engagement.

Define offline behaviour before deployment

Work areas may have unreliable connectivity or device restrictions. Decide what the approved process allows when the application cannot obtain current state. A cached permit can become misleading if it was suspended elsewhere after the device last synchronised.

Display the last synchronisation time and define how stale information is handled. The site's safety process should determine whether and how work can continue through an authorised alternative. The software team should not invent a permissive default to improve usability.

Reconcile offline actions after connectivity returns. Preserve actual event times and identify conflicts. A later upload should not overwrite a suspension or create two incompatible versions of the same authorisation.

Close the job and hand back the asset

Work completion, area handback and equipment readiness can involve different checks and authorities. Define the relevant sequence under the site's procedures and preserve the evidence. Closing a permit should not automatically mark production equipment ready if other requirements remain.

The maintenance-readiness guide covers that operating handback. Link the permit outcome to the maintenance record so production sees the appropriate state and any remaining dependency.

If work is incomplete or the asset remains restricted, the closure or suspension record should explain that condition. Avoid a binary closed/open field that loses the reason the equipment cannot yet be used.

Pilot with exceptions and competent reviewers

Start with a defined permit category and area approved for the pilot. Use controlled exercises for scope change, conflicting work, shift handover, an unavailable authoriser and lost connectivity. The relevant safety specialists should judge whether the workflow preserves the site's required controls.

Measure ambiguous permits, unresolved handovers and time spent locating current information. Faster approval is useful only when the decision remains informed and the physical prerequisites are properly addressed.

NextEdge Labs can digitise the records, dependencies and status sharing around the approved permit process. The implementation should be accepted through realistic scenarios, not merely a demonstration that signatures can be collected on a phone.

Summary and next actions

A digital permit system should preserve the scope, conditions and competent decisions that authorise work. Its value is clear coordination and evidence, while physical safety remains governed by the site's approved process and responsible people.

• Map one permit category from work definition through suspension and handback.
• Define how scope changes and simultaneous work trigger reassessment.
• Test shift handover and stale offline information with the competent site team.
• Verify that permit closure cannot bypass unfinished equipment-readiness conditions.