Decision Rights Matrix Template

Executive summary

A decision rights matrix is a table that names, for each recurring decision, one person who decides, the people who recommend and are consulted first, and the people who are informed afterward. It exists to stop two failures that look opposite but have the same cause. In one, everything escalates to the CEO because nobody is sure they are allowed to decide. In the other, a manager commits the company to something that needed approval because no one told them where the line was.

This guide provides a decision rights matrix template you can copy. It deliberately uses bracketed placeholders such as [X] for every threshold, because the right dollar limit, discount level, or contract term depends on your size, your credit agreement, your risk appetite, and your people. A number copied from another company is worse than a blank, because it looks authoritative. The method below shows how to arrive at each threshold from your own data and your own obligations.

The one rule of the matrix is simple: every row has exactly one decider. If a decision has two deciders, it has none.

When to use this

Use this guide when:

• The CEO is a bottleneck for approvals that the team should handle.
• Spending, discounts, or hiring decisions have been reversed after being made.
• A new owner, sponsor, or board has asked for a delegation of authority.
• A lender, auditor, or insurer has asked what approval controls exist.
• Two leaders believe they own the same decision, or neither does.
• You are changing the leadership structure and want authority to follow the new roles.

This is an operating tool, not a legal document. Where authority is set by your articles, bylaws, shareholder agreement, loan or credit agreement, or applicable law, those documents govern. Read them first, record the limits they impose as fixed rows, and involve your counsel and advisers before relying on the matrix for anything with legal or contractual consequences. Nothing in this guide is legal advice.

Diagnostic questions

Answer these in a working session with the CEO, CFO, and function heads. Write down the answers rather than discussing them in the abstract.

1. What are the 15 to 20 recurring decisions that most often reach the CEO's desk, and how many of them did the CEO actually need to make?
2. In the last quarter, which decisions were reversed, re-opened, or made twice, and why?
3. For each of those, who believed they had the authority, and who believed they did not?
4. Which approval limits already exist (in the credit agreement, shareholder agreement, board resolutions, bank mandates, insurance requirements)?
5. Who can sign contracts, release payments, approve hires, grant discounts, and change prices today, and is that written anywhere?
6. What is the cost of a slow decision here: a late hire, a lost deal, a stalled capital project, a missed supplier discount?
7. What is the cost of a wrong decision, and which kinds are reversible?
8. Which decisions require someone to be consulted because they hold information the decider lacks (for example, finance on cash, operations on capacity)?
9. Who must be informed so that downstream teams, customers, or lenders are not surprised?
10. Is there a record of decisions and their basis, or do you rely on memory?
11. How are exceptions handled, and who approves the exception to an approval rule?
12. When someone is on leave, who holds each decision right?

Reading the answers: questions 1 to 3 show where authority is unclear. Question 4 gives you the fixed rows. Questions 6 and 7 tell you where to push authority down (cheap, reversible, urgent decisions) and where to keep it up (costly, irreversible ones).

The framework: five roles and one rule

The five roles

Use these codes consistently. Mixing in extra letters (A, S, P, and so on) makes matrices harder to read and rarely changes the decision.

The one-decider rule

Every row has exactly one D. If you find two deciders in a row, ask which one is accountable if the decision is wrong, and make that person D. The other becomes R or C. A committee can be the D only if the committee has a named chair with a casting vote, and the committee's membership and quorum are written down.

Thresholds, tiers, and the escalation path

Many decisions differ by size. Handle that with tiers: the same decision appears in several rows, each for a range, and a different person decides at each tier. Thresholds are shown as placeholders in the template below: [X1] and [X2] for amounts, [Y]% for discounts, and so on. They are for you to fill, using the method in the next section, not for you to copy.

How to choose thresholds without borrowing numbers

Set each threshold from one of four sources, in this order:

1. A document that already sets it. A credit agreement, a bank mandate, a board resolution, or an insurer's requirement may fix a limit above which approval is required. Use it as the ceiling and do not set your own limit above it.
2. Your own history. Pull the last 12 months of the decision type (capital requests, discount exceptions, hires, contract commitments). Sort by size. The threshold between a tier is the point below which the volume is high and the risk is low enough that the CEO's review adds little. Look at the distribution: the number of decisions below the line is the volume you remove from the CEO's desk.
3. Capacity to absorb a mistake. For each tier ask what the company can absorb if the decision is wrong, in cash, margin, or reputation, relative to your cash floor or covenant headroom. The decider's tier must be one where the downside is tolerable.
4. Reversibility. Easily reversed decisions can be delegated lower than irreversible ones, even at the same size.

Write the source of each threshold next to the number once you fill it in. A threshold with no stated source is a candidate for challenge.

Step-by-step process

1. Collect fixed limits. Gather every authority limit already imposed by agreements, bylaws, bank mandates, and policies. Record them as fixed rows. Owner: CFO, with counsel for legal documents. Output: a list of external constraints.
2. List the decisions. Start with the 15 to 20 recurring decisions from the diagnostic. Group them: financial, commercial, people, operations, and governance. Owner: CEO with the leadership team. Output: a decision list.
3. Draft the first matrix. For each decision, name D, R, C, I, E in the template. Add tiers where size matters, with bracketed thresholds. Owner: CFO or chief of staff. Output: a draft matrix.
4. Check the one-decider rule. Count the D in each row. Any row with zero or more than one is returned for resolution. Owner: CFO. Output: a corrected matrix.
5. Set the thresholds. Fill each bracket from the four sources, recording the source. Owner: CEO and CFO. Output: a matrix with numbers and sources.
6. Test with real cases. Take 10 decisions from the last quarter and ask whether the matrix would have given the same decider and the same speed. Owner: leadership team. Output: adjustments.
7. Approve and publish. The CEO approves, and the board or sponsor approves any rows that touch their authority. Publish in one place everyone can find. Owner: CEO. Output: the approved matrix with a version and date.
8. Log and review. Record decisions in a log, check exceptions monthly, and review the matrix quarterly. See operational decision systems for how to record decisions and later check their results. Owner: chief of staff or finance lead. Output: decision log and review notes.

Templates

Template A: Decision rights matrix with placeholders

Columns show roles: Board, CEO, CFO, Owning function leader (the leader whose budget or area the decision belongs to), and Other leaders. Use a dash where a role has no part. Replace every bracket before use.

Row 10 and rows 4 and 1 depend on your governing documents. Set them from those documents and your counsel's advice, not from this template.

Template B: Threshold register (one line per bracket)

Template C: Decision log entry

Template D: Exception request

Worked example (illustrative)

The values below are invented to show how the one-decider check works. They are not recommended structures or thresholds, and every bracket stays a bracket.

Take the 12-row matrix in Template A. The team checks each row for exactly one D, then counts decisions per role.

Twelve rows, twelve D entries, one per row, so the check passes. The count also tells a story: the CEO is decider on four of twelve rows, all of which are above a threshold, in an exception, or a senior hire. Function leaders decide three rows that are small, reversible, or inside an approved policy. If the CEO were D on eight rows, the team would ask which tiers can move down.

Now the team tests the matrix against five real decisions from last quarter, using placeholders for amounts:

1. A machine replacement in the row 3 tier waited on a board email. Under the matrix the CEO decides after the CFO recommends. Verdict: faster, provided [X2] is set above this amount.
2. A sales manager gave a discount above [Y]% without approval. Row 6 applies: the CEO decides with the CFO consulted. Verdict: the matrix closes a gap that did not exist before.
3. A hire into a budgeted role waited for the CEO. Row 7 gives the decision to the owning function leader. Verdict: faster, and the CFO is informed so headcount tracking stays current.
4. A plant manager signed a supplier contract longer than [N] months. Row 9 routes it to the CEO. Verdict: the matrix would have caught it.
5. An account owner released a customer credit hold. Row 11 makes the CFO the decider. Verdict: the matrix changes who decides, which the sales leader may contest.

Two of the five show faster decisions, two show a gap closed, and one changes who decides and is contested. The team records the contested row for the quarterly review rather than quietly reassigning it.

Metrics and KPIs

Setting targets without invented benchmarks. Take your own baseline from the last quarter before the matrix: how long decisions took, how often they were reversed, and how many reached the CEO. The first target is simply to improve on that baseline for the lower tiers while holding or lowering the reversal rate. For exceptions, a rising count on a single row signals the threshold or the role is wrong, so treat it as information, not a violation. Do not apply a "decision speed" figure from another company.

Common mistakes

1. Two deciders in a row. Shared accountability means no accountability. Pick one.
2. Thresholds copied from another company. An amount that works for a business ten times your size or one with different margins will either choke you or fail to protect you. Derive them from your own history and agreements.
3. A matrix that contradicts governing documents. If the bank mandate requires two signatures above a stated amount, the matrix cannot say otherwise. Check with counsel.
4. Too many rows. A matrix with 80 rows will not be read. Start with the 15 to 20 recurring decisions that matter and add rows only when a real case shows a gap.
5. Consulted becomes approval. C means the decider must ask and consider, not that the consulted person can veto. If you want a veto, make that person D or write a named exception.
6. No record of decisions. Without a log you cannot tell whether the matrix is followed or whether a decider's basis was sound.
7. No path for exceptions. People will invent informal ones. Give them a formal route, with an expiry date.
8. Setting and forgetting. Thresholds go stale as the company grows. Name a delegate for each D, and review thresholds quarterly.

AI prompt assistance

AI can help with structure and consistency checks. It cannot know your legal limits or your risk tolerance, and it must never be used to invent thresholds. Provide your own source documents and have counsel review anything that touches legal authority.

1. Draft the decision list from an incident log.

Here are 30 decisions, escalations, and reversals from the last quarter (pasted). Group them by type (financial, commercial, people, operations, governance), merge duplicates, and list the 15 to 20 recurring decision types. For each, say how many times it appeared and who decided it according to the notes.

Check: confirm the counts against the source list and ask the leadership team whether any type is missing.

2. Check a matrix for structural errors.

Here is a decision rights matrix as a table (pasted). For each row, count the entries coded D. List rows with zero or more than one D, rows where no one is coded E or R, and any role that is D on more than a third of rows. Do not change the matrix; only report issues.

Check: verify the flagged rows by eye and confirm that the table pasted matches the current version.

3. Compare the matrix with a source document.

Here is an extract of our credit agreement approval and covenant clauses (pasted) and the draft matrix. List any row in the matrix that may conflict with a clause, quoting the clause. State that this is a drafting aid and not legal advice.

Check: send every flagged conflict, and any row the model said was clear, to counsel. Do not treat a "no conflict" result as clearance.

4. Summarize the decision log for the quarterly review.

Using this decision log (pasted), summarize decisions by matrix row, show median time to decision by tier, list exceptions and reversals, and propose which rows or thresholds the leadership team should review. Do not infer reasons not in the log.

Check: reconcile the counts to the log and have the chief of staff confirm that the log was complete.

Implementation guide

Governance: the CEO owns the matrix. The CFO owns the threshold register and the checks. The board or sponsor approves rows that touch their reserved powers. A chief of staff or finance lead maintains the log. Review the matrix in the quarterly session described in operating cadence: weekly, monthly, quarterly rhythms, and align it with the governance charter template if a sponsor is involved.

What to expect: the first weeks expose disagreements that were previously invisible, usually about who decides on discounts, hires, and contracts. That is the value of the exercise. Expect to revise thresholds after the first quarter's data, and expect leaders to test the boundaries. Treat each test as a data point for the next threshold review.

Downloadable assets

Templates A to D above are designed to be copied into a spreadsheet as they are, with brackets left in place until you fill them from the threshold method. No calculator is currently planned for this topic in the operator library asset set.

Related resources

• CEO toolkit: the hub for CEO operating-system guides.
• Operational decision systems: recording decisions and outcomes: how to log decisions and check results.
• Operating cadence: weekly, monthly, quarterly rhythms: where decisions are made and reviewed.
• CEO 100-day communication plan: how to announce new decision rights to the organization.
• VCP governance charter template: the owner-level governance the matrix sits inside.
• KPI design: choosing 12 metrics: who decides when a metric definition changes.
• Decision rights for AI actions: extend the matrix to what an AI may read, draft, recommend and do.

Frequently asked questions

What is a decision rights matrix?

A decision rights matrix is a table that names, for each recurring decision, who decides, who recommends, who is consulted before, who is informed after, and who executes. Its purpose is to remove ambiguity about authority so decisions are made at the right level, quickly, and with a record of who made them.

How many deciders should each decision have?

Exactly one. A decision with two deciders has no one accountable if it goes wrong, and it tends to stall or be reversed. If two people feel equally responsible, ask who answers for the outcome and make that person the decider, with the other as recommender or consulted.

How do you set approval thresholds without copying benchmarks?

Start with limits already set by your agreements, bank mandates, or board resolutions. Then use your own last 12 months of decisions to find where volume is high and risk is low, test against what the company could absorb if a decision were wrong, and consider reversibility. Record the source next to each number.

What is the difference between consulted and informed?

Consulted means the decider must ask for input before deciding, because that person holds information or bears a consequence. Informed means the person is told after the decision so they can act or avoid surprise. Neither role holds a veto. If you need a veto, make that person the decider or write a named exception.

How often should a decision rights matrix be reviewed?

Review it quarterly, and also after any material change in leadership structure, financing, or company size. Check the exception log and the decision log for patterns, such as repeated exceptions on one row, which signal a threshold or role that no longer fits. Date and version every change.

How this works in a System of Performance

A decision rights matrix is only as good as the record showing it was followed and whether the decisions held up. In most companies that record is a thread of emails and memory, so the next review cannot tell whether a threshold is too tight or too loose. A Performis routine can take on a recurring job like this, with the scope and fit agreed with you: it works from the records your team supplies, prepares the work for your named reviewer, and keeps each approval on record. If you want to see how decisions move through your company today, bring it to us as a launch partner.