Most EHS platforms treat a worker as a row in a payroll export or a name typed into a checklist. SiteGuard takes a different stance: every field worker in the platform has a Safety Profile, a first-class identity object that aggregates their code, registration date, active safety status, certification history, violation history, and assigned corrective actions into a single record the worker can open in SiteGuard Field and a safety officer can govern in SiteGuard Manager. The Safety Profile is not a cosmetic "user card" — it is the per-worker compliance ledger that ties together the Certificates module, the Worker Compliance module, the Recent Violations module, the Corrective Action Programs module, and the Assigned Actions module. When a Saudi Civil Defense inspector asks to see the safety record of a specific electrician working on a NEOM substation, the safety officer does not assemble documents from five systems; they open the Safety Profile and the entire per-worker evidence trail is on one screen. This article walks through how the Safety Profile is structured, what it binds together, and why it is the backbone of ISO 45001:2018 clauses 7.2 and 9.1.1 in any GCC field safety operation.
What the Safety Profile actually is #
The Safety Profile is the field-worker identity record inside SiteGuard. On SiteGuard Field, every worker opens the app and sees their own profile with a code, a registration date, and a current safety status — typically active, suspended, or expired. The status is not manually edited; it is derived from the worker's current certificates, open violations, and assigned corrective actions. A worker whose fall-protection certificate expired yesterday is automatically flagged expired; a worker with two open high-priority violations may be flagged suspended. This derivation is what turns the Safety Profile from a static card into a living compliance surface. On SiteGuard Manager, the safety officer sees the same profile with the full history layered on — every certificate issued, every violation reported, every corrective action assigned, every visit completed. The profile is the lens through which a safety officer reads the safety story of one worker across their entire tenure on the platform, regardless of which site they were on or which plan they executed.
Certification history: Certificates, Certificate Types, Worker Compliance #
A worker's certification history is not a folder of PDFs; it is a structured timeline the Safety Profile renders natively. On the manager side, Certificate Types configures the categories your organisation recognises — fall protection, confined-space entry, hot-work permit, scaffolding erection, forklift operation, NEBOSH IGC, Aramco HSE induction — with expiry filters per type. Worker Compliance is the workflow that issues those certificates to specific workers and manages their active versus expired status. When a certificate is issued, it appears on the worker's Safety Profile in SiteGuard Field with start date, expiry date, and status, and the worker can open it to verify the issuing authority and the certificate number. The safety officer can filter the entire workforce by which workers have which certificates expiring in the next 30 days, which is the operational view a Civil Defense inspector expects to see during an unannounced audit. For an oil and gas contractor running 1,200 workers across six sites, this is the difference between an audit that takes 20 minutes and one that takes three days of scrambling through folders.
Violation history: Recent Violations and Violation Closure #
The Safety Profile also binds the worker's violation history. When an inspector on SiteGuard Field logs a violation through Violation Reporting — capturing type, priority, photo evidence, and the forfeit amount — the violation is linked to the responsible worker's Safety Profile. Recent Violations on the field app shows the worker the violations logged in the current month against them, so the worker has full visibility rather than learning about a violation days later from a supervisor. On the manager side, Violation Closure drives each violation through a status workflow — open, under review, corrective action assigned, closed — and the Safety Profile shows the full history including the closure status and the corrective action that resolved it. This transforms the violation record from a punitive note into a learning record. A worker who has been cited three times for missing PPE on three different sites sees that pattern on their profile; a safety officer reviewing the workforce can identify the workers who need targeted coaching rather than blanket retraining. For a Saudi contractor bidding on a Red Sea mega-project, being able to show the client that violation history is tracked per worker — and closed per worker — is a procurement-grade evidence point that most competing EHS platforms cannot produce from a single screen.
Training records via Corrective Action Programs and Assigned Actions #
Training records in legacy EHS tools are usually a separate spreadsheet the safety officer maintains by hand. SiteGuard treats training as a workflowed outcome of corrective action. When a worker is cited for a fall-protection violation, Corrective Action Programs defines the correction program with the type of training required and the certificate that will be issued on completion. Assigned Actions then assigns that program to the specific worker with a tracked closure status — assigned, in-progress, completed, certificate issued. The Safety Profile renders this entire flow as a training timeline: the worker sees the assigned corrective program, the due date, the assigned trainer, and the certificate that will be issued on completion. The safety officer sees which workers have outstanding corrective actions, which are overdue, and which certificates have been issued through corrective programs in the last quarter. For an Aramco contractor where the HSE Code requires documented retraining after every fall-protection violation, this is the difference between a defensible training record and a spreadsheet that falls apart under audit scrutiny. The training record is not separate data; it is the natural output of the violation-to-certificate closed loop, rendered on the Safety Profile.
The audit value: ISO 45001 clauses 7.2 and 9.1.1 #
ISO 45001:2018 clause 7.2 requires organisations to determine the necessary competence of workers, ensure they are competent on the basis of education, training, or experience, and retain documented information as evidence of that competence. Clause 9.1.1 requires organisations to monitor and measure what is relevant to the OH&S management system and retain documented information as evidence. The Safety Profile is the surface where both clauses collapse into a single record. For any worker, the safety officer can produce the certification history that satisfies clause 7.2 (competence evidence) and the violation-and-corrective-action history that satisfies clause 9.1.1 (monitoring evidence) from one screen. When the auditor asks to verify that worker number 427 — an electrician on the Diriyah project — was competent to work at height last Tuesday, the safety officer opens the Safety Profile, filters to that date, and shows the active fall-protection certificate, the prior violation history, the corrective program completed, and the GPS-stamped visits on which the worker performed work at height. That is audit-grade evidence in under a minute. Mainstream EHS suites can produce this evidence by stitching together training management, incident management, and competency matrices across three modules and a custom report — which works but takes hours per worker and is exactly the friction ISO 45001 audits are designed to surface.
How the worker experiences the Safety Profile in SiteGuard Field #
The worker experience of the Safety Profile is the part most legacy EHS platforms get wrong. In SiteGuard Field, the worker opens the app and the Safety Profile is one tap away — code, registration date, current safety status, active certificates, recent violations, and any assigned corrective actions. There is no hunting through menus, no logging into a separate training portal, no asking a supervisor to look up a record. When the worker needs to show their fall-protection certificate to a Civil Defense inspector at the site gate, they open the profile and the certificate is on the screen with the issuing authority, the certificate number, and the validity window. When the worker is assigned a corrective program after a violation, the program appears on the Safety Profile with the due date and the assigned trainer — the worker does not need to chase a supervisor to find out what retraining they owe. Notifications push profile changes to the worker: a new certificate issued, a corrective action assigned, a violation closed. The Safety Profile becomes the worker's personal compliance surface, which is what drives adoption: the worker uses SiteGuard Field not because the safety officer mandated it, but because the worker's own safety record lives there and is useful to the worker in real situations, not just to the safety officer in audit season.
How Safety Profile fits the rest of SiteGuard #
The Safety Profile is not a standalone feature; it is the convergence point of half the SiteGuard feature set. Certificates and Certificate Types and Worker Compliance feed the certification history. Violation Reporting and Recent Violations and Violation Closure feed the violation history. Corrective Action Programs and Assigned Actions feed the training timeline. Vehicle surfaces the worker's assigned vehicle and license validity on the same profile, which matters for drivers and inspectors. GPS Check-in stamps every visit the worker completes against their profile, so Visit History renders the worker's actual site presence over time. Compliance Reporting rolls the per-worker evidence into a regulator-ready export that filters by worker, by site, by date, or by certificate type. Users & Roles and Company Scope ensure the profile runs within the right legal entity and role boundaries, which matters for holdings operating across multiple subsidiaries. Platform Settings configures the certificate and violation types that the profile renders. The Safety Profile is the lens; the other features are the data sources that make the lens worth looking through. For a safety officer running a 1,500-worker operation across a NEOM package, this convergence is what makes per-worker safety governance tractable rather than aspirational.