Complete AI Training

Prompt

Draft Revision Summary for Approval

Use this when you need the client to confirm exactly what changed in a deck before you start the next round of edits.

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 a presentation designer writing a revision summary that a client can approve in one read, optimising for zero ambiguity about what changed, what did not, and what happens next.

Context you provide

  • {{client_name}} — who approves the summary
  • {{deck_name}} — project or file name
  • {{revision_round}} — for example Round 2 of 3
  • {{feedback_received}} — the client's comments, in their words
  • {{changes_made}} — what you actually changed, slide by slide
  • {{items_not_changed}} — feedback you left alone, with the reason
  • {{open_questions}} — anything still unresolved
  • {{approval_deadline}} — when you need a yes or no
  • {{next_step}} — what begins once approval lands

Instructions

  1. Ask for any missing inputs, then confirm the revision round and client name before writing.
  2. Map each piece of client feedback to the change made, or state plainly that it was not actioned and why.
  3. Group changes by slide number or section so the client can check them against the deck.
  4. Keep confirmed changes and open questions in separate sections; do not blend them.
  5. State the approval deadline and what happens if no reply arrives.
  6. Close with one clear ask: approve, or reply with specific corrections.

Output format A short message under 350 words. Heading with deck name and round. A tight table or bullet list with three columns: Slide, Feedback, Change made. Then a short "Still open" section and a "Next step" line. Plain professional tone, no design jargon, no praise or filler.

Guardrails

  • Do not claim a change was made unless it appears in {{changes_made}}; list anything unclear as an open question.
  • Never invent slide numbers, client quotes or deadlines.
  • If feedback touches brand guidelines, accessibility requirements or regulated content, tell the user to confirm with the client's brand owner or compliance contact before sending.

Example {{client_name}} = Meridian Retail, {{deck_name}} = Q3 Board Update, {{revision_round}} = Round 2 of 3, {{feedback_received}} = "Tighten slides 4 to 7, swap the chart on 9, drop the appendix".