RACI matrix for project managers and business analysts
RACI (Responsible, Accountable, Consulted, Informed) is the most-used responsibility-assignment matrix in business analysis and project management. This page covers what RACI is, how to build one, the variants (RASCI, RACI-VS, DACI), and how to anchor the matrix to a BPMN process map so each cell points at the step it governs.
By Jack Finnegan · Updated 21 May 2026
What a RACI matrix actually is
Most RACI matrices have three As per row and live in a Word doc
Four pieces of a working RACI
Rows are deliverables, not tasks
Rows should be the things the team delivers or decides - "approve the design", "sign off the budget", "ship the release". Activities at the granularity of "have a meeting" produce useless matrices.
Columns are roles, not people
A RACI by named individual breaks the moment someone leaves. Use roles ("Engineering Manager", not "Alice"); the matrix outlives the headcount.
Exactly one A per row
This is the non-negotiable rule. If two roles are Accountable for the same outcome, nobody is. Resolve the political conversation at construction time, not at delivery time.
Anchor to a process map
Each row should point at a step or decision in the BPMN process map. Without that anchor the matrix is abstract; with it, RACI becomes a working artefact stakeholders can navigate.
Building a RACI as a process
The construction flow itself - list deliverables, list roles, assign letters, validate the rules, review, publish.
Building a RACI matrix as a process map
The canonical RACI-matrix-construction process rendered as BPMN 2.0. List deliverables, list roles, assign R/A/C/I per cell, validate the "one A per row" rule, review with stakeholders, and publish.
- List the deliverables, decisions, or tasks the RACI needs to cover.
- List the roles (not named individuals - roles) that participate in the work.
- For each (deliverable × role) cell, assign R, A, C, I, or leave blank.
- Validate the rules: exactly one A per row; at least one R per row; no role can be everything everywhere.
- If a violation is found, route back to assignment. Otherwise continue to review.
- Review with stakeholders, capture sign-off, and publish the matrix alongside the process map.
Frequently asked questions
What is a RACI matrix?
A RACI matrix is a responsibility-assignment matrix that maps deliverables (rows) against roles (columns), with each cell carrying one of R (Responsible - does the work), A (Accountable - owns the outcome, exactly one per row), C (Consulted - two-way input before the work), or I (Informed - one-way notification after the work). The Business Analysis Body of Knowledge (BABOK Guide) and the PMBOK Guide both treat it as a standard project-management technique.
What's the difference between Responsible and Accountable?
Responsible (R) is the role that does the work. Accountable (A) is the role that owns the outcome - "the buck stops here". The rule is that exactly one role is Accountable per row; multiple roles can be Responsible. In small teams the R and the A are often the same person; in larger organisations they diverge - the engineer is Responsible for shipping the feature, the engineering manager is Accountable for whether it ships on time.
What are RASCI, RACI-VS, and DACI?
RASCI adds Support (S) for roles that help the Responsible role execute - useful when a deliverable needs cross-team assistance without diluting accountability. RACI-VS adds Verifies (V - checks the deliverable meets criteria) and Signs-off (S - the final authority). DACI replaces the four letters with Driver, Approver, Contributor, Informed and is popular in tech product management because it makes the decision-driver explicit. Pick one variant and use it consistently.
How is a RACI different from a swimlane diagram?
A swimlane (BPMN) diagram shows who does what when - the temporal flow of work across roles, with handoffs visible as message flows between lanes. A RACI is a static matrix - it shows who plays which role for each deliverable, without the time dimension. The two are complementary: the swimlane shows the dynamics; the RACI shows the static accountability for each outcome. The strongest project-management artefacts use both together.
When should you build a RACI?
RACI is most valuable in three situations: cross-team programmes where accountability is genuinely unclear; new-process rollouts where the team is learning who owns what; and post-incident reviews where unclear accountability contributed to the incident. For small, established teams running familiar work, the overhead is usually not worth the benefit - a one-paragraph note saying 'Alice owns shipping this' achieves the same thing.
Does BA Copilot replace our existing project-management tool?
No. BA Copilot is the modelling layer - it produces the BPMN process maps that RACI rows can anchor to. Project-management tools (Jira, Asana, Smartsheet) own the actual work tracking; BA Copilot produces the diagram that gives the RACI structure its meaning.
14 Years in BPMN
I'm Jack Finnegan. I've spent fourteen years working hands-on with BPMN, as an analyst, an engineer, and a product director, where I felt every sharp edge of legacy business process platforms.
BA Copilot is the platform I wanted on every one of these projects: AI-first process management, which treats BPMN as a first-class output rather than an export afterthought.
Anchor your RACI to the process it governs
Open the process the RACI describes, attach each row to the step it governs, and publish both artefacts together. The matrix means more when it sits next to the diagram.