Step 1: choose processes, not people
The matrix is built from processes, not from names. For this page we assume three: entry of visitors and contractors, permits for dangerous work and evacuation. Describe each process in one sentence, from the opening event to the closing event, because without boundaries responsibility cannot be assigned.
For the permit process the procedure itself sets the boundaries: a work permit requires the signatures of the right people: the issuer, the approver and the works coordinator, plus verification of employee qualifications. This gives a ready skeleton of roles to enter into the matrix.
Step 2: define the functions involved
The example includes five functions: health and safety, security, IT, HR and purchasing. In your plant maintenance and production managers will likely be added. It is important to use function names, not job titles, because job titles change and functions persist.
InnerWeb works as an independent system that complements the client's existing systems: access control, time and attendance, HR and ERP. The owners of those systems remain in the responsibility matrix, so add them as consulted or informed where the process touches their data.
Sample matrix: number of letters by function
- A (accountable)
- R (responsible)
- C (consulted)
- I (informed)
Step 3: assign letters according to four rules
The letters are R (responsible, does the work), A (accountable, approves), C (consulted before the decision) and I (informed after the decision). Four rules protect the matrix from dissolving: exactly one A in each process, at least one R, C limited to those without whom the decision would be wrong, and I limited to those who actually need the outcome.
An example for three processes and five functions shows how this works in practice. Entry: A and R security, health and safety and HR consulted, IT and purchasing informed. Permits: A and R health and safety, security and purchasing consulted, IT and HR informed. Evacuation: A health and safety, R security, IT consulted, HR and purchasing informed.
- exactly one A in each process,
- at least one R in each process,
- C only where a decision without consultation would be wrong,
- I only where the outcome is needed to do the work.
Step 4: check the matrix against the rules of the system
The matrix cannot assign responsibility the system does not allow to be exercised. Approving or rejecting work that is particularly dangerous is reserved for a user on the plant side, not for the contractor. In the matrix the letter A for such work can therefore only go to a plant function.
The issuer, approver and coordinator fields in a permit are filled in by default according to the team assigned to the location, and can be hidden per location. Align the matrix with this configuration: if the hall team is assigned as approver, the matrix and the settings say the same thing.
Step 5: record what the system does not replace
The system does not replace the works manager or the person authorising the work: it enforces the rules, while responsibility stays with the people named in the process. Put this statement into the document with the matrix, so that the auditor and the employees see that the software is a tool, not an entity that bears responsibility.
It is also good practice to add deputies: who takes over the letter A during the owner's leave. Without this the matrix works only at full staffing.
Step 6: implement, test and review quarterly
Test the matrix with a rehearsal: choose a scenario, for example entry of a contractor without valid training, and walk through it with the people in the matrix, noting who actually reacted. Correct the differences between the matrix and reality right away.
Teams in the system mirror the matrix: they group the people responsible for parts of the plant, and have areas, members, roles in jobs and report categories. A quarterly review of these teams together with the matrix keeps the document and the configuration consistent.
Checklist
Video
Frequently asked questions
Can a RACI matrix have several people with letter A?
No. Exactly one A per process is the basic rule. If responsibility is shared, split the process into two smaller ones.
Does the system replace the people in the matrix?
No. The system enforces the rules, while responsibility stays with the people named in the process.
How do I link the matrix to the system configuration?
Through the teams assigned to locations. By default they fill in the issuer, approver and coordinator fields of a permit.
Let us build the matrix together
We will run a workshop in which, with your functions, a RACI matrix for entry, permits and evacuation is built and linked to the team configuration.
Let's talk