RACI vs DACI: Which Framework Fits Your Team?

RACI and DACI both name who does what, but they answer different questions. RACI shows who is responsible for a task and who is accountable for its result. DACI shows who drives a decision, who approves it, who contributes and who is kept informed. Use RACI to organise delivery across a project. Use DACI when a specific decision keeps stalling, and you need one named person to make it by a set date.

The rest of this guide sets out the roles, the differences, worked examples and a simple way to choose. It is written for owners and managers of small and mid-sized businesses who want fewer meetings and clearer ownership, not a bigger process.

TL;DR

• RACI (Responsible, Accountable, Consulted, Informed) maps ownership of tasks and deliverables across a project.
• DACI (Driver, Approver, Contributors, Informed) maps roles in a single decision, with one Approver who has the final say.
• Both rely on one clear owner: one Accountable person in RACI, one Approver in DACI.
• Use RACI for ongoing delivery and handovers, DACI for one-off or contested decisions, and both together on larger projects.
• Agree the roles at the start, write them down, and revisit them when the project changes phase.

Table of Contents

• What RACI and DACI each mean
• The roles side by side
• Responsible vs accountable: the distinction that causes most confusion
• A RACI example
• A DACI example
• How to assign roles in each framework
• When to use RACI, when to use DACI
• Common mistakes
• Our perspective
• Putting this into practice with us
• FAQ
• Sources

What RACI and DACI each mean

Both are responsibility-assignment tools. They put names against roles so that nobody has to guess who is doing the work, who signs it off and who needs to hear about it.

RACI

UK Government security guidance defines RACI as Responsible, Accountable, Consulted and Informed and recommends adapting a RACI matrix to clarify inputs and expectations on a project. The Department for Transport’s Street Manager team describes it in plain terms: Responsible delivers the work, Accountable owns completion and sign-off, Consulted gives two-way input, and Informed receives updates.

DACI

DACI is narrower. One widely used definition has it as Driver, Approver, Contributors and Informed, a framework for clarifying stakeholders’ roles in making a decision. Some guides use Accountable in place of Approver, as in this explainer, which describes the DACI chart as a matrix of each person’s part in decisions on major project tasks, distinct from the project plan. The letters differ slightly between sources, but the logic is the same: a Driver runs the process, and one person decides.

The roles side by side

The comparison from Project Management.com captures the core difference well: RACI emphasises who is responsible for a task and accountable for its result, while DACI emphasises driving a decision and approving its output. In DACI the Driver leads the process, but the Approver holds final authority.

Responsible vs accountable: the distinction that causes most confusion

Most RACI problems start here. Cornell’s IT service management guidance defines Responsible as the person or team responsible for correct execution, and Accountable as the single person who owns quality and the end result and makes sure resourcing and participation are adequate. It also specifies only one Accountable person per task, deliverable or decision.

The University of Leeds adds a useful test: accountability cannot be delegated, whereas responsibility can be. If a junior colleague drafts a client proposal, they are Responsible for the draft. The director who signs it off stays Accountable if it goes wrong.

Two practical consequences follow:

• When two people are both marked Accountable, neither fully is. Pick one.
• The same person can be both R and A on a small task. That is fine in a ten-person firm, and often sensible.

DACI sidesteps the confusion by splitting the roles by function. The person who runs the process (Driver) and the person who decides (Approver) have different names, so nobody mixes up doing with deciding. In DACI, Atlassian’s guidance maps Responsible to those who complete the work and Accountable to the final approver, with Consulted and Informed keeping roughly the same meaning.

A RACI example

A practical RACI matrix is a grid with deliverables down the left and roles across the top, and each cell marked R, A, C or I. Mastt’s template shows a full version for an aquatic-centre redevelopment, with 18 deliverables across 11 roles. For a university example closer to home, Keele’s systems-architecture page gives an indicative RACI for initiation and concept requirements analysis.

Here is a smaller illustration for a professional services firm launching a new client onboarding process. The names and assignments are ours, for demonstration only.

Notice what makes it work. Every row has exactly one A and at least one R. Cells that do not apply are blank rather than filled with a defensive I. The practical guidance on RACI matrices recommends exactly these checks, along with circulating the matrix for confirmation and revisiting it at phase gates.

A DACI example

A DACI plan names a Driver to gather information and facilitate the meeting, one Approver (typically a manager or leader), Contributors with relevant knowledge, and the affected people as Informed, as set out in the Atlassian playbook. Contributors have a voice but no vote. Informed stakeholders receive the outcome and have neither.

Project Management.com’s marketing example assigns a project manager as Approver for writing a blog, an expert writer as Driver, a content director as Contributor, and graphic design and web development as Informed.

A decision a small firm might face looks like this. Again, this is an illustration, not a case study.

• Decision: Which client management system do we move to this year?
• Driver: Operations lead, who gathers requirements, books the demos and sets the decision date.
• Approver: Managing director, who makes the final call.
• Contributors: Account managers, finance, and whoever administers the current system.
• Informed: The wider team, told the outcome and the rollout timetable.

The Driver’s job matters more than it looks. In DACI the Driver corrals stakeholders, gathers information, defines the scope and drives the decision to an agreed date. Most stalled decisions have no Driver, only a lot of interested people.

DACI also works for decisions that arrive under pressure. Think of an on-call team deciding whether to escalate or roll back during a service disruption: the roles of Driver, single Approver, Contributors and Informed stakeholders apply just as well there, as this look at incident response for on-call teams shows in its own setting.

How to assign roles in each framework

Setting up a RACI matrix

1. List the activities and decisions down the left, and stakeholder roles across the top. This is the layout the University of Leeds recommends.
2. Assign R, A, C or I to each cell.
3. Check each row for one A only and at least one R.
4. Agree it with stakeholders before the work starts. The University of Essex advises agreeing the matrix with stakeholders before the project begins.
5. Revisit it as phases change. GOV.UK guidance recommends starting the exercise at the beginning and continually reassessing roles as requirements shift through delivery.

Setting up a DACI decision

Plane’s guidance outlines a practical sequence, which we would adapt like this:

1. Write the decision as a single sentence, with its scope.
2. Name the Driver, the Approver, the Contributors and the Informed group.
3. Gather input from Contributors, in writing where possible.
4. Set a deadline for the decision.
5. Let the Approver decide. No vote, no committee.
6. Record the outcome and the reasoning, and tell the Informed group.

The record matters. A decision that lives only in someone’s memory gets reopened in three months.

When to use RACI, when to use DACI

Choose by the problem you have, not by which acronym is more fashionable.

Use RACI when:

• the work is a repeating process or a project with many deliverables;
• handovers between teams keep dropping;
• you need to see capability gaps. GOV.UK’s Secure by Design workshop says agreeing RACI responsibilities helps teams assign ownership, identify skills and resource gaps, and give people responsibility for mitigating risk.

Use DACI when:

• one decision is stuck and several people think it is theirs;
• the choice crosses teams and needs a single owner and a date;
• you want a short written record of who decided what and why.

Use both when a project is large enough to need a delivery map and also contains a handful of decisions that could derail it. RACI covers who delivers what. DACI covers the five or six decisions that shape the delivery. Do not make DACI cards for every minor choice, or you will have replaced one kind of overhead with another.

Other variants exist, such as RASCI, which adds a Supporting role, but we would start with the simpler pair and only add letters if a real confusion appears.

Common mistakes

• Too many Approvers. A decision with three signatories is a committee. If you cannot name one, the real question is who in the business has authority over the issue.
• Everyone is Consulted. If every row has a C for everyone, you have recreated the meeting you wanted to avoid. Consult people whose input changes the outcome.
• Informed as a safety net. Marking people I to avoid offending them fills the grid with noise.
• A matrix nobody uses. A RACI chart filed in a shared drive and never opened is decoration. Put it where the project is run and refer to it in status meetings.
• Setting roles once. People change jobs, scope grows, and phases end. Revisit the roles.
• Naming departments, not people. A role held by a team is a role held by nobody. Name an individual for A and for the Approver.

These are mostly alignment problems rather than tool problems. Our piece on getting cross-functional teams pulling together covers the wider picture, and judgement before execution explains why settling who decides comes before doing the work.

Our perspective

We work with small and mid-sized businesses and founder-led professional services firms, and the pattern is consistent. Teams rarely lack effort. They lack a shared answer to who decides, and that gap costs more than most budget lines.

We treat RACI and DACI as capability tools, not paperwork. A growing firm usually begins with the founder making every call, then adds people, and then finds that decisions slow or get remade. Naming one Approver for each important decision, and one Accountable owner for each deliverable, is often the cheapest improvement available. It needs no software, only a conversation and a page of notes.

Our advice is to start small. Pick the three decisions that most often stall, write a DACI line for each, and run a RACI only for the one project that matters most this quarter. Once the habit holds, extend it. If you are deciding what to tackle first, choosing what to build next and capability mapping around one decision set out how we sequence that work.

The frameworks do not replace judgement. They make it visible, so that the person who decides can be held to the decision and the people who contribute can see their input counted.

— Chris

Putting this into practice with us

If you would rather build this capability with support than on your own, our staged approach starts with a launch-ready foundation in about a month, described in how we deliver a Foundation in four weeks. It then moves toward ongoing managed capability. Managed Capability is listed at £999 per month, £2,850 per quarter or £10,000 per year, and you can see every option on our pricing page. To talk through where decision ownership is breaking down in your business, book a discovery call.

FAQ

Is DACI a replacement for RACI?

No. They answer different questions. RACI assigns ownership of tasks and deliverables, while DACI structures a single decision around a Driver and one Approver. Many teams use RACI for the project and DACI for its key decisions.

Can one person be both Driver and Approver?

In a very small team, yes, and it is better than leaving the decision unowned. As the group grows, separate them. The Driver’s job is to gather input and keep the process moving, and the Approver’s is to decide, so splitting the two helps the decision feel fair and avoids it being bottlenecked on one person.

How many people can be Accountable in a RACI?

One per task, deliverable or decision. Cornell’s guidance is explicit on this. If you find two candidates, either split the task into two rows or decide which person has the authority to sign it off.

When should we set up the matrix?

At the start of the project, before work begins, and with the people named in it. Then review it whenever scope or phase changes, as GOV.UK guidance recommends.

Sources

• Agreeing roles and responsibilities, UK Government Security
• RACI guidance, Department for Transport Street Manager
• What is DACI: An Explainer, Capterra
• DACI: A Decision-Making Framework, Atlassian Team Playbook
• DACI vs. RACI Model Guide, Project Management.com
• DACI Decision-Making Framework, Project Management.com
• RACI and RASCI Definitions, IT@Cornell
• RACI Process, University of Leeds
• Responsibility matrix, University of Essex
• Secure by Design Resources Workshop, GOV.UK
• RACI Matrix Template, Mastt
• Systems architecture RACI example, Keele University
• What is a DACI framework, Plane
• Incident response for on-call teams

Recommended

• Capability Mapping for Strategists: Build Around One Decision
• Cross-Functional Alignment: How to Get Teams Pulling Together