Prompt Library

AI Prompts for Operations & Workflows

25 ready-to-use prompts for workflow design, project planning, SOPs, risk management, and operational efficiency. Hartz AI designed these prompts from real consultancy engagements for UK operations teams. Copy, customise, and use with ChatGPT, Claude, or your preferred AI tool.

McKinsey research found that knowledge workers spend 60% of their time on coordination and communication rather than skilled work. The UK Government's Made Smarter Review identified AI-assisted process improvement as a priority for SME productivity growth. Hartz AI designed these prompts to help operations teams reclaim that lost time.

25 prompts6 categoriesIncludes SOP templates

Workflow Design Project Planning SOPs & Documentation Risk Management Operational Efficiency Quality & Standards

These 25 AI prompts cover workflow mapping, project planning, SOPs, risk management and operational efficiency. Each prompt is tested with ChatGPT, Claude and Gemini, with structured inputs that produce actionable outputs for UK operations teams.

60%

of knowledge worker time spent on coordination

McKinsey Global Institute

20-30%

productivity gains from AI workflow automation

UK Department for Business and Trade

60%

of UK SMEs lack a business continuity plan

Federation of Small Businesses

How to use these prompts

1Copy the prompt – Click the copy button on any prompt card.
2Fill in the [brackets] – Replace placeholder text with your specific details.
3Paste into your AI tool – Works with ChatGPT, Claude, Gemini, Copilot, and others.
4Refine the output – Ask follow-up questions to improve the response.

Workflow Design

Prompts for mapping, improving, and automating business processes.

Process mapping

Help me map out this business process:

Process name: [what you're documenting]
Purpose: [why this process exists]
Who's involved: [roles/people]
Trigger: [what starts the process]
End point: [what indicates completion]
Current pain points: [known issues]

Create a process map including:
1. Step-by-step workflow (numbered sequence)
2. Decision points and branches
3. Handoffs between people/teams
4. Time estimates for each step
5. Tools/systems used at each step
6. Potential bottlenecks identified
7. Suggested improvements

Keep it simple enough to follow but detailed enough to be useful.

Tip: Walk through the process with the people who actually do it before finalising.

Workflow improvement

Analyse this workflow and suggest improvements:

Current process:
[Describe or paste your current workflow steps]

Problems we're experiencing:
- [Issue 1]
- [Issue 2]
- [Issue 3]

Constraints:
- Budget: [available spend]
- Team capacity: [current workload]
- Systems: [tools we must keep using]

Provide:
1. Root cause analysis for each problem
2. Quick wins (implement this week)
3. Medium-term improvements (implement this quarter)
4. Longer-term optimisation opportunities
5. Estimated impact of each change
6. Implementation priority order

Focus on practical changes, not theoretical perfection.

Automation opportunities

Identify automation opportunities in my business:

Business type: [what you do]
Team size: [number of people]
Current tools: [software you use]
Repetitive tasks we do: [list manual work]
Time spent on admin: [estimate]
Technical capability: [low/medium/high]

Identify:
1. Tasks that could be fully automated
2. Tasks that could be partially automated
3. Recommended tools for each (including free options)
4. Estimated time savings per week
5. Implementation difficulty (easy/medium/hard)
6. Where to start (priority order)
7. What should stay manual and why

Be realistic about what a small team can implement.

Handoff process design

Design a handoff process between teams/roles:

Handoff description: [what's being handed over]
From: [role/team passing it on]
To: [role/team receiving it]
Current problems: [issues with handoffs]
Volume: [how often this happens]
Stakes: [what goes wrong if handoff fails]

Create:
1. Clear trigger point for handoff
2. Checklist of what must be included
3. Format/template for handoff documentation
4. Confirmation process (how receiver acknowledges)
5. Escalation path if something's missing
6. Quality check mechanism
7. Metrics to track handoff success

Make handoffs foolproof, not dependent on tribal knowledge.

Project Planning

Prompts for planning, tracking, and delivering projects successfully.

Project plan creation

Create a project plan for:

Project name: [what you're delivering]
Objective: [what success looks like]
Deadline: [target completion date]
Budget: [available resources]
Team: [who's involved and their availability]
Dependencies: [what needs to happen first]
Risks: [known concerns]

Create a project plan including:
1. Project scope (what's in, what's out)
2. Key milestones and dates
3. Work breakdown structure (phases and tasks)
4. Resource allocation
5. Dependencies mapped
6. Risk register with mitigations
7. Communication plan
8. Success criteria

Keep it practical for a small team to execute.

Tip: Build in buffer time. Projects almost always take longer than planned.

Project status report

Help me write a project status report:

Project: [name]
Reporting period: [dates]
Overall status: [on track/at risk/off track]

Progress this period:
- [What was completed]

Planned vs actual:
- [What was supposed to happen vs what did]

Blockers/issues:
- [Current problems]

Next period plan:
- [What's coming up]

Create a status report that:
1. Opens with a clear summary (green/amber/red)
2. Highlights key achievements
3. Honestly addresses issues without blame
4. Provides clear next steps
5. Identifies decisions needed from stakeholders
6. Is concise enough to read in 2 minutes

Write it so someone who hasn't been involved understands the situation.

Project kickoff agenda

Create a project kickoff meeting agenda:

Project: [name and brief description]
Duration: [meeting length]
Attendees: [who's invited]
Project timeline: [start to end]
Key stakeholders: [decision makers]

Create an agenda covering:
1. Welcome and introductions
2. Project background and objectives
3. Scope overview (what's included/excluded)
4. Roles and responsibilities
5. Timeline and key milestones
6. Communication approach
7. Risks and assumptions
8. Questions and discussion
9. Immediate next steps

Include timing for each section and suggested discussion questions.

Project retrospective

Facilitate a project retrospective:

Project: [name]
Duration: [how long it ran]
Outcome: [delivered/partial/failed]
Team involved: [who worked on it]
Budget performance: [under/on/over budget]
Timeline performance: [early/on time/late]

Create a retrospective structure:
1. Setting the scene (ground rules for honest discussion)
2. What went well (celebrate successes)
3. What didn't go well (without blame)
4. What we learned
5. What we'll do differently next time
6. Action items and owners

Include specific questions to prompt discussion in each section.

Resource planning

Help me plan resource allocation:

Projects/work to resource:
- [Project 1: brief description, deadline]
- [Project 2: brief description, deadline]
- [Add more as needed]

Available team:
- [Person 1: role, hours available, skills]
- [Person 2: role, hours available, skills]
- [Add more as needed]

Constraints:
- [Leave, holidays, other commitments]
- [Budget for contractors if available]

Create:
1. Skills matrix (who can do what)
2. Capacity overview (available hours vs required)
3. Recommended allocation by person/project
4. Gaps identified (skills or capacity)
5. Options to address gaps
6. Risk of overcommitment
7. Weekly view for next month

Be realistic about capacity. People aren't productive 100% of their time.

SOPs & Documentation

Prompts for creating standard operating procedures and process documentation.

Standard operating procedure

Create an SOP for:

Procedure name: [what task this covers]
Purpose: [why this SOP exists]
Who performs this: [role/team]
Frequency: [how often it's done]
Systems/tools used: [software, equipment]
Current method: [how it's done now, if documented]

Create an SOP including:
1. Purpose and scope
2. Roles and responsibilities
3. Prerequisites (what's needed before starting)
4. Step-by-step instructions (numbered, clear)
5. Screenshots/visuals placeholders where helpful
6. Common errors and how to avoid them
7. Troubleshooting guide
8. Quality check/verification steps
9. Related documents/SOPs
10. Version control and review date

Write for someone doing this for the first time.

Tip: Have someone unfamiliar with the process test your SOP before finalising.

Quick reference guide

Create a quick reference guide for:

Task: [what this covers]
Audience: [who will use this]
Skill level: [beginner/intermediate/advanced]
Format needed: [one-pager, checklist, flowchart]
Key scenarios: [common situations this covers]

Create a quick reference that:
1. Fits on one page (or screen)
2. Uses bullet points and clear headings
3. Includes a decision tree if relevant
4. Lists keyboard shortcuts or quick actions
5. Has a troubleshooting section
6. Provides contact for help

Make it scannable. People use reference guides when they're stuck.

Onboarding checklist

Create an onboarding checklist for a new team member:

Role: [job title]
Department: [team they're joining]
Start date context: [remote/office/hybrid]
Systems they'll need: [software, accounts]
Key relationships: [who they need to meet]
First week goals: [what they should achieve]
First month goals: [what success looks like]

Create a comprehensive checklist:

Before day 1 (for manager):
- [Setup tasks]

Day 1:
- [Welcome activities]

Week 1:
- [Essential training and introductions]

First 30 days:
- [Learning and integration milestones]

Include who's responsible for each item and how to verify completion.

Process documentation template

Create a template for documenting any business process:

Our context:
- Business size: [employees]
- Industry: [sector]
- Compliance requirements: [if any]
- Documentation maturity: [none/basic/advanced]

Create a reusable template that includes:
1. Standard header (process name, owner, version, dates)
2. Process overview section
3. Roles and responsibilities section
4. Step-by-step procedure section
5. Supporting information section
6. Change log section
7. Review and approval section

Include guidance on how to complete each section. Make it easy for anyone to document a process consistently.

Risk Management

Prompts for identifying, assessing, and mitigating operational risks.

Risk assessment

Conduct a risk assessment for:

Context: [project, process, or initiative]
Scope: [what we're assessing]
Timeframe: [period covered]
Stakeholders: [who's affected]
Known concerns: [risks already identified]

Create a risk assessment:
1. Risk identification (brainstorm all potential risks)
2. For each risk:
   - Description
   - Likelihood (low/medium/high)
   - Impact (low/medium/high)
   - Risk score (likelihood x impact)
   - Current controls in place
   - Additional mitigation needed
   - Risk owner
3. Risk matrix visualisation
4. Top 5 risks requiring immediate attention
5. Monitoring and review approach

Be thorough but practical. Include risks people don't like to talk about.

Tip: Review risks regularly, not just at project start. New risks emerge.

Business continuity plan

Create a business continuity plan for:

Business: [what you do]
Critical functions: [essential operations]
Key staff: [roles that can't be without]
Key systems: [technology dependencies]
Key suppliers: [critical third parties]
Previous disruptions: [past incidents if any]

Create a continuity plan covering:
1. Critical business functions (prioritised)
2. Recovery time objectives for each
3. Scenarios to plan for (IT failure, staff absence, premises access, supplier failure)
4. Response procedures for each scenario
5. Communication plan (internal and external)
6. Key contacts and alternates
7. Manual workarounds where possible
8. Testing and review schedule

Keep it usable in a crisis. If it's too complex, no one will follow it.

Incident response plan

Create an incident response plan for:

Type of incident: [data breach, system outage, safety incident, etc.]
Business context: [your organisation]
Regulatory requirements: [reporting obligations]
Current response process: [what happens now]
Past incidents: [previous experience]

Create an incident response plan:
1. Incident classification (severity levels)
2. Immediate response actions (first 15 minutes)
3. Escalation matrix (who to contact when)
4. Investigation process
5. Communication templates (internal, customer, regulatory)
6. Documentation requirements
7. Recovery and remediation steps
8. Post-incident review process
9. Lessons learned integration

Design for clarity under pressure. People don't read lengthy documents during a crisis.

Vendor risk assessment

Assess risk for this vendor/supplier:

Vendor name: [company]
Service provided: [what they do for us]
Criticality: [how important to operations]
Data shared: [what information they access]
Contract value: [annual spend]
Contract length: [term remaining]
Concerns: [any known issues]

Assess:
1. Operational risk (what if they fail to deliver)
2. Financial risk (what if they go out of business)
3. Security risk (data protection, cyber)
4. Compliance risk (regulatory implications)
5. Reputation risk (how their actions affect us)
6. Concentration risk (over-reliance)

For each risk area:
- Current risk level
- Existing controls
- Recommended additional controls
- Monitoring approach

Provide an overall risk rating and recommended actions.

Operational Efficiency

Prompts for improving productivity, reducing waste, and optimising operations.

Time audit

Help me analyse how time is spent in my team:

Team description: [roles and responsibilities]
Team size: [number of people]
Current pain points: [where time seems wasted]
High-value activities: [what we should spend more time on]
Low-value activities: [what feels like wasted effort]

Create a time audit framework:
1. Categories to track (meetings, admin, core work, etc.)
2. One-week tracking template
3. Analysis questions to answer
4. Common time traps to look for
5. Benchmarks for healthy time allocation
6. Quick wins to reclaim time
7. Structural changes to consider
8. How to maintain improvements

Make it simple enough that people will actually do it.

Tip: Track time for at least a week to get accurate data. One day isn't representative.

Meeting audit

Help me improve our meeting culture:

Current state:
- Average meetings per week per person: [estimate]
- Typical meeting length: [duration]
- Common meeting types: [list them]
- Known frustrations: [complaints]
- Tools used: [calendar, video, etc.]

Analyse and recommend:
1. Meeting audit criteria (which meetings add value)
2. Questions to evaluate each recurring meeting
3. Meeting hygiene standards to implement
4. Alternative formats to meetings
5. Rules for meeting-free time
6. Template for effective meetings (agenda, timing, follow-up)
7. How to decline meetings diplomatically
8. Metrics to track improvement

Be realistic. Some meetings are necessary. The goal is fewer, better meetings.

Bottleneck analysis

Help me identify and fix bottlenecks:

Process or area: [what's slowing down]
Symptoms: [how the bottleneck shows up]
Volume: [how much work flows through]
Timeline: [how long things take vs how long they should]
Previous attempts to fix: [what's been tried]

Analyse:
1. Where exactly is the bottleneck (pinpoint it)
2. Root causes (why does it exist)
3. Impact quantified (time/money/quality)
4. Short-term relief (what helps immediately)
5. Long-term solution (what fixes it properly)
6. Resources needed for the fix
7. How to prevent similar bottlenecks
8. Metrics to confirm it's resolved

Don't just move the bottleneck elsewhere. Actually solve it.

Capacity planning

Help me plan team capacity:

Team: [roles and people]
Current workload: [what they're doing now]
Upcoming demand: [expected work in next 3-6 months]
Seasonal patterns: [busy/quiet periods]
Growth plans: [business trajectory]
Hiring constraints: [budget, timeline]

Create a capacity plan:
1. Current capacity calculation
2. Demand forecast by month
3. Gap analysis (capacity vs demand)
4. Options to address gaps:
   - Efficiency improvements
   - Prioritisation/saying no
   - Temporary resources
   - Permanent hires
   - Outsourcing
5. Recommended approach
6. Contingency for demand spikes
7. Review and adjustment schedule

Plan for reality, not hope. Build in flex for the unexpected.

Quality & Standards

Prompts for maintaining quality, consistency, and continuous improvement.

Quality checklist

Create a quality checklist for:

Deliverable: [what's being checked]
Standards required: [expectations]
Common defects: [typical problems]
Who reviews: [role]
When reviewed: [point in process]
Consequences of errors: [why quality matters here]

Create a checklist that:
1. Lists all items to verify (be comprehensive)
2. Groups items logically
3. Specifies pass/fail criteria for each
4. Includes visual inspection where relevant
5. Has space for notes/comments
6. Requires sign-off
7. Tracks common issues for pattern analysis

Design it so checking is fast but thorough.

Tip: Keep checklists visible and easy to use. Hidden checklists don't get used.

Service level agreement

Draft an internal SLA for:

Service: [what's being provided]
Provider: [team/role providing it]
Customer: [team/role receiving it]
Current performance: [baseline if known]
Pain points: [current issues]
Business impact: [why performance matters]

Create an SLA including:
1. Services covered (scope)
2. Service levels and metrics:
   - Response time targets
   - Resolution time targets
   - Quality standards
   - Availability expectations
3. Measurement method
4. Reporting frequency
5. Escalation process
6. Review and improvement process
7. Exclusions and limitations

Make it fair and achievable. An SLA no one can meet builds resentment.

Continuous improvement framework

Create a continuous improvement framework for my team:

Team: [description]
Current maturity: [how much improvement work we do now]
Time available: [realistic capacity for improvement]
Previous initiatives: [what's worked or failed]
Culture: [receptiveness to change]

Design a framework:
1. How to capture improvement ideas (from anyone)
2. Prioritisation criteria
3. Small experiment approach (test before scaling)
4. Success metrics for improvements
5. Recognition for contributors
6. Regular improvement rhythm (daily/weekly/monthly)
7. Documentation of lessons learned
8. Leadership role in supporting improvement

Make it sustainable. Improvement should be normal, not a special event.

Error analysis

Analyse this error/failure to prevent recurrence:

What happened: [describe the incident]
When: [date/time]
Impact: [consequences]
Who was involved: [not for blame, for understanding]
Immediate cause: [what directly caused it]
How it was discovered: [detection method]
How it was resolved: [fix applied]

Conduct analysis:
1. Timeline of events
2. Root cause analysis (5 whys or similar)
3. Contributing factors
4. What controls should have prevented this
5. Why those controls failed
6. Systemic issues revealed
7. Recommended preventive actions
8. How to verify the fix works

Focus on systems and processes, not blaming individuals.

Unlock 21 more prompts

You're viewing 4 of 25 Operations & Delivery prompts. Enter your email to unlock the full library - free, instant access.

Frequently asked questions

Do I need technical knowledge to use these operations prompts?

No. Every prompt is written in plain English with bracketed placeholders you fill in with your specific context. Copy the prompt into ChatGPT, Claude or Gemini, replace the placeholders, and you will receive structured, actionable output immediately. No coding or prompt engineering knowledge required.

Which AI tools work with these prompts?

All prompts work with ChatGPT (free or Plus), Google Gemini, Anthropic Claude and Microsoft Copilot. The prompts use natural language, so they transfer across any large language model without modification.

Can I adapt these prompts for my specific industry?

Yes. Each prompt includes placeholder sections you customise for your sector, team structure and operational context. For fully tailored prompt libraries matched to your internal processes, Hartz AI offers bespoke prompt library development as part of our AI training programmes.

How are these operations prompts different from generic ChatGPT prompts?

These prompts are designed by operations consultants who understand UK business contexts. Each prompt includes structured inputs, specific output requirements and practical tips - producing results that are immediately usable rather than requiring extensive refinement.

Explore other prompt libraries

Find prompts for other business functions.

Business & Strategy Marketing & Growth People & HR Sales & Relationships Market Research

Want prompts tailored to your operations?

We create custom prompt libraries for organisations, designed around your specific processes, systems, and workflows.

Book Discovery Call View AI Training