A roles and responsibilities template is only worth the paper it's on if you can fill it in without guessing. Most people open one, see the columns, and start assigning letters by instinct. That instinct is exactly what produces a grid where two people believe they own the same decision and nobody is marked as doing the work. The way out is a fixed order of four questions, applied one row at a time. Approving a customer refund is the fastest way to learn it, because everyone recognises the task and the wrong answers are obvious.
Key takeaways
- Fill every row in the same order: who does the work (R), who owns the outcome (A), who must be asked before it happens (C), who only needs to know after (I).
- Guessing tends to produce two A's and a missing R — the two failures that quietly make a matrix useless.
- A row is finished when it has exactly one A and at least one R.
- Add a one-line SOP under each row so the assignment survives the first week of real work.
| Letter | The question to ask | Answer for refund approval | What goes wrong if you skip it |
|---|---|---|---|
| R | Who actually does the work? | Support rep | The task has an owner but no doer |
| A | Who owns the outcome if it goes wrong? | Support lead (one name only) | Two owners mean the decision stalls |
| C | Who must be asked before it happens? | Finance, above your refund threshold | Money leaves without a check |
| I | Who just needs to know after? | Account manager, bookkeeper | People find out sideways and lose trust |
The order matters more than the letters
Almost everyone knows what the four letters stand for. Almost nobody applies them in sequence, and the sequence is where the clarity comes from. If you start with who needs to be informed, you end up with a long list of people who feel involved and nobody who decides. Start at the work and move outward: doer, owner, consulted, informed.
Run the decision tree on one task: approving a customer refund
Step 1 — R: who actually does the work?
Not who is senior. Not who cares most. Who opens the billing system and processes the refund. For most teams that's the support rep handling the ticket. If two people trade the task, both get an R — multiple R's are allowed and healthy, because work can be shared.
Step 2 — A: who owns the outcome?
Exactly one person. Ask: if this refund turns out to be wrong, whose name is on it? For refunds, usually the support lead. If the person doing the work also owns the outcome, that's fine — mark it AR. What is never fine is two A's in one row, because two owners means the decision stalls the moment they disagree.
Step 3 — C: who must be asked before it happens?
Consulted is two-way and it happens before the decision. Finance, for anything above the refund threshold you set. Nobody else. Every name you add here is a person the support rep has to wait for, so the test is simple: does this refund get worse if this person isn't asked? If the answer is no, they're not a C.
Step 4 — I: who just needs to know after?
The account manager who will hear about it from the customer. Whoever reconciles the books. Informed is one-way and it happens after. They get told; they don't get a vote.
The same task, filled in twice
Filled in by guessing:
- Support rep — A
- Support lead — A
- Finance — C
- Account manager — I
Filled in by the decision tree:
- Support rep — R
- Support lead — A
- Finance — C
- Account manager — I
The guesser read "accountable" as the important-sounding version of "responsible," so the two people closest to the task both got an A and the work itself got nothing. On paper it looks thorough. In practice, when a refund is disputed, both the rep and the lead believe they own the call, and nobody has written down who executes.
What the rule-breaking flags catch
Run both versions through the free generator at https://tools.exiuss.com/raci-matrix and the guessed version lights up twice: two A's, so the matrix can't tell you who decides, and no R, so the task has an owner but no doer and will get escalated instead of processed. The tree version passes.
Then check the quieter problems the flags also surface: a C who is really an I (consultation creep — a waiting room dressed up as a stakeholder), a row where everyone is I (which means it isn't a task at all), and a role carrying A on every row (a decision bottleneck wearing a job title).
Make the roles and responsibilities template survive week one
A letter grid tells you who. It doesn't tell you how, and a week later the person doing the work will improvise. Under the refund row, write the few lines that make it repeatable:
"Support rep checks the order, confirms the refund reason matches policy, processes the refund in the billing system, and records the reason code. Refunds above the threshold route to finance before processing. Support lead reviews the weekly refund log."
That's a standard operating procedure in miniature, and it's the difference between a roles and responsibilities template that sits in a folder and one the team actually uses. The SOP tool drafts a full procedure from those few lines, free, using only your own inputs.
Do this on one row today
Open the free RACI matrix generator at https://tools.exiuss.com/raci-matrix, add your roles, add one recurring task, and click a box to cycle through blank, R, A, AR, C and I. Read the flags before you read the matrix. Then export as PDF, CSV or text and keep it where the team can find it. One row done properly is a method; a whole grid done by guesswork is a document nobody trusts.
Quick checklist
- Pick one recurring task that keeps landing on you — a refund, an approval, a sign-off.
- Assign R first: who physically does the work?
- Assign exactly one A: whose name is on the outcome if it goes wrong?
- Add a C only if the task gets worse when that person isn't asked beforehand.
- Move everyone else to I, including the people who will complain about not being consulted.
- Enter the row in the generator, clear the flags, and export the PDF with a one-line SOP attached.