The OS · Evidence Integrity

On the day it matters, what can you prove?

Compliance is judged in hindsight — by an inspector, an insurer, a commissioner or a court. SiteActive is built for that day: records captured as they happen, sealed against tampering, and exportable as structured evidence aligned to the ECT Act 25 of 2002.

01

Evidence Integrity

Key compliance events are captured as tamper-evident, independently verifiable, forensic-grade records. Not a backup. Not a promise. A record built to be tested by someone hostile to it.

Tamper-evident
It shows if it’s touched
A sealed record cannot be quietly altered after the fact — any interference is detectable on examination.
Tamper-evident by design
Interference is detectable
Built to be examined
Independently verifiable
Take SiteActive’s word for nothing
Verification does not depend on trusting SiteActive — a token-secured verification console lets legal teams, auditors and insurers run the integrity check themselves.
Token-secured verification console
No trust in the vendor required
Forensic-grade by intent
02

The audit log

Every significant action on the platform is written to a sealed, timestamped audit log — who did what, when, in sequence. It exports as a structured legal record when the sequence of events is the question.

Sealed record
Written once, in order
Actions are logged as they happen with actor, time and detail — a sealed sequence, not an editable table.
Every significant action logged
Actor and time on every entry
Sequence preserved and sealed
Legal export
The timeline, on demand
The log exports as a structured legal record for a defined period — the timeline of events, produced in minutes rather than discovered in weeks.
Structured legal export
Any date range, on demand
Ready for legal review
03

The evidence pack

One export, six sections: the SHE File state, permits, corrective actions, the audit trail, record confirmation and integrity verification — with a statement aligned to the ECT Act 25 of 2002 that governs electronic evidence in South Africa.

Structured
Ordered for scrutiny
The pack is assembled the way it will be read — by a legal team, an insurer or a commissioner — not as a folder of loose PDFs.
Six structured sections
Ordered for legal reading
Produced on demand
ECT-aligned
Built for admissibility
Every pack carries a statement aligned to the ECT Act 25 of 2002 and the integrity verification to support it — structured for admissibility, produced in minutes.
ECT Act 25 of 2002 alignment
Integrity verification included
Minutes, not a discovery process
04

Signatures that stand

Every legal signing moment on the platform — Section 37(2) on both sides, permit closeouts, client pass-out sign-offs — is identity-verified and captured with full audit detail.

Verified identity
The signer is the signer
Signing is confirmed with a one-time PIN — time-limited, attempt-limited — so the person on the record is the person who signed.
One-time-PIN verification
Time- and attempt-limited
Applied at every legal touchpoint
Audit detail
Everything around the signature
Each signature captures when it happened and from where — the ECT Act audit detail that turns a click into a defensible act.
Time and origin captured
Aligned to the ECT Act 25 of 2002
Held with the signed record
05

Evidence from the field

Site photographs are captured with the time and location sealed into the image at the moment it’s taken — a photo that can say where and when, not just what.

Sealed capture
Where and when, built in
Photographs carry an embedded watermark with time and location applied at capture — not added later, not editable after.
Time and location at capture
Embedded watermark
Nothing applied after the fact
In context
Attached where it belongs
Field evidence attaches to the record it supports — the permit, the incident, the inspection — and stays there.
Attached to the source record
Preserved in context
Part of the exportable evidence
06

The labour ledger

Hours and labour records are written once and cannot be edited afterwards — each day’s record is closed and anchored. When a labour dispute reaches the CCMA, the record was kept before the dispute existed.

Immutable
Written once
Ledger entries cannot be modified after they are written — corrections are new entries, and the original stays visible.
No edits after writing
Corrections are additive
The original always survives
Anchored days
Closed and sealed daily
Each day’s ledger closes as a sealed record — the working record of hours and conditions, sealed day by day.
Day-close anchoring
Sealed as it accrues
Kept before any dispute exists
07

Outputs your insurer takes seriously

The same architecture produces the documents that move premiums and settle audits — risk profiles, performance certificates and monthly health reports, all computed from live records.

Risk profile
The underwriter’s document
A structured risk profile — compliance state, incident rates, training coverage, contractor compliance — computed from the live system, not compiled by hand.
Computed from live records
Incident and training metrics included
Renewal-ready on demand
Certificates & reports
Proof on a schedule
Compliance performance certificates and an automated monthly health report — verifiable outputs, produced by the system itself.
Verifiable performance certificate
Automated monthly health report
No month-end assembly
More on insurer & auditor views →

Build your record before you need it

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 →