PACSI: Giving the Reviewer a Veto

Summary

PACSI relabels RACI’s roles and re-powers the review step: Perform does the work, Accountable owns it, Control reviews it and can reject it, Suggest advises, and Informed is told. The pivotal move is Control, a veto rather than an opinion, and the matrix deliberately allows several independent controllers over one accountable owner. Choose it for audited, regulated, or safety-critical work where a reviewer must be able to stop the work, not just comment on it. Avoid it in fast-moving teams, where turning reviewers into veto-holders manufactures gridlock. Its lesson in governance is that authority and accountability need not coincide: the owner answers for the outcome, yet the controllers hold real power over it.

The letters

PACSI keeps the same underlying grid as RACI but relabels and re-powers several roles.

The pivotal role is Control. In RACI, the reviewer is Consulted, which is a passive, advisory position: they may offer a view, but they cannot stop the work. In PACSI, Control can veto. Importantly, multiple people can hold Control over the output of a single Accountable person, which is unusual and deliberate.

Origin and history

PACSI is a well-documented alternative to RACI that is particularly associated with European and operational-governance settings. It appears in the standard reference lists and in reputable project-management sources including Smartsheet, ClickUp, and CIO Wiki, which describe it consistently: a version useful in situations where multiple stakeholders can review and veto the work of a single accountable person. As with most of the family, no single named individual is credited with inventing it; it is a governance-oriented convention that took hold because it addresses a real weakness in RACI’s treatment of review.

That weakness is straightforward. RACI’s Consulted role gives reviewers a voice but no power. In many operational and regulated contexts that is exactly wrong: the reviewer is supposed to be a gate, not a commentator. PACSI was shaped by environments where the review step must be able to stop the work, and it encodes that power directly into the role definition.

What problem it solves

PACSI solves the toothless-reviewer problem. When quality, safety, or compliance depends on a genuine check, a Consulted role is inadequate because it cannot enforce anything: the Responsible party is free to take the advice or ignore it and press on. By replacing that with Control, PACSI makes the review a real gate. Work cannot proceed past a Controller who has not approved it, which is the behavior you want when the review exists to protect against defects, risk, or non-compliance.

The second thing PACSI does well is accommodate multiple controllers over one owner. In audited or high-assurance work, several independent parties may each need to be able to block, for different reasons: a security controller, a compliance controller, a technical controller. PACSI expresses that cleanly, whereas RACI would force them all into a single powerless Consulted column.

When to choose it, and when not

Choose PACSI for quality-gated and compliance-heavy work: audits, regulated processes, safety-critical deliverables, security and risk reviews, and any task where a reviewer must be able to reject the output rather than merely comment on it. It is a strong fit in healthcare, construction, finance, and IT security, where validation is as important as speed and where several parties may each hold a veto.

Do not use it for fast-moving work where reviews are advisory and blocking would only create bottlenecks. In a product team iterating quickly, turning every reviewer into a Controller manufactures gridlock. Where the control you need is a formal verification-and-signature gate rather than a rejectable review, RACI-VS is a better match; where the standing function is quality assurance rather than per-task control, RACIQ fits better.

Common pitfalls

• Too many Controllers. Each Control is a potential stop. Pile on controllers and you convert the matrix into a veto swamp where nothing ships. Grant Control only where a genuine block is warranted.
• Control used as ordinary consultation. If Controllers never actually reject anything, they are really Suggesters, and the distinction that makes PACSI valuable has been lost.
• Tension between Control and Accountable. The Accountable owner answers for the outcome but cannot override a Controller’s veto. That tension is by design, but it needs to be understood, or the owner will feel responsible for something they cannot fully command.
• No escalation path. When Controllers disagree or block, someone must be able to resolve the impasse. Define that route, or a single veto can stall the work indefinitely.

Worked example

A cybersecurity policy update in a regulated firm.

Reading the “Review for compliance” row: the CISO remains Accountable (A), while the Compliance Officer and Legal both hold Control (C) and can send the policy back if it fails their checks. Neither is merely Consulted; each can block release. The Security Analyst drafted the work (P on the first row) but is Informed here. This geometry, one accountable owner subject to several independent vetoes, is precisely what PACSI is for and what RACI cannot express.

Where it sits in the family

PACSI is one of three control-oriented cousins in the task family, alongside RACI-VS (verify and sign-off gates) and RACIQ (a standing quality role). Its distinctive contribution is the rejectable review: the Control role with a veto and the ability to have several controllers over one owner. Choose PACSI when the review must be able to stop the work and when multiple independent parties each need that power. It is favored in operational-governance and European process contexts for exactly that reason.

Sources

Web sources

• RACI Chart Explained, Smartsheet (PACSI: multiple stakeholders can review and veto): https://www.smartsheet.com/comprehensive-project-management-guide-everything-raci
• Best RACI Matrix Alternatives, ClickUp: https://clickup.com/blog/raci-alternatives/
• 6 RACI Matrix Alternatives, project-management.com (PACSI for quality and compliance): https://project-management.com/raci-alternatives/
• RACI Analysis Template, TCC (PACSI role definitions): https://www.tcc-net.com/resources/templates/raci-analysis

Academic sources

No peer-reviewed literature treats PACSI as its own subject; the matrix is documented through practitioner references. The control posture it encodes is well grounded in the governance literature.

• Fama, E.F. and Jensen, M.C. (1983) ‘Separation of ownership and control’, Journal of Law and Economics, 26(2), pp. 301-325. The economics of giving a ratifying party power over an executing party, which is exactly the Control-over-Accountable arrangement.
• Institute of Internal Auditors (2020) The IIA’s Three Lines Model. Lake Mary, FL: IIA. The risk-governance model whose independent second-line challenge PACSI’s Control role expresses at task level.