Create a Permit from a Routine Permit
Status:
Request →
Awaiting Validation
TO BE CONFIRMED — Placement: routine permits also belong to the Routines module (module 5). Confirm whether this task is documented here or there before scaling. Source needed: project decision.
Generate a new permit from an approved routine template and submit it for validation.
When to use
Use this task for recurrent work that has an approved routine, to standardise the permit. The work must still match the conditions the routine was approved for.
Before you start — check before launching the task
- You hold the Permit Requester role.
- An approved routine exists for this work and still fits the current conditions.
Step-by-step
- Open the create menu and select Routine permit. screenshot pending
- Choose the approved routine for this work. The permit opens in Request, pre-filled from the routine. screenshot pending
- Check the permit against the current conditions on site (the routine is a template, not a live assessment). Fields fixed by the routine (e.g. Management Comments Routine) are not editable.
- Sign Request Routine Permit by Permit Requestor to submit it. screenshot pending Because the routine carries the assessment, the per-member Confirm Risk Assessment signatures are not used. Downstream, the permit is authorised with Authorise Routine Permit by Operating Authority or RSES (see Authorise a Permit), not the standard RSES authorisation — and a routine-based permit can also be closed by the PCA from the Awaiting Issue state.
Expected result
The permit moves from Request to Awaiting Validation. The next task is Validate a Permit.
Key Referentiel rules
- Reuse (routine) does not remove the need to check current work conditions. (CR-GR-HSE-402, Req 3.2.1)
- A "simplified"/routine permit is only for recurrent, low-risk work that does not generate co-activity or simultaneous operations. (CR-GR-HSE-402, Req 3.1.8)
- The list of work eligible for a routine/simplified permit is established by risk analysis and reviewed at least yearly. (CR-GR-HSE-402, Req 3.1.8)
Tips & pitfalls
Tip — confirm the routine still fits. A routine approved months ago may no longer match today's plant state.
Pitfall — assuming "routine" means "no checks". Current conditions, co-activity and SIMOPS must still be checked.
Common mistakes
| Mistake | Consequence |
|---|---|
| Using a routine for work that is not low-risk/recurrent | Outside the routine's scope; non-compliant |
| Not checking current conditions | Controls may not match the real situation |
| Expecting the standard authorisation flow | Routine permits follow a different authorisation signature |