RACI Matrix: What It Is and How to Make One That Gets Used
A RACI matrix says who does each task, who owns the result, who is asked first and who is told after. Here is how to build one, a template you can copy, worked examples for a small business and the mistakes that make most charts useless.
Most operational problems in a growing business are not about skill. They are about ownership. Two people both think the other one sent the invoice. A client gets three different answers. A decision gets made, then made again by someone who did not know it was settled.
A RACI matrix is the simplest tool for fixing that. It is a table that says, for each task or decision, who does the work, who owns the result, who is asked first and who is told after. It takes an hour to build and it ends a lot of “I thought you had it.”
This guide covers what each letter means, how to build a RACI matrix in six steps, a template you can copy, filled-in examples and the mistakes that make most charts useless.
What a RACI matrix is
A RACI matrix (also called a RACI chart or responsibility assignment matrix) lists tasks down the side and people or roles across the top. Each cell holds one of four letters:
| Letter | Role | What it means | How many per task |
|---|---|---|---|
| R | Responsible | Does the work | One or more |
| A | Accountable | Owns the result, approves it and answers for it | Exactly one |
| C | Consulted | Asked for input before or during the work. Two-way | As few as possible |
| I | Informed | Told about the outcome. One-way | Anyone who needs to know |
The difference that matters most is between R and A. Responsible people do the task. The Accountable person is the one you go to when it was late or wrong. If you can only get one thing right, get one A per row.
The difference between C and I is about timing and direction. A Consulted person is heard before the work is finished and can change it. An Informed person hears after and cannot.
When a RACI matrix helps
You do not need one for every task. It earns its place when:
- Work crosses people. Anything that hands off between sales, delivery and finance, or between an office and a field crew.
- Things fall through gaps. Follow-ups that nobody sends, approvals that nobody gives.
- Decisions get made twice. Or made by someone who should only have been told.
- You are adding a role. A new operations manager, a first hire in finance or a second location changes who owns what.
- You are documenting a process. An SOP that does not say who owns each step leaves the hardest question unanswered.
If a task belongs to one person from start to finish and nobody else touches it, skip the matrix and name the owner in the SOP.
How to make a RACI matrix in six steps
Step 1: Pick one process
Start with one process, not the whole business. Choose one that crosses at least two people and has caused a dropped ball recently. Client onboarding, month-end close, hiring and job scheduling are common first choices.
Step 2: List the tasks and decisions
Write the main tasks in order, starting each with a verb: “Send the welcome email,” “Approve the project budget,” “Schedule the kickoff call.” Aim for 8 to 15 rows. Fewer and the chart hides the handoffs. More and nobody will read it.
If you have already mapped the process, the steps on the map are your rows. Include decisions as their own rows. “Approve the discount” is often where the confusion lives.
Step 3: List the roles
Put roles across the top, not names: “Account manager,” not “Dana.” People change jobs and go on holiday. Roles are what the chart is really about. In a very small business a role and a person may be the same thing for now, which is fine.
Include outside roles if they act on the process, such as a bookkeeper, a client or a contractor.
Step 4: Fill in the A first
Go row by row and decide who is Accountable. Exactly one per row. If two people both feel they own a task, that disagreement is the most useful thing the exercise will surface. Settle it now, out loud.
Then add the R, the person or people who do the work. Then the C and I.
Step 5: Check the rows and the columns
Read across each row and down each column. The patterns tell you what to fix:
| What you see | What it usually means |
|---|---|
| A row with no A | Nobody owns the result. This is where things get dropped |
| A row with two As | Two owners, so in practice nobody owns it |
| A row with no R | The task is approved but nobody does it |
| A row with many Cs | The task will be slow. Move some to I |
| A column full of As and Rs | One person is a bottleneck. Delegate some of it |
| A column with nothing but Is | This role may not need to be on the chart |
| A column with no letters at all | Remove it |
Step 6: Review it with the people on it
Walk the chart with everyone who appears on it. Ask each person to read their own column and say whether it matches what they actually do. Disagreements here are cheaper than disagreements in front of a client.
Then put it where the work happens. A RACI matrix in a forgotten folder changes nothing.
RACI matrix template
Copy this and replace the tasks and roles with your own.
| Task or decision | Role 1 | Role 2 | Role 3 | Role 4 |
|---|---|---|---|---|
| [Verb + object] | A | R | C | I |
| [Verb + object] | A/R | I | ||
| [Verb + object] | C | R | A | |
| [Verb + object] | I | R | A |
Rules to keep next to it:
- One A per row, no exceptions.
- At least one R per row. A/R is fine when the owner also does the work.
- Use roles, not names. Keep a separate list of who holds each role today.
- Date it, and name who owns the chart itself.
RACI matrix examples
The examples below use fictional companies to show how a chart reads once it is filled in.
Client onboarding at a small marketing agency
A fictional six-person agency, Northline Creative, kept missing kickoff calls because sales assumed delivery would book them and delivery assumed sales already had.
| Task | Owner | Account manager | Project lead | Bookkeeper | Client |
|---|---|---|---|---|---|
| Sign the contract | A | R | I | I | R |
| Send the first invoice | I | C | A/R | I | |
| Send the welcome email and intake form | A/R | I | I | ||
| Schedule the kickoff call | A | R | C | ||
| Set up the project and folders | I | A/R | |||
| Run the kickoff call | I | R | A | R | |
| Approve the project plan | C | C | R | A | |
| Send the 30-day check-in | I | A/R | C | I |
The fix was one row: “Schedule the kickoff call” now has a single A and a single R, and the matrix sits at the top of the onboarding SOP.
Month-end close at a fictional home services company
| Task | Owner | Office manager | Bookkeeper | Crew leads |
|---|---|---|---|---|
| Submit job sheets and receipts | I | A | R | |
| Reconcile bank accounts | I | A/R | ||
| Chase unpaid invoices | I | A/R | C | |
| Review the profit and loss report | A | C | R | |
| Approve write-offs | A | C | R | |
| Share the monthly numbers with the team | A/R | I | I |
Reading down the columns shows the owner is accountable for three rows and the office manager for two. That balance is intentional: the owner keeps the money decisions and hands off the chasing.
Common RACI mistakes
- More than one A. Shared ownership sounds collaborative and works like no ownership.
- Everyone is Consulted. It feels inclusive and makes every task wait for a meeting.
- Names instead of roles. The chart is out of date the first time someone leaves.
- Too many rows. A 60-row chart covers everything and gets read by nobody.
- Built once, never updated. New hires, new tools and new services change who owns what. Review the chart when the process changes, and at least once or twice a year.
- A chart with no procedure behind it. RACI says who. It does not say how. Without written steps, the Responsible person still has to ask the Accountable one how the task is done.
RACI, SOPs and process maps work together
The three tools answer different questions:
| Tool | Answers |
|---|---|
| Process map | What happens, in what order, and where the handoffs are |
| RACI matrix | Who does each step, who owns it and who needs to be involved |
| SOP | Exactly how each step is done |
A good order is to map the process, build the RACI for it, then write SOPs for the steps that need them, naming the owner from the A column. When someone asks “who owns this?” or “how do I do this?”, the answer is written down instead of held in one person’s head.
How SOPCompass helps
You can build a RACI matrix in a spreadsheet. Where SOPCompass helps is turning the chart into procedures people can follow and keeping ownership attached to them.
- Write the “how” behind each row. The AI assistant interviews the Responsible person by text or voice and drafts the SOP, or you can record the task once and get the steps with screenshots. Nothing is saved until a person approves it.
- Give every SOP an owner and a review date. Each SOP can have an owner and a review interval, and Insights shows each owner which of their SOPs are due for review or have never been reviewed.
- Map who owns what. The accountability chart under People and roles shows each seat, the person in it and what they answer for.
- Hand the procedure to the person doing the work. Assign an SOP to the Responsible person with a note and a due date, and see when they have completed it.
- Keep the Consulted in the loop on the step itself. Comments on steps let people flag the exact step that needs a change, and version history keeps what was there before.
What it will not do: it does not decide who should own what. That conversation, especially settling a row with two As, is still yours to have.
Where to start today
Pick the process that caused the most recent “I thought you had it.” List its tasks, put the roles across the top and fill in one A per row. Show it to the people on it this week. If the A column surprises anyone, you have found the problem the chart was for.