Workplace Communication
DACI or RACI? Separate Decision Authority from Delivery Responsibilities
Two completed role maps for one fictional rollout separate a product-scope decision from owned work packages, mandatory review, and release authorization.
Use DACI to clarify who drives a particular decision, who makes it, whose expertise informs it, and who needs the outcome. Use RACI to clarify who performs and accepts each work package. Write the exact decision question or delivery package before assigning letters. A person coordinating a choice is not automatically responsible for implementing it, and a consulted expert does not acquire general veto power from a chart.
This LandOffer.ai guide applies both frameworks to one fictional internal rollout, then repairs two concrete responsibility conflicts. All people, approvals, assignments, and project records are invented teaching examples. No employer process, account permission, production change, or real launch was assessed or modified.

Start with the question the chart must answer
If the unresolved question is “Who can choose between these rollout options?”, begin with the decision. If it is “Who will prepare the rollback instructions and who accepts them?”, begin with that deliverable. Job titles alone leave those questions open until the team defines the relevant scope and authority.
Atlassian's DACI play defines a Driver who gathers information and moves the decision forward, one Approver who decides, Contributors who provide expertise, and people who are Informed. The framework describes a decision process. Its letters do not establish that your chosen approver actually has budget, technical, or release authority in your organization.
Asana's RACI guide, dated December 3, 2025, maps responsibilities to tasks, milestones, and deliverables. It distinguishes performing the work, accepting the result, providing input, and receiving updates. The completed example below names one responsible lead and one accountable owner per work package. That is this example's explicit convention; teams should define their own use of the letters rather than assume every RACI description handles shared work identically.
The same project can need both kinds of clarity. It does not necessarily need two large documents. A decision note with a small delivery table can be enough if people can find the current owners and understand the boundaries. Keep one current role record so a teammate joining the project can identify the authority for a question without reconciling conflicting charts.
Keep the meaning of each letter beside its scope
DACI's A means Approver for the named decision. RACI's A means Accountable for a named activity or deliverable. Those roles can belong to the same person, but matching letters are not proof that they should. A product owner can choose a pilot scope while an engineering lead accepts implementation work and a release owner authorizes deployment.
Likewise, a DACI Driver coordinates the decision rather than performing every downstream task. A RACI Responsible lead performs or coordinates the defined work package. They need an agreed deliverable, relevant access, time, and a route for resolving questions; the chart itself supplies none of those resources.
Atlassian's documented use of RACI for security incidents distinguishes the party doing work from the party answerable for its completion, two-way consultation, and one-way information. Only those role definitions are relevant here. Its security obligations, customer agreement, incident roles, and operational procedures do not transfer to the fictional rollout.
Describe consultation concretely. “Ask the documentation specialist whether the instructions match the workflow” is different from “obtain mandatory security acceptance.” If a real policy requires a specialist's sign-off, preserve that gate explicitly. Calling the specialist C in a broader business-choice note does not remove their separate authority over a required review.
Worked asset: one rollout, a bounded DACI decision
In the fictional case, an internal design portal will show a small catalog of approved font packages. The team is choosing whether to pilot it with two design teams or open it to all internal teams immediately. This is a rollout-scope choice, not permission to distribute fonts externally or bypass licensing, access, or release checks.
Owen owns product scope. Eda is the engineering lead. Selene owns release authorization. Quinn coordinates preparation and implements the catalog configuration. Bo maintains the operational instructions. Akari owns the required access-review acceptance under this invented team's process. The two pilot-team representatives are consulted before committing their teams to participation; they have not accepted a date yet.
Quinn completes decision note D-19:
Question: should we prepare a two-team pilot or an immediate organization-wide rollout for the approved-font catalog?
Boundary: choose the preparation scope only. All required access review, technical acceptance, participating-team agreement, and release authorization remain separate. A preference for a pilot does not authorize enabling it.
Options: prepare a limited two-team pilot with a defined support route, or prepare broad internal availability with wider support and communications requirements. The team has not established support capacity for the broad option. Neither option includes external sharing or new font-license rights.
Decision date: October 7, after the named contributors provide their scoped input. If required input is missing, record the gap and defer or narrow the choice rather than mark an unanswered request approved.
Quinn records these confirmed DACI assignments:
| DACI role | Named person or group | What this role means for D-19 |
|---|---|---|
| Driver | Quinn | Collect scope options, contributor input and unresolved questions; bring a decision-ready note to Owen |
| Approver | Owen | Choose the preparation scope within his product authority; cannot waive other gates |
| Contributors | Eda, Selene, Bo, Akari, and the two proposed pilot representatives | Explain feasibility, release conditions, operational support, required access review, and participation constraints respectively |
| Informed | Internal design-portal support group | Receive the recorded scope choice and open conditions; no implementation assignment created by being informed |
The participants confirm the listed roles for this question. Akari confirms that contributing review conditions to D-19 is distinct from accepting the later access-review deliverable. Selene confirms that she is not the second approver of product scope; her release authority remains intact.
At the fictional October 7 discussion, Owen chooses preparation for the two-team pilot; no configuration or release result is established by that choice. Bo's input has exposed the unconfirmed broad-support capacity, so organization-wide availability is deferred. The note states that the pilot representatives still need to accept participation and timing. It does not describe the pilot as scheduled, tested, or released.
Map the resulting work with RACI
The scope choice now creates work that needs owners. Quinn cannot assume that everyone consulted will perform it. The team uses the following compact RACI convention: one named responsible lead coordinates each package, one accountable owner accepts that package's result, consulted people supply defined input, and informed people receive its status. Supporting contributors can work under the responsible lead without disappearing from the work plan.
| Work package | Responsible lead | Accountable owner | Consulted | Informed |
|---|---|---|---|---|
| Prepare catalog configuration and technical checks | Quinn | Eda | Akari, Bo | Owen, Selene |
| Complete required access review | Akari | Akari | Quinn, Eda | Owen, Selene, Bo |
| Prepare support and rollback instructions | Bo | Eda | Quinn, Selene | Owen, Akari |
| Confirm pilot participation and proposed timing | Quinn | Owen | Two pilot representatives, Bo | Eda, Selene |
| Assemble release evidence and request authorization | Quinn | Selene | Eda, Akari, Bo | Owen and accepted pilot representatives |
Akari holds R and A for the access review in this example. That reflects the invented team's accepted process; it is not a recommendation to combine preparation and acceptance when an actual policy requires independent review. Similarly, Selene accepting the release-evidence package does not make an incomplete access review acceptable.
Each owner accepts the assignment. Eda allocates Quinn two preparation days by deferring an optional catalog-layout experiment. Bo accepts a half-day instructions package within an existing support allocation. Akari accepts reviewing the submitted configuration after Quinn supplies the required evidence, but has not promised an acceptance result. These allocations fund preparation; they are not a project completion estimate.
The table also needs sequencing. Technical and access-review evidence, support instructions, and pilot participation must be ready before Quinn requests release authorization. If a prerequisite remains open, the release row stays blocked. A RACI table assigns relationships; it does not by itself model those dependencies or reserve a deployment window.

Repair overlapping authority and an unowned step
The first draft of D-19 listed both Owen and Selene as A for “approve rollout.” That wording combined two different choices: which audience to prepare for and whether the actual configured change was ready to enable. Their apparent disagreement about who decides was partly a disagreement about the question.
Quinn brings the ambiguity to both people. Owen says, “I can choose the pilot scope, but I cannot authorize deployment.” Selene replies, “I own the release gate, not whether product should fund broad availability. I need completed evidence before I can decide about enabling anything.” They replace the combined row with the separate DACI scope question and the RACI release package above.
This repair retains a single approver for D-19 while preserving another legitimate decision elsewhere. It does not solve the problem by downgrading Selene to someone whose required release decision can be ignored. If both people really had authority over the same indivisible decision, Quinn would need the appropriate governance owner to clarify that authority rather than assign a preferred letter unilaterally.
The second conflict concerns rollback instructions. Quinn thought Bo would write them because Bo had reviewed the operational approach. Bo thought Quinn would write them because Quinn knew the configuration. The first chart listed both as C, leaving no responsible lead and no person accepting the package.
They complete this repair record:
| Gap in the first draft | Confirmed repair | What remains pending |
|---|---|---|
| Owen and Selene both A for an undefined “approve rollout” | Owen approves preparation scope in D-19; Selene owns the separate release authorization after required evidence | Release decision has not been requested or made |
| Quinn and Bo both consulted on rollback instructions; no owner | Bo accepts R for the instructions, Quinn supplies configuration detail, and Eda accepts A for reviewing the package | Bo's completed instructions and Eda's acceptance are future work |
| Akari listed as a contributor in the scope note | Preserve that consultation and retain Akari's separate required access-review row | No access acceptance can be inferred from consultation or silence |
Bo accepts delivering the instructions draft by October 12 at 16:00 UTC. Quinn accepts supplying the relevant configuration detail by October 9 at noon UTC. Eda accepts a review on October 13. If Quinn's input is late or changes the rollback boundary, Bo will flag the impact to Eda and propose a revised date; he does not silently inherit unlimited extra work.
Keep the decision and delivery status distinct
Quinn updates the common record after the role discussion: D-19's preparation-scope choice is accepted; the delivery table is confirmed; implementation checks, access acceptance, support instructions, pilot participation, and release authorization are all pending. The team has clarified ownership, not completed the rollout.
At the next status review, Bo should identify whether the instructions draft is written and ready for Eda to review; Eda should separately record whether that package is accepted within her authority. The other work packages need the same distinction. “Consulted,” “review requested,” “review completed,” and “accepted” describe different events. A link sent to Akari is not an access approval, and Owen's scope choice is not Selene's release decision.
Review the chart when scope, staffing, or required gates change. Before using either framework, write one precise decision question or deliverable, confirm the authority and capacity of its named owners, and preserve the dependencies that the letters cannot express. Save the confirmed role record with the decision and delivery packages, including outstanding inputs, accepted dates, and the person who must resolve any remaining authority gap. More workplace guides are available through LandOffer.ai.
Sources and Further Reading
- Atlassian Team Playbook: DACI — Driver, one decision Approver, Contributors, and Informed roles.
- Asana: Your guide to RACI charts — December 3, 2025; task and deliverable responsibility definitions and review of missing owners.
- Atlassian: Security incident responsibilities — RACI role definitions only; the security-service obligations are outside this article's example.


