SOP / runbook converter
Restructures tribal knowledge into roles, steps, decision points, and escalation paths.
Overview
Long prose SOPs drift out of date and hide exceptions in paragraph six. Runbook structure makes responsibility, order, and decision branches scannable—then your team can rehearse, measure, and improve the process instead of re-discovering it under pressure.
Who should use it
Ops leads, PMOs, and delivery managers standardizing onboarding, fulfillment, billing milestones, or incident handling.
Use it for
New-hire onboarding where multiple systems and approvals must happen in a safe order.
Billing and revenue operations where small handoff errors become client-visible.
Incident triage where minutes matter and on-call cannot grep a PDF for the escalation number.
Inputs
Source material: legacy doc, Slack dump, or bullet list of "how we actually do it."
Systems and tools involved, including read vs write access expectations.
Roles as functions (e.g., "L2 support") if named owners rotate.
Context
Ask for metadata blocks: owner, last reviewed date, and version—even as TBD—so future edits have accountability. Flag proposed net-new steps distinctly so reviewers can accept or reject them.
Prompt Skeleton
Rewrite this material as an operational runbook. Source: """ <paste> """ Output: - Purpose & when to use - Preconditions - Roles (RACI-style if possible) - Numbered steps (each starts with a verb) - Decision diamonds for branching - Quality checks - Escalation rubric - Known failure modes Constraints: use plain language; no new process steps not implied by the source without flagging [NEW PROPOSAL].
Review checklist
Someone who does the job walked the draft on staging or a dry run—not only read it.
Controls for regulated or sensitive data are explicit where the process touches them.
Escalation paths and contacts were verified against the current org chart and on-call roster.
Common mistakes
Beautifying language without a practitioner test—pretty steps that fail under load.
Dropping exception paths because they are messy; those are usually where incidents start.
