The SHARD Permit to Work module is live. It supports the practical PTW lifecycle: creating permits, assigning responsible people, moving permits through status changes, linking risk context, and keeping active work visible across the operational team.
The system is built around controlled transitions rather than loose form edits. A permit moves through defined operational states — requested, confirmed, approved, issued, open, extended, closed, and archived — and those transitions are enforced at both the application and database level. Deletion is handled as a soft-delete, preserving the audit record.
The important point is accountability. Approvers, issuers, requesters, and permit holders are not just names on a form — their roles determine what actions are permitted at each stage. The platform is also consolidating toward a cleaner role taxonomy that separates tenant-level roles from platform-level roles.
PTW connects to related SHARD surfaces including SIMOPS, matrix generation, project settings, personnel visibility, and risk assessment links. It is not just a record of permission. It is part of the operating control layer.