RACI Chart Template Builder: Roles for One Real Decision

The row everyone signed

Picture a project kickoff — a composite of a common scene. The RACI chart runs to forty rows: draft the business case, run the customer survey, update the forecast. Row thirty-one reads “Approve go/no-go.” Four people are marked A. Everyone signed the chart, and nobody noticed that the only row that mattered had four owners.

This builder starts from the decision, not the task list. Ten fields take you through the choice, the date, the model, one decider, the person who drives it, the few who must agree, who gives input, who carries it out, who is told and how disagreement gets settled. Checks flag the usual faults. You leave with a one-page chart to send round before the analysis starts.

The live comparison of the three models makes the case that RACI charts fail because they assign tasks when the fight is over a decision. This tool is the practical end of that argument: write the decision as a choice first, and the letters come after.

Write the decision before the letters.

The three models in one table

The roles line up more than the letters suggest. The RAPID entries follow Bain's definitions ¹; the DACI and RACI entries follow Atlassian's Team Playbook, which treats RACI as a variation in which Accountable is the final approver of the work ². For RACI on its own, see the RACI matrix page.

The tool asks for every job, whichever model you pick, because a chart that leaves a job out does not make the job disappear. It just leaves it to whoever grabs it.

What the checks catch

The checks are our rules of thumb, built on what the model publishers say. They warn; they never block.

• A task where the decision should be. “Prepare the pricing deck” is work. “Whether to raise list prices in July” is a decision. Only a decision needs a decider.
• More than one decider. Atlassian calls the Approver “The one person (yes: one!) who makes the decision” ²; Bain says “Ideally, there should only be one decider for each decision” ¹. If a group truly holds it, Bridgespan advises the group to settle in advance how it will decide, for example by majority vote, or by consensus with the chair deciding if members cannot align ³.
• Too many gatekeepers. Bain: “Agree roles are assigned sparingly and may not be needed for all decisions” ¹. Bridgespan adds that having the A means helping the recommender reach a viable recommendation, “not to veto a decision after it has been made” ³. The tool warns above two.
• Performers left out of the input. Bridgespan suggests naming who has the P early and giving them an I, so implementation concerns shape the recommendation ³.
• No date and no tiebreak. A decision with neither drifts until someone senior notices.

A worked chart

The chart is a map of power

Bridgespan's guide says it plainly: mapping how decisions are made exposes the ways in which power flows through the organization, and some leaders prefer to leave control of certain issues ambiguous ³. That is why the four-A row happens. Nobody misread RACI. Each person wanted to keep the right to stop the decision without saying so.

The fair objection is that ambiguity sometimes helps, early in an exploration, before anyone knows the options. Then do not publish a chart. Write “decider to be named by” and a date. A chart that names a decider while a senior leader keeps what Bridgespan calls a veto “in their pocket” ³ is worse than no chart, because it teaches everyone that the chart is fiction.

In organizations that regularly use RAPID, people often ask “Who has the D?” ³, which is also the title of Paul Rogers and Marcia Blenko's 2006 Harvard Business Review article ⁴. Ask it before the analysis starts, out loud, of the people who could stop the decision. For what happens once the room is in session, see getting a room to decide. The letters are cheap. The agreement is the chart.

Questions

What should a RACI chart template include?

For work, a list of tasks and, for each, who is Responsible, Accountable, Consulted and Informed. For a decision, start with the decision written as a choice and a date, then name one person who makes the call, who drives it, who must sign off, who advises, who carries it out, who is told and how disagreement is settled.

Can a RACI chart have more than one Accountable?

For a decision, it should not. Atlassian's DACI play insists on one Approver, and Bain says there should ideally be one decider per decision. If a board or committee truly holds the decision, write down in advance how it will decide, such as a majority vote or consensus with the chair breaking ties.

Should I use RACI, DACI or RAPID?

Use RACI to assign the work once a decision is made. Use DACI for a team or project decision one person can approve. Use RAPID when the decision crosses units and some people, such as finance or legal, must sign off before it goes forward. Many big decisions use RAPID to decide and RACI to deliver.

Where to go next

• RACI vs. RAPID vs. DACI: Which Decision Model, When
• Getting a Room to Decide: A Decision-Making Framework
• Stakeholder Mapping for Strategy Work
• Decision Log