Copilot prompts for project managers

Create a working prompt pack for a project manager leading [PROJECT TYPE] with [TEAM AND STAKEHOLDERS]. The project objective and current context are [PROJECT CONTEXT], and the delivery constraints are [CONSTRAINTS].

Produce exactly six copy-paste prompts, each 130 to 180 words, for these project-management tasks: project charter, work breakdown and milestones, weekly status report, risk and issue log, meeting follow-up, and scope-change assessment. Each must be written as the project manager speaking to Copilot, ChatGPT, or Claude, and must contain its own labeled square-bracket fields for needed project information.

Make the prompts operationally rigorous. The charter must distinguish objectives, out-of-scope items, success measures, decision rights, and assumptions. The plan must show dependencies, owners, acceptance criteria, critical-path candidates, and decisions required by dates. The status report must distinguish completed work, next work, blocked work, risks, and decisions needed; never disguise a missed milestone as “in progress.” The risk log must separate risks from active issues and include trigger, owner, mitigation, contingency, and review date. The scope-change prompt must assess impact on schedule, budget, resources, quality, and approved baseline before drafting a recommendation.

For every prompt, add a one-sentence use note. Do not invent commitments, dates, owners, budget figures, approval decisions, or stakeholder positions. Before answering, check that any uncertainty is labeled and that every action item has one accountable owner and a due date or an explicitly missing due date. Ask up to 3 clarifying questions only if a required input is missing.

Create a weekly project status report from [PROJECT UPDATES]. The approved baseline is [BASELINE PLAN], and the audience is [AUDIENCE]. Output: overall health with evidence, completed work, planned work, milestone table with baseline versus forecast dates, blockers, risks, issues, decisions needed, and action items. Separate facts from assumptions and do not assign a green status when a critical milestone is forecast to slip. Give each action one owner and due date; mark missing fields as unresolved. Keep it to 500 words plus tables.

Prepare a 45-minute project risk workshop for [PROJECT]. Participants are [PARTICIPANTS] and known concerns are [KNOWN CONCERNS]. Produce an agenda, a risk-capture table, and facilitator questions that distinguish uncertain future events from active issues. For each risk, require probability, impact, trigger, accountable owner, mitigation, contingency, and next review date. Include prompts to test dependencies, vendor assumptions, security or compliance requirements, and resource bottlenecks. Do not score or prioritize risks without the team's stated criteria and evidence.

Assess this requested change: [CHANGE REQUEST] for [PROJECT]. The approved scope and baseline are [BASELINE]. Using [CURRENT PLAN AND ESTIMATES], produce a change-control summary: request description, rationale, affected deliverables, dependencies, schedule impact, cost or effort impact, quality and risk implications, options, and decision required. Distinguish known impacts from estimates and list information needed to estimate responsibly. Draft a neutral recommendation only when evidence supports it. Do not silently add work to the plan or assume stakeholder approval.