The AR box is legal inside a RACI template, and that is exactly what trips people up. RACI does not forbid one person from being both Responsible and Accountable — it just tells you, quietly, that the task has no safety net. The office manager who processes a vendor invoice and then signs off on that same invoice is doing two jobs that a documented handoff could separate. Here is where that combination appears in a real template, why it is allowed, why it is risky, and how to rewrite the row so the doer and the decision-maker are different people — with a short SOP so the handoff holds when you are not in the room.
Key takeaways
- A RACI template assigns Responsible (the doer) and Accountable (the decision-maker) for every task, and the same name can legally sit in both boxes as AR.
- AR is allowed because small teams genuinely collapse roles, but it removes the check that a second pair of eyes provides, so the matrix should flag it rather than hide it.
- The fix for a vendor-invoice bottleneck is not more discipline from the office manager; it is moving R to a junior admin and leaving A where the accountability actually lives.
- A handoff only survives if there is a written SOP behind the task telling the doer exactly when to escalate, and the matrix gets exported so nobody has to ask.
Where the AR combination actually appears
Take one recurring task: approving a vendor invoice. It is small, it is weekly, and it is precisely the kind of task nobody documents because it feels too obvious to document.
The first draft of the matrix usually has one row per role and one column per task. The office manager lands in the invoice column twice — as R, because she processes the invoice, and as A, because she signs it off. If you click that box again, it cycles from R to A to AR, and the tool flags it.
The flag is not an error message. It is a warning that says: the person doing the work is also the person judging whether the work is right. If you want to see that flag for yourself, open the free RACI matrix generator and click a box to cycle through blank, R, A, AR, C and I.
Why AR is allowed but risky
RACI has a small set of hard rules. Every task gets exactly one A. The A is a role or a person, never a committee. The R does the work. C is consulted before the decision. I is told after. Nothing in those rules forbids R and A from being the same name, because in small teams they genuinely are the same name, and a template that refuses reality is a template nobody uses.
The risk is not theoretical. When the doer is also the approver:
- Nobody checks the invoice against the purchase order, because the person who would catch the error is the person who made it.
- Approval becomes a personal habit rather than a rule, so when the office manager is on leave, the invoices stop.
- Spend decisions lose their second set of eyes, which is fine until the week it is not.
- The escalation path lives in someone's memory, so 'just ask her' becomes the process.
None of that is a character flaw. It is a design flaw in the matrix, and it is fixable in a few clicks.
The corrected template: R moves, A stays
The instinct is to tell the office manager to be more careful, or to delegate 'when she gets a chance'. Both fail, because delegation without a matrix entry is just a favour. The template itself needs to change.
Move R to a junior admin. Keep A with the office manager. Add the finance lead as C on vendor terms and spend thresholds, and the affected department heads as I so their budgets do not surprise them later.
| Cell | First draft | Corrected version | Why it matters |
|---|---|---|---|
| R — does the work | Office manager | Junior admin | The doer no longer approves their own work |
| A — decides | Office manager (AR) | Office manager, A only | Accountability stays with the budget owner, separated from the task |
| C — consulted | Blank | Finance lead, on vendor terms and spend limits | Gives the junior admin a defined place to take a question |
| I — informed | Blank | Affected department heads, after approval | Nobody learns about the spend from the bank statement |
Write the SOP so the handoff survives
Moving the letter is the easy part. The reason AR creeps back in is that the new R has no instructions and no permission to escalate, so they start asking the office manager every single time and the bottleneck quietly rebuilds itself.
This is where a few lines behind the task earn their keep. Behind the invoice task, write:
- Match the invoice to the purchase order and the delivery confirmation before doing anything else.
- If the amounts differ beyond the agreed tolerance, stop and escalate to the office manager.
- If the vendor is new, or the invoice covers a service not in the contract, escalate.
- If the vendor is already flagged or the payment date falls outside the next payment run, escalate.
- If everything matches, process and file it — do not ask.
Read that back. It is not a policy document. It is a handful of lines and a default, and it converts 'ask her' into 'check the SOP'. Those same lines can be expanded into a full standard operating procedure, which is worth doing once and reusing forever.
Export it so nobody has to ask
A matrix that lives in one person's head is not a matrix, it is a habit. Export the finished version as a PDF, CSV or text file and put it where the team already looks — the shared drive, the onboarding folder, the task page itself. The PDF is what you hand a new hire. The CSV is what you paste into a tracker. The text is what goes at the top of the SOP.
The one-person bottleneck on invoice approval never announced itself. It arrived one reasonable decision at a time, and it will leave the same way — one cell at a time.
Quick checklist
- List the recurring approvals your team runs and mark who does the work and who signs off on it
- Enter roles as rows and tasks as columns in a blank matrix
- Flag every AR cell and ask whether the doer could plausibly be wrong about their own work
- Move R to someone else and leave A with whoever genuinely owns the outcome
- Write three to five lines of SOP behind the task — what to check, when to escalate, to whom
- Export the final matrix as PDF, CSV or text and put it where the team already looks
Start with a blank matrix at https://tools.exiuss.com/raci-matrix. It is free, it drafts from the roles and tasks you type in, it tells you where the matrix breaks the RACI rules, and it lets you take the result away as a PDF, CSV or text file before the next invoice lands on your desk.