Skip to content

Convert Rough Screen-Share Notes or Bullet Steps Into a Repeatable Team SOP

Transform messy Loom transcripts or tribal 'how I do it' notes into scannable Standard Operating Procedures with prerequisites, edge cases, and QA checks.

Copy the prompt and paste it into the AI assistant you already use.

Why nobody follows 10-page SOPs—and how to write ones that work

  1. 01

    List Permissions, Logins, and Input Files at the very top

    Nothing frustrates a new executor more than reaching Step 7 of 9 only to discover they lack Stripe Billing Admin role or the Finance mapping sheet—front-load prerequisites.

  2. 02

    Start every numbered step with an imperative verb + exact UI location

    Write 'Click Billing > Invoices > Export CSV (set filter: Status = Paid, UTC)' rather than vague prose like 'Next you'll want to grab last month's paid export.'

  3. 03

    Add 'Expected Result / Sanity Check' right after risky steps

    Tell the operator what normal looks like ('Row count should be ~400–550; if <50, verify UTC date filter didn't reset to Today') to catch mistakes before emailing outputs.

  4. 04

    Validate by having a beginner execute it silently without coaching

    An SOP isn't finished when the expert writes it; watch a teammate run it cold and patch every ambiguous step where they paused to ask a question.

How it works in practice

Raw Loom transcript excerpt

So every Tuesday I go into Zendesk, grab enterprise SLA breaches—wait, make sure you exclude sandbox test orgs or numbers look crazy, tag is 'internal_test'—then export CSV, match org_id in the Master ARR sheet tab 2, and if ARR is over $50k I ping #cs-vip-alerts with the ticket link.

Clean Repeatable Team SOP

SOP: Weekly Enterprise SLA Breach Alert (Every Tue by 10:00 AM ET | Est: 12 min) • PREREQUISITES: Zendesk Explore Viewer access + Master ARR Sheet (Viewer). • STEPS: 1. Open Zendesk > Views > 'SLA Breached (Last 7d)'. 2. Filter OUT tag `internal_test` (Sanity check: removes ~15–30 QA tickets). 3. Export CSV -> Match `org_id` against Master ARR Sheet > Tab `02_Active_Orgs`. 4. For every row with `ARR >= $50,000`, post Ticket URL + Account Owner + Breach Hours in `#cs-vip-alerts`. • DONE CHECK: Post '0 Enterprise SLA breaches >$50k this week' in `#cs-vip-alerts` even if list is empty so leadership knows audit ran.

Moving the 'exclude internal_test' afterthought directly into Step 2 and adding a zero-breach confirmation turns tribal memory into reliable infrastructure.

Common questions

Should we replace written SOPs entirely with Loom videos?

Pair both: a 4-minute video builds great first-time context, while a written 8-step checklist lets someone execute the task six months later in 90 seconds without scrubbing through video.

How do we stop UI screenshots inside SOPs from going stale every month?

Avoid screenshotting every trivial 'Save' button; write crisp menu breadcrumbs (`Settings > Security > API Keys`) and reserve annotated screenshots strictly for complex multi-field screens.

How do we know when an SOP has gone stale before an error happens?

Include an `Owner` and `Next Review Date (+6 months)` header on every critical SOP, and empower anyone running the checklist to edit minor UI label shifts immediately.

Learn more

Related guides and background articles for this task