RACI: The Baseline Responsibility Matrix

Summary

RACI maps every task against four roles: who does the work (Responsible), who owns the outcome (Accountable, exactly one per task), who is consulted before the work proceeds, and who is informed after. It descends from the Linear Responsibility Chart of 1950s industrial engineering and has no single inventor; it is the convention that crystallized out of decades of responsibility charting practice. Use it when work is a set of tasks, the team is cross-functional, and you want the lowest-overhead tool that prevents dropped balls. Its two rules carry all the value: exactly one Accountable per row, and a clean separation between doing and owning. When the real question is who decides rather than who delivers, use a decision-rights framework such as RAPID or DACI instead.

The letters

RACI assigns each task or deliverable a set of four roles, mapped against the people or teams involved.

The discipline of the matrix lives in two rules: exactly one A per row, and a clear separation between the person doing the work (R) and the person answerable for it (A). Almost every failure of a RACI chart is a violation of one of those two rules.

Origin and history

RACI did not spring from a single paper or a single author, which is why you will rarely see it attributed to a named inventor. It is the modern shorthand for a much older idea called responsibility charting, itself descended from the Linear Responsibility Chart (LRC) developed in industrial engineering in the 1950s. The LRC pioneered the basic geometry that RACI still uses: tasks on one axis, people on the other, and a code in each cell describing the nature of the involvement.

The earliest forms were sometimes called the “Decision Rights Matrix”, a name that is telling, because it shows the tool was born to clarify authority as much as effort. Over the following decades the technique was absorbed into mainstream project management and eventually codified by the Project Management Institute as the generic Responsibility Assignment Matrix (RAM) in the PMBOK Guide, with RACI as its most common instance. The honest position on authorship is therefore that RACI is a convention that crystallized out of practice, not an invention with a patent or a founding article.

What problem it solves

RACI exists to kill one specific and expensive failure: the “I thought you had it” gap, where a task falls between two people because neither believed they owned it, or stalls because three people believed they did. It does this by forcing an explicit answer to four questions for every unit of work: who does it, who is answerable for it, whose opinion must be sought first, and who merely needs to know.

Its enduring dominance comes from being the smallest matrix that still makes the single most valuable distinction in the whole family: doing versus owning. Cheaper matrices collapse those into one role and reintroduce the ambiguity. Richer matrices add precision at the cost of complexity. RACI sits at the point where the marginal role earns its keep, which is why it remains the default.

When to choose it, and when not

Choose RACI when the work is a set of tasks or deliverables, the team is cross-functional enough that ownership is not obvious, and you want the lowest-overhead tool that still prevents dropped balls. It suits the majority of projects precisely because it is unremarkable.

Reach for a variant instead when RACI’s four roles hide something that matters to your context:

• If hands-on helpers are being folded invisibly into Responsible, use RASCI to name Support.
• If a regulated deliverable needs explicit verification and formal acceptance, use RACI-VS.
• If blank cells keep prompting “why isn’t my team involved?”, use CAIRO to mark Omitted.
• If the real friction is a decision rather than a task, leave the task family entirely and use DACI or RAPID.

Do not use RACI where the central question is authority over a call rather than ownership of a deliverable. A responsibility matrix answers “who builds it”, not “who decides whether we build it”, and stretching it to cover decisions is the most common way people end up frustrated with the tool.

Common pitfalls

• Two A’s on a row. The single most damaging error. If two people are accountable, no one is. Split the task until each half has one owner.
• No A on a row. A silent gap. Every row needs an owner, even if it is the same person across several rows.
• Confusing A with R. Accountable is not “the boss who also does the work”. If the senior owner is genuinely doing the task, say so, but keep the roles conceptually distinct.
• Consulted sprawl. Every extra C adds a two-way conversation and slows the task. Keep the list short.
• Informed fatigue. Over-long Informed lists train people to ignore updates. Reserve I for people whose own work depends on knowing.
• Over-granular rows. Too fine a task breakdown produces an unreadable grid and multiplies the cases where several people collaborate, which the base matrix handles poorly.

Worked example

A software release, mapped for a small delivery team.

Reading the “Approve go-live” row: the Product Manager does the work of assembling the go-live case (R), the Head of Engineering owns the decision and its consequences (A), the Eng Lead and QA are consulted, and the developer is informed. One A per row, one clear R per row, and the Consulted and Informed lists kept lean.

Where it sits in the family

RACI is the origin point. Every other task-centric matrix is defined by reference to it: RASCI is RACI plus Support, CAIRO is RACI plus Omitted, RACI-VS is RACI plus two control roles, and so on. A few near-identical relatives are worth knowing but do not merit separate study:

• ARCI is RACI with the codes reordered and pronounced “arky”. Conceptually identical.
• RASI replaces Consulted with Support, dropping the advisory role entirely.
• RACI-F adds Facilitation, a niche addition used in some Scrum contexts to name whoever runs the ceremony.
• DCI strips the matrix down to Decision maker, Consulted, Informed, losing the doing-versus-owning split that makes RACI valuable.

If you learn RACI properly, including its two rules and its failure modes, you have learned four-fifths of every other matrix in the family.

Sources

Web sources

• Responsibility assignment matrix, Wikipedia: https://en.wikipedia.org/wiki/Responsibility_assignment_matrix
• RACI Matrix, CIO Wiki (notes the 1950s “Decision Rights Matrix” and “responsibility charting” lineage): https://cio-wiki.org/wiki/RACI_Matrix
• Understanding the Responsibility Assignment Matrix, project-management.com: https://project-management.com/understanding-responsibility-assignment-matrix-raci-matrix/
• ARCI, DACI, RASCI, RACI, RACI Solutions: https://www.racisolutions.com/blog/bid/46600/arci-daci-rasci-raci-and-the-art-of-scalability

Academic sources

• Korey, G. (1973) ‘LRC: modern technique for functional organization analysis’, Academy of Management Proceedings, 1973(1), pp. 184-189. The linear responsibility chart presented to an academic audience, documenting the technique RACI descends from.
• McCann, J.E. and Gilmore, T.N. (1983) ‘Diagnosing organizational decision making through responsibility charting’, Sloan Management Review, 24(2), pp. 3-15. The classic scholarly treatment of responsibility charting as a diagnostic method.
• Gilmore, T.N. and Kazanjian, R.K. (1989) ‘Clarifying decision making in high-growth ventures: the use of responsibility charting’, Journal of Business Venturing, 4(1), pp. 69-83. https://doi.org/10.1016/0883-9026(89)90034-9
• Jensen, M.C. and Meckling, W.H. (1976) ‘Theory of the firm: managerial behavior, agency costs and ownership structure’, Journal of Financial Economics, 3(4), pp. 305-360. https://doi.org/10.1016/0304-405X(76)90026-X
• Fama, E.F. and Jensen, M.C. (1983) ‘Separation of ownership and control’, Journal of Law and Economics, 26(2), pp. 301-325. The decision-management versus decision-control distinction behind the R/A split.
• Cabanillas, C., Resinas, M. and Ruiz-Cortés, A. (2012) ‘Automated resource assignment in BPMN models using RACI matrices’, in On the Move to Meaningful Internet Systems: OTM 2012, Lecture Notes in Computer Science 7565. Berlin: Springer. https://doi.org/10.1007/978-3-642-33606-5_5
• Prabaswari, Ali, Y. and Gultom, R.A.G. et al. (2025) ‘Enhancing cyber crisis preparedness in Indonesia: a RACI-based approach to formulating a national cyber crisis task force’, Journal of System and Management Sciences, 15(2), pp. 225-244. A recent peer-reviewed application of RACI at national-institution scale.
• Project Management Institute (2021) A Guide to the Project Management Body of Knowledge (PMBOK Guide). 7th edn. Newtown Square, PA: PMI. Codifies the responsibility assignment matrix, with RACI as its most common form.