DEV Community

Nav
Nav

Posted on • Originally published at promptzy.app

The 30 Best AI Prompts for Operations & Project Managers

#ai #productivity #projectmanagement #prompts

If you run operations or manage projects, you're spending a lot of time on things that should take minutes. Status reports. Risk summaries. Meeting agendas. Escalation emails. The work behind the work.

AI prompts for project managers can cut that overhead dramatically — but only if the prompts are actually built for how ops and PM work functions. Generic "summarize this" prompts don't cut it when you need a structured risk log or a vendor scorecard that your stakeholders will actually read.

This is a list of 30 AI prompts built specifically for operations and project managers. Copy them directly, or save them in Promptzy so you can fire any one of them with a keyboard shortcut.

Status Reports & Updates

1. Weekly status report from bullet points

Write a professional weekly project status report. Project: [PROJECT NAME]. RAG status: [RED/AMBER/GREEN]. Key updates this week: [BULLET POINTS]. Blockers: [LIST]. Next week priorities: [LIST]. Keep it under 300 words. Use a clear structure with headers.
Enter fullscreen mode Exit fullscreen mode

2. Executive summary for stakeholders

Summarize the following project update into a 5-sentence executive summary for senior stakeholders who want the headline, not the detail. Focus on: current status, any risks, key decisions needed. Update: [PASTE UPDATE]
Enter fullscreen mode Exit fullscreen mode

3. Turn messy notes into a formal status update

I have rough meeting notes and want to turn them into a clean stakeholder update email. Clean up the language, organize into: progress, risks, actions, next steps. Notes: [PASTE NOTES]
Enter fullscreen mode Exit fullscreen mode

4. Red status escalation message

Write a professional escalation email for a project that has just moved to RED status. Project: [NAME]. Core issue: [DESCRIBE]. Impact if unresolved: [IMPACT]. What I need from leadership: [WHAT YOU NEED]. Tone: direct, factual, no blame.
Enter fullscreen mode Exit fullscreen mode

5. Sprint retrospective summary

Write a sprint retrospective summary from these team inputs. Format: What went well, what didn't, what we're changing. Keep each section to 3 bullet points max. Inputs: [PASTE RAW NOTES]
Enter fullscreen mode Exit fullscreen mode

Risk Management

6. Risk log entry

Write a risk log entry for the following risk: [DESCRIBE RISK]. Include: risk description, likelihood (High/Medium/Low), impact (High/Medium/Low), risk owner, mitigation actions (3 bullet points), contingency plan. Format as a table row I can paste into a spreadsheet.
Enter fullscreen mode Exit fullscreen mode

7. Risk assessment from project description

I'm starting a new project: [DESCRIBE PROJECT]. Identify the top 5 risks I should log immediately. For each risk: name it, rate likelihood and impact, suggest one mitigation action. Be specific to my project context, not generic.
Enter fullscreen mode Exit fullscreen mode

8. Risk update for steering committee

I need to present our top project risks to a steering committee. Here are the risks: [LIST RISKS AND STATUS]. Write a 3-paragraph narrative that explains the risk landscape, what we're doing about it, and what decisions the committee needs to make.
Enter fullscreen mode Exit fullscreen mode

9. Issue escalation vs. risk differentiation

Help me categorize these items as either active issues (already affecting the project) or risks (potential future problems): [LIST ITEMS]. For each, tell me how to log it and what immediate action to take.
Enter fullscreen mode Exit fullscreen mode

Meeting Agendas & Facilitation

10. Kick-off meeting agenda

Write a 60-minute project kick-off meeting agenda for: [PROJECT NAME AND BRIEF DESCRIPTION]. Attendees: [LIST ROLES]. Include: introductions, project overview, scope, roles & responsibilities, timeline, risks, open Q&A. Add time allocations and the goal for each section.
Enter fullscreen mode Exit fullscreen mode

11. Retrospective facilitation guide

Create a 45-minute retrospective facilitation guide for a team of [NUMBER] people. Use the Start/Stop/Continue format. Include: opening warm-up activity, time allocations, exact facilitator prompts to use, and how to close with clear action items.
Enter fullscreen mode Exit fullscreen mode

12. Recurring standup format

Write a standup meeting format for a [NUMBER]-person ops team. Each person has 2 minutes. The format should surface blockers fast and stay under [TOTAL MINUTES] total. Include the exact 3 questions each person answers.
Enter fullscreen mode Exit fullscreen mode

13. Meeting notes to action items

I have raw meeting notes. Extract all action items and format them as a table with: Action, Owner, Due Date, Priority (H/M/L). Notes: [PASTE NOTES]. If owner or due date isn't mentioned, flag it as TBD.
Enter fullscreen mode Exit fullscreen mode

14. Steering committee deck outline

Create a steering committee presentation outline for project [NAME] at [MILESTONE/STAGE]. The committee wants: status summary, financials, risks, decisions needed, and next steps. Give me a slide-by-slide outline with 2-3 bullet points per slide.
Enter fullscreen mode Exit fullscreen mode

SOPs & Documentation

15. Standard operating procedure template

Write a standard operating procedure (SOP) for the following process: [DESCRIBE PROCESS]. Include: purpose, scope, roles and responsibilities, step-by-step procedure, exceptions, revision history table. Tone: clear, direct, no unnecessary jargon.
Enter fullscreen mode Exit fullscreen mode

16. Process documentation from brain dump

I'm going to describe a process in rough terms. Turn it into a clean, numbered SOP that a new team member could follow without asking questions. My description: [PASTE DESCRIPTION]
Enter fullscreen mode Exit fullscreen mode

17. Runbook for recurring operations task

Create a runbook for: [TASK OR PROCESS NAME]. This is a recurring task done by [ROLE]. Include: trigger/when to run this, prerequisites, step-by-step instructions with commands or system steps where relevant, common errors and how to handle them.
Enter fullscreen mode Exit fullscreen mode

18. RACI matrix from project description

Build a RACI matrix for a [PROJECT TYPE] project. Roles involved: [LIST ROLES]. Key workstreams: [LIST WORKSTREAMS OR DELIVERABLES]. Use a table format with Responsible, Accountable, Consulted, Informed clearly marked.
Enter fullscreen mode Exit fullscreen mode

Escalations & Difficult Communications

19. Scope creep response email

Write a professional email to a stakeholder who is requesting work outside the original project scope. Acknowledge their request, explain the scope boundary clearly, offer to raise a formal change request if they want to proceed, and keep the tone collaborative. Context: [DESCRIBE REQUEST]
Enter fullscreen mode Exit fullscreen mode

20. Missed deadline notification

Write an email informing stakeholders that [DELIVERABLE] will be delayed from [ORIGINAL DATE] to [NEW DATE]. Explain the reason honestly without over-apologizing. Include what's being done to prevent further delays and the revised plan. Tone: direct, accountable.
Enter fullscreen mode Exit fullscreen mode

21. Pushback on unrealistic deadline

Help me write a professional response to a request to deliver [DELIVERABLE] by [UNREALISTIC DATE]. I need to say no clearly, offer an alternative timeline with reasoning, and keep the relationship intact. My actual estimate: [YOUR TIMELINE]. Context: [BACKGROUND]
Enter fullscreen mode Exit fullscreen mode

22. Post-incident summary

Write a post-incident summary for the following operations issue. Format: incident summary, timeline of events, root cause, impact, immediate actions taken, long-term remediation plan. Details: [PASTE INCIDENT NOTES]
Enter fullscreen mode Exit fullscreen mode

Vendor & Budget Management

23. Vendor evaluation scorecard

Create a vendor evaluation scorecard for selecting a [TYPE OF VENDOR/SERVICE]. We're evaluating [NUMBER] vendors. Criteria to include: [LIST YOUR KEY CRITERIA]. Weight each criterion by importance. Format as a spreadsheet-ready table with scoring columns.
Enter fullscreen mode Exit fullscreen mode

24. RFP requirements section

Write the requirements section for an RFP for [PRODUCT/SERVICE]. We need: functional requirements, technical requirements, vendor qualifications, and SLA expectations. Context about our needs: [DESCRIBE CONTEXT]. Be specific, not generic.
Enter fullscreen mode Exit fullscreen mode

25. Budget variance explanation

Write a budget variance explanation for a [PROJECT/DEPARTMENT]. We're [OVER/UNDER] budget by [AMOUNT/PERCENTAGE]. Reason: [EXPLAIN WHY]. Write a 2-paragraph explanation for a finance review meeting that is factual, clear, and includes a corrective action.
Enter fullscreen mode Exit fullscreen mode

26. Contract renewal decision brief

Write a one-page decision brief for renewing or replacing our contract with [VENDOR NAME]. Contract details: [COST, TERM, WHAT THEY DO]. Our experience: [POSITIVES AND NEGATIVES]. Options: renew, renegotiate, or switch to [ALTERNATIVE]. Recommendation: [YOUR RECOMMENDATION]. Format for a leadership read.
Enter fullscreen mode Exit fullscreen mode

Planning & Strategy

27. Project charter draft

Draft a project charter for: [PROJECT NAME AND DESCRIPTION]. Include: project objective, scope (in/out of scope), success criteria, key stakeholders, high-level timeline, assumptions and constraints, budget summary, and approvals section. Keep it to one page.
Enter fullscreen mode Exit fullscreen mode

28. Dependency map from project list

I have a list of workstreams for a project. Identify the dependencies between them and flag which are on the critical path. Workstreams: [LIST THEM]. Format as a table showing: workstream, depends on, must complete before, on critical path (Y/N).
Enter fullscreen mode Exit fullscreen mode

29. Lessons learned document

Write a lessons learned document for a recently completed [TYPE] project. Team size: [SIZE]. Duration: [DURATION]. Outcome: [SUCCESSFUL/PARTIALLY SUCCESSFUL/FAILED AND WHY]. Include: what worked well, what didn't, recommendations for future similar projects, and a summary section for the project archive.
Enter fullscreen mode Exit fullscreen mode

30. Quarterly ops review outline

Create an outline for a quarterly operations review for [TEAM/DEPARTMENT]. Audience: [LEADERSHIP LEVEL]. Include: KPI scorecard, highlights, lowlights, blockers resolved, open risks, team capacity, and priorities for next quarter. Format as a presentation outline with talking points per slide.
Enter fullscreen mode Exit fullscreen mode

Making These Prompts Work Harder

A few things that separate the PMs who get real leverage from AI versus the ones who spend more time fixing outputs than they saved:

Be specific about format. Prompts that say "write a status report" get generic output. Prompts that say "under 300 words, use headers, RAG status at the top" get something you can actually send.

Use variables. Where you see [PROJECT NAME] or [PASTE NOTES], that's a placeholder. The more specific context you provide, the better the output. This is also where tools like Promptzy help — you can store these prompts with {{clipboard}} tokens that auto-fill your clipboard content on paste, so you don't have to restructure the prompt every time.

Iterate on outputs. First draft from AI is rarely the final version. Use a follow-up prompt: "Make this more direct" or "Cut this by 30%" to get closer to what you need.

Save the prompts you use most often so they're always one shortcut away. Store these in Promptzy and assign a keyboard shortcut to the ones you reach for daily.

Top comments (0)