A responsibility assignment chart that maps every task or deliverable to four roles: Responsible (does the work), Accountable (owns the outcome), Consulted (provides input), and Informed (receives updates).
Key Takeaways
A RACI matrix is a simple grid that answers one question for every task in a project or process: who does what? Each task gets mapped against four role types. Responsible is the person who actually does the work. Accountable is the one person who owns the outcome and has final sign-off authority. Consulted includes the people whose input you need before the work moves forward. Informed covers anyone who needs to know the outcome but doesn't contribute directly. The concept originated in the project management world during the 1950s, but HR teams have adopted it because people operations involves constant cross-functional coordination. A single onboarding process might touch recruiting, IT, facilities, payroll, and the hiring manager. Without a RACI, tasks fall through cracks. Emails bounce between departments with nobody taking ownership. The new hire shows up on Day 1 without a laptop. That's not a technology problem. It's a role-clarity problem.
Each letter in RACI represents a distinct level of involvement. Getting these definitions right matters because people often confuse Responsible with Accountable.
| Role | Letter | What It Means | Example (Hiring Process) |
|---|---|---|---|
| Responsible | R | Does the work. Completes the task or deliverable. | Recruiter screens resumes and conducts phone screens |
| Accountable | A | Owns the outcome. Approves or rejects the work. Only one per task. | Hiring manager makes the final hire/no-hire decision |
| Consulted | C | Provides input before the work is done. Two-way communication. | HR Business Partner advises on salary band and offer structure |
| Informed | I | Notified after a decision or action. One-way communication. | HRIS admin receives notification to set up the new employee in the system |
Building a RACI isn't difficult, but it requires input from the people who'll actually use it. Don't build one in isolation and hand it down.
Start by listing every task, decision, or deliverable in the process you're mapping. For an onboarding RACI, that might include: create offer letter, run background check, set up IT equipment, schedule orientation, assign buddy, complete I-9, enroll in benefits, conduct 30-day check-in. Be specific. "Handle onboarding" isn't a task. "Send Day 1 welcome email with login credentials" is.
List every person or role involved in the process across the top of the matrix. Use role titles, not individual names, so the RACI survives staff turnover. Common stakeholders in HR processes include: HR generalist, recruiter, hiring manager, HRIS admin, payroll specialist, IT support, department head, and legal counsel.
For each task, assign R, A, C, or I to each stakeholder. Follow three rules strictly. First, every task must have exactly one A. If you can't pick one Accountable person, the task needs to be broken into smaller pieces. Second, every task needs at least one R. Someone has to do the work. Third, minimize C's and I's. If everyone is Consulted on everything, meetings never end and decisions take weeks.
Share the draft with everyone on it. Ask two questions: "Does your column accurately reflect what you actually do?" and "Are there tasks where you should be involved but aren't listed?" This step catches 90% of errors. People are quick to flag when they've been assigned work they didn't agree to or left off tasks they consider essential to their role.
RACI isn't just a project management tool. It's especially useful in HR because so many processes cross departmental lines.
Onboarding typically involves 6 to 10 different stakeholders: the recruiter, hiring manager, IT, facilities, payroll, benefits, the buddy or mentor, and the HR generalist coordinating everything. A RACI for onboarding eliminates the daily "who's doing what?" emails. It makes it clear that IT is Responsible for provisioning the laptop, the hiring manager is Accountable for the 90-day plan, and payroll is Informed when the start date changes.
Annual reviews involve employees, managers, skip-level managers, HR business partners, and sometimes calibration committees. A RACI clarifies who writes the review (R: manager), who approves the final rating (A: skip-level or calibration committee), who provides input on talent ratings (C: HRBP), and who gets notified of final ratings (I: compensation team for merit planning).
Creating a new HR policy requires input from legal, HR leadership, affected departments, and sometimes the executive team. The RACI prevents the common scenario where a policy draft circulates for months because nobody knows who has final approval authority. The HR director might be R for drafting, the CHRO is A for approval, legal is C for compliance review, and all people managers are I once the policy is published.
System implementations fail without clear ownership. A RACI maps who's Responsible for data migration, who's Accountable for go-live readiness, who needs to be Consulted on workflow configurations, and who's Informed about training schedules. Without it, the vendor assumes HR owns testing while HR assumes the vendor handles it.
The RACI framework is simple in concept but easy to misuse. Here are the patterns that undermine its effectiveness.
RACI isn't the only role-clarity framework. Depending on the complexity of your processes, an alternative might fit better.
| Framework | Roles | Best For | Limitation |
|---|---|---|---|
| RACI | Responsible, Accountable, Consulted, Informed | Most HR processes, cross-functional projects | Doesn't distinguish between types of support |
| RASCI | Adds Supportive (assists the Responsible person) | Complex processes needing hands-on backup | More columns to maintain, can create confusion |
| DACI | Driver, Approver, Contributor, Informed | Decision-making scenarios where speed matters | Less useful for ongoing processes |
| RAPID | Recommend, Agree, Perform, Input, Decide | Enterprise-level decisions with multiple approval layers | Overhead for simple processes |
| MOCHA | Manager, Owner, Consulted, Helper, Approver | Nonprofits and smaller organizations | Less standardized, harder to benchmark |
A RACI only works if people trust it and use it consistently. Here's what successful implementations have in common.
Data showing why role clarity tools like RACI directly impact project and team outcomes.