Executive Leadership & GovernanceTemplate3 min readUpdated September 2026

How to Write a Decision Rights Document for Your Company

A decision rights document lists your company's recurring decisions and says, for each, who recommends, who decides, who must be consulted and who is told afterward. It ends the confusion over whose call something is, and it lets founders stop approving everything by default.

This walkthrough shows how to build one in an afternoon with your leadership team: inventory the decisions, assign four roles, set limits, and test it on a real example.

What does a decision rights document do?

It replaces guessing with a written answer. When a manager isn't sure whether they can approve a discount, hire a contractor or change a policy, the document tells them, so they don't stop and wait for you.

It also protects against the opposite problem: two people each assuming the decision was theirs. Founders who work with co-founders feel this most, which is why the co-founder agreement should say who has the final call in each area. Without written rights, both problems show up as delays, rework and quiet resentment.

How to build the decision inventory

Gather your leadership team and brainstorm the decisions that come up repeatedly. Don't list one-off strategy questions; list the recurring calls. Group them by area:

  • Money: budget changes, spending above a threshold, pricing and discounts, refunds, payment terms.
  • People: hiring, compensation changes, promotions, terminations, contractor engagement.
  • Customers: contract terms, custom work, service exceptions, renewals.
  • Product and operations: what ships, vendor choices, process changes, security exceptions.
  • Governance: signing contracts, board communications, legal matters.

Aim for thirty to fifty entries to start. If a decision hasn't come up in the past year, leave it out.

The four roles to assign for each decision

For every row in your inventory, name people, not committees, in these roles:

  1. Recommender: does the analysis and proposes the answer.
  2. Consulted: must be asked before the decision is made, and can object but not veto.
  3. Decider: makes the call. One name only.
  4. Informed: told after the decision so they can act on it.

The rule that keeps the document honest is a single decider. If two names appear, the decision will stall whenever they disagree. When you feel tempted to list two, ask which of them you'd pick if they were in the room together, and write that name down.

Two cautions. Don't make everyone consulted; if five people must be asked, the decision slows to the pace of the slowest reply. And don't confuse informed with approved. People who are told afterward can raise a concern, but they can't reverse the call.

Worked example: discounts on new customer contracts

Say a sales rep wants to offer a customer a bigger discount to close before quarter-end. Your document might read: the account executive recommends; the finance lead is consulted on margin; the head of sales decides on discounts within a set range; the CEO decides above that range; the customer success lead is informed so they can plan onboarding.

Notice what this does. The account executive knows the route. Finance has a defined role instead of learning after signature. The founder is involved only when the deal falls outside the normal range, which is the point. Limits like this pair naturally with an escalation policy, which describes what happens when a decision needs to move up.

How to roll it out and keep it current

Share the draft with the team and ask them to challenge any row where they feel unclear or uncomfortable. Fix what they raise, then publish one version where everyone can find it. Review it after the first month, because the gaps only show up in use, and then once a quarter alongside your planning process.

Tie it to the calendar too. Decisions that need the CEO should have a slot in the week, which the CEO weekly schedule helps you design. And when priorities shift, update the document at the same time as strategy on a page or your annual plan, so authority follows strategy.

A quick check after launch helps: ask three managers to name who decides a specific, recent question, then compare their answers with the document. Any mismatch is either a row that's unclear or a row nobody has read. Fix the row, then tell the team what changed and why, so the document earns trust.

Executive Capability Standard

What Good Looks Like

Every recurring decision has one named decider, and people know what they can approve without asking.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Learn the four roles (recommend, consult, decide, inform) and how they clarify accountability.
2. Do Manually:Run a workshop, list your recurring decisions and assign roles in a shared spreadsheet.
3. Delegate:Give your operations lead ownership of the document and its quarterly review.
4. Automate:Encode spending and discount limits in your approval workflow so the rules apply without a manual check.
5. Buy:Use a fractional COO or facilitator to run the workshop if leadership disagreements make it hard to reach consensus.

How to Get Started

Frequently Asked Questions

What is a decision rights document?

It's a written list of recurring decisions that names who recommends, who must be consulted, who decides and who is informed for each one. It tells people what they can decide on their own and where to escalate.

How many decisions should a decision rights document cover?

Start with thirty to fifty recurring decisions. More than that becomes hard to use. Add rows only when a decision comes up repeatedly and causes confusion or delay.

Why should each decision have only one decider?

Two deciders stall whenever they disagree, and each can assume the other will act. One name makes accountability clear and speeds the decision. Others still have a voice as consulted or recommending roles.

How often should we update decision rights?

Review it a month after launch, then quarterly, and any time you hire a leader or change strategy. Roles shift as the company grows, and a stale document is worse than none because people stop trusting it.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides