Act as a senior event operations planner. Build a working planning pack for this event using only the details I provide. Event brief: [EVENT BRIEF] Budget and commercial constraints: [BUDGET DETAILS] Venue, suppliers, and logistics: [LOGISTICS] Attendee and stakeholder needs: [ATTENDEE NEEDS]
Known risks and non-negotiables: [RISKS AND REQUIREMENTS]
Produce a planning pack with: a one-paragraph event objective and success measures; a milestone timeline from planning through post-event; a day-of run sheet; a responsibility matrix; a budget-control checklist; and a risk register.
For the run sheet, use a table with time, activity, location, owner, dependency, attendee-facing message or cue, supplier cue, and contingency. Include build, soundcheck or technical testing, registration, program transitions, meals if relevant, accessibility checks, breakdown, and handover. Do not make up venue capacity, supplier availability, permits, prices, staffing, or travel times. Mark missing operational facts as "confirm" with the role that should confirm them.
For the responsibility matrix, distinguish accountable owner from support roles. For the risk register, include risk, trigger, likelihood, impact, prevention, response, decision owner, and latest decision time. Cover realistic issues such as late speakers, registration queues, AV failure, dietary needs, weather, crowd flow, and safeguarding only where relevant to the event.
Finish with the ten highest-priority unanswered questions, ordered by their effect on guest experience, safety, budget, or schedule. Before answering, check that no two people are accountable for the same decision and that every run-sheet dependency has an owner. Ask up to three clarifying questions only if a required input is missing.Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [EVENT BRIEF] | Describe the event type, date, audience size, objectives, agenda, and format. | One-day customer summit on November 12 for 220 operations leaders; 9:00 a.m. to 5:30 p.m.; two keynotes, four breakouts, and evening reception. |
| [BUDGET DETAILS] | Provide the approved budget, committed costs, revenue assumptions, and spending limits. | Approved budget $68,000; venue deposit $14,000 committed; catering cap $52 per guest; no ticket revenue. |
| [LOGISTICS] | List the venue, rooms, suppliers, arrival details, equipment, and known logistics. | Harbor Hall, Boston; main room plus three breakouts; AV supplier booked; loading dock access from 7:00 a.m.; 12 exhibitors. |
| [ATTENDEE NEEDS] | Describe registration, accessibility, dietary, communication, and VIP requirements. | Online registration closes five days prior; five gluten-free meals requested; two wheelchair users; 18 executive guests need a quiet green room. |
| [RISKS AND REQUIREMENTS] | List non-negotiables, safety requirements, approvals, policies, and known risks. | CEO keynote cannot move after 10:00 a.m.; venue requires certificate of insurance; rain plan needed for rooftop reception. |
How to use
- Paste the event brief with confirmed facts and identify every assumption you want the AI to label rather than fill.
- Check the run sheet against venue access times, supplier contracts, and the actual agenda before circulating it.
- Assign named people to the accountability roles and resolve the highest-priority unanswered questions first.
- Follow up with: "Turn this run sheet into a staff briefing for registration, AV, speakers, and floor managers, with radio-call language."
Variations
Vendor brief
Use this to give a supplier a precise brief that reduces day-of ambiguity.
Draft a vendor brief for [VENDOR TYPE] supporting [EVENT]. Use these confirmed requirements: [REQUIREMENTS], venue details: [VENUE], and schedule: [SCHEDULE]. Produce a one-page brief with scope, deliverables, arrival and access instructions, technical or service specifications, named decision owner, acceptance checks, escalation path, and questions requiring vendor confirmation. Separate confirmed details from assumptions. Do not invent contract terms, capacities, equipment, or pricing. Include a checklist the vendor can return completed. Ask up to three questions only if essential details are missing.
Guest email sequence
Use this when attendees need clear information before an event.
Write a guest communication sequence for [EVENT] for [AUDIENCE]. Confirmed logistics are [LOGISTICS], and the tone is [TONE]. Create three emails: registration confirmation, one-week reminder, and day-before message. Each should state only confirmed details, include arrival or joining instructions, accessibility and dietary contact information, a concise agenda cue, and a clear support contact. Flag missing details rather than creating them. Keep each email under [WORD LIMIT] words and provide subject lines. Ask up to three questions only if required information is missing.
Post-event report
Use this after an event to turn results and feedback into decisions.
Prepare a post-event report for [EVENT] using these results: [RESULTS], budget records: [BUDGET], attendee feedback: [FEEDBACK], and incident notes: [INCIDENTS]. Produce an executive summary, attendance and engagement results, budget variance table, what worked, what failed, risk or incident follow-up, and five recommendations with owner roles and deadlines. Distinguish measured results from participant opinions. Do not infer ROI or satisfaction scores without data. Flag information that needs finance, legal, or safety review. Ask up to three questions only if a required input is missing.
Tips
- Build the run sheet backward from immovable moments such as doors open, keynote start, venue curfew, and supplier load-out.
- Give each transition an owner and a contingency; transitions, not agenda blocks, are where delays commonly compound.
- Use one source of truth for versioned run sheets and make the latest version visible to every floor lead before doors open.
- Record decisions with a deadline and owner, especially around menus, attendee counts, AV specifications, and weather triggers.
FAQ
Can AI create a complete event plan from a short brief?
It can create a useful structure and expose missing decisions, but venue rules, contracts, permits, staffing, and safety plans still need confirmation from responsible people.
What belongs in a day-of run sheet?
Include every handoff that can affect timing or guest experience: access, setup, cues, transitions, meals, speaker movements, contingencies, and closeout.
Should AI write attendee emails?
Yes, after you provide confirmed logistics and a contact path for exceptions. Do not let it invent transport, accessibility, or schedule details.