AI Prompts for Operations Managers: 11 Copy-Ready Templates

You are an operations manager at [COMPANY]. Here are my rough notes on how we [PROCESS]:

[PASTE NOTES OR TRANSCRIPT]

Write a one-page SOP: purpose, when it applies, who does it, the steps in order, what "done" looks like and what to do when something goes wrong. Number the steps and start each with a verb. Where my notes skip a step or an owner, write "Missing: confirm" instead of filling it in.

Format: headed sections, steps under 20 words each.

Act as a process improvement lead. Here is how [PROCESS] works today, in my words:

[PASTE DESCRIPTION]

List the steps in order with who does each and what triggers the next one. Then point out handoffs, waits, rework loops and steps that need the same data typed twice. Suggest up to three improvements and what each would need.

Format: a numbered step table (Step, Owner, Trigger), then Bottlenecks and Improvements as bullets.

You are making a working checklist for [ROLE] from this SOP:

[PASTE SOP]

Keep only the actions someone must tick off while doing the work, in order, with any check value or limit from the SOP (such as a dollar threshold or a time). Do not add steps that are not in the SOP.

Format: a check-box list that fits on one page, with a sign-off line at the bottom.

You are the operations manager at [COMPANY]. Here are this week's numbers and notes from each team lead:

[PASTE METRICS AND NOTES]

Write the weekly review: what is on track, what slipped and why (from the notes only), the decisions needed, and an action list where every task has an owner and a due date, or "Owner needed" if none was named.

Format: four headed sections, then an Actions table (Action, Owner, Due).

Act as an operations manager writing an incident report. What happened: [DESCRIPTION]. When and where: [TIME AND PLACE]. Who was involved (by role): [ROLES]. Impact: [IMPACT]. Immediate actions taken: [ACTIONS].

Write a factual report with a timeline, the impact, the likely cause as described by the people involved (labeled as their account), and corrective actions with owners. Do not assign blame or state a root cause that is not supported by the facts.

Format: headed sections with a timeline table.

You are reviewing [VENDOR] for the [PERIOD] contract review. Our expectations: [SLA OR CONTRACT TERMS]. What happened: [DELIVERY DATES, ISSUES, TICKETS, COSTS].

Write a balanced review that compares results to each expectation, lists the issues with dates, notes what went well and proposes three discussion points for the review meeting.

Format: a scorecard table (Expectation, Result, Met or Not met), then notes and discussion points.

You are the operations manager at [COMPANY] and need quotes for [PRODUCT OR SERVICE]. Requirements: [QUANTITY, SPECS, DELIVERY DATE, LOCATION]. Quotes are due by [DATE].

Write a request-for-quote email that lists the requirements clearly, asks for price, lead time, payment terms and warranty in a consistent format, and names a contact for questions: [CONTACT].

Format: a subject line, a short intro, a numbered requirements list and a "Please include" list.

Act as an operations manager. Order [PO NUMBER] from [VENDOR] for [ITEMS] was due on [DUE DATE] and has not arrived. Impact on us: [IMPACT].

Write a firm, polite follow-up that asks for a confirmed delivery date and tracking by [RESPONSE DEADLINE], and asks what they can do to make up the delay. Do not threaten anything our contract does not allow.

Format: under 120 words.

You are an operations analyst. Here are the recurring tasks my team does, with rough frequency and time per task:

[PASTE TASKS]

Rank the tasks by how good a fit they are for automation: repetitive, rule-based, digital input, and low risk if a step fails. For each top candidate, describe what an automation would do in plain words and what a person should still check.

Format: a ranked table (Task, Fit, Why, Human check). Use only the times I gave; do not estimate savings.

Act as an operations manager. Requests arrive by [CHANNEL] and need to go to the right person. The types of requests and who handles them: [TYPES AND OWNERS]. Urgent means: [URGENT RULE].

Write the routing rules as simple if-then statements a person or an automation could follow, plus a catch-all rule for anything that does not match. Point out any overlap where one request could match two rules.

Format: a numbered list of rules, then Overlaps.

You are helping [NAME] hand off their work while they are away from [START DATE] to [END DATE]. Here is what they handle:

[PASTE TASKS, CONTACTS, DEADLINES]

Write a coverage handoff: what needs doing each day or week, what can wait, who covers what, key contacts and where to find files. Flag anything with a deadline during the absence.

Format: a coverage table (Task, Frequency, Covered by, Notes), then Deadlines during absence.