Most project failures don’t start with a technical problem. They start with a sentence: “I thought you were handling that.” Tasks fall through gaps between people, decisions wait for approval nobody was assigned to give, and three people rewrite the same document because none of them knew the others were on it.
The RACI matrix is a simple tool for eliminating that ambiguity. It’s a grid that states, for every task in a project, exactly who does the work, who owns the outcome, who gets asked, and who gets told. This article covers what each role means, how to build a matrix, and the mistakes that turn a useful RACI into a decorative spreadsheet.
What RACI stands for
RACI is an acronym for four types of involvement a person can have in a task. The distinction between the first two is where most of the value lies.
| Letter | Role | Meaning | How many per task |
|---|---|---|---|
| R | Responsible | Does the work | One or more |
| A | Accountable | Owns the outcome and approves it | Exactly one |
| C | Consulted | Gives input before the work is finished; two-way | As few as possible |
| I | Informed | Is told the result; one-way | As many as needed |
Responsible vs Accountable
Responsible is about effort; Accountable is about ownership. A designer who produces a landing page is Responsible. The marketing lead who signs off on it and answers for the result is Accountable. The same person can hold both letters on a small task, but the roles are conceptually different.
The rule that matters most: each task has exactly one Accountable person. Two owners means no owner, because each can reasonably assume the other is deciding.
Consulted vs Informed
Consulted means a genuine conversation happens before the work is complete, and the input can change the result. Informed means the person receives the outcome, with no expectation of a reply.
Teams often mark too many people as Consulted out of politeness. Every C adds a round trip and a potential delay, so it’s worth asking whether the person’s input would actually change the decision. If not, they’re Informed.
What a RACI matrix looks like
The structure is always the same: tasks or deliverables run down the left as rows, people or roles run across the top as columns, and each cell holds a letter — or stays empty.
| Task | Project manager | Designer | Developer | Marketing lead | Client |
|---|---|---|---|---|---|
| Define requirements | A | C | C | C | R |
| Create wireframes | A | R | C | I | I |
| Build the pages | A | C | R | I | I |
| Approve visual design | I | R | I | A | C |
| Launch | A | I | R | C | I |
Notice that empty cells are allowed and desirable. If everybody has a letter on every row, the matrix isn’t clarifying anything.
How to build one
- List the tasks that matter. Use deliverables and decisions, not every micro-step. Ten to twenty rows is usually enough for a project phase.
- List the roles, not the names. Roles survive staff changes; names don’t. Add names in a second column if helpful.
- Assign one A per row first. Ownership is the hardest and most important call, so make it before anything else.
- Add the R’s. Who actually performs the work? More than one is fine when the task is genuinely shared.
- Add C and I sparingly. For each one, ask what that person will do with the information.
- Review the matrix with the team. This conversation is where hidden disagreements surface — and it is the real value of the exercise.
Reading the matrix for problems
Once built, the grid can be scanned for warning signs in both directions.
- A row with no R: nobody is doing the work.
- A row with two or more A’s: ownership is split, and the decision will stall.
- A row full of C’s: the task will move slowly through endless consultation.
- A column with A’s everywhere: one person is a bottleneck for the whole project.
- A column with only I’s: that person may not need to be in the project at all.
- A column that is empty: either the role is unnecessary or a task is missing.
Common mistakes
The most frequent failure is building the matrix alone and sending it out by email. RACI works because of the discussion it forces, not because of the file it produces. A grid nobody argued about is a grid nobody agreed to.
The second is excessive detail. A matrix with 200 rows will not be maintained and will be ignored within a month. Keep it at the level of deliverables and decisions.
The third is treating it as permanent. Projects change scope, people change roles, and a matrix that no longer reflects reality is worse than none, because it gives false confidence. Revisit it at the start of each phase.
Variations you may encounter
Several extensions of the model exist. RASCI adds an S for Support — people who assist the Responsible party without owning the task. RACI-VS adds a Verifier, who checks the work against criteria, and a Signatory, who gives formal approval. These are useful in regulated or highly formal environments, but for most teams the original four letters are enough, and simpler tends to mean actually used.
Conclusion
A RACI matrix costs an hour to build and prevents weeks of confusion. Its real output isn’t the spreadsheet — it’s a team that agrees on who decides, who does the work, and who simply needs to be kept in the loop.
If you’d like to build on this with scheduling, scope and stakeholder management, the free project management courses on Cursa are a good place to continue.
