35 ChatGPT Prompts for Event Planners: Timelines, Vendor Management, and Attendee Experiences That Work

Write an event concept brief for the following event:

Client/organization: [NAME]
Event type: [CONFERENCE / GALA / CORPORATE RETREAT / PRODUCT LAUNCH / TRADE SHOW / ETC.]
Audience: [WHO WILL ATTEND AND APPROXIMATELY HOW MANY]
Purpose: [WHAT THE EVENT IS MEANT TO ACHIEVE]
Date and location: [DATE, CITY, VENUE IF KNOWN]
Budget: [APPROXIMATE RANGE]

The brief should include:
- Event theme and positioning statement
- Three core experience goals (what attendees should feel, learn, or do)
- Three elements that will make this event memorable
- Success metrics (how we know the event worked)
- Key risks and initial mitigation ideas

Write a set of discovery questions to ask a new client at the first planning meeting for a [EVENT TYPE].

The questions should uncover:
- The business or strategic objective behind the event
- Budget flexibility and non-negotiables
- Audience profile and expectations
- Constraints (dates, venues, brand guidelines, approvals)
- How success will be measured and by whom
- Past event history and what worked or failed

Include 3 warm-up relationship questions, 8 core event strategy questions, and 3 post-meeting questions to send via email if they weren't covered. Provide one follow-up probe for the 3 most important questions.

Write a one-paragraph event positioning statement for:

Event name: [NAME]
Event type: [TYPE]
Host organization: [ORGANIZATION]
Target attendee: [WHO THEY ARE AND WHAT THEY DO]
Core promise: [WHAT THEY WILL GET FROM ATTENDING]
Differentiation: [WHAT MAKES THIS DIFFERENT FROM OTHER EVENTS IN THIS SPACE]

The positioning statement will be used to:
- Guide all creative and copy decisions
- Brief vendors and partners
- Write the event website and marketing copy

Write in third person. Under 100 words.

Create an initial budget allocation framework for a [EVENT TYPE] with a total budget of [AMOUNT].

Expected attendance: [NUMBER]
Location type: [IN-PERSON / VIRTUAL / HYBRID]
Event duration: [HOURS OR DAYS]
Client priority categories: [LIST WHAT THEY CARE MOST ABOUT — e.g., production quality, food and beverage, speaker experience]

Allocate the budget across these categories:
- Venue and logistics
- Food and beverage
- Audio/visual and production
- Entertainment and programming
- Marketing and communications
- Staffing
- Contingency (minimum 10%)

Show as percentages and dollar amounts. Flag where the biggest trade-off decisions will arise.

Create a risk register for [EVENT NAME], a [EVENT TYPE] with [ATTENDANCE] expected on [DATE] in [LOCATION].

Identify at least 12 risks across these categories:
- Weather and venue
- Vendor/supplier
- Technology and AV
- Speaker or talent
- Health and safety
- Budget and financial
- Attendance and registration
- Reputational or PR

For each risk:
- Likelihood (1-3)
- Impact (1-3)
- Risk score
- Mitigation strategy
- Contingency if mitigation fails
- Owner

Sort by risk score descending.

Write a Request for Proposal (RFP) for an event venue to host [EVENT NAME].

Event details:
- Date: [DATE]
- Expected attendance: [NUMBER]
- Event type: [TYPE]
- Activities: [LIST — e.g., general sessions, breakouts, dinner, exhibition]
- Location preference: [CITY OR AREA]
- Budget range for venue: [RANGE]

The RFP should request:
- Venue capacity and room configurations
- F&B minimums and catering options
- AV/technology capabilities
- Accommodation room block options
- Accessibility features
- Deposit, payment terms, and cancellation policy
- References from similar events

Include evaluation criteria we'll use to compare proposals.

Create a vendor comparison matrix for selecting [VENDOR TYPE — e.g., caterer, AV company, photographer] for [EVENT NAME].

Vendors being evaluated: [LIST VENDOR NAMES]
Budget: [BUDGET FOR THIS VENDOR CATEGORY]
Non-negotiable requirements: [LIST]

Evaluation criteria (customize as needed):
- Price vs. budget fit
- Portfolio and relevant experience
- References and reputation
- Contract flexibility
- Responsiveness in the RFP process
- Unique value or differentiator

Create a weighted scoring matrix where weights reflect our priorities. Score each vendor from 1-5 per criterion. Include a recommendation with rationale.

Prepare a negotiation brief for a call with [VENDOR NAME] about their proposal for [EVENT NAME].

Their proposal: [SUMMARY OF WHAT THEY'VE OFFERED AND AT WHAT PRICE]
Our budget: [WHAT WE CAN ACTUALLY SPEND]
Gap to close: [DIFFERENCE]
What we value most in their proposal: [THE THINGS WE DON'T WANT TO LOSE]
What we're flexible on: [WHAT WE COULD GIVE UP]

For the negotiation call:
- Opening statement
- 3 points of leverage we have
- 3 concessions we could offer (in order of preference)
- Fallback position (what we'd accept as minimum terms)
- Walk-away point (what makes this vendor not worth pursuing)

Create a budget tracking template for [EVENT NAME] with a total budget of [AMOUNT].

Budget categories: [LIST OR USE STANDARD EVENT CATEGORIES]
Tracking fields needed:
- Budgeted amount
- Contracted/committed amount
- Invoiced amount
- Paid amount
- Variance
- Notes

Add:
- A summary section at the top showing total budget, total committed, total paid, and remaining budget
- A flag system for items that are over budget or at risk
- A section for budget changes and approvals log

Format as a spreadsheet structure with clear column headers and formulas noted.

Create a vendor contract review checklist for event contracts.

Use for: [VENUE / CATERING / AV / SPEAKERS / ENTERTAINMENT]

The checklist should verify:
- Services scope and deliverables (specific, not vague)
- Pricing and payment schedule
- Cancellation and attrition clauses
- Force majeure language
- Liability and insurance requirements
- Intellectual property rights (for photography, video, branded content)
- Performance standards and remedies
- Exclusivity clauses
- Amendment process

Flag the 3 most commonly problematic clauses in [VENUE / CATERING / AV] contracts and what to look for.

Create a master planning timeline for [EVENT NAME], scheduled for [DATE].

Event details:
- Type: [EVENT TYPE]
- Scale: [ATTENDANCE, NUMBER OF SESSIONS, LOCATIONS]
- Today's date: [DATE — so we can calculate backwards]

Build a reverse timeline from event day to now with milestones for:
- Venue and vendor contracts
- Speaker/talent confirmation
- Marketing and registration launch
- Sponsorship deadlines
- AV and production planning
- Attendee communications
- Week-of preparation
- Day-of execution
- Post-event close-out

Mark critical path items (if delayed, the whole event is affected) in bold.

Write a run of show (ROS) for [EVENT NAME] on [DATE].

Venue: [VENUE NAME]
Event type: [TYPE]
Program: [PASTE YOUR AGENDA OR LIST THE PROGRAM ELEMENTS]

For each agenda item, include:
- Start time and end time
- Owner/responsible party
- Location (room or stage)
- AV/tech requirements
- Cue notes for stage manager or AV team
- Pre-event prep notes (setup required before this item)
- Buffer notes (where there's flex time built in)

Flag hard stops (items that cannot run over) in bold. Format as a table.

Write a day-of briefing document for [EVENT NAME] staff and volunteers.

Event date: [DATE]
Venue: [VENUE]
Total staff/volunteers: [NUMBER AND ROLES]
Event schedule: [SUMMARY]

The briefing should cover:
- Event overview and goals (1 paragraph)
- Staff roles and responsibilities (table)
- Venue layout and key locations
- Communication protocol (who to contact for what, radio channels)
- Escalation chain for problems
- Common scenarios and how to handle them
- What "success" looks like at the end of the day

Format for printing as a 1-2 page handout.

Write a contingency plan for [EVENT NAME] addressing the following scenarios:

1. [SCENARIO 1 — e.g., keynote speaker cancels day-of]
2. [SCENARIO 2 — e.g., AV system failure during main session]
3. [SCENARIO 3 — e.g., venue becomes unavailable 2 weeks before]
4. [SCENARIO 4 — e.g., severe weather forces indoor event outdoors]
5. [SCENARIO 5 — e.g., attendance is 30% lower or higher than projected]

For each scenario:
- Trigger (how do we know this is happening)
- Immediate response (first 15 minutes)
- Communication plan (who to tell and how)
- Resolution options (ranked by preference)
- Resources needed and who has authority to approve them

Write an agenda for a 90-minute post-event debrief meeting for the team who planned [EVENT NAME].

Event overview: [BRIEF DESCRIPTION — TYPE, DATE, SCALE]
Team size: [NUMBER]
Key stakeholders attending debrief: [ROLES]

Agenda should cover:
- What went well (20 min — structured, not just verbal)
- What didn't go as planned (25 min — blameless, focused on process not people)
- Attendee feedback summary (15 min)
- Vendor performance review (10 min)
- Budget actuals vs. plan (10 min)
- Action items for next event (10 min)

Include specific discussion questions for each section and a documentation template to capture outputs.

Write an invitation email for [EVENT NAME].

Event details:
- Type and theme: [DESCRIPTION]
- Date, time, location: [DETAILS]
- Audience: [WHO YOU'RE INVITING]
- Key speakers or highlights: [LIST]
- Registration link: [URL]
- Deadline or capacity limit: [IF APPLICABLE]

The email should:
- Open with a compelling reason to attend (not a description of the event)
- Make the value proposition clear in 3 bullets
- Create urgency without being pushy
- Have one clear CTA
- Be under 300 words

Include subject line and preview text.

Write a 3-email pre-event sequence for registered attendees of [EVENT NAME].

Email 1 (Immediately after registration): Confirmation + what to expect
Email 2 ([X] weeks before event): Practical details (agenda, travel, logistics)
Email 3 (2 days before event): Final prep checklist + what to bring

Each email should:
- Reinforce excitement and value
- Give one actionable next step
- Be under 250 words

Include subject lines. The sequence should feel like helpful preparation, not just automated reminders.

Write an invitation email to [SPEAKER NAME], [TITLE/ROLE], inviting them to speak at [EVENT NAME].

Event details:
- Date and location: [DETAILS]
- Audience: [NUMBER AND PROFILE]
- Format requested: [KEYNOTE / PANEL / WORKSHOP / ETC.]
- Topic suggestion: [TOPIC IDEA]
- Honorarium or compensation: [AMOUNT OR "TO BE DISCUSSED"]

The email should:
- Open by noting something specific about their work that makes them right for this event
- Describe the audience clearly and why this is a good opportunity for them
- Make the request specific and easy to respond to
- Leave the door open for topic collaboration

Keep it under 250 words. This is the first touch — not the full brief.

Write a comprehensive FAQ page for [EVENT NAME] attendee registration.

Event type: [TYPE]
Date and location: [DETAILS]
Common questions attendees ask about:
- Registration and tickets
- Location and parking/transit
- Schedule and programming
- Accessibility and accommodations
- Photography and recording policy
- What to wear
- Networking and social events

For each question: write a clear, friendly answer. Flag any question where the answer needs further information from the client or venue. Organize by category with anchor links.

Create a social media content plan for [EVENT NAME] across [PLATFORMS — e.g., LinkedIn, Instagram, Twitter/X].

Event date: [DATE]
Launch date for marketing: [DATE]
Key highlights worth promoting: [SPEAKERS, FEATURES, UNIQUE ELEMENTS]
Hashtag: [HASHTAG]

Plan for three phases:
- Pre-event (6 weeks to day-of): Build anticipation and drive registration
- Live event: Real-time engagement and FOMO creation
- Post-event: Gratitude, highlights, and registration capture for next year

For each week: 2-3 post ideas per platform with copy direction (not full copy), recommended content type (photo, video, story, poll), and optimal posting time.

Create a venue setup checklist for [EVENT NAME] at [VENUE NAME].

Event type: [TYPE]
Rooms/spaces in use: [LIST WITH PURPOSES — e.g., main ballroom for dinner, Room 3 for breakouts]
Setup start time: [TIME]
Event start time: [TIME]

For each space, include:
- Furniture and layout requirements
- AV/tech setup items
- Signage and branding elements
- F&B setup items
- Registration/check-in area items
- Accessibility requirements
- Pre-event inspection checklist (what to check before doors open)

Flag items that require venue staff vs. event staff vs. vendor.

Write a standard operating procedure for the registration desk at [EVENT NAME].

Expected attendance: [NUMBER]
Check-in window: [START TO END TIME]
Technology in use: [CHECK-IN APP / PAPER LIST / BADGE PRINTER / ETC.]
Staff at registration: [NUMBER AND ROLES]

SOP should cover:
- Setup steps before doors open
- Standard check-in flow (step by step)
- How to handle: late additions, name changes, group check-ins, VIP arrivals
- What to do when the system fails
- End-of-check-in close-out steps
- Escalation protocol for complaints at the desk

Create a day-of event communications log template for [EVENT NAME].

The log will be used by the event director to track:
- Issues that arise and how they were resolved
- Vendor communications
- Last-minute changes to program or logistics
- Attendee incidents or complaints
- Budget decisions made on the day

Format as a running log with fields for: time, issue/communication type, who reported it, action taken, resolution, and who is responsible for follow-up.

Include a pre-populated section with known time-sensitive items for the specific event day.

Write a speaker briefing document for [SPEAKER NAME] presenting at [EVENT NAME].

Session details:
- Title: [SESSION TITLE]
- Date, time, location: [DETAILS]
- Format: [KEYNOTE / PANEL / WORKSHOP]
- Allocated time: [DURATION]
- Audience: [NUMBER AND PROFILE]

The briefing should cover:
- Event overview and context (2 paragraphs)
- Audience expectations and sophistication level
- Room setup and AV available
- What to bring (slides, handouts, tech requirements)
- Timing protocol (when to arrive, where to check in, Q&A format)
- Points of contact day-of
- Social sharing guidelines and hashtag

Create an incident report template for events, compliant with standard duty of care requirements.

The template should capture:
- Date, time, location of incident
- Persons involved (attendee, staff, vendor, third party)
- Description of what happened (factual, no opinion)
- Witness information
- First aid or emergency services involvement
- Venue notification
- Organizational notification chain
- Actions taken
- Follow-up required

Add a guidance note to the person completing the form reminding them to be factual, not speculative, and to preserve any physical evidence. The template should be completable within 10 minutes.

Write a sponsorship prospectus for [EVENT NAME].

Event overview: [TYPE, DATE, LOCATION, EXPECTED ATTENDANCE]
Audience profile: [WHO ATTENDS — demographics, professional profile, buying power]
Sponsor categories you're seeking: [e.g., title, gold, silver, media, in-kind]

For each tier:
- Price
- Package inclusions (logo placement, speaking opportunity, booth, tickets, digital exposure)
- Estimated impressions or reach for each inclusion
- Exclusivity terms if applicable

End with a "why sponsor" section (3 compelling reasons specific to this event's audience) and clear next steps for interested sponsors.

Write an onboarding email to a confirmed sponsor of [EVENT NAME].

Sponsor name: [COMPANY]
Sponsorship tier: [TIER AND AMOUNT]
Inclusions agreed: [LIST]
Key upcoming deadlines: [LOGO DUE DATE, AD DEADLINE, BOOTH SETUP, ETC.]
Their point of contact on our team: [NAME AND EMAIL]

The email should:
- Thank them genuinely without sounding like a form letter
- Confirm all agreed inclusions
- List the 3 most urgent action items with due dates
- Set expectations for how communication will work going forward
- Attach or reference the deadline matrix

Under 300 words.

Write a post-event sponsor ROI report for [SPONSOR NAME], a [TIER] sponsor of [EVENT NAME].

Sponsor investment: [AMOUNT]
Inclusions delivered: [LIST — e.g., logo on materials, speaking slot, booth]
Event metrics: [ATTENDANCE, REACH, ENGAGEMENT METRICS]
Sponsor-specific tracking: [e.g., booth scans, lead list size, session attendance, website clicks from event]

The report should:
- Present the metrics clearly with context (e.g., "2,400 unique attendees with 73% matching your target buyer profile")
- Calculate estimated media value or reach value where possible
- Document each promised inclusion and confirm delivery
- End with a re-engagement offer for next year

Keep it under 2 pages. Professional but warm in tone.

Write an exhibitor kit for [EVENT NAME] for sponsors with booth presence.

Event details: [DATE, VENUE, SETUP TIMES]
Booth sizes available: [LIST]
Venue rules: [KEY RESTRICTIONS — e.g., no hard-wall displays, noise levels, electrical limits]

The kit should include:
- Booth specifications and dimensions
- Move-in and move-out schedule
- What's provided vs. what they bring
- Power, Wi-Fi, and equipment ordering instructions
- Catering and staffing rules
- Signage guidelines (brand standards compliance)
- Emergency and venue contacts
- FAQ for first-time exhibitors

Write a media/press partner brief for [EVENT NAME].

Event overview: [TYPE, DATE, SCALE]
Newsworthy angles: [WHAT'S INTERESTING TO PRESS — speakers, announcements, first-of-kind element]
Press access: [WHAT MEDIA CAN DO — attend, photograph, interview speakers, exclusive sessions]
Accreditation process: [HOW THEY APPLY AND WHAT THEY RECEIVE]
On-site press support: [WHO THEY WORK WITH]

The brief should give journalists what they need to pitch a story. Include a "5 story angles" section with specific pitchable angles and the spokesperson for each.

Write a post-event thank you email to attendees of [EVENT NAME].

Event date: [DATE]
Highlights worth referencing: [2-3 MEMORABLE MOMENTS OR ANNOUNCEMENTS]
Next steps you want them to take: [e.g., complete survey, download resources, register for next year]
Survey link (if applicable): [LINK]
Next event date (if applicable): [DATE]

The email should:
- Feel warm and specific to this event — not generic
- Reference something that made this event particular
- Have one primary CTA and one secondary
- Be under 250 words
- Send within 48 hours of event close

Write a post-event survey for [EVENT NAME] targeting [ATTENDEES / SPEAKERS / SPONSORS].

Event type: [TYPE]
Evaluation goals: [WHAT YOU WANT TO LEARN — e.g., overall satisfaction, session quality, logistics, likelihood to return]

Survey design:
- 8-12 questions maximum
- Mix of rating scales (1-5 or NPS format), multiple choice, and 2-3 open text
- Start with overall satisfaction question
- End with one open-ended "anything else" question

For each question: the question text, response format, and what you'll do with the data. Keep completion time under 5 minutes.

Write a post-event recap report for [EVENT NAME] for the client/stakeholder review.

Event overview: [DATE, LOCATION, TYPE]
Attendance: [ACTUAL VS. TARGET]
Budget: [ACTUAL VS. BUDGET — summarized]
Key program moments: [LIST 3-5]
Quantitative results: [SURVEY SCORES, ENGAGEMENT METRICS, SOCIAL REACH, ETC.]
Sponsor/partner delivery: [SUMMARY]
What worked: [TOP 3]
What to improve: [TOP 3]
Recommendations for next year: [LIST]

Format as a professional 2-3 page document with an executive summary (one page) and appendix sections for budget detail and survey data.

Write a vendor performance review for [VENDOR NAME] who provided [SERVICES] for [EVENT NAME].

Contracted deliverables: [WHAT THEY WERE SUPPOSED TO DO]
Actual performance: [WHAT HAPPENED — be specific and factual]
Issues during the event: [LIST ANY PROBLEMS]
Issue resolution: [HOW EACH WAS HANDLED]

Rating per category (1-5 with notes):
- Communication and responsiveness
- Quality of work
- Adherence to timeline
- Problem-solving on the day
- Overall value for money

Overall recommendation: use again / use with conditions / do not use. Include specific evidence for the recommendation. This document will be added to our vendor database.

Create a post-event close-out checklist for [EVENT NAME].

Timeline for completion: [DATE BY WHICH ALL TASKS MUST BE DONE]
Team size handling close-out: [NUMBER AND ROLES]

The checklist should cover:
- Venue (return items, venue sign-off, dispute claims if any)
- Vendor final invoices and payments
- Financial reconciliation and budget close-out
- Attendee follow-up communications
- Sponsor and speaker thank-yous and deliverables
- Media and content (photos, video, recording distribution)
- Documentation archiving (contracts, photos, reports, feedback)
- Team debrief and lessons learned
- Kick-off for next year (if recurring)

Mark each item with owner and deadline. Flag items with financial implications that need approval.