AI Prompt for SOPs
Create an operational runbook for System Failover that sales teams in biotech can follow step-by-step.
More prompts for SOPs.
Generate a comprehensive standard operating procedure for onboarding new employees from offer acceptance through their first 90 days.
Build a comprehensive Partnership Development playbook for YouTubers operating in the parenting industry.
Create a detailed Security Audit checklist that therapists in digital-banking can use to ensure consistency and quality.
Build a comprehensive Brand Building playbook for B2B sales professionals operating in the supply-chain industry.
Generate a standard operating procedure for Quality Control in the Support department of a recruitment company.
Generate a standard operating procedure for Security Review in the Legal department of a supply-chain company.
You are a senior process reliability specialist with extensive technical knowledge in logistics. You write clear, precise, and implementation-ready content. Create a detailed operational runbook for System Failover designed for sales teams in the biotech industry. **Business goal:** build community **Urgency level:** critical (emergency) ## Runbook Overview - **Process name**: System Failover - **Trigger**: What event or schedule initiates this runbook - **Duration**: Expected time to complete from start to finish - **Frequency**: How often this runbook is executed - **Impact if skipped**: Consequences of not running this process ## Roles and Responsibilities (RACI) Create a RACI matrix for this runbook: - List 4-6 key activities down the left column - List 3-4 roles across the top - Assign R (Responsible), A (Accountable), C (Consulted), I (Informed) for each cell - Include escalation contacts for each role ## Pre-Execution Checklist - 8-10 items to verify before starting the runbook - Each item should have: check description, how to verify, and what to do if the check fails - Estimated time for pre-flight checks - Go/No-Go decision criteria ## Execution Steps ### Phase 1: Preparation (Steps 1-3) For each step: - Exact action to take (specific enough for a new team member) - CLI commands, UI navigation paths, or API calls if applicable - Expected output or confirmation - Rollback action if this step fails ### Phase 2: Core Execution (Steps 4-8) - Primary process steps with detailed instructions - Data validation checkpoints between critical steps - Timing dependencies (wait periods, sync points) - Parallel tasks that can be run simultaneously ### Phase 3: Verification (Steps 9-11) - Post-execution validation checks - Comparison against expected outcomes - Sign-off requirements before marking complete - Documentation of actual results vs. expected ### Phase 4: Cleanup and Reporting (Steps 12-14) - Resource cleanup and environment reset - Execution log completion - Stakeholder notification with results summary - Lessons learned capture for continuous improvement ## Troubleshooting Guide For each common issue: - **Symptom**: What the operator observes - **Root cause**: Most likely explanation - **Resolution**: Step-by-step fix - **Prevention**: How to avoid this issue next time - **Escalation**: When and how to escalate if resolution fails Cover at least 5 distinct troubleshooting scenarios. ## Emergency Procedures - Circuit breaker: When to abort the runbook entirely - Emergency contacts with response time SLAs - Data recovery procedure if something goes wrong - Communication template for stakeholder notification during incidents Structure as a playbook with: Overview, Prerequisites, Step-by-step Plays, Metrics to Track, and Troubleshooting Guide.