DUTYGRAPH FIELD NOTES

RACI matrix: roles and responsibilities, and the work beneath them

What a RACI matrix is, how to build a roles and responsibilities matrix from team evidence, and where the labels stop. Free handoff worksheet.

DutyGraph editorial · Updated November 18, 2026

A RACI matrix records who is Responsible, Accountable, Consulted and Informed for each deliverable or activity. It is for managers and advisors untangling shared work across teams. This guide explains how to build one from evidence, where the labels stop, and how DutyGraph captures R, A, C and I from team interviews.

Download the Handoff Map worksheet · Book a demo

What are the four RACI roles?

Responsible: The person or people who perform the work required to produce the result.

Accountable: The person who owns the outcome and is answerable for the decision or deliverable.

Consulted: People whose input is required before the work or decision is complete.

Informed: People who need the result or status but are not performing or approving the work.

Organizations use these labels differently, so agree the definitions before filling a matrix.

How do you build a RACI matrix?

  1. Name the deliverable or activity, one row at a time. Use the work, not the job title.
  2. Assign exactly one Accountable person per row. If you cannot, the ownership question is the finding.
  3. List the people who perform the work as Responsible.
  4. Add only the people whose input is genuinely required as Consulted. A long Consulted list is usually a slow approval chain.
  5. Add Informed for the people who need the result or the status.
  6. Check each row with the people in it, then record what they corrected.

Step 6 is the one most teams skip. A manager can draft the first matrix, but cross-functional work often looks different from the frontline.

When does a RACI matrix help?

A roles and responsibilities matrix is useful when:

  • several departments touch the same deliverable
  • a task has multiple apparent owners
  • approvals are slowing work
  • nobody knows who should resolve an exception
  • a project keeps returning to leadership for decisions
  • a handoff fails because the next team expected another owner

The matrix makes ambiguity visible. That is its job, and it does it well.

Where does a RACI matrix stop?

Consider a row that says Approve supplier setup — Responsible: Procurement — Accountable: Finance. That does not tell you:

  • what information Procurement receives
  • what counts as a complete supplier package
  • which software is used
  • what happens when bank and legal names differ
  • which checks Finance performs
  • what evidence is retained
  • where a human exception decision is required

Those details are the work itself. A RACI chart shows who participates. A task record explains what the job is.

How do you connect responsibility to duties and tasks?

Use three levels:

Role: the organizational position, such as Procurement Manager.

Duty: the ongoing responsibility, such as maintaining approved supplier records.

Task: a bounded piece of work with a trigger and an output, such as reviewing a new supplier submission before the record is created.

Then attach RACI participation to the specific task or deliverable instead of treating a job title as the process. The roles, responsibilities and tasks worksheet gives you a deeper work-record format.

How does DutyGraph capture R, A, C and I from interviews?

Each person answers a few questions about their own work, by voice or by typing, in about 20 minutes. They describe one recent example: what arrived, what they did, who decided, whose input they needed and who received the result.

Those answers become task cards that the person reviews and corrects. Mapping them produces the same four facts a RACI matrix holds — who performed the work, who owned the outcome, whose input was required, who was informed — attached to a named task rather than to a job title. Where two accounts disagree, the map records the difference as unresolved until the right people decide.

Example: quote-to-order handoff

Illustrative scenario: Sales is Responsible for preparing an accepted order. Sales leadership is Accountable. Finance is Consulted on billing exceptions. Operations is Informed that the order is ready.

The matrix appears clear. But Operations still rejects some orders because delivery contacts and configuration details are missing. The problem is no longer simply responsibility: the sending and receiving teams have different definitions of "ready." The cross-functional handoff guide shows how to add the missing acceptance conditions.

Does a RACI label grant permission?

No. A RACI designation does not grant access to software, authorize a financial decision or approve an AI agent. Organizational responsibility, technical permission and formal authority are separate facts. That distinction matters most when a company starts delegating work to AI.

Common questions

What is the difference between Responsible and Accountable?

Responsible people do the work. The Accountable person owns the result and answers for it. Keep one Accountable person per row; when two people share it, exceptions bounce between them.

Can a person be both Responsible and Accountable?

Yes, and in small teams it is common. Write it down anyway, because the two duties separate as the team grows and the row then needs a new owner.

How is a RACI matrix different from an org chart?

An org chart shows reporting lines. A RACI matrix shows participation in one deliverable. Work that crosses departments follows neither, which is why the handoffs between them need their own record.

What should we do when nobody is Accountable?

Treat the empty cell as the finding. Take it to the leaders of the teams involved, agree one owner, and record the date and the decision beside the task so the next exception has an answer.

Where can we get a template?

Use the free Handoff Map worksheet to capture the work beneath the labels: trigger, inputs, owner, receiving owner and acceptance conditions for each handoff.

From matrix to operating map

If the RACI exposes unclear ownership across several teams, process mapping services can connect responsibility to the actual work and handoffs. If the problem is broader, a business operations audit investigates where ownership and process gaps are creating operating friction. See how pricing works before the call.

The goal is not a prettier responsibility chart. It is a shared understanding of how the work should move.