# RACI matrix example: make the approval decision unambiguous

Build a responsibility matrix around deliverables and decisions, with a worked handover example and checks for missing or conflicting accountability.

Canonical: https://project.responseshift.academy/raci-matrix-example/
Publisher: Response Shift
Updated: 2026-10-31

## Choose decisions before initials

RACI separates doing the work (Responsible), owning the result or decision (Accountable), contributing before the decision (Consulted) and receiving the outcome (Informed). Agree these meanings with your team; organisations sometimes use different variants.

Use a row for an observable deliverable or decision, not a broad phase such as “implementation”. As a practical convention in this example, each row has one accountable role. If two authorities must approve different things, split the decision into two rows and show the sequence.

## Worked example: office-access handover



| Deliverable or decision | Sponsor | Delivery lead | Facilities lead | Installer | Security reviewer |
| --- | --- | --- | --- | --- | --- |
| Approve opening-date change | A | R | C | I | C |
| Install configured readers | I | A | C | R | C |
| Accept facilities handover | I | R | A | C | C |
| Approve security test evidence | I | R | C | C | A |

## Read across and down

Reading across exposes missing ownership and unnecessary consultation. Reading down exposes a person who must approve every task and becomes a bottleneck. Ask the accountable role to confirm the decision and turnaround expected, rather than circulating a matrix and assuming silence means agreement.

Responsible and Accountable can be the same role when that matches authority. A consultant who provides advice does not automatically receive a veto. Where a real regulatory or contractual sign-off is required, represent that decision explicitly instead of hiding it in a C.

## Copyable responsibility worksheet



```text
Decision or accepted deliverable:
Responsible role and task:
Accountable role and authority:
Consulted roles / input required / response deadline:
Informed roles / channel / timing:
Acceptance evidence:
Escalation if the approver is unavailable:
Date roles confirmed:
```

- [Download the template (Markdown)](https://project.responseshift.academy/raci-matrix-example/raci-matrix-template.md)
- [Download the worked example (CSV)](https://project.responseshift.academy/raci-matrix-example/raci-matrix-example.csv)

## Resolve a conflict before drawing the final matrix

Suppose facilities and security both say they own go-live. Ask what each must accept: physical readiness, security evidence or the overall business decision. These may be three separate decisions with a sponsor accountable for the final trade-off.

The matrix does not create authority by itself. Validate it against actual governance, contracts and role agreements. Use it beside the schedule and communication plan so the people needed for a decision are available when it is due.

## Continue

[Project practice week](https://project.responseshift.academy/practice-week/)

- [APM: project controls background](https://www.apm.org.uk/resources/what-is-project-management/what-is-project-controls/)
