Free template
A free RACI matrix template in Word, with a worked example and the few rules that stop a RACI turning into a wall of letters nobody reads.
By Christopher Fagan, Managing Partner, PEF Consulting Partners
A note before you start
A RACI is only worth having if it settles arguments before they happen. The useful ones fit on a page, have exactly one A on every line and get checked whenever a person leaves or a supplier changes. Use this one for the decisions and deliverables that cause friction, such as sign offs, go live and data ownership, rather than for every task in the plan.
Christopher Fagan, Managing Partner, PEF Consulting Partners
List the roles first, not the names, so the matrix survives people moving on. Then list the deliverables and decisions that matter, one per row. For each row give exactly one A, the person who owns the outcome and signs it off, and at least one R, the person or team doing the work. Keep C for the few people whose input genuinely changes the answer, and I for the people who simply need to know. Review it at each stage gate and whenever the team changes.
[Organisation name] | Version 0.1 | [Date] | Owner: [Name, role]
| Letter | Meaning | Rule |
|---|---|---|
| R | Responsible: does the work | At least one per line |
| A | Accountable: owns the outcome and signs it off | Exactly one per line |
| C | Consulted: gives input before the work is done | Two way, keep the list short |
| I | Informed: told after the decision or delivery | One way |
Name the roles, then the people currently in them.
| Role | Name | Organisation | Notes |
|---|---|---|---|
One row per deliverable or decision. One A per row.
| Deliverable or decision | Role 1 | Role 2 | Role 3 | Role 4 | Role 5 | Role 6 | Notes |
|---|---|---|---|---|---|---|---|
| Deliverable or decision | Sponsor | Programme director | Finance lead | Systems integrator | Data lead | Change lead |
|---|---|---|---|---|---|---|
| Business case approval | A | R | C | I | I | I |
| Solution design sign off | I | A | C | R | C | C |
| Data migration rules | I | C | A | C | R | I |
| User acceptance testing | I | A | R | C | C | C |
| Go live decision | A | R | C | C | C | C |
| Training plan | I | A | C | C | I | R |
Every row has exactly one A. Every row has at least one R. Nobody is accountable for more than they can genuinely attend to. The C column is a short list, not everyone. The matrix has an owner and a review date.
Template by PEF Consulting Partners, pefconsultingpartners.co.uk. Free to use and adapt.
Related reading: the RAID log template, the project charter template, the steering committee terms of reference template, programme management consultancy.
Responsible, accountable, consulted and informed. Responsible people do the work, the accountable person owns the outcome, consulted people give input before the work is done and informed people are told afterwards.
Yes, on small pieces of work the same person often does the work and signs it off. Show it as A, and make sure it is a deliberate choice rather than a gap where nobody else wanted the job.
They are variations for decisions. DACI names a driver, approver, contributors and informed, and RAPID splits recommend, agree, perform, input and decide. RACI is the most widely understood, which is why it works best on programmes with several suppliers.
Usually six to ten. If you need more columns than that, split the matrix by workstream rather than squeezing everyone onto one page.
If your RACI has two As on a line, or nobody can say who signs off go live, fix it before the next steering committee rather than after the next argument.