A RACI chart example is easiest to learn from when it's small. Take one task — approving a vendor invoice — and map it against every role that touches it. Tasks down the left, roles across the top, one letter per cell: Responsible does the work, Accountable owns the decision, Consulted gets asked before it's made, Informed gets told after. That is the entire format. And the format is almost never what breaks. The letters are. Below are three versions of the same invoice approval, so you can see exactly where they break.
Key takeaways
- The clean version puts the person doing the work as R and exactly one named approver as A.
- Two A's on one task means the decision has two owners, which in practice means it waits until someone gives up and escalates.
- Marking one manager A on every row keeps the chart technically valid and still turns every task into a queue behind one calendar.
- The free RACI matrix generator flags both broken patterns in the grid before you export it as PDF, CSV or text.
The RACI chart example: approving a vendor invoice
Vendor invoice approval is a good test case because it is boring, frequent, and touches several people. Boring matters: the failures here are the ones you stop noticing because they have been happening so long.
The roles, in plain language:
- Accounts payable clerk — receives the invoice, matches it to the purchase order, enters it.
- Finance manager — signs off on spend.
- Controller — owns the payment decision and the ledger.
- Department head — confirms the goods actually arrived.
- Vendor — wants to know when they get paid.
Now chart it three ways.
Version 1: two A's, no R
- AP clerk — blank
- Finance manager — A
- Controller — A
- Department head — C
- Vendor — I
Two people hold the decision. Nobody is named as the person who does the work. Everyone reading the chart knows the clerk processes invoices, but the chart doesn't say so — and a chart that doesn't say so is not a chart, it's a note that everyone already knows. On a bad week, both A's wait for the other. On a worse week, both approve, and the invoice gets paid twice or paid wrong. The decision doesn't slow down because anyone is careless. It slows down because the grid never said who starts.
Version 2: the manager is A on everything
- AP clerk — R
- Finance manager — A on every row
- Controller — I on everything
- Department head — C on everything
- Vendor — I
This one passes the basic rule check. One R, one A. It still fails, because the A is the same person on every line. Every decision the team makes now has to reach one desk. Speed stops being a property of the process and becomes a property of one person's calendar. When that person is in back-to-back meetings, on leave, or simply away from the screen, invoices sit — not because anyone dropped them, but because the chart said only one person could move them.
This is the pattern behind the phrase "everything lands on me." It isn't a feeling. It's a written rule, and the whole team is following it.
Version 3: the clean version
- AP clerk — R (receives, matches, enters, prepares for approval)
- Controller — A (approves payment and owns the decision)
- Department head — C (confirms receipt of goods before approval)
- Finance manager — I (told once the invoice clears)
- Vendor — I (told when payment is scheduled)
One doer. One decision owner. One consultation that happens before the decision, not after. The rest is notification. Work starts the moment the invoice arrives, because the clerk's job doesn't depend on anyone else's calendar. The approval is a single step, not a search for the right person.
Three versions side by side
| Version | What the cells say | What it does to decision speed |
|---|---|---|
| Two A's, no R | Two decision owners, nobody named to do the work | Stalls until someone escalates or the work gets duplicated |
| Manager A on every row | Valid rule-wise, one approver for all tasks | Moves at the speed of one person's availability |
| Clerk R, controller A | One doer, one owner, input separated from notice | Starts on arrival; approval is one step |
What the rule-breaking flags catch
You can hold these three versions in your head for one task. You cannot hold them for twenty tasks across six roles, which is where most matrices quietly rot. This is the part where a tool beats a whiteboard: the RACI matrix generator drafts the letters from the roles and tasks you enter, then checks the grid against the rules.
It catches the first version immediately — a row with two A's, and a row with nobody marked R. It also makes the second pattern visible, because when one name fills the entire A column it is impossible to miss once you are reading the column instead of the row.
You click a cell to cycle through blank, R, A, AR, C and I. If the same person genuinely does the work and owns the decision — common in a two-person team — mark it AR and write down that you did it on purpose. Deliberate is fine. Accidental is how you end up with version 1.
Each task row also has space for the SOP behind it: a few lines on how the invoice gets matched, who to chase, what to do when the purchase order doesn't match. That turns a letter in a cell into something a new hire can actually follow. Then export as PDF for the shared folder, CSV for the spreadsheet, or text for the wiki.
Quick checklist
- Pick one recurring task that keeps landing on people — invoice approval, refund sign-off, contract review.
- List the roles, not the names. Names change; the rules shouldn't.
- Mark R first: who actually does the work.
- Mark exactly one A per row. If two people argue for it, the task is really two tasks — split it.
- Add C only where someone's input changes the outcome, and I for everyone else.
- Build it at https://tools.exiuss.com/raci-matrix, fix what it flags, and export the clean version.