ChatGPT Prompts for Event Planners (From Venue Hunt to Post-Event Recap)
Event planners spend as much time on writing as they do planning. Client briefs, vendor emails, run-of-show documents, social media copy, post-event recaps, and follow-up emails — all of it from scratch, for every event. These 31 ChatGPT prompts cover the full workflow so you can spend less time writing and more time executing.
The average event planner juggles dozens of writing tasks for every event they run — discovery call summaries, scope of work documents, vendor RFPs, negotiation emails, run-of-show timelines, social media posts, debrief reports, thank-you notes, and re-engagement pitches. Most of it follows a predictable structure. All of it takes time.
These prompts are organized around the actual lifecycle of an event — from first client conversation through post-event follow-up and repeat business. They work for independent planners, corporate event teams, venue coordinators, and anyone who spends their days making events happen on time and within budget.
Every prompt uses [BRACKETS] for the variables you fill in. Copy, customize, paste into ChatGPT, and edit the output before it goes to a client or vendor.
Section 1: Client Discovery & Event Briefs (Prompts 1–6)
The discovery and briefing phase is where events are won or lost before the planning even starts. These prompts help you run better discovery calls, document client goals clearly, navigate budget conversations confidently, write tight scopes of work, and build the pre-planning alignment that prevents disputes later.
1. Discovery Call Question Guide
Generate a structured discovery call framework that surfaces everything you need to plan the event — before you quote a single number.
Write a discovery call question guide for an initial meeting with a new event planning client. Event type I'm expecting: [E.G. "corporate conference," "private wedding," "nonprofit gala," "brand activation," "birthday celebration"]. What I need to learn from this call: [LIST — e.g. "budget, guest count, vision, who else they're considering, decision timeline"]. Generate a structured guide with 20–25 questions organized into sections: (1) Event Fundamentals — date flexibility, location preferences, guest count estimate, indoor vs. outdoor preference; (2) Goals and Success Metrics — what does a successful event look like, what would make guests talk about this event 6 months later; (3) Budget — overall range, what they've spent on comparable events, what they're NOT willing to cut; (4) Vision and Atmosphere — describe the ideal feeling when guests walk in, 3 adjectives to describe the event, any events they've attended that inspired this one; (5) Constraints and Non-Negotiables — what they must have, what they're trying to avoid, any brand or venue restrictions; (6) Decision Process — timeline for choosing a planner, who else is involved in the decision, what makes them say yes; (7) Past Experience — have they worked with a planner before, what went well or poorly. For each question: write it as I would ask it on the call, and add a brief note on what I'm actually learning from that question. Tone: conversational and curious — discovery calls are where you earn trust by listening more than talking.2. Event Brief Template — Post-Discovery
Draft a comprehensive event brief to send after the discovery call so both parties are aligned before any planning begins.
Write a formal event brief document to send to a client after a discovery call. Client name: [NAME]. Event type: [DESCRIBE]. Event date or date range: [DATE OR RANGE]. Venue (confirmed or TBD): [NAME/LOCATION OR "TBD"]. Estimated guest count: [NUMBER]. Budget range confirmed: [$RANGE]. Key goals as I understand them: [LIST — e.g. "celebrate the team's milestone," "generate media coverage," "create a networking moment for 200 VIPs"]. Style or atmosphere direction: [DESCRIBE — from the call]. What the client said they absolutely must have: [LIST NON-NEGOTIABLES]. What they want to avoid: [LIST]. Decisions still outstanding: [LIST — e.g. "venue confirmation," "final guest count," "entertainment decision"]. Write an event brief with: (1) Event overview (name, type, date, venue, guest count, budget range), (2) Goals and success metrics in clear language, (3) Creative and atmosphere direction based on what they described, (4) Non-negotiables and constraints, (5) Scope of services I'm providing vs. what's the client's responsibility, (6) Open decisions with owner and target date for each, (7) Proposed next steps with dates. Format: clean, professional document with bold headers. Under 600 words. Tone: organized and aligned — this brief is a shared agreement, not an internal planning doc. It should make the client feel heard and confident that you understand their event.3. Budget Conversation Script
Navigate the budget conversation without awkwardness — extract real numbers, set realistic expectations, and position your fees confidently.
Write a budget conversation script for an event planning consultation. My planning fee structure: [DESCRIBE — flat fee, percentage of total budget, day rate + expenses, or combination]. What I need to learn in this conversation: [LIST — e.g. "their total budget, how firm it is, what they've budgeted for planning fees specifically, what category they'll flex on vs. not"]. Common objection I face: [E.G. "they want to know my fee before sharing their budget," "they have a lower budget than I can realistically work with," "they've never hired a planner and don't understand what's included"]. Write a conversation guide with: (1) How to open the budget conversation naturally — a transition line from vision to numbers that doesn't feel abrupt; (2) Questions to ask that surface the real budget (including the ones clients are sometimes reluctant to share); (3) How to respond when a client says "we're flexible" without an actual number — the follow-up questions to pin it down; (4) How to present my fee transparently and frame it as value, not cost; (5) How to respond if their budget is below what I can deliver — two paths: (a) gracefully referring out, (b) scoping down to what I can offer at their budget; (6) Closing language that moves from budget conversation to the next step without pressure. Format: dialogue-style script with my lines in one color and notes on the strategy behind each. Tone: confident, transparent, and client-focused — the budget conversation is where planners lose clients or build deep trust.Section 1 (continued): Client Discovery & Event Briefs
4. Scope of Work Summary Email
Write a clear scope of work email that prevents scope creep, sets boundaries, and protects both planner and client.
Write a scope of work summary email to send to a client before contract signing. My name / company: [NAME]. Client name: [NAME]. Event: [DESCRIBE BRIEFLY]. Services I'm providing: [LIST SPECIFICALLY — e.g. "venue sourcing and site visits (up to 3 venues)," "full vendor coordination and management," "day-of on-site coordination (up to 10 hours)," "run-of-show document drafting"]. What is NOT included: [LIST EXPLICITLY — e.g. "entertainment booking," "floral design," "printed collateral," "travel expenses beyond 30 miles"]. Number of planning calls included: [NUMBER + DURATION — e.g. "6 planning calls of 60 minutes each"]. Revision policy: [E.G. "up to 2 rounds of revisions on planning documents; additional revisions at $X/hour"]. What happens if the event scope changes significantly: [DESCRIBE YOUR CHANGE ORDER POLICY]. Write a scope of work summary with: a brief event overview, a detailed bulleted list of what's included, a clearly labeled "Not included" section, the call and revision policy, the change order process, and a statement about what I need from the client to do my job well (e.g. timely decisions, a single point of contact). Under 500 words. Tone: professional and specific — a clear scope email prevents the most common planning disputes before they start. It should feel like a professional service agreement, not a warning.5. Client Intake Form — Questions to Ask Every New Client
Build an intake form that collects every piece of information you need before your first planning session.
Write a client intake form for new event planning clients. Event type I typically plan: [DESCRIBE — e.g. "corporate events," "private social events," "weddings," "brand activations"]. What I need to know before our first planning session: [LIST — or ask for a comprehensive intake]. Write a 20–25 question intake form organized into sections: (1) Contact Information — client name, company (if applicable), preferred contact method, best time to reach; (2) Event Basics — event type, working title, date options (first and second choice), venue preference (specific or general area), indoor/outdoor, guest count estimate; (3) Budget — total budget range, flexibility level, what percentage is earmarked for planning fees; (4) Vision — 3 words to describe the atmosphere, any events they've attended that inspired this one, what they want guests to feel, any themes or color directions; (5) Logistics — catering format (plated, buffet, cocktail, etc.), entertainment or program requirements, AV needs, accessibility considerations; (6) Non-Negotiables — must-haves, must-avoids, any vendor exclusivity requirements; (7) Decision Making — who else is involved in decisions, preferred communication style (email, calls, project management tool), how quickly they typically respond; (8) Past Experience — have they worked with an event planner before, what worked well, what they want to do differently. Format each question for a form (short answer, dropdown, or multiple choice as appropriate). Include a final open-text field: "Is there anything else I should know before we start planning?" Tone: professional and friendly — the intake form is often the first formal interaction with a new client.6. Goals Alignment Memo — Pre-Planning Agreement
Write a goals alignment memo that documents shared expectations before the first invoice — the single document most planners skip that prevents the most disputes.
Write a goals alignment memo to share with a client at the start of an engagement. Client name: [NAME]. Event: [TYPE + DATE]. Budget confirmed: [$AMOUNT]. Guest count: [NUMBER]. What the client has told me success looks like: [DESCRIBE IN THEIR WORDS — from discovery call or intake form]. My interpretation of what they actually need: [YOUR PROFESSIONAL ASSESSMENT — what you think the real goal is, even if they haven't framed it this way]. Any tension or misalignment I've noticed in their stated goals: [E.G. "they want a luxury feel but have a mid-range budget," "they want intimacy but have invited 250 people," "they want 'low key' but their vendor list suggests otherwise"]. My recommendation to address those tensions: [DESCRIBE]. Write a goals alignment memo with: (1) Stated event goals (in their words), (2) My interpretation and framing of those goals as planning objectives, (3) What success will look like — 3 specific, measurable outcomes I'll use to evaluate whether the event achieved what it was meant to, (4) Any gaps between stated goals and current constraints (budget, timeline, guest count) — and how I recommend addressing them, (5) What I need from the client for this event to succeed (timeline decisions, responsiveness, a single point of contact). Under 500 words. Format: memo with numbered sections. Tone: professional and advisory — this is the document where a planner earns trust by demonstrating they've understood the event more deeply than the client has articulated it yet.Section 2: Vendor Outreach & Negotiation Emails (Prompts 7–11)
Vendor management generates more writing than almost any other part of event planning — venue inquiries, RFPs, negotiation emails, briefing documents, and post-event performance reviews. These prompts cover every vendor touchpoint from initial inquiry to closing the relationship.
7. Venue Inquiry Email
Write an initial venue inquiry that gets a response, a real quote, and availability confirmation — without back-and-forth.
Write an initial venue inquiry email. My name / company: [NAME]. Event type: [DESCRIBE — e.g. "corporate dinner for 150," "wedding reception for 200," "product launch party for 100"]. Preferred event date(s): [DATE OR RANGE]. Guest count: [NUMBER]. Format: [E.G. "seated dinner," "cocktail reception," "conference with breakout sessions"]. What I need from the venue: [LIST — e.g. "main hall capacity, catering exclusivity policy, setup and teardown access windows, parking, AV capabilities, pricing structure"]. Budget range for venue rental (optional): [$RANGE — or "please provide pricing"]. Other venues I'm considering: [MENTION IF RELEVANT — creates urgency without being aggressive]. Write a venue inquiry email that: opens with a clear one-sentence description of the event, provides all information the venue needs to give me a useful first response, asks specific questions I need answered before a site visit, communicates timeline (when I need to make a decision), and ends with a clear next step (availability confirmation + site visit scheduling). Under 300 words. Tone: professional and efficient — venue coordinators handle dozens of inquiries a week. A specific, organized email rises to the top.8. Vendor RFP — Request for Proposal
Write a detailed RFP that produces accurate, comparable quotes from multiple vendors — not vague estimates you can't evaluate.
Write a vendor RFP (Request for Proposal) email for an event. Event overview: [DESCRIBE — type, date, guest count, venue if confirmed]. Vendor category: [E.G. "catering," "floral design," "AV production," "photography," "entertainment"]. Specific scope for this vendor: [DESCRIBE IN DETAIL — e.g. "full catering for a 200-person seated dinner including staff, rental equipment, and a plated 3-course menu with 3 dietary options"]. Budget range for this vendor category (optional): [$RANGE — or "please provide your full pricing"]. What I need in their proposal: [LIST — pricing, what's included, staffing, setup/teardown times, deposit and payment terms, cancellation policy, insurance certificates]. Deadline for proposals: [DATE]. Decision date: [DATE]. Write an RFP email with: a concise event overview, a detailed scope-of-work for their category, specific questions they must answer in their proposal, the timeline and decision date, and a CTA for their next step. Under 350 words. Tone: precise and professional — a well-structured RFP produces proposals you can actually compare. Vague inquiries produce vague quotes.9. Vendor Negotiation Email
Negotiate a price or scope adjustment professionally, without burning the vendor relationship you'll rely on for years.
Write a vendor negotiation email. Vendor name and category: [NAME + E.G. "catering," "venue," "AV"]. Their quote: [DESCRIBE — price and what's included]. What I need to change: [DESCRIBE SPECIFICALLY — e.g. "the quote is $4,000 over my client's budget," "we need to add a cocktail hour but keep the current price," "the payment schedule requires 50% upfront and I need 30%"]. My negotiation position: [DESCRIBE — e.g. "I have a competing quote that's $3,000 lower," "I can offer payment in full 30 days early," "I'm bringing them 4 events this year," "I don't have leverage but need to find savings"]. What I'm willing to offer in return: [E.G. "guaranteed 2 referrals," "early full payment," "portfolio photography they can use," "repeat bookings"]. Write a negotiation email that: opens by affirming genuine interest in working with this specific vendor (not just as a setup to the ask), states the specific ask clearly with a real reason, offers something of value in return if applicable, and closes with an invitation to find a solution — not an ultimatum. Under 200 words. Tone: direct and collaborative — the best vendor negotiations preserve the relationship. Be honest about what you need without being adversarial.10. Vendor Confirmation and Briefing Email
Send a pre-event vendor briefing that eliminates day-of confusion and ensures every vendor knows exactly what's expected.
Write a vendor briefing email to send 1–2 weeks before an event. Event name: [NAME OR DESCRIPTION]. Event date: [DATE]. Venue: [NAME + ADDRESS]. Vendor name: [NAME]. Vendor's scope: [DESCRIBE SPECIFICALLY — what they're doing and delivering]. Setup window: [E.G. "load-in begins at 2:00 PM, event starts at 6:00 PM"]. Teardown window: [E.G. "teardown must be complete by midnight"]. Day-of parking and load-in instructions: [DESCRIBE — or "to be confirmed"]. Key contacts on event day: [PLANNER NAME + PHONE, VENUE COORDINATOR NAME + PHONE]. Special instructions for this vendor: [ANY SPECIFICS — e.g. "catering must use the service entrance on Oak Street," "photographer should avoid the stage area until the reveal at 7:30 PM"]. Write a briefing email with: a clean event overview (name, date, venue), their confirmed scope, a timeline of key time markers that affect them, day-of logistics (load-in, parking, contacts), and any special instructions. Format: scannable with headers. Under 400 words. Tone: operational and complete — the best vendor briefings eliminate every logistical question so vendors can do their job without calling you on event day.11. Post-Event Vendor Review Email
Write a post-event vendor feedback email that builds long-term relationships — even when you have honest criticism to share.
Write a post-event vendor feedback email. Vendor name and category: [NAME + CATEGORY]. Event: [DESCRIBE BRIEFLY — type, date]. What went well: [LIST 2–3 SPECIFIC THINGS — not generic, cite actual moments or decisions]. What could be improved: [LIST 1–2 SPECIFIC THINGS — honest and constructive]. Whether I plan to use this vendor again: [YES / POSSIBLY / NO — and the brief honest reason]. Write a feedback email that: opens with a specific, genuine acknowledgment of something this vendor did well — not "great working with you!"; addresses any improvement areas directly but professionally — not passive-aggressively; communicates your future intent clearly; and if you plan to use them again, signals that warmly. Under 200 words. Tone: honest and professional — vendor relationships are long-term assets. The best feedback email is one a vendor can actually act on. Don't write a complaint; write a professional review.Section 3: Run-of-Show & Timeline Drafting (Prompts 12–16)
The run-of-show and logistics documents are what separate events that feel effortless from those that feel chaotic. These prompts help you build complete run-of-show timelines, setup checklists, staff briefings, speaker briefings, and contingency plans that hold up under pressure.
12. Full Run-of-Show Document
Build a complete minute-by-minute run-of-show that every vendor and staff member can work from on event day.
Write a complete run-of-show document for the following event. Event name: [NAME]. Event date: [DATE]. Venue: [NAME + ADDRESS]. Guest count: [NUMBER]. Event format: [DESCRIBE — e.g. "cocktail reception followed by seated dinner and awards ceremony," "one-day conference with breakout sessions," "product launch with presentation and networking"]. Key event segments and approximate timing: [LIST — e.g. "registration: 5:30–6:00 PM," "welcome reception: 6:00–7:00 PM," "dinner service: 7:00–9:00 PM," "awards: 8:30 PM," "dancing: 9:00–11:00 PM"]. Key personnel: [LIST — host, MC or emcee, speakers, AV lead, catering captain, photographer, event planner]. Write a run-of-show with: a header section (event name, date, venue, key contacts with cell numbers), a minute-by-minute timeline from vendor setup through teardown, for each time block: exact time, activity, who is responsible, and notes or cues, a vendor arrival and departure schedule, and a contingency section addressing the 3 most likely timing disruptions for this event type. Format: clean table or structured list that can be printed or used on a phone. Tone: operational and precise — every line should have a clear owner and a clear action. No vague entries like "dinner continues" — every minute should be accounted for.13. Event Setup Timeline and Checklist
Draft a setup timeline that coordinates every vendor arrival, transforms the venue without conflicts, and has the space ready before the first guest arrives.
Write a setup timeline and checklist for an event. Event name: [NAME]. Venue access start time: [E.G. "8:00 AM"]. Event start time (doors open to guests): [E.G. "6:00 PM"]. Vendors arriving for setup: [LIST — e.g. "floral: 9:00 AM," "AV: 10:00 AM," "catering: 2:00 PM," "lighting: 8:00 AM"]. Event setup elements to coordinate: [LIST — e.g. "guest seating and table layouts," "stage and AV setup," "bar setup," "registration desk," "décor and florals," "signage and branding"]. Any venue constraints or sequencing rules: [E.G. "AV must finish rigging before floral can come in," "floor must be cleared before tables set"]. Write a setup timeline that: maps each vendor's arrival window and scope, sequences setup activities to avoid vendor conflicts, identifies the critical path (what must be done before anything else can proceed), includes a pre-event walkthrough checkpoint 45–60 minutes before doors open, and lists a setup completion checklist organized by area (entrance, registration, main room, catering, restrooms, emergency). Format: timeline block followed by area-by-area checklist. Under 600 words. Tone: operational — setup timelines are coordination documents, not narratives. Every entry should have a time, an owner, and an outcome.14. Day-of Staff Briefing Document
Write a staff briefing that aligns your team on roles, responsibilities, and standards before the doors open.
Write a day-of event staff briefing document. Event name: [NAME]. Event date, time, and venue: [DETAILS]. Total event staff: [NUMBER]. Staff roles and assignments: [LIST — e.g. "registration desk: [NAME]," "guest services / floor: [NAME]," "vendor liaison: [NAME]," "AV point of contact: [NAME]"]. Key moments requiring coordinated attention: [LIST — e.g. "guest arrival 5:30–6:30 PM," "program start 7:00 PM," "dinner service transition 8:00 PM"]. Guest experience standards for this event: [DESCRIBE SPECIFICALLY — e.g. "no guest waits more than 90 seconds at check-in," "every guest acknowledged within 30 seconds of entering the main room," "food allergies confirmed at seating"]. Communication protocol: [E.G. "radio check-in every 30 minutes," "all issues escalate to [NAME] first"]. Emergency contact: [NAME + PHONE]. Write a staff briefing with: event overview (name, type, format, guest count, times), individual role assignments and key responsibilities for each, timeline of key moments where all staff attention is required, guest experience standards, escalation and communication protocol, and emergency contact information. Format: clean and skimmable with bold headers. Under 400 words. Tone: direct and operational — this gets read once before the event. Important instructions must stand out.15. Speaker or Presenter Briefing
Write a presenter brief that sets every speaker up for success — and eliminates last-minute chaos.
Write a speaker or presenter briefing document. Event name: [NAME]. Event date and time: [DETAILS]. Venue: [NAME + ADDRESS]. Speaker name: [NAME]. Their role: [E.G. "keynote speaker," "panel moderator," "awards presenter," "emcee"]. Presentation time slot: [TIME + DURATION]. AV setup: [DESCRIBE — e.g. "podium microphone + wireless clicker, 16:9 screens, confidence monitor at stage edge"]. Slide submission requirements: [E.G. "submit slides in PowerPoint by [DATE]" — or "no slides"]. Green room or speaker arrival: [WHERE TO GO, WHEN]. Sound check time: [IF APPLICABLE]. Day-of contact: [NAME + PHONE]. What the speaker should know about the audience: [BRIEF CONTEXT — size, professional background, energy level expected]. Write a speaker briefing with: event overview (name, date, format, audience), their specific role and what to expect, arrival and green room instructions, technical setup and slide requirements, what the run-of-show looks like around their slot (what comes before and after), and the day-of contact. Under 350 words. Include a brief "what to expect on the day" section so they walk in confident. Tone: organized and reassuring — a well-briefed speaker shows up on time and focused. This document should eliminate every logistical question they have in advance.16. Event Day Contingency Plan
Write a contingency plan for the most likely event-day problems — so you're never making decisions under pressure without a plan.
Write an event contingency plan for the following event. Event name: [NAME]. Event type: [DESCRIBE]. Event date and venue: [DETAILS]. Write a contingency plan covering the 7 most common event-day problems with a response protocol for each: (1) A key vendor (catering, AV, entertainment) cancels or fails to show, (2) The event runs significantly behind schedule, (3) Technical AV failure during a live presentation or program moment, (4) Guest count arrives significantly over or under RSVP, (5) A medical emergency involving a guest or staff member, (6) A serious weather issue (for outdoor or partially outdoor events), (7) A speaker or featured guest cancels last minute. For each scenario: state the problem, describe the immediate first response (who does what in the first 5 minutes), outline the resolution path, and identify who has final decision-making authority. Format: numbered scenarios with bold headers and bullet-point response steps. Under 500 words. Tone: operational and direct — a contingency plan is a decision tree for high-pressure moments. It needs to be readable in 30 seconds while stressed. Every entry must have a clear owner.Section 4: Social Media & Promotional Copy (Prompts 17–21)
Whether you're promoting your own events or creating marketing deliverables for clients, every event needs social media packs, countdown posts, highlight reel scripts, sponsor mentions, and email sequences. These prompts cover the full event marketing workflow across platforms.
17. Event Announcement — Multi-Platform Social Pack
Write a launch social media pack for an upcoming event across Instagram, LinkedIn, and Facebook.
Write a social media announcement pack for an upcoming event. Event name: [NAME]. Event type: [DESCRIBE — e.g. "annual gala," "brand activation," "private corporate dinner," "ticketed fundraiser"]. Date, time, and venue: [DETAILS]. Who should attend: [DESCRIBE THE TARGET AUDIENCE]. What makes this event special: [LIST 2–3 SPECIFIC DRAWS — speaker, cause, experience, exclusivity]. Registration or ticket link: [URL]. Write the following posts: (1) Instagram announcement (100–130 words): Hook opening — what the event offers, not just what it is. Visual description suggestion in brackets. 3–5 targeted hashtags. CTA with link. (2) LinkedIn announcement (150–180 words): Professional framing. Focus on value for the audience. More context, less hashtags. Tag key people if applicable. (3) Facebook event post (130–160 words): Conversational and community-focused. Full logistics in the copy. RSVP/ticket CTA. (4) Short-form story/reel hook (under 15 seconds, written as spoken script): 1 opening claim that creates curiosity or excitement. CTA at end. For each post: write the full caption, note any visual direction in brackets, and include a note on the tone adjustment per platform. Tone: energetic but accurate — event promotion copy loses credibility when it oversells. Write to the actual audience with specificity.18. Countdown Post Series — 5 Posts
Write a 5-post countdown series that builds genuine anticipation without feeling repetitive.
Write a 5-post countdown series to build anticipation for an upcoming event. Event name: [NAME]. Event date: [DATE]. What I want audiences to feel across this series: [DESCRIBE — e.g. "excited, like they can't miss it," "credible and confident in the quality of the event," "urgency to register before it sells out"]. Key details to feature across the series: [LIST — e.g. "speakers," "entertainment," "venue reveal," "ticket deadline," "cause or mission"]. Register/ticket link: [URL]. Write 5 countdown posts on the following schedule: Post 1 (2 weeks out — "Save the Date" or event reveal): Create intrigue. Tease the event without revealing everything. Post 2 (10 days out — venue or experience reveal): Show what the event looks or feels like. Make people picture themselves there. Post 3 (7 days out — speaker or programming spotlight): Feature the most compelling program element. Post 4 (3 days out — urgency): Direct and honest urgency (ticket numbers, deadline, capacity). Post 5 (day before — "Tomorrow" post): Short and energetic. Final CTA for last-minute registrations. For each post: write the full caption (under 120 words), note the platform (Instagram + LinkedIn + Facebook unless specified), and include a hook-first opening — never start with "Only X days until [EVENT]." Tone: build across the series from intrigue to excitement to urgency.19. Event Highlight Reel Script
Script a 60-second highlight reel that captures the energy of the event and drives interest in next year.
Write a script for a 60-second event highlight reel video for social media. Event name: [NAME]. Event type and brief description: [DESCRIBE]. 3–5 most memorable moments or visuals from the event: [DESCRIBE EACH IN 1–2 SENTENCES — e.g. "the venue reveal when doors opened," "the awards moment," "the packed dance floor at 10 PM"]. Key stat or milestone: [E.G. "350 guests," "raised $120,000," "sold out in 3 days"]. Platform: [INSTAGRAM REELS / TIKTOK / YOUTUBE SHORTS]. What I want viewers to feel: [DESCRIBE — e.g. "they missed out and want to attend next year," "confidence in the event brand"]. Write: (1) A 10-second opening hook (on-screen text or spoken voice): the most compelling single claim or image from the event. (2) 3 clip transition lines (under 10 words each): brief spoken or on-screen bridges that connect highlight clips with narrative momentum. (3) A 10-second close: invite viewers to register for the next event, follow for updates, or visit the link in bio. Format as a production script with time markers and direction notes. Total spoken word count: under 120 words. Tone: energetic and specific — this reel competes for 3 seconds of attention. Every second must earn the next.20. Sponsor Thank-You and Mention Copy
Write sponsor mention copy that fulfills obligations, looks professional, and makes the sponsor feel genuinely valued.
Write social media sponsor acknowledgment copy for an event. Sponsor name: [NAME]. Sponsor tier: [E.G. "title sponsor," "gold sponsor," "presenting sponsor," "community partner"]. What the sponsor contributed: [DESCRIBE — monetary amount or in-kind, or just their category]. Event name: [NAME]. Sponsor's social handle: [IF APPLICABLE]. What I promised them in terms of social mentions: [E.G. "3 posts across event week," "1 pre-event feature," "1 post-event thank-you"]. Write the following: (1) Pre-event sponsor feature post (Instagram + LinkedIn versions): Feature the sponsor specifically — not just a logo mention. Reference what they're contributing and why it matters to the event. Tag them. Under 100 words. (2) Day-of mention (Instagram Story script — 15 seconds spoken): Warm, genuine, brief. Reference the sponsor by name and their contribution. (3) Post-event thank-you post (Instagram + LinkedIn versions): Acknowledge the sponsor with specificity — what their support made possible. Tag them. Under 100 words. For each post: write the full copy, note any image direction (e.g. "logo placement," "photo from event with sponsor rep"), and include relevant hashtags. Tone: genuine and specific — sponsor posts that feel like PR fluff damage relationships. Write as if this sponsor genuinely made the event better.21. Email Invitation Sequence — 3 Emails
Write a 3-email sequence that converts cold invitees to confirmed attendees without spamming.
Write a 3-email invitation sequence to drive registrations for an event. Event name: [NAME]. Event type and format: [DESCRIBE]. Date and venue: [DETAILS]. Target attendee: [DESCRIBE — who they are and why this event is specifically relevant to them]. The 3 most compelling reasons to attend: [LIST]. Registration link: [URL]. Any early-bird pricing or deadline: [IF APPLICABLE]. Email 1 (initial invitation — 3 weeks out): Build desire. Make the event feel like a genuine opportunity, not an obligation. Don't lead with logistics — lead with what they'll get or experience. Email 2 (follow-up — 10 days before): Overcome the most likely hesitation. Add social proof, a programming highlight, or a deadline signal. Personalize the opening. Email 3 (last chance — 3 days before): Direct and specific. Final registration reminder with clear deadline. Acknowledge it's the last email. For each email: write the subject line, preview text, and full body. Under 200 words per email. Tone: vary across the sequence — Email 1 is expansive and inviting, Email 2 is persuasive with a specific reason, Email 3 is direct and final. Never open with "Just a quick reminder."Section 5: Post-Event Recaps & Thank You Notes (Prompts 22–26)
The post-event window is where event planners build lasting client relationships, collect feedback that improves future events, and position themselves for the next contract. These prompts cover client debrief reports, thank-you notes to clients and vendors, attendee thank-yous, and feedback surveys.
22. Client Post-Event Debrief Report
Write a professional post-event debrief that demonstrates your value, documents what happened, and positions you for the next engagement.
Write a post-event debrief report to deliver to a client after an event. Client name: [NAME]. Event name: [NAME]. Event date and venue: [DETAILS]. Guest count — expected vs. actual: [BOTH NUMBERS]. Budget — allocated vs. final spend: [BOTH AMOUNTS]. What went well: [LIST 4–5 SPECIFIC THINGS — not generic]. What could be improved for next time: [LIST 2–3 HONESTLY — be constructive, not self-protective]. Vendor performance summary: [BRIEF — which performed well, which had issues]. Guest feedback or reactions: [QUOTE OR SUMMARIZE — formal survey or informal comments]. Your recommendation for the next event: [1–2 KEY CHANGES YOU'D MAKE]. Write a debrief report with: event summary (name, type, date, final attendance), budget overview (summary table — budgeted vs. actual by category), what went well (specific, not general), opportunities for improvement (honest and actionable), vendor performance summary (brief ratings), guest feedback summary, and your recommendation for the next event. Under 600 words. Format: professional memo with headers. Tone: honest and credible — the best debrief reports don't spin everything as a success. Clients who receive honest, specific analysis bring their planner back.23. Thank-You Email to Client
Write a post-event thank-you that closes the engagement on a high note and opens the door for future work.
Write a post-event thank-you email to a client. Client name: [NAME]. Event: [DESCRIBE BRIEFLY]. What I most want to acknowledge: [DESCRIBE — e.g. "their trust in my judgment during a high-pressure moment," "how smoothly the budget collaboration worked," "the client's contribution to making the event possible"]. A specific moment from the event I want to reference: [DESCRIBE — a genuine, memorable detail that shows I was present and paying attention]. Whether I'd like to work with them again: [YES / STRONGLY — be direct]. What I'll be following up with: [E.G. "the debrief report," "vendor invoices," "survey results"]. Write a thank-you email that: opens with a specific observation about the event — not "what a wonderful evening!"; genuinely acknowledges what made this client or this event relationship distinctive; references one specific moment from the event; communicates follow-up next steps; and if I'd like to work with them again, makes that clear without being transactional about it. Under 200 words. Tone: warm and professional — a well-written post-event thank-you is one of the highest-ROI 5 minutes in event planning. Don't write a template; write something they'll remember.24. Thank-You Notes to Vendors and Venue
Write vendor and venue thank-you notes that build the relationships you'll rely on for years.
Write a post-event thank-you email to a vendor or venue partner. Vendor name: [NAME + CATEGORY — e.g. "Oak & Ember Catering"]. Event: [DESCRIBE BRIEFLY — type, date, scale]. What specifically they did well: [DESCRIBE — 1–2 concrete moments or aspects, not "the food was great"]. Whether I plan to work with them again: [YES / LIKELY]. Whether I'll refer them to others: [YES / PROBABLY]. Write a thank-you that: opens with a specific, genuine acknowledgment of something this vendor did exceptionally (not "Great working with you!"); expresses appreciation without padding; communicates whether I plan to bring them back; and if I'll refer them, makes that explicit in a way they can quote. Under 150 words. Tone: warm, professional, and specific — vendor thank-you notes are one of the most underused relationship tools in event planning. A specific note after every event builds a vendor network that goes above and beyond in return. Do not write the same email to every vendor. Write it for this specific vendor and what they did.25. Attendee Post-Event Thank-You Email
Write a post-event thank-you to attendees that closes the experience on a high and builds loyalty for the next event.
Write a post-event thank-you email to send to all attendees after an event. Event name: [NAME]. Event date: [DATE]. What went especially well or what I most want to acknowledge: [DESCRIBE 1–2 HIGHLIGHTS]. Any stat or milestone worth noting: [E.G. "we raised $90,000," "400 attendees," "most attended event in our 8-year history"]. What's next: [E.G. "save the date for next year," "upcoming event series," "resources available from the event"]. Any specific ask: [E.G. "fill out the feedback survey," "share your photos on social with #HASHTAG," "pre-register for next year"]. Write a thank-you email that: opens with a specific, genuine reflection on the event — what made this one different; acknowledges attendees as central to why the event worked; shares a meaningful stat or highlight if relevant; communicates what's next in a way that creates anticipation; and closes with one specific ask that feels like a natural invitation. Under 200 words. Tone: warm and personal — post-event emails have high open rates because the experience is fresh. Don't waste the opportunity on generic copy.26. Attendee Feedback Survey
Write a post-event survey that collects actionable data — not vanity metrics — in under 5 minutes.
Write a post-event attendee feedback survey. Event name: [NAME]. What I most want to learn from this survey: [LIST 3 THINGS — e.g. "overall satisfaction, what elements were most and least valuable, likelihood to attend again"]. Survey platform: [E.G. "Google Forms," "Typeform," "email reply"]. Write a survey with 8–10 questions covering: (1) Overall event satisfaction (1–10 scale + open text: "What made you give that score?"), (2) What they valued most about the event, (3) What felt missing or could be improved, (4) Venue and logistics rating (5-point scale), (5) Programming or content rating (if applicable), (6) Catering or food experience rating, (7) Likelihood to attend the next event (1–10 scale), (8) Would they recommend this event to a colleague (NPS: 0–10), (9) Open-ended: "What's the one change that would make the next event unmissable for you?", (10) Optional: name and email for follow-up. Keep to 10 questions maximum. Include scale options for quantitative questions and open fields for qualitative ones. Tone: concise and genuine — the best post-event surveys feel like honest curiosity, not administrative obligation. Every question should have a clear reason for existing.Section 6: Upsell & Repeat Business Follow-Ups (Prompts 27–31)
The most valuable events business comes from clients who keep coming back. These prompts handle re-engagement emails to past clients, annual retainer pitches, service upgrade offers, referral requests, and year-end newsletters that keep your name at the top of the list when the next event comes up.
27. Re-Engagement Email to Past Client
Write a re-engagement email to a past client that opens conversation for future events without feeling pushy.
Write a re-engagement email to a past event planning client. Client name: [NAME]. Event I planned for them: [DESCRIBE — type, date]. What we worked well on together: [DESCRIBE — 1 specific thing that made the relationship work]. How long it's been since the event: [E.G. "3 months," "6 months," "nearly a year"]. What might be coming up for them: [DESCRIBE WHAT YOU KNOW OR SUSPECT — e.g. "their annual gala is typically in Q4," "they're a growing company that likely has upcoming events," "they mentioned a product launch earlier in the year"]. What I'm offering or proposing: [DESCRIBE — e.g. "early booking for next year's event," "a planning call to discuss any upcoming needs," "a new service I'm offering"]. Write a re-engagement email that: opens with a specific reference to their event — a genuine callback, not a "hope you're well"; notes naturally that time has passed; references what might be coming up for them (without assuming too much); makes an offer or a simple ask to reconnect; and closes with a low-pressure CTA. Under 200 words. Tone: warm and relationship-focused — the best re-engagement emails don't feel like sales outreach. They feel like a professional checking in on someone they actually cared about working with.28. Annual Event Planning Proposal Pitch
Write an annual event retainer or planning package pitch for a client who runs recurring events.
Write an annual event planning pitch to a client who runs recurring events and currently hires me event-by-event. Client name: [NAME]. Events they run annually: [LIST — e.g. "Q1 team off-site," "summer client appreciation event," "Q4 holiday gala"]. Total number of events per year: [NUMBER]. What they currently spend hiring me per event: [APPROXIMATE]. What I'm proposing: [DESCRIBE — e.g. "an annual planning retainer," "an event package pricing structure," "a preferred planner agreement"]. Key benefits for them: [LIST — e.g. "priority availability," "volume pricing," "dedicated planning time each month," "first access to venue holds"]. What I want from the relationship: [E.G. "predictable revenue," "a longer planning horizon," "more creative influence"]. Write a pitch email that: opens by referencing the history we've built together (genuine, not flattery); frames the annual arrangement as a benefit to them (not "I want more consistent revenue"); outlines the specific structure I'm proposing; states the pricing or investment clearly; and closes with a specific next step — a call to discuss, not a passive "let me know." Under 300 words. Tone: confident and collaborative — annual engagement pitches work when they're framed as a partnership benefit, not a sales ask.29. Service Upgrade / Upsell Email
Write an upsell email that introduces an upgraded service tier at the right moment — without feeling sales-y.
Write an upsell email to introduce an additional or upgraded service to an existing client. Client name: [NAME]. Current service they're receiving: [DESCRIBE — e.g. "day-of coordination only," "venue sourcing," "partial planning package"]. Upgraded service I'm offering: [DESCRIBE SPECIFICALLY — e.g. "full-service planning," "a social media promotion package," "vendor management add-on"]. What problem it solves for them: [DESCRIBE — what gap in their current setup this addresses]. What prompted me to bring this up now: [E.G. "they mentioned being overwhelmed by vendor coordination," "the event is growing and the current scope doesn't cover it," "they're adding a new event element that needs more management"]. Price of the upgrade: [$AMOUNT — or "I can send a quote"]. Write an upsell email that: opens with a reference to something specific about their current event or a moment from our work together; identifies the gap or opportunity directly — don't bury it; introduces the upgraded service as a solution to their specific situation; states what's included and the investment clearly; and closes with a low-pressure next step. Under 200 words. Tone: advisory and specific — the best upsell emails don't feel like upsells. They feel like a planner noticing something the client needs and offering a solution.30. Referral Request Email
Write a referral request email that makes it easy for happy clients to send you business — without the awkward ask.
Write a referral request email to send to a satisfied past client. Client name: [NAME]. Event I planned for them: [DESCRIBE — type, date]. How the event went: [DESCRIBE — specifically, what they were happy with]. What type of referrals would be valuable to me: [DESCRIBE — e.g. "corporate clients in the [INDUSTRY] space," "companies planning events over [SIZE]," "anyone planning a gala or formal event in [CITY]"]. Whether I offer a referral incentive: [YES — describe / NO — be honest about it]. Write a referral request email that: opens with a genuine, specific callback to their event — what made it successful, a moment that stood out; makes the ask naturally and directly — don't bury it or apologize for asking; explains exactly what kind of referral would be valuable and why; makes the mechanics of referring easy (who to send, what to say, or what link to share); and acknowledges the referral with what you'll do for them (update them on outcomes, referral credit if applicable, genuine gratitude). Under 200 words. Tone: direct and grateful — the best referral requests feel like a natural extension of a good relationship, not a sales script. A satisfied client who knows exactly who to refer you to and how to do it easily will act.31. Year-End Portfolio and Planning Newsletter
Write a year-end newsletter to your client list that showcases your work and opens conversations for next year.
Write a year-end newsletter email to send to your past clients and prospects. My name / company: [NAME]. Year: [YEAR]. Events I want to highlight this year: [LIST 2–3 — describe each briefly: type, what made it notable]. A milestone or stat from the year: [E.G. "planned 14 events," "managed $2.4M in event budgets," "worked with 9 repeat clients"]. A lesson or insight I gained this year: [1–2 SENTENCES — something genuine and professional, not generic]. What I'm offering or interested in planning next year: [DESCRIBE — types of events, new services, booking availability]. Early booking incentive (if any): [DESCRIBE — or "I'm happy to discuss priority scheduling"]. Write a year-end newsletter with: a brief personal opening from me (warm and genuine — not a generic "what a year!"), 2–3 event highlights with a sentence on what made each one memorable, a year-in-numbers section (1–3 stats), my professional insight or reflection from this year, a look ahead — what I'm excited to plan and my availability, and a clear CTA for scheduling a planning call for next year's events. Under 450 words. Tone: personal and credible — a year-end newsletter works when it reads like a genuine professional update, not a marketing email.Get all 31 prompts
Unlock the full list — plus Professional client onboarding templates for service businesses — for just $29
Unlock Now — $29Instant download · Digital product — no shipping or physical delivery.
Get the Client Onboarding Kit →
The Client Onboarding Kit includes professional onboarding templates, intake forms, welcome sequences, and communication frameworks for service businesses — including event planners. Start every client relationship on solid ground. One payment, instant download.
Get the Client Onboarding Kit — $29 →Event planners who use AI well aren't replacing their professional judgment, their vendor relationships, or their eye for what makes an event memorable. They're using it to eliminate the hours spent producing documents that follow a predictable structure — discovery briefs, vendor emails, run-of-show timelines, post-event reports, and follow-up sequences that are necessary but not where your professional value lives. These 31 prompts give you that time back. For more professional prompt libraries, see our guide to ChatGPT prompts for project managers and our post on ChatGPT prompts for virtual assistants.