RACI is a grid that assigns four roles to each task or decision in a piece of work. Responsible does the work. Accountable is the single person who answers for the outcome. Consulted is asked for input before it happens. Informed is told once it has. One row per deliverable, one letter per person, and — the part that carries all the value — exactly one A on every row.
Everything else about RACI is administration. The reason it exists is that most coordination failures in a company are not skill problems or effort problems; they are ownership problems, where three people each assumed one of the others had it. Writing a single name in the Accountable column is what ends that argument.
Whether you need the full grid is a separate question, and for a small company the honest answer is usually no. Below is what the letters mean, what they get confused with, when the grid earns its keep, and the lighter version that does most of the same work.
What each letter stands for
Take one concrete example: a company changing how it onboards new clients.
- R — Responsible. The people who do the actual work: writing the new welcome sequence, updating the intake form, rebuilding the checklist. There can be several, and there usually are.
- A — Accountable. The one person who answers for whether it happened and whether it was any good. Not the person who does the most work; the person you would ask if it were late. There is exactly one, on every row, always.
- C — Consulted. People whose input is genuinely needed before the thing is finished — two-way, and expensive. In this example: the person who runs delivery, because they inherit whatever you design.
- I — Informed. People who need to know after — one-way, cheap. Sales, in this example, so they can describe onboarding accurately.
The letters attach to a row, not to a person. The same person can be R on one row and I on the next, which is exactly the sort of thing that goes unsaid otherwise.
What is the difference between Responsible and Accountable?
This is the question that sends people looking for a definition in the first place, and the distinction is real.
Responsible is about hands. Accountable is about answers. If a client complaint arrives about the new onboarding, the Accountable person takes the call — even if someone else wrote every word of the sequence. They chose to ship it.
Three rules keep it usable:
- A is singular. Two Accountable names mean nobody is accountable — that is the entire failure mode the letter exists to prevent.
- A is not automatically the most senior person. Accountability travels with the work, not the title. An owner who takes the A on everything has built an org chart, not a RACI.
- A and R are often the same person on a small team, and that is fine. Write both letters and move on. The point is not to spread the work across more people; it is to stop pretending the work has an owner when it does not.
When does a RACI actually matter?
Use it where ambiguity has a cost you can name:
- Work crosses more than two people or functions, especially where one person's output is another's input.
- A handoff keeps dropping — the same thing falls through in the same place every month.
- Decisions stall because nobody is sure whose call it is, and everyone is being polite about it.
- Someone new inherits a process, and the ownership currently lives in one person's head.
- An outside vendor, contractor, or agency is involved, where assumed ownership is far riskier because they cannot read the room.
- Something went wrong and the review found no owner. That is the cheapest moment to write the rows.
And skip it when the team is small enough that everyone is in the same thread, the work is a one-off, or ownership is already obvious. A grid that documents what everybody already knows is pure overhead — and if the real problem is that one person is at capacity, no chart will fix it. Our guide to delegating without losing control of quality covers that version of the problem, which is far more common in small companies than genuine confusion about who owns what.
What RACI is confused with
Four things, and the difference matters because each one solves a problem RACI does not:
- An org chart shows who reports to whom. RACI shows who owns what on this specific work — and the two often disagree, legitimately.
- A job description covers a role in general. RACI covers one project or process, and expires with it.
- An SOP documents how the work is done, step by step. RACI documents who. They complement each other, which is why our guide to writing an SOP people actually follow is the natural companion to a chart like this.
- Decision-rights models such as DACI or RAPID look similar but are built for choosing, not for delivering. If your problem is that decisions do not get made, those fit better; if your problem is that work does not get finished, RACI fits better.
There is also a common variant, RASCI, which adds S for Support — people who help without owning. Useful on large projects, usually unnecessary on small ones.
How to build one in under an hour
- List the deliverables and the decisions, not the activities. Eight to fifteen rows is normal for a small project. "Approve the new pricing" is a row; "have meetings" is not.
- Assign the A first, before anything else. If a row takes more than a minute to assign, you have found exactly why the work keeps stalling.
- Then the R. Several names are fine here.
- Add C sparingly. Every C is a conversation someone has to have, and generous consulting is the most common way a RACI slows a company down instead of speeding it up.
- Make I a distribution list, not a ceremony.
- Read the columns, not just the rows. Anyone who is C on everything is a bottleneck. Anyone with no letters anywhere is either miscast or missing. Anyone who is A on most rows is a single point of failure.
- Put it where the work lives — the project board, the shared doc, the process file — not in a deck nobody opens again.
Where RACI charts go wrong
- Two A's on a row, usually added to avoid a difficult conversation. It reinstates the exact ambiguity you were removing.
- An A with no authority over budget, time, or people. Accountability without leverage is just blame with a nicer name.
- Too many C's, which turns a delivery tool into a consultation queue.
- Charting activities instead of outcomes, which produces forty rows nobody reads.
- Writing it once and never revisiting it. People leave, scope changes, and a stale grid is worse than none because it is quoted with confidence.
- Using it after the fact to assign fault. Do that once and the next chart will be negotiated rather than honest.
The lighter version most small teams should use instead
For a team under roughly ten people, the maintenance cost of a full grid usually exceeds the coordination benefit. Three columns capture most of the value:
Deliverable | Owner | Who must be asked first
One line per deliverable, one owner, and the short list of people who have to weigh in before it is final. Anyone else finds out when it ships. That is a RACI with the ceremony removed, it fits on one page, and people actually update it.
Reach for the full four-letter version when the work crosses functions, involves outside parties, or has enough moving pieces that "who must be asked" stops being obvious. The broader operating rhythm this sits inside is covered in our operations and process guide.
FAQ
Can two people be Accountable for the same thing? No — that is the one rule worth being rigid about. Shared accountability reliably becomes no accountability, because each person assumes the other is carrying it. If two people genuinely own different parts, split the row into two rows.
What if the Accountable person is also doing all the work? Common on a small team, and perfectly valid. Put both letters against their name. The chart is describing reality, not prescribing a headcount.
What does being Consulted actually commit someone to? Giving input before the work is finished, within a stated window. Without a deadline, a C becomes an open-ended veto, which is how these charts acquire their reputation for slowing everything down.
Is RACI the same as an org chart? No. An org chart shows reporting lines that persist. RACI shows ownership on a specific piece of work, and it should regularly disagree with the org chart — juniors own things, senior people get informed.
How often should a RACI be updated? At the start of a project, whenever scope or people change, and at any review where something fell through a gap. If nobody has looked at it in months, it is either finished work or fiction.
RACI is one idea wearing four letters: every piece of work has exactly one name that answers for it, and everyone else has a defined relationship to that name. Start with the ownership question on the handoff that keeps failing, use the three-column version until the work outgrows it, and add the full grid only when the coordination cost is real. For more practical operations guidance built for small and mid-sized companies, visit Consulting Firm USA.
