Quick answers to common questions about DOA, approval matrices, and RACI - and how they work together in real workflows.
This comes up constantly: people use "DOA," "approval matrix," and "RACI" as if they're interchangeable. They're related, but they answer fundamentally different questions — and confusing them creates governance gaps that show up during audits and incidents.
A: DOA is the formal assignment of decision rights and approval limits. It defines who is allowed to approve or commit the organization to an action — and under what constraints (thresholds, conditions, scope, time).
Think: permission to commit the company.
A: An approval matrix is a structured representation of approval rules — usually a table — that spells out which authority level is required for a given decision type and threshold.
An approval matrix often sits inside the broader DOA program, but in many organizations it becomes the "working DOA" because it's what people actually use day to day.
Think: the rulebook format people reference.
A: RACI is a responsibility model: Responsible, Accountable, Consulted, Informed. It clarifies who does the work, who owns the outcome, and who should be involved.
RACI is useful for process clarity, but it does not grant authority. You can be "Accountable" in a RACI chart and still not have delegated authority to approve a transaction above a threshold.
Think: who does the work and who owns the outcome.
A: Each serves a distinct governance purpose. The table below clarifies what each tool does, what it controls, and where it falls short.
The critical insight: workflow systems capture that an approval happened, but they often cannot prove the approver had authority for that specific decision at that time. This is the gap that causes the most audit pain. According to Deloitte's research on organizational decision-making, clear decision rights are one of the most powerful organizational levers at a leader's disposal — yet most organizations conflate these frameworks rather than connecting them deliberately.
A: No. RACI can clarify roles, but DOA is what establishes decision rights and approval limits. If you only have RACI, you'll still end up relying on informal approvals, escalation via email, and "whoever the executive trusts." McKinsey found that 72 percent of senior executives said bad decisions were as frequent as or more common than good ones — much of that stems from unclear authority, which RACI alone cannot solve.
A: In practice, yes — even if it doesn't look like a spreadsheet. Somewhere, people need a deterministic way to map a scenario to an approver. That's what the matrix provides. Without it, DOA remains a policy document that people reference occasionally rather than a working tool that governs daily decisions.
A: Workflows are where governance meets reality. Systems like ERP, procurement, CLM, and treasury tools enforce (or fail to enforce) approval rules. The more your workflow rules drift from the matrix, the more you get:
West Monroe's 2026 Speed Wins research found that 44 percent of executives cite bureaucratic processes as the top cause of slow decisions. When workflow rules diverge from the authority matrix, both speed and control suffer.
A: Use each for what it's good at:
Our recommendation: The most impactful alignment step is ensuring workflow routing rules in your ERP, procurement, and contract systems reference the same authority matrix — rather than maintaining separate approval logic that was configured independently. This single step eliminates the most common source of authority drift.
A: Pick one system of record for authority rules and delegations. Then integrate outward so workflows reference the same source. When the matrix lives in one place, delegations live in another, and workflow rules live in three more, you're managing mismatches instead of managing authority.
Next: If you want to pressure-test your authority controls and evidence, read DOA and SOX/Internal Controls (Q&A).
Connect with our team for a discovery session to learn more about how Aptly can help within your organization. If you are already a client and need support, contact us here.
