Using RACI for agency projects (without the bureaucracy)
A lightweight way to use RACI on agency projects - what it is, when it helps (and when it's overkill), and the two-letter version most small agencies actually need.
Part of the systemise your agency guide
Most "who owns this?" problems are RACI problems
The single most expensive question in an agency is "who owns this?" - asked in a Slack thread, on a Friday afternoon, about a deliverable nobody's sure is theirs. Multiply it across enough projects and it becomes the operational tax that quietly eats founder time. RACI is the standard fix, and it's a fine one - as long as you don't turn it into the bureaucratic version that gives RACI a bad name.
The lightweight version is two letters and a five-minute conversation. That's almost always all a small agency needs.
What RACI actually means
RACI assigns four kinds of ownership for any task or deliverable:
- R - Responsible. The person doing the work.
- A - Accountable. The single person who's on the hook if it goes wrong. Only ever one.
- C - Consulted. People whose input is needed before it's done.
- I - Informed. People who need to know once it's done.
The two that matter most are R and A. Get those right and the rest tends to sort itself out. The C and I columns are useful on cross-functional or multi-stakeholder work, and pure noise on a two-person task.
When RACI is worth the effort
Don't put a RACI on everything - that's how it becomes the joke. Use it when:
- A project involves more than two roles or teams.
- It's not obvious who has the final say (designer vs. strategist vs. account lead).
- A handoff has gone wrong before on similar work.
- You're standing up a new productized service and need the delivery roles defined.
For straightforward, single-owner work, "R + A on a sticky note" is enough. The point is clarity, not the form.
The two-letter RACI most agencies need
For 80% of agency projects, you only need R and A. A simple table at project kickoff:
[Project / deliverable] R A
Brief written Account lead Account lead
Concept Designer Creative director
Copy Writer Creative director
Build Developer Tech lead
Client review Account lead Account lead
Sign-off - Client (single approver)Notice the last row - explicitly naming the single approver on the client side is the most valuable line on the page. Most delays in agency work trace back to "who signs this off?" being ambiguous on the client side.
For larger or messier projects, layer in C and I where genuine input or notification is needed. Resist the urge to "be thorough" by filling every cell - empty cells are a feature.
Where RACI fits in the wider system
RACI is one tool inside the people section of your agency operations manual. It pairs naturally with clean handoffs (the same chart often tells you where they happen) and with SOPs (the R column points at who follows them). For the wider operations picture, see the systemise your agency guide.
Frequently asked questions
What is RACI?
A way to assign ownership for a task: Responsible (does the work), Accountable (single person on the hook), Consulted (whose input is needed), Informed (who needs to know when it's done). For most agency work, the R and A columns alone are enough.
When should an agency use RACI?
On cross-functional work, when it's not obvious who has the final say, when handoffs have gone wrong on similar work before, or when standing up a new productized service that needs delivery roles defined. For simple single-owner work, RACI is overkill.
Who is "Accountable" in RACI?
The single person who's on the hook if it goes wrong - and only ever one person. Two accountables means nobody is. Accountable can equal Responsible (same person doing the work and on the hook), but they need to be named.
How is RACI different from a project plan?
A project plan says what gets done by when. RACI says who's on the hook for each piece - the missing layer that prevents the "I thought you were handling that" conversation a fortnight later.