RACI stands for Responsible, Accountable, Consulted, and Informed, and it exists to answer one question that derails more projects than any technical problem: when two people disagree about a decision, whose call is it. A RACI matrix maps every task or decision in a project to the people who fill each of those four roles, so the answer is written down before the disagreement happens, not during it.
What changed in 2026
- RACI now auto-populates from project tools in many teams, pulling Responsible and Accountable directly from task assignees, though Consulted and Informed still need a manual pass.
- DACI and RASCI variants gained ground for decision-heavy projects, adding a distinct Driver role or splitting Support out from Responsible.
- Lightweight who-decides RACI became common — a single-page version covering major decisions only, instead of a row for every task, for teams that found full-project RACI too heavy to maintain.
What each letter actually means
Responsible is whoever does the work. There can be more than one Responsible person on a task.
Accountable is whoever owns the outcome and answers for it if the task fails. There must be exactly one Accountable person per task — this is the rule teams break most often, and it is the one that matters most.
Consulted is whoever gives input before a decision is made. This is two-way: their feedback should actually change the outcome, or they should not be listed as Consulted.
Informed is whoever needs to know the outcome after it happens. This is one-way: no input expected, just a notification.
How to build a RACI matrix
- List the major tasks or decisions down the left column. This list often comes directly out of the project kickoff — not every single to-do, just the ones where role confusion would actually cause a problem.
- List every person or role across the top.
- Assign exactly one Accountable per row. If two names seem accountable, the task needs to be split or the ownership question needs to be resolved before moving on.
- Fill in Responsible, Consulted, and Informed for each row, checking that Consulted stays short.
- Review it with the team, not just the project lead — people often catch a missing Informed party or a Consulted role that should not be there.
RACI matrix example
| Task |
Responsible |
Accountable |
Consulted |
Informed |
| Approve project budget |
Finance lead |
Sponsor |
Project lead |
Whole team |
| Write technical design |
Engineering lead |
Engineering lead |
Product, Security |
Stakeholders |
| Approve final copy |
Content writer |
Marketing lead |
Legal |
Sales |
| Launch decision |
Project lead |
Sponsor |
Engineering, Support |
Whole company |
Common RACI mistakes
Two people marked Accountable. This feels collaborative but produces the opposite effect — when something goes wrong, each person assumes the other is handling it.
Everyone marked Consulted. A Consulted list that matches the full team is not a role assignment, it is a way of avoiding the decision about who actually needs a say.
Building it once and never updating it. Roles shift as a project moves from planning into execution. A RACI matrix that still reflects the original team six months in is actively misleading.
FAQ
Can the same person be Responsible and Accountable for the same task?
Yes, and for small tasks this is common. The value of naming both separately shows up on larger or cross-team tasks, where the two roles are more likely to be different people.
How is RACI different from an org chart?
An org chart shows reporting lines. A RACI matrix shows decision rights on a specific project, which frequently cuts across reporting lines entirely.
Is RACI worth using for a small team?
Often not. A three- or four-person team where everyone already knows their role gets little benefit from formalizing it, and the matrix becomes overhead nobody maintains.
What is the difference between RACI and DACI?
DACI swaps Accountable for a Driver role focused on moving a decision forward, and is popular for one-time decisions rather than ongoing task ownership. Pick whichever vocabulary your organization already uses consistently.
Where to go next