Operations professionals who need SOP drafts done fast. Copy these prompts into ChatGPT, fill in your specifics, and get polished procedures you can implement immediately.
These prompts pair well with Jasper AI for Operations-specific tone control, or Copy.ai for fast iteration.
New Process Documentation
You are an operations manager documenting a new procedure for the first time.
Process: {process_name} Department: {department} Frequency: {daily/weekly/monthly} Staff level: {entry_level/experienced/mixed} Key steps you’ve observed: {five_to_seven_main_steps} Common mistakes you’ve seen: {two_to_three_mistakes} Tools required: {specific_tools_or_software} Approval needed: {yes_or_no}
Write a 400-500 word SOP using numbered steps. Start with purpose and scope in 2 sentences. Include a “Before You Begin” checklist of 3-4 items. End with a troubleshooting section covering the common mistakes. Use active voice and imperative mood throughout.
When to use it: You’ve been running a process manually for months and your manager just asked for documentation by Friday.
Pro tip: List the steps exactly as you do them, including the “obvious” parts. New staff won’t know to save work before switching systems.
You are writing an SOP for handling customer escalations that reach operations.
Escalation trigger: {what_brings_it_to_ops} Response time requirement: {timeframe} Decision authority: {who_can_approve_what} Documentation system: {ticketing_or_tracking_tool} Escalation path: {manager_director_vp} Common resolution types: {three_to_four_typical_outcomes} Handoff requirements: {back_to_support_legal_sales}
Write a 350-400 word SOP structured as: Immediate Response (first 30 minutes), Investigation (gathering facts), Resolution Options (with approval levels), and Closure Requirements. Include specific email templates for customer communication at each stage.
When to use it: Support keeps escalating issues to you without clear handoff criteria, and you’re tired of explaining the same process.
Pro tip: Include exact timeframes for each step. “Investigate promptly” becomes “gather initial facts within 2 hours of assignment.”
You are documenting the monthly inventory reconciliation process that currently lives in one person’s head.
Inventory system: {software_name} Physical locations: {warehouse_sections_or_stores} Reconciliation trigger: {month_end_cycle_count_discrepancy} Tolerance levels: {acceptable_variance_percentage} Investigation steps: {current_troubleshooting_approach} Adjustment authority: {dollar_limits_by_role} Reporting requirements: {who_gets_final_report}
Write a 500-600 word SOP with four main sections: Pre-Reconciliation Setup, Variance Identification, Investigation Protocol, and Adjustment Processing. Include a decision tree for different variance scenarios and specific approval workflows.
When to use it: Your inventory specialist gave notice and you need to transfer their knowledge before they leave.
Pro tip: Document the unofficial workarounds they use. That “quick fix” for system lag is probably essential for hitting deadlines.
You are creating an SOP for onboarding new vendors into your procurement system.
Vendor type: {service_provider_supplier_contractor} Approval threshold: {dollar_amount_requiring_approval} Required documents: {insurance_tax_forms_contracts} System access: {portal_name_and_permissions} Payment terms: {net_30_45_other} Compliance checks: {background_financial_regulatory} Go-live timeline: {typical_duration}
Write a 450-500 word SOP organized by week: Week 1 (Documentation Collection), Week 2 (Verification and Approvals), Week 3 (System Setup), Week 4 (Testing and Go-Live). Include specific handoff points between departments and clear completion criteria for each phase.
When to use it: You’re setting up vendor relationships monthly but each one feels like you’re starting from scratch.
Pro tip: Build buffer time into Week 2. Vendor compliance documents always come back with issues that need fixing.
You are writing an SOP for the quarterly budget variance analysis that finance requests from operations.
Reporting period: {Q1_Q2_Q3_Q4} Variance threshold: {percentage_requiring_explanation} Data sources: {erp_system_spreadsheets_other} Cost categories: {labor_materials_overhead_other} Explanation requirements: {level_of_detail_expected} Presentation format: {slides_report_meeting} Deadline: {days_after_quarter_end}
Write a 400-450 word SOP with three phases: Data Collection (Week 1), Analysis and Documentation (Week 2), and Report Preparation (Week 3). Include specific variance calculation formulas and a template for variance explanations that satisfies finance requirements.
When to use it: Finance sends the same variance analysis request every quarter and you waste time figuring out their format requirements.
Pro tip: Save last quarter’s accepted explanations as examples. Finance prefers consistent language across reporting periods.
Emergency Response Procedures
You are documenting the procedure for handling a critical system outage during business hours.
System affected: {erp_crm_pos_manufacturing} Business impact: {operations_stopped_degraded_workaround_available} Notification list: {internal_teams_external_vendors} Escalation timeframe: {minutes_until_management_involved} Workaround options: {manual_processes_backup_systems} Communication channels: {slack_email_phone_tree} Recovery testing: {how_to_verify_system_restored}
Write a 300-350 word SOP structured as: Immediate Response (0-15 minutes), Assessment and Communication (15-30 minutes), Workaround Implementation (30+ minutes), and Recovery Verification. Include specific message templates for customer communication and internal status updates.
When to use it: Your system went down last month and everyone stood around asking “who calls who” while customers waited.
Pro tip: Test your communication tree quarterly. Phone numbers and escalation contacts go stale fast.
You are creating an SOP for handling a workplace injury in a warehouse environment.
Facility type: {warehouse_manufacturing_retail} Injury severity: {requiring_medical_attention} On-site resources: {first_aid_station_nurse_safety_officer} Documentation system: {incident_report_software} Notification requirements: {osha_insurance_corporate} Investigation timeline: {hours_days_for_completion} Return-to-work protocol: {medical_clearance_restrictions}
Write a 400-450 word SOP with immediate priorities: Secure the Scene and Provide Care (0-10 minutes), Notification and Documentation (10-60 minutes), Investigation (24-48 hours), and Follow-up (ongoing). Include specific language for incident reports that meets compliance requirements.
When to use it: You have basic safety training but need clear steps for the documentation and investigation that follows an incident.
Pro tip: Take photos of the incident scene before any cleanup. Insurance and safety investigations always need visual documentation.
You are writing an SOP for handling a product recall affecting your inventory.
Product category: {food_electronics_automotive_medical} Recall scope: {specific_lot_numbers_date_ranges} Inventory locations: {warehouse_retail_customer_sites} Notification source: {manufacturer_fda_internal_quality} Customer impact: {b2b_b2c_internal_use_only} Disposal requirements: {return_destroy_quarantine} Documentation needs: {traceability_reports_certifications}
Write a 450-500 word SOP covering: Immediate Inventory Hold (0-2 hours), Customer Notification (2-24 hours), Inventory Segregation and Tracking (24-48 hours), and Disposal Documentation (ongoing). Include templates for customer communications and inventory tracking logs.
When to use it: You received a recall notice and need to move fast on inventory isolation and customer notifications.
Pro tip: Start with inventory isolation even if the recall notice lacks details. You can always release non-affected stock later.
You are documenting the procedure for handling a critical supplier failure during production.
Supplier type: {raw_materials_components_services} Failure type: {quality_issue_delivery_failure_bankruptcy} Production impact: {hours_days_of_inventory_remaining} Alternative suppliers: {qualified_unqualified_none_identified} Quality requirements: {testing_certification_approval_needed} Cost implications: {rush_orders_premium_pricing} Customer commitments: {delivery_dates_at_risk}
Write a 400-450 word SOP structured as: Immediate Assessment (0-4 hours), Alternative Sourcing (4-24 hours), Quality Verification (24-72 hours), and Production Recovery (ongoing). Include decision criteria for choosing alternatives and customer communication protocols for delivery delays.
When to use it: A key supplier just told you they can’t deliver next week’s order and production stops without it.
Pro tip: Activate multiple backup suppliers simultaneously. First-choice alternatives often have capacity constraints during supplier crises.
You are creating an SOP for handling a data security incident that affects operational systems.
Incident type: {data_breach_ransomware_system_compromise} Systems affected: {customer_data_financial_operational} Detection method: {automated_alert_employee_report_audit} Isolation requirements: {network_segments_to_disconnect} Investigation team: {it_legal_operations_external} Notification obligations: {customers_regulators_law_enforcement} Recovery priorities: {critical_systems_first}
Write a 350-400 word SOP covering: Immediate Containment (0-1 hour), Assessment and Notification (1-4 hours), Investigation Coordination (4-24 hours), and Recovery Planning (ongoing). Include specific criteria for external notifications and communication scripts for stakeholders.
When to use it: IT detected suspicious activity and you need to coordinate the operational response while they handle technical containment.
Pro tip: Preserve system logs immediately, even if it means extended downtime. Legal and regulatory investigations require forensic evidence.
Quality Control Documentation
You are writing an SOP for the weekly quality audit of production output.
Product line: {manufactured_goods_food_pharmaceutical} Sample size: {percentage_or_units_per_batch} Testing parameters: {specifications_to_verify} Testing equipment: {tools_software_labs_required} Pass/fail criteria: {tolerance_ranges_go_no_go} Documentation system: {quality_management_software} Corrective action triggers: {failure_rates_requiring_response}
Write a 450-500 word SOP structured as: Sample Selection Protocol, Testing Procedures, Results Documentation, and Corrective Action Initiation. Include specific statistical methods for sample selection and escalation criteria for different failure patterns.
When to use it: Quality complaints are increasing and you need consistent testing procedures across all production shifts.
Pro tip: Randomize sample selection timing within each shift. Operators adjust quality when they know testing happens at 2 PM daily.
You are creating an SOP for handling customer quality complaints that require investigation.
Complaint type: {product_defect_service_failure_safety_issue} Product category: {specific_product_line} Complaint source: {direct_customer_distributor_regulatory} Investigation timeline: {response_time_requirements} Evidence collection: {samples_photos_documentation_needed} Root cause analysis: {method_5_why_fishbone_statistical} Response requirements: {customer_communication_corrective_action}
Write a 400-450 word SOP covering: Initial Response and Evidence Collection (0-24 hours), Investigation and Analysis (24-72 hours), Corrective Action Planning (72-96 hours), and Customer Communication (ongoing). Include templates for customer updates and internal investigation reports.
When to use it: Customer complaints are handled inconsistently across your team, and some investigations drag on for weeks.
Pro tip: Assign investigation ownership in the first 4 hours, even if details are incomplete. Unowned complaints become forgotten complaints.
You are documenting the monthly calibration procedure for critical measurement equipment.
Equipment type: {scales_sensors_gauges_meters} Calibration frequency: {monthly_quarterly_after_use} Reference standards: {certified_weights_known_values} Tolerance limits: {acceptable_deviation_ranges} Documentation requirements: {certificates_logs_compliance_records} Out-of-tolerance protocol: {equipment_quarantine_investigation} Calibration service: {internal_external_certified_lab}
Write a 350-400 word SOP structured as: Pre-Calibration Checks, Calibration Procedure, Results Documentation, and Out-of-Tolerance Response. Include specific record-keeping requirements for regulatory compliance and equipment tagging procedures.
When to use it: An audit found gaps in your calibration records and you need consistent procedures for all measurement equipment.
Pro tip: Schedule calibrations 1-2 weeks before due dates. Equipment failures during calibration can halt operations if you’re already overdue.
You are writing an SOP for the quarterly supplier quality review process.
Supplier category: {critical_preferred_approved} Performance metrics: {quality_delivery_responsiveness_cost} Data sources: {receiving_reports_customer_complaints_audits} Review period: {quarterly_data_to_analyze} Scoring methodology: {weighted_factors_pass_fail_criteria} Action triggers: {performance_thresholds_requiring_response} Improvement planning: {corrective_action_requests_timelines}
Write a 500-550 word SOP covering: Data Collection and Analysis, Supplier Scorecard Development, Review Meeting Facilitation, and Action Plan Implementation. Include specific meeting agendas and follow-up tracking procedures.
When to use it: Supplier performance varies wildly but reviews happen inconsistently, making it hard to drive improvements.
Pro tip: Send scorecards to suppliers 48 hours before review meetings. Cold performance discussions rarely produce useful improvement commitments.
You are creating an SOP for investigating and resolving batch quality failures in production.
Product type: {manufactured_assembled_processed} Failure discovery: {in_process_final_inspection_customer_report} Batch tracking: {lot_numbers_serial_ranges_date_codes} Investigation scope: {related_batches_materials_equipment} Testing requirements: {additional_analysis_needed} Disposition options: {rework_scrap_conditional_release} Documentation standards: {investigation_reports_approvals}
Write a 450-500 word SOP structured as: Immediate Containment and Hold, Investigation and Root Cause Analysis, Batch Disposition Decision, and Preventive Action Implementation. Include specific approval authorities for different disposition decisions and customer notification requirements.
When to use it: A production batch failed final inspection and you need systematic investigation to prevent recurrence and handle existing inventory.
Pro tip: Quarantine the next three batches produced after the failed batch, not just the failed batch itself. Process problems often affect multiple production runs.
Training and Development
You are writing an SOP for onboarding new operations staff in their first week.