What Is a Change Agent? Roles, Skills, and Characteristics Explained
A change agent drives transformation inside organizations. Learn the definition, four types, key responsibilities, essential skills, and...
Guide users inside their tools
Measure real usage
Keep the app portfolio under control
A RACI matrix defines who is Responsible, Accountable, Consulted and Informed for every task. Learn the full definition, see examples, and build yours in 5
A RACI matrix is a responsibility assignment chart that maps every task, milestone or key decision in a project to the people involved in it. RACI (Responsible, Accountable, Consulted, Informed) is an acronym: each letter names the role a person holds for a given task, so everyone knows exactly what is expected of them. The tool is also called a RACI chart, RACI model, roles and responsibilities matrix, or RAM (responsibility assignment matrix).
A RACI matrix is a project management tool that clarifies task ownership by defining each team member's role in completing a task or reaching a decision. It takes the form of a grid: tasks or deliverables are listed down one side, and the people or roles involved are listed across the top. Each cell contains one of the four RACI letters to show how that person relates to that task.
The formal name for this tool is a RAM (responsibility assignment matrix) or linear responsibility chart. You will also see it called a RACI chart, RACI model, RACI framework, responsibility matrix or roles and responsibilities matrix. For a closer look at the visual structure, see our guide to building a RACI diagram.
The matrix exists to prevent two common project failures: tasks that no one owns, and tasks that too many people try to own at the same time. Making roles explicit keeps communication clean and decisions fast.
RACI stands for Responsible, Accountable, Consulted and Informed. Each letter represents a distinct type of involvement a person or team can have on a given task or decision. Together the four roles cover the full spectrum of participation: who does the work, who owns the result, who provides expert input, and who is kept in the loop.
| Letter | Full word | One-line definition |
|---|---|---|
| R | Responsible | Does the work to complete the task |
| A | Accountable | Owns the outcome and gives final sign-off |
| C | Consulted | Provides expert input before work is finalized (two-way) |
| I | Informed | Kept up to date on progress or outcomes (one-way) |
Each letter defines a distinct type of involvement. Here is a summary of each role:
The Responsible person or group performs the actual work and produces the deliverable. A task can have more than one Responsible party when the work is shared, but each person's contribution should be clear. The Responsible role answers the question: who does this?
The Accountable person has final authority over the task and answers for its outcome. They approve the work before it is considered done. The golden rule of RACI is that every task must have exactly one Accountable person. Assigning more than one creates competing authority and stalls decisions. This role is often held by a project manager, team lead or executive sponsor.
Consulted people are subject-matter experts or stakeholders whose input is needed before a decision is made or a task is completed. Communication is two-way: they review work and give feedback, but they do not make the final decision. Legal or compliance officers, technical architects and department heads are common examples. Keep the number of Consulted people small; too many slow the process down.
Informed people are kept up to date on progress and outcomes but are not involved in the work itself. Communication is one-way: they receive updates rather than provide input. They may be senior leaders, end users or other departments affected by the results.
| Role | Involvement | Communication direction | Typical example |
|---|---|---|---|
| Responsible | Executes the work | Active | Developer, analyst, content writer |
| Accountable | Approves and owns the outcome | Oversight | Project manager, team lead |
| Consulted | Provides expert input before completion | Two-way | Legal counsel, technical architect |
| Informed | Receives updates after completion | One-way | Executive sponsor, end users |
A RACI matrix example shows how roles are assigned in practice. The examples below cover a product launch, a website redesign and a software rollout because these three scenarios represent the most common uses of the tool across industries.
Here is how a SaaS company might assign roles when launching a new product feature.
| Task | CEO | CTO | CIO | CMO | Project manager | Engineering | Marketing | Sales |
|---|---|---|---|---|---|---|---|---|
| Define technical requirements | I | A | C | C | R | I | ||
| Build and test the feature | A | I | C | R | ||||
| Prepare marketing materials | I | A | I | R | C | |||
| Approve the launch date | A | C | I | C | R | I | I | I |
Take the first task. Engineering is Responsible because it writes the technical specification. The CTO is Accountable because they own the roadmap and approve the requirements. The CIO is Consulted because the feature must fit the wider IT infrastructure. The CEO and sales team are Informed so they can plan the launch and customer communications.
When a marketing department leads a website overhaul, the web development team is Responsible for building pages and the marketing director is Accountable for the final product. The IT architect is Consulted on CRM (customer relationship management) integration requirements. The project sponsor and executive leadership are Informed of milestones and launch dates. On smaller teams, one person may hold both the Accountable and Responsible roles for some tasks, and the matrix should show this explicitly.
Software rollouts are one of the most common uses of a RACI matrix in project management, because they involve IT, business teams and end users at the same time. Here is a sample RACI document for rolling out a new business application, such as a CRM or ERP (enterprise resource planning) system.
| Task | Project sponsor | Project manager | IT team | Change manager | Department managers | End users |
|---|---|---|---|---|---|---|
| Select the software | A | R | C | C | C | I |
| Configure and test | I | A | R | C | C | C |
| Write the communication plan | A | C | I | R | C | I |
| Train end users | I | A | C | R | C | I |
| Go-live support | I | A | R | R | C | I |
| Track adoption after launch | I | C | C | A | R | I |
Notice that training and adoption tracking each have a clear owner. These are the tasks most often left unowned in software projects, which is why many rollouts go live on time but are never fully used. To plan the people side of the rollout, pair the matrix with a change model such as the ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement) model. Lemon Learning's digital adoption platform can then support the Responsible teams after go-live, with step-by-step guidance embedded inside the application itself.
The purpose of a RACI matrix is to give every team member a single, unambiguous view of their role across all project tasks. Beyond that core benefit, the matrix delivers several practical advantages.
These steps work whether you use a spreadsheet, a project management tool or the free template below.
Document every task, milestone and key decision, working from your project plan or WBS (work breakdown structure). Be specific: "conduct user testing" is more useful than "testing". Include decisions (approving a budget), communications (notifying stakeholders) and reviews (quality sign-off), because these are where role confusion causes the most problems.
List every role, team or person involved across the top of the RACI chart. Use role titles rather than names, because people change but roles persist. Only include people with a real stake in at least one task: too many columns make the matrix hard to read and use.
Go through each row and apply these rules consistently:
Share the draft with everyone named before treating it as final. This check surfaces disagreements about authority, uncovers gaps and gets explicit buy-in. Watch for these warning signs during the review:
A RACI matrix is a living document. Tasks change, people move roles and new stakeholders appear. Make the project manager responsible for maintaining it and review it at the start of each project phase or whenever scope changes significantly.

Most RACI failures come from a small set of repeating errors. Knowing them in advance makes the difference between a matrix that clarifies ownership and one that creates new confusion.
RACI is the most widely used responsibility framework, but several variants address specific needs. The standard RACI model works for most teams. The alternatives below add roles only when the extra precision justifies the added complexity.
| Framework | Roles | Best for |
|---|---|---|
| RACI | Responsible, Accountable, Consulted, Informed | Most projects and teams across industries |
| RASCI | Adds Supportive (S): people who provide resources or assistance to the Responsible party | Large organisations where one team depends on another for tools or data |
| DACI | Driver, Approver, Contributor, Informed | Decision-making in product and agile teams |
| RACI-VS | Adds Verifier (V) and Signatory (S) for formal compliance steps | Regulated industries such as pharmaceuticals or aerospace |
For a detailed comparison of two of the most common variants, see the key differences between RASCI and RACI.
Unclear ownership is one of the most common reasons organizational transformations stall. When a company rolls out a new platform, restructures a department or introduces a new process, the number of people to involve, consult or inform grows quickly and coordination becomes fragile.
Before launch, the RACI matrix answers the critical questions: who trains employees on the new system, who approves the communication plan, which department heads are consulted on the timeline, and which end users simply need to know the go-live date.
"Change management's goal is to ensure end users adopt the new solution."
Julie Guerre, Director People and Change, HR Path
Mapping these responsibilities ensures adoption activities have named owners and no communication falls through the gaps. Lemon Learning's change management solution then supports end users inside their applications at the moment of need. For the wider process, see our guide to running a successful change management process.
A RACI matrix solves a problem every team faces: unclear ownership. The RACI acronym stands for Responsible, Accountable, Consulted and Informed. Used correctly, the matrix is a simple, visual document that eliminates gaps, prevents duplicated effort and keeps projects moving. Remember the core rules:
A change agent drives transformation inside organizations. Learn the definition, four types, key responsibilities, essential skills, and...
RACI and RASCI are responsibility assignment matrices used in project management. Learn their definitions, meanings, and the key differences between...
Learn how to create truly effective e-learning training in 5 steps, from defining objectives to measuring ROI, using innovative digital tools and...