RATSI: Separating Authority from Responsibility

Summary

RATSI splits what RACI bundles into three distinct roles: Responsible ensures the work happens, Authority holds the final decision power, and Task does the hands-on work, with Support and Informed completing the set. That split matters in matrix organizations, where the person who owns a deliverable is often not the person empowered to make key decisions about it, a tension plain RACI cannot express. Its natural home is organization design and role clarification rather than day-to-day delivery: restructures, confused reporting lines, and consultancy diagnosis. For routine project work, RACI’s coarser split is enough and RATSI’s precision becomes overhead. It is the task family’s bridge toward the decision-rights frameworks.

The letters

RATSI breaks the doing-and-owning question into finer parts than RACI does.

The defining move is the split between three things RACI keeps bundled: who ensures it happens (Responsible), who has the authority to decide (Authority), and who physically does it (Task). In RACI, “Responsible” covers both ensuring and doing, and “Accountable” covers both owning and deciding. RATSI teases those apart.

Origin and history

RATSI is a documented member of the family that is most closely associated with organization design and roles analysis rather than day-to-day project delivery. CIO Wiki describes it as a tool used in organization design, and it appears consistently across reputable project-management references including ClickUp and specialist listings. As with the rest of the task family, it has no single named inventor; it is a convention that emerged in the org-design community to handle a distinction that ordinary responsibility charts blur.

Its natural home is the kind of work where you are not organizing a single project but analyzing how authority and responsibility are distributed across roles: designing a new function, clarifying a confused reporting structure, or untangling a matrix organization where decision power and delivery responsibility have drifted apart. In those settings the RACI pair is too coarse, and RATSI’s finer split is what people reach for.

What problem it solves

RATSI solves the conflation of authority with responsibility. In many organizations, and especially in matrix structures, the person who owns a deliverable is not the person who has the authority to make the key decisions about it, and neither is necessarily the person who does the work. RACI cannot express that cleanly: it offers only Responsible and Accountable, and it quietly assumes that the accountable owner also holds decision authority. When that assumption is false, which is common, the chart hides the very tension that is causing trouble.

By naming Authority as a separate role, RATSI surfaces it. You can now say explicitly that a delivery manager is Responsible for ensuring a piece of work happens, a functional head holds the Authority to approve the approach, and a specialist has the Task of doing it. That separation is exactly what an organization-design exercise needs to see, because misalignment between authority and responsibility is one of the most common and most damaging structural faults.

When to choose it, and when not

Choose RATSI for organization design, role clarification, and matrix-management analysis: whenever the question is not “who is on this project” but “how are authority, responsibility, and execution distributed across these roles”. It suits consultancy engagements, restructures, and the diagnosis of confused reporting lines, and it is a good fit when decision authority genuinely sits apart from delivery responsibility.

Do not use it for straightforward project delivery where RACI’s simpler split is enough. Introducing a three-way distinction between Responsible, Authority, and Task on routine work overcomplicates the chart and invites the same confusion it was meant to cure. RATSI is a diagnostic and design instrument, not an everyday task tracker.

Common pitfalls

• Blurring Responsible, Authority, and Task. The matrix’s whole value is the three-way split. If people cannot reliably tell ensuring, deciding, and doing apart, RATSI delivers false precision.
• Leaving Authority implicit. The temptation is to assume the Responsible person also holds Authority. If that is true, say so explicitly; if it is not, the gap is exactly what you are trying to expose.
• Over-engineering simple work. A five-role analysis of a two-person task is wasted effort and reads as bureaucracy.
• Confusing it with a decision framework. RATSI clarifies the authority attached to a piece of work; it is not a full decision-rights framework. For recurring high-stakes decisions, RAPID or DACI are the right tools.

Worked example

An organization-design analysis for a newly created data-governance function.

Reading the “Classify a data domain” row: the Data Governance Lead is Responsible for ensuring the classification happens (R), the Domain Steward and Data Engineer do the actual work (T), but the Business Owner holds the Authority to approve how their domain is classified (A). RACI would have forced the Business Owner and the Governance Lead into a single Accountable slot and hidden the fact that decision authority sits with the business, not with governance. RATSI makes that structural reality visible, which is the point of an org-design exercise.

Where it sits in the family

RATSI is the task family’s frontier with the decision-rights family. It shares the doing-side richness of RASCI (through its Task and Support roles) but adds something none of the pure task matrices have: an explicit Authority role. That makes it less an everyday delivery tool and more a design and diagnosis tool. If RACI answers “who is on the hook for this deliverable”, RATSI answers “how are the doing, the ensuring, and the deciding split across these roles”, which is a structural question rather than a scheduling one.

Sources

Web sources

• RACI Matrix, CIO Wiki (RATSI in organization design and roles analysis): https://cio-wiki.org/wiki/RACI_Matrix
• Best RACI Matrix Alternatives, ClickUp (RATSI separates authority from responsibility): https://clickup.com/blog/raci-alternatives/
• RACI Analysis Template, TCC (RATSI role definitions): https://www.tcc-net.com/resources/templates/raci-analysis

Academic sources

No peer-reviewed literature treats RATSI as its own subject; it is documented through practitioner and organization-design references. The authority-versus-responsibility split it operationalizes is core to the economics of organizations.

• Jensen, M.C. and Meckling, W.H. (1992) ‘Specific and general knowledge, and organizational structure’, in Werin, L. and Wijkander, H. (eds.) Contract Economics. Oxford: Blackwell, pp. 251-274. The argument that decision rights should be co-located with the knowledge to use them, which is what a RATSI analysis tests.
• Fama, E.F. and Jensen, M.C. (1983) ‘Separation of ownership and control’, Journal of Law and Economics, 26(2), pp. 301-325. The decision-management versus decision-control distinction RATSI’s Authority role isolates.
• Galbraith, J.R. (2014) Designing Organizations: Strategy, Structure, and Process at the Business Unit and Enterprise Levels. 3rd edn. San Francisco, CA: Jossey-Bass. A standard reference on aligning structure, roles, and decision authority, the kind of design work RATSI supports.