Digital work permits during maintenance shutdowns: coordinating simultaneous tasks
During a maintenance shutdown, each team may have a well-planned task while unknowingly sharing a condition that conflicts with another intervention. Risk emerges between jobs: an area, installation, access route or change of state affecting several people. Digital work permits therefore require an overall view of the shutdown and the relationships between activities.
A work permit records the conditions and authorisations associated with a defined intervention. Its usefulness depends on those conditions being checked and remaining valid. An approval stored in the system loses operational value if the people doing the work do not know that circumstances have changed.
Identify relationships between interventions
INSST technical note NTP 562 describes an approach to special-work authorisations and coordination between responsible parties. It is a good-practice reference; specific procedures must reflect the assessment and legislation applicable to the particular work.
Before configuring forms, identify the area, equipment, scope, participating companies and planned period. Connect permits that share an installation or may interfere with one another. The Explore entry on permit-to-work systems helps establish which information belongs with an authorisation.
Separate preparation, authorisation and execution
The request describes the planned work. Preparation brings together required conditions and checks. Authorisation belongs to the people designated by the procedure. Execution begins when the applicable conditions are met, and monitoring must detect relevant changes. These stages need distinct states in the tool and clear responsibility for progression.
Avoid treating completion of every field as automatic authorisation. Some checks require attendance, competence or a specific responsibility. Software should retain who performed each check, when and within what scope, while preserving the technical judgement of the person responsible for the decision or verification.
Example: two jobs on a shared installation
Imagine a shutdown where one contractor inspects equipment while another works on a connected component. Each supervisor understands their task, but both depend on a common installation condition. Coordination needs to identify this dependency and establish who can authorise any change affecting both interventions.
The digital case connects jobs, owners and communications. If one job’s scope changes, its effect on the other is reviewed before work continues. This example is illustrative and does not describe a technical isolation or restart procedure: those controls must be defined for the specific installation by competent personnel.
Manage shift changes and suspensions
A handover needs to transfer the actual work status: completed activities, outstanding work, limitations and conditions that must remain in place. A signature from the incoming shift without that information may create an impression of continuity that does not reflect the conditions at the work location.
Define which changes require suspension and permit review under the procedure, such as changes in surroundings, participating teams, scope or assumptions. Record the reason, who receives the communication and what is needed before restarting. Maintenance safety depends on maintaining this connection between planning and the work actually being carried out.
- A permit status that is visible and understandable.
- A named owner for each decision and communication.
- Connections to other affected jobs.
- Outstanding conditions before work can resume.
- A change history available to the people who need it.
Close the permit and return the installation
Completing a task and returning an installation to operation are related milestones that may require different checks. Closure should identify outstanding work, area conditions and the confirmations required by the procedure. Expiry of the planned time should not automatically mark a job as satisfactorily closed.
Subsequent observations should improve future shutdowns. Connect interface problems with coordination between prevention management and CAE, and outstanding findings with corrective action follow-up. This preserves learning beyond the point when the permit itself is filed and no longer appears among active work.
What to test when evaluating software
Prepare a demonstration involving two connected jobs, a shift change and a suspension. Check how status is displayed, how affected people are informed and what happens if connectivity fails. Define operational contingencies so nobody interprets an outdated screen as a currently valid authorisation to proceed.
When exploring Sabentis for prevention management, validate this scenario with maintenance and prevention managers. The test should demonstrate that the digital workflow reflects the responsibilities and conditions of the actual procedure, including the exceptions that arise during a busy shutdown.
Digital workflow tests before a maintenance shutdown
Run a coordination simulation outside the real intervention. Its purpose is to check how changes are communicated and acknowledged; technical safety conditions remain governed by the installation’s procedures and the judgement of competent personnel responsible for the work.
- Simulate two permits linked to the same equipment and check how their dependency is identified before authorisation.
- Change an owner during handover and verify that the transferred scope and outstanding matters are clearly recorded.
- Record a test suspension and check which status is shown to people viewing a screen opened earlier.
- Rehearse a discrepancy between the displayed status and conditions at the location, using the contingency specified in the procedure.
- Review a simulated closure with outstanding work and confirm that it is not interpreted as automatic installation availability.
Frequently asked questions
Does an approved permit remain valid when the work scope changes?
It must be reviewed according to the applicable procedure and the conditions supporting its authorisation. The digital workflow should make the change visible and bring it to those responsible for deciding. An earlier approval should not be interpreted as automatic authorisation for a different intervention.
Can a digital signature replace checks at the work location?
A signature can record a decision, but it does not by itself establish that installation conditions have been checked. Define who verifies each aspect and what evidence is appropriate. Software should reflect that work, without treating a button press as a technical safety check.
What is the difference between suspending and closing a permit?
Suspension interrupts work and requires restart conditions to be addressed under the procedure. Closure records completion and the corresponding checks. Distinguish the two states so that stopped work does not appear finished and an installation is not mistakenly considered available for operation.
How should permits viewed offline during a shutdown be handled?
Establish in advance how the current status will be confirmed and what action follows if it cannot be confirmed. A local copy may be outdated. Testing should demonstrate the agreed contingency rather than assume that having the document means having current authorisation.
Legislation and sources consulted
- INSST: NTP 562, special work authorisations: Spain: technical good-practice guidance on special work authorisations; it is not itself a legal obligation.
- Royal Decree 171/2004: Spain: the preventive coordination framework for concurrent companies, relevant to work involving several contractors.
Sources consulted on 6 October 2026. The practical checklist proposes management checks; its application should reflect each organisation’s scope.
