lockstep
4 min readNaman Jain

RACI vs DACI: which one to use, with examples

RACI assigns who does the work; DACI assigns who makes a decision. The roles in each, a side-by-side example, and when a team needs one, the other, or both.

A product team starts a pricing project with a tidy RACI chart. Every task has an owner. Three weeks in, the team is stuck: nobody agrees whether to cap the free plan at three projects or five, and the chart doesn't say who decides. Everyone is Consulted. Nobody is the Approver.

That's the gap between RACI and DACI. They look alike, four letters and four roles, but they answer different questions. This guide compares them and shows when to use each.

The short answer

RACIDACI
AnswersWho does what on this work?Who decides this, and how?
UnitA task or deliverableOne decision
RolesResponsible, Accountable, Consulted, InformedDriver, Approver, Contributors, Informed
Final sayAccountable: answers for the outcomeApprover: makes the call
LifespanThe whole projectUntil the decision is made
Typical homeA project plan or spreadsheetA decision page

RACI: roles for work

A RACI chart, also called a responsibility assignment matrix, gives each stakeholder one of four roles for each task or deliverable:

  • Responsible: does the work.
  • Accountable: ultimately answerable for the result.
  • Consulted: asked for input before or during the work.
  • Informed: kept up to date.

The common rule, per the responsibility assignment matrix convention, is exactly one Accountable per task or deliverable. RACI shines when the work is clear and the risk is dropped balls: tasks with no owner, or owners who didn't know.

DACI: roles for a decision

DACI gives one decision four roles. Atlassian's DACI play defines them:

  • Driver: gets the decision made, gathers stakeholders and input.
  • Approver: the one person who makes the decision.
  • Contributors: experts who give input but don't vote.
  • Informed: people affected who need to know the outcome.

The play stresses one Approver per decision, an active decision-maker rather than a rubber stamp. DACI shines when the work is blocked by a choice: two options, strong opinions, and no clear owner of the call. For a full template, see the DACI decision-making template.

The same project, both ways

The free plan pricing project, run with RACI for the work and DACI for its key decision:

RACI for the work

TaskPMEng leadDesignerFinanceSupport
Write the pricing PRDA, RCCCI
Build the project capIAII
Design the upgrade dialogACRI
Update help docsIA, R

DACI for the decision "how many projects on the free plan?"

RolePerson
DriverPM
ApproverHead of Product
ContributorsEng lead, Finance, Designer
InformedSupport, Sales, the rest of engineering

The RACI keeps the project moving. The DACI unblocks it, and records who made the call.

When to use which

  • Use RACI when everyone agrees what to do and the risk is ownership: launches, migrations, recurring processes.
  • Use DACI when the work waits on a decision with real disagreement or cross-team impact.
  • Use both on most projects that matter: RACI for the plan, a DACI for each significant decision inside it.
  • Use neither for small, reversible calls a single owner can make. A framework for every decision slows a team down.

Common mistakes

  1. Two Accountables or two Approvers. Shared final say means no final say.
  2. Everyone Consulted. If ten people must weigh in, the decision stalls. Contributors give input; they don't vote.
  3. Using RACI for a decision. It says who is accountable for a task, not who decides between options.
  4. Forgetting Informed. The decision is made, but the people building against it never hear. That's how teams end up shipping the option that lost.

After the decision

DACI ends when the Approver decides. The decision then has to reach everyone in the Informed column and stay findable after the project closes. Write it in a decision log, with the Approver as owner, the reason, and the options rejected. See the decision log template.

Where Lockstep fits

Lockstep covers the step after the Approver says yes. It captures decisions from PRDs, Slack threads, and pull requests, routes each to its owner for one-click approval, and then briefs the people and AI coding agents building against it, so Informed actually means informed. When the decision changes, the new version replaces the old one and the old one stays visible.

See how it works.

Sources checked 16 November 2026

For the DACI template in full, see the DACI decision-making template. For scoring options, see the decision matrix template. For the wider set of frameworks, see product decision-making frameworks. For logging the outcome, see decision log vs ADR. For a fillable RACI chart, see the RACI chart template. For identifying who should be Informed, see the stakeholder map template.

Frequently asked questions

What is the difference between RACI and DACI?
RACI assigns roles for work: who does it, who is accountable, who is consulted, and who is informed, across a project's tasks and deliverables. DACI assigns roles for a single decision: who drives it, who approves it, who contributes input, and who is informed of the outcome.
When should I use DACI instead of RACI?
When the hard part is making a decision rather than doing the work. If people disagree about what to build, which option to pick, or who has the final say, DACI makes that explicit. If the question is who owns which tasks, RACI fits.
Can a team use RACI and DACI together?
Yes. Use a RACI chart to run a project and a DACI for each significant decision within it. The project lead might be Accountable for delivery in the RACI and the Driver of a scoping decision in a DACI, with a product leader as Approver.
How many Accountable or Approver roles should there be?
One. The RACI convention is a single Accountable per task or deliverable, and Atlassian's DACI play specifies one Approver per decision. Two people with the final say means nobody has it.
What does the A mean in RACI and DACI?
In RACI, A is Accountable: the one person ultimately answerable for a task or deliverable. In DACI, A is Approver: the one person who makes the decision. The letters overlap but the jobs differ: one owns an outcome, the other makes a call.

Keep reading