RACI Chart Template: Examples, Rules and a Free Builder
A RACI chart is a grid with tasks or decisions down the side, roles across the top, and one letter in each cell: R for the people who do the work, A for the one person who owns the outcome and signs it off, C for those whose input is needed before the work is done, and I for those who are told afterward. It takes an afternoon to build and settles the question that stalls most projects, which is who decides. Gallup's 2025 data found only 47% of US employees strongly agree they know what is expected of them at work, down nine points since 2020; a RACI does not fix that alone, but it makes the gaps visible.
Below: a builder that produces a RACI and checks it against the rules, the rules themselves, two worked examples from HR projects, how to run the workshop that fills it in, the variants (RASCI, DACI, RAPID and others) and when to use them, and the mistakes that turn a RACI into shelfware. For defining roles more broadly, see roles and responsibilities; for the project plan the RACI sits inside, the project plan template.
RACI builder and checker
The checker flags rows with no A or more than one A, rows with no R, rows that are all C and I, and roles that are accountable for too many items or appear nowhere. It runs in your browser; nothing is sent anywhere.
What R, A, C and I mean
| Letter | Role | Question it answers | How many per task |
|---|---|---|---|
| R | Responsible: does the work | Who is doing it? | One or more |
| A | Accountable: owns the outcome, approves the result, answers for it | Who decides, and whose name is on it? | Exactly one |
| C | Consulted: gives input before the work is finished; two-way | Whose expertise or agreement do we need first? | As few as possible |
| I | Informed: told after a decision or milestone; one-way | Who needs to know? | As needed |
The distinction that matters most is between A and R. The accountable person may delegate the work but not the ownership; when a deliverable is late or wrong, the A is the one who explains it. The distinction between C and I matters second: consulting someone means waiting for their input, so every C added to a row slows it.
The rules
- One A per row. Two accountable people means none. If two leaders genuinely share a decision, the task is really two decisions; split it.
- At least one R per row. If the A will also do the work, mark the cell A/R.
- Rows are deliverables or decisions, not activities. "Select the vendor" works; "vendor stuff" does not.
- Columns are roles, not people. People change; roles survive reorganizations. Add names in a legend.
- Keep Cs to the minimum. A row with five Cs is a committee.
- Check the columns as well as the rows. A role with As on half the chart is a bottleneck; a role with only Is may not need to be on the chart; a role with no letters should be removed.
- The A should have the authority. Accountability without decision rights, budget or the ability to say no is blame, not ownership.
Worked examples
Example 1: rolling out a time-tracking system (the default in the builder above).
| Task | HR Director | Payroll Manager | IT Lead | Finance Controller | Legal | Line Managers |
|---|---|---|---|---|---|---|
| Select the vendor | A | C | C | C | - | I |
| Check state monitoring and notice laws | A | - | - | - | R | - |
| Configure pay rules, rounding and overtime | C | A/R | R | C | - | - |
| Write and send the employee notice | A/R | - | - | - | C | I |
| Run two parallel payrolls | I | A | R | C | - | - |
| Train managers | A | C | R | - | - | I |
| Approve go-live | A | C | C | C | C | I |
The chart makes three choices visible that teams often leave implicit: Legal is responsible for the notice-law check but HR owns it; Payroll owns the pay rules even though IT keys them; and line managers are informed, not consulted, on the vendor choice. Each is arguable, which is the point. The time tracking rollout guide covers the sequence.
Example 2: annual performance review cycle.
| Task | CHRO | HR Business Partner | Manager | Employee | Calibration Committee |
|---|---|---|---|---|---|
| Set the review calendar and form | A | R | C | I | - |
| Complete self-evaluation | - | I | I | A/R | - |
| Write the manager review | - | C | A/R | - | - |
| Calibrate ratings | I | R | C | - | A |
| Deliver the review conversation | - | C | A/R | I | - |
| Approve pay changes | A | R | C | I | C |
See the performance review template and self-evaluation examples for the documents each row produces.
How to fill it in: a one-hour workshop
- Before: list the deliverables and decisions from the work breakdown structure or project plan (10 to 25 rows) and the roles involved (4 to 8 columns). Send both in advance.
- First 10 minutes: agree the definitions above, especially the one-A rule.
- Next 30 minutes: go row by row. Assign the A first, then the R, then C and I. Disagreements about the A are the most valuable part of the hour; resolve them in the room or escalate them with a deadline.
- Next 10 minutes: read the columns. Who is overloaded? Who is missing?
- Last 10 minutes: confirm owners for unresolved rows, agree where the chart lives, and set the review dates (each phase gate).
- After: publish it where the team works, link it from the project charter (see the project charter template), and ask each A to confirm their rows in writing.
RASCI, DACI, RAPID and other variants
| Variant | Letters | When to use it |
|---|---|---|
| RACI | Responsible, Accountable, Consulted, Informed | Most projects and processes |
| RASCI | Adds Support: helps the R without owning the work | Large teams where many people contribute to a task |
| DACI | Driver, Approver, Contributors, Informed | Single decisions, popularized as a team play by Atlassian; the Driver runs the process |
| RAPID | Recommend, Agree, Perform, Input, Decide | Major decisions with veto holders; developed by Bain (Rogers and Blenko, Harvard Business Review, 2006) |
| RACI-VS | Adds Verify and Sign-off | Regulated work with quality checks |
| CARS | Communicate, Approve, Responsible, Support | Operations and service teams |
The chart descends from the linear responsibility charts of the 1950s and is listed as a responsibility assignment matrix in the Project Management Institute's PMBOK Guide. The variants add precision at the cost of simplicity; most teams are better served by a plain RACI used consistently than by a richer scheme used once.
Mistakes that make a RACI useless
- Everyone is consulted. The chart becomes a list of people who can delay the work.
- The senior person is A on everything. Decisions queue behind one calendar.
- Rows are too vague. "Communications" has no owner because it is ten things.
- Names instead of roles. The chart is obsolete at the first reassignment.
- Built once, never used. If no one checks the chart when a decision stalls, it is decoration.
- Accountability without authority. An A who cannot decide or fund the work will pass every hard call upward.
- Hiding conflict. Two departments each marking themselves A, and nobody raising it, is the problem the chart was supposed to surface.
Keeping it current
Review the chart at each phase gate and whenever someone joins, leaves or changes role. Keep it in the same place as the project plan and the status report, and add a row whenever a new recurring decision appears. For standing processes (payroll, onboarding, month-end close), the RACI becomes part of the standard operating procedure.
Key takeaways
- A RACI chart lists tasks or decisions against roles and assigns each cell Responsible (does the work), Accountable (owns and approves), Consulted (input before) or Informed (told after).
- Rules: exactly one A per row, at least one R, roles not names as columns, rows as concrete deliverables or decisions, minimal Cs, and an A who has the authority to decide.
- Read the columns too: a role with As on half the chart is a bottleneck; a role with no letters should be removed.
- Fill it in a one-hour workshop: definitions, A first then R then C and I row by row, read the columns, resolve or escalate disputed As, publish and review at each phase gate.
- Variants include RASCI (adds Support), DACI (single decisions), RAPID (Bain's decision model) and RACI-VS (verify and sign-off); a simple RACI used consistently usually beats a richer scheme used once.
- Only 47% of US employees strongly agree they know what is expected of them (Gallup, 2025); a RACI makes role gaps visible but works only if it is checked when decisions stall.
Frequently asked questions
What is a RACI chart?
A responsibility assignment matrix that lists tasks or decisions in rows and roles in columns, with each cell marked R (Responsible, does the work), A (Accountable, owns the result and signs off), C (Consulted, gives input beforehand) or I (Informed, told afterward). It clarifies who does what and, most importantly, who decides.
What is the difference between responsible and accountable?
Responsible is doing the work; accountable is owning the outcome. Several people can be responsible for a task, but exactly one should be accountable: the person who approves the result and answers for it. The accountable person can delegate the work but not the ownership.
Can there be more than one A in a RACI?
No. The core rule is one accountable person per task. If two people seem accountable, the task usually contains two decisions and should be split into two rows, each with its own owner. Shared accountability tends to mean nobody acts.
How do you make a RACI chart?
List the project's deliverables or decisions as rows and the roles involved as columns. For each row, assign the A first, then one or more Rs, then the fewest Cs needed, then the Is. Check that every row has one A and at least one R, then read each column for overloaded or idle roles. Review it at each project phase.
What is the difference between consulted and informed?
Consulted people give input before the work is finished, so the work waits for them; it is two-way communication. Informed people are told about a decision or result after the fact; it is one-way. Moving people from C to I is the fastest way to speed up a slow project.
What is RASCI?
A variant of RACI that adds S for Support: people who help the Responsible person without owning the task. It is useful in large teams where many contributors would otherwise all be marked R.
What is the difference between RACI and DACI?
DACI (Driver, Approver, Contributors, Informed) is designed for single decisions: the Driver runs the process, the Approver makes the call. RACI is designed for whole projects or processes with many tasks. Both rely on one final decision-maker per item.
Who should be accountable in a RACI chart?
The person with the authority, budget and information to make the decision and answer for the result, usually the most senior person close to the work rather than the most senior person overall. Making an executive accountable for every row creates a bottleneck.