01
Capture the real task
Document the trigger, current actions, finish line, tools, ownership, and recent exceptions based on how the work is actually performed.
Made for Entrepreneurs
Turn a Repeated Task Into a Clear SOP
Also useful for: people in Entrepreneurs
35 min
Intermediate
Business & Entrepreneurship
Get Organized
Document a recurring business task so it can be repeated, checked, and delegated without constant clarification.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Reduce guesswork, missed steps, and founder dependence by capturing how recurring work actually gets done, including the judgment calls that basic checklists miss.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Expose hidden judgment
Separate routine actions from decisions, exceptions, approvals, and failure points that could block reliable delegation.
03
Produce and pressure-test the SOP
Run the compiled prompt, then test the draft against a normal case and a difficult case before rollout.
Make Your Play
Turn a Repeated Task Into a Clear SOP
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Describe the recurring task, why it matters, how often it happens, and who receives the result.
0/10000
List the actions currently taken in the order they usually happen, including shortcuts, repeated work, and informal checks.
0/10000
State what starts the task and what evidence proves it is finished.
0/10000
Describe judgment calls, common variations, likely mistakes, and situations that should stop or escalate the work.
0/10000
List the primary owner, possible backup, tools, access needs, deadlines, and quality standards.
0/10000
Select the level that best reflects the harm caused by a missed or incorrect step.
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Capture the real task
Document the trigger, current actions, finish line, tools, ownership, and recent exceptions based on how the work is actually performed.
02
Expose hidden judgment
Separate routine actions from decisions, exceptions, approvals, and failure points that could block reliable delegation.
03
Produce and pressure-test the SOP
Run the compiled prompt, then test the draft against a normal case and a difficult case before rollout.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Choose a task completed often enough to remember clearly. Describe what actually happens now, including shortcuts and workarounds. Avoid writing the ideal process unless it is already followed.
Advanced instructions
Include task volume, approval limits, system permissions, service standards, and exception rates when known. After drafting, test the SOP against a normal case and a difficult case before delegation.
Use this when
A recurring task lives mostly in your head, produces inconsistent results, or takes too much explanation each time it is assigned.
You'll need
- Task and purpose
- Current process
- Trigger and finish line
- Decisions and exceptions
- Ownership, tools, and quality
- Consequence level
You'll get
- A specific trigger and completion definition
- Every required action placed in working order
- Ownership assigned for execution and escalation
- Common decisions expressed as if/then rules
- Quality checks tied to observable evidence
- Unknown details clearly marked for confirmation
By the end of this playbook
You will have:
- A specific trigger and completion definition
- Every required action placed in working order
- Ownership assigned for execution and escalation
- Common decisions expressed as if/then rules
- Quality checks tied to observable evidence
- Unknown details clearly marked for confirmation
Examples
Progress 1 of 3