Permit to Work
Seven permit types — hot work, confined space, excavation, electrical, elevated work, line break, general. Status workflow, expiry tracking, role-based approvals, signal-domain alignment.
Platform · 02 · Field operations
Eleven field surfaces, one data model. Every permit, observation, handover, and incident tagged to a signal domain and tied to the document that governs it. Nothing in a spreadsheet. Nothing disconnected from the program it lives under.
Pre-authorization
03 surfacesSeven permit types — hot work, confined space, excavation, electrical, elevated work, line break, general. Status workflow, expiry tracking, role-based approvals, signal-domain alignment.
Task broken down step by step, with hazards, controls, and PPE per step. Risk classification from low to critical. Linked directly to tailgate meetings and the relevant permit-to-work.
Attendees, topics, hazards reviewed, PPE confirmed, permit cross-referenced. Every crew on the same page before work starts — with acknowledgement captured.
Execution
04 surfacesVoice or text capture with offline support. Five note types — site observation, drainage, equipment, training, general. Voice transcribed automatically, tagged to a signal domain.
Safe behavior, at-risk behavior, and positive recognition. Category-based with photo attachment and severity. Powers dashboards and trend analysis across domains.
Every stop-work event logged — hazard type, severity, resolution, lessons learned. Resumption tracked. Real-time domain breakdown so patterns surface early.
Air, water, waste, and noise readings against threshold and regulatory limits. Alert level computed on the fly. Compliance-ready records, not a spreadsheet.
Transition
02 surfacesIncoming lead acknowledges with timestamp. Open items carry forward. Safety observations, equipment status, personnel count, weather — the signal of a real handoff.
Draft → risk assessment → approval → implementation → closure. Per-change risk scoring, signal-domain impact, and a direct link from the change to every affected program.
Closure + competency
02 surfacesSeverity from near-miss to fatality. Root cause, corrective actions, signal-domain tags. Investigation and trend analysis in the same surface that captured the event.
Team-wide skill matrix across certifications, technical skills, and signal domains. Gap count per person, overall coverage score, expiry alerts — exportable.
Why it matters
The programs on the shelf describe what should happen. The permits, observations, and handovers describe what actually did. We instrument both, in the same system, so the gap between written and lived is visible — not inferred from a post-incident report.