CAIRO / RACIO: Stating Who Is Deliberately Left Out
RACI plus Omitted. The cheap, high-value addition that kills the ambiguity of a blank cell by declaring that an absence is intentional, not an oversight.
Summary
CAIRO, also written RACIO, adds a single role to RACI: Omitted, marking people who are deliberately not involved in a task. It solves the ambiguity of the blank cell, which in plain RACI can mean either “not needed” or “forgotten”, two readings that look identical on the page and generate very different politics. The addition costs almost nothing, because it only annotates cells that would otherwise be blank, yet it preempts the “why isn’t my team on this?” escalation before it happens. Use it on large, politically sensitive, cross-departmental work with contested boundaries; skip it on small teams where every absence is obvious.
The letters
CAIRO and RACIO are the same matrix under two arrangements of the letters. Both add a single role, Omitted, to the RACI baseline.
Responsible
Does the work.
Accountable
Owns the outcome. One per task.
Consulted
Advisors consulted before the work proceeds.
Informed
Kept up to date after the fact.
Omitted
Explicitly and deliberately not involved in this task. Sometimes rendered “Out of the loop” or “Outsider”.
CAIRO simply reorders these as Consulted, Accountable, Informed, Responsible, Omitted. The added role is the whole story: O marks a person or team whose non-involvement is a decision, recorded on purpose.
Origin and history
RACIO is one of the oldest and most sensible RACI extensions, and it appears in the standard reference lists of the family, including Wikipedia’s account of the responsibility assignment matrix. As with the rest of the family, the Omitted role has no single named author; it is a practitioner refinement that stabilized because it addresses a problem every large matrix eventually hits.
That problem is the ambiguity of the empty cell. In a plain RACI chart, a blank means one of two very different things: either the person has no role in this task by design, or somebody forgot to consider them. The two look identical on the page and are frequently confused, which produces exactly the political friction the matrix was meant to prevent. RACIO’s contribution is to make the first meaning explicit, converting a silent gap into a stated decision.
What problem it solves
CAIRO solves the “why isn’t my team on this?” problem before it is asked. On any initiative touching many stakeholders, someone will assume they should be involved in a task and will read their blank cell as an oversight. That assumption generates escalations, defensive meetings, and scope creep as people lobby their way onto tasks that do not need them. By marking such stakeholders as Omitted, the chart states plainly that their exclusion was considered and chosen, which closes the conversation.
The value is asymmetric. Adding the O role costs almost nothing, because you are only annotating cells that would otherwise be blank, yet it removes a whole category of misunderstanding. This is why it is often described as the highest return-on-effort addition in the entire family: a single extra code that preempts a recurring and expensive class of friction.
When to choose it, and when not
Choose CAIRO when your stakeholder list is long, when the boundaries of a task are contested, or when you have learned from experience that people read blank cells as invitations to get involved. It is particularly useful in politically sensitive environments, in large cross-departmental programs, and in any situation where scoping people out is as important as scoping them in.
Do not bother with the O role on small, tight teams where every person’s involvement in every task is obvious and no one would ever be surprised by an absence. There, the Omitted column will simply be noise. CAIRO is a tool for scale and for contested boundaries, not for the simple case.
Common pitfalls
- Over-marking Omitted. You do not need to mark every uninvolved person on every task. Reserve O for people who would otherwise reasonably expect to be involved, so their exclusion is worth stating.
- Using O as a weapon. Explicitly omitting a person or team can read as a deliberate snub if not handled with care. The role should record a scoping decision, not settle a political score.
- Treating O as permanent. A stakeholder omitted from one task may be central to the next. The mark is per-task, not a judgment about the person.
- Forgetting to explain the “why”. An Omitted mark answers “were you left out on purpose?” but not “why?” For contested exclusions, a one-line rationale alongside the chart saves a follow-up meeting.
Worked example
A cross-department data-platform rollout, where several teams have historically assumed a stake in every initiative.
| Task | Data Eng | Platform Lead | Security | Marketing | Finance |
|---|---|---|---|---|---|
| Design the schema | R | A | C | O | O |
| Set access controls | C | A | R | O | I |
| Migrate the data | R | A | C | O | O |
| Announce the launch | I | C | I | R | O |
Reading the “Design the schema” row: Data Engineering does the work (R), the Platform Lead owns it (A), Security is consulted (C), and Marketing and Finance are explicitly Omitted (O). The O marks matter because on a prior project both teams had lobbied to review schema decisions that did not concern them. Recording the omission states that their exclusion was a deliberate scoping choice, which preempts the “why weren’t we consulted?” escalation.
Where it sits in the family
CAIRO is one of the lowest-cost, highest-value refinements of RACI, and it composes cleanly with the others: you can add Omitted to a RASCI or a RACI-VS chart without disrupting the base matrix. It sits alongside the other single-role additions as an example of the family’s central design pattern, RACI plus one deliberate role, and it is arguably the addition with the best return for the least complexity.
Sources
Web sources
- Responsibility assignment matrix, Wikipedia (lists RACIO/CAIRO, Omitted / Out-of-the-loop): https://en.wikipedia.org/wiki/Responsibility_assignment_matrix
- RAPID vs RACI (RASCI, RACI-VS, RACIO), Interfacing: https://interfacing.com/rapid-vs-raci
- RACI Matrix, CIO Wiki: https://cio-wiki.org/wiki/RACI_Matrix
Academic sources
No peer-reviewed work treats CAIRO or the Omitted role as its own subject; the variant is documented through practitioner references. The academic grounding is in stakeholder theory, which formalizes the judgment the O role records.
- Mitchell, R.K., Agle, B.R. and Wood, D.J. (1997) ‘Toward a theory of stakeholder identification and salience: defining the principle of who and what really counts’, Academy of Management Review, 22(4), pp. 853-886. https://doi.org/10.5465/amr.1997.9711022105
- McCann, J.E. and Gilmore, T.N. (1983) ‘Diagnosing organizational decision making through responsibility charting’, Sloan Management Review, 24(2), pp. 3-15. Family-level foundation for the charting technique CAIRO extends.