If you have ever handed a process to a contractor and then spent the next month answering the same questions about it, the problem is rarely the steps. It is that a standard SOP template documents what to do and forgets to document who decides. A useful sop template covers two things: the steps of the work, and the decisions inside that work — who may make them, how far they can go, and when they must stop and escalate.
This walkthrough uses social media posting as the worked example, because it is one of the most common things founders hand off and one of the most common places decision rights quietly go missing. You can follow the same structure for any contractor-run process.
Key takeaways
- A sop template that only lists steps leaves every judgment call inside the process sitting with you, which is why the contractor keeps asking.
- The decision section is written as four fields: decision, who may decide, limit, and escalate when.
- Writing the decisions first makes the steps easier to write, because the exceptions are already handled.
- A contractor with documented decision rights can act on the ordinary cases and only brings you the ones you actually wanted to see.
Why the steps alone don't work
Picture the handoff. You write down how to draft a post, how to schedule it, which platforms matter, what the brand voice sounds like. You send it over. It looks thorough.
Then the questions start. A post mentions a competitor — publish or not? Someone leaves a negative comment — reply or wait? A post is getting traction — can we put money behind it?
None of those are step questions. They are decision questions, and the SOP had no place to put them. So each one travelled back to you, and the handoff became a slow approval queue with extra steps.
The fix is not a longer SOP. It is a sop template with a dedicated section for decisions, so the questions get answered once, in writing, before they come up.
The four fields that carry the whole thing
Every decision row has the same shape:
decision | who may decide | limit | escalate when
- Decision — name it in the words the contractor would use, not in abstract policy language. "Approve a post that mentions a competitor" is a decision. "Brand safety" is not.
- Who may decide — a named person or role. Be specific. "The team" decides nothing.
- Limit — the boundary inside which the decision is theirs. This is what makes delegation safe: they can act, but only up to a line you set.
- Escalate when — the specific conditions that send it to you. Not "if unsure." Actual triggers.
That last field is the one people skip, and it is the one that does the most work. "Escalate when unsure" pushes every borderline case back to you. "Escalate when the comment mentions legal action or asks for a refund" gives the contractor a clear signal and gives you a clear filter.
Worked example: social media posting
Start by listing every decision that currently waits for you. Do it from memory and be honest — the list is usually longer than expected. A typical first pass looks like this:
- Approve a post that mentions a competitor
- Respond to a negative comment
- Boost a post with ad spend
- Post something that touches on pricing
- Use a customer's words or image in a post
- Publish something time-sensitive outside agreed hours
Now fill in the four fields for each. Here is how three of them might read.
| Decision | Who may decide | Limit | Escalate when |
|---|---|---|---|
| Respond to a negative comment | Contractor | Standard apology plus an offer to take it offline, no promises about refunds or fixes | Comment mentions legal action, asks for a refund, or comes from a named partner |
| Boost a post with ad spend | Contractor | Small test budget on already-approved content only, stopping at the agreed ceiling | New budget needed, or the post makes a claim that has not been approved |
| Approve a post that mentions a competitor | Founder | No exception — comparison posts are always a founder call | Contractor believes a response is urgent |
The second row is where the real relief lives. The contractor does not need to ask before testing a post that is already approved. They just cannot exceed the ceiling or promote new claims. You have handed over the motion without handing over the wallet.
The first row shows how escalation triggers protect you. The contractor replies to the ordinary grumbles without a check-in, and the moment a comment mentions a lawyer or a refund, it lands with you.
The third row shows it is fine — often correct — for some decisions to stay entirely with you. The point of the exercise is not to delegate everything. It is to know which is which.
Then write the steps
With the decisions settled, the step list gets much shorter and much plainer. Write it as a checklist the contractor can actually follow:
- Check the content calendar for the week and confirm what is already approved
- Draft posts in the brand voice, one idea per post
- Check every draft against the decision table before scheduling
- Schedule approved posts in the agreed slots
- Review comments each working day and respond within the decision limits
- Send a short weekly note listing anything escalated and why
Notice what is not in there: long explanations of judgment. The judgment lives in the decision table, where it belongs, and the steps are just the sequence.
The weekly note matters more than it looks. It gives you visibility without giving you a queue, and it shows you over time which rows in the table need tightening or loosening.
The mistake almost everyone makes
Writing the steps first.
When you draft the checklist first, the decision section becomes an afterthought, and afterthoughts default to "ask the founder." That single default recreates the bottleneck you were trying to remove.
Draft the decision table first. Ask yourself: for this process, what will they face that only I would normally answer? List those, assign the fields, and only then write the steps around them. The steps become obvious once the decisions are named.
A second, smaller mistake: writing limits in vague terms. "Reasonable spend" is not a limit. "Up to the ceiling we agreed for test boosts" is. If the contractor has to guess where the line is, they will guess conservatively and ask — which is the behaviour you were trying to fix.
Doing it in one sitting
You do not need a long project for this. Pick one process currently handled by a contractor. Set a timer. List the decisions that have reached you in the last month. Fill in the four fields for each. Write the steps as a checklist. Send it over with one instruction: follow the table, escalate on the triggers.
If you want a structure to fill in rather than a blank page, the free SOP template at https://tools.exiuss.com/sop-template is built for exactly this. It includes the decision section as a first-class part of the document, and the "Fill with an example" button shows how a row reads as decision, who may decide, limit, and escalate when. You fill in your own inputs and it produces a clear, ready-to-use procedure. Most people get through a first SOP in about fifteen minutes.
The first version will not be perfect. That is fine. A decision table with three rows beats a perfect one that never gets written, because the three rows are three questions that stop arriving in your inbox.
Quick checklist
- Pick one contractor-run process that currently generates questions for you
- List every decision inside that process that has recently waited on you
- Fill in who may decide, the limit, and the escalate-when trigger for each
- Leave the genuinely sensitive decisions with yourself, on purpose
- Write the steps as a short checklist that references the decision table
- Send it over and revise the table after the first month of real use
