Guide
RACI chart: what it is, with a two-person example
A RACI chart is a table that says, for each task, who does it, who answers for it, who is asked first and who is told afterwards. The four letters are Responsible, Accountable, Consulted and Informed. This guide explains each one and builds a chart for a team of two.
Not legal advice. A RACI chart records who does and answers for work inside your team. It does not decide who owns code, equity, money or a domain in law. That depends on your agreements and local law.
What is a RACI chart?
A RACI chart lists tasks down the left side and people across the top. In each cell you put a letter, or leave it empty. The letter tells you what that person has to do with that task.
You will also see it called a RACI matrix, a RACI model or a responsibility assignment matrix. These names point at the same idea: a grid that replaces "I thought you had that" with something anyone can read. If you want a blank grid to copy now, use the RACI matrix template. If you want the wider method, including a second table for accounts, read the responsibility matrix guide for small teams.
My view after reading how the main guides describe it: the letters are easy. The hard part is deciding who gets the A. Most of this page is about that.
What do R, A, C and I stand for?
The definitions below match how the pages listed under Sources describe them. Wording differs a little between sources, but the four roles are the same.
| Letter | Role | In plain words | How many per task |
|---|---|---|---|
| R | Responsible | Does the work | One or more |
| A | Accountable | Signs off on the result and answers for it | Exactly one |
| C | Consulted | Gives input or reviews before the work moves on | Zero or more |
| I | Informed | Is told about progress or the outcome | Zero or more |
Asana describes Responsible as the individual who completes the task and Accountable as the person who signs off on the work and owns the final result. It describes Consulted people as those who provide guidance or review work before it progresses, and Informed people as those who monitor progress and completion. Wikipedia gives matching definitions and notes that, according to some theories of project management, each task or deliverable should have only one accountable stakeholder.
Responsible: who does it
The R is the person with their hands on the task. A task can have more than one R when the work is shared. A task with no R is a task nobody will start.
Accountable: who answers for it
The A makes the final call and carries the consequences. This is a different thing from doing the work. A founder can be A for the monthly bills while a bookkeeper does the work as R. The same person can be both R and A, and in a two-person team that is the most common case.
Consulted: asked before
A C is asked for input before a decision or before the work moves on. It is a two-way exchange: you ask, they answer, you may change course. Use it for people whose view could change the result.
Informed: told after
An I is kept up to date. It is one-way: you tell, they listen. Use it for people who need to know what happened, not for people who get a vote.
Why is the Accountable rule the one that matters?
Asana's guide states that there should be only one Accountable role per task. I agree, and here is the failure it prevents.
Say two people are both marked A for "renew the domain". The renewal email arrives. Each assumes the other is on it. Nothing happens until the domain lapses. With one A, the email has one destination.
If you cannot pick one person, the task is probably two tasks. "Handle the website" is too big. "Publish the weekly update" and "renew the domain" are not. Split the row and give each half its own A.
A two-person example
Two people, Nora and Ben, run a small paid newsletter as a side project. The names, tasks and assignments are invented to show the method. They are not a recommendation for how your team should split work.
| Task or decision | Nora | Ben |
|---|---|---|
| Write the weekly issue | A / R | C |
| Send the issue | I | A / R |
| Answer subscriber email | A / R | I |
| Approve a refund | A / R | I |
| Pay the monthly tool bills | I | A / R |
| Renew the domain | C | A / R |
| Change the price | C | A |
| Back up the subscriber list | I | A / R |
Read it the way you would read it aloud. "Nora writes the issue and answers for it. Ben is asked before it goes out." "Ben pays the bills and answers for them. Nora is told." Each row works as one sentence.
What the example shows
- Every row has exactly one A. There is no task that two people both think is theirs.
- The A and the R are often the same person. That is normal in a team of two. The letters still help, because they show who answers when it goes wrong.
- "Change the price" has an A but no R. That is allowed. A decision can have an owner without a long list of work. Add an R if someone has to carry out the change.
- Ben is A for four rows and Nora for three. Nothing says the split must be equal. It does say whether the load matches what you agreed.
How to build a RACI chart in 20 minutes
- List 8 to 12 recurring tasks and decisions. Write them as verbs: send the issue, pay the bill, approve a refund. Skip one-off tasks. Add them later if they repeat.
- Write the people across the top. Use names, not job titles. A person can answer for something. "The tech team" cannot.
- Mark the A in each row first. One name per row. If two people want it, talk it through now, while it is cheap.
- Mark the R. Put it on whoever does the work. If that is the A, write A / R.
- Add C only where input changes the result. If you would go ahead regardless of the answer, that person is an I, not a C.
- Add I for people who need to know. Keep it short. Informing everyone about everything stops anyone reading it.
- Check each row. Exactly one A. At least one R. Then read it as one sentence.
- Check each column. A person with an A on every row is carrying the whole project. A person with no letters is not in the chart, and you should ask why.
Common RACI mistakes
| Mistake | What goes wrong | Fix |
|---|---|---|
| Two A's on one task | Each person assumes the other has it | Pick one, or split the task in two |
| No A on a task | The task is nobody's problem | Name an A before you name anything else |
| C on everything | Every decision waits for everyone | Keep C for people whose input can change the outcome |
| Titles instead of names | Nobody can answer to a title | Write one person per column |
| Too many rows | Nobody reads the chart | Group related tasks or drop the rare ones |
| Filled in once, never reviewed | It describes last quarter's team | Re-read it on a calendar date and when roles change |
RACI chart, RACI matrix and responsibility matrix: same thing?
Close, with one difference of scope. RACI chart, RACI matrix and RACI model all describe the four-letter grid. "Responsibility assignment matrix" is the broader name, and RACI is one common version of it. Wikipedia lists RACI as a type of responsibility assignment matrix.
You can use the same grid with other letters, or with simpler marks like "owner" and "helper". For a team of two or three, I would keep the four letters. They are well known, so a new person can read the chart without a lesson.
When a RACI chart is not enough
A RACI chart covers tasks and decisions. It leaves three things out, and small teams often need all three.
- Who controls each account. "Ben renews the domain" says who does the job. It does not say whose login holds the domain, whose card pays or where recovery goes. The two-table method adds an account table for this, and the access audit shows where only one person has full control.
- The rules for the whole team. A RACI assigns accountability task by task. It does not set how you disagree or how much anyone can spend. That belongs in a team charter. The difference between charters is covered in team charter vs project charter.
- Why a decision was made. A chart tells you who decided. It does not record what they decided or why. A decision log does.
If one person holds every login, your chart can look healthy while the project is fragile. The bus factor guide explains how to test that.
Copy-and-paste starter
Paste this into a spreadsheet or shared document. Replace the names, delete the rows you do not need and add yours.
| Task or decision | Person 1 | Person 2 | Notes |
|---|---|---|---|
| Do the main work | |||
| Answer customers or users | |||
| Pay recurring bills | |||
| Renew the domain and subscriptions | |||
| Approve spending above an agreed amount | |||
| Decide what to do next | |||
| Back up and recover data |
Rules: one A per row. At least one R per row. C only if the answer could change the plan. Review on a fixed date every quarter, and whenever a role changes.
What this guide does not cover
It does not cover large-organisation project governance, certification or how any one project-management body defines RACI in its own standards. It does not cover who owns equity, code or an asset in law, and it does not tell you how to resolve a dispute between cofounders. It is a working explanation for teams of two to six people. If a real dispute is under way, get advice from a qualified professional in your country.
Frequently asked questions
What is a RACI chart?
A table that shows, for each task, who is Responsible, Accountable, Consulted and Informed. It makes ownership of each task explicit, so nobody has to guess.
What does RACI stand for?
Responsible, Accountable, Consulted, Informed. Responsible people do the work. The Accountable person signs off and answers for the result. Consulted people give input first. Informed people are told afterwards.
What is the difference between Responsible and Accountable?
Responsible is the person who does the task. Accountable is the person who owns the outcome and makes the final call. They can be the same person, and often are in a small team.
Can one task have two Accountable people?
The sources I checked say there should be only one. If two people seem to share it, split the task into two tasks with an owner each.
Is a RACI chart the same as a RACI matrix or RACI model?
In everyday use, yes. They all mean the same grid of tasks and people. "Responsibility assignment matrix" is the wider term, and RACI is one common version of it.
Do I need a RACI chart for a two-person project?
You do not need a big one. Eight to ten rows is enough. It pays off most on the tasks that quietly fall between two people: bills, renewals, refunds and backups.
Sources
- Asana: RACI charts, the ultimate guide, with examples (byline dated 3 December 2025), checked 2026-11-17. Used for the four role definitions and the one-Accountable-per-task rule.
- Wikipedia: Responsibility assignment matrix, checked 2026-11-17. Used for the four definitions and for the relationship between RACI and the broader responsibility assignment matrix. Wikipedia presents the one-accountable rule as part of some project-management theories.
Related
- Responsibility matrix for a small team: tasks and accounts
- RACI matrix template
- Team charter template
- Decision log template
- Team charter vs project charter
- Bus factor: who can recover your project?
- Glossary: RACI
- All co-founder guides and free tools
Keep owners, payers and recovery in one place.