A RACI chart is a simple grid that maps every project task to the people involved, clarifying exactly who does the work, who owns the outcome, who needs to weigh in, and who just needs updates. Building one takes about 30 minutes for a moderately complex project, and the payoff is fewer “I thought you were handling that” moments once work begins. Here’s how to create one from scratch.
What the Four Roles Mean
RACI is an acronym for four role types you’ll assign to each task on your chart. Understanding the distinctions before you start filling in cells prevents the most common mistakes.
- Responsible: The person or people who actually do the work. A task can have multiple responsible parties, but someone still needs to execute. If you’re writing the report, building the feature, or running the test, you’re Responsible.
- Accountable: The single person who owns the outcome and makes final decisions about it. This person ensures the right resources and participation are in place. Think of them as the task-level project lead. Every task gets exactly one Accountable person, never more.
- Consulted: The knowledge holders whose input you need before a decision or deliverable is finalized. These are subject-matter experts, legal reviewers, or technical specialists who provide context. Communication flows both ways: you ask, they answer.
- Informed: People who need to know what’s happening but aren’t actively contributing to the work. This is typically leadership, stakeholders, or downstream teams. Communication flows one way: you send updates, they receive them.
The critical rule is the one-Accountable limit. When two people both think they’re the decision-maker on a task, you get delays, contradictory direction, and resentment. If you catch yourself wanting to assign two A’s to the same row, that’s a sign the task needs to be split or a reporting line needs clarification.
Step 1: List Every Task
Start by writing out all the tasks, deliverables, or decisions involved in your project. Place them along the left side of your chart, one per row, in roughly the order they’ll be completed. Be specific enough that each row represents a distinct piece of work. “Design homepage mockup” is useful. “Design stuff” is not.
If you already have a project plan or work breakdown structure, pull directly from it. If you’re starting from scratch, walk through the project chronologically and ask what needs to happen at each stage. Include approval steps and handoff points, not just production tasks. These are often where accountability gets murky, and a RACI chart is most valuable precisely at those transitions.
Step 2: Identify Stakeholders
List every person or role involved in the project across the top of the chart, one per column. You can use individual names or role titles (Project Manager, UX Designer, VP of Marketing) depending on team size. For smaller teams, names work well. For larger organizations or templates meant to outlast staff changes, roles are more practical.
Include anyone who will do work, make decisions, provide input, or need status updates. It’s better to list someone now and leave most of their cells blank than to discover midway through the project that a key stakeholder was never consulted.
Step 3: Fill In the Matrix
Go row by row and assign R, A, C, or I to each stakeholder for each task. Many cells will stay empty, and that’s fine. Not everyone is involved in every task. For each row, ask four questions:
- Who will do this work? (R)
- Who owns the final outcome and has decision-making authority? (A)
- Whose expertise or opinion do we need before this is done? (C)
- Who needs to know the result but doesn’t need to contribute? (I)
A single person can hold more than one role on a task. The Accountable person is often also Responsible, especially on small teams. That’s perfectly valid. What you want to avoid is assigning someone as both Consulted and Informed on the same task, since those roles imply different levels of engagement.
Step 4: Validate the Chart
Before sharing the chart, run through a few checks that catch problems early.
First, scan each row. Every task needs at least one R and exactly one A. If a row has no Responsible party, the work won’t get done. If a row has two A’s, resolve the conflict now by deciding who truly owns the outcome.
Next, scan each column. If one person has an R or A on nearly every row, they’re overloaded and will become a bottleneck. If someone is marked C on a large number of tasks, every one of those tasks will stall while waiting for their input. Look for opportunities to redistribute or to downgrade some C’s to I’s where full consultation isn’t truly necessary.
Finally, check for rows with too many C’s. Each consulted person adds a feedback loop. Three or four consulted parties on a single task can slow things down significantly. Ask whether each one genuinely needs to provide input before the work moves forward, or whether they’d be fine just receiving an update (making them an I instead).
Step 5: Share and Get Agreement
A RACI chart only works if the people on it agree with their assignments. Share the completed chart with all stakeholders at the project kickoff or planning meeting. Walk through it together, and give people the chance to flag disagreements. Someone marked as Informed may feel they should be Consulted. The person marked Accountable may not realize they’re expected to be the final decision-maker. Surface these conversations before work begins, not after a deadline is missed.
Once everyone agrees, treat the chart as a living reference document. Post it in your shared workspace, project management tool, or team wiki. When scope changes or new tasks emerge, update the chart rather than relying on verbal agreements.
Choosing the Right Tool
You don’t need specialized software. A spreadsheet is the most common format: tasks down column A, stakeholder names across row 1, and R/A/C/I values in the intersecting cells. Microsoft offers a free downloadable Excel template for this purpose, and Google Sheets works just as well if you want real-time collaboration.
If your team already uses a project management platform like Jira, Asana, Monday, or Smartsheet, most of these tools either have built-in RACI templates or let you create a custom table view that serves the same function. The advantage of keeping the chart inside your project tool is that it stays close to the actual task assignments and is more likely to get updated as the project evolves.
For quick, informal projects, even a shared document with a simple table works. The format matters far less than the conversation it generates and the clarity it creates.
When a Standard RACI Isn’t Enough
Some teams find four roles don’t capture every relationship. Several variations add extra letters to handle those gaps. RASCI adds an S for “Support,” identifying people who assist the Responsible party without owning the work. RACI-VS adds “Verify” and “Sign-off” roles, which are useful in regulated industries or quality-sensitive projects where someone needs to formally check the work and someone else needs to formally approve it.
These variations solve real problems, but they also add complexity. Start with the standard four-letter model. If you consistently find yourself unable to express an important role distinction, switch to a variation for your next project. Adding letters to a chart that’s already confusing people won’t make it clearer.