RACI Matrix

A RACI matrix is a responsibility assignment chart that maps every key task or decision on a project to four roles: Responsible, Accountable, Consulted, and Informed, to eliminate ownership gaps before delivery begins.

The four roles

Letter	Role	Meaning
R	Responsible	Does the work. Can be multiple people.
A	Accountable	Owns the outcome. Exactly one per task.
C	Consulted	Provides input before or during. Two-way dialogue.
I	Informed	Receives updates after decisions are made. One-way.

The only hard rule: every task must have exactly one A. Multiple accountable owners is equivalent to no accountable owner, because each person assumes one of the others will take responsibility.

Why it matters on professional services engagements

Client and vendor team boundaries blur quickly during delivery. The RACI forces an explicit agreement, before work starts, about who approves deliverables, who escalates blockers, who signs off on scope changes, and who simply needs to be kept informed.

Without this agreement, those conversations happen at the worst possible time: under deadline pressure or in the middle of a dispute. A RACI produced and signed at kickoff removes the ambiguity that enables each side to claim the other was responsible.

A RACI also protects the delivery team from scope creep that arrives disguised as small informal requests from client stakeholders who assumed they had authority over work they were not contracted to direct. When it is on the RACI that the client’s procurement lead is Informed rather than Accountable for a deliverable, that boundary is explicit.

Common mistakes

• Assigning multiple Accountable parties to a single task. This is the most frequent error and the one with the most damaging consequences.
• Confusing Consulted with Informed. Consulted means the team waits for that person’s input before proceeding. Informed means the team notifies them after a decision is made. Treating an Informed stakeholder as Consulted creates unnecessary bottlenecks; treating a Consulted stakeholder as Informed creates downstream objections.
• Creating a RACI so large and detailed that the document is not practical to use during delivery.
• Building it without the client present, then presenting it as a completed decision rather than a collaborative agreement.

Building a practical RACI

List tasks and decisions in rows and stakeholder roles in columns. Start with the decisions that caused ownership disputes on the last comparable engagement, then add the standard categories: deliverable approval, scope change authorization, issue escalation, and invoice sign-off.

Keep it to one page where possible. A RACI that runs to multiple pages tends to reflect a governance structure that is itself too complex. Review it at the start of the engagement and revisit it whenever scope changes under a formal change order.