Use cases Standard operating procedures

Write the procedure by doing the work once.

No blank page, no format argument. Record the task the correct way and Stepwright drafts a numbered, screenshotted procedure — the same structure every time, whoever recorded it.

Record your first procedure See how it works

Free plan, no credit card. Windows and browser.

In short

Stepwright creates standard operating procedures by recording a task once and producing a numbered SOP — a screenshot and a written instruction for every step, drawn from your screen and your spoken narration. Every procedure comes out in the same structure, can carry your branding, and is updated in minutes when the process changes.

Everyone agrees the team needs SOPs, and writing them from a blank page is the task that never reaches the top of the list.

The ones you have are inconsistent — different formats, different detail — depending on who wrote them and how much time they had.

A procedure written once and never touched is wrong within months, so people quietly stop following it.

Screenshots are pasted in by hand, so the moment an interface changes the document no longer matches the screen.

One run in, one procedure out.

The recording is the input and the draft is the output. What is left for you is the judgement: where the procedure starts and stops, and whether someone who has never done the task can follow it.

01 / 04

Do the task the correct way, once

On a real case rather than a rehearsed example, so the branches get captured too — the approval that is sometimes needed, the field only filled in for EU customers. Narrate the decisions as you reach them.

02 / 04

The draft arrives in one format, always

A numbered procedure: screenshot per step with the click target highlighted, instruction text drawn from your narration. The night shift's SOP and the supervisor's SOP come out looking like they were written by the same person, because the format is not a choice anyone makes.

03 / 04

Put your own name on it and send it out

Apply your branding, then publish a link or export to PDF, HTML or Markdown for the SOP library, the wiki or a training platform. Redact anything sensitive on paid tiers before it leaves.

04 / 04

Keep it matching what is on screen

A tool changes, a step moves: record that part and the procedure updates in minutes. This is the whole difference between a living SOP and a document people learn to ignore.

How to

How to create an SOP by recording your screen.

You do not need a tool to do this. The manual version works, and it is worth understanding before you automate any of it — the slow parts are not the ones most people expect.

  1. Decide where the procedure starts and stops

    Most unusable SOPs fail here rather than in the writing. Pick the trigger that starts the work and the state that means it is finished — 'from the refund request landing in the queue to the customer receiving confirmation'. Anything outside that belongs in a different document.

  2. Run it once, on real work

    Do the task at normal speed on a genuine case, not a rehearsed example. Rehearsed runs skip the branches — the approval that is sometimes needed, the field only filled in for EU customers — and the branches are where readers get stuck.

  3. Record your screen and narrate as you go

    Say what you are doing and, more importantly, why. 'I'm checking the order date because refunds over 30 days need a manager' is the sentence that makes an SOP useful. Any screen recorder does this part.

    With Stepwright: The recording is the input. There is no separate writing stage afterwards.

  4. Turn the recording into numbered steps with screenshots

    Scrub through, capture a screenshot at each meaningful click, crop each one to the region that matters, and write one instruction per screenshot. This is the slow part: expect roughly an hour of editing per ten minutes of recording.

    With Stepwright: Steps, screenshots and crops are generated from the recording, and your narration becomes the instruction text.

  5. Redact anything that should not be shared

    Real work means real data on screen: customer names, invoice totals, internal account IDs. Blur them before the SOP leaves your machine. Doing it by hand is the step people quietly skip, which is how customer data ends up in a wiki.

    With Stepwright: Sensitive regions can be blurred on the generated screenshots before the guide is shared, and recordings are processed and stored in the EU (AWS Frankfurt).

  6. Have someone who has never done the task follow it

    The author is the worst possible reviewer — they fill gaps from memory without noticing. Watch someone else attempt the procedure using only the document, and fix every point where they hesitate.

  7. Put it where the work happens, and set a review date

    An SOP filed in a folder nobody opens is the same as no SOP. Link it from the tool the task is performed in, and diarise a review — most procedures drift within two quarters, and a confidently wrong document is worse than a missing one.

Steps 1, 2, 6 and 7 are judgement calls no tool should make for you. Steps 3 to 5 are mechanical, and they are where the hours go — which is the part Stepwright removes.

What a procedure library gains.

They actually get created

Recording a task you already know how to do beats writing it from scratch, so the procedures finally get documented instead of staying on the someday list.

One format, every author

Every SOP follows the same numbered, screenshotted structure regardless of who recorded it, so the library stops being a patchwork.

Screenshots that match reality

The images come from the real run, so the SOP shows what the user sees — and updating keeps it that way after an interface change.

The reasoning is preserved

Narration in your own voice captures why a step matters, so the procedure teaches the judgement and not only the clicks.

Your branding, your library

Custom branding and export to PDF, HTML or Markdown mean finished SOPs slot straight into the library or training platform you already use.

Private and redactable

Guides are private by default and encrypted in transit and at rest, with redaction on paid tiers for any sensitive data caught on screen.

Questions about SOPs.

Related

Record yourself doing the task once. Stepwright captures a screenshot and a written step for each action as you perform the procedure, then assembles the numbered SOP. No writing steps or pasting screenshots into a document by hand.

A template still leaves you to write every step and capture every screenshot manually. Stepwright generates those from a single recording, so the first draft is done. Export to PDF, HTML or Markdown and store it wherever your SOPs live.

When the process changes, record only the part that changed. The rest of the guide stays exactly as it was, including edits you made by hand. Because updating is cheap, procedures stay accurate instead of drifting away from what is on screen.

Yes. Apply custom branding so procedures look like part of your own documentation, then export or share them for your library or training platform.

Pick the procedure people keep asking about.

Record it the next time you do it, and the SOP exists by lunchtime. The free plan needs no card.

Record your first procedure See pricing