Responsibility Assignment Matrix (RACI)
A structured framework to define project roles, prevent task overlap, and clarify stakeholder involvement throughout the project lifecycle.
§1Framework Definitions
The RACI matrix (Responsibility Assignment Matrix) standardises how project roles interact with specific deliverables. It is a critical tool for optimising team communication and ensuring no essential task is orphaned.
The matrix utilises four primary classifications for each work package or activity:
- Responsible (R): The person or team directly performing the work to achieve the task.
- Accountable (A): The individual answerable to the Project Manager (or Sponsor) ensuring the work is done on time and meets requirements. They have ultimate ownership and sign-off authority.
- Consult (C): Stakeholders who possess information, capability, or context necessary to complete the work. They provide two-way communication and input.
- Inform (I): Individuals who must be notified when the work is complete or changed. They are kept in the loop via one-way communication.
§2Blank RACI Matrix
The baseline template structured for immediate deployment. Map your project's work packages to the left and assign your specific team members across the top row columns.
| Work Package / Activity | Person 1 | Person 2 | Person 3 | Person 4 | Person 5 | Person 6 |
|---|---|---|---|---|---|---|
| Project charter | ||||||
| Stakeholder identification | ||||||
| Requirements gathering | ||||||
| Information architecture | ||||||
| Visual / brand design | ||||||
| Content writing | ||||||
| CMS development | ||||||
| CRM integration | ||||||
| Quality assurance / UAT | ||||||
| Accessibility audit | ||||||
| Launch / Go-Live | ||||||
| Post-launch support handoff | ||||||
| Project closeout |
§3Worked Example: Website Project
A practical demonstration of the RACI model applied to Mary's Consulting - New Company Website project delivery. Notice the single point of Accountability (A) assigned horizontally across each work package to prevent management overlap.
| Work Package / Activity | Mary (Sponsor) |
Andrew (PM) |
Bob (Developer) |
Bill (Designer) |
Christine (Content) |
Marketing Lead |
|---|---|---|---|---|---|---|
| Project charter | A | R | I | I | I | C |
| Stakeholder identification | I | R | I | I | I | C |
| Requirements gathering | C | A | C | C | C | R |
| Information architecture | I | A | C | R | C | C |
| Visual / brand design | A | C | I | R | C | C |
| Content writing | I | A | C | R | C | |
| CMS development | A | R | C | I | I | |
| CRM integration | I | A | R | I | I | C |
| Quality assurance / UAT | A | R | R | R | C | |
| Accessibility audit | I | A | C | R | I | I |
| Launch / Go-Live | A | R | R | C | C | C |
| Post-launch support handoff | A | R | C | C | C | R |
| Project closeout | A | R | I | I | I |
Quick reference
Performance (R)
The "doer". The individual actively working on creating the deliverable or completing the task. Multiple people can be responsible.
Ownership (A)
The "owner". Answerable for ensuring the task is complete and standard. Strictly limited to one individual per task to avoid confusion.
Support (C / I)
Subject matter experts who provide crucial two-way feedback before completion (Consult), or those who are updated one-way upon completion (Inform).