How to Build a Safety Decision Rights Matrix in 30 Days

A safety decision rights matrix defines who can approve, pause, escalate, accept, and restart high-risk work. It turns vague accountability into named authority for supervisors, EHS, operations, maintenance, contractors, and executives when risk changes in the field.

Many organizations say that safety is everyone's responsibility, then leave the hardest decisions to the person with the least power at the worst moment. A mechanic sees a missing isolation point. A contractor notices that the scope has changed. A supervisor feels pressure to restart because the line is late. Without clear decision rights, the safest choice becomes a negotiation.

The stronger thesis is that accountability is not created by a slogan. It is created by visible authority, escalation thresholds, restart rules, and consequences for bypassing the agreed path. Across 25+ years in executive EHS roles, Andreza Araujo has seen that serious events often grow in the gray zone between what the procedure says and who is allowed to decide when reality changes.

What you need before starting

Before building the matrix, collect your critical-risk register, permit-to-work procedure, management-of-change rules, contractor interface process, incident investigations, near-miss records, and the last three months of delayed or disputed work decisions. ISO 45001:2018 supports this work because it requires roles, responsibilities, accountabilities, and authorities to be assigned, communicated, and understood.

Do not start with a generic RACI template. A RACI chart can help with project governance, but field safety needs decision rights that answer operational questions under pressure. Who can stop a lift? Who can accept a temporary barrier? Who can restart after an alarm? Who must escalate when the control owner is absent?

Andreza Araujo's book A Ilusao da Conformidade, glossed as The Illusion of Compliance, is useful here because a signed procedure can hide weak authority. A site may have every responsibility written somewhere and still leave the supervisor alone when production, maintenance, and a contractor disagree at the job front.

Step 1: List the decisions that actually create exposure

Start by listing decisions, not job titles. The matrix should cover approval to start high-risk work, authority to pause a task, escalation of changed conditions, acceptance of temporary controls, restart after interruption, handover between shifts, contractor release, and closure of corrective actions tied to critical controls.

The test is whether the list includes moments where a wrong decision could place someone in the line of fire, release energy, weaken isolation, hide a serious precursor, or normalize work outside the planned control set. If the matrix only says who owns the procedure, it will not help the field when conditions change.

Use recent evidence. Pull three permits, two near misses, one maintenance delay, and one contractor dispute, then ask which decision was unclear. This prevents the matrix from becoming a governance artifact with no contact with work.

Step 2: Separate technical authority from managerial authority

Some decisions require technical competence. Others require managerial accountability. The same person may hold both, but the matrix should not assume that a senior title is enough to approve a technical risk decision.

For example, a plant manager may own the business consequence of an extended shutdown, while an electrical authorized person owns the decision that isolation is verified. A maintenance manager may coordinate the work, while EHS challenges whether the temporary control is acceptable for the exposure. Confusing these authorities invites quiet pressure and weak approvals.

James Reason's work on latent conditions helps explain the risk. The visible error may happen at the task, although the deeper weakness was an authority system that allowed a commercial or schedule decision to override the person who understood the hazard.

Step 3: Define four authority levels for each decision

Use four practical levels. The first is field authority, held by the worker, contractor, operator, or supervisor who can pause work when a control is missing or uncertain. The second is technical authority, held by the competent person who can judge whether the control is valid.

The third is management authority, held by the line leader who owns resources, schedule, and operational coordination. The fourth is executive authority, used when the decision affects critical risk appetite, major production loss, cross-site precedent, or acceptance of residual risk above the local threshold.

The matrix should show these levels in plain language. If the crew cannot tell the difference between who may pause, who may approve, who may escalate, and who may restart, the authority levels are still too abstract.

Step 4: Build escalation triggers before conflict appears

Escalation should not depend on personal courage or the supervisor's mood. Write specific triggers that force the decision to move up a level. Common triggers include changed scope, missing isolation evidence, unavailable competent person, repeated alarm, overdue corrective action, contractor disagreement, temporary control request, or any condition linked to a serious injury or fatality precursor.

The article on field risk escalation matrices gives a useful companion method because escalation only works when thresholds are named before the shift starts. The decision rights matrix defines who decides. The escalation matrix defines when the decision must leave the local level.

Verification is simple. Give a supervisor a realistic scenario and ask where the decision goes. If two supervisors give two different answers, the trigger is still written as opinion rather than rule.

Step 5: Connect the matrix to permits, MOC, and restart rules

A decision rights matrix fails when it sits outside the systems where decisions happen. Link it directly to permit approval, shift handover, management of change, pre-startup safety review, LOTO handback, contractor release, and restart after interruption.

The related comparison of MOC, PTW, and PSSR matters because different controls answer different questions. Permit-to-work authorizes a defined task. Management of change handles altered conditions. PSSR verifies readiness before startup. The matrix should prevent leaders from using the wrong forum because it is faster.

As Andreza Araujo argues in Safety Culture: From Theory to Practice, culture appears in what leaders reinforce and tolerate. If restart authority is unclear, the organization may reward the person who gets work moving, even when the control basis has changed.

Step 6: Name deputies and absence rules

Many safety decisions break down when the named authority is absent. The matrix should name deputies for each authority level and define which decisions cannot be delegated without documented competence.

Absence rules are not administrative detail. They protect the system from informal substitution. If the permit issuer is unavailable, who can issue the permit? If the competent electrical person is on another site, who can verify isolation? If the contractor manager is absent, who can accept the restart condition on behalf of that crew?

In more than 250 cultural transformation projects supported by Andreza Araujo's team, a recurring weakness is that organizations design authority for normal days and then improvise on abnormal days. The matrix should be written for the day when the usual person is unavailable, production is late, and the job still has to be decided.

Step 7: Create a one-page field version

The full matrix may live in a procedure, but the field version should fit on one page. Use rows for decision moments and columns for field authority, technical authority, management authority, executive authority, evidence required, and restart condition.

Keep the language operational. Replace "accountable stakeholder" with the job role that the crew recognizes. Replace "consult EHS as needed" with the exact trigger that requires EHS review. Replace "management approval" with the position or on-call role that can decide during nights and weekends.

The one-page version should be tested during a pre-job brief. Ask the crew to point to the line that applies to their work. If they cannot find the decision in thirty seconds, the field version is designed for document control rather than work control.

Step 8: Audit decisions, not only documents

The first audit should follow real decisions from the field to closure. Select one paused job, one permit change, one temporary control, one contractor interface, and one restart after interruption. For each case, ask whether the right authority decided, whether the evidence was adequate, whether escalation happened at the defined threshold, and whether the restart condition was met.

Use the audit to improve the matrix. If supervisors bypass escalation because it takes too long, the problem may be response time, not attitude. If managers approve temporary controls without technical review, the matrix has failed at the boundary between authority and competence.

The article on risk acceptance and decision authority is relevant because residual risk should never be accepted by the person who merely wants the job finished. The person who owns the risk must also own the evidence and the consequence.

Final checklist for the 30-day build

• The matrix lists decision moments, not only departments or job titles.
• Technical authority and managerial authority are separated where the risk requires it.
• Field, technical, management, and executive authority levels are visible in the same table.
• Escalation triggers are based on changed conditions, missing controls, uncertainty, and SIF precursors.
• Permit, MOC, PSSR, handover, contractor, and restart routines all point back to the matrix.
• Deputies and absence rules are named before the usual authority is unavailable.
• The field version can be used during a pre-job brief without interpretation by EHS.
• Audits follow real decisions and test whether authority matched evidence.

A safety decision rights matrix is not bureaucracy. It is the difference between a worker hoping the right person listens and a system that already knows who must decide when controls are uncertain.

Visit andrezaaraujo.com to explore Andreza Araujo's books, diagnostics, and corporate programs for companies that need safety leadership to work where risk decisions are made.