35 ChatGPT Prompts That Cut Your Project Admin Time in Half

Write a weekly status report for [project name]. Here's the raw information: Completed this week: [list items] In progress: [list items with % complete] Blocked: [list blockers] Key metrics: [any numbers — velocity, bug count, etc.] Budget: [on track/over/under] Timeline: [on track/at risk/delayed] Format the report with: a one-line executive summary (green/yellow/red status with reason), completed items grouped by workstream, in-progress items with expected completion dates, risks and blockers with owners and next steps, upcoming milestones for next week, and any decisions needed from leadership. Keep it under 1 page. Use bullet points, not paragraphs.

I need to present a project update to [audience: executives/board/client]. Meeting duration: [time]. The project is currently [on track/at risk/delayed]. Key updates: [List major updates, wins, issues] Create a slide outline (5-7 slides) with: executive summary slide (status, key metrics, headline), progress against milestones (visual timeline), wins and completed deliverables, risks and issues (with mitigation plans), budget and resource status, upcoming milestones and decisions needed, and Q&A prep (likely questions and answers). For each slide, provide: title, 3-4 bullet points (maximum), speaker notes with what to say, and data visualizations to suggest.

I need to communicate a project delay to [audience]. The details: Original deadline: [date] New deadline: [date] Reason for delay: [honest explanation] Impact: [what this affects] What we're doing about it: [mitigation actions] Write a communication that: leads with the new timeline (don't bury the bad news), explains the root cause honestly without throwing anyone under the bus, outlines what we've already done to minimize the delay, presents a recovery plan with specific actions, offers to meet to discuss concerns, and maintains confidence in the team's ability to deliver. Write two versions: one for executives (3 paragraphs) and one for the broader team (more detailed).

I just finished a [meeting type: standup/planning/review/retro] that ran [duration]. Here are my raw notes: [paste meeting notes] Create: a clean summary (3-5 sentences capturing key decisions), action items extracted as a table: Action | Owner | Due Date | Priority, decisions made (list each with brief rationale), open questions that need follow-up, parking lot items deferred to future discussion, and any risks or concerns raised. Format this as something I can paste directly into [Slack/email/Confluence/Notion].

I need to submit a change request for [project name]. The change: What: [describe the change] Why: [business reason] Impact on timeline: [delay/no delay] Impact on budget: [cost change] Impact on scope: [what changes] Risk of NOT making this change: [what happens if we keep the original plan] Write a change request document that: clearly describes the change, provides business justification, quantifies the impact on timeline, budget, and resources, compares the cost of change vs cost of not changing, proposes an implementation approach, and identifies who needs to approve. Keep it factual and objective — let the data make the argument.

Design a communication plan for [project name]. Stakeholders: [List each stakeholder/group and what they care about] Team: [size and distribution: co-located/remote/hybrid] Duration: [project length] Create a plan that specifies: who needs what information, how often (daily/weekly/monthly/ad hoc), through what channel (Slack/email/meeting/dashboard), in what format (report/presentation/standup), and who is responsible for each communication. Include: a meeting cadence (recurring meetings with purpose and attendees), escalation paths for blockers and risks, how decisions get documented and shared, and templates for recurring communications.

Create a risk register for [project name]. Project context: Type: [software/construction/marketing/etc.] Timeline: [duration] Team: [size and experience] Dependencies: [external dependencies] Stakeholder complexity: [low/medium/high] Identify 15-20 risks across categories: technical, resource, schedule, scope, external, and organizational. For each risk: description, likelihood (1-5), impact (1-5), risk score (likelihood × impact), trigger (how we'll know it's happening), mitigation strategy (reduce likelihood), contingency plan (reduce impact if it happens), and owner. Sort by risk score descending. Highlight the top 5 risks that need immediate attention.

My project is behind schedule. Help me analyze why: Original plan: [key milestones and dates] Actual progress: [where we are vs where we should be] Team size: [current vs planned] Scope changes: [any additions since kickoff] Blockers encountered: [list them] Quality issues: [bugs, rework] Perform a root cause analysis: is this a planning problem (underestimated), execution problem (slow velocity), scope problem (creep), resource problem (understaffed), or dependency problem (waiting on others)? For each root cause identified, suggest specific corrective actions. Then: create a recovery plan with revised timeline, identify what can be cut or deferred to hit the original deadline, and recommend what to communicate to stakeholders.

Run a pre-mortem for [project name]. Imagine it's [deadline date] and the project has failed completely. What went wrong? Project context: [Brief description of the project, team, timeline] Generate: 10 plausible failure scenarios, ordered from most likely to least, the chain of events that would lead to each failure, early warning signs for each scenario, preventive actions we can take NOW for each, and a prioritized list of the top 3 actions that would prevent the most failures. Frame everything as "we could prevent this by..." rather than doom and gloom.

I need to escalate a project issue. Details: Issue: [describe the problem] Impact: [what happens if unresolved] What I've tried: [actions already taken] What I need: [decision/resources/help from leadership] Deadline: [when this needs to be resolved by] Write an escalation message to [audience: skip-level manager/VP/steering committee] that: summarizes the issue in one sentence, provides enough context without over-explaining, shows what I've already done (I'm not just passing the problem up), clearly states what I need from them and by when, and proposes 2-3 options with my recommendation. Tone: professional, urgent without being panicked, solution-oriented.

Help me set up and populate a decision log for [project name]. Key decisions already made: [List decisions with rough dates and context] For each decision, document: decision (what was decided), date, context (why this decision was needed), options considered (what alternatives were evaluated), rationale (why this option was chosen), decision maker(s), impact (what changes as a result), and review date (when to revisit if applicable). Create a template for future decisions. Include a section for "decisions pending" with the information needed to make them.

A stakeholder just requested a new requirement for [project name]: New requirement: [describe it] Current project status: [phase, % complete, remaining timeline] Current scope: [brief summary of what's in scope] Assess the impact: effort estimate to implement this (in developer days/sprint points), timeline impact (will it delay the deadline? by how much?), resource impact (do we need additional people?), technical impact (does this conflict with existing architecture or decisions?), quality risk (does adding this increase bug risk?), opportunity cost (what existing work gets delayed?). Provide three options: 1) Add it and accept the timeline impact 2) Add it but remove something else 3) Defer it to a future release. Recommend one option with justification.

Facilitate a sprint retrospective for my team. Context: Sprint: [number/name] Sprint goal: [what we aimed to do] Outcome: [did we hit the goal? what shipped?] Velocity: [planned vs actual] Key events: [anything notable — outages, scope changes, team changes] Generate: a retrospective agenda using [format: Start/Stop/Continue, 4Ls, Sailboat, or Mad/Sad/Glad], 3 discussion prompts for each category that are specific to OUR sprint (not generic), facilitation tips for drawing out quiet team members, a framework for turning complaints into actionable improvements, an action items template with owner and deadline, and a follow-up template to track if last retro's actions were completed.

My team's daily standups are [describe the problem: too long, unfocused, people zone out, same updates daily, etc.]. Team size: [number], working on [type of project], using [methodology]. Design an improved standup format that: keeps it under [target minutes], stays focused on blockers and collaboration (not status reporting), engages everyone without putting people on the spot, handles async/remote team members, surfaces risks early, and replaces the boring "what I did yesterday" format with something more useful. Include: the new format/questions, ground rules, what to take offline, and how to handle when someone has nothing new to share.

Help me prepare for sprint planning. Context: Team capacity: [available person-days this sprint, accounting for PTO and meetings] Backlog items: [list top priority items with brief descriptions] Technical debt items: [if any] Carryover: [unfinished items from last sprint] Sprint length: [days/weeks] Create a sprint planning agenda that: reviews last sprint metrics (5 min), presents sprint goal candidates for team vote, walks through backlog items in priority order, includes estimation guidance for the team, allocates [X]% of capacity to technical debt, reserves [X]% buffer for unexpected work, and produces a clear sprint backlog with acceptance criteria for each item. Also prepare: a capacity worksheet and a "what if we can't fit everything" conversation framework.

I need to prepare a sprint review/demo for stakeholders. This sprint we completed: [List completed items with brief descriptions] For each item, help me create: a demo script (what to show, in what order, what to say), talking points connecting this feature to business value, before/after comparison if applicable, any limitations or known issues to address proactively, and metrics or data showing the impact. Also create: an opening that reminds stakeholders of the sprint goal, a closing that previews what's coming next sprint, and answers to likely stakeholder questions.

Help my team create a working agreement. Team context: Size: [number] Distribution: [co-located/remote/hybrid, time zones] Methodology: [Scrum/Kanban/hybrid] Current pain points: [what's not working] Draft a working agreement covering: communication norms (response time, channels, async vs sync), meeting etiquette (cameras, agenda, note-taking), code review standards (turnaround time, approval requirements), definition of done (when is a task truly complete?), conflict resolution process, work-life boundaries (core hours, after-hours expectations), and decision-making framework (when to decide independently vs when to discuss). Frame each item as a positive agreement, not a rule. Include a review date to revisit and update.

I need to allocate my team across [number] concurrent projects/workstreams: Team members: [List each person with their skills and current capacity] Projects: [List each project with: required skills, priority, deadline, estimated effort] Create a resource allocation plan that: assigns people to projects based on skills and priority, avoids splitting anyone across more than 2 projects (context switching tax), identifies skill gaps where we need to hire or contract, shows utilization per person (flag anyone over 85%), highlights conflicts where multiple projects need the same person simultaneously, and includes a contingency plan for unplanned absences. Format as a person-by-project matrix showing allocation percentages.

I need to justify hiring [number] more [role] for my team. Current state: Team size: [current] Current workload: [projects in flight, backlog size] Delivery metrics: [velocity, lead time, quality] Pain points: [what's suffering — quality, speed, morale] Business impact of delays: [revenue, customer satisfaction, competitive risk] Build a business case that: quantifies the current capacity gap (specific numbers), shows the cost of NOT hiring (delayed projects, quality issues, burnout turnover), calculates ROI of the new hire(s) based on project value, proposes a ramp-up timeline with expected productivity curve, offers alternatives considered (contractors, process improvements, scope reduction) and why they're insufficient, and includes a specific job profile and hiring timeline.

Create a skill matrix for my team to identify gaps and growth opportunities: Team members: [List each person with their role] Skills needed for our projects: [List technical and soft skills] Create a matrix template that: lists each team member against each skill, uses a rating scale (1=learning, 2=can do with help, 3=independent, 4=can teach others), highlights single points of failure (only one person knows a critical skill), identifies cross-training priorities (highest business risk skill gaps), suggests a development plan for each person (one skill to grow this quarter), and flags any skills where we have zero coverage (hiring or training emergency).

A key team member is leaving the project/company in [timeframe]. They own: [List their responsibilities, knowledge areas, and ongoing work] Create a knowledge transfer plan that: lists everything that needs to be transferred, identifies who will take over each responsibility, creates a transfer schedule (what to cover each day/week), includes documentation the departing person needs to create, plans for pairing sessions on complex areas, identifies anything that needs to be deprioritized to make time for knowledge transfer, and has a "dead man's switch" checklist (access, accounts, recurring tasks). Prioritize by: what's impossible to recover if not transferred vs what we could figure out later.

Help me calculate and forecast my team's velocity for better sprint planning. Historical data (last 6 sprints): [Sprint 1: committed X points, completed Y points] [Sprint 2: committed X points, completed Y points] [continue...] Upcoming factors: [new team members, holidays, complex upcoming work, etc.] Analyze: average velocity and trend (improving, declining, stable), variance and predictability, commitment accuracy (are we overcommitting?), impact of team composition changes, and recommended capacity for next sprint. Also: identify patterns (do we slow down before releases? after sprints with carryover?), suggest a sustainable velocity target, and create a simple forecasting model for "when will we finish [X] remaining points?"

I'm handing off [project name] to [new PM/team]. Create a comprehensive handoff document that covers: project overview and current status, key stakeholders and their concerns/priorities, team members and their roles/strengths, outstanding risks and issues (with status), decisions made and their rationale, upcoming milestones and deadlines, where to find everything (documents, repos, boards, channels), recurring meetings and their purpose, budget status and approvals, things I would do differently (lessons learned), and the #1 thing the new PM needs to pay attention to. Format as a reference document they can consult repeatedly, not a narrative they'll read once.

Design a project dashboard for [project name]. Audiences: [List each audience and what they care about: execs want progress, team wants blockers, clients want deliverables] For each audience, specify: key metrics to display (and how to calculate them), visualizations that make the data clear at a glance, update frequency (real-time, daily, weekly), data sources and how to pull them, red/yellow/green thresholds for status indicators, and drill-down paths (what can they click to see more detail?). Keep the main view to one screen — no scrolling. Include a mock layout description.

Create a "Definition of Done" for my team. Context: Team type: [frontend/backend/full-stack/design/etc.] Methodology: [Scrum/Kanban] Deployment: [CI/CD/manual releases] Quality standards: [code review required? testing standards?] Create a DoD checklist for: user stories/features, bugs, technical debt items, and documentation tasks. Each checklist should be: specific enough that two people would agree whether each item is met, realistic (achievable within a sprint), and ordered from development through testing to deployment. Include a "DoD violation" process (what happens when something is "done" but doesn't meet the checklist). Make it a printable one-page reference.

One of our team processes is broken: Process: [name and description of the process] Current steps: [list each step, who does it, how long it takes] Pain points: [what's frustrating about it] Frequency: [how often this process runs] People involved: [who participates] Analyze: where are the bottlenecks (steps that take longest or block most often)? What steps could be automated, eliminated, or combined? What's the root cause of the pain points? Propose a redesigned process with: new steps and owners, estimated time savings, automation opportunities, implementation plan (how to transition from old to new), and metrics to track if the new process is actually better.

Help me create a lessons learned document for [project name] that just [completed/reached a milestone]. Project summary: [brief description, timeline, outcome] What went well: [list wins] What went poorly: [list problems] Surprises: [things we didn't expect] Organize lessons by category: planning and estimation, execution and delivery, communication and stakeholder management, technical decisions, team dynamics and collaboration, and process and tools. For each lesson: what happened (factual), why it happened (root cause), what we'd do differently, and specific recommendation for future projects. End with the top 5 lessons the organization should adopt across all projects.

Design a lightweight governance framework for [organization/team]. We manage [number] projects with [team size]. Current problems: [List governance issues: unclear decision authority, inconsistent processes, lack of visibility] Create a framework that covers: project intake and prioritization (how do new projects get approved?), project categorization (small/medium/large with different oversight levels), decision authority matrix (who can approve what, at what threshold), reporting cadence and format for each project tier, escalation paths and trigger criteria, quality gates and phase reviews, and portfolio-level visibility (how leadership sees across all projects). Keep it lightweight — governance should enable speed, not create bureaucracy.

We had an incident that affected [project/product/service]. Help me write a post-incident review: Incident: [what happened] Impact: [who was affected, for how long] Timeline: [when detected, when resolved] Root cause: [what caused it] Response: [what we did] Create a review document with: incident summary (3 sentences), detailed timeline with timestamps, root cause analysis (use "5 Whys" technique), contributing factors (what made this worse), what went well in our response, what could be improved, action items to prevent recurrence (with owners and deadlines), and a severity classification with criteria. Maintain a blameless tone throughout — focus on systems and processes, not individuals.