Welcome to the Founder-Proof Kit

You bought yourself a little breathing room.

You just did the thing most founders put off for years. Watch the walkthrough first, then fill in the three templates in order. About an hour, and your team stops having to guess.

Do it in this order

These three documents work together, and the order matters. First, get clear on who owns what. Then decide what those people have the authority to do. Finally, establish what happens when something needs to be escalated.

  1. 20 min

    Role Clarity Matrix

    Get everyone’s responsibilities out of your head and onto paper. Start with the founder example from Kiln & Co., then work through your own.

  2. 15 min

    Decision Authority Matrix

    Decide what your team can handle without checking with you first. You’ll set the limits based on your business, not someone else’s.

  3. 10 min

    Escalation Framework

    Give your team a clear plan for what happens when something goes wrong, who gets involved, and when.

  4. 15 min

    Walk your team through it

    Don’t just send everyone a document and hope for the best. Talk through all three together, answer questions, and make sure everyone understands what they’re responsible for.

Plan for about 60 minutes, although every business is different. And if you’re struggling to figure out who owns something, pay attention to that. It’s probably something worth looking into.

Everything in one go

Grab the whole kit.

Every template, worked example, AI prompt and bonus as plain files in tidy folders. They open in Notion, Google Docs, Word or any text editor.

Founder-Proof-Kit.zip

Document 1 of 3

Role Clarity Matrix

Who owns what, and what does owning it mean?

In this one: Start with yourself. Seriously. Write down everything that still comes to you, including the things you probably shouldn’t be handling anymore. Then work through the rest of your team.

Download .md
Worked example + blank template

Role Clarity Matrix: Kiln & Co. worked example

Worked example. Kiln & Co. is a made-up business and these numbers are examples. Set your own.

Kiln & Co.

Prepared by: Whitney Radacina — The Founder-Proof Method

Date: November 18, 2026

Version: 1.0 — The Founder-Proof Kit


What this document is: This is your team's operating clarity document. It defines what each person on your team owns — not just what they do, but what results they are accountable for, what they are empowered to decide without you, and where their role begins and ends. This document exists so you stop being the answer to every question, and your team stops waiting for permission to lead.

How to use it: Share this with your full team. Walk through it together. Every person should leave that conversation knowing exactly what is theirs, what isn't, and who to go to when something falls outside their lane. Review and update it every 90 days or when a role changes.


FOUNDER ROLE — Maya Ortega

Title: Founder + CEO


What You Own

These are the outcomes only you should be driving. If you're spending significant time on anything outside this list, something in the architecture needs to change.

Outcome What It Means in Practice
Business vision + strategic direction Where Kiln & Co. is going across the shop, classes and wholesale, what it stands for, and what it says no to (for example, no mass-produced lines and no more than three revenue streams)
Key client relationships Wholesale accounts. Maya sets the pricing, takes the renewal conversations, and steps in when an account is unhappy. Dev handles the day-to-day with them
Revenue growth + offer development New collections, new class series, new wholesale terms, and any price change
Hiring + team culture Who joins Kiln & Co., who is let go, and how the studio feels to work in. Maya makes every hire and every contractor decision
Final financial decisions Anything above $1,500, whether it is a spend or a commitment (an example number; set your own)

What You Are No Longer The Default For

These are the things that have been routing to you that now have a defined owner. Your job is to stop answering these — and trust the architecture.

  • Order status, class booking changes and everyday customer questions (Dev)
  • Refunds up to $500 (Dev up to $150, Priya up to $500)
  • Studio scheduling, who covers which shift, and room and kiln-time conflicts (Priya)
  • Supply orders, glaze and clay stock, and firing schedule changes (Tessa)
  • Posting class schedule updates and day-to-day Instagram and email sends (Jo)
  • Chasing unpaid wholesale invoices (Priya)

Your Decision Threshold

The line between what you decide and what the team decides.

You decide: Anything strategic, anything above $1,500, wholesale pricing, new offers and price changes, hiring or ending a contractor, public statements about a dispute, anything legal, and any wholesale situation that puts the relationship at risk.

The team decides: Everything else. If it falls within their defined role and below the escalation threshold — it's theirs. They don't need to check with you first.


TEAM ROLES


Priya Shah — Studio Operations Manager

Reports to: Maya Ortega (Founder + CEO)

Primary category: Team & Decision Architecture


Owned Outcomes

What this person is accountable for — the results, not just the tasks. If these outcomes aren't being hit, this is the person responsible.

Outcome What Success Looks Like
The team can run without Maya in the room Fewer than 5 questions a week reach Maya that Priya, Dev, Tessa or Jo could have answered. Tracked in the weekly check-in
Escalations get answered on time Tier 2 questions answered within 4 business hours, and 2 hours when urgent. Checked every Friday against the escalation log
Cash and costs stay inside the plan Operating spend stays within the monthly budget Maya signs off on, and every unpaid wholesale invoice is followed up within 3 business days of going past due
Role docs and decision rules stay current This document and the decision rules are reviewed every 90 days, with changes shared with the team within a week

Day-to-Day Responsibilities

The recurring work that drives the outcomes above.

  • Runs the 30-minute Monday team check-in and sends out the notes the same day
  • Answers Tier 2 escalations from Dev, Tessa and Jo, and passes only true Tier 3 items to Maya
  • Approves refunds from $151 up to $500 and operations spend up to $1,500
  • Chases unpaid wholesale invoices and keeps the invoice tracker up to date
  • Reviews the weekly numbers (orders, class seats sold, refunds, open wholesale invoices) and flags anything off to Maya every Friday
  • Coordinates Jo's content calendar against the class and firing schedules

Decision Authority

What this person is fully empowered to decide and act on — without checking with the founder first.

Can decide independently:

  • Operations spend up to $1,500 (equipment repairs, studio supplies, software, shipping materials)
  • Refunds from $151 up to $500
  • Shift swaps, schedule changes and who covers what in the studio
  • Settling disagreements between Dev, Tessa and Jo about priorities or timing
  • How and when unpaid wholesale invoices are chased, including payment reminders and payment plans of up to 30 days

Does not decide without escalating:

  • Any spend or commitment above $1,500
  • Refunds above $500
  • Wholesale pricing, new offers or price changes
  • Hiring or ending a contractor
  • Public statements about a dispute, and anything legal

Interface Points

Who this person works with regularly and what they coordinate on.

Person What They Coordinate On Cadence
Maya Ortega Tier 3 escalations, weekly numbers, budget, the Friday wrap-up Weekly, and as needed for escalations
Dev Okafor Refund approvals, order and class booking problems, wholesale account support Daily
Tessa Lindqvist Firing schedule against ship dates, supply spend, quality problems Daily
Jo Brandt Class and promotion scheduling, content calendar Weekly
Wholesale accounts Unpaid invoice follow-up only. Pricing and terms stay with Maya As needed, within 3 business days of an invoice going past due

Escalation Triggers

The specific situations where this person stops and escalates — upward to the founder, or sideways to another team member.

Escalate to Maya when:

  • A wholesale account says it may leave, or asks to change its pricing or terms
  • A refund or spend above the limit is needed, or a decision would commit the studio to more than $1,500
  • A customer-safety issue comes up, or a payment or order failure affects more than one customer (urgent, so Maya hears within 2 hours)
  • A public complaint is gaining traction, or anything legal shows up, such as a lawyer's letter or a chargeback dispute that turns into a claim

What's Not Their Job

Explicit boundaries — what this role does not own and should not be absorbing.

  • Setting wholesale pricing or negotiating terms with wholesale accounts
  • Deciding new offers, price changes or the studio's direction
  • Throwing, glazing or firing work, and answering everyday customer questions (that is Tessa's and Dev's work, and Priya steps in only when they are out)

Dev Okafor — Client Experience Lead

Reports to: Priya Shah (Studio Operations Manager)

Primary category: Client Experience


Owned Outcomes

What this person is accountable for — the results, not just the tasks. If these outcomes aren't being hit, this is the person responsible.

Outcome What Success Looks Like
Customer questions get answered fast Every email and message answered the same business day. Nothing sits more than 24 hours without a reply
Orders and class bookings run without errors Fewer than 2% of orders need a fix after they ship. Class bookings are confirmed within 1 business day
Problems get fixed in one touch At least 9 in 10 refund and replacement requests are settled without going to Priya
Wholesale accounts feel looked after Every wholesale order confirmed within 1 business day. Questions answered the same day. Pricing questions passed to Maya with the account's history attached

Day-to-Day Responsibilities

The recurring work that drives the outcomes above.

  • Works the shared inbox and the shop's contact form, replying the same business day
  • Confirms online orders, tracks shipping and answers where-is-my-order questions
  • Manages class bookings, waitlists, reschedules and reminder emails
  • Checks in with students midway through each multi-week class series
  • Handles wholesale order confirmations, reorders at existing prices, delivery questions and invoice copies
  • Logs every refund, remake and escalation in the shared tracker

Decision Authority

What this person is fully empowered to decide and act on — without checking with the founder first.

Can decide independently:

  • Refunds up to $150 per order
  • A replacement or remake of a damaged item at no charge
  • Moving a student to a different class date, or putting them on a waitlist
  • Answering any customer or wholesale question that already has an answer in the studio's policies

Does not decide without escalating:

  • Refunds above $150 (go to Priya, who can approve up to $500)
  • Any wholesale pricing, discount or change to wholesale terms (go to Maya)
  • Any spend or commitment above what the role allows
  • Public replies to a complaint, and anything legal

Interface Points

Who this person works with regularly and what they coordinate on.

Person What They Coordinate On Cadence
Priya Shah Refunds above $150, tricky customer cases, weekly numbers Daily, as needed
Maya Ortega Wholesale pricing questions and accounts at risk, passed up through Priya unless urgent As needed
Tessa Lindqvist Remakes, firing status, damaged items, and whether an item can ship on the promised date Daily
Jo Brandt Class seats left, new class dates, promotion questions from customers Weekly
Customers and wholesale accounts Order, booking and account questions, and everyday wholesale support Same business day

Escalation Triggers

The specific situations where this person stops and escalates — upward to the founder, or sideways to another team member.

Escalate to Priya when:

  • A refund above $150 is needed, or a customer is unhappy and a standard reply has not settled it
  • An order or booking problem affects more than one customer
  • A wholesale account asks about pricing or terms, or says it may leave (Priya takes it to Maya the same day)
  • A customer reports a safety issue, such as a chipped or cracked piece that cut someone, or a public complaint starts gaining traction (urgent, reply within 2 hours)

What's Not Their Job

Explicit boundaries — what this role does not own and should not be absorbing.

  • Setting or changing wholesale pricing, or negotiating terms
  • Deciding the firing schedule or what gets made (Tessa)
  • Posting on Instagram or sending marketing emails (Jo)

Tessa Lindqvist — Production Lead

Reports to: Priya Shah (Studio Operations Manager)

Primary category: Systems & Operations


Owned Outcomes

What this person is accountable for — the results, not just the tasks. If these outcomes aren't being hit, this is the person responsible.

Outcome What Success Looks Like
Orders are made on time At least 95% of shop and wholesale orders leave the studio by the promised ship date
Firing schedule is planned and shared Next two weeks of firings posted every Monday, and any change shared with Priya and Dev the same day
Quality stays high Fewer than 5% of pieces rejected after firing, and every customer-facing flaw caught before packing
Inventory never runs out unexpectedly Clay, glaze and packing supplies counted every Friday, with reorders placed before anything drops below 2 weeks of stock

Day-to-Day Responsibilities

The recurring work that drives the outcomes above.

  • Plans the throwing, glazing and firing schedule and keeps it current
  • Loads and unloads kilns and logs each firing
  • Checks every piece for flaws before it is packed or goes to a class or wholesale order
  • Counts clay, glaze and packing supplies each Friday and places reorders
  • Tells Dev when a promised ship date is at risk, with a new date, as soon as she knows
  • Keeps the studio equipment clean and the kilns maintained

Decision Authority

What this person is fully empowered to decide and act on — without checking with the founder first.

Can decide independently:

  • Supply and material orders up to $500
  • Rescheduling firings, including moving one kiln load ahead of another
  • Rejecting or re-making any piece that does not meet the quality standard
  • Which pieces get made first when the schedule is tight, within the ship dates already promised

Does not decide without escalating:

  • Supply or equipment spend above $500 (go to Priya, who can approve up to $1,500)
  • Any spend or commitment above $1,500 (go to Maya through Priya)
  • Promising a new ship date to a wholesale account (Dev tells the account; Priya checks with Maya if the account is at risk)
  • Changing a recipe, product line or price
  • Hiring or ending a contractor

Interface Points

Who this person works with regularly and what they coordinate on.

Person What They Coordinate On Cadence
Priya Shah Supply spend above $500, kiln repairs, staffing the studio, anything that threatens ship dates Daily, as needed
Dev Okafor Order status, remakes, ship dates, damaged items Daily
Jo Brandt What is coming out of the kiln and when, so photos and class promotion match what is real Weekly
Maya Ortega New collections and product ideas, only when Maya brings them As needed

Escalation Triggers

The specific situations where this person stops and escalates — upward to the founder, or sideways to another team member.

Escalate to Priya when:

  • A kiln breaks or fails and it will push back more than one order
  • A supply order above $500 is needed, or a supplier cannot deliver clay or glaze that the schedule depends on
  • A promised ship date for a wholesale account cannot be met (Priya takes it to Maya the same day if the account is at risk)
  • A quality problem shows up in more than one batch, or a piece may be unsafe for food use (urgent, reply within 2 hours)

What's Not Their Job

Explicit boundaries — what this role does not own and should not be absorbing.

  • Answering customer questions or sorting out refunds (Dev)
  • Setting prices or deciding what the studio makes next (Maya)
  • Posting about the studio or running class promotion (Jo)

Jo Brandt — Marketing + Community Coordinator

Reports to: Maya Ortega for strategy, Priya Shah for scheduling. Part-time contractor.

Primary category: Client Experience


Owned Outcomes

What this person is accountable for — the results, not just the tasks. If these outcomes aren't being hit, this is the person responsible.

Outcome What Success Looks Like
Class seats fill At least 80% of seats sold at least 3 days before each class series starts
The email list keeps growing One email a week goes out on schedule, and the list grows by at least 100 new subscribers a month
Instagram stays active and on-brand 4 posts a week, with replies to comments and messages within 1 business day
Promotion matches what is real Every post and email about a class, drop or sale checked against the class schedule and firing schedule before it goes out

Day-to-Day Responsibilities

The recurring work that drives the outcomes above.

  • Writes and sends the weekly email and any campaign emails Maya has approved
  • Plans and posts Instagram content, and replies to comments and messages
  • Posts class schedule updates to the website, email and Instagram the same day they change
  • Promotes upcoming classes and workshops and reports seats sold to Priya each week
  • Tracks ad results and keeps ad spend within the monthly limit
  • Collects photos and customer stories from Tessa and Dev for posts

Decision Authority

What this person is fully empowered to decide and act on — without checking with the founder first.

Can decide independently:

  • Ad spend up to $200 per month
  • Discounts up to 15% inside a campaign that Maya has already approved
  • What goes in each post and email, within the brand guidelines and the approved campaign plan
  • Posting times and the order of the content calendar

Does not decide without escalating:

  • Ad spend above $200 per month, or any other spend above what the role allows
  • Discounts above 15%, or any discount outside a campaign Maya has approved
  • New offers, price changes or wholesale pricing (Maya)
  • Public statements about a dispute, or replies to a public complaint
  • Anything legal, such as using a customer's photo without permission or running a giveaway

Interface Points

Who this person works with regularly and what they coordinate on.

Person What They Coordinate On Cadence
Maya Ortega Marketing strategy, campaign approvals, new offers Every 2 weeks, and before any new campaign
Priya Shah Content calendar against class and firing schedules, seats sold Weekly
Dev Okafor Customer questions that come in through Instagram and email, class seats left Weekly, as needed
Tessa Lindqvist Photos, what is coming out of the kiln and when Weekly
Customers and followers Replies to comments and messages about classes and the shop Within 1 business day

Escalation Triggers

The specific situations where this person stops and escalates — upward to the founder, or sideways to another team member.

Escalate to Maya (strategy) or Priya (scheduling and day-to-day) when:

  • A campaign needs more than $200 a month in ad spend, or a bigger discount than 15% (Maya)
  • A public complaint or a negative post starts gaining traction (Priya, urgent, reply within 2 hours, and Priya takes it to Maya)
  • A class date or firing date changes in a way that affects what has already been promoted (Priya)
  • A customer asks about a refund, a damaged item or a wholesale account in a comment or message (pass it to Dev the same day)

What's Not Their Job

Explicit boundaries — what this role does not own and should not be absorbing.

  • Refunds, order problems and customer service (Dev)
  • Setting prices, discounts outside approved campaigns, or wholesale terms (Maya)
  • Deciding what the studio makes or when it fires (Tessa and Priya)

ROLE OVERVIEW — AT A GLANCE

A consolidated view of who owns what across the business. Use this as your quick reference.

Role Person Primary Ownership Decision Authority Level Escalates To
Founder / CEO Maya Ortega Vision, growth, key relationships, culture Full — sets the standard —
Studio Operations Manager Priya Shah Running the studio day to day, the team's decisions, cash and costs, wholesale invoices High — spend up to $1,500, refunds up to $500 Maya Ortega
Client Experience Lead Dev Okafor Orders, class bookings, customer questions, wholesale account support Defined threshold — refunds up to $150, free replacements Priya Shah
Production Lead Tessa Lindqvist Making the work, firing schedule, inventory, quality control Defined threshold — supply orders up to $500, firing reschedules Priya Shah
Marketing + Community Coordinator (part-time contractor) Jo Brandt Email, Instagram, class promotion Defined threshold — ads up to $200 a month, discounts up to 15% in approved campaigns Maya Ortega for strategy, Priya Shah for scheduling

OWNERSHIP GAP LOG

Anything that surfaced during the build that currently has no clear owner. These need to be assigned before this document is considered complete.

Workflow / Outcome Currently Falling To Recommended Owner Action Required
Mid-class-series check-ins with students Maya by default Dev Okafor Reassign + add to Dev's role
Chasing unpaid wholesale invoices Maya Priya Shah Reassign + automate where possible (invoice reminders sent automatically at 7 and 14 days past due)
Tracking the firing schedule against promised ship dates Nobody Tessa Lindqvist Assign + build SOP
Posting class schedule updates Maya Jo Brandt Reassign + add to Jo's role

HOW TO MAINTAIN THIS DOCUMENT

Review cadence: Every 90 days — or immediately when a role changes, a new hire joins, or a new offer launches. The first review is due February 16, 2027.

Who owns the update: Priya Shah

What triggers an immediate update:

  • A team member's responsibilities shift significantly
  • A new hire joins the business
  • A role is eliminated or restructured
  • Recurring escalations reveal that a decision boundary needs to be redrawn

Role Clarity Matrix built as part of The Founder-Proof Method by Whitney Radacina. Prepared for Kiln & Co.

Hit Copy, then paste into Notion or Google Docs. The headings and tables come with it. Fill in every [bracket].

Document 2 of 3

Decision Authority Matrix

Who can decide what, up to what limit?

In this one: This is where you give your team permission to actually do their jobs. Set spending limits, approval requirements, and decision-making authority based on what you’re comfortable handing over. The Kiln & Co. numbers are just examples.

Download .md
Worked example + blank template

Decision Authority Matrix: Kiln & Co. worked example

Worked example. Kiln & Co. is a made-up business and these numbers are examples. Set your own.

Kiln & Co.

Prepared by: Whitney Radacina — The Founder-Proof Method

Date: November 18, 2026

Version: 1.0 — The Founder-Proof Kit


What this document is: This is how Kiln & Co. makes decisions. It says who can decide what, up to what limit, without asking Maya first. Every kind of decision in the studio has a named owner. Every owner has a limit. Nothing goes to Maya by default anymore.

Why it matters: Kiln & Co. does about $1.4M a year across the online shop, classes and workshops, and wholesale. For a long time Maya answered every question, approved every refund, and was the only person who talked to wholesale accounts. The team wasn't asking because they couldn't decide. They were asking because nobody ever told them what was theirs. This document tells them.

How to use it: Maya, Priya, Dev, Tessa and Jo walk through this together before it goes live. Everyone reads the whole thing, not just their own rows. When Dev knows what Tessa can decide, he stops sending her questions to Maya. Priya reviews it every 90 days, or sooner if 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. Dev, Tessa, Jo and Priya, in the rows they own
Level 2 — Decide + Notify Decides and acts, then tells the named person afterward. Example: Tessa moves a firing, then tells Dev the same day. Dev, Tessa, Jo and Priya, in the rows they own
Level 3 — Consult + Decide Asks one named person before deciding, then owns the outcome. Example: Jo checks the send date with Priya, then sends the email. Dev, Tessa, Jo and Priya, in the rows they own
Level 4 — Escalate Does not decide. Brings it to Maya (or Priya, where a row says so) with a recommendation. Maya (founder), Priya (senior lead)

THE MATRIX


1. CLIENT DECISIONS

"Client" at Kiln & Co. means shop customers, class students and wholesale accounts.

Decision Owner Authority Level Threshold / Notes
Responding to routine customer questions (orders, shipping, class details, wholesale account questions) Dev Level 1 Same business day
Sending order, class and wholesale status updates Dev Level 1 Order confirmed, order shipped, class reminder, wholesale delivery date
Scheduling class bookings, studio visits and wholesale calls Dev Level 1 Using the booking tool. Wholesale calls that involve pricing go to Maya
Checking in with students partway through a class series Dev Level 1 Used to default to Maya. Now Dev's. Mid-series check-in at the halfway session
Approving minor changes to an open order or booking Dev Level 2 No extra cost, and no more than 3 business days added to ship or class date. Tell Tessa if it changes what she fires
Replacing or remaking a damaged item Dev Level 1 At no charge to the customer. Log it so Tessa can add the remake to her list
Issuing a partial refund or credit Dev / Priya Level 1 (Dev) / Level 2 (Priya) Dev: up to $150 per order, no approval. Priya: $151 to $500, then tells Maya in the weekly update. Over $500 goes to Maya
Handling a customer complaint Dev Level 3 Dev replies the same business day and owns the first response. If it isn't solved within one business day, Priya takes it (reply within 4 business hours)
Ending a wholesale relationship or banning a customer Maya Level 4 Always escalates to Maya
Changing wholesale pricing, launching a new offer, or changing a price Maya Level 4 Maya only. Always escalates to Maya
Making a commitment outside what we normally offer (custom wholesale runs, private events, special terms) Maya Level 4 Always escalates to Maya

2. OPERATIONAL DECISIONS

Decision Owner Authority Level Threshold / Notes
Assigning and managing daily tasks Priya (studio and office), Tessa (production floor) Level 1 Within current work and capacity
Rescheduling firings Tessa Level 2 Tell Dev the same day if any promised ship date or class date is affected
Tracking the firing schedule against promised ship dates Tessa Level 1 Nobody owned this before. Now Tessa's. She flags any date at risk to Dev before it slips
Updating or improving an existing SOP Priya, Dev, Tessa Level 2 Write down the change and tell Priya
Creating a new SOP Priya, Dev, Tessa Level 2 Build it, tell Priya, add it to the shared SOP folder
Changing a tool or platform the team uses Priya Level 3 Check with Maya before switching anything customers see, like the shop checkout or class booking tool
Restructuring a workflow or process Priya Level 3 Bring Maya a recommendation before changing anything
Changing how projects and tasks are organized in the team's task system Priya Level 4 Escalates to Maya

3. FINANCIAL DECISIONS

Decision Owner Authority Level Threshold / Notes
Ordering supplies and materials (clay, glazes, packaging) Tessa Level 1 Up to $500 per order
Spending on operations (tools, subscriptions, equipment repairs, studio needs) Priya Level 2 Up to $1,500. Tell Maya afterward. A yearly subscription counts at its full yearly cost
Ad spend Jo Level 1 Up to $200 per month
Any spend or commitment over $1,500 Maya Level 4 Always escalates to Maya
Sending invoices (shop, class and wholesale) Dev (shop and class), Priya (wholesale) Level 1 Using the approved invoice template and current prices
Chasing unpaid wholesale invoices Priya Level 1 Used to default to Maya. Now Priya's. Maya steps in only if a payment is 30 days late and the account is at risk
Issuing refunds Dev / Priya Level 1 (Dev) / Level 2 (Priya) Dev: up to $150 per order. Priya: up to $500, then tells Maya. Over $500 goes to Maya
Contractor or vendor payments Priya Level 2 Within the approved budget. Tell Maya
Hiring a new contractor or team member Maya Level 4 Always escalates to Maya
Ending a contractor relationship Maya Level 4 Always escalates to Maya

4. COMMUNICATION DECISIONS

Decision Owner Authority Level Threshold / Notes
Responding to inbound DMs, emails and inquiries Dev Level 1 Using the approved replies and tone guide. Same business day
Posting to Instagram Jo Level 1 Within the approved content plan
Posting class schedule updates Jo Level 1 Used to default to Maya. Now Jo's. Priya sends her the schedule changes
Offering a discount inside a campaign Jo Level 1 Up to 15%, and only in a campaign Maya already approved
Responding to media or press inquiries Maya Level 4 Always escalates to Maya
Making a public statement, including anything about a dispute Maya Level 4 Maya only. Nobody else posts or replies publicly about a dispute
Anything legal (contracts, claims, threats, takedown notices) Maya Level 4 Maya only. Don't reply. Send it to Maya
Telling existing customers about a business change (new policy, price change, closure) Maya Level 4 Always escalates to Maya
Sending a campaign or broadcast email Jo Level 3 Maya approves the campaign and offer first. Jo checks the send date with Priya, then sends

5. TEAM DECISIONS

Decision Owner Authority Level Threshold / Notes
Assigning tasks to team members Priya Level 1 Within each person's role and capacity
Approving time off requests Priya Level 2 Tell Maya if it affects a class, a firing run or a wholesale delivery
Giving performance feedback Priya Level 2 Write it down. Tell Maya if the same issue comes up again
Adjusting a team member's responsibilities Maya Level 3 Maya asks Priya, then decides
Hiring a new team member Maya Level 4 Always escalates to Maya
Ending employment or a contractor relationship Maya Level 4 Always escalates to Maya
Changing compensation Maya Level 4 Always escalates to Maya

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. Example: Tessa moves a firing to Thursday. She can move it back.
Does this affect a client relationship at a strategic level? Escalate. Level 4. Example: a cafe asks for new wholesale terms.
Does this involve money above your threshold? Escalate. Level 4. Example: Dev is asked for a $200 refund. That goes to Priya. A $600 refund goes to Maya.
Does this change how the business operates structurally? Consult first. Level 3 minimum. Example: Priya wants to move class bookings to a new tool.
Is this something that happens regularly and has a known answer? You own it. Level 1. Example: "When will my order ship?" is Dev's.
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, Salt & Sage Cafe is upset. What should I do?"

Do say: "Hey, Salt & Sage Cafe got 12 mugs and 3 arrived chipped. I've checked the photos and here's what I think we should do: remake the 3 mugs at no charge, ship them Friday, and take 10% off their next order. 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.

How fast each level replies (example numbers):

Who Reply time
Tier 1: the team (Dev, Tessa, Jo) Same business day
Tier 2: Priya Within 4 business hours
Tier 3: Maya Within 1 business day
Urgent, anyone Within 2 hours

Urgent means: a customer-safety issue, a payment or order failure affecting more than one customer, a wholesale account at risk of leaving, or a public complaint gaining traction. Mark it URGENT in the message so it jumps the line.


THRESHOLD REFERENCE

Quick reference for the financial thresholds that govern this document. All amounts are examples.

Threshold Amount Owner
Team member independent spend Up to $500 per supply or material order. Up to $200 per month on ads Tessa (supplies), Jo (ads)
Ops manager spend limit Up to $1,500 on operations Priya
Refund / credit limit without approval Up to $150 per order (Dev). Up to $500 (Priya, then tells Maya) Dev / Priya
Founder approval required Above $1,500, for any spend or commitment Maya

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. Next review: February 16, 2027.

Owner of updates: Priya

Signs this document needs an update:

  • The same type of decision keeps escalating to Maya 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, like a new workshop format or a new wholesale account type
  • A role changes significantly, like Dev taking on more wholesale work

Decision Authority Matrix built as part of The Founder-Proof Method by Whitney Radacina. Worked example for Kiln & Co., a made-up business.

Hit Copy, then paste into Notion or Google Docs. The headings and tables come with it. Fill in every [bracket].

Document 3 of 3

Escalation Framework

When something goes wrong, where does it stop and who hears about it?

In this one: Who does your team go to when they can’t solve something themselves? If the answer is always you, that’s worth paying attention to. And if you don’t have someone who can take that second level of responsibility yet, that’s okay. Write it down.

Download .md
Worked example + blank template

Escalation Framework: Kiln & Co. worked example

Worked example. Kiln & Co. is a made-up business and these numbers are examples. Set your own.

Escalation Framework

Kiln & Co.

Prepared by: Whitney Radacina — The Founder-Proof Method

Date: 2026-11-18

Version: 1.0 — The Founder-Proof Kit


What this document is: This is how Kiln & Co. handles escalation. It says what gets escalated, who it goes to, and how fast they answer. It exists so that when something goes wrong, or a decision is bigger than someone's authority, there is a written path that doesn't end at Maya by default.

Why it matters: Right now, most escalations at Kiln & Co. follow an invisible path: everything goes up. A customer wants a refund? Goes to Maya. Dev isn't sure about a damaged-mug replacement? Goes to Maya. A cafe asks a question about an order? Goes to Maya, because she is the only one who has ever talked to wholesale accounts. Not because she's the only one who can handle it, but because nobody ever defined where things should stop. This document defines that.

How to use it: Everyone on the team (Dev, Tessa, Jo and Priya) reads this in full. When something feels like it needs to go higher, check this document first. The answer to "who handles this" is in here. We review it every 90 days, or sooner when a new situation shows a gap.


ESCALATION TIERS

Every situation at Kiln & Co. that needs a decision or a response falls into one of three tiers. The tier decides 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. Dev owns orders, class bookings, customer questions and wholesale account support. Tessa owns throwing, glazing, firing, inventory and quality control. Jo owns email, Instagram and class promotion.

No notification required: Unless it affects a customer's order, a class date or a promised ship date

Response time: Same business day

These situations fall clearly inside someone's role and authority. They have the information and the authority to resolve it. It doesn't need to go anywhere else. Example limits (set your own): Dev refunds up to $150 per order and remakes damaged items at no charge; Tessa orders supplies and materials up to $500; Jo spends up to $200 a month on ads.


Tier 2 — Ops Manager / Senior Lead Level

Resolved by: Priya Shah, Studio Operations Manager

Notify founder: After resolution. A short Slack update to Maya is enough.

Response time: Within 4 business hours

These situations are bigger than one team member's authority but don't need Maya. Priya has full authority to resolve them and owns the outcome. Example limits (set your own): Priya spends up to $1,500 on operations and approves refunds up to $500.


Tier 3 — Founder Level

Resolved by: Maya Ortega, Founder + CEO

How to escalate: Slack message to Maya with a clear summary and your recommendation (see the escalation protocol below)

Response time: Maya responds within 1 business day during working hours

These are situations that are strategic, involve money over $1,500, or put a relationship at risk. They need Maya's judgment and authority. Maya alone decides wholesale pricing, new offers and price changes, hiring or ending a contractor, public statements about a dispute, and anything legal. Everything else should be resolved before it reaches her.


THE ESCALATION MAP

Every kind of situation Kiln & Co. runs into, and exactly which tier owns it.


CLIENT SITUATIONS

Situation Tier Owner Response Time
Customer asks a routine question about an order or a class booking Tier 1 Dev Same business day
Customer asks to move a class date or change a ship date slightly Tier 1 Dev Same business day
Customer hasn't answered a follow-up (2+ days) Tier 1 Dev Follow-up the same business day
Customer is confused about what a class or order includes Tier 1 Dev Clarify the same business day using the class or shop listing
Wholesale cafe asks a routine question about an existing order Tier 1 Dev Same business day
Item arrives damaged and the customer wants a replacement or remake Tier 1 Dev Same business day — no charge, no approval needed
Customer expresses mild frustration Tier 2 Priya Acknowledge within 4 business hours — resolve within 2 business days
Customer asks for something outside what was sold (a custom piece, a private class) Tier 2 Priya Assess + respond within 4 business hours — escalate if cost or timeline impact is large
Customer asks for a refund or credit Tier 2 Priya Up to $500 — resolve independently. Above $500 → Tier 3. (Dev handles up to $150 per order himself.)
Customer is very unhappy or threatens to leave Tier 3 Maya Escalate right away — Maya responds within 1 business day (2 hours if urgent)
Wholesale account asks for new pricing or new terms Tier 3 Maya Escalate with a summary + recommendation
Wholesale account is at risk of leaving Tier 3 Maya Escalate right away — flag as URGENT
Customer's complaint is public (review, post, tag) and gaining traction Tier 3 Maya Escalate right away — flag as URGENT. No public reply until Maya decides.

OPERATIONAL SITUATIONS

Situation Tier Owner Response Time
An internal deadline needs a small adjustment (glaze day, packing day) Tier 1 Tessa Adjust + tell the team the same day
A firing needs to be rescheduled Tier 1 Tessa Reschedule + tell Dev the same day so ship dates stay honest
An SOP needs a small fix or correction Tier 1 Whoever owns the area Update + note the change in the SOP
A tool has a minor issue (shop plugin, booking form, email tool) Tier 1 Dev for shop and bookings, Jo for email Troubleshoot + resolve the same business day
A bottleneck is slowing one order or one class Tier 2 Priya Find the cause + resolve within 4 business hours
A promised ship date or class date is at risk Tier 2 Priya Tell Maya right away + present the plan
The online shop, booking system or payment system goes down entirely Tier 2 Priya Triage right away — tell Maya within 2 hours
A failure affects more than one customer (payment or order failure, kiln batch lost) Tier 3 Maya Escalate right away with the full impact — flag as URGENT
A structural change is needed (new studio hours, new fulfillment setup) Tier 3 Maya Escalate with a recommendation — Maya decides

FINANCIAL SITUATIONS

Situation Tier Owner Response Time
Purchase inside someone's limit (Tessa supplies up to $500, Jo ads up to $200 a month) Tier 1 Tessa or Jo Go ahead — log the expense
Purchase between $500 and $1,500 Tier 2 Priya Approve or decline within 4 business hours — tell Maya after
Any spend or commitment above $1,500 Tier 3 Maya Escalate before committing
Customer or wholesale invoice dispute Tier 2 Priya Look into it + respond within 1 business day. Escalate to Tier 3 if above $1,500 or if the dispute is about wholesale pricing.
Unplanned expense that wasn't in the budget (a kiln repair, say) Tier 2 Priya Assess urgency — escalate to Tier 3 if above $1,500
Chasing an unpaid wholesale invoice Tier 2 Priya First reminder within 1 business day of the due date — tell Maya if it's 30+ days late
Contractor invoice doesn't match the agreed work (Jo's invoice, for example) Tier 2 Priya Resolve within 2 business days — tell Maya

TEAM SITUATIONS

Situation Tier Owner Response Time
Someone needs clarity on a task Tier 1 Priya (Dev and Tessa), Maya for strategy questions from Jo Same business day
Someone asks for time off Tier 2 Priya Approve or flag within 4 business hours — tell Maya if it affects firings, classes or ship dates
Performance concern, first time Tier 2 Priya Write it down + talk to the person directly within 3 business days
Performance concern, keeps happening Tier 3 Maya Escalate with notes — Maya joins the resolution
Two people can't sort out a conflict between themselves Tier 2 Priya Mediate within 1 business day — escalate if it's still stuck
Someone resigns Tier 3 Maya Tell Maya right away
Request to change someone's role or pay, or to hire or end a contractor Tier 3 Maya Escalate with a recommendation

UNEXPECTED + EDGE CASE SITUATIONS

Situation Tier Owner Response Time
Something comes up with no SOP and no past example Tier 2 Priya Assess + make a call. Write the decision down. Escalate if it touches a customer or money above Priya's limit.
Something breaks and nobody knows why (a glaze batch comes out wrong, the shop stops taking orders) Tier 2 Priya Triage right away — tell Maya within 2 hours if customers are affected
A legal, safety or contract question comes up (a wholesale contract, a claim that a piece hurt someone) Tier 3 Maya Escalate right away — don't go ahead without Maya knowing. A customer-safety issue is URGENT.
It feels wrong but doesn't fit any row Tier 3 Maya When in doubt, escalate. Bring your read and a recommendation.

ESCALATION PROTOCOL

How to escalate, every time, no exceptions.


The Rule: Never Bring a Problem Without a Recommendation

When you escalate to Maya, you are not handing the problem off. You are asking for a decision on a recommendation you've already formed. That keeps Maya deciding, not problem-solving.


The Escalation Message Format

Use this format every time you escalate by 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 Maya.

DEADLINE: When you need a response by.


Example (a real-looking message from Priya to Maya, flagged URGENT because a wholesale account is at risk):

URGENT

SITUATION: Fernwood Coffee, our biggest wholesale cafe, says they will move their mug orders to another studio if their late order of 48 mugs doesn't ship by Friday.

IMPACT: Fernwood is about $1,800 a month in wholesale sales, and two of their owner's friends run cafes we also supply. The order was due last Friday because a glaze firing came out patchy and Tessa had to redo it.

WHAT I'VE DONE SO FAR: Tessa moved the redo firing to tomorrow, so the mugs are ready to ship Thursday. Dev called Fernwood this morning and told them the new date. I gave them a $200 credit on this order, which is inside my limit. They still said they want to talk about pricing before they reorder.

MY RECOMMENDATION: You call their owner today and offer 10% off their next two orders. That is a wholesale pricing change, so it's yours to decide. I think it keeps the account for less than one lost month of sales.

DECISION NEEDED: Do you approve 10% off their next two orders, and do you want to make the call or should I make it with your numbers?

DEADLINE: Fernwood wants an answer by 5pm today, so I need your reply by 3pm. This is urgent, so a reply within 2 hours would be great.


Response Time Expectations for Escalations

Tier Escalation Response Time
Tier 1 No escalation. Resolved at team level the same business day.
Tier 2 Priya responds within 4 business hours
Tier 3 — Standard Maya responds within 1 business day
Tier 3 — Urgent Maya responds within 2 hours — flag as URGENT in Slack

Urgent = a customer-safety issue, a payment or order failure affecting more than one customer, a wholesale account at risk of leaving, or a public complaint gaining traction.


WHAT "URGENT" MEANS

Not everything is urgent. Here is the exact definition used at Kiln & Co.

Urgent escalation (respond within 2 hours):

  • A customer-safety issue (for example, a customer says a piece cracked or chipped and cut them)
  • A payment or order failure affecting more than one customer
  • A wholesale account at risk of leaving
  • A public complaint (review, post or tag) that is gaining traction

Standard escalation (respond within 1 business day):

  • Everything else on the Tier 3 list

Not an escalation:

  • Everything on the Tier 1 and Tier 2 list
  • Anything where the answer is in the Decision Authority Matrix
  • Anything where the answer is in an SOP
  • Anything that feels uncomfortable but is inside your authority. Own it.

ESCALATION RED FLAGS

Signs the framework isn't working, and what to do when you see them.

Red Flag What It Signals What To Do
Refund requests between $150 and $500 keep landing on Maya The limit is wrong, or those requests are not getting to Priya Check the thresholds. Send them to Priya, and raise the limit only if Priya is clearly handling them well.
Maya is answering Tier 1 questions again (order status, class bookings, cafe questions) The team isn't using the framework or isn't confident in their authority Go back over the Role Clarity Matrix and Decision Authority Matrix with Dev, Tessa and Jo
Escalations show up without a recommendation The team hasn't taken on the escalation format Reply with "What do you recommend?" and wait. Bring a recommendation every time.
Priya is the bottleneck on Tier 2 (answers take longer than 4 business hours) Her load is too heavy or her authority isn't clear enough Review what Priya owns and her limits. Move small items down to Dev or Tessa.
Someone commits to Tier 3 things alone (a discount on a wholesale order, a public reply to a dispute, ending a contractor) The line between Tier 2 and Tier 3 isn't clear to them Talk to them the same day and update this document

HOW TO MAINTAIN THIS DOCUMENT

Review cadence: Every 90 days, or sooner when a pattern of mis-escalations shows a gap.

Owner of updates: Priya Shah. She owns the next review.

Update immediately when:

  • A new offer or revenue stream (a new class series, a new wholesale line) creates situations that aren't covered here
  • A role changes and ownership moves
  • The same kind of escalation keeps repeating and a threshold needs to move
  • Something happened that wasn't covered and a precedent was set

Escalation Framework built as part of The Founder-Proof Method by Whitney Radacina. Prepared for Kiln & Co. (made-up example).

Hit Copy, then paste into Notion or Google Docs. The headings and tables come with it. Fill in every [bracket].

Let AI do the first draft.

You don’t have to start with a blank page. Open ChatGPT, Claude, or whatever AI tool you prefer. Copy the prompt, upload the blank template and completed example, and talk through how your business works. You can even use a voice note transcript if that’s easier.

AI can help you organize the information, but it doesn’t know your team or your business the way you do. You’re still responsible for the decisions, the numbers, and making sure everything is accurate before sharing it.

Prompt 1: Role Clarity Matrix

I'm going to give you two things: a blank Role Clarity Matrix template and a finished worked example for a different business. After that I'll describe my business and my team by brain dump.

Your job: fill in my blank template, following the structure of the example. Use my words and my situation. Do not copy the example's content.

Rules:
1. Do not invent names, roles, outcomes or dollar amounts. If I haven't told you something, leave the bracket in place and add it to a short list of open questions at the end.
2. Write plainly. No consulting language.
3. Under "What You Are No Longer The Default For" and the Ownership Gap Log, use the things I say still land on me.
4. When you finish, give me the open-questions list and nothing else.

Wait for my brain dump before you start.

Prompt 2: Decision Authority Matrix

I'm going to give you a blank Decision Authority Matrix, a finished worked example for a different business, and my completed Role Clarity Matrix. After that I'll tell you which decisions still land on me.

Fill in my blank template following the structure of the example, using the roles from my Role Clarity Matrix.

Rules:
1. Never choose a dollar limit, threshold or time for me. Where a number is needed and I haven't given one, leave a bracket and list it at the end as a question for me.
2. Use my decisions and my business, not the example's.
3. Keep the four decision levels exactly as the template defines them.
4. Finish with a short list of the numbers I still need to set.

Wait for my input before you start.

Prompt 3: Escalation Framework

I'm going to give you a blank Escalation Framework, a finished worked example for a different business, and my completed Role Clarity Matrix and Decision Authority Matrix. After that I'll tell you what has gone wrong in my business before.

Fill in my blank template following the structure of the example. Use the roles and limits already in my other two documents so nothing contradicts.

Rules:
1. Do not invent response times, tiers or people. If I haven't said, leave a bracket and list it at the end.
2. If I don't have anyone for Tier 2 yet, say so in the document and tell me which of my team could grow into it. Do not make up a role.
3. Write one realistic example escalation message from the situations I describe, using the template's message format.
4. Finish with the list of things I still need to decide.

Wait for my input before you start.

Bonuses

Three extras so it actually sticks.

Finish the three documents, then use these. They’re included, and they’re the part most people skip.

Bonus 1

Your business on one page

What do your three documents add up to?

In this one: Once all three are filled in, have AI squeeze them into one page your whole team can read in two minutes. Copy the prompt below, add your three finished documents, and see what you get. The Kiln & Co. example shows what yours should look like.

AI prompt: build your one-pager

I'm going to give you three finished documents for my business: a Role Clarity Matrix, a Decision Authority Matrix and an Escalation Framework. I'm also giving you a one-page example for a different business (Kiln & Co.).

Your job: turn my three documents into one page that follows the structure of the example. Sections: who owns what, what each person can decide without asking, when something goes wrong, gaps this closed, how it stays true.

Rules:
1. Use only what's in my documents. Do not invent names, limits or response times. If something is missing, leave a [bracket] and list it under open questions at the end.
2. Plain words. No consulting language. Keep it to one page.
3. Keep the tables as tables.
4. Do not copy the example's content. Use mine.

Here is the example, then my three documents:
Kiln & Co. example

Kiln & Co. on one page

Worked example. Kiln & Co. is a made-up business and these numbers are examples. Set your own.

This is what the three documents add up to once they're filled in. One page. Anyone on the team can read it in two minutes and know what's theirs, what they can decide, and what to do when something goes wrong.

Who owns what

Person Role Owns
Maya Ortega Founder + CEO Wholesale pricing, new offers and price changes, hiring and ending contractors, public statements about a dispute, anything legal
Priya Shah Studio Operations Manager (Tier 2) Day-to-day operations, the team's schedule, chasing unpaid wholesale invoices, the 90-day review
Dev Okafor Client Experience Lead Orders, class bookings, customer questions, wholesale account support, mid-class-series check-ins
Tessa Lindqvist Production Lead Throwing, glazing, firing schedule, inventory, quality control, tracking firings against promised ship dates
Jo Brandt Marketing + Community Coordinator (part-time) Email, Instagram, class promotion, posting class schedule updates

What each person can decide without asking

Person Can decide on their own Goes to
Dev Refunds up to $150 per order. Free replacement or remake of a damaged item. Priya, for anything over $150
Priya Operations spend up to $1,500. Refunds up to $500. Maya, for anything over $1,500 or $500 in refunds
Tessa Supply and material orders up to $500. Rescheduling firings. Priya, for anything over $500
Jo Ad spend up to $200 a month. Discounts up to 15% in a campaign Maya already approved. Maya, for anything else

When something goes wrong

Level Who Replies within
Tier 1 Whoever owns it Same business day
Tier 2 Priya 4 business hours
Tier 3 Maya 1 business day

Urgent means a customer-safety issue, a payment or order failure that affects more than one customer, a wholesale account at risk of leaving, or a public complaint gaining traction. Urgent gets a reply within 2 hours.

Gaps this closed

  • Mid-class-series check-ins used to be Maya by default. Now they're Dev's.
  • Chasing unpaid wholesale invoices used to be Maya. Now it's Priya.
  • Nobody was tracking the firing schedule against promised ship dates. Now it's Tessa.
  • Posting class schedule updates used to be Maya. Now it's Jo.

How it stays true

Priya reviews all three documents every 90 days. Maya hears about Tier 3 escalations and the handful of things only she decides. Everything else stops with the person closest to it.

Bonus 2

Team announcement

How do you tell your team the good news?

In this one: This is a good thing for your team, so say it like one. Don't just drop three documents in Slack. Send this first, in your own words, then talk it through together.

Download .md
Example + blank template

Team announcement: worked example (Kiln & Co.)

Worked example. Kiln & Co. is a made-up business. Write yours in your own words.

Subject: Good news: things are about to get a lot less confusing

Hi team,

Quick one, and it's a good one. I've been the answer to everything around here, and that's made your jobs harder than they needed to be. Waiting on me. Guessing what I'd say. Double-checking things you already knew how to handle. We're done with that.

I've put together three short docs so you always know what's yours:

  1. Who owns what: [link]
  2. What you can decide without asking me: [link]
  3. What to do when something goes sideways: [link]

What gets better starting Monday, March 3:

  • You can just handle things. Refunds, supplies, ads: there's a number for each one, and under that number it's yours. No check-in needed.
  • Everything has a name next to it. No more "wait, whose job is this?"
  • You'll know exactly where to go when something goes wrong. And so will I.
  • I get to go back to the work I'm actually good at. Which is better for all of us.

What stays the same: I'm still here. Wholesale pricing, new offers, hiring, and anything legal still come to me. Everything else, you've got.

Your part (it's small):

  • Skim all three by Thursday. About 10 minutes.
  • Tell me anything that looks off or missing by Friday.
  • Come to the team meeting Friday at 10. I'm bringing coffee and we'll talk it through together.

Not sure if something is yours? Ask Priya. She's got you.

Maya

Hit Copy, then paste into Notion or Google Docs. The headings and tables come with it. Fill in every [bracket].

Bonus 3

SOP template

Once everyone knows who owns what, how do you write down how it's done?

In this one: Pick one task that still lives in your head or someone else's. Write it up here. The Decisions and Escalate sections pull straight from your Decision Authority Matrix and Escalation Framework.

Download .md
Example + blank template

SOP: Damaged item refund or replacement: worked example (Kiln & Co.)

Worked example. Kiln & Co. is a made-up business and these numbers are examples. Set your own.

Owner: Client Experience Lead (Dev Okafor) · Backup: Studio Operations Manager (Priya Shah) · Last reviewed: March 3 · Next review: June 1

What this is for

Getting a customer taken care of quickly when their order arrives damaged.

When to use it

A customer emails, messages, or replies to an order saying an item arrived broken or chipped.

Who can do it

Client Experience Lead. Studio Operations Manager covers when Dev is out.

What you need before you start

  • Access to the shop's order system and the customer inbox
  • The order number and a photo of the damage

Steps

  1. Reply within the same business day. Say you're sorry and that you're sorting it out.
  2. If there's no photo, ask for one. Don't hold up the fix while you wait if the order is under $150.
  3. Find the order in the shop system and note the item and the amount paid.
  4. Offer the customer a choice: a free replacement or remake, or a refund.
  5. Replacement or remake: add a note for Tessa in the production queue with the item, glaze, and the customer's ship-by date.
  6. Refund: issue it in the shop system and tell the customer when to expect it.
  7. Log it in the damage tracker with the date, item, and what you did.

Decisions along the way

Decision You can decide Check with
Free replacement or remake Any damaged item Nobody
Refund Up to $150 per order Priya, for anything over $150
Anything beyond the above (extra credit, rush shipping on a remake) Nothing Priya

Escalate when

  • The refund is over $150 → Priya, within 4 business hours
  • The customer mentions a safety problem, like a sharp edge or a crack that cut them → Priya, within 2 hours
  • The customer posts about it publicly → Priya, within 2 hours
  • The same item or glaze has been reported damaged more than twice this month → Tessa

Done looks like

The customer has a replacement in the queue or a refund on its way, they've been told what happens next, and it's logged.

Common mistakes

  • Asking for a photo on an order under $150 and then waiting days for it.
  • Promising a remake date without checking the firing schedule with Tessa.

Hit Copy, then paste into Notion or Google Docs. The headings and tables come with it. Fill in every [bracket].

Now keep it working.

  • You set the numbers

    Spending limits, refunds, response times, approval thresholds. These need to make sense for your business. Don’t copy the example numbers just because they’re already filled in.

  • Write it for anyone

    If a process only works because one particular person knows how to handle it, you haven’t really solved the problem. You’ve just moved the dependency to someone else. Build something another capable team member could follow too.

  • Review every 90 days

    Your business is going to change. People get hired, responsibilities shift, and new problems come up. Revisit these documents every quarter, or whenever something stops working the way it should.

Set your 90-day check-in

A repeating reminder every three months, with the review checklist already inside. Takes ten seconds.

Want me to take a look?

Your business on paper and your business in practice aren’t always the same thing.

You just mapped out how things are supposed to work. But what actually happens when a client needs something, a deadline gets missed, or your team has to make a decision without you? That’s what I investigate inside a Dependency Audit.

I get behind the scenes of your business and look at how work actually moves through your team. Where things get stuck, what keeps coming back to you, and what’s causing the problems in the first place. You’ll walk away with a full diagnostic report, a prioritized roadmap for what to fix first, and a strategic debrief call with me to talk through it all.

You don’t need to know what’s broken before we start. That’s my job.

Explore the Dependency Audit