Intermediate 40 minsBusiness AutomationsReviewed AI-assisted guide

Turn an informal business process into a repeatable SOP

Document a recurring business task with owners, controls, exceptions and handoffs.

Written and reviewed by the AI4E editorial team · last reviewed September 20, 2026. Editorial status: Reviewed see our testing method.

Best for

  • Founder-led or undocumented recurring processes

What you need

  • Process notes and owner interview
  • Systems, roles, inputs and expected outputs

Limitations

Not a substitute for legal, safety or compliance review.

C

Recommended tool

Claude

Free tierTry Claude

Claude handles detailed process material and can expose missing controls.

AI4E may earn a commission from partner links. This never affects which tool we recommend. Read the affiliate disclosure →

Pick your stack

Do it for nothing, or move faster with a paid tool.

C

Claude

$0 · Completely free

Claude covers this task on its free plan.

Try Free

AI4E may earn a commission from partner links. This never affects which tool we recommend. Read the affiliate disclosure →

Your copy-paste prompt

Fill in the blanks on the left and the prompt updates as you type.

Fill in your details

0 of 3 fields filled — every matching placeholder updates as you type.

Act as an operations analyst. Convert [PROCESS NOTES] into a repeatable SOP for [BUSINESS/ROLE]. Include purpose, trigger, inputs, roles, numbered actions, handoffs, decision rules, exceptions, quality controls, records, escalation and review owner. Use only supplied facts. Mark absent operational details [CONFIRM]; never invent permissions, systems, policies or compliance steps. Separate current process from suggested improvement. Ask questions where an omission could cause loss, delay or harm.

Step-by-step instructions

  1. 1

    Interview the person who currently performs the task.

  2. 2

    Generate the SOP and resolve every [CONFIRM] item.

  3. 3

    Have another person run the process from the document.

  4. 4

    Record failures, revise and approve with an owner.

Check the result

  • Trigger and completion are measurable
  • Every handoff has an owner
  • Exceptions have a path
  • A second person completed a test run

If the result is poor

  • If it mirrors messy notes, request steps grouped by role and outcome.
  • If controls are invented, require current-state facts only.

Privacy and accuracy

  • Have qualified staff validate financial, legal, privacy and safety controls.

Sample input

Informal monthly invoicing process across email, accounting software and manager approval.

Expected output

A controlled SOP with trigger, nine steps, approval exceptions, reconciliation checks and escalation.

What people do next

Three recipes chosen for the task that usually follows this one, not just for sharing a category.