Who is this prompt pack for?

Operations managers, COOs, supply-chain leads, and anyone who writes SOPs, runs incident reviews, or manages suppliers. The prompts turn routine ops documentation into a fill-in-the-blank exercise instead of a blank page.

Will the SOPs and reports be accurate?

The AI gives you a strong structure and draft, but you must verify the specifics. Operations documents often carry safety, compliance, or financial weight, so a human owner should review every prompt's output before it becomes official.

Which AI tools do these work with?

All of them. The prompts are plain text and model-agnostic, so they work in ChatGPT, Claude, Gemini, or Copilot. Output quality depends mostly on how specifically you fill in the bracketed variables.

Can I use the supplier emails as-is?

Treat them as a first draft. Add your real numbers, order history, and relationship context before sending. Negotiation copy lands better when it references specifics the supplier recognises.

Is anything I type stored?

No. This pack runs entirely in your browser. You copy a prompt to your clipboard and run it elsewhere — nothing you type into the search box passes through this page.

Operations Prompt Pack

Operations work runs on documents nobody enjoys writing — SOPs, process maps, incident reports, supplier emails, KPI definitions. This pack gives you tested prompt templates for the ops tasks you repeat every week, each with fill-in-the-blank variables so you start from structure instead of a blank page.

How it works

Every prompt names the deliverable, the context (your process, industry, supplier), and the format you want back. The bracketed variables — [process name], [industry], [supplier] — are the levers that decide whether you get a generic template or a document your team can actually use. Filter by category or search, replace the brackets, copy, and paste into your AI tool.

Tips for better output

Paste the real process. For bottleneck and waste analysis, paste your actual numbered steps — the AI can only spot waste it can see.
Give it your house style. Drop in one of your existing SOPs and ask the model to match the format, headings, and tone before generating a new one.
Demand specifics in incident reports. Replace vague phrases with times, quantities, and named roles so the post-mortem produces actionable corrective items, not platitudes.
Always review before it’s official. Ops documents carry safety, compliance, and cost consequences. AI drafts fast but a human owner must verify every detail before sign-off.