Most roles and responsibilities templates fail at the same moment: you open it, start filling in names, and realize the same person is landing in almost every row. The template isn't broken. The way the team actually works is. This is a walkthrough of what that looks like on paper, and how to fix it without hiring anyone.
Key takeaways
- A matrix that puts one person in most rows is not a documentation problem; it's a bottleneck you have just made visible.
- The fix is redistribution, not more boxes: move Responsible to people who can actually do the work, and cut Consulted down to the tasks that truly need input.
- Blank or overloaded cells usually mean nobody has written down what the task actually involves, which is why the same person keeps absorbing it.
- A finished matrix is only a delegation plan if each task carries a short procedure behind it that says what to do and when to escalate.
The team, the tasks, and the first draft
Six people. Eight tasks that come back every week or every month. Nothing exotic: a small operations team inside a business that has grown past the point where everyone just knows who does what.
The team: an operations lead, an office manager, a finance coordinator, a customer support lead, an IT and systems person, and a people and hiring coordinator.
The eight recurring tasks:
- Approving supplier invoices
- Onboarding a new hire
- Handling a customer escalation
- Ordering office and equipment supplies
- Scheduling team cover for absences
- Approving a software purchase
- Running the weekly operations meeting
- Updating the internal process documentation
Now the first draft, filled in honestly by the operations lead in about fifteen minutes:
| Task | Office manager's role |
|---|---|
| Supplier invoice approval | Responsible |
| New hire onboarding | Responsible |
| Customer escalation | Consulted |
| Office and equipment supplies | Responsible |
| Absence cover scheduling | Responsible |
| Software purchase approval | Consulted |
| Weekly operations meeting | Responsible |
| Process documentation | Informed |
The office manager is Responsible on five of eight tasks, Consulted on two, Informed on one. Every other name on the sheet appears once or twice, mostly as Consulted. Nobody planned it that way. Ask anyone on the team and they'd say the office manager is just helpful, organized, the person who knows where things are.
That's the description. The diagnosis is different.
What the rule-breaking flags actually show
Run a draft like this through the free generator at https://tools.exiuss.com/raci-matrix and the flags come back quickly, and they're all pointing at the same shape.
- Tasks with no Accountable person. Several rows have an R and a couple of C's but nobody who owns the outcome. So the R becomes the de facto owner, and the R is the office manager.
- Tasks with more than one Accountable. In other rows, two people are marked A because nobody wanted to take it from anyone. Two decision-makers is the same as none.
- Consulted sprawl. Consulting someone who has no useful input is a delay with a polite name. Every C on a task adds a waiting period to it.
- The same name repeating in R across unrelated tasks. This is the flag that matters most, and it's the one most templates never check.
Five R's across invoice approval, onboarding, supplies, absence cover, and the weekly meeting. Those tasks have almost nothing in common. Invoice approval is a finance judgment. Onboarding is a people process. Absence cover is a scheduling puzzle. The only reason one person holds all five is that each one, at some point, was easier to hand over than to define.
That's the root cause: undefined tasks don't get delegated, they get absorbed. When a task has no written procedure, no stated decision rights, and no clear definition of done, the person who picks it up becomes the owner of the ambiguity, not just the work. And ambiguity is sticky. It follows whoever is willing to hold it.
The cost of documenting a bottleneck
A matrix like this does real damage precisely because it looks finished.
It looks like a plan, so nobody revisits it. It reads as deliberate, so the office manager's five R's become formal rather than accidental. Everyone waits for one person's input on invoices, supplies, cover, and onboarding, and that person's calendar becomes the team's actual processing speed. When they take a day off, four processes stall — and the team treats the stall as normal rather than as a design flaw.
The hidden cost is the queue. Not the hours spent on the tasks themselves, but the hours other people spend waiting for a green light that only one person can give. That waiting is invisible in the template, because every row looks complete.
The corrected matrix
The point of the exercise is to move R, not to add columns. Here's the same eight tasks, redistributed across three people who can genuinely own them:
| Task | New Responsible | Accountable | Consulted |
|---|---|---|---|
| Supplier invoice approval | Finance coordinator | Operations lead | Office manager |
| New hire onboarding | People and hiring coordinator | Operations lead | Office manager, IT |
| Customer escalation | Customer support lead | Operations lead | — |
| Office and equipment supplies | Office manager | Operations lead | — |
| Absence cover scheduling | Office manager | Operations lead | — |
| Software purchase approval | IT and systems | Operations lead | Finance coordinator |
| Weekly operations meeting | Operations lead | Operations lead | — |
| Process documentation | Office manager | Operations lead | — |
Three things changed.
First, R moved to three different people — finance, people, support, IT, the operations lead, and the office manager each hold real work, but no one holds everything. The office manager keeps supplies, absence cover, and process documentation, which are genuinely theirs. Invoice approval goes to the person who already reconciles the numbers. Onboarding goes to the person who runs hiring.
Second, Consulted got cut. Customer escalation and supplies no longer list anyone as C. Nobody needed to be consulted on either; the C's existed because the office manager had always been in the room. Consulted should mean "this person's input changes the decision," not "this person likes to know."
Third, everyone can see who decides. The operations lead is Accountable across the board, which is not an accident: it gives the team one escalation point while spreading the doing. One decision-maker, several doers.
Why redistribution alone doesn't hold
Move the R and the work will drift back within a month unless each task carries a short procedure that tells the new owner what to do and when to escalate.
This is where most templates stop and most delegations fail. The office manager's version of invoice approval lived in their head: which invoices need a second look, which supplier quirks matter, which threshold means pick up the phone. Handing over the R without handing over that knowledge just relocates the waiting.
The fix is a few lines per task — a short standard operating procedure that answers three questions: what does done look like, what do I check before I decide, and what makes me escalate. For invoice approval, that's the supplier list, the checks performed, and the conditions that trigger a call to the operations lead. For absence cover, it's the coverage rules and the point at which the schedule needs a decision rather than a swap.
A few lines is enough. The generator at https://tools.exiuss.com/raci-matrix lets you write the SOP behind each task as you build the matrix, so the plan and the procedure live in the same place instead of in someone's memory.
From description to delegation plan
A roles and responsibilities template earns its keep when the finished version looks different from the first draft. If every name is in the same place it started, you've written a description of your bottleneck.
Export the final matrix as a PDF and you have something you can actually hand over: who does what, who decides, who is consulted and why, and what each owner does when the task lands on their desk. That document is a delegation plan. It survives a holiday, a resignation, and a busy week.
Click a box, cycle through blank, R, A, AR, C and I, and check the flags before you call it done. The first draft will tell you the truth about your team. The second draft is where you change it.
Start with the free RACI matrix generator at https://tools.exiuss.com/raci-matrix — list your roles and tasks, fill it in honestly, and let the flags point at the name that keeps showing up.
Quick checklist
- List your six to eight recurring tasks before you assign anyone.
- Fill in the first draft honestly, even if one name lands in most rows.
- Run the flags and count how many tasks share the same Responsible person.
- Move R to people who already do the underlying work, and cut every Consulted who doesn't change the decision.
- Assign one Accountable per task, and no more than one.
- Write a short SOP behind each task: what done looks like, what to check, when to escalate.
- Export the corrected matrix as a PDF and share it with everyone named in it.