A RACI chart is a simple table that shows who does the work, who owns the outcome, who gives input and who just needs to be kept in the loop for every task in a project. For small businesses, where the same few people wear several hats, it is one of the quickest ways to stop work falling through the cracks or two people quietly doing the same job. This guide explains what each letter means, how to build a RACI chart in under an hour, and the mistakes that make one useless.
Who this guide is for
This guide is for founders, small business owners and team leads who run projects with a handful of people, often alongside contractors or a freelance designer. If you have ever asked “I thought you were handling that?” at the end of a project, a RACI chart is worth trying on your next one.
What RACI stands for
Atlassian’s guide to RACI charts describes the method as a responsibility assignment matrix that clarifies who is responsible, accountable, consulted and informed for every project task. Here is what each role means in practice:
- Responsible (R): the person or people who do the work. A task can have more than one responsible person.
- Accountable (A): the one person who owns the result and makes the final call. They sign off when the task is done.
- Consulted (C): people whose knowledge or opinion is needed before or during the work. Communication with them runs both ways.
- Informed (I): people who need updates on progress or decisions but do not contribute directly. Communication runs one way.
The one rule that makes a RACI chart work
Atlassian’s guide is clear that each task should have only one accountable person. Two “owners” usually means no owner: each assumes the other will make the decision, or they make conflicting ones. If you cannot pick one name for the A column, that is a sign the task is too big or too vague and should be split.
The same guide also recommends keeping the Responsible and Consulted columns short. Too many people doing a task blurs who actually does it, and too many people consulted slows decisions and invites conflicting opinions.
How to build a RACI chart in five steps
Atlassian sets out a four-step process: list the tasks, discuss roles with the team, build the chart and review it. Here is that process with practical detail for a small team.
- List the tasks and deliverables. Write each major task as a short verb phrase, such as “approve homepage copy” or “set up email automation”. Aim for tasks that take hours or days, not minutes.
- List the people. Put names, or roles if the people change, across the top of a spreadsheet. Include contractors and clients if they have decisions to make.
- Fill in the A column first. For each task, decide who owns the outcome. Only one A per row.
- Add R, C and I. Decide who does the work, who must be asked and who just needs to know. A person can be both A and R on the same task, which is common in small teams.
- Review it with everyone. Walk through the chart together, look for gaps and overlaps, and agree changes before work starts.
A worked example: launching a new service page
Imagine a three-person studio launching a new service page with help from a freelance copywriter.
- Write page copy: copywriter is R; founder is A; designer is C; operations lead is I.
- Design the page: designer is R and A; founder is C; copywriter is I.
- Set up the enquiry form and automation: operations lead is R and A; designer is C; founder is I.
- Approve launch: founder is A; designer and operations lead are C; copywriter is I.
Four rows are enough to show a lot. The founder is accountable for the copy and the launch but not the design, so the designer can make visual calls without waiting. The copywriter knows they will be told when the page goes live but are not expected in every meeting.
A simple RACI chart template
You do not need special software. A spreadsheet with one row per task and one column per person is enough. Here is the layout to copy:
| Task | Founder | Designer | Operations lead | Freelancer |
|---|---|---|---|---|
| Write page copy | A | C | I | R |
| Design the page | C | R, A | I | |
| Set up enquiry form | I | C | R, A | |
| Approve launch | A | C | C | I |
Leave cells blank where a person has no role. Blank cells are useful information: they show who can safely skip a meeting.
A few practical tips make the template easier to use day to day:
- Freeze the first column and header row so task names and people stay visible as the chart grows.
- Add a “decision due” column for tasks that need sign-off by a date, so the accountable person knows when they are on the hook.
- Link each task to its card in your project board, so the chart and the work stay connected.
- Keep one chart per project, stored alongside the project brief, rather than a single company-wide chart nobody updates.
How to check your chart for problems
Once the chart is filled in, scan it in two directions.
Read across each row (each task)
- No A: nobody owns the task. Assign one.
- More than one A: pick one, or split the task.
- No R: nobody is doing the work. Either the accountable person is doing it, so mark them R too, or it needs an owner.
- A long C list: ask whether every consulted person really needs to give input, or whether some could simply be informed.
Read down each column (each person)
- Lots of A and R: this person may be a bottleneck. Consider moving some accountability or work elsewhere.
- Almost all I: check whether they are needed on the project at all, or whether their skills are being missed.
- No empty cells: someone involved in everything usually slows everything down.
Common mistakes to avoid
- Making tasks too broad. “Marketing” is not a task. “Write launch email” is.
- Filling it in alone. A chart one person writes and emails round is easy to ignore. Building it together gets agreement on the spot.
- Treating it as finished. Projects change. Revisit the chart when scope, people or deadlines shift.
- Using it instead of talking. Atlassian notes that a RACI chart clarifies roles but does not guide how tasks are done, and teams can over-rely on it. Keep regular check-ins alongside it.
Where a RACI chart fits in your business systems
A RACI chart works best as one piece of a simple operating system: a task list or board that shows what is happening, standard operating procedures that explain how recurring work is done, and the RACI chart that shows who decides. For recurring processes, such as onboarding a new client or publishing a blog post, add a small RACI table to the SOP itself so nobody has to ask who signs off. Our business systems articles cover how to set up those other pieces.
Key takeaways
A RACI chart lists every task against every person and marks who is Responsible, Accountable, Consulted and Informed. Give each task exactly one accountable owner, keep the responsible and consulted lists short, and build the chart with the team rather than for them. Check rows for missing or duplicate owners, check columns for overloaded people, and revisit the chart whenever the project changes.
Written by the Design Productive Editorial desk. Disclosure: this guide contains no affiliate or sponsored links.
