DACI vs RACI vs RAPID: when you need more
All three frameworks answer the same question (who plays what part in a decision) with different emphasis. Here’s what each one actually means, where each fits, and where every framework stops.
RACI: task responsibility, adapted to decisions
Responsible · Accountable · Consulted · Informed. RACI is the oldest of the three and wasn’t designed for decisions at all. It’s a responsibility-assignment matrix for tasks and deliverables. Exactly one person is Accountable; others execute, advise, or are kept in the loop. Teams adapt it to decisions because it’s familiar, but it has no concept of a decision being made, only of work being owned.
DACI rebuilds RACI for decisions
Driver · Approver · Contributors · Informed. DACI emerged at Intuit in the 1980s as a decision-focused variant of RACI. The Driver moves the decision forward; one Approver makes the call; Contributors bring knowledge; Informed hear the outcome. Its core virtue is the single named approver. Decisions stall when approval is ambient.
RAPID®: decision rights for big organisations
Recommend · Agree · Perform · Input · Decide. RAPID was developed by Bain & Company and popularised in the 2006 Harvard Business Review article “Who Has the D?”. It separates the people who recommend from the one who decides, gives a deliberately narrow veto to Agree (typically legal or compliance), and names who must perform the outcome. It shines in large organisations where recommendation and decision authority sit in different places. (RAPID® is a registered trademark of Bain & Company.)
Side by side
| RACI | DACI | RAPID® | |
|---|---|---|---|
| Built for | Tasks & deliverables | Decisions | Decision rights at scale |
| Single decider | Accountable (implied) | Approver (explicit) | Decide (explicit) |
| Veto concept | No | No | Yes, Agree (narrow) |
| Execution role | Responsible | No | Perform |
| Best fit | Project plans | Product & team decisions | Cross-functional, regulated, large orgs |
Where every framework stops
A framework is a naming convention. It tells you who should play which part. Then it trusts slides, docs, and goodwill to make it happen. In practice:
- Nothing enforces the roles. A decision marked “approved” may never have been seen by the approver.
- Nothing records the decision. The framework names the players; the reasoning still lives in a thread.
- Nothing connects decisions to the strategy above them or the work below them.
- Nothing survives an audit. “We use RAPID” is a process claim, not evidence.
Check what framework support actually means
A product can display your framework’s labels without running the decision process you intended. Compare the actual workflow using one decision from your team.
| Framework | What to verify in the software |
|---|---|
| RACI | Can you distinguish responsibility for doing the work from accountability for it, and explicitly define who approves the decision? |
| DACI | Can the Driver gather contributions while approval remains with the named Approver? Can you inspect that approval afterward? |
| RAPID | Can you distinguish Recommend, Agree and Decide, including the scope of required agreement, without treating every participant as an interchangeable approver? |
Traceway brings the decision, rationale, alternatives, roles and human approval into one shared record, with links to resulting work. Check how the responsibilities and authority in your chosen framework map to that workflow.
Ask the vendor to show the configured roles, the approval event, a later change and the linked work. Check the product and plan you would actually buy. For a comparison of dedicated software and approval workflows in tools you already use, see our decision record and approval software shortlist.
Explore Traceway’s approval governance, or use the worked decision-log example in your evaluation.
What a seven-role model adds
DACERIO, Traceway’s approval model, extends the decision-rights idea to seven roles: Driver, Approver, Consulted, Enabler, Reviewer, Informed, Owner. The additions cover what the classic frameworks leave implicit: an Enabler who clears blockers and provides resources, a Reviewer who checks the record before sign-off, and an Owner accountable for the decision’s life after approval. Decisions don’t end when they’re made.
Traceway is a platform for recording and approving business decisions. When a decision changes, its owners can see which commitments to revisit.
Stop losing the why.
Traceway is the system of record for decisions: AI capture, real governance, an audit-grade trail, and a chain from strategy to the work.
Book a demo