Operations management is the job that makes everything else possible and gets credit for nothing. When logistics runs smoothly, when the warehouse hits its throughput, when the SOP gets followed, nobody notices. When it breaks, everyone knows who to call.
The documentation load is staggering. Process documentation, vendor contracts, KPI dashboards, staff schedules, escalation procedures, shift handover notes, budget variance reports — all of it needs to be written, maintained, and communicated to people who have other things to do.
ChatGPT doesn't optimize your operations. It won't know your throughput constraints, your team's actual capabilities, or the supplier relationship you've been managing for 8 years. But it eliminates the blank-document problem for every deliverable that should take 30 minutes but currently takes 3 hours.
These 35 prompts are fill-in-the-bracket templates. Replace the bracketed sections with your operation's specifics and get a working draft in under 60 seconds.
1. Process Documentation and Standard Operating Procedures
SOPs only work if someone actually reads them. These prompts help you write documentation people use.
Prompt 1 — Standard operating procedure draft:
You are an experienced operations manager. Write a standard operating procedure (SOP) for [PROCESS NAME] at a [COMPANY TYPE/SIZE]. The process involves: [DESCRIBE — who does it, what they do, what systems they use, what the output is]. The audience is [EXPERIENCE LEVEL — e.g., new hires with no prior experience, trained staff needing a reference, seasonal employees]. Format: numbered steps with a one-sentence description per step, a materials/access required section at the top, a definition of done, and a troubleshooting section for the 3 most common errors. Keep instructions at a 6th-grade reading level.
Prompt 2 — Process map narrative description:
Write a narrative description of the following process for inclusion in an operations manual: [PROCESS NAME]. Process flow: [DESCRIBE START TO END — or paste a list of steps]. Include: the trigger that starts the process, each major step with the responsible role, any decision points and what determines which path is taken, the handoff between departments or roles, the definition of completion, and any compliance or safety checkpoints. Under 400 words. Write for an operator who needs to understand the whole process, not just their step.
Prompt 3 — SOP revision and gap analysis:
I have an existing SOP for [PROCESS] that was written [TIME AGO]. The process has changed because [DESCRIBE CHANGE — new system, regulatory update, workflow redesign, recurring errors]. Current SOP: [PASTE OR DESCRIBE]. Help me: identify the gaps between the current SOP and how the process actually runs now, flag any steps that are unclear or missing error handling, and produce a revised version with tracked changes clearly noted. Preserve what's still accurate.
Prompt 4 — Work instruction for a specific task:
Write a step-by-step work instruction for [SPECIFIC TASK — e.g., opening the facility, running end-of-day cash reconciliation, completing a quality check, operating a specific piece of equipment]. Audience: a new employee with [BACKGROUND — e.g., basic computer skills, no prior industry experience]. Each step should include: the action, why it matters (brief), and what to do if something goes wrong. Include warnings for steps with safety or compliance implications. Format for lamination or tablet display — short, visual-friendly, unambiguous.
Prompt 5 — Process improvement proposal:
I want to propose a process improvement for [CURRENT PROCESS]. Current state: [DESCRIBE HOW IT WORKS NOW — include the pain points, time estimates, error rates if known]. Proposed change: [DESCRIBE WHAT YOU WANT TO DO DIFFERENTLY]. Write a process improvement proposal that covers: the current problem (quantified if possible), the proposed solution, expected benefits (time saved, errors reduced, cost impact), implementation requirements (people, systems, training needed), risks and how to mitigate them, and a 30/60/90-day rollout plan. Format for a manager or director audience.
2. Team Scheduling and Workforce Planning
Scheduling is where operations management becomes math + politics. These prompts handle both.
Prompt 6 — Shift schedule template:
Create a weekly shift schedule template for a [TYPE OF OPERATION — e.g., retail store, manufacturing floor, call center, warehouse, healthcare clinic] with the following constraints: operational hours [HOURS/DAYS], minimum staffing requirements per shift [DESCRIBE — e.g., 2 floor staff + 1 supervisor on day shift, 1 staff on overnight], total headcount available [NUMBER], any fixed constraints [e.g., X employee can't open, Y is part-time only on weekends]. Format as a weekly grid. Flag any coverage gaps and suggest how to address them.
Prompt 7 — Overtime and coverage gap communication:
Write an internal communication to [AUDIENCE — team, department, specific shift] about a staffing situation: [DESCRIBE — e.g., unexpected absences next week, higher-than-normal volume requiring overtime, a new schedule change due to expanded hours]. The communication should: explain the situation factually, state what's needed from the team (specific ask — volunteer for overtime, confirm availability, accept a schedule change), acknowledge the inconvenience honestly, and explain what the company is doing to address the root cause. Professional, not guilt-tripping.
Prompt 8 — Headcount justification for seasonal or peak demand:
Write a headcount justification memo for [NUMBER] additional [TEMPORARY/PERMANENT] staff for [TIME PERIOD — e.g., Q4 holiday season, summer peak, a specific project]. Current capacity: [HEADCOUNT AND THROUGHPUT]. Projected demand: [VOLUME INCREASE — specific numbers]. Impact of not hiring: [DESCRIBE — missed orders, customer complaints, overtime costs, quality decline]. Cost of hiring vs. cost of not hiring: [ESTIMATE IF POSSIBLE]. Audience: [GM, CFO, HR DIRECTOR]. Under 300 words. Make the business case, not just the operational case.
Prompt 9 — Absence and coverage policy summary:
Write a practical summary of our absence and coverage policy for [TYPE OF OPERATION] staff. Policy key points: [DESCRIBE — call-out notification time, how to find your own coverage vs. manager finds it, points system, disciplinary thresholds, etc.]. Write this as a one-page employee reference that: is honest about expectations (no watering down), explains the why behind key rules, provides specific steps for the most common absence scenarios, and answers the 5 most common questions employees ask about calling out.
Prompt 10 — Workforce planning for a new location or expansion:
Help me develop a workforce plan for [NEW LOCATION / EXPANSION / NEW SERVICE]. Opening date: [TARGET]. Operation size: [DESCRIBE — sq ft, volume, service type]. Staffing needed at launch: [ESTIMATE — roles and quantities]. Recruiting timeline working backwards from opening: [I'll fill in, suggest what lead times to assume]. Training requirements: [DESCRIBE OR ESTIMATE]. Write a workforce planning timeline that covers: when to post positions, when to start training, ramp-up assumptions, and what could go wrong with the plan (hiring slower than expected, training taking longer, etc.).
3. KPI Tracking and Performance Reporting
Operations data tells the story. These prompts help you communicate what the numbers mean and what to do about them.
Prompt 11 — Weekly operations report:
Write a weekly operations report for [WEEK OF DATE] for [OPERATION TYPE]. Audience: [MANAGEMENT, LEADERSHIP, OR CROSS-FUNCTIONAL TEAM]. Include: key metrics summary (use placeholders like [METRIC: X vs. TARGET Y] that I'll fill in), narrative on any metrics that missed target (what happened, root cause, corrective action), operational highlights and wins, issues or risks that need leadership attention, and next week's priorities. Under 400 words. Lead with the most important information — don't bury problems.
Prompt 12 — KPI dashboard design:
Design a weekly KPI dashboard for [OPERATION TYPE — e.g., warehouse, customer service center, production floor, multi-location retail]. The dashboard should track: [LIST THE 8–12 MOST IMPORTANT METRICS FOR YOUR OPERATION — or ask me to suggest them for your operation type]. For each metric: the name, definition (exactly how it's calculated), frequency of measurement, owner responsible for the data, and the target/threshold (green/yellow/red). Format as a dashboard spec I can use to build in [TOOL — Excel, Google Sheets, Power BI, etc.].
Prompt 13 — Root cause analysis for a recurring operational problem:
Help me conduct a root cause analysis for a recurring operational problem: [DESCRIBE — e.g., shipping errors occurring at 3x baseline, customer complaints about wait time, inventory count discrepancies, safety incidents in a specific area]. Problem frequency: [HOW OFTEN]. Data available: [WHAT I KNOW — specific error types, when/where they occur, which staff are involved, systems involved]. Use the 5-Why method to work through the most likely root cause. Then suggest: 2–3 possible root causes, what additional data would confirm the true root cause, and one corrective action for the most likely cause.
Prompt 14 — Performance variance explanation for leadership:
Write an explanation of an operations performance variance for a leadership audience that doesn't have operational visibility. We missed [METRIC NAME] this [PERIOD] by [AMOUNT/PERCENTAGE]. Target: [X]. Actual: [Y]. Explanation: [DESCRIBE THE CAUSES — staffing, equipment, volume spike, supplier issue, etc.]. Write a memo that: leads with the key number, explains the causes clearly without making excuses, describes what actions are in place to recover, and projects when we expect to return to target. Under 250 words. Factual and accountable.
Prompt 15 — Quarterly business review (QBR) operations summary:
Write the operations section of a quarterly business review for [QUARTER/YEAR]. Audience: senior leadership and cross-functional partners. Include: performance against key operational metrics (I'll insert the numbers — [METRIC: TARGET vs. ACTUAL]), top 3 operational achievements of the quarter, top 3 challenges and how they were addressed (or are being addressed), key investments or changes made, and operational priorities for next quarter. Frame in terms of business impact, not just operational activity. Under 500 words.
4. Vendor and Supplier Management
Supply chain and vendor relationships are high-stakes. These prompts manage the communication and documentation layer.
Prompt 16 — Vendor performance review:
Write a vendor performance review for [VENDOR NAME], providing [PRODUCT/SERVICE], review period [QUARTER/DATES]. Performance data:
- On-time delivery/service rate: [X%] vs. [CONTRACT SLA%]
- Quality defect/error rate: [X%] vs. [TARGET]
- Invoice accuracy: [X%]
- Open issues older than SLA: [NUMBER]
- Notable incidents: [LIST]
Write: a performance summary paragraph, whether vendor is in compliance, what improvement is required, and whether we recommend contract renewal, renegotiation, or competitive rebid.
Prompt 17 — Supplier issue escalation:
Write an escalation email to a supplier regarding [ISSUE — e.g., late shipments for 3 consecutive orders, quality failure batch, invoice disputes, capacity reduction notice]. Issue details: [DESCRIBE: what happened, business impact, what we've already communicated at the account level, what they've promised and haven't delivered]. This email goes to [ESCALATION CONTACT — account director, VP, regional manager]. Include: clear description of the issue and impact, specific resolution required, timeline expected, and statement of what we will do if not resolved (e.g., source elsewhere, contract remedy). Firm but professional.
Prompt 18 — Request for proposal (RFP) outline:
Create an outline for an RFP for [SERVICE/PRODUCT TYPE]. We need proposals from vendors to [DESCRIBE WHAT WE NEED — e.g., provide 3PL warehousing, supply raw materials for manufacturing, manage our fleet, provide facility maintenance services]. Key requirements: [LIST — volume, geography, service level expectations, compliance requirements]. The RFP outline should include: company and project overview, scope of work, technical and operational requirements, compliance and insurance requirements, pricing format instructions, evaluation criteria and weighting, and submission instructions with deadline.
Prompt 19 — Vendor contract amendment request:
Write a formal request to amend a vendor contract for [VENDOR NAME], current contract [REFERENCE NUMBER OR DATE]. Change requested: [DESCRIBE AMENDMENT — e.g., price adjustment, service level change, volume commitment revision, payment terms, territory expansion]. Reason for the change: [EXPLAIN]. Business impact if not amended: [DESCRIBE]. Proposed effective date: [DATE]. Tone: collaborative and professional — this is a negotiation request, not a demand. End with a specific next step (proposed meeting, conference call, or written response).
Prompt 20 — Supplier diversity and qualification checklist:
Create a supplier qualification checklist for [PRODUCT/SERVICE CATEGORY]. The checklist should cover: financial stability indicators, operational capacity verification, quality management system (certifications, audit history), regulatory and compliance requirements [LIST RELEVANT ONES — e.g., food safety, environmental, labor], insurance requirements, references and customer performance history, pricing and payment terms structure, and ESG/supplier diversity criteria if applicable. Format as an evaluator worksheet with a scoring guide and a go/no-go recommendation threshold.
5. Incident Management and Problem Solving
When things go wrong in operations, speed and clarity save money and relationships. These prompts help you respond fast.
Prompt 21 — Operational incident report:
Write an operational incident report for [INCIDENT NAME/DATE]. Incident type: [DESCRIBE — e.g., safety incident, equipment failure, quality escape, shipment error, customer complaint]. What happened: [DESCRIBE — timeline, what failed, who was involved]. Immediate response: [WHAT WAS DONE]. Business impact: [QUANTIFY IF POSSIBLE — cost, delay, customer impact]. Root cause (preliminary): [DESCRIBE]. Corrective actions: [LIST WITH OWNERS AND DEADLINES]. Preventive actions: [LIST]. Format as a formal incident report for operations leadership and [SAFETY/QUALITY/COMPLIANCE] records.
Prompt 22 — Customer complaint response (operations context):
Write a customer complaint response for [COMPLAINT TYPE — e.g., late delivery, damaged goods, wrong item shipped, service failure]. Customer: [COMPANY NAME or CUSTOMER TYPE]. Complaint details: [DESCRIBE WHAT HAPPENED AND WHAT THEY SAID]. Our fault assessment: [OUR FAULT / SHARED / NOT OUR FAULT — explain]. Resolution offered: [REPLACEMENT, REFUND, DISCOUNT, CREDIT, EXPEDITE, EXPLANATION ONLY]. Tone: accountable for what we did wrong, clear about what we're doing to fix it, professional about what we aren't offering. Don't over-apologize. Don't make promises you can't keep.
Prompt 23 — Business continuity response plan:
Create a business continuity response checklist for [DISRUPTION TYPE — e.g., key supplier failure, facility outage, major equipment breakdown, severe weather, critical staff departure]. Operation affected: [DESCRIBE]. Write a response checklist covering: immediate assessment steps (first 2 hours), communication notifications (who to tell and when), short-term continuity options (workarounds, alternative sources, capacity shifting), escalation decision points (when to invoke formal BCP), and recovery milestones (how we'll know we're back to normal). Format for use under pressure — numbered steps, no paragraphs.
Prompt 24 — Safety incident investigation summary:
Write a safety incident investigation summary for [INCIDENT DATE/TYPE]. This summary is for [AUDIENCE — operations team, OSHA recordkeeping, leadership, insurance]. Incident description: [WHAT HAPPENED, WHERE, WHO WAS INVOLVED]. Severity: [DESCRIBE — near miss, first aid, recordable, lost time]. Root cause findings: [DESCRIBE — using 5-Why or contributing factors]. Contributing factors: [LIST]. Corrective actions required: [LIST WITH OWNERS, DUE DATES, AND STATUS]. Communication to team: [WHAT WAS SHARED]. Note any information that should not be included in general communication for legal reasons — flag and I'll review.
Prompt 25 — Escalation decision framework:
Create an operational escalation decision framework for [OPERATION TYPE]. The framework should guide front-line staff and supervisors on when and how to escalate issues. Include: decision criteria for escalating vs. handling at the local level, escalation tiers (tier 1: supervisor, tier 2: manager, tier 3: director/executive) with triggers for each, communication protocol (how to escalate — what information to include, which channel to use, how fast), authority levels at each tier (what decisions each tier can make), and a reference card for the 10 most common operational issues and the correct escalation path for each.
6. Budget Management and Cost Control
Operations budgets are managed in detail and explained in summary. These prompts bridge both.
Prompt 26 — Operations budget variance analysis:
Write a budget variance analysis for [PERIOD] for [OPERATION/DEPARTMENT]. Budget data:
[PASTE LINES OR DESCRIBE: line item, budget, actual, variance $, variance %]
For the top 3 positive and negative variances: explain the cause (one-time event, run-rate change, volume-driven, error, etc.), whether the variance will recur, and what action (if any) is being taken. Close with an updated full-year forecast outlook and whether we expect to end the year on budget. Audience: CFO/finance partner and operations leadership.
Prompt 27 — Capital expenditure request:
Write a capital expenditure request for [EQUIPMENT/ASSET/PROJECT]. Cost: $[AMOUNT]. What we're buying: [DESCRIBE]. Business justification: [WHY — capacity, efficiency, safety, compliance, replacement of failing asset]. Current state without this investment: [DESCRIBE RISK/COST OF NOT BUYING]. ROI calculation: [DESCRIBE — payback period, cost savings, revenue enablement, risk reduction value]. Implementation plan: [BRIEF — timeline, who installs/manages, training needed]. Alternatives considered: [LIST AND WHY REJECTED]. Format for a capital expenditure approval committee.
Prompt 28 — Cost reduction initiative proposal:
Write a cost reduction initiative proposal for [OPERATIONS AREA — e.g., logistics costs, facility overhead, labor efficiency, waste reduction, energy consumption]. Current spend: $[AMOUNT/PERIOD]. Reduction target: [$ OR %]. Proposed initiatives: [LIST 3–5 INITIATIVES — describe each one]. For each initiative: estimated savings, implementation cost/effort, timeline to realize savings, and risks. Prioritize by net benefit. Include a 90-day quick-win plan and a 6-month roadmap. Audience: operations leadership and finance.
Prompt 29 — Vendor cost renegotiation prep:
Help me prepare for a cost renegotiation with [VENDOR NAME] for [SERVICE/PRODUCT]. Current contract: $[AMOUNT/PERIOD]. Our goal: reduce by [TARGET — % or $] at the next renewal [DATE]. Prepare me with: the business case for a reduction (market data, volume leverage, competitive alternatives), the specific asks to make (price reduction, improved terms, value-adds instead of price cut, volume-tiered pricing), our walk-away position and BATNA (best alternative to negotiation agreement), and the negotiation sequence — what to ask for first and how to respond to pushback.
Prompt 30 — Make vs. buy analysis:
Help me conduct a make vs. buy analysis for [ACTIVITY/PRODUCT/SERVICE — e.g., manufacturing a component in-house vs. outsourcing, providing internal IT support vs. managed services, operating our own fleet vs. 3PL]. Make option costs: [LIST — capital, labor, overhead, management time]. Buy option costs: [LIST — vendor pricing, management overhead, transition cost, dependency risk]. Strategic considerations: [CORE COMPETENCY? QUALITY CONTROL? SPEED TO SCALE? IP SENSITIVITY?]. Format as a comparison framework with a recommended decision and the 2–3 factors that most strongly drive the recommendation.
7. Cross-Functional Communication
Operations managers communicate up, down, and sideways. These prompts handle the translation work.
Prompt 31 — Operations-to-sales communication about capacity or lead times:
Write a communication to the sales team about [CAPACITY CONSTRAINT / LEAD TIME CHANGE / AVAILABILITY ISSUE]. What's changed: [DESCRIBE — e.g., lead times increased by X weeks, product Y is temporarily constrained, we can't commit to orders over X units until Q2]. Reason: [BRIEF EXPLANATION — supplier, equipment, demand spike]. What sales can tell customers: [SPECIFIC LANGUAGE THEY CAN USE]. What sales should NOT promise: [SPECIFIC — be clear]. Who to contact for exceptions: [NAME/CHANNEL]. Deadline for any in-flight commitments that need review: [DATE]. Professional, clear, not alarming.
Prompt 32 — New process rollout communication:
Write a communication to [AUDIENCE — floor team, all staff, department managers] announcing the rollout of [NEW PROCESS/SYSTEM/POLICY]. What's changing: [DESCRIBE THE CHANGE]. Why: [EXPLAIN THE REASON — be honest if it's fixing a problem]. Effective date: [DATE]. What they need to do: [SPECIFIC ACTION ITEMS AND TIMELINE]. Training or support available: [DESCRIBE]. Who to contact with questions: [NAME/CHANNEL]. Tone: clear and direct, not bureaucratic. Acknowledge if this is a change that affects their daily routine.
Prompt 33 — Operations update for executive leadership:
Write a monthly operations executive summary for [MONTH] for [OPERATION TYPE]. Audience: CEO, COO, or board. Maximum 1 page. Cover: the most important operational metric and whether we're on track, one operational win to highlight, one operational risk or concern requiring leadership attention, and the top priority for next month. No operational jargon. Write as if the reader has 3 minutes and no operational context. Every sentence should answer "why does this matter to the business?"
Prompt 34 — Cross-departmental issue resolution email:
Write an email to [DEPARTMENT/TEAM] to address a recurring operational issue that crosses department lines: [DESCRIBE ISSUE — e.g., sales is committing to lead times operations can't meet, finance is requiring approvals that slow operations below our SLA, IT changes are deployed without operational impact review]. This is a peer-level communication — I don't manage them. Tone: collaborative problem-solving, not blame. Include: description of the impact on operations, request for a specific change to their process, proposal for a joint solution or conversation, and a specific next step.
Prompt 35 — Shift handover report template:
Create a shift handover report template for [OPERATION TYPE — e.g., manufacturing plant, retail store, call center, logistics hub, healthcare facility]. The report should ensure the incoming shift has everything they need to start without briefing calls when possible. Sections: shift summary (volume, throughput, key metrics), open issues and status (what's being watched, who owns it), equipment or system status (anything out of normal operating condition), staffing notes (absences, on-call coverage, new starters), compliance actions completed (safety checks, opening/closing procedures completed), and priority items for the incoming shift. Each section under 5 bullet points.
Get 35 More Prompts — Advanced Operations Management Scenarios
These 35 prompts cover core operations management workflows. The full pack adds 35 more for advanced scenarios: supply chain resilience planning, multi-site operations, lean/Six Sigma project management, operations technology implementation, and enterprise operations strategy.
Get the full 70-prompt Operations Manager ChatGPT Pack →
Use LAUNCH30 for 30% off — limited uses remaining.
Every prompt is editable. Works with ChatGPT-4, Claude, and Gemini.
Top comments (0)