Claude Prompts for SOPs People Actually Follow
20 copy-paste Claude prompts for standard operating procedures, runbooks, RACI charts, and process documentation. Long-context Claude can ingest existing process notes + spit out structured SOPs.
In short: This page contains 16 copy-paste ready prompts, organized into 4 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
SOP Writing
4 promptsSOP from Process Description
1/16✨ What it does
Claude turns [Paste rough description of process] into a formal SOP with purpose, scope, owner, prerequisites, numbered steps, if/then points, verification, exceptions, and a version date, and flags steps too vague for a new hire. Paste the rough notes, then tighten every flagged step before you publish it.
[Paste rough description of process]. Convert to SOP. Output structure: purpose, scope, owner, prerequisites, step-by-step (numbered), decision points (if/then), verification, exceptions handling, version + last updated. Each step actionable enough that a new hire could execute. Flag steps too vague to follow.
Pro tip: SOPs fail at "varies depending on situation." Vague steps = inconsistent execution. Decision-point notation (if X then Y, else Z) = SOPs that handle reality.
Runbook for Recurring Task
2/16✨ What it does
Claude builds a runbook for [recurring task] with the trigger, prerequisites, step-by-step procedure, expected output, troubleshooting, escalation, and time estimates so someone tired or new can follow it. Name the task, then walk the first step yourself before you hand the runbook over.
Build a runbook for [recurring task]. Output: trigger (when this runs), prerequisites (access, tools, data), step-by-step procedure, expected output, troubleshooting if step fails, escalation path, time estimate per step. Designed for someone tired or new to follow without thinking.
Pro tip: Best runbooks designed for "tired ops engineer at 2am." Plain language, no assumed context, escalation visible. Smart-engineer runbooks fail when smart engineer is sick.
Onboarding SOP
3/16✨ What it does
Claude writes an onboarding SOP for new [role] covering pre-day-1 prep, day 1, week 1, 30-60-90 expectations, who does and owns each piece, a sign-off checklist, and a feedback loop so any manager could run it. Fill your role, then assign who owns day 1 before a hire starts.
SOP for onboarding new [role]. Output: pre-day-1 prep, day 1 schedule + activities, week 1 milestones, 30-60-90 day expectations, who handles what (RACI), checklist signed-off when complete, feedback loop to improve SOP itself. Specific enough that any manager could run.
Pro tip: Onboarding without SOP = inconsistent experience. Some managers thorough; others wing it. New hire experience depends on luck. SOP = repeatable + improvable.
Customer Onboarding SOP
4/16✨ What it does
Claude builds a post-sale customer onboarding SOP for stage [SaaS / agency / product] with kickoff agenda, data checklist, account setup, first-value milestone, success criteria, CSM handoff, owners per step, and time-to-value under [target]. Pick your stage and target, then time the kickoff against that goal.
SOP for customer onboarding (post-sale). Stage: [SaaS / agency / product]. Output: kickoff call agenda, data collection checklist, account setup sequence, first-value milestone, success criteria, handoff to CSM. RACI per step. Goal: time-to-value < [target].
Pro tip: Customer onboarding SOP gaps = churn. Random onboarding = some customers ramp, some flounder. Standardized = consistent experience + improvable through observation.
XML tags are just the start. Learn the full Claude workflow.
A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.
RACI + Process Design
4 promptsRACI Chart from Process
5/16✨ What it does
Claude builds a responsibility chart from [Paste process or SOP] with who does the work, one owner of the outcome, who is asked, and who is told, and flags any step that has two owners. Paste your process, then pick one owner for every flagged row.
[Paste process or SOP]. Build RACI chart: Responsible (does the work), Accountable (one person, owns outcome), Consulted (input expected), Informed (kept in loop). Output as table: rows = process steps, columns = roles. Flag any step with multiple Accountables (anti-pattern).
Pro tip: Multiple Accountables = no Accountable. RACI clean = one A per step. Common mistake: making everyone "accountable" = nobody owns. Force the choice.
Process Bottleneck Audit
6/16✨ What it does
Claude audits [Paste process] for bottlenecks: the slowest step, waits at handoffs, work you could run in parallel, automation candidates, and redundant steps, ranked by time saved. Drop the process in, then cut or automate the top-ranked wait first.
[Paste process]. Audit for bottlenecks. Output: which step takes most time (% of total), where work waits (handoffs, approvals), parallelizable steps currently sequential, automation candidates, redundant steps that could be cut. Time savings ranked by impact.
Pro tip: Most processes 80% wait, 20% work. Wait time = handoffs + approvals + queue. Automating the work = small win. Cutting wait = big win. Audit handoffs first.
Process Design from Outcome
7/16✨ What it does
Claude designs a process backward from outcome [describe] under constraints [team, tools, time], with metrics, working-backward steps, owners, dependencies, pass/fail criteria, and what you measure to improve. Fill both blanks, then assign the first owner before you add more steps.
Design a process backwards from desired outcome: [describe]. Constraints: [team, tools, time]. Output: outcome metrics, working-backward steps, owner per step, dependencies, success/fail criteria, what we measure to improve. Outcome-led design > activity-led.
Pro tip: Activity-based processes ("schedule daily standup") = busy. Outcome-based ("communicate blockers within 24h") = effective. Output-design > input-design.
Approval Workflow
8/16✨ What it does
Claude designs an approval workflow for [decision type] given [risk level, $ amount, time-sensitivity], covering who approves at each threshold, who can be skipped, escalation if someone is out, the audit trail, and automation hooks. Set your dollar and risk lines, then name the backup approver.
Design an approval workflow for [decision type]. Constraints: [risk level, $ amount, time-sensitivity]. Output: who approves at what threshold, who can be bypassed, escalation path if approver unavailable, audit trail captured, automation hooks. Speed + control balanced.
Pro tip: Approval workflow trapped between control + speed. Too tight = stalls. Too loose = mistakes. Threshold-based (anyone < $X, manager < $Y, exec ≥ $Z) = both.
SOP Audits + Improvement
4 promptsSOP Compliance Audit
9/16✨ What it does
Claude audits the gap in [Paste SOP + describe how team actually works], listing skipped steps, unofficial extras, obsolete steps, and unrealistic ones, then whether to update the SOP or change the work. Put both of your versions in, then choose update or enforce before the next cycle.
[Paste SOP + describe how team actually works]. Audit gap between SOP and reality: which steps team skips (and why), which steps team adds (often valuable, undocumented), which steps are obsolete, where SOP is unrealistic. Update SOP to match reality OR change reality to match SOP.
Pro tip: Best SOPs reflect reality. SOP team ignores = useless paper. Either fix the SOP (most common) or fix the team behavior (sometimes correct). Audit is the tool.
SOP Simplification
10/16✨ What it does
Claude simplifies [Paste current SOP] by cutting steps that do not change the outcome, merging same-owner steps, turning prose into checkboxes, dropping jargon, and aiming for one page. Paste the bloated SOP, then keep only the shortened version your team will actually follow.
[Paste current SOP]. Simplify: cut steps that don't change outcome, merge consecutive steps with same owner, replace prose with checkboxes, remove jargon for fresh-eyes reader, single-page if possible. Goal: same compliance, half the friction.
Pro tip: SOPs grow over time as edge cases get added. After 2 years = 3-page bloat. Quarterly simplification = tight + followed. Bloat = unread.
SOP Translation for Different Levels
11/16✨ What it does
Claude adapts [Paste expert-level SOP] for [junior level / new hire / contractor] with more context, jargon definitions, spelled-out assumptions, common mistakes, screenshot placeholders, and a lower escalation bar. Choose the audience, then add the screenshots before you share it.
[Paste expert-level SOP]. Adapt for [junior level / new hire / contractor]. More context per step, definitions of jargon, assumed knowledge spelled out, common mistakes flagged, screenshots placeholder, escalation lower-threshold.
Pro tip: Same SOP doesn't serve senior + junior equally. Junior SOP needs more handholding; senior SOP feels patronizing. Versions per audience = high quality across team.
SOP Visualization
12/16✨ What it does
Claude converts [Paste SOP] into a mermaid flow you can paste, a one-page checklist, a decision tree if it branches, and a quick reference card for different ways people use it. Paste the SOP, then pin the one format where people actually look.
[Paste SOP]. Convert text-heavy SOP to visual. Output: process flow diagram description (mermaid syntax I can paste), checklist version (one-page sticky), decision tree if branching, quick reference card. Different formats for different consumption contexts.
Pro tip: Text SOPs get read once. Visual SOPs (flowchart, checklist on wall) = consulted daily. Form factor matters more than content for compliance.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.
Specialty SOPs
4 promptsCrisis Response SOP
13/16✨ What it does
Claude writes a crisis SOP for [security incident / outage / PR / data breach] with severity levels, the first 15 minutes, escalation, internal and external templates, decision rights, a post-mortem trigger, and any regulatory notices. Pick your crisis type, then print the 15-minute steps where on-call can find them.
Crisis response SOP. Crisis type: [security incident / outage / PR / data breach]. Output: severity classification, initial response in 0-15 min, escalation chain, communication templates internal + external, decision rights during crisis, post-mortem trigger, regulatory notifications if any. Designed for panic-state.
Pro tip: Crisis SOPs designed for calm read but panic execution. Templates pre-written = blast email out in 5 min, not 50. Decision rights pre-decided = no debate during fire.
Knowledge Transfer SOP
14/16✨ What it does
Claude writes a knowledge-transfer SOP for when [employee leaves / role changes], covering walkthroughs, access, customer handoffs, in-progress work, and a post-transition support window so the handoff is not late and rushed. Start your walkthrough before the last week, not on the goodbye day.
SOP for knowledge transfer when [employee leaves / role changes]. Output: documentation transfer (1-on-1 walkthrough format), system access, customer relationship handoffs, in-progress work transition, post-transition support window. Common mistake: transfer too late + too rushed.
Pro tip: Most knowledge transfer = 2 weeks before exit, panic mode. SOP-driven KT = 6 weeks of structured handoff. Departures less catastrophic when SOP exists.
Vendor Onboarding SOP
15/16✨ What it does
Claude writes a vendor onboarding SOP for vendor type [describe] with due diligence, contract review, least-privilege access, kickoff, review cadence, and an offboarding plan. Describe the vendor type, then finish due diligence before you grant any access.
SOP for onboarding new vendor. Vendor type: [describe]. Output: due diligence (security, financial, compliance), contract review, system access provisioning (least privilege), kickoff meeting, ongoing review cadence, offboarding plan. Vendor risk = real risk.
Pro tip: Vendor onboarding = security + procurement + legal + ops touchpoints. Without SOP = something gets missed (often security review, sometimes contract terms). SOP catches before it bites.
SOP Library Architecture
16/16✨ What it does
Claude architects an SOP library for [company size] with org, team, and role hierarchy, naming, version control, owners and review cadence, search, and a retire process so the set stays usable as it grows. Set your company size, then name one owner per top-level folder.
Help me architect an SOP library for [company size]. Output: hierarchy (org-wide / team / role-specific), naming convention, version control, ownership + review cadence, how to find SOPs (search/index), retire-old-SOP process. Library that scales beats SOP collection that grows.
Pro tip: Random SOPs in random folders = nobody finds them = nobody uses them. Architectured library + naming convention + search = SOPs become institutional asset.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides