What is a RACI Matrix?

A RACI matrix is a table that shows who plays which role on each piece of work in a project. Deliverables run down the rows, people or roles run across the columns, and each cell holds one of four letters: Responsible, Accountable, Consulted or Informed. Its job is to settle, before the work starts, who does the work, who owns the result, who must be asked and who only needs to hear about it.

It is also called a responsibility assignment matrix (RAM) or a RACI chart. Its roots are usually traced to the linear responsibility charts used in project management from the 1950s onward. The format has lasted because the problem it solves never goes away: as soon as work crosses a team boundary, everyone assumes someone else has it.

This guide explains the four roles, walks through a complete worked example for a real-world style project, and shows the row and column checks that catch problems before they become missed deadlines.

The four RACI roles

Two distinctions cause most of the confusion:

• Responsible vs. Accountable. The Responsible person does the work; the Accountable person answers for whether it was done right. On small teams they are often the same person, written as A/R. What matters is that someone is named for both.
• Consulted vs. Informed. Consulted people can change the work, so they slow it down. Informed people cannot, so they cost nothing but an update. Every C you add is a meeting or a review someone has to wait for.

A worked RACI matrix example

Here is a RACI for a fictional company moving its sales team from one CRM to another. The project touches sales, operations, data, security and finance, which is exactly the kind of work where ownership gets lost.

Read it row by row and every deliverable has one owner. Read it column by column and you can see each person's load at a glance: the RevOps Lead is accountable for five of the eight rows, which is a conversation worth having before the project starts, not halfway through.

What the first draft got wrong

This matrix did not start out this clean. The first draft had three problems that are common in almost every RACI:

1. The VP Sales was accountable for everything. It felt safe to put the most senior person in every A cell, but it made one person the bottleneck for eight sign-offs. Pushing each A down to the person who could actually judge the work removed the queue.
2. The cutover had two A's. The RevOps Lead and the Data Engineer both thought they were running the weekend. The fix was to make RevOps accountable and the Data Engineer responsible, so one person makes the call if something breaks at 2 a.m.
3. Support was consulted on every row. Nobody wanted to leave them out, but a C on every row means every deliverable waits for Support. In the final version Support is consulted on the requirements and informed about the rest.

How to check a RACI matrix

A RACI is only as good as the checks you run on it. Run these two passes before you share it.

Row checks (one deliverable at a time):

• Exactly one A. None means nobody owns it; two means nobody does.
• At least one R. An A with no R means the owner has to do the work, which is fine only if that was the plan.
• No more C's than you need. Ask: if we don't consult this person, what specific risk are we taking? If there is no answer, make them an I.
• No empty rows. A deliverable nobody touches should not be on the matrix.

Column checks (one person at a time):

• Too many A's or R's means that person is overloaded, or is a bottleneck in disguise.
• No A's or R's at all is a question: should this person be on the matrix, or just on the update email?
• A full column with no blanks usually means the role was added out of politeness, not need.

How to build one in a 45-minute meeting

1. Before the meeting: list 8 to 12 deliverables, not tasks. "Run the cutover weekend" is a deliverable; "send the cutover email" is a task. Add one column per role, with a named person for each.
2. First 5 minutes: define the four letters out loud, especially the difference between R and A.
3. Next 20 minutes: go row by row. Assign the A first, then the R's, then the C's, then the I's. Do not move on from a row with two A's.
4. Next 10 minutes: run the column checks and rebalance anyone who is overloaded.
5. Last 10 minutes: agree where the matrix will live (the project tool, not a shared drive) and when you will review it.

For the facilitation side, including how to handle the politics when two leads both want the A, see how to facilitate a RACI matrix session.

RACI variants

The four letters are not the only option. A few variants add roles for specific situations:

• RASCI adds Support: people who help the Responsible person but do not own any part of the work.
• RACI-VS adds Verifier, who checks the work meets its criteria, and Signatory, who formally approves it. It suits regulated work.
• CAIRO adds Out of the loop, to state explicitly who is not involved.
• DACI and RAPID are not variants so much as different tools. They assign roles for a single decision rather than for ongoing work. We compare them in RACI vs. DACI vs. RAPID.

When to use a RACI matrix, and when not to

A RACI is most useful at a project kickoff, during a reorganization, when someone new joins a cross-functional team, or when the same kind of work keeps falling between two teams.

It is the wrong tool when:

• You need to make one contested decision. Who decides which vendor to pick is a DACI or RAPID question, not a RACI one.
• The team is small and stable. Three people who sit together rarely need a matrix to know who owns what.
• The disagreement is about priorities, not roles. If two teams disagree about what matters most, a matrix will not settle it. Start with a SWOT analysis or an honest conversation about the goal.

When the matrix is not the problem

Often the matrix is the easy part. The hard part is the conversation that comes before it, when two leads both believe they own the cutover, or nobody wants the A on the risky deliverable. A spreadsheet does not resolve that; people talking it through does.

If that is where your team is stuck, you can talk ownership through live with Medi, our AI facilitator. Medi runs the cross-functional discussion out loud and writes down the owner, the risks and the next steps before anyone leaves.

Free RACI matrix template

The free RACI matrix template comes as a PDF, Word document, Excel workbook and PowerPoint deck, with the four roles defined at the top and rows ready for your deliverables.

Frequently asked questions

Ready to put this into practice? Run it with your team using the free RACI matrix template.