Operations teams need process documentation that works, not another template to fill out later. These 25 prompts generate finished SOPs, workflows, and process guides you can use immediately.
These prompts pair well with Jasper AI for Operations-specific tone control, or Copy.ai for fast iteration.
Standard Operating Procedures
You are an Operations Manager documenting a critical business process that new hires struggle with.
Process: {process_name} Department: {department_name} Frequency: {daily/weekly/monthly/as_needed} Average completion time: {time_estimate} Tools required: {software_and_systems} Common mistakes: {three_frequent_errors} Compliance requirements: {regulatory_or_policy_requirements} Audience skill level: {beginner/intermediate/expert}
Write a 600 to 800 word SOP using numbered steps with clear decision points. Include a “Before You Start” checklist, step-by-step instructions with specific screenshots callouts, and a troubleshooting section for the three most common errors. End with quality checkpoints and escalation contacts.
When to use it: When you’re getting the same process questions in Slack for the third time this week and need to document it properly.
Pro tip: Add specific screenshot callouts like “Screenshot needed: the blue ‘Generate Report’ button in the top right” so whoever updates this later knows exactly what visuals to include.
You are documenting a handoff process between two departments that currently breaks down every month.
Handoff from: {department_a} Handoff to: {department_b} Trigger event: {what_initiates_handoff} Information passed: {data_documents_context} Timeline requirement: {deadline_or_SLA} Current failure points: {where_things_go_wrong} Systems involved: {platforms_tools_databases} Sign-off required: {yes/no_and_who}
Create a 400 to 500 word handoff SOP with clear ownership at each step. Use a table format showing WHO does WHAT by WHEN. Include communication templates for the initial handoff and completion confirmation. Address the current failure points with specific prevention steps.
When to use it: After another project falls through the cracks between teams and you need bulletproof handoff documentation.
Pro tip: Build in redundancy by requiring both an automated notification AND a personal confirmation message for critical handoffs.
You are writing an emergency procedure for when a critical system fails during business hours.
Failed system: {system_name} Business impact: {revenue_customer_operational_impact} Detection method: {how_team_knows_its_down} Immediate workaround: {manual_alternative_process} Key stakeholders to notify: {internal_and_external_contacts} Escalation timeline: {when_to_escalate_and_to_whom} Recovery time estimate: {typical_restoration_time} Communication requirements: {customer_facing_updates_needed}
Write a 300 to 400 word emergency response procedure with minute-by-minute actions for the first 30 minutes. Include pre-written notification templates, clear escalation triggers, and specific roles for team members. Format as a numbered action list with time stamps.
When to use it: Building your incident response playbook so your team doesn’t panic when systems actually go down.
Pro tip: Test your emergency procedures during planned maintenance windows to find gaps before you need them for real incidents.
You are creating an SOP for a monthly compliance reporting process that involves multiple data sources.
Report name: {compliance_report_type} Regulatory body: {agency_or_authority} Data sources: {systems_spreadsheets_departments} Submission deadline: {date_and_time_requirements} Data validation steps: {accuracy_checks_required} Approval chain: {who_reviews_before_submission} File format requirements: {PDF_Excel_specific_formatting} Backup procedures: {what_if_primary_system_fails}
Create a 500 to 600 word monthly compliance SOP with a timeline working backwards from the deadline. Include data collection templates, validation checklists, and approval tracking. Add specific file naming conventions and submission confirmation steps.
When to use it: When compliance deadlines sneak up on you because the process isn’t documented and nobody remembers all the steps.
Pro tip: Set calendar reminders two weeks before each step, not just the final deadline, because compliance data collection always takes longer than expected.
You are documenting a quality control process for a product or service delivery.
Product/Service: {what_youre_quality_checking} Quality standards: {specific_metrics_or_criteria} Inspection points: {when_in_process_checks_happen} Testing tools: {equipment_software_checklists} Pass/fail criteria: {specific_thresholds} Rejection procedure: {what_happens_to_failures} Documentation requirements: {records_to_maintain} Review frequency: {how_often_process_gets_audited}
Write a 450 to 550 word quality control SOP with clear inspection criteria and decision trees. Include sample forms for recording results, specific actions for different failure types, and tracking requirements for trend analysis. End with continuous improvement triggers.
When to use it: After quality issues reach customers and you need systematic prevention instead of reactive fixes.
Pro tip: Include photos or diagrams of what “good” and “defective” look like, especially for visual quality checks that rely on human judgment.
Workflow Documentation
You are mapping a complex approval workflow that currently lives in people’s heads and email chains.
Workflow name: {approval_process_name} Request types: {what_needs_approval} Approval levels: {who_approves_what_amounts_or_types} Decision criteria: {how_approvers_make_decisions} Timeframe expectations: {how_long_each_step_takes} Escalation rules: {when_and_how_to_escalate} Documentation required: {supporting_materials_needed} Communication touchpoints: {when_to_update_requestor}
Create a 400 to 500 word workflow guide with a visual decision tree format. Show parallel vs sequential approvals clearly. Include template language for approval requests and status updates. Add specific criteria for automatic approvals vs manual review.
When to use it: When approval requests sit in limbo because nobody knows whose desk they should be on next.
Pro tip: Include dollar thresholds or other automatic triggers that bypass certain approval levels to speed up routine requests.
You are documenting a customer onboarding workflow from initial sale to full activation.
Customer type: {enterprise/SMB/individual} Onboarding duration: {typical_timeline} Key milestones: {major_checkpoints_or_deliverables} Team members involved: {sales_support_technical_account_management} Customer responsibilities: {what_they_must_provide_or_complete} Success metrics: {how_you_measure_successful_onboarding} Common roadblocks: {where_onboarding_typically_stalls} Handoff points: {between_teams_or_systems}
Write a 500 to 600 word onboarding workflow with week-by-week owner assignments. Include customer communication templates for each phase, internal handoff checklists, and specific escalation triggers for delayed milestones. Format as a timeline with parallel tracks for different team activities.
When to use it: When new customers take twice as long to activate because your onboarding process isn’t systematic.
Pro tip: Build in proactive check-ins at day 3, week 1, and week 2 rather than waiting for customers to get stuck and reach out.
You are creating a workflow for processing and resolving customer complaints from intake to resolution.
Complaint channels: {phone_email_chat_social_media} Severity levels: {how_you_categorize_complaint_urgency} Response time targets: {SLA_for_different_severity_levels} Investigation process: {how_you_research_and_verify_issues} Resolution authority: {who_can_approve_what_remedies} Documentation requirements: {what_records_to_maintain} Follow-up protocol: {post_resolution_customer_contact} Escalation triggers: {when_to_involve_management}
Create a 450 to 550 word complaint resolution workflow with clear triage criteria and response templates. Include decision points for different resolution paths, approval requirements for compensation, and quality assurance checkpoints. End with customer satisfaction tracking steps.
When to use it: When customer complaints disappear into a black hole and resurface as angry executives emails three weeks later.
Pro tip: Set up automatic reminders at 50% and 90% of your SLA deadline so complaints don’t slip past response time commitments.
You are documenting a procurement workflow for non-standard purchases that require vendor evaluation.
Purchase category: {equipment/services/software} Budget range: {spending_threshold_triggering_this_process} Evaluation criteria: {technical_financial_compliance_requirements} Stakeholders involved: {requesting_department_procurement_finance_legal} Vendor requirements: {qualifications_certifications_documentation} Timeline constraints: {how_long_process_typically_takes} Approval gates: {decision_points_and_sign_offs} Contract requirements: {terms_negotiations_legal_review}
Write a 500 to 600 word procurement workflow with vendor evaluation scorecards and decision criteria. Include template RFP language, comparison frameworks, and approval documentation. Add specific timelines for each phase and contingency plans for urgent purchases.
When to use it: When you need to buy something outside normal purchasing agreements and nobody knows what hoops to jump through.
Pro tip: Maintain a pre-approved vendor list for common purchase categories to skip the full evaluation process for routine buys.
You are mapping an employee offboarding workflow to ensure security, knowledge transfer, and compliance.
Employee type: {role_level_and_access_requirements} Notice period: {two_weeks_immediate_extended_transition} System access: {applications_databases_physical_locations} Knowledge transfer needs: {projects_relationships_institutional_knowledge} Equipment return: {laptop_phone_keys_parking} Final documentation: {exit_interview_compliance_forms} Handoff responsibilities: {ongoing_work_client_relationships} Timeline: {last_day_and_transition_period}
Create a 400 to 500 word offboarding workflow with day-by-day checklists for IT, HR, and the departing employee’s manager. Include knowledge transfer templates, access removal verification steps, and compliance documentation requirements. Add specific timing for each task relative to the last day.
When to use it: After discovering departing employees still have system access three months later, or critical knowledge walked out the door.
Pro tip: Start knowledge transfer immediately when someone gives notice, not in their final week when they’re mentally checked out.
Process Improvement Documentation
You are documenting findings from a process improvement analysis with specific recommendations for implementation.
Current process: {process_being_improved} Performance baseline: {current_metrics_time_cost_quality} Problem areas identified: {bottlenecks_waste_errors} Proposed solution: {specific_changes_recommended} Expected benefits: {quantified_improvements} Implementation requirements: {resources_timeline_training} Risk factors: {potential_disruptions_or_failures} Success metrics: {how_youll_measure_improvement}
Write a 600 to 700 word process improvement recommendation with before/after comparisons, implementation roadmap, and ROI analysis. Include change management considerations, training requirements, and monitoring plans. Format with executive summary, detailed analysis, and action plan sections.
When to use it: When you’ve identified process improvements but need formal documentation to get leadership buy-in and resources.
Pro tip: Include quick wins that can be implemented immediately alongside longer-term improvements to show early progress.
You are creating documentation for a pilot program testing a new process before full rollout.
Pilot process: {what_youre_testing} Test environment: {department_team_or_location} Pilot duration: {timeline_for_testing} Success criteria: {metrics_that_define_success} Baseline measurements: {current_state_for_comparison} Test parameters: {what_varies_from_current_process} Feedback collection: {how_youll_gather_user_input} Rollback plan: {what_if_pilot_fails}
Create a 450 to 500 word pilot program documentation with clear testing protocols, data collection methods, and decision criteria for full implementation. Include participant briefing materials, feedback collection templates, and go/no-go evaluation framework.
When to use it: Before rolling out process changes company-wide that might break everything if they don’t work as expected.
Pro tip: Choose pilot participants who will give honest feedback, not just cheerleaders who’ll say everything is wonderful.
You are documenting lessons learned from a failed process implementation to prevent repeating mistakes.
Failed process: {what_was_being_implemented} Implementation timeline: {when_it_started_and_stopped} Failure points: {specific_where_and_why_it_broke} Root causes: {underlying_reasons_not_just_symptoms} Impact assessment: {cost_time_morale_customer_effects} Warning signs missed: {early_indicators_ignored} Stakeholder feedback: {what_users_and_managers_said} Lessons for future: {specific_preventable_mistakes}
Write a 500 to 600 word post-mortem analysis with specific failure modes, contributing factors, and prevention strategies. Include early warning indicators to watch for in future implementations and revised change management approaches. Frame as learning opportunity, not blame assignment.
When to use it: After a process change crashes and burns, and you need to extract value from the failure before trying again.
Pro tip: Interview everyone involved separately before writing the post-mortem to get honest perspectives without group think.
You are creating a process standardization guide to align inconsistent practices across multiple teams or locations.
Inconsistent process: {what_varies_between_teams} Current variations: {how_different_groups_do_it_now} Performance differences: {which_variations_work_better} Standardization scope: {what_will_be_uniform_vs_flexible} Best practices identified: {proven_approaches_to_adopt} Implementation challenges: {resistance_training_system_changes} Training requirements: {what_people_need_to_learn} Compliance monitoring: {how_youll_ensure_adoption}
Create a 550 to 650 word standardization guide with unified procedures, implementation timeline, and adoption tracking methods. Include change rationale for each team, training materials outline, and performance monitoring approach. Address specific concerns from different groups.
When to use it: When you discover five different teams doing the same process five completely different ways with wildly different results.
Pro tip: Identify the informal leaders in each team early and get them on board before announcing the standardization to everyone else.
You are documenting a process automation project transitioning manual work to automated systems.
Manual process: {current_human_tasks} Automation scope: {what_will_be_automated_vs_manual} Technology solution: {software_tools_or_systems} Human touchpoints: {remaining_manual_oversight_needed} Error handling: {what_happens_when_automation_fails} Transition timeline: {phased_or_immediate_cutover} Training requirements: {new_skills_people_