Skip to content
GanttPal
Log in Get started

RACI Chart: Roles, How to Build One, and Examples

A RACI chart maps each project task to the people who will do it, own its outcome, give input before it is finished, and receive updates afterward. Use it during planning to remove guesswork about approvals, handoffs and follow-through.

What a RACI chart does

A RACI chart is a responsibility assignment matrix. For every task, milestone or decision it answers four practical questions: who performs the work, who has final ownership, whose advice is needed beforehand, and who should hear about progress or the result. That structure goes beyond a simple list of assignees because it separates doing, approving, advising and informing.

The four roles, and the Responsible versus Accountable distinction

Responsible (R): the person or people who carry out the work. At least one is required, and more than one may share execution. Accountable (A): the single person who answers for the result, reviews the deliverable and gives final approval. The same person may also be Responsible, but there must be only one Accountable owner per task. Consulted (C): people whose expertise or downstream impact means they should be asked before the work is completed. There is no fixed minimum or maximum. Informed (I): people who need progress or outcome updates without being drawn into the detail. There is no fixed minimum or maximum. The key distinction is execution versus outcome: Responsible is task-oriented and can be shared, while Accountable is outcome-oriented and stays singular.

Why teams use it

Clarity is the main payoff. When ownership is visible, duplicated effort and dropped work become easier to spot, approvals have a named decision-maker, and stakeholders receive the right level of visibility. Consulted and Informed assignments also help prevent both under-communication and meeting overload. Check the matrix for uneven workloads, missing coverage, multiple Accountable owners, or long lists of Consulted people with no clear reason to be asked.

How to build and check a matrix

  1. List tasks, milestones and decisions down the left side, grouped by phase where helpful.
  2. Put each person or role across the top.
  3. Mark every intersection with R, A, C or I as appropriate.
  4. Audit the result: at least one Responsible per task, exactly one Accountable, a role for everyone involved, and no person overloaded with Responsible work.
  5. Share the finished chart and use it to shape the communication plan.

In a spreadsheet, put tasks in column A and people across row 1, add a small key defining R, A, C and I, use data validation for a drop-down of the four letters, and apply conditional formatting so each letter is easy to scan. Keep the key visible; the letters are easy to misremember under pressure.

Worked examples: handout, software, and a handoff

For a marketing handout, the content writer is Responsible for creating content, the editorial director is Accountable for quality and accuracy, the marketing manager is Consulted for subject-matter input, and the creative director, designer, project manager and CMO are Informed because design and oversight depend on the content. The pattern shows how one task can have shared execution, one approver, targeted input and wider visibility without making everyone a decision-maker. For a software product, market research might make the business analyst and marketing manager Responsible, the product manager Accountable, sales and customer support Consulted, and the project manager and developers Informed. During development, developers become Responsible while the software architect is Accountable, with product and QA consulted. The accountable owner can shift by phase, which is why the matrix should be reviewed as work moves forward. At a handoff, mark the next team Informed. For example, if catering depends on a final venue headcount, the person collecting the number is Responsible, one owner is Accountable, the venue or finance may be Consulted, and the caterer is Informed so a slipped deadline reaches them before the order cutoff.

When to use it, when to skip it, and alternatives

Use RACI when approvals could stall work, ownership is disputed, workloads look uneven, or new team members need a fast way to learn who does and approves what. A very small, straightforward project or a team already aligned through daily communication may not need one, provided a clear project plan still exists. Alternatives change the emphasis: RASCI adds a Supportive role for helpers who do not own the outcome; DACI is built around a decision driver, approver, contributors and informed parties; RAPID separates recommending, agreeing, performing, input and deciding; CARS merges Consulted and Informed into a single Communicate role. Start with RACI for task planning, use RASCI when support needs a label, DACI or RAPID when a major decision is the bottleneck, and CARS when fewer communication roles are wanted. Common failures are assigning roles without team input, never revisiting the chart after kickoff, and adding too many Consulted or Informed people without a lightweight way to update them. Walk through assignments together, review the chart in regular check-ins, and keep it next to the tasks it describes.

RACI roles at a glance
RoleMeaningAssignment rule
Responsible (R)Does the work to complete the taskAt least one per task; may be shared
Accountable (A)Answers for the outcome, reviews and approves the deliverableExactly one per task
Consulted (C)Provides input before the work is doneNo minimum or maximum stated
Informed (I)Receives progress or decision updatesNo minimum or maximum stated

Assignment limits are taken from the source definitions chart; Consulted and Informed have no stated minimum or maximum.

Example: Create content for a marketing handout
TaskResponsibleAccountableConsultedInformed
Create contentContent writerEditorial directorMarketing managerCreative director, designer, project manager, CMO

Illustrative assignments for the Create content task only, drawn from the source marketing handout example.

Choosing a RACI alternative
FrameworkWhat changesBest fit
RASCIAdds Supportive for helpers who do not own the outcomeSupport work needs its own label
DACIDriver, Approver, Contributor, InformedA major decision is the main challenge
RAPIDRecommend, Agree, Perform, Input, DecideAuthority and accountability need separating
CARSMerges Consulted and Informed into CommunicateFewer communication roles are wanted

Summarizes the source descriptions of each alternative; it is a selection aid, not a full definition of each framework.

Frequently asked questions

What is the golden rule of a RACI chart?

Give each task a single Accountable owner. Several people may share Responsible work, but only one person should answer for the outcome and approve completion. That single point of ownership keeps decisions clear.

Are RACI charts outdated?

No. The model still helps cross-functional teams clarify who does work, who approves it, who provides input and who needs updates. It remains in use alongside Agile and hybrid methods, including in construction, engineering and IT.

Who creates the RACI chart?

Usually the project manager drafts it during planning, once work is broken into tasks and deliverables. They should build it with the team, because the people doing the work know where reviews and handoffs occur, and Accountable owners should confirm their assignments before work starts.

Should a RACI chart use individual names or roles?

Use roles when staffing may change, because a role-based chart survives turnover and can be reused. Use names when one person fills each role or on a small team. In a project tool where real people are assigned to tasks, the matrix will naturally show names.

Does the referenced project tool have a built-in RACI feature?

Whether a given project tool includes a dedicated RACI view is a product-specific question, so check its current documentation or feature list before relying on one. If no built-in matrix exists, the same result is achievable manually: keep a task list in one column, add a column per person or role, and record R, A, C or I in each cell, then review the chart at regular check-ins. Where a tool does offer RACI assignments, the practical test is whether roles can be attached to individual tasks and seen alongside the schedule, so ownership stays visible without maintaining a separate file.