Event audiences don’t remember every slide—they remember the point, the proof, and what to do next. The prompt templates below are built for turning keynotes and panels into crisp, publishable briefs: accurate, attributable, and easy to scan.
Before you prompt: collect the right inputs
- Source: transcript, notes, slide text, or a time-stamped outline (preferably all three).
- Event context: session title, speakers, orgs, date, and audience type.
- Constraints: desired length, reading level, and whether you must include citations.
- Accuracy rule: “If it isn’t in the source, label it as an assumption or omit it.”
Template 1: Keynote summary (tight newsroom brief)
Use when you need a single, shareable recap that reads like a compact daily block.
PROMPT
You are an event newsroom editor. Write a concise keynote brief for mature professional readers (ages 40–60). INPUTS: - Session title: - Speaker(s) + affiliations: - Date/location: - Source text (transcript/notes/slides): OUTPUT REQUIREMENTS: 1) Headline (max 12 words) 2) One-sentence “Why it matters” 3) 5–7 bullet highlights (each: claim + evidence or example) 4) 1–2 notable quotes (only if present in source) 5) “What changed / what’s new” (max 3 bullets) 6) “Who should care” (roles/industries) ACCURACY RULES: - Do not invent facts, stats, names, or company actions. - If a detail is unclear, write: “Not specified in the source.” - If you infer, label it explicitly as an inference. STYLE: - Plain English, no hype, no buzzword stacking. - Keep sentences short. Prefer concrete nouns and verbs.
Template 2: Keynote “executive memo” (decisions-first)
Use when the reader wants implications, tradeoffs, and next actions (not a play-by-play).
PROMPT
Act as an executive analyst. Convert the keynote into a decision-oriented memo. INPUT: (paste source text) STRUCTURE: - Summary (3 sentences max) - Key assertions (3–5 bullets). For each: (a) assertion (b) supporting evidence in source (c) risk/limitation. - Strategic implications (3 bullets) - Open questions to verify (3–6 bullets) - Recommended next steps (5 bullets) split by: 0–7 days / 8–30 days / 31–90 days GUARDRAILS: - Only cite what appears in source. - If evidence is missing, mark the assertion as “unsubstantiated in source.” - No generic advice; each next step must name an owner role and a tangible artifact (brief, checklist, test plan, outreach list, etc.).
Template 3: Panel takeaways (multi-speaker, attribution-safe)
Panels can blur who said what. This template prioritizes attribution and consensus vs. disagreement.
PROMPT
You are summarizing a panel discussion for publication. INPUTS: - Panel title: - Moderator: - Panelists (name + org): - Source text: OUTPUT: A) One-paragraph overview of the panel’s central question. B) “Areas of agreement” (3–6 bullets). Each bullet must include: (1) takeaway (2) which panelists supported it (by name) or “multiple panelists” if unclear. C) “Points of disagreement” (2–4 bullets) with attribution. D) “Notable frameworks or examples” (up to 5 bullets) — only if present. E) “Action items” (5 bullets) written as: verb + object + intended outcome. ATTRIBUTION RULES: - If the speaker is not explicitly identified, label as “Unattributed in transcript.” - Do not merge different speakers’ positions into one statement. STYLE: - Neutral tone. No editorializing.
Template 4: Action items you can actually assign
Many summaries stop at “should consider.” This forces ownership, deliverables, and timing.
PROMPT
Extract actionable next steps from the source text. INPUT: (paste source) OUTPUT A TABLE with columns: 1) Action item (start with a verb) 2) Owner role (e.g., Marketing Ops, IT Security, Program Manager) 3) Deliverable (a concrete artifact) 4) Due window (0–7 / 8–30 / 31–90 days) 5) Success signal (how we’ll know it worked) 6) Dependencies / blockers RULES: - Each action must be feasible and derived from source. - If ownership is unclear, propose 1–2 plausible roles and mark as “suggested.” - Avoid duplicates; merge similar actions and keep the stronger wording.
Template 5: Quote validation + fact check pass
Run this after drafting. It reduces misquotes and overconfident phrasing. For deeper accuracy workflows, see Reducing Hallucinations….
PROMPT
You are a meticulous fact-checker. Compare the DRAFT to the SOURCE. INPUTS: - SOURCE: - DRAFT: TASKS: 1) List any statements in the draft that are not supported by the source. 2) Flag numbers, dates, names, and claims that need verification. 3) Check quotes: confirm exact wording exists in source; otherwise mark “not found.” 4) Suggest safer rewrites that preserve meaning without adding new facts. OUTPUT: - Unsupported/uncertain statements (bulleted) - Quote issues (bulleted) - Recommended rewrites (bulleted with replacements) - Overall risk level: low / medium / high (with one-sentence rationale)
Template 6: “Daily block” category formatting (community calendar style)
If your site publishes short, categorized blocks, this transforms a session into a consistent format readers can skim.
PROMPT
Rewrite the session recap into a compact daily block.
INPUTS:
- Category (choose one): Tech & AI / Business / Health / Arts / Local Government / Nonprofit / Education
- Source text:
OUTPUT FORMAT:
Category: {one}
Headline: {8–12 words}
What happened: {2 sentences}
Key details:
- {3 bullets}
Practical takeaway: {1 sentence}
If you go / if you share: {1 sentence with who it’s for}
CONSTRAINTS:
- Keep total under 120 words.
- No speculation; if critical detail missing, write “Details not specified.”
Operational tips for consistent results
- Two-pass method: first extract claims + evidence; second write the brief. This lowers confident-sounding gaps.
- Force structure: require bullets, max lengths, and explicit “not specified” handling.
- Prefer “evidence hooks”: ask for an example, stat, or quote per highlight—even if the answer is “none in source.”
- Standardize action items: verb + object + deliverable + owner + timeframe. If you’re building an end-to-end recap workflow, pair this with AI Event Recaps: A Workflow….
Copy/paste checklist
- Paste source text first (transcript + notes).
- Add speaker list and session title.
- Pick one template; run it once.
- Run the fact-check template against the draft.
- Publish only what’s supported; mark unknowns.