How JHA Connects to the Permit Lifecycle
When a permit requires a JHA, the JHA runs its own lifecycle and the permit cannot be authorized until the linked JHA is approved.
Role: Permit Requester, JHA Requestor, JHA Owner, JHA Team, Permit Authorizer. Platform: Web and Mobile.
| Point in the permit lifecycle | What happens to the JHA | Where to continue |
|---|---|---|
| The requester raises a permit that requires a JHA | The configured JHA request is initiated as part of the permit workflow. | The JHA Requestor opens the request from the Request tab (Request Received) on the JHA screen and raises the JHA. See Raise a JHA on Web. |
| Before authorization | The JHA moves through Initiate → Assign → In Progress → Approve. | The JHA Owner assigns the JHA Team, the team completes Work Acknowledgement, and the JHA Owner approves the JHA. See Create and Manage JHA. |
| Authorize | If the linked JHA is not yet approved, the Permit Authorizer cannot authorize the permit. | After the JHA is approved, the Permit Authorizer continues with Authorize the Permit on Web or Authorize the Permit on Mobile. |
| JHA is reverted for changes | Team members must re-acknowledge after the changes are made. | See Complete Work Acknowledgement on Web or Complete Work Acknowledgement on Mobile. |
