| Permit administration | Documented by vendor | The help material describes creating, issuing and managing permits through their lifecycle. Test permissions for each issuer and recipient. Permit administration help |
|---|
| Control-of-work linkage | Depends on scope | The product page describes JSA, LOTO and SIMOPS links. Demonstrate the exact rules and required package rather than assuming automatic risk prevention. Permit features and offline synchronization claims |
|---|
| Incident investigation | Documented by vendor | Reporting, investigation roles and corrective work are described with configurable workflows. Incident workflow and mobile reporting |
|---|
| Inspection review | Documented by vendor | Custom templates, scheduling, findings and reviewer approval support an inspection cycle. Inspection templates, approval and trial |
|---|
| Offline capture | Depends on scope | The incident page documents later synchronization. Permit authorization needs a separate conflict-handling demonstration. Permit features and offline synchronization claimsIncident workflow and mobile reporting |
|---|
| Incident exports | Documented by vendor | The help article documents filtered incident listings and Excel export. This offline spreadsheet use is distinct from disconnected app operation. Incident listing, filters and export help |
|---|
| HIRA risk statements, approval and version history | Depends on scope | The HIRA page describes risk statements with a 5x5 likelihood-severity matrix, residual risk, controls, approval before publication, archived prior versions, searchable tags, export and audit trail. It also says HIRA comes with the Audits module and describes Permit and Incident links as Enterprise features. Confirm module entitlement, matrix configuration and governance, competent approvers, control verification, reapproval triggers, version comparison, export completeness and whether cross-module links are included. HIRA risk statements, 5x5 matrix, approvals, versioning and Enterprise links : checked 29 September 2026 |
|---|
| Safety observations and action-dependent closure | Depends on scope | The official help article lists Unsafe Acts, Unsafe Conditions and Best Practices, severity sorting, search, site, type and date filters, Excel export and mobile detail views; observation cards move to Closed after all linked actions close. Confirm reporting identity, anonymous access if required, evidence and privacy, duplicate handling, reviewer verification, reopen rules and whether action status alone is sufficient to close an observation. Observation types, severity, actions, filters and export : checked 29 September 2026 |
|---|
| Cross-module assigned-action register | Depends on scope | The Actions help article describes one list consolidating assignments from Observations, Incidents and Audits with category, keyword, date and status filters. Confirm whether inspection and HIRA actions are included, ownership and reassignment, due dates, escalation, evidence, acceptance, effectiveness checks, reopen behavior and export or API access; a consolidated list does not prove verified completion. Cross-module assigned-action list and filters : checked 29 September 2026 |
|---|
| Role-authorized permit approval | Depends on scope | The permit approval help page says admins or user roles with granted privileges may issue permits, with pending status, permit-detail review, editing, approval and in-app or email requests. Confirm segregation of request, edit and approval duties, multi-stage or site-specific approval, reapproval after edits, identity assurance, timestamp and signature evidence, delegation, expiry and emergency override. Role-authorized permit approval and notification flow : checked 29 September 2026 |
|---|
| Permit revocation and affected-person notification | Depends on scope | The revocation help page describes immediate revocation from a permit form and notifications or email to workers and designated authorities connected to the permit. Treat 'all work operation will be halted' as a procedural intent, not a guaranteed physical outcome. Demonstrate authorized revokers, mandatory reason, device and connectivity states, recipient acknowledgement, failed or delayed notices, stale offline permits, reissue rules and audit history. Permit revocation and affected-person notification flow : checked 29 September 2026 |
|---|