The RACI matrix: making team responsibilities clear

A project can have a clear deadline, enthusiastic colleagues and a sensible plan, yet still stall because nobody knows who makes the final decision.

A RACI matrix helps a team agree who does the work, who owns the outcome, whose advice is needed and who simply needs an update. It is particularly useful when work crosses departments or involves several approval points.

The value is not in filling every cell. It is in having the conversations that prevent missed tasks, duplicated effort and endless rounds of consultation.

What is a RACI matrix?

A RACI matrix is a responsibility assignment table. It lists activities, decisions or deliverables against the people or roles involved, using four labels:

Label	Meaning	Plain-English question
R: Responsible	Carries out the work	Who does it?
A: Accountable	Owns the outcome and has authority to approve or accept it	Who makes sure this is delivered and decides whether it is acceptable?
C: Consulted	Provides relevant advice before action or a decision	Whose input do we need?
I: Informed	Receives an update without being asked to approve	Who needs to know?

Under the usual RACI convention, each row has one accountable owner and at least one responsible person. The same person can be both responsible and accountable, shown as A/R.

RACI is a coordination tool, not a substitute for employment responsibilities, professional duties, statutory accountability or formal governance.

Where does RACI come from?

RACI belongs to the wider family of responsibility assignment matrices used in project and organisational management. It should not be presented as the invention of a single, confidently identified author: published accounts of its origins vary.

The approach is established in professional practice, but familiarity is not proof that it improves every project. The recommendations below are practical conventions, not guarantees of better performance.

Why responsibilities need more than a job title

Job descriptions explain broad responsibilities. They rarely settle the detailed questions that arise during cross-team work:

Does the training lead approve the programme, or only organise it?
Can a line manager refuse to release staff?
Who checks whether the learning platform works?
Does the staff representative need to approve the materials or advise on them?
Who decides whether the pilot is ready to become a full launch?

Without explicit agreement, people often make different assumptions. One colleague waits for permission while another assumes the work is already under way.

In FE and Skills settings, this can happen when curriculum teams, learning support, IT, HR and managers share a project. In other workplaces, similar problems arise between operations, finance, customer service and technical teams.

RACI can make those dependencies visible. It does not create time, expertise or authority, but it helps expose where these are missing.

Understanding the four roles properly

Responsible means doing the work

The responsible person produces the output or completes the activity.

For a training programme, that might mean writing materials, configuring enrolment or delivering a workshop.

More than one person can contribute, but a row with several Rs needs care. “Everyone is responsible” can hide uncertainty about who starts, coordinates and finishes the work. Where contributions differ, split the activity or name a delivery lead.

Accountable means owning the outcome

The accountable person makes sure the activity has an owner, receives appropriate oversight and meets its agreed requirements. They must have sufficient authority to make the relevant decisions.

Accountability does not necessarily mean personally doing the work or approving every minor detail. Nor must it always sit with the most senior person.

A learning and development lead might be accountable for the training materials, while a director is accountable for approving the budget.

One A per row is a useful design rule, not an instruction to rewrite governance. If a committee must approve a decision, record that formal approval route rather than pretending one individual can act alone. Separate preparation, recommendation and approval where necessary.

Consulted means contributing before a decision

Consultation is two-way communication. The team seeks input and considers it before proceeding.

For example, staff representatives might identify barriers affecting colleagues who work shifts. An accessibility specialist might review whether materials can be used with assistive technology.

Being consulted does not automatically confer a veto or require unanimous agreement. However, a RACI label cannot remove consultation obligations, contractual rights or specialist approval requirements.

Informed means kept up to date

Informed people receive relevant information but are not routinely asked to comment or approve.

A finance colleague might need confirmation that the approved programme has launched, without attending every planning meeting.

A blank cell is also acceptable. Not every person needs a role in every activity.

Worked example: launching a staff training programme

An FE college is introducing staff training on using a new digital learning platform. The programme includes self-paced materials, practical workshops and a pilot before wider launch.

The project involves:

Sponsor: a director who authorises resources and major decisions.
L&D lead: the person coordinating the programme.
Trainer: the nominated lead for materials and delivery.
IT lead: the person coordinating technical setup.
Line manager: the relevant manager arranging staff release.
Staff representative: someone advising on practical staff needs.

An initial RACI might look like this:

Activity or deliverable	Sponsor	L&D lead	Trainer	IT lead	Line manager	Staff representative
Agree programme outcomes and scope	A	R	C	C	C	C
Approve budget and resources	A	R	I	C	C	I
Produce learning materials	I	A	R	C	C	C
Configure access and enrolment	I	A	C	R	I	I
Confirm staff release for each team	I	C	I	I	A/R	I
Deliver the pilot	I	A	R	C	I	C
Review pilot evidence and decide whether to launch	A	R	C	C	C	C

This table makes several distinctions clear:

The trainer creates the materials, but the L&D lead accepts them against agreed requirements.
IT carries out the technical setup, while the L&D lead owns its readiness for this programme.
Each line manager arranges release for their own team. In the working version, this row can be repeated for each team.
The sponsor decides whether to proceed after the pilot, informed by the L&D lead’s recommendation.

Naming the IT lead as responsible does not override IT security controls or change technical approval requirements. Those remain part of the organisation’s governance.

Add the information RACI cannot hold

The matrix needs a small amount of supporting detail. For example:

Deliverable: Pilot materials ready for use.
Responsible: Named trainer.
Accountable: L&D lead.
Completion criteria: Exercises tested, accessibility checks completed and facilitator notes available.
Consultation: Comments requested from named reviewers by the agreed date.

Dates belong in the project plan or task tracker. Acceptance criteria belong alongside the deliverable. RACI clarifies involvement, but it does not replace either.

How to agree responsibilities together

A manager can draft a matrix, but should not treat an untested draft as an agreement.

1. Decide whether RACI is necessary

Use it when work involves several functions, unclear decision rights, repeated handover problems or competing assumptions about ownership.

If a short task list would resolve the issue, start there.

2. Define the outputs

Write rows around meaningful pieces of work:

“Approve the programme budget”
“Publish accessible learning materials”
“Confirm workshop staffing”

Avoid vague rows such as “communications” or “support”. They hide several activities with potentially different owners.

Also avoid mapping every email and meeting. Excessive detail creates maintenance work without necessarily improving clarity.

3. Agree responsibility and accountability first

For each row, ask:

Who will actually do this?
Who can decide whether it is acceptable?
Do they have the authority, time and resources?
Have they agreed to the role?

If no suitable accountable owner exists, that is a governance gap. Filling the cell with a senior name does not solve it.

4. Challenge each consultation requirement

Ask: What specific input do we need from this person, and what risk would arise without it?

Useful consultation has a purpose. “They might want to be involved” is not always enough.

For each C, agree the question, timing and method. A short written review may be more useful than another standing meeting.

5. Test the draft against real situations

Use realistic prompts:

The trainer and IT lead disagree about whether an exercise will work. Who decides what happens next?
A manager cannot release staff. Who negotiates an alternative?
Pilot feedback reveals an accessibility barrier. Who arranges the response and authorises any delay?
The sponsor is unavailable. What delegation or escalation route applies?

If the team gives conflicting answers, revise the matrix or supporting arrangements.

6. Keep it visible and current

Store the agreed matrix alongside the working plan. Add a version date and identify who maintains it.

Review it when scope, staffing, authority or major dependencies change. A matrix that nobody checks can create false confidence.

How to avoid excessive consultation

A crowded C column is a warning sign. It can turn routine work into a slow search for consensus.

To keep consultation useful:

Consult on defined questions. Ask whether a proposed timetable works for shift staff, rather than requesting general thoughts.
Separate advice from approval. Explain who decides after considering the feedback.
Use proportionate deadlines. Allow enough time for meaningful input.
Consolidate contributions. A nominated representative can sometimes gather a team’s views.
Close the loop. Explain the decision and how relevant feedback influenced it.

Do not assume that silence means consent unless this arrangement is appropriate and explicitly agreed. It must not bypass required consultation or approval.

For informed colleagues, choose the lightest suitable update: a project summary, team briefing or launch notice may be enough.

A second example: when a task list is enough

A workplace supervisor and administrator are arranging a repeat induction session for six new starters. The content is approved, the budget is unchanged and both know the process.

A simple tracker may be sufficient:

Task	Owner	Due date
Book the room	Administrator	Monday
Confirm attendees	Supervisor	Tuesday
Send joining instructions	Administrator	Wednesday
Deliver induction	Supervisor	Friday

A RACI matrix would add little if ownership and authority are already clear.

If the induction changes to involve several sites, external trainers and new approval requirements, RACI may become worthwhile. The trigger is coordination complexity, not simply the number of tasks.

Limitations and related approaches

RACI is useful, but it cannot fix every organisational problem.

Common misunderstandings include:

“Accountable means legally liable.” A project label does not determine legal accountability.
“Consulted means must approve.” Advice and authorisation are different.
“The matrix solves workload problems.” An overloaded person remains overloaded after being assigned an R.
“Every cell needs a letter.” Unnecessary involvement creates noise.
“Once agreed, it is permanent.” Responsibilities need to reflect current work.
“RACI explains the whole process.” It does not show sequence, dependencies or escalation in sufficient detail.

Choose complementary tools according to the problem:

Task lists for straightforward ownership and deadlines.
Process maps for sequence, handovers and recurring workflows.
Delegation agreements for decision boundaries and escalation.
Decision logs for recording what was decided, by whom and why.

Variants such as RASCI add a supporting role. They may help some teams, but definitions vary. Agree what each letter means before using a variant, rather than assuming everyone shares the same interpretation.

Summary and your next step

A RACI matrix clarifies who does the work, owns the outcome, contributes advice and receives updates. It works best when people agree it together, consultation is purposeful and accountable owners have genuine authority.

Keep it proportionate. Use a task list where that is enough, and combine RACI with deadlines, completion criteria and escalation arrangements where needed.

Your next step: choose one live cross-team project and draft five to eight key activities. Ask colleagues to check the responsible and accountable roles first, then challenge every proposed consultation requirement.

Sources and further reading

Association for Project Management: glossary
Professional terminology covering project management, governance and responsibility.
Microsoft Learn: align responsibilities across teams
An applied RACI example in a technical setting. This is vendor guidance, not independent evidence of effectiveness.
UK Government: project delivery functional standard
Authoritative guidance on project governance, roles and accountabilities in government. Useful context for understanding why a responsibility table must fit wider decision-making arrangements.