35 ChatGPT Prompts for Operations Managers (SOPs, Team Communication, and Process Improvement Done Faster)
Operations managers keep the machine running. You're writing SOPs that nobody reads, chasing updates across five teams, running vendor reviews, documenting processes that change quarterly, and somehow also expected to lead improvement initiatives while keeping the lights on.
ChatGPT doesn't run your operations. But it writes your SOPs in a fraction of the time, turns meeting chaos into structured action items, drafts your vendor communications, and helps you structure a process improvement that doesn't get killed in committee. These 35 prompts are built for operations managers across industries — manufacturing, logistics, tech, healthcare, and professional services.
Section 1: SOPs and Process Documentation
Prompt 1 — Standard Operating Procedure
Write a Standard Operating Procedure (SOP) for [process name] at [company type]. The process involves: [describe the steps at a high level]. Audience: new employees with [no / basic / intermediate] experience. Include: Purpose, Scope, Roles and Responsibilities, Step-by-Step Procedure (numbered), Quality Checks / Checkpoints, Common Errors and How to Avoid Them, and Related Documents. Use plain language. No jargon unless industry-standard.
Prompt 2 — Process Flow Narrative
Write a narrative description of this process flow for inclusion in our operations manual: [describe the process — inputs, steps, decision points, outputs]. The narrative should: describe each step in order, explain why each step exists (not just what to do), call out decision points clearly, and note who is responsible at each stage. Audience: front-line staff and supervisors. Under 500 words.
Prompt 3 — SOP Update Summary
Write a change summary for an updated SOP. Previous version: [what it said]. Updated version: [what changed]. Reason for update: [why]. Impact on staff: [what they need to do differently]. Effective date: [date]. Format: brief memo I can attach to the new SOP to explain the changes without requiring staff to re-read the entire document.
Prompt 4 — Onboarding Checklist
Create an onboarding checklist for a new [role: warehouse associate / customer service rep / operations coordinator / team lead] at [company type]. Cover the first 30 days. Include: Day 1 orientation tasks, systems access and training to complete (Week 1), shadowing and independent task milestones (Weeks 2–4), required certifications or compliance training, and check-in touchpoints with their manager. Format as a checklist with owner (new hire / manager / HR).
Prompt 5 — Knowledge Base Article
Write a knowledge base article for our internal wiki on [topic: how to process a return / how to escalate a vendor issue / how to run the weekly report / how to handle a compliance incident]. Audience: employees who may encounter this for the first time. Include: a brief description of when this applies, step-by-step instructions, what to do if something goes wrong, and who to contact for help. Under 400 words.
Section 2: Team Communication
Prompt 6 — Weekly Ops Team Update
Write a weekly operations update email to the [team / department / leadership]. This week: [key activities and completions]. In progress: [current work]. Blockers or issues: [list with owners]. Metrics vs. target: [key numbers]. Next week's priorities: [list top 3]. Keep it under 300 words. Scannable with headers. No fluff.
Prompt 7 — All-Hands Operations Briefing
Write a 5-minute all-hands operations briefing script for [monthly / quarterly] team meeting. Cover: performance summary ([key metrics vs. target]), highlight of the month ([win or progress]), one area of focus for next period ([improvement initiative or priority]), and one recognition or shout-out. Tone: direct, encouraging, clear. No management-speak.
Prompt 8 — Escalation Email (Internal)
Write an internal escalation email to [manager / director / VP] about [issue: recurring quality problem / bottleneck / vendor failure / staffing gap]. Include: what the problem is, how long it's been occurring, impact (quantified if possible), what's been tried, and what I need from them (decision / resource / executive support). Direct, factual, no drama. Under 200 words.
Prompt 9 — Cross-Team Dependency Request
Write an email to [team name] requesting their support for [what you need]. Context: [why this matters to operations]. Specific ask: [what you need them to do, by when]. Impact if not done: [briefly]. What we'll provide in return: [if applicable]. Collaborative, not demanding. Under 150 words.
Prompt 10 — Difficult Performance Conversation Prep
Help me prepare for a performance conversation with a team member who is [specific issue: not hitting productivity targets / showing up late repeatedly / making repeated errors / conflict with teammates]. My goal: [what I want to achieve]. What I've observed: [specific behaviors, not character]. What good looks like: [the standard]. What I'm offering: [support, timeline, consequences]. Format as talking points, not a script.
Section 3: Process Improvement
Prompt 11 — Problem Statement
Help me write a clear problem statement for a process improvement initiative. The issue: [describe in plain terms]. What we observe (symptoms): [list]. What we've measured (if anything): [data points]. Impact on the business: [cost / time / quality / customer experience]. What "solved" would look like: [the goal state]. Use this to build a crisp, one-paragraph problem statement that I can present to leadership for approval.
Prompt 12 — Root Cause Analysis (5 Whys)
Guide me through a 5 Whys root cause analysis for [problem]. Starting symptom: [describe]. Ask "why" five times, building on each answer, to reach the root cause. Then write a structured summary: Problem, Root Cause, Contributing Factors, and Proposed Corrective Action. I'll fill in the "why" answers — you format the final document.
Prompt 13 — Process Improvement Proposal
Write a 1-page process improvement proposal for [initiative name]. Problem: [describe]. Current state: [what's happening now, quantified if possible]. Proposed solution: [what change you're recommending]. Expected benefit: [time saved / cost reduced / error rate reduced / other]. Resources required: [people, tools, time]. Risks: [list]. Request: [what you need approved]. Audience: your manager or operations leadership.
Prompt 14 — After-Action Review
Write an after-action review (AAR) for [event: product launch / incident / busy season / process rollout]. Cover: What was planned, What actually happened, What went well (specific), What didn't go well (specific), Root causes of issues, Lessons learned, and Action items for next time (with owners). Format as a structured internal document for team review.
Prompt 15 — Metrics Dashboard Narrative
Write a brief narrative for our operations metrics dashboard for [period]. Key metrics: [list with values and targets]. For each metric: current value, vs. target (% difference), vs. prior period, 1-sentence interpretation. Audience: department heads who receive this weekly. Flag any metric that needs attention and name the owner. Under 400 words total.
Section 4: Vendor and Supplier Management
Prompt 16 — Vendor Evaluation Matrix
Create a vendor evaluation matrix for selecting a [vendor type: logistics provider / software platform / staffing agency / materials supplier]. Evaluation criteria: [list 6–8 factors — price, lead time, quality, reliability, support, compliance, scalability]. Scoring: 1–5 per criterion. Weights: [assign based on priority]. Format as a table. Write brief descriptions for what "1" and "5" look like for each criterion.
Prompt 17 — Vendor Performance Review Email
Write a vendor performance review email to [vendor name] covering the [period]. Summary of performance: [overall assessment]. Areas of strength: [list]. Areas requiring improvement: [list with specific examples]. Metrics: [on-time delivery %, quality defect rate, response time, etc.]. Next steps: [what we need from them by when]. Tone: professional and direct — not punitive, but clear. Under 300 words.
Prompt 18 — Vendor Issue Escalation
Write an escalation email to a vendor's account manager or senior contact about a recurring issue: [describe issue — missed SLAs / quality failures / billing errors / communication gaps]. Reference: [previous communications or meetings where this was flagged]. Impact on our business: [quantify]. What we need: [specific action, specific timeline]. Consequence if unresolved: [what we'll do — contract review / alternative sourcing]. Professional but firm. Under 200 words.
Prompt 19 — RFP Requirements Section
Write the requirements section for an RFP for [service or product]. Our business context: [brief]. Key requirements: [list — include must-haves and nice-to-haves separately]. Evaluation criteria: [list]. What vendors must include in their response: [list of deliverables]. Submission deadline and format: [details]. Under 400 words. Clear enough that any qualified vendor can self-assess fit before responding.
Section 5: Incident Management and Risk
Prompt 20 — Incident Report
Write an incident report for [type of incident: equipment failure / safety incident / IT outage / quality breach / delivery failure]. Date/time: [when]. What happened: [factual sequence of events]. Impact: [business, customer, safety impact]. Immediate response taken: [what was done]. Root cause (preliminary): [initial assessment]. Corrective actions: [what's being done now]. Preventive actions: [what will stop recurrence]. For management and compliance records.
Prompt 21 — Business Continuity Communication
Write a communication to [team / customers / partners] about a service disruption or operational issue: [describe issue]. What's affected: [specific impact]. What we're doing: [response actions]. Expected resolution: [timeline if known / "we will update by [time]" if not]. Alternative options during the disruption: [if any]. Contact for questions: [who]. Tone: factual, calm, no over-promising. Under 200 words.
Prompt 22 — Risk Register Entry
Write risk register entries for [3–4 operational risks] in [our business area: supply chain / staffing / technology / regulatory]. For each: Risk Description, Likelihood (High/Medium/Low), Impact (High/Medium/Low), Current Controls, Additional Mitigation Actions, Owner, and Review Date. Format as a table. Risks: [list them].
Section 6: Capacity and Resource Planning
Prompt 23 — Headcount Justification
Write a headcount justification memo for [role: 1 new operations coordinator / 2 additional warehouse staff / a team lead]. Current workload evidence: [data points — volume handled, overtime hours, error rates, missed SLAs]. What's being done with existing team: [describe the gap]. Impact of not hiring: [risk to operations / customer experience / team burnout]. Expected ROI: [what the hire enables]. Under 300 words. For HR and finance approval.
Prompt 24 — Capacity Planning Summary
Write a capacity planning summary for [department / facility] for [next quarter / busy season]. Current capacity: [describe — headcount, equipment, throughput]. Projected demand: [what's coming — volume forecast, new contracts, seasonal peak]. Gap analysis: [where we're short]. Recommended actions: [list — hire, cross-train, add shifts, outsource]. Timeline for action: [when decisions need to be made]. Under 300 words. For operations leadership review.
Section 7: Compliance and Quality
Prompt 25 — Compliance Training Reminder
Write a reminder email to [team] about upcoming compliance training: [training name]. Due date: [date]. What happens if not completed: [consequence — system lockout / regulatory risk / HR action]. How to complete it: [link/location/process]. Estimated time: [X minutes]. Tone: clear and matter-of-fact — not threatening, but serious. Under 150 words.
Prompt 26 — Audit Preparation Checklist
Create an audit preparation checklist for an upcoming [type of audit: ISO / OSHA / financial / customer / regulatory]. Audit scope: [what's being reviewed]. Checklist sections: Documentation Review (what to have ready), Process Walkthroughs (what to demonstrate), Personnel Preparation (who needs to know what), Facility/System Readiness (what to check), and Day-of Logistics. Timeline: [X weeks out / 1 week out / day before].
Prompt 27 — Quality Issue Root Cause Email
Write an email to [customer / internal stakeholder / leadership] explaining a quality issue that occurred: [describe issue]. What happened: [factual explanation, no excuses]. Root cause: [honest assessment]. What we've done immediately: [corrective action]. What we're doing to prevent recurrence: [systemic fix]. Timeline for resolution: [date]. Tone: accountable, solution-focused. Under 200 words.
Section 8: Career and Personal Effectiveness
Prompt 28 — LinkedIn Profile for an Operations Manager
Write a LinkedIn "About" section for an operations manager with [X] years of experience in [industry: manufacturing / logistics / tech / healthcare / retail]. Specialties: [e.g., process improvement, lean/six sigma, supply chain, team leadership]. Key accomplishments: [2–3 measurable achievements]. Career goal: [stay IC / move to director / pivot to consulting / COO track]. 150–200 words. Human, specific, not a job description.
Prompt 29 — Self-Assessment for Performance Review
Help me write my annual performance review self-assessment as an operations manager. Key contributions: [list]. Metrics I improved: [with numbers — throughput, error rate, cost, SLA compliance]. A challenge I solved: [describe]. Leadership or team development wins: [list]. What I want to focus on next year: [goal]. 400–500 words. Confident and evidence-based.
Prompt 30 — Ops Manager Interview Prep
Prepare me for a senior operations manager interview at [company type] in [industry]. Generate 10 likely questions — both behavioral (tell me about a time you...) and operational (how would you...) — and for each: a model answer structure (STAR where appropriate) and what the interviewer is actually evaluating. Include 2 questions I should ask them.
Section 9: Project and Change Management
Prompt 31 — Change Management Communication
Write a change management communication to [team] about [upcoming change: new system / process change / org restructure / policy update]. Cover: what's changing, why it's changing, what it means for them day-to-day, what support is available, and the timeline. Anticipate the top 2 concerns and address them proactively. Tone: transparent, empathetic, direct. Under 300 words.
Prompt 32 — Project Status Update (Ops Initiative)
Write a weekly status update for [operations initiative: new WMS implementation / facility move / process redesign / ERP rollout]. Status: [on track / at risk / delayed]. Completed this week: [list]. Upcoming milestones: [list with dates]. Risks/issues: [list with owner and mitigation]. Decision needed: [if any]. Audience: project sponsor + leadership. Under 250 words.
Prompt 33 — Lessons Learned Document
Write a lessons learned document for [completed project or initiative]. What we set out to do: [objective]. What we actually delivered: [outcome]. What went well (3 things): [list with brief explanation]. What didn't go well (3 things): [list with brief explanation]. Root causes of the issues: [analysis]. Recommendations for future similar projects: [list]. This document will be added to our project archive.
Prompt 34 — Stakeholder Update on Delayed Project
Write an email to [stakeholder] informing them that [project or deliverable] will be delayed from [original date] to [new date]. Reason for delay: [factual explanation]. Impact on their plans: [acknowledge specifically]. What we're doing to minimize the delay: [actions taken]. New timeline and key milestones: [list]. One ask from them (if any): [what you need]. Direct and accountable. Under 200 words.
Prompt 35 — Executive Brief on Ops Initiative
Write a 1-page executive brief on [operations initiative] for [CEO / board / senior leadership]. Cover: Why we're doing this (strategic context), What we're doing (scope in plain terms), Expected outcomes (quantified where possible), Resources required (budget + headcount), Timeline (key milestones), Risks (top 2 with mitigations), and Decision needed from leadership (specific ask). Under 400 words. Decision-ready format.
Build a Faster, Cleaner Operation
These 35 prompts handle the documentation and communication layer that slows every operations manager down. The real work — the judgment calls, the team coaching, the trade-off decisions — still requires you. These prompts just remove the blank page so you can get to what matters.
Want 50 more operations prompts? The Operations Manager AI Toolkit includes advanced prompts for lean process documentation, supply chain communication, operations analytics narratives, and building an ops leadership career. ($14.99, instant download.)
More professional ChatGPT prompt guides: financial analysts | consultants | data analysts
Top comments (0)