What RACI actually means
The four letters are frequently misunderstood, particularly Accountable and Consulted. The distinctions matter because assigning the wrong letter is effectively not assigning accountability at all.
The person or people who do the work. Multiple people can be Responsible for the same activity — this is the "how" of execution. Being Responsible does not mean having the authority to make final decisions about the activity.
Watch for: Multiple Rs without coordination creates a diffusion of effort. Two people both responsible for writing a deliverable often produce half a deliverable each.
The one person who is ultimately answerable for the correct and thorough completion of the activity. There must be exactly one Accountable per activity — no more, no fewer. If two people are accountable, neither is. If no one is accountable, the activity has no owner.
Watch for: The most common RACI failure is assigning A to the PM by default. The PM is accountable for the project, but rarely the right person to be accountable for each specific activity within it.
People whose input is sought before a decision is made or work is completed. Consulted is a two-way relationship — the person being consulted should be able to influence the outcome. If their input is not going to influence anything, they are Informed, not Consulted.
Watch for: Over-assigning C creates a consultation burden that slows delivery. If every senior stakeholder is Consulted on every activity, nothing moves. Be deliberate about who genuinely needs to influence the outcome.
People who are kept updated on progress or decisions after they are made. Informed is a one-way relationship. The Informed party receives information — they do not provide input or bear accountability. Governance stakeholders who need awareness but not involvement are typically Informed.
Watch for: Under-assigning I is as problematic as over-assigning C. Stakeholders who should be Informed but aren't will surface their concerns at the wrong time — typically in a review meeting rather than during execution.
The activities that belong in a RACI
The activities in a RACI should be at the right level of granularity — specific enough to assign accountability meaningfully, not so granular that the matrix becomes unmanageable. For most projects, the right level is major deliverables, key decisions, and governance activities — not individual tasks.
The activities most worth including are the ones where accountability is genuinely ambiguous — where, without explicit assignment, different stakeholders will have different expectations about who is responsible. These are typically the activities where, when something goes wrong, everyone discovers simultaneously that they all assumed someone else owned it.
The failure modes that make RACI useless
Built at kickoff and never updated
The RACI produced at kickoff reflects the project as it was understood at kickoff — the team structure, the stakeholder map, the governance assumptions. All of these change. A RACI that is not updated when the team changes, when a business owner is replaced, or when governance is restructured is a document that describes a different project.
PM assigned as Accountable for everything
The PM is accountable for managing the project. They are rarely the appropriate person to be accountable for each technical deliverable, business decision, or sign-off within it. When the PM is assigned A for everything, the RACI tells the stakeholders nothing about who actually owns what — it just tells them to come to the PM, which they already knew.
Everyone is Consulted on everything
Over-consulting creates a governance structure that is technically inclusive but practically unworkable. When every senior stakeholder is Consulted on every activity, the consultation process becomes a bottleneck, and stakeholders learn to either ignore consultation requests or treat them as FYIs. Either way, the C loses its meaning.
Not used in meetings
The most diagnostic signal of a RACI that is not working is that decisions are being made in meetings by whoever is most senior in the room, regardless of what the RACI says. When a decision is made by someone who the RACI does not assign as Accountable, that is a RACI variance — and it should be recorded as one.
Used as a blame document rather than a clarity document
A RACI used primarily to establish who is at fault when something goes wrong will rapidly be gamed. Stakeholders will resist being assigned A to activities where they perceive high risk. The RACI should be framed and used as a clarity instrument — this is how we will make decisions — not as a future liability assignment.
Using RACI as a living instrument
A RACI that is treated as a living instrument — reviewed at each phase boundary, updated when the team or governance structure changes, and actively referenced in decisions — is one of the most powerful accountability tools in the PM's toolkit.
The review trigger should be any significant change to the project — a team member departing, a governance structure being revised, a business owner being replaced, a new workstream being added. The question to ask at each review is not "does the RACI still look reasonable" but "does the RACI still reflect who is actually making decisions and who is actually accountable for outcomes."
When decisions are made in practice by someone who the RACI does not assign as Accountable, there are two possible responses: update the RACI to reflect the actual decision-making structure, or address the variance and restore the agreed structure. Both are legitimate responses. What is not a legitimate response is noting the variance and doing nothing — that is a RACI that has ceased to function as an accountability instrument.
For PMs capturing meeting notes and transcripts, RACI compliance can be tracked continuously — identifying where decisions were made by someone other than the assigned authority, where Consulted parties were bypassed, or where Responsible parties failed to deliver. This turns the RACI from a snapshot into a longitudinal accountability record.