Every manager in the UK has been there: a deadline is looming, yet nobody knows who will make the final call. Colleagues duplicate work, other tasks slip through, and email threads grow with everyone copied but no clear owner. The problem is simple: roles and responsibilities aren't defined.
The RACI matrix is a straightforward tool that fixes this. When you learn how to create a RACI matrix properly, you build a single source of truth that answers the question everyone asks: who is responsible for what?
understanding RACI in plain terms
RACI stands for Responsible, Accountable, Consulted and Informed. These four roles cover who does the work, who owns the outcome, who gives input, and who simply needs updates.
The Responsible person does the work. Multiple people can be Responsible, but too many makes things unclear. The Accountable person signs off and is ultimately answerable — and there should be exactly one per task. Consulted stakeholders give two-way input before decisions are made. Informed parties get one-way updates to stay in the loop without blocking progress.
the 10 practical steps
-
map the right level of activity
List tasks and deliverables that matter. Avoid tiny sub-tasks and avoid vague headings. For example, use "agree supplier contract" rather than "email supplier". Tasks should be things people will ask about in a status meeting.
-
identify who’s involved
List everyone who touches the project: core team, department leads, external suppliers, finance and legal. If you’re working with agencies in Manchester or suppliers near Birmingham, add them now rather than discovering them later.
-
build a clear grid
Put tasks down the left and people across the top. Use a spreadsheet or your project tool — whatever the team can access easily from London, Leeds or remote sites in the Scottish Highlands.
For other resources and templates, you can read more articles on the Naboo blog to help set up your sheet.
-
assign Accountable first
Decide who will answer for the outcome. One person only. This choice drives every other assignment.
-
add Responsible people next
Who will do the work? If several people contribute, name a clear lead to avoid blurred ownership.
-
pick who to Consult
Limit Consulted to those whose input materially improves the task. Too many consultees slows things down.
-
mark who to Inform
Decide who needs status updates. Keep this list tight so meetings and emails stay focused.
-
review with the team
Run a session to walk through the draft. People will spot missing stakeholders or conflicting accountabilities. Sort these out before work proceeds.
-
set an update routine
Projects change. Set a regular review — weekly for fast work, monthly for longer efforts — and appoint a matrix owner to keep it current.
-
use it in day-to-day work
Reference the matrix in meetings and when assigning tasks. Treat it as the working record, not a one-off document. For team social planning or cross-department activities, look for inspiring event ideas that can be added to your matrix for role clarity on non-project tasks.
the CLEAR checklist
Use this short checklist to keep matrices useful:
- constrained scope: Keep each matrix to one project or process.
- limited accountabilities: One Accountable per task.
- explicit definitions: Define R, A, C and I for your organisation.
- active maintenance: Treat it as a living document.
- realistic assignments: Don’t overload one person.
a quick UK example
Imagine a product launch run from London with development in Manchester, marketing in Leeds and legal support in Birmingham. The initial matrix covers everything and becomes too big. Split it: one matrix for development work, another for launch activities. Define terms clearly, reduce the number of Accountable roles and schedule short weekly reviews. Within weeks the team sees fewer meeting attendees, quicker decisions and a smoother launch.
common mistakes to avoid
Don’t build the matrix alone. Don’t set too many Consulted stakeholders. Avoid excessive detail or the opposite — being too vague. And crucially, don’t file the matrix away and forget it. Use it in every status meeting and update it when roles change.
how to measure success
Look for practical signs: faster decisions, smaller and more effective meetings, fewer arguments about who does what, better on-time delivery and staff saying they understand their responsibilities. Use a mix of these indicators rather than relying on one metric.
adapting RACI to different projects
Make the matrix lighter for agile teams and more formal for long projects. For recurring processes, keep a standing matrix. Cross-functional work benefits most — a clear matrix prevents silos and confusion across departments and regions.
sustaining the habit
Start every project by reviewing or creating the RACI matrix. Name the owner, mention roles in meeting notes and praise teams when clear roles speed up outcomes. When errors happen, use them as coaching moments rather than blame games.
RACI Matrix Implementation Guide: Quick Comparison
| Project Type | Team Size | Setup Duration | Difficulty Level | Estimated Cost | Best For |
|---|---|---|---|---|---|
| Small Startup Project | 3-5 people | 2-4 hours | Easy | Free | Quick decisions, product launches |
| Mid-Size Department Initiative | 6-15 people | 1-2 days | Medium | £0-500 | Cross-team work, quarterly goals |
| Enterprise Transformation | 16+ people | 1-2 weeks | Hard | £500-2,000 | Organization-wide change, compliance |
| Agile Development Sprint | 5-10 people | 4-6 hours | Easy | Free | Sprint planning, software releases |
| Marketing Campaign | 4-8 people | 6-8 hours | Medium | £0-300 | Campaign launches, multi-channel work |
| Construction/Infrastructure | 8-20+ people | 2-3 weeks | Hard | £1,000-5,000 | Large projects, regulatory needs |
| Product Development | 7-12 people | 1 week | Medium | £200-800 | Feature roadmaps, stakeholder alignment |
variations to know
- RASCI: adds Supportive for helpers.
- RACI-VS: adds Verify and Sign-off for regulated work.
- DACI: Driver, Approver, Contributor, Informed — useful when you want a single driver role.
frequently asked questions
what is the difference between Responsible and Accountable?
The Responsible person does the work. The Accountable person owns the outcome and makes final decisions. A task can have several Responsible people but only one Accountable person.
how many tasks should one person be Accountable for?
Avoid giving one person more than five to seven Accountable tasks in a single project. Above that, they become a decision bottleneck.
can one person be both Responsible and Accountable?
Yes, especially in small teams, but it should be the exception. Separating the roles adds oversight and prevents overload.
how often should we update the matrix?
Review whenever the team changes, scope shifts or priorities move. As a minimum, review every two to four weeks on active projects.
what if people disagree about assignments?
Use a focused discussion to sort expertise, authority and workload. If the team can’t agree, the sponsor or senior leader should decide and document the reason.