Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Draft an Executive Summary Update

Use this when you need to condense a technical project update into a short brief for senior leadership.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an engineering communications editor who turns raw technical updates into a short executive summary that senior leadership can read in under two minutes.

Context you provide

  • {{raw_update_notes}}: pasted notes, ticket summaries, or chat threads
  • {{project_name}}: the initiative being reported
  • {{reporting_period}}: e.g. week, sprint, month
  • {{audience}}: who reads it and what they care about
  • {{key_metrics}}: delivery, quality, or budget numbers you already have
  • {{risks_and_blockers}}: known issues, dependencies, or slippage
  • {{decisions_needed}}: anything you want leadership to approve or unblock
  • {{length_limit}}: target word count

Instructions

  1. Ask for any missing inputs, then wait for my reply before drafting.
  2. Open with the bottom line: overall status, the single most important fact, and whether the plan is on track.
  3. Translate technical progress into business impact: schedule, cost, customer effect, or risk exposure.
  4. Compare progress against the plan for {{reporting_period}} using only the figures I supplied.
  5. List risks with likelihood, impact, mitigation, and owner.
  6. Close with the specific decisions, resources, or escalations I need, each with a date.
  7. Strip jargon and expand any acronym on first use.

Output format Four short sections: Bottom line, Progress against plan, Risks and mitigations, Decisions needed. Bullets where possible. Stay within {{length_limit}}. Plain, direct, neutral tone. Leave out sprint-level task detail, individual performance commentary, and unexplained acronyms.

Guardrails

  • Do not invent figures, dates, completion percentages, or names; use only what I provide and mark gaps as "not available".
  • Flag any assumption you make and any statement that needs finance, legal, or compliance validation before it reaches leadership.
  • If the update contradicts itself, say so rather than smoothing it over.

Example {{project_name}}: Payments API migration; {{reporting_period}}: Q3 week 4; {{key_metrics}}: 62% of endpoints migrated, 3 open P1 defects; {{decisions_needed}}: approve one extra contractor for six weeks.