# Escalation Framework


# Escalation Framework

### [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 business's escalation architecture. It defines exactly what gets escalated, through what path, to whom, and with what response time standard. It exists so that when something goes wrong — or when a decision exceeds someone's authority — there is a clear, documented path forward that doesn't default to the founder.
>
> **Why it matters:** Right now, most escalations in your business follow an invisible path: everything goes up. Client complaint? Goes to the founder. Team member unsure of a decision? Goes to the founder. Unexpected situation with no obvious answer? Goes to the founder. Not because she's the only one who can handle it — but because nobody ever defined where things should actually stop. This document defines that.
>
> **How to use it:** Every person on the team should read this document in full. When something comes up that feels like it needs to go higher — check this document first. The answer to "who handles this" is in here. Review and update every 90 days or when a new situation reveals a gap.

---

## ESCALATION TIERS

*Every situation in this business that requires a decision or response falls into one of three tiers. Tier determines who owns the resolution — not seniority, not availability, not whoever is online.*

---

### Tier 1 — Team Level

**Resolved by:** The team member who owns that area of the business

**No notification required:** Unless it affects a client deliverable or timeline

**Response time:** Within [X] business hours

These are situations that fall clearly within a team member's defined role and authority. They have the information, the authority, and the capability to resolve it. It doesn't need to go anywhere else.

---

### Tier 2 — Ops Manager / Senior Lead Level

**Resolved by:** [Ops Manager name / Senior team member]

**Notify founder:** After resolution — brief Slack update is sufficient

**Response time:** Within [X] business hours

These are situations that exceed a team member's individual authority but don't require the founder's direct involvement. The ops manager or senior lead has full authority to resolve and owns the outcome.

---

### Tier 3 — Founder Level

**Resolved by:** Founder

**How to escalate:** Slack message with a clear summary + your recommendation (see escalation protocol below)

**Response time:** Founder responds within [X] business hours during working hours

These are situations that are genuinely strategic, financial above threshold, or carry relationship-level risk. They require the founder's judgment and authority. Everything else should be resolved before it reaches here.

---

## THE ESCALATION MAP

*Every category of situation your business encounters — and exactly which tier owns it.*

---

### CLIENT SITUATIONS

| Situation | Tier | Owner | Response Time |
| --- | --- | --- | --- |
| Client asks a routine question about their project | Tier 1 | [Team Member] | Within [X] hrs |
| Client requests a minor timeline adjustment | Tier 1 | [Team Member] | Within [X] hrs |
| Client hasn't responded to follow-up (2+ days) | Tier 1 | [Team Member] | Follow-up within [X] hrs |
| Client is confused about scope or deliverables | Tier 1 | [Team Member] | Clarify within [X] hrs using agreed scope doc |
| Client expresses mild dissatisfaction or frustration | Tier 2 | [Ops Manager] | Acknowledge within [X] hrs — resolve within [X] hrs |
| Client requests something outside agreed scope | Tier 2 | [Ops Manager] | Assess + respond within [X] hrs — escalate if cost or timeline impact is significant |
| Client requests a refund or credit | Tier 2 | [Ops Manager] | Up to $[X] — resolve independently. Above $[X] → Tier 3 |
| Client expresses significant dissatisfaction or threatens to leave | Tier 3 | Founder | Escalate immediately — founder responds within [X] hrs |
| Client relationship is at risk of breaking down entirely | Tier 3 | Founder | Escalate immediately |
| Client requests scope change with significant cost or timeline impact | Tier 3 | Founder | Escalate with full summary + recommendation |

---

### OPERATIONAL SITUATIONS

| Situation | Tier | Owner | Response Time |
| --- | --- | --- | --- |
| Internal deadline needs minor adjustment | Tier 1 | [Team Member] | Adjust + notify team same day |
| SOP needs a small update or correction | Tier 1 | [Team Member] | Update + document change |
| Tool or software has a minor issue | Tier 1 | [Team Member] | Troubleshoot + resolve within [X] hrs |
| Workflow bottleneck affecting one project | Tier 2 | [Ops Manager] | Identify root cause + resolve within [X] hrs |
| Client-facing deadline is at risk | Tier 2 | [Ops Manager] | Notify founder immediately + present resolution plan |
| A key tool or system goes down entirely | Tier 2 | [Ops Manager] | Triage immediately — notify founder within [X] hrs |
| A process failure affects multiple clients | Tier 3 | Founder | Escalate immediately with full impact assessment |
| A structural change to operations is needed | Tier 3 | Founder | Escalate with recommendation — founder decides |

---

### FINANCIAL SITUATIONS

| Situation | Tier | Owner | Response Time |
| --- | --- | --- | --- |
| Purchase within team member's approved threshold | Tier 1 | [Team Member] | Proceed — log the expense |
| Purchase between $[X] and $[X] | Tier 2 | [Ops Manager] | Approve or decline — notify founder after |
| Any financial commitment above $[X] | Tier 3 | Founder | Escalate before committing |
| Client invoice dispute | Tier 2 | [Ops Manager] | Investigate + respond. Escalate to Tier 3 if above $[X] |
| Unexpected expense that wasn't budgeted | Tier 2 | [Ops Manager] | Assess urgency — escalate to Tier 3 if above $[X] |
| Contractor invoice discrepancy | Tier 2 | [Ops Manager] | Resolve within [X] hrs — notify founder |

---

### TEAM SITUATIONS

| Situation | Tier | Owner | Response Time |
| --- | --- | --- | --- |
| Team member needs clarification on a task | Tier 1 | [Team Member / Ops Manager] | Within [X] hrs |
| Team member requests time off | Tier 2 | [Ops Manager] | Approve or flag within [X] hrs — notify founder if delivery-impacting |
| Team member performance concern (first instance) | Tier 2 | [Ops Manager] | Document + address directly within [X] days |
| Team member performance concern (recurring pattern) | Tier 3 | Founder | Escalate with documentation — founder involved in resolution |
| Team conflict that can't be resolved peer-to-peer | Tier 2 | [Ops Manager] | Mediate within [X] hrs — escalate if unresolved |
| Team member resignation | Tier 3 | Founder | Notify founder immediately |
| Request to adjust a team member's role or compensation | Tier 3 | Founder | Escalate with recommendation |

---

### UNEXPECTED + EDGE CASE SITUATIONS

| Situation | Tier | Owner | Response Time |
| --- | --- | --- | --- |
| A situation arises with no clear SOP or precedent | Tier 2 | [Ops Manager] | Assess + make a call. Document the decision. Escalate if client-facing or financial. |
| Something breaks and you don't know why | Tier 2 | [Ops Manager] | Triage immediately — notify founder within [X] hrs if client-impacting |
| A legal, compliance, or contractual question arises | Tier 3 | Founder | Escalate immediately — do not proceed without founder awareness |
| A situation feels wrong but doesn't clearly fit any category | Tier 3 | Founder | When in doubt, escalate. Bring your read on the situation and a recommendation. |

---

## ESCALATION PROTOCOL

*How to escalate — every time, without exception.*

---

### The Rule: Never Bring a Problem Without a Recommendation

When you escalate to the founder, you are not handing off the problem. You are asking for a decision on a recommendation you've already formed. This keeps the founder in a decision-making role — not a problem-solving role.

---

### The Escalation Message Format

Use this format every time you escalate via Slack:

---

**SITUATION:** [One sentence — what happened]

**IMPACT:** [Who or what is affected and how]

**WHAT I'VE DONE SO FAR:** [Any steps already taken]

**MY RECOMMENDATION:** [What you think should happen next]

**DECISION NEEDED:** [The specific yes/no or choice you need from the founder]

**DEADLINE:** [When a response is needed by]

---

**Example:**

SITUATION: [Client name] has responded to the Week 3 check-in saying they're feeling behind and worried we won't hit the Week 6 deadline.

IMPACT: If the timeline slips, it affects their planned team launch on [date].

WHAT I'VE DONE SO FAR: Reviewed the project board — we're actually on track. The confusion seems to be a communication gap, not a delivery gap.

MY RECOMMENDATION: I send a reassurance message today with a clear visual of where we are vs. where we need to be by Week 6, and schedule a 20-minute call this week to walk them through it.

DECISION NEEDED: Do you want to be on that call, or should I handle it?

DEADLINE: I'd like to respond to them today.

---

### Response Time Expectations for Escalations

| Tier | Escalation Response Time |
| --- | --- |
| Tier 1 | No escalation — resolved at team level |
| Tier 2 | Ops Manager responds within [X] business hours |
| Tier 3 — Standard | Founder responds within [X] business hours |
| Tier 3 — Urgent | Founder responds within [X] hours — flag as URGENT in Slack |

*Urgent = active client relationship at risk, a financial commitment with a hard deadline, or something that is actively breaking right now.*

---

## WHAT "URGENT" MEANS

*Not everything is urgent. Here is the exact definition used in this business.*

**Urgent escalation (respond within [X] hours):**

- A client has expressed they want to leave or is threatening to escalate externally
- A system failure is actively preventing client delivery right now
- A financial commitment with a hard external deadline is at risk
- Something has happened that could damage the business's reputation or relationships

**Standard escalation (respond within [X] business hours):**

- Everything else on the Tier 3 list

**Not an escalation:**

- Everything on the Tier 1 and Tier 2 list
- Situations where the answer is in the Decision Authority Matrix
- Situations where the answer is in an SOP
- Anything that feels uncomfortable but falls within your defined authority — own it

---

## ESCALATION RED FLAGS

*Signs the escalation framework isn't working — and what to do when you notice them.*

| Red Flag | What It Signals | What To Do |
| --- | --- | --- |
| The same type of situation keeps reaching Tier 3 | The threshold is wrong or the team needs more authority in this area | Revisit the matrix — move it to Tier 2 |
| The founder is responding to Tier 1 situations | The team isn't using the framework — or isn't confident in their authority | Revisit the Role Clarity Matrix + Decision Authority Matrix with the team |
| Escalations are arriving without recommendations | The team hasn't internalized the escalation protocol | Reiterate the format — bring a recommendation every time |
| The ops manager is bottlenecking Tier 2 resolutions | Response times are too slow or authority isn't clear enough | Review Tier 2 ownership + thresholds |
| Team members are making Tier 3 decisions independently | Authority boundaries need to be reclarified | Immediate conversation + document update |

---

## HOW TO MAINTAIN THIS DOCUMENT

**Review cadence:** Every 90 days — or when a pattern of mis-escalations reveals a gap.

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

**Update immediately when:**

- A new offer or service line creates escalation scenarios not covered here
- A role changes and ownership shifts
- A recurring escalation pattern reveals a threshold needs to move
- A situation occurred that wasn't covered and a precedent was set

---

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