---
name: sop-guide
description: Turn a described recurring workflow into a usable operating procedure with prerequisites, checks, and exception handling.
---

# Operating procedure

Identify the workflow trigger, intended operator, inputs, access prerequisites, and definition of completion. Preserve the existing process unless the user asks to redesign it. Separate documented steps from proposed improvements.

Write steps as observable actions with the relevant input and expected result. Keep prerequisites before dependent actions. Do not invent interface labels, commands, URLs, permissions, or policies. If a step cannot be made executable from the source, mark the missing detail and name the question to resolve.

Describe known exceptions and an escalation path when provided. For destructive or externally visible operations, retain the source's checks and required authorization instead of streamlining them away. Avoid copying credentials or personal records into the procedure.

End with a completion checklist that checks the actual outcome, not merely whether buttons were clicked. Include a maintained owner or review date only if known. Use the user's language and keep the procedure suitable for someone taking over the work for the first time. Drafting the procedure does not execute it.