30 Claude Prompts Built for Event Planners

You are a senior event planner building the master timeline for an event. <context> You need a minute-by-minute run-of-show that every vendor and staff member can follow on the event day, from setup to breakdown. </context> <inputs> - Event type and date: [PLACEHOLDER] - Key moments and rough times: [PLACEHOLDER] - Vendors involved: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed event: 80-guest 50th birthday celebration, doors open 5:00pm, cocktail hour 5:00-6:00pm, dinner 6:00-7:30pm, speeches 7:30-7:50pm, cake cutting 7:50-8:00pm, dancing 8:00-10:00pm, vendors are caterer, DJ, and photographer. Build a full run-of-show from vendor setup (assume 3 hours before doors) through breakdown, with a column for which vendor or staff owns each block. </task> <constraints> - Start the timeline at vendor arrival/setup, not at doors open. - Every block must name who owns it (caterer, DJ, planner, etc.). - End the timeline at breakdown complete, not at the last guest moment. </constraints> <format> A table: Time, Activity, Owner, Notes. Covering setup through breakdown. </format>

You are a senior event planner scripting the formal program portion of an event. <context> An event has a structured program segment (speeches, awards, ceremony) that needs precise minute-by-minute sequencing so it doesn't run long or feel disjointed. </context> <inputs> - Program segment type: [PLACEHOLDER, e.g. awards ceremony, speeches] - Speakers/participants and rough order: [PLACEHOLDER] - Total time allotted: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed program: awards ceremony segment, total time allotted 25 minutes, participants are the host opening, three award presentations with a short speech each, and a closing thank-you. Build a minute-by-minute script allocating time to each part, adding a 2-minute buffer, and totaling to confirm it fits the allotted time. </task> <constraints> - Time allocations must sum to no more than the total time allotted, including the buffer. - Flag any part likely to run over (e.g. "speeches often run long, confirm speaker has a written version under 2 minutes"). - Include a named transition line between each part (e.g. "MC introduces next presenter"). </constraints> <format> A table: Order, Part, Allotted Time, Transition Line, Risk Note. With a totals row confirming it fits. </format>

You are a senior event planner coordinating vendor load-in and load-out for an event. <context> Multiple vendors need access to the venue before and after the event, and you need a schedule that avoids access conflicts and respects the venue's access rules. </context> <inputs> - Vendors and their setup/breakdown needs: [PLACEHOLDER] - Venue access window: [PLACEHOLDER] - Venue access restrictions: [PLACEHOLDER, e.g. loading dock hours, elevator size] </inputs> <task> If inputs are blank, use this seed load-in: venue access window is 6 hours before doors to 2 hours after event end, vendors are a rental company delivering tables/chairs/linens, a florist, a DJ with sound equipment, and a caterer, venue restriction is a single loading dock that can only fit one vendor truck at a time. Build a load-in and load-out schedule sequencing vendors so they don't conflict at the loading dock, and confirm all setup finishes before doors open. </task> <constraints> - Only one vendor may occupy the loading dock at a time; sequence accordingly with clear time slots. - All setup must complete with at least 30 minutes of buffer before doors open. - Load-out sequencing should let vendors with earlier finish times (e.g. DJ after dancing ends) leave before slower ones if it doesn't conflict. </constraints> <format> A table: Time Slot, Vendor, Activity (Load-In/Load-Out), Dock/Access Notes. </format>

You are a senior event planner confirming vendor arrival times for an event. <context> You need a single reference sheet showing exactly when each vendor arrives, how long their setup takes, and when they must be fully ready, to send to each vendor for confirmation. </context> <inputs> - Vendors and their setup time needs: [PLACEHOLDER] - Doors open time: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed event: doors open 5:00pm, vendors are a rental/decor team needing 3 hours, a florist needing 1.5 hours (after decor is placed), a caterer needing 2 hours, and a DJ needing 1 hour. Calculate each vendor's required arrival time working backward from doors open, sequencing dependent vendors correctly (florist after decor). </task> <constraints> - Work backward from the doors-open time to calculate each arrival time. - Respect stated dependencies (e.g. florist cannot start until decor team is done). - Build in a 30-minute overall buffer before doors open. </constraints> <format> A table: Vendor, Setup Duration, Dependency, Required Arrival Time, Must Be Ready By. </format>

You are a senior event planner preparing a backup plan for an outdoor or weather-dependent event. <context> The event has a weather or logistics risk, and you need a contingency timeline showing exactly what changes and who decides, so the team isn't improvising on the day. </context> <inputs> - Event type and primary risk: [PLACEHOLDER, e.g. outdoor ceremony, rain] - Backup plan/location: [PLACEHOLDER] - Decision deadline: [PLACEHOLDER, e.g. how far ahead the call must be made] </inputs> <task> If inputs are blank, use this seed event: outdoor garden ceremony and reception, primary risk is rain, backup plan is moving the full event into an indoor tent already on-site, decision deadline is 4 hours before doors open based on the forecast. Build a contingency timeline showing the decision point, who makes the call, what changes in the run-of-show if the backup is triggered, and who needs to be notified and by when. </task> <constraints> - Name one single decision-maker responsible for triggering the contingency. - List every vendor/staff member who must be notified if the backup is triggered, with a notification deadline for each. - State clearly what stays the same and what changes in the original run-of-show. </constraints> <format> A document: Decision Point (who, when, based on what), Notification List (Who, By When, How), Changed Elements (What Changes / What Stays the Same). </format>

You are a senior event planner briefing a caterer for an event. <context> You need a clear brief to send a caterer covering guest count, dietary needs, service style, and timing, so their proposal comes back accurate the first time. </context> <inputs> - Event type, date, and guest count: [PLACEHOLDER] - Dietary restrictions known: [PLACEHOLDER] - Service style preference: [PLACEHOLDER, e.g. plated, buffet, family-style] - Meal timing: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed event: 80-guest 50th birthday celebration, dietary restrictions are 3 guests with nut allergies and 2 vegetarian, service style is family-style dinner, meal timing is 6:00-7:30pm following a 1-hour cocktail hour. Write a caterer brief covering all logistics and a menu spec sheet placeholder structure (starters, mains, sides, dessert) with dietary notes flagged against each category. </task> <constraints> - List every dietary restriction explicitly, not folded into a general note. - State the service style and timing clearly enough that the caterer can size staffing. - Do not invent specific menu dishes; leave the menu categories for the caterer to propose, but flag dietary needs against each category. </constraints> <format> A brief document: Event Logistics, Dietary Restrictions (list), Service Style, Timing, Menu Category Placeholders (Starters/Mains/Sides/Dessert) each with dietary flags. </format>

You are a senior event planner comparing vendor proposals for an event. <context> You have received multiple vendor proposals for the same category and need an objective matrix to help the client (or you) decide. </context> <inputs> - Vendor category: [PLACEHOLDER, e.g. photography, DJ, florist] - Proposals received (price/details): [PLACEHOLDER] - Client priorities: [PLACEHOLDER, e.g. price, style, availability] </inputs> <task> If inputs are blank, use this seed comparison: photography category, client priorities are style match, coverage hours, and price under $2,800, considering three photographers with rough quotes of $2,200 for 6 hours, $3,100 for 8 hours, and $2,600 for 6 hours with an album included. Build a comparison matrix scoring each vendor against the stated priorities with a brief justification per score. </task> <constraints> - Use a consistent scoring scale (e.g. Low/Medium/High or a 1-5 scale) across all vendors. - Justify every score in one line. - End with a neutral summary unless one vendor clearly wins on every stated priority. </constraints> <format> A matrix table: rows are vendors, columns are priorities plus a justification note, followed by a short neutral summary paragraph. </format>

You are a senior event planner reviewing a vendor contract before an event. <context> You have a signed vendor contract and want a plain-language summary of the key terms (deposit, cancellation, overtime fees) so you and the client both know what applies if plans change. </context> <inputs> - Vendor type: [PLACEHOLDER] - Key contract terms: [PLACEHOLDER, e.g. deposit amount, cancellation window, overtime rate] </inputs> <task> If inputs are blank, use this seed contract: DJ vendor, terms are a 30% non-refundable deposit, full cancellation refund if cancelled 60+ days out and no refund inside 30 days, overtime rate of $150/hour beyond the contracted 5 hours. Write a plain-language summary of these terms so both the planner and client understand what happens under different scenarios (cancel early, cancel late, event runs long). </task> <constraints> - Cover each term (deposit, cancellation, overtime) as a separate short paragraph. - Walk through at least one concrete scenario per term (e.g. "if you cancel 45 days out, you get X"). - State clearly this is a summary for convenience and the signed contract is the governing document. </constraints> <format> A short summary document with headers per term (Deposit, Cancellation, Overtime), each with a plain-language explanation and a concrete scenario. </format>

You are a senior event planner briefing a florist or decor vendor for an event. <context> You need a clear brief covering the color palette, key pieces needed, and venue constraints, so the florist's proposal matches the event's design direction. </context> <inputs> - Event type and design direction: [PLACEHOLDER] - Key floral/decor pieces needed: [PLACEHOLDER, e.g. centerpieces, arch, bouquets] - Venue constraints: [PLACEHOLDER, e.g. no open flame, delivery window] </inputs> <task> If inputs are blank, use this seed event: 50th birthday celebration, warm and elegant design direction in dusty sage and amber tones, needed pieces are 10 table centerpieces, one welcome sign arrangement, and a dessert table backdrop, venue constraint is no open flame and a 2-hour delivery/setup window. Write a florist brief covering the palette, each needed piece with a brief description, and the venue constraints the florist must design around. </task> <constraints> - List each decor piece separately with its own line, not bundled together. - State venue constraints explicitly as hard requirements, not suggestions. - Reference the color palette by name in each piece description so the florist can match tone consistently. </constraints> <format> A brief document: Design Direction/Palette, Piece List (Piece, Description, Quantity), Venue Constraints. </format>

You are a senior event planner coordinating AV and entertainment needs for an event. <context> A DJ, band, or speaker needs specific technical requirements met, and you need a technical rider style document to confirm what the venue and vendor each need to provide. </context> <inputs> - Entertainment type: [PLACEHOLDER, e.g. DJ, live band, keynote speaker] - Technical needs mentioned by the vendor: [PLACEHOLDER] - Venue's known AV capabilities: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed setup: DJ entertainment, vendor needs two speakers, a wireless mic for speeches, a small mixing table, and access to a standard power outlet within 20 feet, venue provides in-house speakers but no wireless mic. Build a technical rider listing each requirement, who provides it (vendor or venue), and flag any gap where neither side currently has it covered. </task> <constraints> - Mark each requirement's source as Vendor-Provided, Venue-Provided, or Gap (unassigned). - For every Gap item, name who needs to resolve it and by when. - Keep technical language plain enough for a non-technical client to skim if needed. </constraints> <format> A table: Requirement, Provided By, Status (Confirmed/Gap), Action Needed (if Gap). </format>

You are a senior event planner building a detailed event budget. <context> You need to break a total event budget down by category so the client can see where the money goes and where there's flexibility. </context> <inputs> - Total budget: [PLACEHOLDER] - Event type and guest count: [PLACEHOLDER] - Known big-ticket items: [PLACEHOLDER, e.g. venue, catering] </inputs> <task> If inputs are blank, use this seed event: total budget $18,000 for an 80-guest 50th birthday celebration, known big-ticket item is venue rental estimated at $5,000. Break the budget into categories (venue, catering, decor/florals, entertainment, photography, rentals, staffing, contingency) with a dollar allocation and percentage for each, flagging which allocations are estimates versus confirmed. </task> <constraints> - Always include a contingency line of 10-15% of the total. - Allocations must sum exactly to the stated total budget. - Mark the category containing the known big-ticket item as "partially confirmed." </constraints> <format> A spreadsheet-style table: Category, Allocation ($), Allocation (%), Status (Estimate/Confirmed/Partially Confirmed). Totals row at the bottom. </format>

You are a senior event planner tracking vendor payments for an event. <context> Multiple vendors have different deposit and final payment schedules, and you need a single tracker so nothing is paid late or missed. </context> <inputs> - Vendors, total cost, and deposit terms: [PLACEHOLDER] - Event date: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed event: event date in 10 weeks, vendors are venue at $5,000 total (50% deposit due now, balance due 2 weeks before event), caterer at $6,200 total (30% deposit due now, balance due on event day), and DJ at $1,400 total (full payment due 1 week before event). Build a payment schedule tracker calculating each due date and amount, sorted chronologically. </task> <constraints> - Calculate each due date relative to the event date, not just relative to today. - Sort all payments chronologically across vendors, not grouped by vendor. - Flag any payment due within 7 days of the event as "final payment, confirm now." </constraints> <format> A table sorted by due date: Due Date, Vendor, Amount Due, Payment Type (Deposit/Balance/Full), Flag. </format>

You are a senior event planner analyzing event costs on a per-guest basis. <context> A client wants to understand the cost per guest to help decide whether to adjust the guest list or budget, and you need a clear breakdown. </context> <inputs> - Total budget and guest count: [PLACEHOLDER] - Category breakdown (any format): [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed event: total budget $18,000, 80 guests, category breakdown is venue $5,000, catering $6,200, decor $2,400, entertainment $1,800, photography $1,600, rentals $900. Calculate cost per guest for each category and the overall total, then note which categories scale with guest count (like catering) versus which are largely fixed (like venue and entertainment). </task> <constraints> - Show the per-guest math for every category, not just the total. - Explicitly separate variable (scales with guest count) from fixed cost categories. - If the client were to add or remove 10 guests, state the approximate cost impact using only the variable categories. </constraints> <format> A table: Category, Total Cost, Cost Per Guest, Fixed or Variable. Followed by a short paragraph on the impact of a +/-10 guest change. </format>

You are a senior event planner updating a budget after a client requests a change. <context> The client added or changed something mid-planning, and you need an updated budget reforecast showing the impact clearly before proceeding. </context> <inputs> - Original budget and category breakdown: [PLACEHOLDER] - Requested change: [PLACEHOLDER] - Cost impact of the change: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed change: original budget $18,000 with venue $5,000, catering $6,200, decor $2,400, entertainment $1,800, photography $1,600, rentals $900, contingency $100 leftover, client now wants to add a live band instead of a DJ, adding $2,600 to entertainment. Produce a reforecast showing the original allocation, the new allocation, and where the extra cost is coming from (additional client budget, reduced contingency, or cut from another category), based on what the client specifies. </task> <constraints> - Show original and new numbers side by side for every affected category, not just the one that changed. - If no funding source for the added cost is specified, present 2 clear options (increase total budget, or cut from a named category) rather than silently absorbing it. - New total must be internally consistent (allocations sum to the new total). </constraints> <format> A table: Category, Original Allocation, New Allocation, Change (+/-). Followed by a short note on funding source options if unspecified. </format>

You are a senior event planner closing out the budget after an event has happened. <context> The event is over and you need a final reconciliation comparing planned budget to actual spend, to close out with the client and improve future estimates. </context> <inputs> - Planned budget by category: [PLACEHOLDER] - Actual spend by category: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed reconciliation: planned was venue $5,000, catering $6,200, decor $2,400, entertainment $1,800, photography $1,600, rentals $900, contingency $2,100 (total $18,000), actual came in with catering at $6,650 due to a final headcount increase, decor at $2,150, entertainment at $2,400 due to the band upgrade, everything else on plan. Build a reconciliation report comparing planned versus actual per category, with variance and a one-line reason for each variance over 5%. </task> <constraints> - Calculate variance in both dollars and percentage for every category. - Only require a reason note for variances over 5%; leave on-target categories without commentary. - End with whether the contingency fully covered the overages or if the client owes/is owed a balance. </constraints> <format> A table: Category, Planned, Actual, Variance ($), Variance (%), Reason (if >5%). Followed by a closing summary line on contingency coverage. </format>

You are a senior event planner building an intake process for new clients. <context> You want a structured questionnaire to send a new client before the first call, so the call time is spent on discussion rather than gathering basic facts. </context> <inputs> - Event type: [PLACEHOLDER] - Any facts already known: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed event type: milestone birthday celebration, no facts known yet beyond the event type. Build a discovery questionnaire covering event basics (date, guest count, budget range), style preferences, must-haves, dealbreakers, and logistics constraints (accessibility, dietary, venue preference). </task> <constraints> - Group questions into clear sections (Basics, Style, Must-Haves and Dealbreakers, Logistics). - Keep the total question count to 15-20; do not overwhelm a new client with a 40-question form. - Phrase questions in plain, friendly language, not planner jargon. </constraints> <format> A questionnaire document grouped into labeled sections, each with numbered questions. </format>

You are a senior event planner keeping a client informed during active planning. <context> You want a consistent weekly status update format so the client always knows what's been done, what's next, and what you need from them. </context> <inputs> - What was completed this week: [PLACEHOLDER] - What's planned for next week: [PLACEHOLDER] - Anything needed from the client: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed week: completed this week were venue deposit paid and caterer proposal received, planned for next week are finalizing the menu and booking the florist, needed from client is a decision on the band vs. DJ question by Friday. Write a weekly status update email covering these three sections concisely. </task> <constraints> - Keep the email under 150 words. - Put anything needed from the client in its own clearly labeled section with a deadline. - Use a warm but efficient tone; this is a routine update, not a big announcement. </constraints> <format> An email: Subject line, Completed This Week, Coming Up Next Week, Needed From You (with deadline). </format>

You are a senior event planner preparing for an uncomfortable client conversation. <context> You need to deliver unwelcome news, such as a budget overage or a vendor falling through, and want a calm, direct script to prepare for the call or email. </context> <inputs> - What went wrong: [PLACEHOLDER, e.g. budget overage, vendor cancellation] - Size/impact of the issue: [PLACEHOLDER] - Proposed resolution options: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed situation: the originally booked florist cancelled 6 weeks before the event due to a business closure, proposed resolution options are a comparable replacement florist at a similar price with 1 week less lead time, or a slightly higher-priced florist with full availability. Write a script that states the issue plainly, explains what's being done about it, presents the resolution options, and invites the client's decision. </task> <constraints> - Lead with the issue in the first two sentences; do not bury it under pleasantries. - Show that action has already been taken (researching replacements) before asking the client to decide, so it doesn't read as just a problem dump. - Always end by giving the client a clear choice or decision to make. </constraints> <format> A short script with labeled sections: Opening (state the issue), What We've Already Done, Options, Closing Ask. </format>

You are a senior event planner managing guest RSVPs for an event. <context> You're collecting RSVPs and need a structured tracking sheet that captures attendance, dietary restrictions, and seating notes in one place for the caterer and venue. </context> <inputs> - Guest list source (any format, names/notes): [PLACEHOLDER] - RSVP deadline: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed guest list: 10 sample guests with notes like "Confirmed, vegetarian," "Pending," "Confirmed, nut allergy, bringing a plus one," "Declined," and similar realistic mixed statuses, RSVP deadline is 3 weeks before the event. Build a tracking sheet listing each guest with RSVP status, dietary notes, plus-one status, and a summary count at the bottom (confirmed, pending, declined, total dietary flags). </task> <constraints> - Every guest needs a clear RSVP status (Confirmed/Pending/Declined), not left blank. - Dietary notes must be a separate column, never combined with the name field. - Include a summary row totaling confirmed guests and dietary flag counts for the caterer. </constraints> <format> A table: Guest Name, RSVP Status, Plus-One, Dietary Notes. With a summary row at the bottom. </format>

You are a senior event planner wrapping up a successful event. <context> An event just wrapped and went well, and you want to send the client a warm recap and, separately, ask for a testimonial without sounding transactional right after their event. </context> <inputs> - Event summary and highlights: [PLACEHOLDER] - Where you'd like the testimonial posted: [PLACEHOLDER, e.g. Google, The Knot] </inputs> <task> If inputs are blank, use this seed event: 50th birthday celebration for 80 guests that went smoothly despite a last-minute florist swap, testimonial requested for Google reviews. Write one email that thanks the client, recaps 2-3 highlights of the event, and separately asks for a short testimonial with a direct link placeholder. </task> <constraints> - Keep the recap and the testimonial ask as two clearly separate paragraphs, not blended into one pitch. - Make the testimonial ask specific (2-3 sentences about their experience) rather than an open-ended "leave a review." - Keep the overall tone warm and celebratory, not transactional. </constraints> <format> One email: Subject line, warm recap opening with highlights, Testimonial Ask paragraph, warm closing. </format>

You are a senior event planner preparing for event day. <context> You want a single master checklist covering everything that needs to happen on the day of the event, from your own arrival through final vendor departure, so nothing is missed under pressure. </context> <inputs> - Event type and key moments: [PLACEHOLDER] - Vendors involved: [PLACEHOLDER] - Your own arrival time: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed event: 80-guest 50th birthday celebration, key moments are cocktail hour, dinner, speeches, cake cutting, and dancing, vendors are caterer, DJ, florist, and photographer, planner arrives 3 hours before doors. Build a master checklist grouped into Pre-Event Setup, During Event, and Post-Event Breakdown, covering vendor check-ins, timeline milestones, and emergency supplies. </task> <constraints> - Group items into the three named phases, not one flat list. - Include a vendor check-in item for each vendor listed, not a generic "check vendors" line. - Include at least 3 emergency/backup supply items (e.g. stain remover, phone charger, spare cash). </constraints> <format> A checklist grouped by phase (Pre-Event Setup, During Event, Post-Event Breakdown), each item as a checkbox-style line. </format>

You are a senior event planner preparing a reference sheet for event day. <context> On event day, staff and vendors need a single sheet with every vendor's contact info, arrival time, and role, so questions get answered fast without hunting through email threads. </context> <inputs> - Vendors, contact info, and roles: [PLACEHOLDER] - Arrival/setup times: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed vendor list: caterer (lead contact, arriving 2pm), DJ (lead contact, arriving 3pm), florist (lead contact, arriving 1pm), photographer (lead contact, arriving 4pm), each with a placeholder phone number format. Build a point-of-contact sheet listing each vendor's role, contact name, phone number placeholder, and arrival time, sorted by arrival time. </task> <constraints> - Sort vendors by arrival time, earliest first. - Use a consistent phone number placeholder format (e.g. [PHONE]) for any number not provided. - Include a role description for each vendor, not just the company name. </constraints> <format> A table sorted by arrival time: Arrival Time, Vendor, Role, Contact Name, Phone. </format>

You are a senior event planner preparing for unexpected issues on event day. <context> You want a physical emergency kit checklist plus a short contingency list of common event-day problems and their quick fixes, so small issues don't derail the day. </context> <inputs> - Event type and venue setting: [PLACEHOLDER, e.g. outdoor, indoor] - Known risk factors: [PLACEHOLDER, e.g. weather, outdoor power access] </inputs> <task> If inputs are blank, use this seed event: outdoor garden reception with an indoor backup tent, known risk factors are weather and uneven ground for high heels. Build an emergency kit checklist (physical items to bring) and a separate contingency list of 5 common problems with a quick fix for each. </task> <constraints> - Emergency kit items must be physical, packable items, not services or plans. - Each contingency problem needs a specific quick fix, not "handle as needed." - Tailor at least 2 contingency items to the stated venue setting or risk factors. </constraints> <format> Two lists: Emergency Kit Checklist (items), Contingency Quick-Fixes (Problem, Fix). </format>

You are a senior event planner assigning roles to event-day staff. <context> You have a small team helping run the event and need clear role assignments so everyone knows their zone and responsibilities without checking in with you constantly. </context> <inputs> - Staff/team members available: [PLACEHOLDER] - Key zones/tasks needing coverage: [PLACEHOLDER] </inputs> <task> If inputs are blank, use this seed team: 3 staff members plus the lead planner, key zones are guest check-in/welcome, catering and bar liaison, and floating troubleshooter, plus the lead planner overseeing timeline and vendor coordination. Assign each staff member a zone, primary responsibilities, and who to escalate to if something goes wrong outside their zone. </task> <constraints> - Every staff member gets exactly one primary zone; no split assignments that create ambiguity. - Include an escalation path (who to contact) for every role. - State each role's start and approximate end time for their assigned duty. </constraints> <format> A table: Staff Member, Zone, Primary Responsibilities, Escalation Contact, Duty Hours. </format>

You are a senior event planner closing out an event after it ends. <context> The event just finished and you need a checklist covering final vendor payouts, rental returns, lost-and-found handling, and client close-out, so nothing slips through after everyone's exhausted. </context> <inputs> - Vendors with outstanding balances: [PLACEHOLDER] - Rentals needing return: [PLACEHOLDER] - Client close-out items needed: [PLACEHOLDER, e.g. final invoice, thank-you] </inputs> <task> If inputs are blank, use this seed wrap-up: caterer has a final balance due within 3 days, rental company needs tables, chairs, and linens returned within 24 hours, client close-out needs a final invoice reconciliation and a thank-you note. Build a post-event checklist covering vendor payouts with deadlines, rental returns with deadlines, and client close-out steps. </task> <constraints> - Every vendor payout and rental return needs an explicit deadline, not just "soon." - Separate the checklist into three sections: Vendor Payouts, Rental Returns, Client Close-Out. - Include a final step confirming all sections are complete before the project is marked closed. </constraints> <format> A checklist in three sections (Vendor Payouts, Rental Returns, Client Close-Out), each item with a deadline, ending in a final "Project Closed" confirmation line. </format>