The OS · Live Projects
Every project, live.
A project in SiteActive is a working environment, not a folder. Contractors, documents, permits, workers and readiness all scope to the project — with a gate in front of mobilisation and a live view for the client.
01
The project hub
Everything a project generates lives against the project — its contractors, its SHE file, its permits, its people, its equipment checks — one place, one state.
One environment
Scoped to the project
Contractors, documents, permits and workers attach to the project itself — nothing generic, nothing lost across sites.
Contractors assigned per project
Documents and permits project-scoped
Workers assigned to where they work
Live readiness
A state, not a status meeting
The project carries its own live readiness built from real records below it — visible before anyone asks.
Readiness computed from live records
Moves when the facts move
No manually maintained trackers
02
The project SHE file and the gate
Each project assembles its own SHE file from the tiers above it, checks it against what the engagement actually requires — and gates mobilisation on the result.
Requirements check
Checked against the job
The Project SHE Requirements Check reads the engagement’s scope and confirms the file answers it — requirement by requirement.
Requirements resolved per engagement
Both sides see the same list
Pre-mobilisation gate
Ready before boots on site
A contractor who doesn’t meet the project’s requirements doesn’t mobilise. The gate runs before day one — not in the first audit.
Mobilisation gated on readiness
The deny reason is stated
More on the SHE File →
03
Contractor assignment
Assigning a contractor to a project pulls their live compliance with them — their vault, their gaps, their score — and builds the engagement file from there.
Assignment flow
Invited, assessed, assigned
Contractors are invited into the project, their portfolio is read against its requirements, and the engagement file assembles itself.
Invite and accept on the record
Portfolio read against requirements
Engagement file built automatically
Sub-contractors
The chain stays visible
Guest sub-contractor files are built into the engagement tier — the compliance chain doesn’t stop at the first contract.
Guest sub-contractor files included
Visibility down the chain
More on contractor management →
04
Emergency readiness, geolocated
When something goes wrong, nobody should be searching for a phone number. Every project auto-populates its nearest emergency contacts from its actual location.
Auto-populated
The nearest, not the generic
Nearest hospital, SAPS station and fire station resolved from the project’s coordinates — per project, automatically.
Nearest hospital per project
Nearest SAPS and fire station
Resolved from real location
At hand
There when it’s needed
Emergency contacts sit on the project for everyone working it — current, correct, and never a laminated sheet from the last site.
Visible to the project team
Updates when the project moves
More on incidents & investigations →
05
The client sees it live
Principals and clients get a live, read-only view of the project’s compliance state through a secure link — no account, no monthly PDF, no version confusion.
Client view
A link, not a report
A tokenised public view shows the client the project’s live state — the same truth the system holds, read-only.
Always current, never versioned
Trust built in
Nothing to take on faith
What the client sees is computed from the records underneath it — the same architecture that stands as evidence later.
Computed from live records
Consistent with the evidence layer
No parallel truth in slides
See how it connects in the OS →
Run your next project on the operating system
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 →