RACI Matrix Template: One Accountable Per Row

How to build a RACI matrix that settles arguments instead of causing them — the four roles, the one-Accountable rule, and the variants worth knowing.

A RACI matrix answers a question that costs projects more time than any technical problem: who decides this?

It is a grid. Rows are deliverables or decisions. Columns are people or roles. Each cell holds an R, an A, a C, an I, or nothing at all — and the empty cells matter as much as the filled ones.

The four roles

Responsible — does the work. Can be shared across several people, and often is.

Accountable — owns the outcome, approves the result, answers for it if it goes wrong. Exactly one per row.

Consulted — asked for input before the decision is made. Two-way: they expect a conversation, not a notification.

Informed — told after the decision. One-way. Nobody waits for their reply.

The distinction that causes the most confusion is Responsible versus Accountable. Responsible builds the migration script; Accountable decides it is good enough to run in production. The same person can hold both, but they are different acts, and separating them is what makes the matrix worth building.

The rule that makes it work

One Accountable per row. Never two.

Two people accountable for the same outcome means that in practice neither is. Each assumes the other has it, or each waits for the other to move, and the decision sits between them until someone escalates. Almost every genuinely useful conversation that comes out of building a RACI matrix is triggered by someone trying to put two A's in a row.

Three further rules earn their keep:

• Every row has an A. A row without one is work that nobody owns.
• Not every row needs an R next to the A — but every row needs at least one somewhere, or the deliverable has no one doing it.
• Be sparing with C. Consulted means you will genuinely wait for their input. Listing six people as Consulted on a decision you intend to make on Friday is a promise you are not going to keep, and it is how RACI matrices lose credibility.

Building one

1. List the deliverables and decisions, not the activities. "Approve cutover plan" is a row. "Attend weekly call" is not. Fifteen to thirty rows covers most projects; if you pass fifty, you are describing tasks rather than accountability.
2. List the roles, not the names — Project Manager, Business Owner, Solution Architect, Service Delivery Manager. Names change during a project; roles do not. Keep a separate small table mapping the current name to each role.
3. Fill in the A column first, one per row. Do this before anything else. It is where the disagreements live, and finding them is the point.
4. Then R, then C, then I.
5. Read it by column. Anyone with an A in half the rows is a bottleneck; anyone with only I's probably does not need to be in the matrix at all.
6. Get it agreed out loud. A RACI nobody discussed is a document, not an agreement. Twenty minutes in a room, walking the A column, is what turns it into something people will honour in month four.

The variants

RASCI adds Supportive — people who actively help the Responsible party without owning the work. Useful in matrix organisations where help is borrowed from other teams and needs to be visible.

RACI-VS adds Verifier and Signatory, separating the person who checks the deliverable against criteria from the person who formally signs. Worth the extra complexity in regulated environments, and overkill outside them.

DACI replaces Responsible with Driver and adds Approver, and is oriented around decisions rather than deliverables. It fits product organisations better than delivery programmes.

Start with plain RACI. Add letters only when you can name the specific confusion the extra letter resolves.

When to build it, and when not to bother

Build it during initiation, before the work starts, and revisit it whenever the team or the scope changes materially — a new vendor, a merged workstream, a replaced sponsor.

Building one mid-crisis to settle an argument rarely works. By then the disagreement is about the outcome rather than the roles, and people will fill in cells to defend a position instead of describing reality. The value of a RACI matrix is almost entirely in the conversation you have while creating it, and that conversation is only honest when nothing is yet at stake.