# Decision Authority Matrix


### [Your Business Name]

**Prepared by:** Whitney Radacina — The Founder-Proof Method

**Date:** [Date]

**Version:** 1.0 — The Founder-Proof Kit

---

> **What this document is:** This is your team's decision-making architecture. It defines exactly who is empowered to decide what — at what threshold, without checking with you first. Every decision category in this business has a named owner. Every owner has a defined limit. Nothing routes to you by default anymore.
>
> **Why it matters:** Most founder-dependent businesses don't have a delegation problem. They have an architecture problem. Your team isn't asking you everything because they're incapable — they're asking because nobody ever explicitly told them what they're allowed to own. This document changes that.
>
> **How to use it:** Walk through this document with your team before it goes live. Every person should understand not just their own column — but the full picture. When someone knows what their teammate is empowered to decide, they stop routing things upward unnecessarily. Review and update every 90 days or when a role changes.

---

## DECISION AUTHORITY LEVELS

*Every decision in this business falls into one of four levels. These levels are referenced throughout the matrix.*

| Level | What It Means | Who Holds It |
| --- | --- | --- |
| **Level 1 — Full Authority** | Decides and acts. No approval needed. No notification required. | Assigned role owner |
| **Level 2 — Decide + Notify** | Decides and acts, then notifies the relevant person after the fact. | Assigned role owner |
| **Level 3 — Consult + Decide** | Consults one other person before deciding, then owns the outcome. | Assigned role owner |
| **Level 4 — Escalate** | Does not decide. Brings to the founder or senior lead with a recommendation. | Founder / Senior lead |

---

## THE MATRIX

---

### 1. CLIENT DECISIONS

| Decision | Owner | Authority Level | Threshold / Notes |
| --- | --- | --- | --- |
| Responding to routine client questions | [Team Member] | Level 1 | Within 24 business hours |
| Sending project status updates | [Team Member] | Level 1 | Per agreed touchpoint cadence |
| Scheduling client calls and meetings | [Team Member] | Level 1 | Using approved scheduling tool |
| Approving minor scope adjustments | [Team Member] | Level 2 | No additional cost to client, no timeline impact beyond X days |
| Issuing a partial refund or credit | [Team Member / Founder] | Level 3 | Up to $[X] — consult founder above threshold |
| Handling client dissatisfaction or complaint | [Team Member] | Level 3 | First response owned by team. Escalate if unresolved within 24hrs |
| Terminating a client relationship | Founder | Level 4 | Always escalates to founder |
| Changing pricing for an existing client | Founder | Level 4 | Always escalates to founder |
| Making a commitment outside agreed scope | Founder | Level 4 | Always escalates to founder |

---

### 2. OPERATIONAL DECISIONS

| Decision | Owner | Authority Level | Threshold / Notes |
| --- | --- | --- | --- |
| Assigning and managing daily tasks | [Team Member / Ops Manager] | Level 1 | Within existing project scope |
| Adjusting internal deadlines | [Team Member / Ops Manager] | Level 2 | Notify founder if client-facing deadline is affected |
| Updating or improving an existing SOP | [Team Member / Ops Manager] | Level 2 | Document the change + notify founder |
| Creating a new SOP | [Team Member / Ops Manager] | Level 2 | Build it, notify founder, add to library |
| Changing a tool or platform the team uses | [Ops Manager] | Level 3 | Consult founder before switching anything client-facing |
| Restructuring a workflow or process | [Ops Manager] | Level 3 | Present recommendation to founder before implementing |
| Changing the PM system structure | [Ops Manager] | Level 4 | Escalates to founder |

---

### 3. FINANCIAL DECISIONS

| Decision | Owner | Authority Level | Threshold / Notes |
| --- | --- | --- | --- |
| Purchasing tools, subscriptions, or software | [Team Member] | Level 1 | Up to $[X]/month |
| Purchasing tools, subscriptions, or software | [Ops Manager] | Level 3 | $[X]–$[X]/month — consult founder |
| Any financial commitment above $[X] | Founder | Level 4 | Always escalates to founder |
| Sending client invoices | [Team Member / Ops Manager] | Level 1 | Using approved template + pricing |
| Issuing refunds | [Team Member] | Level 3 | Up to $[X] — consult founder above threshold |
| Contractor or vendor payments | [Ops Manager] | Level 2 | Within approved budget — notify founder |
| Hiring a new contractor or team member | Founder | Level 4 | Always escalates to founder |
| Ending a contractor relationship | Founder | Level 4 | Always escalates to founder |

---

### 4. COMMUNICATION DECISIONS

| Decision | Owner | Authority Level | Threshold / Notes |
| --- | --- | --- | --- |
| Responding to inbound DMs or inquiries | [Team Member] | Level 1 | Using approved messaging and tone guidelines |
| Posting to social media | [Team Member] | Level 1 | Within approved content framework |
| Responding to media or press inquiries | Founder | Level 4 | Always escalates to founder |
| Making a public statement on behalf of the business | Founder | Level 4 | Always escalates to founder |
| Communicating a business change to existing clients | Founder | Level 4 | Always escalates to founder |
| Sending a campaign or broadcast email | [Team Member] | Level 3 | Consult founder before sending to full list |

---

### 5. TEAM DECISIONS

| Decision | Owner | Authority Level | Threshold / Notes |
| --- | --- | --- | --- |
| Assigning tasks to team members | [Ops Manager] | Level 1 | Within defined roles and capacity |
| Approving time off requests | [Ops Manager] | Level 2 | Notify founder if it impacts client delivery |
| Giving performance feedback | [Ops Manager] | Level 2 | Document it — notify founder if pattern persists |
| Adjusting a team member's responsibilities | Founder | Level 3 | Consult ops manager, founder decides |
| Hiring a new team member | Founder | Level 4 | Always escalates to founder |
| Ending employment or a contractor relationship | Founder | Level 4 | Always escalates to founder |
| Changing compensation | Founder | Level 4 | Always escalates to founder |

---

## DECISION ESCALATION FAST REFERENCE

*When something comes up and you're not sure where it lands — use this.*

| Ask yourself this | If yes → |
| --- | --- |
| Is this decision reversible within 24 hours? | You probably have authority. Use Level 1 or 2. |
| Does this affect a client relationship at a strategic level? | Escalate. Level 4. |
| Does this involve money above your threshold? | Escalate. Level 4. |
| Does this change how the business operates structurally? | Consult first. Level 3 minimum. |
| Is this something that happens regularly and has a known answer? | You own it. Level 1. |
| Are you unsure AND the stakes are high? | Escalate. When in doubt, bring a recommendation — don't just bring the problem. |

---

## WHEN YOU ESCALATE — HOW TO DO IT

*Escalating isn't passing the problem. It's bringing the problem + your recommended solution and asking for a decision.*

**Don't say:** *"Hey, [client] is upset. What should I do?"*

**Do say:** *"Hey, [client] raised [specific issue]. I've assessed it and here's what I think we should do: [recommendation]. Does that work, or would you handle it differently?"*

The goal is to bring a decision that just needs a yes — not a situation that needs to be solved from scratch.

---

## THRESHOLD REFERENCE

*Quick reference for the financial thresholds that govern this document.*

| Threshold | Amount | Owner |
| --- | --- | --- |
| Team member independent spend | Up to $[X] | [Team Member] |
| Ops manager spend limit | Up to $[X] | [Ops Manager] |
| Refund / credit limit without approval | Up to $[X] | [Team Member / Ops Manager] |
| Founder approval required | Above $[X] | Founder |

*Update these numbers here and in the matrix above whenever thresholds change.*

---

## HOW TO MAINTAIN THIS DOCUMENT

**Review cadence:** Every 90 days — or when a role changes, a threshold no longer makes sense, or decisions keep routing to the wrong level.

**Owner of updates:** [Founder / Ops Manager]

**Signs this document needs an update:**

- The same type of decision keeps escalating to the founder when it shouldn't
- A team member is making decisions that should be escalating
- A new offer or service line creates decision scenarios not covered here
- A role changes significantly

---

*Decision Authority Matrix built as part of The Founder-Proof Method by Whitney Radacina. Prepared for [Your Business Name].*
