Can the same person be R and A on the same row?

Yes. The doer can also be the owner of the outcome. The distinction matters when the doer and owner are different people, which is common on cross-functional work.

What if we genuinely have two accountable parties?

Then the role design is wrong. Split the row into two decisions, or escalate one level until there's a single accountable party. Two A's is a structural problem, not a RACI problem.

Isn't RACI too bureaucratic for agile?

Only if you build a 200-row matrix and stop there. A one-page RACI on the 20 decisions that recurringly cause friction is lighter than the friction it removes. Agile teams that resist RACI usually rediscover its principles under another name, like decision ownership in a DACI.

How big should a RACI be?

One page, 20–40 rows max. Beyond that nobody reads it. Pick the recurring decisions and tasks that actually cause ambiguity; ignore the rest.

The project manager or PMO owns the document; the named A's own their rows. The owner runs the periodic review and updates after phase gates.

How do we handle RACI across multiple contractors?

Build one cross-vendor RACI for the inter-vendor processes (interfaces, change control, RFI, risk escalation). Each vendor maintains their internal RACI separately. The cross-vendor one is what prevents finger-pointing on the seams.

What happens when an A leaves the project?

Update the matrix immediately; an empty A is worse than an unclear one. If the replacement isn't named, the previous A's manager becomes the A until a replacement is named.

Is RACI mandatory under any standard?

Not by that name, but PMBOK refers to it as a Responsibility Assignment Matrix (RAM), and ISO 21500 / 21502 implicitly require equivalent clarity. Most public-sector tenders expect to see one in the project management plan.

Which calculators on PMMilestone.org apply to RACI Matrix?

For RACI Matrix, the most relevant tools on the flagship platform are the Schedule Health Checker (stage-gate readiness) and EVM Calculator. They reproduce the formulas referenced in this entry against your own project data.

What is a common misconception about RACI Matrix?

That stage-gate sign-off proves readiness. Stage gates only work when the gate criteria include an independent project-controls assessment — schedule health, EVM forecast and a current quantitative risk analysis.

Which related encyclopedia entries should I read alongside RACI Matrix?

Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.

How does Dr. Hassan Eliwa's research treat RACI Matrix?

Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. RACI Matrix is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.

How is RACI Matrix defined on PMMilestone Research & Insights?

A responsibility assignment chart that clarifies, for each task or decision, who is Responsible, Accountable, Consulted and Informed — eliminating the diffuse-ownership ambiguity that kills projects. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

Can the same person be R and A on the same row?

Yes. The doer can also be the owner of the outcome. The distinction matters when the doer and owner are different people, which is common on cross-functional work.

What if we genuinely have two accountable parties?

Then the role design is wrong. Split the row into two decisions, or escalate one level until there's a single accountable party. Two A's is a structural problem, not a RACI problem.

Isn't RACI too bureaucratic for agile?

Only if you build a 200-row matrix and stop there. A one-page RACI on the 20 decisions that recurringly cause friction is lighter than the friction it removes. Agile teams that resist RACI usually rediscover its principles under another name, like decision ownership in a DACI.

How big should a RACI be?

One page, 20–40 rows max. Beyond that nobody reads it. Pick the recurring decisions and tasks that actually cause ambiguity; ignore the rest.

The project manager or PMO owns the document; the named A's own their rows. The owner runs the periodic review and updates after phase gates.

How do we handle RACI across multiple contractors?

Build one cross-vendor RACI for the inter-vendor processes (interfaces, change control, RFI, risk escalation). Each vendor maintains their internal RACI separately. The cross-vendor one is what prevents finger-pointing on the seams.

What happens when an A leaves the project?

Update the matrix immediately; an empty A is worse than an unclear one. If the replacement isn't named, the previous A's manager becomes the A until a replacement is named.

Is RACI mandatory under any standard?

Not by that name, but PMBOK refers to it as a Responsibility Assignment Matrix (RAM), and ISO 21500 / 21502 implicitly require equivalent clarity. Most public-sector tenders expect to see one in the project management plan.

Which calculators on PMMilestone.org apply to RACI Matrix?

For RACI Matrix, the most relevant tools on the flagship platform are the Schedule Health Checker (stage-gate readiness) and EVM Calculator. They reproduce the formulas referenced in this entry against your own project data.

What is a common misconception about RACI Matrix?

That stage-gate sign-off proves readiness. Stage gates only work when the gate criteria include an independent project-controls assessment — schedule health, EVM forecast and a current quantitative risk analysis.

Which related encyclopedia entries should I read alongside RACI Matrix?

Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.

How does Dr. Hassan Eliwa's research treat RACI Matrix?

Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. RACI Matrix is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.

How is RACI Matrix defined on PMMilestone Research & Insights?

A responsibility assignment chart that clarifies, for each task or decision, who is Responsible, Accountable, Consulted and Informed — eliminating the diffuse-ownership ambiguity that kills projects. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

Governance · Letter R

RACI Matrix

A responsibility assignment chart that clarifies, for each task or decision, who is Responsible, Accountable, Consulted and Informed — eliminating the diffuse-ownership ambiguity that kills projects.

By Dr. Hassan Eliwa, PhD · Founder of PMMilestone.org and PMMilestone.com · Updated 2026-06-23

Definition

A RACI matrix is a simple table that maps tasks or decisions on one axis and roles on the other, then marks each intersection with one of four letters: Responsible (does the work), Accountable (single owner of the outcome), Consulted (must be asked before the decision), Informed (must be told after). Done well, it eliminates the diffuse-ownership ambiguity that quietly destroys projects — the "I thought you were doing it" problem.

The Rule That Matters Most

Every row must have exactly one A. If two people are accountable, no one is. If no one is accountable, the row will fail silently. The R, C, and I columns can have multiple entries, but the A column has one — period. Most RACI matrices I review have at least one row with two A's or none; both are bugs to be fixed before the matrix is published.

Real-World Construction Example

On a £300M mixed-use development, the contract was a design-build with three architects, two engineering firms, and a client representative. RFI turnaround had degraded to 18 days, well past the 7-day target. A two-hour RACI workshop produced one table for the RFI process: contractor R (raises), client representative A (owns turnaround), design lead C (consulted on design impact), commercial team I (informed). Once published and enforced, RFI turnaround dropped to 5.4 days within a month. Nothing else changed except clarity.

Real-World IT / Agile Example

Agile teams often resist RACI as too bureaucratic — but the same teams routinely have decisions stall because nobody owns them. On a platform team I worked with, deployment authorisation, customer-impact comms, and post-incident review ownership were all ambiguous. A one-page RACI — product owner A on customer comms, SRE lead A on deployment authorisation, engineering manager A on post-incident — cut mean-time-to-decision in half. The agile framework was unchanged; the ambiguity was gone.

When to Build a RACI

Project kick-off, for the major recurring decisions and processes.
When a decision keeps stalling — that decision belongs in a RACI row.
Cross-functional or multi-vendor work, where ownership is naturally fuzzy.
Hand-overs between phases or teams.
After incidents that traced to ownership ambiguity.

Variants

RASCI: adds Supportive (a role that helps the R deliver).
RACI-VS: adds Verifier and Signatory for governance-heavy processes.
DACI: Driver, Approver, Contributors, Informed — popular at Atlassian for decisions specifically.
CAIRO / RACIO: adds Out-of-loop, useful when scope creep is the problem.

Pick one and stick with it. Mixing variants on the same project just trades one ambiguity for another.

Project Controls Perspective

Controls teams should publish the project's RACI alongside the WBS and the governance charter. We use it to route change-control items, risk owners, and cost-account ownership. A clean RACI shortens the average time-to-decision and makes audit findings easier to close. We track decision turnaround time by process; a RACI is the lever that moves it.

Common Mistakes

Two A's on a row. The most common error. Force a choice; if it can't be made, the role design is wrong.
Too many rows. A RACI with 200 rows is not used; one with 25 is. Pick the decisions and tasks that actually create ambiguity.
Building it alone. A RACI written by the PMO and emailed out doesn't change behaviour. Build it in a workshop with the named people in the room.
Treating it as a one-off artefact. RACI changes as the project changes; review it at every major milestone.
Confusing R and A. The classic confusion: "you do it, I'm responsible." The doer is R; the owner of the outcome is A. They can be the same person; they can be different people.
Too many C's. Anyone who insists on being Consulted on everything is really an A in disguise — or a bottleneck. Push back.

Expert Tips

One A per row is non-negotiable. Make this the rule of the workshop.
Keep it to one page. If it doesn't fit on a page, the audience won't read it.
Name people, not titles, where possible. "Sarah Khan" is clearer than "PMO lead."
Walk the matrix with each named A. If they're surprised by any of their A's, the matrix is wrong.
Revisit at every phase gate. The ownership map for design is different from construction is different from operations.

Key Takeaways

RACI clarifies who does, owns, advises, and is told — for each decision and task.
One Accountable per row. No exceptions.
Build it in a workshop, not in a PMO email.
It is a living document; review at every phase gate.
The construction and software variants of the problem are the same; so is the solution.

Related Encyclopedia Entries

Stakeholder Engagement — companion entry on a directly related concept.
Change Control — companion entry on a directly related concept.
Scope Management — companion entry on a directly related concept.
Risk Management — companion entry on a directly related concept.
Handover Management — companion entry on a directly related concept.
Program Management — companion entry on a directly related concept.

Frequently Asked Questions

Can the same person be R and A on the same row?
Yes. The doer can also be the owner of the outcome. The distinction matters when the doer and owner are different people, which is common on cross-functional work.
What if we genuinely have two accountable parties?
Then the role design is wrong. Split the row into two decisions, or escalate one level until there's a single accountable party. Two A's is a structural problem, not a RACI problem.
Isn't RACI too bureaucratic for agile?
Only if you build a 200-row matrix and stop there. A one-page RACI on the 20 decisions that recurringly cause friction is lighter than the friction it removes. Agile teams that resist RACI usually rediscover its principles under another name, like decision ownership in a DACI.
How big should a RACI be?
One page, 20–40 rows max. Beyond that nobody reads it. Pick the recurring decisions and tasks that actually cause ambiguity; ignore the rest.
Who owns the RACI?
The project manager or PMO owns the document; the named A's own their rows. The owner runs the periodic review and updates after phase gates.
How do we handle RACI across multiple contractors?
Build one cross-vendor RACI for the inter-vendor processes (interfaces, change control, RFI, risk escalation). Each vendor maintains their internal RACI separately. The cross-vendor one is what prevents finger-pointing on the seams.
What happens when an A leaves the project?
Update the matrix immediately; an empty A is worse than an unclear one. If the replacement isn't named, the previous A's manager becomes the A until a replacement is named.
Is RACI mandatory under any standard?
Not by that name, but PMBOK refers to it as a Responsibility Assignment Matrix (RAM), and ISO 21500 / 21502 implicitly require equivalent clarity. Most public-sector tenders expect to see one in the project management plan.
Which calculators on PMMilestone.org apply to RACI Matrix?
For RACI Matrix, the most relevant tools on the flagship platform are the Schedule Health Checker (stage-gate readiness) and EVM Calculator. They reproduce the formulas referenced in this entry against your own project data.
What is a common misconception about RACI Matrix?
That stage-gate sign-off proves readiness. Stage gates only work when the gate criteria include an independent project-controls assessment — schedule health, EVM forecast and a current quantitative risk analysis.
Which related encyclopedia entries should I read alongside RACI Matrix?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.
How does Dr. Hassan Eliwa's research treat RACI Matrix?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. RACI Matrix is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.
How is RACI Matrix defined on PMMilestone Research & Insights?
A responsibility assignment chart that clarifies, for each task or decision, who is Responsible, Accountable, Consulted and Informed — eliminating the diffuse-ownership ambiguity that kills projects. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

View the full FAQ page for RACI Matrix →