Home
Part I: Understand iPermits
Understand iPermits roles, permissions, lifecycle stages, and the Web and Mobile screens used for each action.
Create and Manage Permits
A permit moves through Raise, Review, Authorize, Issue, Execute, and Close. Each stage passes responsibility to the role that owns the next action.

Title and Copyright
Copyright and Terms of Use page for iPermits.
Preface
Use this guide according to your role in the Permit-to-Work or JHA lifecycle.
Part I: Understand iPermits
Understand iPermits roles, permissions, lifecycle stages, and the Web and Mobile screens used for each action.
- Introduction to iPermits
  iPermits is a digital Permit-to-Work application that helps to manage work permits and Job Hazard Analyses (JHAs) throughout their lifecycle. Depending on your role, you may create, review, approve, issue, execute, or close permits. This guide explains how to perform these tasks using the iPermits Web and Mobile applications.
- Roles and Responsibilities in the Permit Lifecycle
  Identify which role owns each permit and JHA stage before taking or handing off an action.
- Create and Manage Permits
  A permit moves through Raise, Review, Authorize, Issue, Execute, and Close. Each stage passes responsibility to the role that owns the next action.
  - Revert, Reject, Hold, Surrender, and Close
    Understand what each lifecycle action does and who is responsible next.
- Sign In and Find Pending Actions
  Sign in on Web or Mobile, then use the available dashboard and lists to find permit or JHA actions assigned to your role.
Part II: Raise and Plan Permits
Raise work-order-linked or standalone permits, complete required planning information, and submit them for review.
Part III: Review and Prepare Permits
Review, authorize, validate, issue, hold, resume, or reject permits according to the active lifecycle role.
Part IV: Execute and Close Permits
Acknowledge and execute permitted work, complete safety checks, surrender the permit, and close it after completion.
Part V: Create and Manage JHAs
Create a JHA, assign the field team, acknowledge hazards and controls, and approve or return the JHA.
Part VI: Create and Manage Isolations
Create an Isolation Control Certificate (ICC), define the isolation plan, and move the isolation through the required review, approval, isolation, de-isolation, and closure stages.
Part VII: Monitor and Audit
Monitor permit expiry and extensions, review retained evidence, access archives, and resolve execution or synchronization issues.
Part VIII: Design and Configure (Administrator / Template Author)
Design and publish Permit, JHA, and Form templates and configure the list views shown to users.

Create and Manage Permits

A permit moves through Raise, Review, Authorize, Issue, Execute, and Close. Each stage passes responsibility to the role that owns the next action.

The normal permit lifecycle is:

Raise → Review → Authorize → Issue → Execute → Close

When the permit template requires field validation (see When Field Validation Is Required), the lifecycle is:

Raise → Review → Authorize → Field Validation → Issue → Execute → Close


Completed stage	Next owner	Next action
Raise	Permit Reviewer	Review the submitted scope, hazards, and controls.
Review	Permit Authorizer	Perform authorization checks.
Authorize	Field Validator or Permit Issuer	Validate the site when required, then issue the permit.
Field Validation	Permit Issuer	Issue the validated permit.
Issue	Permit Holder or Technician	Acknowledge and execute the permitted work on Mobile.
Surrender	Permit Issuer	Review completion and close the permit.

Within Execute, the Permit Holder acknowledges the permit, performs the work, and surrenders the permit; the Permit Issuer then closes it.

When the permit requires a JHA, the Permit Authorizer cannot authorize the permit until the linked JHA is approved. See How JHA Connects to the Permit Lifecycle.

Use Role-Based Permissions to confirm the role and platform responsible for a specific action. Execution is performed on Mobile; Web supports the documented lifecycle, monitoring, closure, and administration actions.