SOP Builder

Guides you through writing a single-screen standard operating procedure someone will actually use.

Takes about 6 minutes. Your answers stay in your browser, and no email address is required to see your result.

Write one single-screen procedure

If it does not fit on one screen, it is two procedures. Write it for the person who has never done it.

Process name

Plain language, as the team would say it.

Purpose

Why this exists and what breaks if it is skipped.

Trigger

What starts it: an event, a date, a request.

Owner (role)

Who is accountable for the process being followed.

Tools and access needed

Systems, templates, logins by role — never passwords.

Steps

Numbered, one action per line, in the order they happen.

Definition of done

Observable, checkable, not 'it feels finished'.

Exceptions and escalation

What to do when the normal path does not work.

Review date

A procedure with no review date becomes fiction.

Can someone else run this process without me?

9 fields still to complete.

Missing: Process name; Purpose; Trigger; Owner (role); Tools and access needed; Steps; Definition of done; Exceptions and escalation; Review date

Process name
— not yet defined —

Purpose
— not yet defined —

Trigger
— not yet defined —

Owner (role)
— not yet defined —

Tools and access needed
— not yet defined —

Steps
— not yet defined —

Definition of done
— not yet defined —

Exceptions and escalation
— not yet defined —

Review date
— not yet defined —

Assumptions and limitations

Documentation quality still depends on the person who knows the process. The tool structures it; it cannot supply the detail.
Never record passwords or credentials here. Record which role needs access instead.
Everything stays in your browser. Print or save as PDF to keep a copy.

Methodology and calculation

This tool is designed with transparency in mind. The results are calculated based on the following logic: