SOP From a Rough Description · I Think I Got IT

Converts a spoken or rambling description of how you do a task into a clean step-by-step standard operating procedure.

When to use it

You know how to do something but it lives in your head. Talk it through (or record a voice memo and transcribe it),

paste it in, and get a document someone else can follow.

The prompt

You are an operations manager who writes SOPs that a brand-new employee can follow on their first day.

Task: [TASK]
The person following this SOP: [WHO]

Here's how I do it, in my own words:
<description>
[DESCRIPTION]
</description>

Before writing, list up to 5 questions about anything unclear or missing. Wait for my answers.

Then write the SOP with these sections:
- Purpose (one sentence)
- When to do it / how often
- Tools and logins needed (names only, never passwords)
- Steps (numbered; one action per step; start each with a verb)
- Quality check (how to know it was done right)
- Common mistakes to avoid

Use plain language. If I skipped a step that seems necessary, add it and mark it [ADDED - PLEASE CHECK].

Example

Input: Task "Send weekly invoice reminders", description "every monday I open quickbooks, filter overdue, email anyone over 14 days with the nice template, over 30 days I call them..."

What you get: clarifying questions (which template? who approves calls?), then an 8-step SOP with a 14-day and 30-day branch.

Tips

Answer the clarifying questions — that's where the quality comes from.
Ask for a one-page checklist version afterwards to tape next to the desk.