Live Permits — SiteActive

One permit per job

Every job gets its own permit with its own daily log — live state, not paper in a folder. Who is working, under what permit, on which site, right now.

Live state

A permit you can watch

Every active permit is visible in real time across the organisation — open, confirmed, logged, closed.

One permit per job, no blanket permits

Live status across all sites

Full history retained per permit

Daily logs

Logged every day it runs

Multi-day jobs carry a daily permit log — each day confirmed, each day recorded, gaps impossible to hide.

Daily confirmation per running permit

Continuous record for multi-day work

Log travels with the permit record

The gate is not negotiable

A permit cannot be issued to a contractor who doesn’t qualify for one. The system checks live compliance at the moment of issue — and deterministic rules block issuance outright on critical lapses.

Score gate

Below the bar, no permit

Permit issuance is hard-gated on the live compliance score. It is not a warning or a report — the permit simply cannot be created.

Issuance blocked below threshold

Checked live at the moment of issue

No manual workaround culture

Hard blocks

Some lapses stop everything

An expired Section 37(2) agreement, a lapsed COIDA good standing, a failed medical fitness — deterministic rules that block work, with the reason stated.

Section 37(2) expiry blocks issuance

COIDA and medical fitness lapses demobilise

The deny reason is always given

See the GTI & Circuit Breaker →

The workspace confirms the job

Permits tied to a business unit route to the appointed workspace owner — the person accountable for that floor confirms or declines before work proceeds.

Appointee routing

The right person signs

Business-unit permits notify the appointed workspace authority automatically — accountability lands where the law puts it.

Routed to the BU appointee

Confirm or decline, on record

No permit floats without an owner

Advisory

The workspace answers back

Workspace-level advisories surface conditions and conflicts before the job starts — the site talks back to the permit.

Conditions surfaced at confirmation

Conflicts visible before work starts

Recorded against the permit

Closeout that means something

A permit isn’t finished when the job is — it’s finished when the closeout is verified. Identity-verified sign-off, closure notes, and an explicit incident flag on every single closure.

Verified sign-off

Identity-verified closure

Closeout is confirmed with a one-time PIN — the person closing the permit is the person recorded closing it, with full ECT Act audit detail captured.

One-time-PIN verified closure

Signer, time and origin recorded

Aligned to the ECT Act 25 of 2002

Incident flag

The question is always asked

Every closeout asks whether an incident occurred — answered on the record, feeding the incident register when it matters.

Incident flag on every closure

Closure notes preserved

Feeds incidents & investigations

Visible beyond the login

Clients and inspectors don’t need accounts to see a permit. Tokenised public views put the live permit in front of whoever needs to see it — read-only, current, verifiable.

Public view

Show the permit, not a PDF

A secure public link shows the live permit state to a client or inspector — no account, no stale printout.

Tokenised read-only access

Always the current state

Nothing to install or sign up for

For the record

It stands afterwards

The full permit record — issuance checks, confirmations, daily logs, verified closeout — is preserved as evidence.

Complete lifecycle preserved

Part of the evidence architecture

There on the day it matters

See how it connects in the OS →

Put permit-to-work behind a real gate

Software-only deployment takes up to 72 hours — no hardware, no rip-and-replace.

Applications close 31 July 2026Programme commences 4 August 2026Seats strictly limited

Apply for the pilot →

No compliance. No permit.