Permits, JHA & Isolation
Innovapptive · Web & mobile
Making the next step clear in safety workflows.
Connected web and mobile experiences that show the job, linked safety records, and who needs to act next.
- MY ROLE
- UX design, interaction flows & later frontend contributions
- PERIOD
- September 2024 onwards
- TEAM
- Product managers, design leadership & engineering
- STATUS
- Historical designs and scoped frontend contributions
Connected permit review, hazard analysis and isolation through visible roles, linked records and clear next actions across web and mobile.
The challenge
Related records. Different responsibilities.
A permit controls authorization for potentially hazardous work. Job Hazard Analysis (JHA) records the steps, hazards and controls. Isolation records describe the equipment isolation process. These are connected, but each has its own responsibilities and lifecycle.
I joined Permit to Work after the work had begun with another designer, then grew into ownership across permits, JHA and isolation. I mapped roles with in-house industry experts and existing clients, with experts reviewing design decisions.
Keep the job in view
Preserve job details and linked work orders where applicable. Permits can also be standalone.
Make responsibility explicit
Show the current stage, responsible role, linked records and available next action.
01 · Permit review
Show the linked status at the decision.
A reviewer needs to understand the permit and its supporting records together. I placed linked JHA status inside permit review so that the reviewer can check progress without losing the job context.
The design separates work details, safety information and progress. Required checks and stage sequences depend on configuration; one lifecycle should not be assumed to apply to every customer.
02 · Hazard analysis
Keep the assessment and its team connected.
JHA brings job steps, hazards and controls into one working area. The owner assigns the team, contributors amend and acknowledge the analysis, and an approver reviews it.
I kept the assessment visible behind a focused team-assignment dialog. This makes assignment a clear decision within the work rather than a separate administrative task.
03 · Isolation
Make status understandable at equipment level.
Isolation control certificates (ICCs) can be difficult to follow as a flat list. I grouped records by equipment and made status and ownership visible together.
This gives reviewers the context to understand which records belong to an asset. Isolation and de-isolation retain their own reviews and approvals; the interface should clarify these responsibilities rather than collapse them.
04 · In the field
Support the same decisions on a smaller screen.
On mobile, the work included selecting a work order, retaining its reference and checking required fields before signing. Expired forms are read-only, with appropriate surrender behavior rather than an unrestricted editing flow.
Later frontend contributions covered reference handling and validation. I checked interactions in the browser and iOS simulator. The goal was to preserve the role, stage and job context as people moved between surfaces.
Outcome & reflection
Clarity across handoffs, not just individual screens.
The work spans permit flows, JHA authoring and isolation, with later implementation contributions. Historical designs and individual frontend changes should not be read as a claim that every depicted feature shipped.
There are no measured safety or completion-time improvements to report. My takeaway is to design around responsibility: who acts next, what evidence they need, and what happens when a prerequisite is incomplete.