Why do projects need a RACI matrix?
Most project friction is about ownership. Who orders the supplies? Who tells the donor about a delay? Who signs off the training report? When nobody knows, tasks wait, or two people do the same work.
A RACI matrix answers these questions once, in one table. It is quick to write and easy to read. It also helps new staff understand the project in their first week.
What do R, A, C and I mean?
RACI is an acronym. Each letter is a type of involvement in a task.
| Letter | Meaning | What the person does |
|---|---|---|
| R | Responsible | Does the work |
| A | Accountable | Owns the result and makes the final decision |
| C | Consulted | Gives input before the decision, in both directions |
| I | Informed | Is told after the decision, one direction only |
Two rules keep a RACI matrix honest. Every task has exactly one A. Every task has at least one R. If a row has two As, you have a future argument.
How do you build one, step by step?
- List the tasks and decisions. Start from your work plan and charter. Include decisions, such as “approve a change to the budget”, not only activities. Group rows by phase: start-up, delivery, reporting, closure.
- List the roles. Use job roles, such as project manager, finance officer, logistics officer, MEAL officer, field coordinator, country director and partner lead. Do not use names.
- Assign one A per row first. Decide who owns each result before you assign anything else. This is where the hard conversations happen, so have them early.
- Add the Rs. Name who does the work. One R is common; two or three is fine for shared tasks.
- Add Cs and Is sparingly. Ask: who must be heard before this is decided? Who only needs to know afterwards? Leave the rest blank.
- Check and agree. Review with every role in the matrix, then publish.
What does a good matrix look like?
Here is a short example for a project with a project manager (PM), finance officer (FO), logistics officer (LO) and country director (CD).
| Task | PM | FO | LO | CD |
|---|---|---|---|---|
| Approve project budget revision | R | C | I | A |
| Raise a purchase request | A | I | R | I |
| Prepare monthly financial report | C | A/R | I | I |
| Submit donor narrative report | A/R | C | I | I |
| Approve project closure | R | C | C | A |
“A/R” means the same person owns the result and does the work. That is allowed. The rule is one A, never two.
What mistakes should you check for?
Read your finished matrix for these four patterns:
- No A in a row. Nobody owns the result. Assign one.
- Many As for one role. One person is the bottleneck. Delegate some decisions to a lower level.
- An empty column. A role has no tasks. Either the role is not needed or the matrix is missing tasks.
- Too many Cs. If five people are consulted on every task, decisions will crawl. Reduce Cs to those with real input.
Also check that approvals match your internal rules. A RACI row for a purchase should not contradict your approval limits for procurement. When the two disagree, the stricter rule wins until you fix the gap.
When should you update the matrix?
A RACI matrix is a living record. Review it when:
- a person leaves or joins in a key role,
- a partner is added or changes scope,
- a donor changes reporting or approval rules,
- an after-action discussion shows confusion about ownership.
Keep the previous version with a date. If a decision was made under an older matrix, you can see who was accountable at that time. Your project charter is a good place to state who may approve changes to the matrix.
Where EMPOBase fits
EMPOBase includes a RACI tool in its Programs module, so responsibilities live with the project record instead of in a separate spreadsheet. When staff or reporting lines change, you can review project responsibility assignments next to the Organogram. Your team still checks that each task has exactly one accountable person. You can see the wider platform or ask for a walk-through with sample data.