InnerWeb
Skip to main content

RACI matrix in rollout: implementation notes

The RACI matrix sets out who executes, who is accountable, who must be consulted and who must be informed. In a safety system pilot it is best to settle it before the first permits and guest registrations. Below are the order of work, the participants and the pitfalls that most often delay the start.

4
steps for setting up the RACI matrix before the pilot
Source: sample calculation

Why RACI in a pilot

In a pilot of a permit, guest and location system, several departments work at the same time. OHS wants to issue permits faster, security needs a simple gate, IT looks after accounts and integrations, and HR wants employee data up to date. Without an agreed matrix, everyone assumes the task belongs to someone else.

RACI is not a document for its own sake. It should answer several specific questions: who approves teams, who reports new accounts, who is responsible for the integration with access control, and who informs external companies about trainings.

Order of setting up the matrix

We recommend four steps. Each ends with a decision that can be written on one page.

Step 1: list the processes in the pilot scope

List the processes covered by the pilot: issuing permits, guest registration, handling the gate alarm, handling location alerts and assigning roles. The scope must be closed, because every additional process adds a row to the matrix.

Step 2: list the roles on the plant side

Collect the roles that actually take part: issuer, approver, work coordinator, security, secretariat, inviter, administrator, and the owners of the access control, time and attendance and HR systems. The issuer, approver and coordinator of a work permit must sign it and verify employee qualifications, so these roles enter the matrix as mandatory.

Step 3: assign R, A, C, I

For each process assign one accountable person (A) and at least one responsible person (R). Consulted (C) and informed (I) are the rest. Rule: only one A per row. The issuer, approver and coordinator fields are filled in by default according to the team assigned to the location, so the matrix must be consistent with the teams.

Step 4: verify on scenarios

Walk through the matrix on three scenarios: a welding permit, a service technician's visit and a scan of a person without valid training at the gate. In the last case the alarm reaches the coordinator of that person's company, and calls are grouped into one per company within a 55-minute window. Control question: does every participant know what to do, and has anyone been left out?

Sample calculation: matrix rows by process

Sample calculation: matrix rows by processHorizontal bar chart: permit issuing 9 rows, guest registration 7, gate alarm 5, location alerts 6, role assignment 4.0246810rowsPermit issuingPermit issuing: 9 rows9Guest registrationGuest registration: 7 rows7Gate alarmGate alarm: 5 rows5Location alertsLocation alerts: 6 rows6Role assignmentRole assignment: 4 rows4
Source: Sample calculation based on assumptions: five processes in the pilot, on average six activities per process.

Who to set this up with

The workshop should include the process owner, the OHS manager, a security representative, a maintenance representative, the IT department and an HR representative. InnerWeb works as an independent system that complements the client's existing systems (access control, time and attendance, HR, ERP), so the owners of those systems remain in the responsibility matrix as consulted parties or as performers of the integration. It is worth inviting them to the very first meeting.

Roles differ between installations, because the full list of roles depends on configuration. The matrix should therefore rest on the roles actually enabled in the installation, not on a general template.

Common pitfalls

The first pitfall is two A's in one row: two people are accountable for the same process, and in practice neither is. The second is leaving out the owners of external systems, which only surfaces during integration. The third is a matrix that does not match the roles in the system: a person marked as performer does not have the permissions to carry out the activity.

The fourth pitfall is staleness. After the pilot the matrix stops reflecting reality if it is not reviewed. Include it in the quarterly review of roles and teams.

Evidence for audit

The RACI matrix in a plant is usually one of the documents an internal auditor asks for. It provides evidence that responsibility was assigned and known to the participants. It does not, however, replace the person managing the works or the authorizing person: the system enforces rules, and responsibility stays with the people named in the process.

Video

Frequently asked questions

Does the RACI matrix have to cover the whole plant?

No. In a pilot, a matrix for the processes in scope is enough, for example for one hall. It can be extended once the setup has been verified.

Who should be responsible for the integration with access control?

The owner of the access control system on the plant side, or its vendor. InnerWeb integrates with the existing system and does not replace the readers.

How often should the matrix be updated?

Once a quarter, and after organizational changes, the launch of a new hall or a change in a broad-scope role.

Let's set the RACI matrix at the workshop

We will prepare a matrix template for the pilot processes and run the workshop with OHS, security, IT and the owners of the systems.

Let's talk