Most EHS platforms track training as a course completion log — the worker attended the course, the trainer signed off, the record is filed. What is missing from this picture is the certificate. A training record says "the worker attended the course"; a certificate says "the worker is authorised to perform this work until this date". The distinction matters because authorisation has an expiry, and expiry drives compliance — a worker whose fall-protection certificate expired yesterday is not authorised to work at height today, regardless of how many courses they attended in the past. SiteGuard treats certifications as first-class worker objects through two paired features: 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, and Worker Compliance is the workflow that issues those certificates to specific workers and manages their active versus expired status. The two features together produce per-worker certification tracking, expiry alerts, and compliance scoring that mainstream EHS suites and leading inspection apps cannot match — and that satisfies ISO 45001:2018 clause 7.2 (competence) evidence requirements. This article explains why the Certificate Types plus Worker Compliance pair is unique to SiteGuard, what competitors do instead, and why it matters for per-worker audit defense.
What Certificate Types and Worker Compliance actually do #
Certificate Types is the manager-side configuration feature in SiteGuard Manager. The safety officer configures the certificate categories the organisation recognises, with an expiry window per type — fall protection valid for 12 months, confined-space entry valid for 24 months, hot-work permit valid for 6 months, NEBOSH IGC valid for 5 years, Aramco HSE induction valid for 12 months. The expiry filter per type drives the proactive renewal queue — Worker Compliance surfaces workers whose certificates are expiring in the next 30 days, so the safety officer can schedule retraining before expiry becomes a compliance failure. Worker Compliance is the workflow that issues certificates to specific workers and manages their active versus expired status. When a worker completes a training course, the safety officer issues the certificate through Worker Compliance with a start date, an expiry date, and a status. The certificate appears on the worker's Safety Profile in SiteGuard Field, so the worker can show it to a Civil Defense inspector at the site gate. When the certificate expires, Worker Compliance automatically flags it expired, and the worker's overall safety status is derived accordingly — active, suspended, or expired. The two features together produce a per-worker compliance ledger that is always current, always queryable, and always exportable through Compliance Reporting.
What mainstream EHS suites and leading inspection apps do instead #
Mainstream EHS suites track training as a course completion log through a Training Management module. The record says the worker attended the course, the trainer signed off, the date is recorded. The certificate is treated as a PDF attachment to the training record, not as a first-class worker object with an expiry window that drives compliance status. Expiry alerts, where they exist, are configured manually per course — the safety officer sets a reminder 30 days before the certificate expiry, but the reminder is a notification, not a workflow that issues a new certificate on completion of retraining. The result is that the per-worker compliance ledger is assembled manually from training records, certificate PDFs, and a separate expiry-tracking spreadsheet — which is exactly where the audit failures actually happen. Leading inspection apps do not ship a training or certification module at all — the inspector is a name on a checklist, with no per-worker compliance surface behind the name. The structural gap is that competitors treat training as attendance and certificates as attachments, while SiteGuard treats certificates as first-class worker objects with expiry-driven compliance status — which is why SiteGuard is the only platform that produces a per-worker compliance ledger that is always current and always exportable.
Why this matters for ISO 45001 clause 7.2 and Civil Defense audits #
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. The SiteGuard Certificate Types plus Worker Compliance pair produces that documented information natively — for any worker, the safety officer can produce a certificate inventory filtered by certificate type, by expiry status, by site, or by date range, all from the Compliance Reporting surface. For an auditor sampling five workers during a stage-2 audit, the per-worker certificate inventory is the difference between a five-minute evidence walk and a two-day document scramble. For a Saudi Civil Defense inspector arriving unannounced at a construction site, the safety officer opens the per-worker compliance ledger and shows the inspector exactly which workers hold which certificates, which certificates are active, and which are expiring in the next 30 days — the inspector sees a current compliance surface, not a folder of training records. For an Aramco contractor where the Aramco code requires specific certifications for specific roles — fall protection for anyone working at height, confined-space entry for anyone entering a confined space, hot-work permit for anyone performing hot work — the per-worker compliance ledger is the difference between a contractor that can prove role-based certification coverage and one that cannot.
How compliance status drives field behaviour #
The compliance status derived from the certificate inventory is not a passive label — it drives field behaviour through the SiteGuard Field app. A worker whose overall safety status is expired cannot be assigned to a Daily Plan that requires the expired certificate; the plan assignment respects the compliance status and surfaces the worker as ineligible. A worker whose status is suspended cannot check in with GPS Check-in for plans that require the suspended certificate. A worker whose status is active sees the certificate on their Safety Profile and can show it to a Civil Defense inspector at the site gate. The compliance status therefore closes the loop between the manager-side Worker Compliance workflow and the field-side execution — the safety officer issues a certificate, the worker's status changes from expired to active, and the worker becomes eligible for plan assignments that require that certificate. Mainstream EHS suites treat the certificate as a PDF attachment that the safety officer checks manually before assigning work, which is exactly where the manual check fails and an uncertified worker gets assigned to a task that requires certification. The automatic derivation of compliance status from the certificate inventory is what makes SiteGuard worker compliance tracking not just a ledger but an operational enforcement mechanism.
How the certificate pair fits the rest of SiteGuard #
Certificate Types and Worker Compliance do not run in isolation; they integrate with the rest of SiteGuard through the Safety Profile. The Safety Profile is the field-side surface that renders every worker's certification history, violation history, and assigned corrective actions on one record. Certificates displays issued certificates on SiteGuard Field with start date, expiry date, and status, so the worker can show them to a Civil Defense inspector at the site gate. The worker's overall safety status — active, suspended, expired — is derived from the certificate states, so a worker whose fall-protection certificate expired yesterday is automatically flagged expired without manual editing. Violation Reporting and Recent Violations and Violation Closure feed the violation history on the Safety Profile. Corrective Action Programs and Assigned Actions feed the training timeline — when a worker is cited for a violation, the corrective program defines the training required and the certificate that will be issued on completion, so the certificate is the natural output of the corrective action. Compliance Reporting rolls the per-worker certificate inventory into a regulator-ready export filtered by entity, by site, by date range, or by certificate type. Company Scope ensures the certificate inventory runs within the right legal entity for multi-subsidiary holdings. The certificate pair is one node in the broader SiteGuard workflow — but it is the node that makes SiteGuard the only platform with a per-worker compliance ledger that is always current and always exportable.