A sop template only earns its keep when it answers the question your team actually asks: "Can I just approve this, or do I need to ask you?" Most templates document the happy path and stop. Then a refund request lands with a wrinkle in it, nobody on the team is sure, and the decision quietly waits in your inbox. This article shows how to write an SOP for a refund process — exceptions included — so the person handling the ticket can act without tracking you down.
Key takeaways
- The section most SOP templates leave out is the decisions that currently wait for you, written as decision | who may decide | limit | escalate when.
- A refund SOP needs three exception rows at minimum: under $50, $50–$200, and over $200 or involving a chargeback.
- Each row names a decider and a limit, so a support rep can approve a small refund immediately instead of forwarding the email.
- The free SOP template at https://tools.exiuss.com/sop-template lets you fill in the form and get a clear, ready-to-use procedure in about 15 minutes.
Why the refund process breaks when you are the only one who knows the exceptions
Refunds are a good test case because the routine case is easy and the edge cases are where everything stalls. A rep can usually handle a straightforward return. But then a customer asks for a refund on a subscription they forgot to cancel, or wants money back on a partially used package, or threatens a chargeback. The rep does not know whether that is allowed. So the ticket sits, the customer gets louder, and you get a message that says "can you look at this?"
The problem is not that your team is careless. The problem is that the SOP describes the steps and leaves the judgment calls undefined. Steps are the easy half. Decisions are the half that frees you up.
The framework: decisions as decision | who may decide | limit | escalate when
Instead of writing loose guidance like "use your judgment on small refunds," write each exception as a row with four fields:
- Decision — what is being decided, stated plainly.
- Who may decide — the role that can approve it without asking anyone.
- Limit — the boundary that role owns.
- Escalate when — the condition that pushes it to the next person.
That is the whole structure. It reads like a sentence, which is why people can follow it under pressure. If you want to see it rendered in a form before you write your own, open the template and click "Fill with an example" to see how decisions are written out.
The three exception rows for a refund SOP
Here is the filled-in section for a refund request process. Copy the shape, not necessarily the numbers — set limits that match your business.
| Decision | Who may decide | Limit | Escalate when |
|---|---|---|---|
| Refund a small order | Any support rep | Refunds under $50 | Amount is $50 or more, or the order has already been refunded once |
| Refund a mid-size order | Team lead | Refunds from $50 to $200 | Amount is over $200, or the customer disputes the original charge |
| Refund a large order or handle a chargeback | Founder | Refunds over $200 and any chargeback | Never escalated further — founder decides or brings in the payment provider |
Read the middle column out loud and you can hear why it works. A rep knows exactly what they own. A team lead knows when they are the ceiling. You know what will actually reach you.
Step 1: Write the routine part of the procedure first
Start with the normal path so the exception section has something to hang on. For a refund request, that means: verify the order, confirm the customer's identity and purchase, check the refund window, confirm the amount, process the refund in the payment tool, and reply to the customer with what happens next and when.
Keep these steps short and imperative. "Verify the order in the billing dashboard" beats "the order should be verified." You are writing instructions for someone who is mid-conversation with a customer.
Step 2: List every refund question that currently lands on you
Before you write a single row, spend ten minutes listing the messages you actually receive. Not the theoretical exceptions — the real ones. Ours looked like this: can I refund a subscription the customer forgot to cancel, can I refund a partially used order, what if they want cash back instead of credit, what if they mention a chargeback, what if this is the second refund for the same customer.
That list is the raw material. Each item on it is either a decision you can delegate or a decision you are choosing to keep. Both are fine. What is not fine is leaving it undefined so it defaults to you.
Step 3: Assign a role, a limit, and an escalation trigger to each one
Take each question and give it the four fields. The discipline is in the limit. "Any support rep can approve small refunds" is not a decision — it is a hope. "Any support rep can approve refunds under $50" is something a person can act on at their desk without a meeting.
Two things to watch for. First, the escalation trigger has to be a condition, not a feeling — "over $200" or "the word chargeback appears" rather than "if it seems risky." Second, every row needs a real destination. If the escalation goes to a role that does not exist or an inbox nobody reads, the row is decoration.
Step 4: Test it against the tickets already in your queue
Open your last batch of support tickets and run them through the SOP. For each one, ask: could the person handling this have decided it using only this document? If the answer is no, you found a missing row. This is the fastest way to find gaps, and it costs nothing but a coffee.
This step is also where you discover rows you over-engineered. If a limit never gets used because every case lands in the same bucket, simplify it.
Step 5: Publish it where the work happens
An SOP stored in a folder nobody opens is not a process. Put the refund section where the ticket lives — a saved reply, a pinned note in the support tool, a link in the ticket template. The decision table should be the part people see first, because it is the part they need mid-conversation.
The common mistake: documenting steps and calling it done
Most SOP drafts read like a recipe for the ideal case. They describe what happens when nothing unusual occurs, and they leave the judgment calls in the founder's head. The team follows the steps until the first wrinkle, then stops and asks. The document looks complete and behaves like it is not.
The fix is not a longer document. It is one extra section — the decisions table — that names who may decide, up to what limit, and when to escalate. You can read more about how that section works on the template page: https://tools.exiuss.com/sop-template.
Advanced application: use the same table for other processes
The refund example is just the first place this structure pays off. The same four fields work for discounts, shipping exceptions, account credits, and access requests. Anywhere a team member pauses before acting, there is a decision waiting to be written as a row.
For a founder, the interesting output is not the document. It is the short list of decisions you decided to keep. When the table is done, you can see exactly what still routes to you and why — and you can choose, deliberately, whether to keep it or hand it down.
Quick checklist
- Write the routine refund steps in short, imperative sentences.
- List every refund question that currently reaches you.
- Write each one as a row: decision, who may decide, limit, escalate when.
- Set the three tiers: under $50 to any rep, $50–$200 to team lead, over $200 or chargeback to founder.
- Test the SOP against real tickets already in the queue.
- Publish the decision table where the tickets are handled.
When you are ready to build your own, the free SOP template at https://tools.exiuss.com/sop-template walks you through the form, section by section. Fill in the fields and you get a clear, ready-to-use standard operating procedure — usually in about 15 minutes.
