Frameworks · Organizing people
The RACI matrix
A grid of tasks against people that shows, for each task, who is responsible, who is accountable, who is consulted and who is informed.
Section 01: The framework at a glance
Text description
A grid of tasks against roles for a fictional project, opening a second branch of a café called Kettle and Crumb. Each cell holds one letter: R, responsible, does the work; A, accountable, owns the result and signs it off, one per task; C, consulted, asked before the decision; I, informed, told once it is made. Choose the site: Owner A, Operations manager R, Finance officer C, Marketing lead C, Head barista I. Agree the budget: Owner A, Operations manager C, Finance officer R, Marketing lead C, Head barista I. Fit out the premises: Owner C, Operations manager A, Finance officer C, Marketing lead I, Head barista R. Recruit and train staff: Owner I, Operations manager A, Finance officer C, Marketing lead I, Head barista R. Plan the opening week: Owner A, Operations manager C, Finance officer I, Marketing lead R, Head barista C. Every task has exactly one person accountable and at least one responsible.
Section 02: What it is, and what it is for
A RACI matrix lists the tasks or decisions of a project down one side and the people or roles across the top. Each cell holds a letter. R, responsible, marks the person who does the work. A, accountable, marks the one person who owns the result and signs it off. C, consulted, marks people whose views are sought before a decision, in two-way discussion. I, informed, marks people who are told once a decision is made.
Two rules make the matrix useful: every task has exactly one A, so that ownership is clear, and at least one R, so that someone actually does the work. Reading down a column shows each person's load; a column full of Rs is a bottleneck, and a column of Cs is someone who will slow every decision. It is a practical tool from project management rather than a theory, and it connects to the guide's ideas of delegation, chain of command and the matrix structure.
What it is for
To make roles explicit in a project or a change, especially where people work across departments or report to two managers, so that tasks are not duplicated, dropped or argued over, and so that people are consulted and informed without slowing everything down.
Section 03: How it is built
The parts of the framework, and what each one holds.
- Tasks and decisions (the rows)
- The main pieces of work and the decisions of the project, in the order they happen.
- Roles (the columns)
- The people or roles involved, by role rather than by name where possible, so that the matrix survives a change of staff.
- Responsible (R)
- The person or people who do the work.
- Accountable (A)
- The one person who answers for the task and signs it off. There is exactly one for each task.
- Consulted (C)
- People whose views are sought before the work is done or the decision made: two-way communication.
- Informed (I)
- People told about progress or the outcome: one-way communication.
Section 04: When to use it
The business situations it suits, and where another tool will serve better.
It suits
- Projects where several people think they own the same decision, or where tasks fall between roles, such as opening a second café.
- Handing over work between teams, where the matrix shows who now answers for what.
- Reducing delay caused by consulting too many people on every decision.
Look elsewhere when
- Small, stable teams that already work well together, where the matrix adds paperwork.
- Problems of trust or capability, which clear letters on a grid cannot fix.
Section 05: How to use it, step by step
- List the main tasks and decisions of the project, in the order they happen.
- List the roles involved, by role rather than by name where possible.
- For each task, mark the one person accountable, then who is responsible for doing the work.
- Add who must be consulted before it is done and who must be informed afterwards; keep both lists short.
- Check the rules: one A for every task, at least one R, and no person overloaded with Rs.
- Share the matrix with everyone involved and revise it when roles change.
Section 06: Applied: Kettle and Crumb opens a second café
The owner of Kettle and Crumb, a fictional café, plans a second branch with four colleagues. In the first draft of the plan, nobody was clearly accountable for fitting out the premises, and both the owner and the operations manager thought they were choosing the site.
The RACI matrix in the diagram settles it. The owner is accountable for choosing the site, agreeing the budget and planning the opening week; the operations manager is accountable for the fit-out and for recruiting and training staff; the head barista is responsible for the fit-out and the training, because that is where her expertise lies.
What it showed
Each task now has exactly one person accountable and at least one responsible, which the check in the diagram confirms. The matrix also showed the finance officer consulted on four of the five tasks, so the team agreed she would be consulted only on spending above a set amount, to avoid slowing decisions down.
Section 07: Reading the result
How to interpret what it shows, and what that does and does not justify deciding.
Read the matrix down each row and across each column. Down a row: does the task have exactly one A and at least one R, and is the list of Cs short enough not to stall it? Across a column: is anyone overloaded with Rs, or holding As for tasks they have no authority over?
The patterns that matter are the faults: a row with no A is a task nobody answers for; a row with two As is a future dispute; a column full of Cs is a person who will slow everything down; a column of As for one person is a bottleneck.
What it can justify deciding
- Naming one accountable person for each task, and giving them the authority to decide.
- Cutting the number of people consulted on routine decisions, or setting a threshold above which they are consulted.
- Rebalancing the workload of anyone with too many Rs.
What it does not justify on its own
- Assuming that clear roles will make people work well together.
- Assigning accountability to someone without the time, authority or resources to carry it.
Section 08: Strengths and limits
Why it helps
- Simple and visual, it removes confusion about who does what and who decides.
- It shows workloads and bottlenecks at a glance by reading down each column.
- It suits matrix structures and cross-department projects, where reporting lines alone do not settle responsibility.
Where it falls short
- It shows roles, not how well people work together; a clear matrix cannot fix a lack of trust.
- For large projects the grid becomes long and hard to maintain.
- Assigning letters does not give people the authority or the time to carry them out.
Section 09: Common mistakes
Errors often made with it, by students and by managers, and how to avoid each.
-
Mistake Giving a task two accountable people.
Instead Choose one; if two people share the work, make one accountable and both responsible.
-
Mistake Consulting everyone on everything.
Instead Consult only those whose knowledge or agreement the task needs, and inform the rest.
-
Mistake Filling in the matrix and never sharing it.
Instead Agree it with everyone named, and revise it when roles change.
Section 10: Apply it
The application mode: the platform's tools that apply this framework, and a worksheet for your own case.
Frameworks structure judgement; they do not produce answers. Each one organizes evidence so that you can see it, test it and argue from it, and the decision, and the reasons for it, remain yours.
No interactive tool on the platform applies the RACI matrix in full yet, so the worksheet below is its application mode.
Your worksheet
Work through the framework part by part for a business you know, then say what the result does and does not justify.
Your worksheet could not be restored on this page; you can still fill it in and copy your work.
Kept on this device as you type, and nowhere else. Not saved without JavaScript: print the page or copy your answers before you leave.
The Framework Application Lab: choose a framework by the decision you face.
Section 11: Try it
The platform's own exercise. Write your answer, then open the guidance.
A student council is organizing a charity concert. Draw a RACI matrix with at least five tasks and four roles, then check it against the two rules and identify any person who is overloaded.
Kept on this device as you type, and nowhere else. Your answer is not saved without JavaScript; copy it before you leave.
The draft could not be restored on this page; you can still write and copy your answer.
Guidance: what a strong answer does
- Choose tasks that cover the whole project, from booking the venue to counting the money raised.
- Give each task exactly one A and at least one R, and keep the Cs and Is to the people who really need them.
- Read down each column to spot overload, and say how you would rebalance it.
- Explain one task where the person accountable and the person responsible should be different, and why.
Section 12: Related concepts
In the glossary
- RACI matrix Beyond IB A table that sets out, for each task or decision in a project, who is responsible for doing it, who is accountable for it, who must be consulted and who must be informed.
- Delegation Passing the authority to carry out a task or make a decision to someone lower in the hierarchy, while the manager who delegates remains accountable for the result.
- Matrix structure A structure in which employees report to two managers at once, usually the manager of their function, such as marketing or engineering, and the manager of the project or product they are working on.
- Chain of command The formal line of authority through which instructions pass down an organization and accountability passes up, from the top of the hierarchy to the bottom.
- Project-based organization A way of organizing in which work is built around projects, each carried out by a temporary team drawn from different functions that disbands when the project is finished.
Read with
- Gantt charts IB toolkit A chart of a project's tasks as bars against a timeline, showing when each starts and ends, which overlap, and the milestones along the way. Compare side by side: The RACI matrix and Gantt charts
- Critical path analysis IB toolkit A method of planning a project as a network of linked activities, to find the shortest time it can take, the activities that cannot slip, and the float on the rest. Compare side by side: The RACI matrix and Critical path analysis
- Mendelow's matrix Enrichment A grid that places each stakeholder group by its power over a decision and its interest in it, to decide how closely to involve each one. Compare side by side: The RACI matrix and Mendelow's matrix
- The McKinsey 7S model Enrichment Seven elements of an organization, three hard and four soft, that must fit together for a strategy or a change to work. Compare side by side: The RACI matrix and The McKinsey 7S model
Compare it with any other framework in the library.
The explanation, method, example and exercise are the platform's own, written as enrichment beyond the IB course. The business in the example is fictional.
Arjun Agrawal | The Business Brief, https://the-business-brief-dun.vercel.app/frameworks/raci-matrix/. Original teaching material, not an IB publication. The organizations in the teaching cases are fictional unless a case says otherwise.