Copilot prompts for report writing

Write a decision-ready [REPORT TYPE] for [AUDIENCE] using only the material in [SOURCE NOTES]. The report covers [REPORTING PERIOD] and must support the following purpose: [DECISION OR ACTION NEEDED].

First, identify the report's central conclusion in one sentence. Then produce a report of 700-1,000 words in this exact structure:
1. Executive summary: 3-5 bullets covering the current state, the most consequential change since the prior period, and the decision or action requested.
2. Progress against plan: a table with workstream, planned outcome, current status (on track, at risk, blocked, or complete), evidence from the notes, and variance from plan.
3. Decisions and dependencies: list each decision needed, its recommended owner, deadline, options if they are present in the notes, and consequence of no decision. Separate external dependencies from internal ones.
4. Action plan: a table with next step, single accountable owner, due date, required input, and success condition. Do not assign a person unless the notes identify that person or role.
5. Risks and issues: for each, state likelihood, impact, early warning sign, mitigation, contingency, and owner when supported.
6. Appendix: short list of source gaps, assumptions, and metrics that need confirmation.

Use plain business language. Distinguish completed work, planned work, and recommendations; do not write a recommendation as an accomplished fact. Preserve exact dates, numbers, and names from the notes. If dates conflict, show the conflict rather than resolving it.

Before answering, run two checks: flag every claim, owner, date, or metric that is not supported by [SOURCE NOTES]; and confirm every action has one accountable owner, a due date, and a testable success condition. Ask up to 3 clarifying questions only if a required input is missing.

Create a 400-word [BOARD OR STEERING COMMITTEE] update from [SOURCE NOTES] for [AUDIENCE]. Include: overall status; three material accomplishments or changes; decisions requested with a recommendation and deadline; top three risks with impact and mitigation; and a next-30-days outlook. Use only facts in the notes. Do not include operational detail unless it changes cost, timeline, scope, compliance, or customer impact. Flag unsupported claims and any decision that lacks a named owner or deadline. Ask up to 3 questions only if required inputs are absent.

Draft a blameless [INCIDENT TYPE] report from [TIMELINE AND EVIDENCE] for [AUDIENCE]. Include a factual summary; customer or business impact with duration and scope; time-stamped timeline; contributing conditions versus confirmed root cause; actions taken; corrective and preventive actions with owners and due dates; and open questions. Do not infer root cause or assign fault beyond the evidence. Flag missing timestamps, unsupported causation, and actions without an accountable owner. Ask up to 3 questions only when needed.

Write a client-facing [REPORTING PERIOD] progress report for [CLIENT] from [PROJECT NOTES]. Produce 500-700 words with: accomplishments tied to agreed deliverables; current milestone status; decisions or materials needed from the client; next steps with dates; and risks framed with practical mitigation. Keep internal staffing discussions and unconfirmed concerns out unless they affect the client’s scope, cost, or date. Do not promise outcomes not documented in the notes. Check that every requested client action has a clear deadline and consequence.