Foundation

How to Build a Prompt That Writes SOPs From Your Verbal Description

A prompt that writes SOPs from your verbal description converts unstructured process explanations into formatted standard operating procedures with numbered steps, responsible parties, time estimates, and checklists. On aidowith.me, the Practical Prompts route walks you through building one in 15 steps over about 75 minutes. You'll create a prompt that accepts a brain dump (typed or pasted from a voice transcript) and outputs a clean SOP in your company's format. The prompt adds structure the speaker didn't: it infers step boundaries, flags missing ownership assignments, and inserts time estimates based on similar tasks. Testing on 3 real processes from your team shows output quality. Most users report creating SOPs in 10 minutes that used to take 2 hours of writing and formatting. The route also covers how to add a review checklist so the SOP gets approved on the first pass. One prompt handles processes from 5 to 25 steps without adjustment.

15 steps ~1h 15min For all professionals Free
Start This Skill →

The Problem and the Fix

Without a skill

  • You have 20+ undocumented processes because writing SOPs takes 2 hours each
  • Subject matter experts can explain processes verbally but won't sit down to write them up
  • Existing SOPs use inconsistent formats, making them hard to follow and maintain

With aidowith.me

  • One prompt converts a verbal brain dump into a formatted SOP in 10 minutes
  • Auto-generates step boundaries, owner fields, and time estimates from unstructured input
  • A consistent output format that works for processes from 5 to 25 steps

Who Builds This With AI

Marketers

Content, campaigns, and briefs done in hours instead of days.

Sales & BizDev

Prep calls, draft outreach, research prospects in minutes.

Managers & Leads

Reports, presentations, and team comms handled faster.

How It Works

1

Record or type a process walkthrough

Pick a real process and describe it as if you're explaining it to a new team member. Don't worry about format or structure.

2

Build the SOP-generation prompt

Create a prompt that takes unstructured text and outputs numbered steps, owners, time estimates, and a completion checklist.

3

Test on 3 real processes

Run the prompt on 3 different processes from your team. Compare to existing SOPs (if any). Adjust for missing steps, then finalize.

Build Your SOP Prompt in 75 Minutes

Follow the route and turn verbal process descriptions into formatted SOPs with one prompt.

Start This Skill →

What You Walk Away With

Record or type a process walkthrough

Build the SOP-generation prompt

Test on 3 real processes

A consistent output format that works for processes from 5 to 25 steps

"I recorded a 5-minute voice memo explaining our client onboarding process. The prompt gave me a 15-step SOP that our ops team approved with zero changes."
- Agency Owner, creative services
See full skill: Practical Prompts

Questions

Yes. The prompt handles processes from 5 to 25 steps. For longer processes, you break the verbal description into sections (setup, execution, review) and run each through the prompt. The route shows you how to stitch sections together into one SOP document. The route provides clear guidance at every step so you can move from setup to results without guesswork.

The prompt flags likely gaps by comparing your description to common process patterns. It inserts placeholder steps marked "confirm with owner" where it detects something missing. You review these flags during the approval step. The route includes a gap-detection test on 3 real processes. The route provides clear guidance at every step so you can move from setup to results without guesswork.

You configure the output format during the route. Paste an example of your current SOP template and the prompt mirrors that structure: headings, numbering style, ownership fields, and checklist format. If you don't have a template, the route provides a default that works for most teams. The route provides clear guidance at every step so you can move from setup to results without guesswork.