Every event restarts the documentation cycle from scratch. The run-of-show is a blank spreadsheet. The vendor emails get re-explained for the hundredth time. The stakeholder recap gets written at midnight after load-out, when you're running on adrenaline and no one is going to see it until Monday anyway. The documentation work is invisible to sponsors, attendees, and leadership — but it's a full-time job layered on top of the actual logistics job. And it resets completely every single event.
This is distinct from what operations managers do (running business operations processes), what executive assistants handle (supporting executive schedules and travel), and what marketing managers own (producing event content and campaigns). Event planners own the full production cycle — site selection through load-out, vendor management through speaker prep, attendee experience through post-event reporting. The documentation burden is proportional to that scope.
Claude doesn't manage your venue, book your vendors, or coordinate day-of logistics. What it does is handle the templated thinking: the first draft of the ROS, the vendor brief structure, the speaker email sequence, the FAQ doc your attendees actually read. You handle the execution and the relationships — and you don't spend the first three hours of every new event starting from a blank page.
Before you use any of these prompts, the honest constraints: Claude cannot connect to your event management platforms — not Cvent, Eventbrite, Bizzabo, Splash, Whova, or any registration or event ops platform. It has no access to your venue contracts, vendor databases, attendee registration lists, floor plans, AV specs, or live inventory. It cannot send emails, manage RSVPs, or handle any day-of coordination. Every output is a starting draft. Before any Claude-produced document goes to a vendor, speaker, or attendee, verify every logistical detail against your actual contracts and venue specs. Claude writes the structure. You verify the facts.
1. Run-of-Show Script
The ROS is the document everyone needs and nobody wants to write. Claude can produce a formatted, column-structured script from your session list and AV notes — the kind that the stage manager can actually use on the day. Every technical cue line gets a [VERIFY AV SPECS] flag because Claude is working from whatever you paste in, not from your actual AV vendor's spec sheet.
I need a run-of-show script for the following event. Format it as a structured table with these columns: Time, Duration, Session/Cue, Presenter/Talent, AV/Technical Notes, Transition Instructions, Contingency Notes.
Event name: [EVENT NAME]
Date and venue: [DATE, VENUE NAME, CITY]
Event type: [corporate conference / trade show / awards dinner / product launch / etc.]
Session list (paste your full agenda):
[SESSION NAME | START TIME | END TIME | PRESENTER NAME | SESSION FORMAT (keynote / panel / demo / networking / etc.)]
AV cues and technical notes:
[paste whatever AV info you have — slide transitions, video playback moments, mic hand-offs, lighting changes]
Key transitions to flag:
[any transitions that are logistically complex or time-sensitive]
Day-of contacts:
[list names and roles — e.g., Stage Manager: [NAME], AV Lead: [NAME], Green Room: [NAME]]
Hard rule: Add [VERIFY AV SPECS] to every row that references a technical cue or AV action. Do not invent speaker names, session times, or technical specs I haven't provided.
What you get: A table-formatted ROS with every session, transition, and AV cue populated from your session list. The [VERIFY AV SPECS] flags on every technical line are your pre-event QA checklist — run through them with your AV vendor before show day.
2. Vendor Brief
Every vendor needs a brief that covers your event, their specific scope, the deliverables, and the logistics — and every vendor gets a slightly different version. Writing eight vendor briefs from scratch for a single conference is a multi-hour exercise in copy-paste variation. Claude structures it from your inputs with a consistent format and [CONFIRM WITH CONTRACT] flags on every line that references a deliverable or spec.
I need a vendor brief for the following vendor engagement. Structure it with these sections: Event Overview / Your Scope / Deliverables + Timeline / Logistics + Access / Day-of Contacts / Questions for You.
Event name: [EVENT NAME]
Date and venue: [DATE, VENUE, ADDRESS]
Vendor type: [catering / AV / photography / décor / transportation / security / registration / etc.]
Vendor company name: [VENDOR NAME]
Vendor contact: [CONTACT NAME, TITLE, EMAIL]
Event overview (3-4 sentences):
[brief description of the event — audience, format, attendance, vibe]
Vendor scope — what they are responsible for:
[list their specific responsibilities in detail]
Deliverables and timeline:
[list each deliverable with the date/time it's due or needs to be in place]
Logistics and access:
[load-in time, load-out window, access points, parking, any venue-specific rules you know about]
Day-of contacts (your team):
[NAME: ROLE, PHONE | repeat for each key contact]
Any open questions for the vendor:
[list anything you need them to confirm before the event]
Hard rule: Add [CONFIRM WITH CONTRACT] to every line that references a specific deliverable, quantity, or spec. Do not invent logistics details, access times, or specs I haven't provided.
What you get: A structured vendor brief that covers every section a vendor needs to arrive prepared. The [CONFIRM WITH CONTRACT] flags are your contract reconciliation list — before you send, verify every flagged line against the signed agreement. This is especially useful for catering, AV, and photography briefs where the scope details are dense and errors have real consequences on the day.
3. Speaker / Presenter Communication Pack
Speaker communications follow a predictable arc — initial welcome, logistics confirmation, day-before reminder, on-site note. Writing four emails per speaker, across a conference with fifteen speakers, is sixty emails from scratch. Claude writes the full sequence as one prompt output. The logistics lines are populated from what you provide — which means you need to review every venue detail before sending.
I need a speaker communication pack for a presenter at my event. Produce four ready-to-send email drafts: (1) Initial Welcome Email, (2) Logistics Confirmation Email (send 2 weeks out), (3) Day-Before Reminder, (4) On-Site Welcome Note.
Event name: [EVENT NAME]
Event date: [DATE]
Venue: [VENUE NAME, ADDRESS]
Speaker name: [SPEAKER NAME]
Speaker title and company: [TITLE, COMPANY]
Session title: [SESSION TITLE]
Session date/time: [DATE, START TIME – END TIME]
Audience description: [who will be in the room — size, seniority, industry]
Talk length: [XX minutes]
Q&A format: [moderated / open / none — length]
AV setup: [slides via USB / presenter remote provided / Zoom for virtual / etc.]
Green room: [yes/no — location if yes]
Parking/arrival instructions: [what you know — or note that venue is still confirming]
Bio deadline: [DATE]
Headshot deadline: [DATE]
Your name and contact for speaker questions: [YOUR NAME, EMAIL, PHONE]
Tone: professional but warm — speaker should feel looked after, not processed.
Note: do not invent venue logistics or AV specs I haven't provided. Where I've left a detail as TBD, write [TBD — CONFIRM WITH VENUE] so I know to update before sending.
What you get: Four ready-to-edit email drafts covering the full speaker communication lifecycle. Review every logistics line against your actual venue spec before hitting send — Claude writes from what you paste in, and speaker logistics errors are the kind that land in your inbox at 7am on event day.
4. Attendee FAQ and Event Guide
Every event generates the same attendee questions: where do I park, what time does registration open, what's the dress code, who do I contact if something's wrong. A well-structured FAQ doc reduces help desk emails, reduces day-of confusion, and gives your registration team something to hand off. Claude builds the full FAQ from your event details, plus a short "Know Before You Go" summary suitable for email or your event app.
I need an attendee FAQ and event guide for the following event. Structure the FAQ in these sections: Getting There / Check-In & Registration / Schedule / On-Site Experience / Need Help? Then produce a short "Know Before You Go" summary paragraph (3-5 sentences, suitable for an email or event app notification).
Event name: [EVENT NAME]
Event date(s): [DATE(S)]
Venue name and address: [VENUE, FULL ADDRESS]
Venue directions/transit notes: [whatever you have — or note that venue map will be sent separately]
Registration/check-in details: [location, open time, what attendees need to bring]
Parking: [options, cost, validation if applicable — or [CONFIRM WITH VENUE] if not yet confirmed]
Schedule highlights: [keynote time, lunch, any key sessions to flag]
Dress code: [business casual / cocktail / casual / etc.]
Dietary options: [what's confirmed — or leave blank and I'll fill in]
Session format: [general session / breakouts / workshops — brief description]
Contact for attendee questions: [NAME, EMAIL or event inbox]
Hard rule: Add [CONFIRM WITH VENUE] to any line referencing venue-specific logistics not yet confirmed. Do not fabricate parking details, venue hours, or attendee-facing logistics I haven't provided.
What you get: A structured FAQ document in five sections plus a short summary paragraph you can drop into your pre-event email. The [CONFIRM WITH VENUE] flags are your logistics verification checklist before the document goes out. This works well as an event website page, a PDF attachment, or content in your event app.
5. Post-Event Recap Report
The recap report is the last thing anyone wants to write after a long event, but it's the document that determines next year's budget. Stakeholders need an executive summary. The team needs a record. Sponsors need ROI evidence. Claude structures the full report from your notes — attendance figures, session highlights, feedback themes, sponsor callouts. The hard constraint matters here: it will not invent attendance numbers, survey percentages, or budget figures you didn't provide. It marks missing data [DATA NEEDED] instead.
I need a post-event recap report. Structure it as: Executive Summary (1 paragraph) / Attendance & Engagement / Session Highlights / Attendee Feedback / Sponsor Value / Financial Summary (only if I provide budget data) / Recommendations for Next Year.
Event name: [EVENT NAME]
Event date and venue: [DATE, VENUE]
Total attendance: [NUMBER — registrations vs. actual check-ins if you have both]
Event format: [in-person / virtual / hybrid]
Session titles and speakers (list each):
[SESSION TITLE | SPEAKER NAME | FORMAT | Any notable moment or outcome]
Key takeaways per session (dump your notes — don't pre-edit):
[paste raw notes for each session]
Sponsor highlights:
[list sponsors, their presence/activations, any metrics you have]
Attendee feedback themes (from survey or informal notes):
[paste raw feedback notes — Claude will identify themes]
Budget actuals vs. planned (optional — only include if you want a Financial Summary section):
[TOTAL BUDGET | ACTUAL SPEND | VARIANCE | any line-item notes]
Hard constraint: Do not invent attendance numbers, budget figures, survey percentages, or sponsor metrics. Use only the numbers I provide. Mark any missing figures as [DATA NEEDED]. Do not round up or estimate.
What you get: A structured stakeholder report covering every section your leadership team expects. The Executive Summary paragraph is the one that gets forwarded — Claude writes a tight version from your attendance and highlights. The [DATA NEEDED] flags are your data collection checklist before the report goes to finance, leadership, or sponsors.
6. Post-Event Thank-You and Follow-Up Sequence
The thank-you sequence — speakers, sponsors, attendees, VIP guests — is the goodwill that carries into next year's event. It also gets written last, when you're exhausted. Claude produces tailored drafts for each segment in one prompt, plus a two-week follow-up email for attendees that keeps the community warm (recordings, resources, save the date for next year). Personalize before sending — Claude writes the structure, you add the specific moments that make it feel personal.
I need post-event thank-you and follow-up emails for the following event. Produce: (1) Speaker Thank-You, (2) Sponsor Thank-You, (3) Attendee Thank-You, (4) VIP Guest Thank-You, (5) Attendee Follow-Up Email (send 2 weeks out — share recordings/resources, keep community warm).
Event name: [EVENT NAME]
Event date and venue: [DATE, VENUE]
Key highlights or moments to reference:
[list 2-4 specific moments, sessions, or accomplishments from the event — the more specific, the better the emails]
For speaker thank-yous:
[any specific callout for each speaker's contribution — or write a general version I'll personalize]
For sponsor thank-yous:
[sponsor names, what they sponsored, any metrics to reference if available]
For VIP guests:
[who they are, how they were involved — or describe the VIP experience they had]
Next steps or upcoming events to reference:
[save the date info, recordings availability, resource links, or next event announcement — or leave blank if none yet]
Tone: genuine and specific. Not templated-sounding. These are relationship emails.
What you get: Five email drafts covering your full post-event sequence. The two-week follow-up for attendees is the one most planners skip — it's also the one that differentiates the events people remember from the ones they don't. Personalize the speaker and sponsor emails with specific callouts before sending. A generic thank-you from a form letter is worse than no thank-you.
Why Claude Over ChatGPT for Event Work
The practical reasons: Claude's 100K+ context window means you can paste your entire event brief — all vendor specs, speaker bios, the full session list, the venue details — in a single prompt. No re-explaining across sessions, no context loss, no "as I mentioned earlier" prompts. For a conference with 20 sessions and 8 vendors, that matters.
Claude also won't invent logistics details you didn't provide. The [VERIFY AV SPECS] and [CONFIRM WITH CONTRACT] flags in these prompts exist because Claude is conservative about fabricating specifics. For event documentation — where a wrong load-in time or incorrect AV spec has real day-of consequences — that default behavior is protective, not just a nice-to-have. There's a fuller comparison of how the two models handle professional work in this breakdown of Claude vs. ChatGPT.
The other practical advantage: Claude Projects. Build one Project per event. Upload your venue contract, your event brief, your speaker roster, your vendor list. Everything you paste once stays in context across the entire planning cycle — from the initial ROS draft through vendor briefs, speaker comms, attendee FAQ, and post-event recap. You stop re-pasting your event brief into every new conversation. For freelance event planners juggling multiple events simultaneously, running separate Projects per client keeps everything clean. This is the same pattern that works well for project management workflows and small business owners managing multiple client workstreams.
Structured output also holds better. When you ask for a table-formatted ROS, you get a table. When you ask for a brief with specific sections, the sections stay intact and in order. That fidelity matters when you're handing documents to vendors and speakers who need to navigate them quickly.
4 Practical Tips
1. One Claude Project per event. All your briefs, specs, session list, venue details, and vendor contacts live there across the full planning cycle. You build context once and draw from it for every document — ROS, vendor briefs, speaker packs, attendee FAQ, recap report — without re-pasting background each time.
2. Paste the actual session list and speaker names. Claude writes a better run-of-show from real names, actual session titles, and specific times than from placeholders. "Opening Keynote — Sarah Chen, CEO of [COMPANY], 9:00–9:45am" produces a usable ROS row. "Morning keynote speaker" does not.
3. Use [CONFIRM WITH CONTRACT] as your own QA checklist. The flags Claude adds to vendor briefs are exactly the lines you need to cross-reference against the signed contract before the brief goes out. Run through every flagged line before you hit send. It turns a review step you'd do anyway into a structured checklist.
4. The recap prompt works best when you dump raw notes. Don't pre-edit your post-event notes into polished prose before pasting — paste the messy version, the half-sentences, the things you jotted on your phone during the closing session. Claude organizes; you don't need to. The same logic applies to session takeaways and feedback themes: more raw input produces a better structured output than a pre-edited summary.
If you want the full prompt system — not just event planning use cases but a complete architecture covering every document type across professional work — The Complete Claude Playbook covers it for $27. It's the reference you build your prompt library from, not a one-time read.