QEHSmodules
Template · SOP / procedure control
Versioned procedures with redline diff, review cadence cron, training acknowledgement, and effectivity-date gating.
5 min read · 3 sections
What it looks like
Procedure AddEdit — 14 fields, 5 workflow states
Redline view — v1.4 vs v1.5 side-by-side
Sample records (pre-seeded)
| Doc ID | Title | Version | Effective | Review due |
|---|---|---|---|---|
| SOP-001 | Hot-work authorisation | v1.5 | 2025-01-02 | 2026-01-02 |
| SOP-002 | LOTO procedure | v2.1 | 2024-11-19 | 2025-11-19 |
| SOP-003 | Forklift pre-op | v1.0 | 2025-03-15 | 2026-03-15 |
| SOP-010 | Emergency evacuation | v3.0 | 2024-06-01 | 2025-06-01 |
Typical configuration
- Capability: versioning is server-side — old versions are retained read-only; new versions open in draft with a redline copy.
- Guard: state cannot move to Effective until Training-acknowledgement quota is met for the assigned audience.
- Cron: 30-day and 7-day review-due alerts to the procedure owner.
- Permissions: Authors write drafts; Approvers sign off; All-staff read-only on Effective versions.