Attach an Inhibit Certificate (INH)
Supporting action. Attach/unlink an INH while the permit is in Request or Awaiting Validation. Full details of the inhibit certificate live in the INH module.
Link an Inhibit Certificate to the permit and keep it in a state that lets the permit progress.
When to use
Use this task when the work needs an inhibition — i.e. when the INH Requirement is set to Full.
Before you start — check before launching the task
- You hold the Permit Requester role (or PCA / an Inhibit Authority role).
- An INH exists (or is created in the INH module) for the function to inhibit.
Step-by-step
- On the permit, select Attach Inhibit. Attaching/unlinking is available in Request and Awaiting Validation; later steps only check the INH state. screenshot pending
- Choose the inhibit certificate. screenshot pending
- Keep the INH in a state allowed for the permit's step. At verification, a Safety inhibit and a Process inhibit require different INH states. (Full state matrix — see the INH module.)
Expected result
The INH is linked to the permit; the permit status is unchanged.
Key Referentiel rules
- A certificate is not a permit and does not authorise work to begin. (CR-GR-HSE-402, Req 3.1.7)
- The risk analysis accounts for the installation's protective functions; inhibiting one is a controlled, documented action. (CR-GR-HSE-402, Req 3.2.1)
Tips & pitfalls
Tip — confirm the inhibit is actually in place. At Issue, a warning appears if the INH is not in place.
Pitfall — wrong INH state for the step. The permit cannot progress if the INH is not in the required state.
Common mistakes
| Mistake | Consequence |
|---|---|
| Issuing while the INH is not in place | Work starts with a protective function still active/unconfirmed |
| Wrong INH type (Safety vs Process) | Verification state requirements not met |