E-Permit

An enterprise-grade Electronic Permit-to-Work platform designed to digitize and manage workplace safety workflows across multi-role approvals, active execution, and closure verification.

The problem

Traditional permit-to-work processes rely on fragmented paperwork, manual handoffs, and siloed approvals, making it difficult to verify safety compliance, inspect real-time permit status, or audit historical closures. E-Permit centralizes and digitizes the entire permit lifecycle with role-based access control and transparent workflow progression.

The engineering approach

Engineered as a modular enterprise React application organized into feature-driven modules, centralized API services, and typed workflow constants. Built with Fluent UI for enterprise-grade design consistency, protected routes with role-based authorization (Initiator, Issuer, Executor, Admin), and React Context for application-level state. Implemented multi-stage lifecycle transitions, structured hazard and PPE checklists, and responsive drawer and modal workflows rather than treating safety permits as basic CRUD records.

What’s inside

• Create and manage electronic permits across categories including Electrical, Mechanical, Hot Work, Confined Space, Height Work, Excavation, and General
• Multi-stage workflow lifecycle: Initiation, Review, Execution, Active Work, Closure, and Verification
• Role-based authorization with distinct permissions for Client, Admin, Sub Admin, Initiator, Executor, and Issuer
• Safety and hazard management with real-time PPE compliance tracking and workplace hazard verification
• Feature-based modular React architecture with centralized REST API service layer and typed state
• Search, status filtering, and workflow drawer & modal interfaces for operational clarity
• Responsive enterprise UI built with Fluent UI, lazy-loaded routes, and centralized status definitions
• Supporting enterprise modules including dashboards, user management, and safety workflows

Challenges & trade-offs

• A strict multi-stage workflow state machine prevents safety policy violations and premature execution, requiring rigorous state validation at every role handoff.
• Client-side role-based routing and context provide responsive UI gating, while requiring strict backend authorization on every API endpoint to enforce compliance.
• Centralized safety taxonomies and feature-based modularization increase initial architecture boilerplate but make adding new permit categories and compliance rules predictable.