Templates · Operations & projects
RACI matrix template
Who is Responsible, Accountable, Consulted and Informed
Start with this template →Sign in
Opens on reph with the template ready to start. No account needed; sign in to keep your document.
Filled example
The template filled in for a made-up company, so you can see what good looks like.
Lumen Labs pricing change RACI
Author: Marcus Hale · Date: 2026-05-11
Legend
- R (Responsible): does the work
- A (Accountable): owns the outcome, signs off (exactly one per activity)
- C (Consulted): input sought before the decision/work
- I (Informed): kept in the loop after the fact
- R/A: one role can both do the work and own it; still only one A per row
Matrix
Lumen Labs is moving from per-seat to usage-based pricing for its analytics product on July 1. This matrix covers the work between now and the switch.
| Activity |
Product (Marcus) |
Finance (Ana) |
Eng (Kofi) |
Marketing (Lena) |
CEO (Sam) |
| Set new price points |
R |
C |
I |
C |
A |
| Model revenue impact |
C |
R/A |
I |
I |
I |
| Build metering and billing |
C |
C |
R/A |
I |
I |
| Update pricing page |
C |
I |
C |
R/A |
I |
| Customer migration emails |
A |
I |
I |
R |
I |
| Grandfathering policy |
R |
C |
I |
C |
A |
| Sales team enablement |
A |
C |
I |
R |
I |
| Go / no-go on July 1 |
R |
C |
C |
C |
A |
Notes
- If any enterprise contract has a fixed per-seat clause, Legal (Imani) becomes Consulted on "Customer migration emails" and Accountable for the contract amendment itself, which is tracked in its own doc.
- Kofi is R/A on metering because the billing system is entirely engineering-owned; Finance only consumes its reports.
- We deliberately kept Sales as Informed only on price points. They gave input in April's interviews and reopening it would stall the decision.
Rules of thumb
- Exactly one A per row. Two accountable owners means zero
- Every row needs at least one R
- Too many Cs slows a decision down; keep the consulted list tight
The first draft had both Sam and Marcus as A on "Set new price points". We resolved it in the May 9 staff meeting: Sam owns the final number, Marcus does the analysis and proposal.
The template
Show the blank template
RACI matrix
Author: [your name] · Date: [date]
Legend
- R (Responsible): does the work
- A (Accountable): owns the outcome, signs off (exactly one per activity)
- C (Consulted): input sought before the decision/work
- I (Informed): kept in the loop after the fact
- R/A: one role can both do the work and own it; still only one A per row
Matrix
One row per activity or decision, not per person. A RACI organized by person hides gaps.
| Activity |
PM |
Eng lead |
Design |
Exec sponsor |
| Define requirements |
A |
C |
C |
I |
| Design the solution |
C |
C |
R/A |
I |
| Build & test |
I |
A |
C |
I |
| Approve launch |
C |
R |
I |
A |
Notes
Anything context-dependent, e.g. "A shifts to Legal once a contract is involved."
Rules of thumb
- Exactly one A per row. Two accountable owners means zero
- Every row needs at least one R
- Too many Cs slows a decision down; keep the consulted list tight
Questions
- Can one person be both R and A?
- Yes, write R/A; there is still only one A per row
- Should rows be people or activities?
- Activities and decisions; columns are roles or people
- How often should it change?
- Revisit it at each phase change or when someone joins or leaves
Fill it with your agent
Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.
Find my reph doc "RACI matrix" with search_docs, then read it with read_doc. Build the matrix from the kickoff doc, team roster and recent decision threads I point you to: one row per activity, exactly one A per row. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (rows with ambiguous evidence, two candidate owners or no R) with add_comment quoting that section's heading line, then call request_review with a one-line summary.
Related templates
All-hands agenda
Run of show for a company all-hands: timed segments with presenters, Q&A collection, and follow-ups owed afterwards
ExecutiveFounderOperationsCommunicationsManagerOffsite agenda
Team or leadership offsite plan: goals, pre-reads, day-by-day schedule, sessions with owners, decisions to make, logistics and outcomes
ExecutiveFounderManagerEngineering managerOperationsProject kickoff
Align a new project on goals, scope, roles and cadence
ManagerProduct managerOperationsRetrospective
What went well, what didn't, and what we'll change
ManagerOperationsEngineerProduct managerRisk register
Track risks with likelihood, impact, owner and mitigation
ManagerOperationsProduct managerSecurity policy starter
An information security policy skeleton in the SOC 2 and ISO 27001 style, with roles, policy statements, exceptions, review cadence and sign-off
OperationsEngineering managerExecutiveFounderStart with this template →Sign in