For operations managers who need working drafts this week, not another framework to build later. Copy these prompts into ChatGPT, fill in your specific details, and get usable outputs in 30 seconds.
These prompts pair well with Jasper AI for Operations-specific tone control, or Copy.ai for fast iteration.
Performance Reviews and Team Management
You are an operations manager writing a year-end performance review for a team lead who consistently hits targets but struggles with delegation.
Employee: {employee_name} Role: {job_title}, {years_at_company} years at the company Key metrics achieved: {three_specific_metrics_with_numbers} Delegation struggles: {specific_examples_of_micromanagement} Team feedback: {two_quotes_from_direct_reports} Development goal: {specific_leadership_skill_to_build} Rating: {exceeds_expectations / meets_expectations / needs_improvement}
Write a 400-500 word performance review using the SBI model. Start with metric recognition. Address delegation in the middle third, framed as growth opportunity not criticism. Close with one concrete development goal and timeline.
When to use it: Thursday afternoon before your Friday review meetings when you need to document a high performer’s leadership development areas.
Pro tip: If the employee manages a critical process, mention how improved delegation reduces single-point-of-failure risk - operations leaders respond better to business continuity framing than soft skills language.
You are an operations manager having a difficult conversation with an underperforming technician whose quality scores have dropped for three consecutive months.
Employee: {employee_name} Current quality score: {percentage_or_rating} Previous score: {baseline_for_comparison} Specific quality issues: {two_to_three_concrete_examples} Root cause (if known): {training_gap / personal_issues / process_change / unclear} Timeline for improvement: {weeks_or_months} Support available: {training / mentoring / schedule_adjustment} Consequence if no improvement: {pip / role_change / termination}
Write a 250-300 word conversation script. Lead with concern not blame. Present the data first. Ask one open question about barriers they’re facing. End with clear expectations and next check-in date.
When to use it: Before a Monday morning one-on-one when quality metrics show decline and you need to address it directly but supportively.
Pro tip: Include the exact quality score in your script - operations staff respond better to specific numbers than vague “performance concerns.”
You are an operations manager writing a promotion recommendation for a shift supervisor being considered for operations coordinator.
Employee: {employee_name} Current role: {current_position} Promotion target: {new_role_title} Tenure in current role: {months_or_years} Key process improvements led: {two_specific_examples_with_results} Leadership evidence: {examples_of_training_others_or_conflict_resolution} Readiness gaps: {skills_or_experience_still_developing} Promotion timing: {immediate / next_quarter / needs_six_months}
Write a 350-400 word memo to senior management. Open with your recommendation and timeline. Present evidence in the middle using specific process improvements and leadership examples. Address any readiness gaps honestly with mitigation plan.
When to use it: Two weeks before promotion cycle deadlines when you need to advocate for a strong internal candidate.
Pro tip: Quantify the process improvements with cycle time, error rates, or cost savings - senior management evaluates operations promotions on measurable impact.
You are an operations manager writing feedback for a new hire completing their 90-day probationary period successfully.
Employee: {employee_name} Role: {job_title} Start date: {hire_date} Training milestones completed: {specific_certifications_or_skills_mastered} Integration with team: {examples_of_collaboration_or_help_given} Performance metrics: {current_productivity_or_quality_scores} Areas still developing: {one_to_two_skills_progressing_normally} Permanent status recommendation: {yes / yes_with_conditions / extend_probation}
Write a 200-250 word probationary review summary. Confirm successful completion first. Highlight two specific examples of good integration. Note developing areas as normal progression. End with clear permanent status decision.
When to use it: Week 11 or 12 of a new hire’s tenure when HR needs probationary period documentation.
Pro tip: Mention specific teammates they’ve collaborated with well - it shows real integration rather than just task completion.
You are an operations manager conducting a skip-level meeting with a frontline employee whose direct supervisor is new to management.
Employee: {employee_name} Direct supervisor: {supervisor_name} Supervisor tenure in role: {weeks_or_months} Employee’s job satisfaction: {high / moderate / concerns} Specific feedback about supervisor: {communication / support / clarity_issues_or_strengths} Process or resource concerns: {equipment / training / workflow_issues} Employee suggestions: {improvements_they_want_to_see} Confidentiality level: {can_share_with_supervisor / anonymous_feedback_only}
Write a 150-200 word follow-up email summarizing the conversation and next steps. Thank them for candid feedback. Acknowledge any legitimate concerns without throwing the supervisor under the bus. Commit to one specific action with timeline.
When to use it: After monthly skip-levels when you need to document feedback and follow through on commitments made.
Pro tip: If there are supervisor development needs, frame them as “additional support I’ll provide” rather than employee complaints - protects both relationships.
Process Documentation and Improvement
You are an operations manager documenting a new standard operating procedure after a process improvement reduced cycle time by 30%.
Process name: {specific_process_title} Previous cycle time: {old_duration_with_units} New cycle time: {improved_duration} Key changes made: {three_to_four_specific_steps_modified} Roles involved: {job_titles_who_execute_this_process} Quality checkpoints: {inspection_or_verification_steps} Common mistakes to avoid: {two_errors_seen_during_rollout} Effective date: {when_this_becomes_standard}
Write a 500-600 word SOP document. Start with purpose and scope. List steps numerically with responsible roles. Include quality checkpoints after critical steps. End with troubleshooting section for common issues.
When to use it: Week after a successful process pilot when you need to formalize the new procedure for training and compliance.
Pro tip: Include the business case (30% cycle time reduction) in the purpose section - helps staff understand why the change matters, not just how to do it.
You are an operations manager writing an incident report after equipment failure caused a 4-hour production stoppage.
Incident date/time: {specific_timestamp} Equipment involved: {machine_or_system_name} Duration of stoppage: {hours_and_minutes} Production impact: {units_lost_or_orders_delayed} Root cause: {mechanical / electrical / operator_error / maintenance_gap} Immediate response: {emergency_actions_taken} Personnel involved: {staff_who_responded} Prevention measures: {specific_actions_to_prevent_recurrence} Cost estimate: {lost_production_value_if_known}
Write a 300-400 word incident report. Open with facts: what, when, duration, impact. Analyze root cause in the middle section. Close with prevention plan and responsible parties. Use factual tone, no blame language.
When to use it: Within 24 hours of a significant production disruption when management needs formal documentation for review.
Pro tip: If the root cause involves deferred maintenance, include the maintenance request date and approval status - shows whether this was preventable through different budget decisions.
You are an operations manager creating a process improvement proposal to reduce inventory carrying costs by consolidating supplier deliveries.
Current delivery frequency: {daily / weekly / multiple_times_per_week} Current inventory value on hand: {dollar_amount_or_days_of_supply} Proposed delivery schedule: {new_frequency} Estimated inventory reduction: {percentage_or_dollar_savings} Supplier flexibility: {willing / needs_incentive / resistant} Implementation timeline: {weeks_to_roll_out} Risk mitigation: {stockout_prevention_plan} Success metrics: {how_youll_measure_results}
Write a 400-500 word business case memo. Lead with the financial benefit and timeline. Present current state costs in the second paragraph. Explain the proposed solution with implementation steps. Address risks and mitigation in final section.
When to use it: When monthly inventory reports show carrying costs are eating into margins and you have a concrete solution to propose.
Pro tip: Calculate the opportunity cost of tied-up capital (carrying cost × current inventory value) to strengthen your financial argument beyond just storage savings.
You are an operations manager documenting lessons learned from a failed process change that was rolled back after two weeks.
Process change attempted: {what_you_tried_to_improve} Implementation date: {when_it_started} Rollback date: {when_you_reversed_it} Problems encountered: {specific_issues_that_caused_failure} Performance impact: {metrics_that_deteriorated} Staff feedback: {resistance_or_confusion_points} Root cause of failure: {poor_training / unrealistic_timeline / flawed_design} Lessons for future changes: {what_youll_do_differently}
Write a 250-300 word lessons learned document. State what was attempted and why it failed without defensiveness. Focus on systemic causes, not individual blame. End with specific recommendations for future change management.
When to use it: After rolling back a failed improvement when you need to document what went wrong for future reference and senior management.
Pro tip: Include timeline pressure as a factor if relevant - operations leaders often underestimate change management time, and documenting this helps with future project scoping.
You are an operations manager writing a quarterly process performance summary showing improvement trends across key metrics.
Quarter: {Q1 / Q2 / Q3 / Q4} {year} Key processes measured: {three_to_four_process_names} Cycle time improvements: {specific_percentages_or_duration_changes} Quality score changes: {before_and_after_percentages} Cost per unit trends: {dollar_amounts_or_percentage_changes} Staff efficiency gains: {productivity_metrics} Major process changes: {improvements_implemented_this_quarter} Next quarter priorities: {top_two_improvement_targets}
Write a 600-700 word quarterly summary report. Open with executive summary of key wins. Present each process performance with before/after metrics. Include a brief section on process changes made. Close with next quarter’s improvement targets and resource needs.
When to use it: Last week of each quarter when senior management needs operations performance data for board reporting.
Pro tip: Include year-over-year comparisons for the same quarter if you have historical data - shows sustainable improvement trends, not just seasonal variation.
Team Communication and Meeting Management
You are an operations manager writing a shift handoff communication after an equipment malfunction was temporarily repaired but needs permanent fixing.
Equipment: {machine_or_system_name} Issue discovered: {what_went_wrong} Temporary fix applied: {immediate_solution_used} Current operational status: {running_normally / limited_capacity / requires_monitoring} Permanent repair needed: {parts_ordered / vendor_contact / scheduled_maintenance} Monitoring requirements: {what_next_shift_should_watch} Escalation trigger: {when_to_call_you_or_maintenance} Estimated repair timeline: {when_permanent_fix_expected}
Write a 150-200 word shift handoff note. Start with current equipment status and what’s been done. Clearly state what the incoming shift needs to monitor. End with specific escalation criteria and your contact availability.
When to use it: End of shift when you’ve dealt with an equipment issue that isn’t fully resolved and the next team needs to understand the situation.
Pro tip: Include the exact symptoms that triggered your concern (unusual noise, temperature reading, etc.) so the next shift knows what normal vs. concerning looks like.
You are an operations manager sending a Monday morning team update after a challenging week with customer complaints about delivery delays.
Previous week’s delivery performance: {on_time_percentage} Root causes identified: {supplier_delays / staffing / equipment / process_issues} Customer complaints received: {number_and_severity} Actions taken last week: {specific_steps_to_address_issues} This week’s priorities: {focus_areas_for_improvement} Additional support available: {overtime / temp_staff / expedited_shipping} Success metrics for this week: {specific_targets} Team recognition: {individuals_who_went_above_and_beyond}
Write a 200-250 word team email. Acknowledge last week’s challenges without dwelling on them. Focus 60% of the message on this week’s action plan. End with appreciation for extra effort and confidence in improvement.
When to use it: Monday morning when you need to motivate a team recovering from a difficult performance period.
Pro tip: Lead with one specific action you’re taking as a manager (getting temp help, expediting supplies) to show you’re removing barriers, not just asking for more effort.
You are an operations manager preparing talking points for a monthly all-hands meeting where you need to announce a policy change that will initially inconvenience staff.
Policy change: {what_is_changing} Effective date: {when_it_starts} Business reason: {compliance / cost_reduction / customer_requirement / safety} Impact on daily work: {specific_inconveniences_or_extra_steps} Training provided: {what_support_staff_will_receive} Timeline for adjustment: {how_long_before_new_normal} Benefits once established: {long_term_advantages_for_team} Your availability: {office_hours / open_door_policy}
Write 300-350 words of talking points. Start with the business context, not the policy details. Present the change as necessary, not optional. Acknowledge the inconvenience honestly. Close with commitment to support during transition and long-term benefits.
When to use it: Week before implementing a policy change when you need to explain unpopular but necessary changes to the full team.
Pro tip: If it’s a compliance requirement, name the specific regulation or customer mandate - staff accept “we have to” better than “we decided to.”
You are an operations manager writing an urgent communication about a temporary workflow change needed due to a key team member’s unexpected medical leave.
Team member: {name_or_role_if_confidential} Leave duration: {estimated_weeks_or_indefinite} Critical responsibilities affected: {specific_tasks_or_processes} Temporary coverage plan: {who_is_covering_what} External support: {temp_agency / contractor / vendor_assistance} Training timeline: {when_coverage_staff_will_be_ready} Process modifications: {any_simplified_or_delayed_procedures} Your increased involvement: {additional_oversight_youll_provide}
Write a 200-250 word team announcement. Express appropriate concern for the team member without sharing medical details. Present the coverage plan as temporary but thorough. Ask for patience during knowledge transfer and offer your direct support.
When to use it: Within 48 hours of learning about an unexpected absence that affects critical operations.
Pro tip: If the absent person handled vendor relationships, include their key contact information and introduction protocol - don’t let external relationships suffer during transition.
You are an operations manager sending a Friday afternoon summary to your boss highlighting this week’s wins and flagging next week’s potential issues.
Week ending: {date} Key accomplishments: {three_specific_wins_with_metrics} Problems resolved: {issues_you_handled_this_week} Team performance: {standout_contributions_or_overall_trends} Next week’s concerns: {potential_problems_youre_watching} Resource needs: {additional_support_or_approvals_needed} Customer feedback: {complaints_resolved_or_compliments_received} Budget status: {on_track / over / under_for_month}
Write a 250-300 word weekly report email. Lead with accomplishments and metrics. Address problems as resolved, not ongoing concerns. Flag next week’s issues with your planned approach. End with specific requests or FYI items needing boss awareness.
When to use it: Every Friday afternoon to keep your manager informed and build credibility through consistent communication.
Pro tip: Include one forward-looking item your boss cares about (budget, safety, customer satisfaction) even if there’s no urgent issue - shows you’re managing strategically, not just firefighting.
Vendor and External Communications
You are an operations manager writing a performance improvement letter to a supplier whose delivery delays have affected your production schedule three times this month.
Supplier company: {vendor_name} Contract/PO reference: {agreement_number} Delivery issues this month: {specific_dates_and_delays} Production impact: {hours_lost_or_orders_affected} Root causes given: {suppliers_explanations_for_delays} Required improvement: {on_time_delivery_percentage_needed} Measurement period: {timeframe_for_evaluation} Consequences of continued delays: {contract_review / alternative_suppliers / penalties} Meeting request: {proposed_date_for_discussion}
Write a 300-350 word formal letter. State the delivery performance problem with specific dates and impact. Reference contract terms without being threatening. Request a face-to-face meeting to discuss improvement plan. Close professionally but firmly.
When to use it: After the third significant delivery delay in a month when you need to escalate beyond phone calls to formal documentation.
Pro tip: Copy your procurement team and your boss on this letter - vendor performance issues often need cross-functional support to resolve effectively.
You are an operations manager requesting a service credit from your logistics provider after a shipment delay caused customer complaints and expedited shipping costs.
Service failure date: {when_shipment_was_delayed} Shipment tracking: {reference_numbers} Promised delivery: {original_commitment_date} Actual delivery: {when_it_finally_arrived} Customer impact: {complaints_received_or_relationship_damage} Additional costs incurred: {expedited_shipping_or_overtime_costs} Service level agreement: {contractual_on_time_commitment} Credit requested: {dollar_amount_or_percentage} Supporting documentation: {attached_receipts_or_complaint_records}
Write a 250-300 word service credit request. Present the facts chronologically. Quantify the business impact and additional costs. Reference specific SLA terms. Request fair compensation professionally. Attach supporting documentation.
When to use it: Within one week of a logistics failure that cost you money or customer relationships when you need financial recovery.
Pro tip: Include customer complaint text or screenshots if you have them - logistics providers respond better to evidence of relationship damage than just internal cost claims.
You are an operations manager writing a vendor qualification letter for a new supplier being considered to replace an underperforming incumbent.
Prospective supplier: {company_name} Product/service category: {what_youre_sourcing} Annual volume estimate: {dollar_value_or_unit_quantity} Critical requirements: {quality_specs_delivery_or_compliance_needs} Current supplier issues: {problems_driving_the_change} Evaluation timeline: {when_you_need_responses} Trial period terms: {small_order_or_pilot_program} Key evaluation criteria: {price_quality_delivery_service_weights} Implementation target: {when_youd_switch_if_selected}
Write a 400-450 word qualification request letter. Introduce your company and opportunity size. Explain evaluation process and timeline clearly. Ask for specific capabilities information and references. Present this as a real opportunity, not just price shopping.
When to use it: When incumbent supplier performance is consistently poor and you need to seriously evaluate alternatives with proper documentation.
Pro tip: Include your current supplier’s performance metrics (delivery %, quality issues, response time) so prospects understand the bar they need to clear.
You are an operations manager writing a contract renewal negotiation letter focusing on service improvements rather than just price reductions.
Supplier: {vendor_name} Contract expiration: {current_agreement_end_date} Contract value: {annual_spend_amount} Current service issues: {specific_problems_needing_improvement} Required service improvements: {measurable_performance_targets} Additional services needed: {new_capabilities_you_want} Competitive alternatives: {other_vendors_youve_evaluated} Renewal timeline preference: {contract_length_desired} Performance incentives: {bonus_payments_for_exceeding_targets}
Write a 350-400 word renewal discussion letter. Express satisfaction with partnership while acknowledging improvement areas. Present specific service level requirements for new contract. Indicate you’ve done market research without threatening. Request proposal meeting.
When to use it: Three months before contract expiration when you want to improve service levels, not just negotiate price.
Pro tip: Propose performance bonuses for exceeding service levels - suppliers often accept tighter SLAs more readily when there’s upside potential, not just penalties.
You are an operations manager writing a vendor termination notice after unsuccessful attempts to improve performance through meetings and warnings.
Vendor: {company_name} Contract reference: {agreement_number} Termination clause: {section_allowing_termination_for_cause} Performance issues: {documented_problems_with_dates} Improvement attempts: {meetings_warnings_or_action_plans_tried} Termination effective date: {last_day_of_service} Final deliverables required: {outstanding_work_to_complete} Transition timeline: {handover_schedule} Final payment terms: {how_outstanding_invoices_will_be_handled}
Write a 250-300 word termination letter. Reference specific contract terms allowing termination. Document the performance issues and improvement efforts objectively. State termination date clearly and transition requirements. Keep tone professional, not emotional.
When to use it: After formal performance improvement attempts have failed and you need to terminate a vendor relationship with proper legal documentation.
Pro tip: Copy your legal and procurement teams on this letter before sending - vendor terminations can trigger disputes, and you want internal alignment on the documentation.
Frequently Asked Questions
What makes these ChatGPT prompts different from generic operations templates?
Each prompt produces a finished draft you can edit and send immediately. Instead of getting another template to fill out, you get actual performance reviews, incident reports, or vendor letters ready for light editing. The variables are specific details from your situation, not placeholder categories.
How do I adapt these prompts for different company sizes or industries?
The core scenarios work across industries - equipment failures, vendor delays, and performance issues happen everywhere. For smaller companies, reduce the formality level by changing tone variables from “formal” to “direct.” For larger organizations, add approval workflow steps in the constraint section.
Can I use these prompts with Claude or other AI tools instead of ChatGPT?
Yes, these prompts work with any conversational AI. Claude tends to be more concise, so you might increase word count targets by 50-100 words. Other tools might need the scenario context repeated if they have shorter memory spans.