What goes into a good SOP?

A clear purpose and scope, the responsible roles, required materials, numbered sequential steps, decision points for branches, and quality checkpoints to confirm each stage was done correctly.

Why specify the detail level?

A senior operator needs less hand-holding than a brand-new hire. Setting detail level tells the model whether to write terse steps or fully explicit ones with rationale.

Should I list who is responsible?

Yes. Naming roles (not people) for each step or section turns a vague process into an accountable one and is essential for audits and handoffs.

What format should I choose?

Numbered lists suit linear procedures, checklists suit repeatable verification tasks, and tables (step / role / output) suit hand-offs across teams. Pick what your team already reads.

Does it produce a final SOP?

It produces a strong prompt; your LLM produces the SOP draft. Always have the responsible role review the draft against the real process before publishing it.

SOP Writing Prompt Builder

SOP writing prompt builder

A Standard Operating Procedure is only useful if anyone can follow it and get the same result. That means numbered steps, clear ownership, the materials needed, the decision points where the process branches, and checkpoints that confirm each stage was done right. This builder converts your process description and responsibility list into an LLM prompt that produces a consistent, audit-ready SOP — not a wall of prose. You bring the prompt to your own model and review the draft.

How it works

You describe the process from trigger to completion, list the responsible roles, set how often it runs, choose a detail level, and pick an output format. The tool assembles a prompt that gives the model a clear SOP structure: purpose and scope, roles, materials, sequential numbered steps, explicit decision points (“if X, then…”), and quality checkpoints. It also instructs the model to flag any missing information rather than invent steps. Everything runs locally until you paste the prompt into your LLM.

Tips and examples

Describe the trigger and the done state. “Starts when a return arrives; ends when the refund is confirmed” bounds the procedure cleanly.
Name roles, not names. “Shift lead” survives staff turnover; “Maria” does not.
Call out the branches. If the process forks (damaged vs. undamaged item), say so — the prompt will turn each fork into a decision point.
Match detail to the reader. New-hire SOPs need explicit, self-contained steps; expert SOPs can be terse. Set the level accordingly.