← Features

Permits (Permit-to-Work)

The Permit-to-Work subsystem — raise, review, issue and close out permits for hazardous work, tied to the live spatial picture.

Permits are how a construction site controls hazardous work. SimOops carries the whole Permit-to-Work (PTW) lifecycle in-app — a contractor raises a permit, a coordinator endorses it, the H&S desk approves it, an appointed issuer signs it live at the morning walk-down, and the named receiver countersigns to take responsibility at the workface. When the work is done, the permit is closed out. Because a permit is tied to the live spatial picture, incompatible permitted activities surface as clashes before anyone is exposed.

What it does for you

  • One record, one lifecycle. A permit moves through a data-driven status spine with the right desk gating each transition. See Permit lifecycle.
  • Approval that fits the site. Two-stage (coordinator endorsement then H&S approval) or a single-stage workflow, chosen per site.
  • Live on the map. A Permit-linked entity carries its permit's window and controls onto the plan, so the clash engine can reason about permitted work — see permit-aware-clash-matrix-and-consequences.
  • The board. Everything in flight is visible on the Permit board, with coverage checks and expiry / activation sweeps keeping it honest.

The lifecycle at a glance

Every permit walks a fixed state machine (the shape never changes; per-site config only decides who acts at each gate). The happy path:

draftrequestedendorsedapprovedissuedclosed

with expired as an alarm state and rejected / corrections_requested / withdrawn as off-ramps. Single-stage types skip endorsement; the two field signatures — issue then countersign — are what actually take an approved permit live.

See it / try it

Where to go next

The Guide zone carries a focused walkthrough per audience:

Generated from source · SimOops living system reference