The RACI Matrix (Responsibility Assignment Matrix) is a project management framework that clarifies task ownership by mapping each activity to exactly four roles: Responsible, Accountable, Consulted, and Informed. Originating in project management practice and formalized in frameworks like PMBOK, RACI solves the accountability ambiguity that plagues cross-functional teams by answering two critical questions: who does the work, and who owns the outcome. The golden rule is non-negotiable: every task needs exactly one Accountable owner — multiple accountables create diffusion of responsibility, while no accountable means work falls through cracks. In 2026, RACI has expanded beyond traditional project work into AI governance, autonomous systems, and regulated compliance frameworks, making role-clarity structures more essential than ever.
What This Cheat Sheet Covers
This topic spans 16 focused tables and 109 indexed concepts, 70 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: Core RACI Roles
The four roles are the entire vocabulary of the framework; every cell in a RACI matrix must resolve to one of these or be left blank. Understanding the precise boundary between each role — especially Accountable vs. Responsible and Consulted vs. Informed — prevents the most common implementation errors.
| Role | Example | Description | |
|---|---|---|---|
Developer writes codeDesigner creates mockup | • The person(s) who perform the actual work to complete the task • can be multiple people; when there are multiple R's, designate one as R-Prime (R1) for tie-breaking accountability | ||
Product Manager approves featureProject Manager signs off deliverable | • The single person who owns the outcome and has final approval authority • the golden rule: exactly one A per task — never zero, never two | ||
Security team reviews architectureLegal provides contract feedback | • Stakeholders whose input is actively sought before decisions or actions • two-way communication; their expertise shapes the outcome | ||
Executive receives status reportCustomer gets launch notification | • Parties kept updated on progress but not providing input • one-way communication for awareness only; C comes before action, I usually comes after |