RACI Matrix Template and Examples: Ready-to-Use Formats for Every Project

A RACI matrix assigns four roles, Responsible, Accountable, Consulted, and Informed, to every task in a project, so nobody has to guess who owns what. If you want the full definition and the thinking behind each letter, the RACI matrix guide covers that in depth.

This page skips the theory. It's a blank template you can copy right now, six worked examples across different project types, and the rules that keep a matrix useful past week one instead of turning into a document nobody opens again. If ownership of tasks isn't actually your problem, and what you're missing is a structure for decisions instead, jump straight to RACI vs RASCI vs DACI.

Key Facts

• PMI's 2026 Pulse of the Profession found that roughly a third of complex projects fail, "nearly twice the 13% rate of failure for projects overall," and complex projects are exactly the ones where ownership goes unstated.
• The PMBOK Guide, Eighth Edition (PMI, November 2025) is built on six core principles and seven performance domains, and resources, meaning the people doing the work and the roles they hold, is one of the seven.
• PMI states the rule that carries the whole model: "every task has exactly one Accountable person," with Accountable defined as "the single person who owns the outcome and answers for it." Every template below is built to hold that rule.

The blank RACI matrix template

Copy this straight into a spreadsheet or doc. Replace the bracketed labels with your own tasks and roles, then fill each cell with a single letter: R, A, C, or I. Leave a cell blank if that role has no involvement in that row at all.

Legend: R = Responsible (does the work) · A = Accountable (owns the outcome, exactly one per row) · C = Consulted (gives input before the work happens, two-way) · I = Informed (gets updated after, one-way)

How to fill it in

1. List deliverables down the left, not individual actions. Start at the deliverable level (a report, a release, a signed contract), not every micro-task. More on picking the right level below.
2. List roles across the top, by name where possible. Job titles work for a template you're sharing widely, but real names remove the ambiguity that shows up the moment two people share a title. Pull the full list from a stakeholder analysis matrix if you have one, so nobody with a stake gets left off.
3. Assign every Accountable first, before anything else. One A per row, no exceptions. This is the single assignment that actually prevents a task from stalling with no one answerable for it.
4. Assign Responsible next. One is cleanest; two is workable if the work is genuinely shared; three or more usually means the row needs to split into smaller deliverables.
5. Add Consulted and Informed last, and keep both short. Every C is someone the Responsible person has to wait on before starting. Every I is a notification someone has to read. Long C and I lists are usually where a matrix starts to rot.
6. Walk the finished matrix past the people in it before calling it final. A matrix built alone and emailed out invites silent disagreement. Five minutes in a project kickoff meeting catches disputes before they turn into missed handoffs.

The rules that keep a matrix from rotting

A RACI matrix stops being useful the moment these get broken, usually without anyone noticing until a task slips.

Six worked RACI matrix examples

Each example below is a full matrix for a real scenario, not a fragment. Swap in your own roles and tasks, but notice the pattern: one A per row holds in every single one.

1. Software release or product launch

The Engineering Lead holds A on two rows and R on two others, which is normal for a technical lead close to the work. Notice QA only shows up where testing actually happens, not on every row, which is what keeps their C load manageable.

2. Marketing campaign

Legal is Consulted early (copy and creative) and Accountable once (the formal review), a common split: input everywhere the work could create risk, ownership only on the sign-off itself.

3. New-hire onboarding

This is a case where Accountable moves between HR and the Hiring Manager depending on the row instead of sitting with one person for the whole process, which is normal: onboarding spans two functions and neither owns all of it.

4. ERP or system implementation

Match the vendor's obligations here against whatever's written into your statement of work. A vendor holding R on configuration and training without a matching SOW clause is a gap worth closing before the contract is signed, not after go-live.

5. Event or office move

Moving day is the one row with three Rs at once (Facilities, IT, and the vendor all doing physical work in parallel), which is fine because it's a single day of coordinated execution, not an ongoing shared deliverable that would otherwise need splitting.

6. Small-team RACI (one person holds several letters)

A three-person team relaunching a company website: a Founder, a contract designer/developer, and a contract marketer. No department heads, no committee, just three people and a deadline.

The Founder is A on five of six rows, which would be a warning sign on a 40-person program but is exactly right here: on a three-person team, the person funding the work is supposed to be the accountable party almost everywhere. What still matters is that Responsible moves around instead of piling onto one person, and that each contractor gets full ownership (A and R together) on the row that's genuinely theirs.

How to read a broken matrix

A matrix can look complete and still be broken. These are the patterns to scan for before you trust one.

Choosing the right granularity

The most common way a RACI matrix goes wrong isn't a bad letter assignment, it's picking the wrong level of detail to build it at in the first place.

Start at the deliverable level almost every time. If your source list is a full work breakdown structure, don't map every leaf node; map the deliverables that sit above them, then drop to task level only for the two or three deliverables where ownership is genuinely contested. A matrix past 40-50 rows has usually stopped being a matrix anyone actually reads and turned into a spreadsheet people search instead.

Common RACI matrix mistakes

Where the matrix lives after it's built

A RACI matrix that only exists in the kickoff deck is a matrix nobody checks again. Build it once, then plug it into the points in the project where ownership actually gets tested.

When RACI stops working

RACI assumes the output of every row is a deliverable someone completes. The moment a row is actually a decision, a go/no-go, a budget call, a prioritization fight, RACI starts to strain. You'll see it as arguments over whether something belongs in the A column or a decision that never quite gets made because everyone's Consulted and no one's clearly driving it.

That's the signal to stop forcing it and switch models for that row, or for that entire workstream. The full breakdown of when to use RACI vs RASCI vs DACI covers how to tell the difference and how to run both side by side without the two matrices contradicting each other.

A RACI matrix earns its keep in the conversation it forces before work starts, not in the document itself. Copy the blank template above, fill it in with the people it actually affects instead of alone at your desk, and revisit it the moment scope or staffing changes. One Accountable per row, a Responsible list that doesn't overload one person, and a Consulted and Informed list short enough that people actually read it: that's the whole system, and it scales from a three-person website relaunch to a multi-vendor ERP rollout without changing shape.