How does SiteGuard support the 5-why methodology?

SiteGuard does not enforce a specific RCA methodology, but its Corrective Action Programs module supports the 5-why output through the correction type field. Each why-answer typically corresponds to a different correction type, and a single CAP can include multiple correction types with different responsible users. The closure certificate for each sub-action documents the specific corrective action taken, which is the artifact the auditor reviews.

Can a single Corrective Action Program include multiple correction types?

Yes. A CAP can include immediate fix, training, procedure change, equipment replacement, and management system change as separate correction types within the same program. Each correction type is assigned to a different responsible user, with its own due date and closure certificate. The CAP does not close until all sub-actions close, which enforces the discipline that prevents symptom-only closure.

Who can sign a closure certificate?

Closure certificates are signed by the reviewer configured on the Corrective Action Program — typically the HSE manager or a senior safety officer. The reviewer is a named individual, not a role, so the audit trail identifies who approved the closure. This satisfies ISO 45001 clause 10.2's requirement for documented information about who verified the corrective action's effectiveness.

How do I know if my CAPA program is working?

SiteGuard's Recent Violations and Visit History trend views surface the leading indicator: if the same violation type reappears on the same site within a quarter, the CAPA did not address the root cause. A working CAPA program shows declining repeat-violation rates over time, which is exactly the trend the HSE director should report in the quarterly management review under ISO 45001 clause 9.3.

Can SiteGuard handle process safety management (PSM) corrective actions?

Yes. PSM corrective actions typically require more extensive RCA (e.g., fishbone diagrams, fault tree analysis) than the 5-why methodology, but the closure workflow is the same: Corrective Action Programs with types, Assigned Actions with responsible users, and closure certificates. SiteGuard supports the closure workflow; the RCA itself can be documented as an attachment to the CAP, with the corrective actions operationalised through the standard SiteGuard features.

Root Cause Analysis & Corrective Actions in EHS

Most CAPA programs fail for a single reason: they treat the symptom, not the root cause. A worker is observed without a harness, the supervisor issues a harness, the violation closes, and the same hazard reappears a week later because the underlying issue — inadequate training, a missing anchor point, a sub-contractor crew that did not receive the toolbox talk — was never addressed. SiteGuard's Corrective Action Programs were designed to break this cycle by enforcing the discipline that distinguishes a working CAPA program from a paperwork exercise: structured root cause analysis, defined correction types, tracked responsible users, and issued closure certificates. This guide walks HSE managers and safety officers through the 5-why methodology, how SiteGuard operationalises it, and a real-world example from a NEOM construction site where a single fall-protection violation triggered a CAPA that closed only after three corrective actions, two training sessions, and one procedure change.

Why most CAPA programs fail #

CAPA programs fail in five recurring patterns. First, they confuse the symptom with the cause — a worker not wearing a harness is a symptom, not a cause. Second, they stop at the first plausible answer — the worker forgot is plausible but not the root cause. Third, they assign the corrective action to the wrong owner — the worker who forgot cannot fix a training gap, only the training manager can. Fourth, they have no closure certificate — without a certificate, there is no artifact the auditor can verify. Fifth, they treat each violation in isolation, missing the systemic pattern that would surface if the HSE team analysed a month of violations together. SiteGuard's Corrective Action Programs were designed to break all five patterns, by enforcing a structured closure workflow with named reviewers and issued certificates, and by linking each CAP bidirectionally to its originating violation so systemic patterns become visible in Recent Violations trend views.

The 5-why methodology — finding the root cause #

The 5-why methodology is the simplest and most effective root cause analysis technique for field safety. It works by asking why five times in sequence, with each answer becoming the premise for the next question, until the root cause emerges. The methodology was developed at Toyota and has been adopted across process safety, healthcare, and construction. The example below shows a 5-why analysis for a fall-protection violation on a NEOM construction site, where a worker was observed working at height without a harness. The key insight is that the corrective action at why-1 (issue a harness) is different from the corrective action at why-5 (revise the permit-to-work procedure), and only the why-5 action prevents recurrence. A CAPA program that stops at why-1 will close the symptom but not the cause, which is the failure mode that distinguishes paperwork from a working safety system.

Corrective Action Programs with types — operationalising RCA #

SiteGuard's Corrective Action Programs operationalise the 5-why output through the correction type field. The CAP module supports multiple correction types: immediate fix (issue a harness), training (retrain the worker and the crew), procedure change (revise the permit-to-work procedure to require storekeeper sign-off), equipment replacement (replace a malfunctioning gas detector), and management system change (update the site manning plan template). For the NEOM fall-protection example above, the CAP would include three correction types — an immediate fix, a training session, and a procedure change — each assigned to a different responsible user, each with its own due date, and each closed with its own certificate. The CAP does not close until all three sub-actions close, which is the discipline that prevents the symptom-only closure that fails most CAPA programs.

Certificates enforce closure #

The closure certificate is the single feature that most distinguishes a working CAPA program from a paperwork exercise. SiteGuard issues a certificate only when the assigned action is approved by the reviewer, and the certificate records: the corrective action taken, the responsible user, the reviewer, the closure date, and the originating violation. The certificate is stored against the Worker Compliance record of the responsible user, so the worker's safety profile reflects the corrective actions they have completed. For training-type CAPs, the certificate is also the training record, satisfying ISO 45001 clause 7.2 (competence). Without the certificate, the violation is, in auditor terms, still open — which is exactly why legacy EHS systems that treat closure as a status field rather than an issued artifact fail clause 10.2 audits. The certificate is the artifact that converts a logged incident into a closed incident.

A NEOM site example — from violation to certificate #

Consider a real-world scenario from a NEOM construction site. On a Tuesday morning, an inspector observes a worker at height without a harness, logs a Violation Reporting record with Photo Evidence and priority critical, and pushes it to Recent Violations. The HSE manager reviews the violation within the hour, creates a Corrective Action Program with three correction types (immediate fix, training, procedure change), and assigns three Assigned Actions: one to the site supervisor (issue a harness and verify all crew harnesses), one to the training manager (retrain the crew on fall protection), and one to the HSE director (revise the permit-to-work procedure). The site supervisor closes the immediate fix on Tuesday afternoon, with Photo Evidence of the worker wearing the harness. The training manager closes the training action on Thursday, with attendance records attached. The HSE director closes the procedure change on Monday of the following week, with the revised procedure document attached. Each closure issues a certificate, stored against the responsible user's Worker Compliance record. The originating violation moves to Closed only when all three certificates are issued. The full audit trail — violation, CAP, three assigned actions, three certificates, three Worker Compliance updates — is bidirectionally linked and retrievable in seconds.

Common root-cause categories in GCC construction #

Across NEOM, Red Sea, and Diriyah mega-project sites, the root causes of safety nonconformities cluster into five recurring categories. Recognising these categories accelerates the 5-why analysis and helps the HSE team design Corrective Action Programs that address the systemic pattern rather than the individual symptom. The five categories below cover roughly 80 percent of the root causes observed in GCC construction safety audits over the past three years. A HSE team that patterns its CAPA program around these categories will close more violations with fewer corrective actions, because each CAP addresses a category rather than a single incident.