RACI Chart: How to Build One in 30 Minutes, With Examples and Without Drama

Picture a team meeting that ends with the most dangerous sentence in business: "Great, so we're all on the same page." Everyone nods. Someone says, "I'll take care of it," in a tone that suggests they will take care of it the way one takes care of a distant cousin's wedding invitation: with good intentions and no date. Three weeks later the email has not been sent, the client has not been called and two people are discovering, with equal surprise, that each assumed the other one was handling it.

That is the problem a RACI chart was made to solve. It is a small grid that turns "someone should" into "Maria does it, Carlos answers for it and Priya gets a heads-up." It is not glamorous. Nobody has ever framed one and hung it in a lobby. But after years of running projects, from road works to clinics to software launches, I would take a clear RACI chart over a motivational poster every time.

This guide explains what the four letters mean, the two rules that make a chart work, how to build one in about thirty minutes, three worked examples (one of them involves an office party and a cake), the mistakes I see most, and how a RACI chart fits with the other tools on this site. In the middle there is a builder that checks your own chart.

What RACI means, with a kitchen

The cleanest way to remember the letters is a restaurant kitchen on a busy Friday.

• R is Responsible. The cook who actually makes the dish. The person (or people) who do the work. If the task is a pizza, R has flour on their hands.
• A is Accountable. The head chef, or the owner, the one who answers if the dish is wrong, late or cold. There is exactly one A per task. When the customer complains, A is the one who picks up the phone, not the one who points at the cook.
• C is Consulted. The person who is asked before the decision, because they know something that matters: the allergy specialist, the supplier, the neighbor with the noise complaint. A two-way conversation.
• I is Informed. The person who is told after the decision or when the work is done: the waiter who needs to know the special sold out. A one-way message.

A task can have several Rs, several Cs and several Is, but only one A. Sometimes the person who does the work is also the one who answers for it, which is fine and is usually written "A/R."

One word of caution about words. Responsibility can be shared. Accountability cannot. You can hand the work to someone else, but the answer for the result stays with one name. If a row has two As, then, in practice, it has none, because each person will assume the other one will be the one to answer.

The two rules that make a chart work

Everything else in this article is decoration around two rules.

1. Every row needs exactly one A. Not zero, because then nobody answers for it. Not two, because then nobody does either.
2. Every row needs at least one R. A task that has an owner but no worker is a wish with a name on it.

Two rules of thumb come right behind them. Keep the Cs few, since every person you must consult adds a delay and a meeting. And don't fill every cell, because if every person has a letter on every task, the chart has become a phone book, and a phone book is excellent for finding phone numbers and terrible for finding who is doing what.

A short history and a few cousins

Charts like this belong to a family called responsibility assignment matrices, a tool project managers have used for decades. RACI is the best-known version. A few relatives you may meet:

• RASCI adds an S for Support: the people who help the R but do not own the work. Useful in large teams.
• DACI is built for decisions rather than tasks: Driver, Approver, Contributors, Informed. Handy when the main question is "who decides?"
• RAPID and other decision frameworks pursue the same goal with different letters.

You do not need to pick the fanciest one. Pick the one your team will actually read. For most projects, the four letters of RACI are plenty.

How to build one in 30 minutes

Set a timer. This is meant to be quick, and a RACI chart that takes three weeks to build has already failed at its own job.

Minutes 0 to 5: list the deliverables and decisions. Write eight to twelve rows. Think in terms of results and decisions, not tiny activities: "Approve the budget," "Choose the contractor," "Sign off the final design," "Run the weekly meeting." If you have more than fifteen rows, you are describing a schedule, not a responsibility chart. Group the small things.

Minutes 5 to 10: list the people or roles. Put them across the top. Six to eight is a good number. Use names when you know them and roles when you do not. A role without a name must get a name before the project starts.

Minutes 10 to 20: fill in the grid, in this order. Start with the A, one per row, since that forces the hardest conversation first. Then add the Rs. Then the Cs, with restraint. Then the Is. If you cannot decide who the A should be, you have found your first real problem, which is the most useful thing a RACI chart can do.

Minutes 20 to 25: test the rules. Check every row for exactly one A and at least one R. Count how many Rs each person has. If one column holds half of the Rs, that person is a bottleneck with a name tag. The builder below does this check automatically.

Minutes 25 to 30: read it out loud with the people on it. Sit down with each person and ask three questions: "Do you agree this is yours? Do you have the time? Who should be consulted that we forgot?" The silent agreement of a chart that nobody has seen is worth exactly what you paid for it.

Example 1: the office holiday party (yes, really)

Let's practice on something with low stakes and high emotions: the year-end party. Here is a short chart for five tasks and four people: Lena (the organizer), Omar (finance), Sofia (the team lead) and Dan (office manager). Each line reads: task, then who has which letter.

• Choose the date and the place: Lena is A and R, Sofia is C, Omar is C, Dan is I.
• Approve the budget: Omar is A, Lena is R (she prepares the numbers), Sofia is C, Dan is I.
• Order food and, importantly, the cake: Dan is A and R, Lena is C, Sofia is I, Omar is I.
• Send the invitations: Lena is A, Dan is R, Sofia is I, Omar is I.
• Make sure the cake is picked up on the day: Dan is A and R. Lena is I.

Look at what happened to the cake. Without the chart, the cake belonged to everyone and therefore to the person who remembered it at four in the afternoon, in a panic, while the bakery was closing. With the chart, the cake has one name next to it. Dan will order it and Dan will answer for it. This is what a RACI chart does: it replaces the question "who should…?" with a name.

Example 2: opening a small clinic or restaurant

Now a project with real money. Imagine five roles: the Owner, the Project manager (PM), the Designer, the Builder and the Operations lead. Here are a few rows. The notation is task, then Owner / PM / Designer / Builder / Operations.

• Approve the budget: A / C / I / I / C
• Sign the lease: A+R / C / I / I / I
• Choose the builder: A / R / C / – / I
• Approve design changes: A / R / C / C / C
• Order long-lead equipment: I / A / C / C / R
• Hire and train the first team: C / I / – / – / A+R
• Pass the final inspection: I / A / C / R / I
• Plan the opening day: C / A / – / C / R

Two details are worth noticing. First, the Operations lead is the A for hiring and training. Staff and systems are part of the same project as the building, a point I make repeatedly in how a clinic opens on time. Second, the Owner holds the A for the money and the contract decisions, and the PM holds the A for the delivery tasks. That is a healthy pattern: the owner decides what to spend, and the PM answers for how it gets done.

Example 3: a change order on a building project

Change orders are where many construction projects bleed time and money, so the chart for one is worth drawing. Roles: Owner, Owner's representative, Designer, General contractor.

• Request the change in writing: whoever wants it is R, the Owner's representative is A for logging it.
• Price the change: General contractor is R, Owner's representative is A (they check the price is fair), Designer is C.
• Check the effect on the schedule: General contractor R, Owner's representative A, Designer C.
• Approve or reject: Owner is A, Owner's representative is R (prepares the recommendation), Designer and General contractor are I.
• Update the budget and the log: Owner's representative A and R, Owner I.

The point is not the exact letters, it is the principle: one person approves, and nobody starts the work before the approval. That one line of a chart saves more money than most clever tools. I wrote about the role of the person on the owner's side in what an owner's representative is, and about keeping changes under control in how to say yes, no and not yet to scope creep.

The hall of fame of bad RACI charts

After enough projects you start to recognize the species. Here are the most common, with their field notes.

• The Committee of Accountability. Every row has four As. The meeting where this chart was approved was very pleasant and nothing has happened since.
• The Hero. One column holds every R. The Hero is brilliant, exhausted and about to take a surprise vacation, which in project terms is called a "key person risk."
• The Phone Book. Every cell has a letter. Everybody is consulted on everything, so decisions take the time it takes to find a day when twelve people are free, which is never.
• The Phantom Informed. The I column has twenty names and nobody ever sends the update. A chart is a promise, and promises of information need a communication plan behind them.
• The Ghost Role. The A is a job title, "Operations," with no name. When asked who that is, three people look at their shoes.
• The Framed Poster. A beautiful chart, approved once, never opened again. It is wrong within a month.
• The Microscopic Chart. Sixty rows, each a ten-minute task. This is not RACI, this is a to-do list with a costume.

If you recognize your own chart in this list, congratulations: you are in excellent company and the fixes take less than an hour.

Build yours: the RACI builder

The builder below starts with a sample chart for a building project. Rename the people across the top, rename the tasks, change any cell and watch the right column. It flags rows with no A, more than one A or no R, warns when you are consulting too many people and tells you who has the most tasks. When you are happy with it, copy it as text and paste it into your notes or your project plan.

Interactive tool

The RACI builder

Loading the tool…

How a RACI chart fits with the rest of your toolbox

A RACI chart tells you who. It does not tell you when or how well, so it works best next to a few friends.

• A schedule shows when. Read the Gantt chart guide for how to build one that tells the truth.
• A stakeholder map shows who matters and how to engage them. The Cs and Is of your chart come naturally from it, as in stakeholder mapping.
• A decision log records what was decided and by whom, which is the memory of the A column. There is a free decision log template.
• A project charter names the project manager and their authority. The first part of my PMBOK series shows how in the business case and the charter.
• Lightweight governance keeps the whole thing from becoming bureaucracy, as I explain in project governance for small teams.

Keep it alive

A RACI chart is not a monument, it is a document with a pulse. Three habits keep it healthy. Review it at the start of every phase, because roles change when a project moves from design to construction or from build to launch. Update it the day someone joins or leaves, not at the next quarterly meeting. And keep it to one page, visible where the team works, in the same place as the schedule and the scoreboard. If you are curious about how I fit these pieces together in a small business, that is the idea behind Project Focus on one page.

What to do this week

Pick one project where you suspect somebody is "taking care of it" and nobody knows who. Spend thirty minutes with the builder and two people from the team. Look for rows without an A and columns with too many Rs. Then have the conversation the chart makes possible. It will probably be a little awkward. It will also be shorter than the awkward conversation you would have had in three weeks, when the email still had not been sent.

If you would like help setting this kind of structure into a project, a small business or a building, that is part of my work with Project Focus and owner's representation, and you can tell me where things are stuck on the contact page.

What is the funniest "I thought you were doing it" story from your own work? Tell me in the comments.

More tools. The decision log, the stakeholder map and the communication plan are free in the toolkit, and a RACI template is on the page-updates calendar.

Frequently asked questions

What does RACI stand for?

RACI stands for Responsible, Accountable, Consulted and Informed. Responsible people do the work, the accountable person answers for the result, consulted people are asked before decisions and informed people are told afterward.

Can a task have more than one accountable person?

No. Each task should have exactly one A. If two people are accountable, each can assume the other will answer, and in practice no one does. Responsibility can be shared, accountability should not be.

What is the difference between RACI and RASCI?

RASCI adds an S for Support, meaning people who help the responsible person but do not own the work. It is useful in larger teams. For most small projects, the four letters of RACI are enough.

How many rows and people should a RACI chart have?

A useful chart usually has eight to twelve rows of deliverables and decisions, and six to eight people or roles. If you need many more rows, you are probably describing a schedule, and it is better to group the small tasks.

Join the conversation

Did this help? A quick reaction tells me what to write next.

Useful Made me smile Go deeper on this

Be the first to react.

Comments

Loading comments…

Leave a comment

NameEmail (required, never shown)

What is the funniest "I thought you were doing it" story from your own work? Post comment

Your name and email create a small profile that shows you are a real person. The email is never shown. The first time, I send you a confirmation link, and every comment is reviewed before it appears. Please keep it respectful and leave links out.