Most small-business projects do not fail because the work was hard. They fail because two people each thought the other one owned it. The RACI matrix exists to kill that specific failure, and in project management it remains the fastest way to make ownership explicit before work starts: one grid, four letters, and every task gets a name next to it. This guide covers what RACI actually means, the one rule that makes or breaks it, the mistakes that turn it into shelf-ware, when to use a variant instead, and a free xlsx template with a built-in check that flags any row missing its single Accountable owner.
Free RACI chart template. One Excel file, four sheets: the blank RACI chart with R/A/C/I/S dropdowns, a column that flags any task without exactly one Accountable, and two filled-in examples (a website redesign and a product launch). It opens in Google Sheets too.
What RACI stands for in project management
RACI is a responsibility assignment matrix: tasks or deliverables down the rows, people or roles across the columns, and one letter in each cell. It is referenced in the PMBOK and the IPMA competence baseline as a core governance tool, which is a fancy way of saying it has survived decades of project managers because it works.
The four letters:
R — Responsible. The person who does the work. Every task needs at least one R, and complex tasks can have several, though piling Rs on one row is usually a sign the task should be split.
A — Accountable. The person who owns the outcome. They sign off, they decide, they are the escalation point when something is stuck. Accountability here is not about blame; it is about there being exactly one person the team can turn to for a definitive answer on that task.
C — Consulted. People whose input is needed before the work is done. Two-way communication: you ask, they answer, their input can change the outcome.
I — Informed. People who need to know the result after the fact. One-way communication: a notification, not a conversation.
The distinction everyone fumbles is R versus A. The Responsible person executes; the Accountable person answers for the result. One person can hold both on the same task (common in small teams), but the roles are different jobs, and confusing them is how tasks end up executed by committee and owned by nobody.
The golden rule: exactly one A per task
Every rule in RACI bends except this one. Each task gets exactly one Accountable owner. Not zero, not two. One.
Two A’s on a row means accountability has effectively disappeared: each owner assumes the other is watching, and the moment a decision is needed, both look across the table. Project managers call this diffusion of responsibility, and the matrix exists specifically to prevent it. Zero A’s is just as bad: a task with an R but no A has an outcome that belongs to everyone, which in practice means it belongs to no one. If you cannot name a single Accountable for a task while building your matrix, that is a governance gap to fix before work begins, not a cell to leave blank.
The supporting rules are softer but worth stating. Every task needs at least one R. C and I are optional per task, but they should be deliberate choices, not defaults. One person can hold A on many rows (a founder often holds most of them); what is forbidden is two A’s on one row.
How to build a RACI matrix in 5 steps
1. List the deliverables, not every micro-task. Five to fifteen rows cover most small-business projects. If your matrix has forty rows, you have built a project plan, not a responsibility chart, and nobody will read it.
2. Put roles across the top, not names, if the project will repeat. For a one-off project, names are fine and clearer. For a recurring process (client onboarding, monthly reporting), use job titles so the matrix survives staff changes.
3. Fill the grid together. A RACI built alone by the project manager and presented as finished is the single most common way these things die. The matrix is a conversation that produces shared language about who does what; the document is a byproduct.
4. Audit the grid. One A per row, at least one R per row, no person carrying R on most rows (that is a capacity problem the matrix just made visible), and no team member with zero R and zero A across the whole project (question whether they need to be on it).
5. Share it and revisit it. Walk every stakeholder through their column before work starts. Then update the matrix at each phase gate or whenever roles change. A RACI that reflected reality at kickoff can be actively misleading six weeks later.
The 7 mistakes that break a RACI matrix
1. Two Accountable owners on one task. The classic. Shared accountability is no accountability; pick the person with decision authority.
2. Confusing R and A. The doer and the owner are different jobs. When the same person holds both, write both letters deliberately rather than assuming it.
3. Too many Consulted. Every C is a conversation that has to happen before the work finishes. Five C’s on a row means a committee, and committees are where momentum goes to die. Keep only the people whose input genuinely changes the outcome.
4. Too many Informed. Not everyone needs updates on everything. Over-using I creates notification noise that trains people to ignore the matrix entirely.
5. Making it too detailed. A RACI should be scannable in thirty seconds. Granularity beyond that belongs in your project plan, and if you need one, our project management guide for small business covers how to structure it.
6. Building it in isolation and never updating it. Both halves of the same failure: the matrix is a living agreement, not a kickoff artifact. Review it when scope, staffing, or stakeholders change.
7. One person holding every R. The matrix does not just assign work; it makes overload visible. If one column is a wall of R’s, redistribute before the project starts, not after the burnout.
RACI vs RASCI vs DACI vs RAPID: pick by bottleneck
The variants exist because RACI has two known gaps, and each variant patches one of them. Pick by where your team actually loses time, not by which acronym sounds more sophisticated.
RASCI adds one letter: S for Support, people who contribute real effort or resources without owning the outcome and without merely advising. A borrowed specialist, a shared-services team, a junior helping a senior execute. If nobody on your project fits that description naturally, skip the extra column; adding it for the look of it is dead weight.
DACI (Driver, Approver, Contributors, Informed) is not a task tool at all. It maps decision authority: the Driver runs the process, exactly one Approver makes the call, Contributors shape it, the Informed hear it. If your post-mortems keep surfacing “we waited three weeks for someone to decide,” that is decision latency, and DACI is the fix. RACI runs the work; DACI runs the calls.
RAPID (Recommend, Agree, Perform, Input, Decide) comes from Bain and is built for rare, high-stakes, cross-functional decisions where some stakeholders hold real veto power: legal, security, finance. The Agree role is the difference. Using RAPID on a two-person call is overhead with no payoff; save it for the two or three decisions a quarter where a “no” from one function genuinely stops the work.
The shortcut: tasks default to RACI, decisions default to DACI, and RAPID is for the dangerous ones. Mature teams run RACI on the workstreams and pull DACI or RAPID out at decision points, sometimes on the same project.
The free RACI chart template (Excel) and its accountability check
Download the free RACI matrix template (Excel / Google Sheets). Four sheets:
Start here — the four roles, the golden rule, and the mistakes checklist, so the file teaches the method while you use it.
RACI template — the blank grid: twenty task rows, six role columns, dropdowns restricted to R, A, C, I, S, and color-coded cells. The last column runs an automatic check on every row: it shows OK when the row has exactly one A, and FIX with the actual count when it has zero or several. That one formula is the difference between a template and a template that catches the golden-rule violation before your team does.
Example — Website redesign — a filled matrix for a five-person small business: founder, designer, developer, copywriter, marketing VA. Notice the founder holds A on every row. That is normal at this size, and it is allowed: one person can own many outcomes, as long as no row has two owners.
Example — Product launch — a filled cross-functional matrix where accountability moves between the CEO (strategy rows) and the product manager (execution rows), which is what healthy delegation looks like on paper.
Upload the file to Google Sheets (File, Import, Upload) and everything works: dropdowns, colors, and the accountability check.
When RACI is the wrong tool
Three cases. First, projects small enough that a five-minute conversation covers ownership; a matrix for a two-person, two-day job is bureaucracy cosplay. Second, agile teams whose roles are already clear and actually held: product owner, developers, scrum master. If an agile team reaches for RACI, it usually signals the standard roles are not being honored, or the work is cross-functional in ways the agile setup does not cover; in that case, run RACI at the workstream level, not the task level. Third, decisions rather than tasks, which is DACI or RAPID territory as covered above.
And a process note: a RACI assigns ownership, but ownership needs a rhythm to survive contact with reality. A short weekly check-in where each Accountable reports on their rows is what keeps the matrix honest. Our team meeting agenda templates include a weekly format built for exactly that, and if the ownership question extends to your first hire’s role, our first-employee checklist pairs well with a fresh RACI. When unclear ownership is really a symptom of missing systems, the fix is bigger than a matrix; our business management software guide covers the tooling side. Pairing that weekly check-in with a project status report template keeps the same ownership visible outside the meeting too.
Frequently asked questions
What does RACI stand for in project management?
Responsible, Accountable, Consulted, Informed. Responsible does the work, Accountable owns the outcome (exactly one per task), Consulted gives input before the work, Informed is notified after. A RACI matrix maps these four roles against every task or deliverable in a project.
What is the difference between Responsible and Accountable in RACI?
Responsible executes the task; Accountable answers for the result and makes the final call. One person can hold both roles on the same task, which is common in small teams, but they are different jobs: the R produces the work, the A signs off on it and absorbs the escalation when it stalls.
Can a task have two Accountable owners in RACI?
No. Two A’s on one row is the most common RACI mistake, and it destroys the tool: each owner assumes the other is watching, and decisions stall. If you genuinely cannot choose between two candidates, the real problem is an unresolved governance question; escalate it and pick one.
Is RACI outdated for agile teams?
Not outdated, but applied differently. Agile teams with clear, honored roles rarely need it. Where RACI still earns its place in agile environments is cross-functional work: run it at the workstream or decision level rather than task by task. The one-Accountable principle is embedded in the PMBOK and IPMA frameworks and is not going anywhere.
What is the difference between RACI and DACI?
RACI assigns ownership of work; DACI assigns ownership of decisions. RACI maps Responsible, Accountable, Consulted, Informed across tasks. DACI maps Driver, Approver, Contributors, Informed across a decision. Use RACI to run deliverables week to week, and DACI for the significant calls that determine direction.
RACI answers “who owns it”; the next question is “how does the work flow”. Our guide to the 8 types of project management helps you pick between Waterfall, Scrum, Kanban, and the rest, with a free decision tree PDF — and it confirms that a team of 1-3 needs ownership and rhythm, not a framework.
The bottom line
RACI in project management is not paperwork; it is a fifteen-minute conversation that prevents the most expensive sentence in a small business: “I thought you had it.” List the deliverables, give every row exactly one Accountable owner, keep the Consulted list honest, and revisit the grid when the project changes shape. Download the template, fill it with your team for the project that is currently fuzziest, and let the built-in check catch any row where ownership is still wishful thinking.
