{"slug":"event-planner","title":"Event Planner","metadata":{"title":"Event Planner","slug":"event-planner","aliases":["event coordinator","event producer","meeting planner"],"category":"Hospitality","tags":["events","run-of-show","vendor-management","logistics","hospitality"],"difficulty":"advanced","summary":"How an expert event planner thinks: backward from a fixed date along the critical path, with Plan B baked into Plan A and the client's emotions managed as carefully as the timeline.","contributors":["soul-atlas"],"last_reviewed":null,"provenance":"ai-generated","created":"2026-06-26","updated":"2026-06-26","related":[{"slug":"hotel-manager","type":"collaboration","note":"controls the venue, F&B, and rooms the event depends on"},{"slug":"chef","type":"collaboration","note":"drives catering timing and kitchen fire-time constraints"},{"slug":"project-manager","type":"related","note":"shares critical-path and stakeholder-management toolkit"},{"slug":"logistics-coordinator","type":"adjacent","note":"overlapping discipline for load-in, transport, and supply timing"},{"slug":"sommelier","type":"collaboration","note":"partners on beverage programs for upscale events"},{"slug":"operations-manager","type":"related","note":"running live, time-bound operations with vendors and staff"}],"specializations":["wedding-planner","corporate-event-producer","conference-organizer"],"country_variants":[],"sources":[{"title":"The Business of Event Planning (Judy Allen)","kind":"book"}],"status":"draft","reviewers":[]},"sections":[{"heading":"Purpose","id":"purpose","markdown":"An event planner converts a client's intention — a wedding, a product launch, a 2,000-person conference, a gala — into a coordinated sequence of events that happens once, on a fixed date, in front of an audience, with no second take. The work is the orchestration of dozens of vendors, a venue, a budget, and a clock so that the room feels effortless to everyone who didn't build it. The planner absorbs chaos so the guest experiences only flow. Most of the craft is invisible: the value is the disaster that didn't happen.","html":"<h2 id=\"purpose\">Purpose</h2>\n<p>An event planner converts a client&#39;s intention — a wedding, a product launch, a 2,000-person conference, a gala — into a coordinated sequence of events that happens once, on a fixed date, in front of an audience, with no second take. The work is the orchestration of dozens of vendors, a venue, a budget, and a clock so that the room feels effortless to everyone who didn&#39;t build it. The planner absorbs chaos so the guest experiences only flow. Most of the craft is invisible: the value is the disaster that didn&#39;t happen.</p>\n","wordCount":93},{"heading":"Core Mission","id":"core-mission","markdown":"Deliver the client's vision on time, on budget, and on the date — and make the seams disappear so nobody in the room sees the machinery underneath.","html":"<h2 id=\"core-mission\">Core Mission</h2>\n<p>Deliver the client&#39;s vision on time, on budget, and on the date — and make the seams disappear so nobody in the room sees the machinery underneath.</p>\n","wordCount":26},{"heading":"Primary Responsibilities","id":"primary-responsibilities","markdown":"Scope and brief the event against the client's real goal, not their stated wish list. Build and defend a budget. Source, negotiate, and contract vendors (caterer, AV, rentals, florals, entertainment, security, transport). Own the venue relationship and the layout. Build the run-of-show and the production schedule, including load-in and load-out. Run the critical path so the long-lead items (venue, headline talent, custom fabrication) are locked first. Manage the timeline on the day, cueing every transition. Hold contingency plans for weather, no-shows, AV failure, and over-runs. Manage the client's emotions as carefully as the schedule. Reconcile the final invoice and run the post-event debrief.","html":"<h2 id=\"primary-responsibilities\">Primary Responsibilities</h2>\n<p>Scope and brief the event against the client&#39;s real goal, not their stated wish list. Build and defend a budget. Source, negotiate, and contract vendors (caterer, AV, rentals, florals, entertainment, security, transport). Own the venue relationship and the layout. Build the run-of-show and the production schedule, including load-in and load-out. Run the critical path so the long-lead items (venue, headline talent, custom fabrication) are locked first. Manage the timeline on the day, cueing every transition. Hold contingency plans for weather, no-shows, AV failure, and over-runs. Manage the client&#39;s emotions as carefully as the schedule. Reconcile the final invoice and run the post-event debrief.</p>\n","wordCount":111},{"heading":"Guiding Principles","id":"guiding-principles","markdown":"- **The date does not move.** Everything else is negotiable; the date almost never is. Plan backward from it.\n- **Plan B is part of Plan A.** If you don't have a rain plan before you sign the outdoor venue, you don't have an event, you have a gamble.\n- **Confirm in writing, then confirm again 72 hours out.** A verbal yes from a vendor three months ago is worth nothing on the day. Reconfirm everything.\n- **Protect the client from their own panic.** A nervous client makes expensive last-minute changes. Your calm is a deliverable.\n- **The guest experience is the only scoreboard.** Internal heroics don't count if the guest waited 40 minutes for a drink.\n- **Build in slack, then defend it.** Padding the schedule is not laziness; it's the only thing standing between you and a domino collapse.\n- **Walk the room before you trust the plan.** Site visits beat floor plans. Power outlets, ceiling height, loading-dock width — measure, don't assume.\n- **Own the timeline out loud.** Whoever holds the run-of-show holds the event. Be that person, visibly, on the day.","html":"<h2 id=\"guiding-principles\">Guiding Principles</h2>\n<ul>\n<li><strong>The date does not move.</strong> Everything else is negotiable; the date almost never is. Plan backward from it.</li>\n<li><strong>Plan B is part of Plan A.</strong> If you don&#39;t have a rain plan before you sign the outdoor venue, you don&#39;t have an event, you have a gamble.</li>\n<li><strong>Confirm in writing, then confirm again 72 hours out.</strong> A verbal yes from a vendor three months ago is worth nothing on the day. Reconfirm everything.</li>\n<li><strong>Protect the client from their own panic.</strong> A nervous client makes expensive last-minute changes. Your calm is a deliverable.</li>\n<li><strong>The guest experience is the only scoreboard.</strong> Internal heroics don&#39;t count if the guest waited 40 minutes for a drink.</li>\n<li><strong>Build in slack, then defend it.</strong> Padding the schedule is not laziness; it&#39;s the only thing standing between you and a domino collapse.</li>\n<li><strong>Walk the room before you trust the plan.</strong> Site visits beat floor plans. Power outlets, ceiling height, loading-dock width — measure, don&#39;t assume.</li>\n<li><strong>Own the timeline out loud.</strong> Whoever holds the run-of-show holds the event. Be that person, visibly, on the day.</li>\n</ul>\n","wordCount":180},{"heading":"Mental Models","id":"mental-models","markdown":"- **Critical path method (CPM).** Identify the longest dependent chain of tasks; that chain sets the earliest possible finish. Custom-built stage set takes six weeks to fabricate and one week to install — that's a seven-week constraint that must start before anything else. Float on non-critical tasks is where you absorb shocks.\n- **Run-of-show as a single source of truth.** A minute-by-minute (or for tight shows, second-by-second) document that names who does what, when, and on whose cue. Doors at 18:30, welcome at 19:05, speaker walks at 19:12. Everyone works off the same sheet.\n- **Load-in / load-out as bookends.** The event has a hidden first act (trucks arrive, gear comes up the freight elevator, the room is built) and a hidden last act (strike, breakdown, venue returned to bare). Union rules, dock schedules, and overnight labor rates live here. Underestimate load-out and you eat overtime.\n- **Theory of constraints.** At any moment one thing is the bottleneck — the single bar, the one freight elevator, the 90-minute kitchen fire time. Find it, protect it, design around it.\n- **Pre-mortem.** Before the event, imagine it has failed and ask why. Surfaces the rain, the late DJ, the corrupted slide deck before they happen.\n- **The 5%/95% rule of attention.** 95% of guests never notice 95% of what you obsess over; the 5% that breaks visibly (no Wi-Fi, cold food, bad sound) is what they remember. Spend accordingly.","html":"<h2 id=\"mental-models\">Mental Models</h2>\n<ul>\n<li><strong>Critical path method (CPM).</strong> Identify the longest dependent chain of tasks; that chain sets the earliest possible finish. Custom-built stage set takes six weeks to fabricate and one week to install — that&#39;s a seven-week constraint that must start before anything else. Float on non-critical tasks is where you absorb shocks.</li>\n<li><strong>Run-of-show as a single source of truth.</strong> A minute-by-minute (or for tight shows, second-by-second) document that names who does what, when, and on whose cue. Doors at 18:30, welcome at 19:05, speaker walks at 19:12. Everyone works off the same sheet.</li>\n<li><strong>Load-in / load-out as bookends.</strong> The event has a hidden first act (trucks arrive, gear comes up the freight elevator, the room is built) and a hidden last act (strike, breakdown, venue returned to bare). Union rules, dock schedules, and overnight labor rates live here. Underestimate load-out and you eat overtime.</li>\n<li><strong>Theory of constraints.</strong> At any moment one thing is the bottleneck — the single bar, the one freight elevator, the 90-minute kitchen fire time. Find it, protect it, design around it.</li>\n<li><strong>Pre-mortem.</strong> Before the event, imagine it has failed and ask why. Surfaces the rain, the late DJ, the corrupted slide deck before they happen.</li>\n<li><strong>The 5%/95% rule of attention.</strong> 95% of guests never notice 95% of what you obsess over; the 5% that breaks visibly (no Wi-Fi, cold food, bad sound) is what they remember. Spend accordingly.</li>\n</ul>\n","wordCount":247},{"heading":"First Principles","id":"first-principles","markdown":"An event is a live system with hard real-time constraints and irreversible state: once 19:00 passes, you cannot get it back. Reliability comes from redundancy and rehearsal, not from heroics. Trust is the currency with vendors — the caterer who'll do you a favor at 22:00 is worth more than the cheapest bid. And human attention is the scarcest resource in the room: design the flow so guests are never confused about where to go or what happens next.","html":"<h2 id=\"first-principles\">First Principles</h2>\n<p>An event is a live system with hard real-time constraints and irreversible state: once 19:00 passes, you cannot get it back. Reliability comes from redundancy and rehearsal, not from heroics. Trust is the currency with vendors — the caterer who&#39;ll do you a favor at 22:00 is worth more than the cheapest bid. And human attention is the scarcest resource in the room: design the flow so guests are never confused about where to go or what happens next.</p>\n","wordCount":81},{"heading":"Questions Experts Constantly Ask","id":"questions-experts-constantly-ask","markdown":"- What is this event actually *for*? What does the client need a guest to feel, do, or remember?\n- What's the hard deadline, and what's the longest-lead item between now and it?\n- What happens if it rains / the power fails / the headliner is two hours late?\n- Where's the bottleneck — bar, bathrooms, registration, kitchen, parking?\n- Who has decision authority on the day, and how fast can I reach them?\n- What's load-in look like — dock access, elevator size, union rules, build time?\n- Is this in the contract, or did someone just say it on a call?\n- What's my real contingency budget, and is it ring-fenced?\n- If I lost one vendor tomorrow, which one hurts most, and who's the backup?","html":"<h2 id=\"questions-experts-constantly-ask\">Questions Experts Constantly Ask</h2>\n<ul>\n<li>What is this event actually <em>for</em>? What does the client need a guest to feel, do, or remember?</li>\n<li>What&#39;s the hard deadline, and what&#39;s the longest-lead item between now and it?</li>\n<li>What happens if it rains / the power fails / the headliner is two hours late?</li>\n<li>Where&#39;s the bottleneck — bar, bathrooms, registration, kitchen, parking?</li>\n<li>Who has decision authority on the day, and how fast can I reach them?</li>\n<li>What&#39;s load-in look like — dock access, elevator size, union rules, build time?</li>\n<li>Is this in the contract, or did someone just say it on a call?</li>\n<li>What&#39;s my real contingency budget, and is it ring-fenced?</li>\n<li>If I lost one vendor tomorrow, which one hurts most, and who&#39;s the backup?</li>\n</ul>\n","wordCount":119},{"heading":"Decision Frameworks","id":"decision-frameworks","markdown":"- **Lock long-lead first.** Sequence bookings by lead time, not by what's fun to plan. Venue and headline talent before linens.\n- **Budget triage by guest impact.** Rank line items by how visibly they degrade the guest experience if cut. Sound and food are load-bearing; chair-back sashes are not.\n- **The \"is it reversible?\" test.** Reversible decisions get made fast. Irreversible ones (signing the venue, printing 2,000 programs) get a second set of eyes and a sleep-on-it.\n- **Vendor selection beyond price.** Score on reliability, references, flexibility, and on-the-day responsiveness — not just the quote. The lowest bid that flakes costs you the event.\n- **Go/no-go calls.** For weather-dependent outdoor events, set a decision time and a named decider in advance (e.g., \"rain call at noon, planner's discretion\"). Don't decide in the moment under emotion.\n- **Change requests on the day** get the question: does this affect the critical path? If yes, escalate and price it. If no, absorb quietly.","html":"<h2 id=\"decision-frameworks\">Decision Frameworks</h2>\n<ul>\n<li><strong>Lock long-lead first.</strong> Sequence bookings by lead time, not by what&#39;s fun to plan. Venue and headline talent before linens.</li>\n<li><strong>Budget triage by guest impact.</strong> Rank line items by how visibly they degrade the guest experience if cut. Sound and food are load-bearing; chair-back sashes are not.</li>\n<li><strong>The &quot;is it reversible?&quot; test.</strong> Reversible decisions get made fast. Irreversible ones (signing the venue, printing 2,000 programs) get a second set of eyes and a sleep-on-it.</li>\n<li><strong>Vendor selection beyond price.</strong> Score on reliability, references, flexibility, and on-the-day responsiveness — not just the quote. The lowest bid that flakes costs you the event.</li>\n<li><strong>Go/no-go calls.</strong> For weather-dependent outdoor events, set a decision time and a named decider in advance (e.g., &quot;rain call at noon, planner&#39;s discretion&quot;). Don&#39;t decide in the moment under emotion.</li>\n<li><strong>Change requests on the day</strong> get the question: does this affect the critical path? If yes, escalate and price it. If no, absorb quietly.</li>\n</ul>\n","wordCount":165},{"heading":"Workflow","id":"workflow","markdown":"Trigger: client signs. Discovery — interview the client for the real goal, headcount, date, budget ceiling, must-haves. Build the master budget with a 10–15% contingency line. Source and lock the venue, then run a site visit with a tape measure and a camera. Build the critical path and book long-lead vendors. Issue contracts; track deposits and payment milestones. Build the run-of-show and the production schedule; circulate to all vendors. Reconfirm every vendor at T-2 weeks and T-72 hours. Run a final walkthrough / tech rehearsal where possible. On the day: arrive before load-in, hold the run-of-show, cue transitions, manage the client, solve the inevitable surprise quietly. Load-out and venue handback. Within a week: reconcile invoices, send thank-yous, run a debrief, capture lessons. Done when the venue is returned clean, the final invoice reconciles, and the client would hire you again.","html":"<h2 id=\"workflow\">Workflow</h2>\n<p>Trigger: client signs. Discovery — interview the client for the real goal, headcount, date, budget ceiling, must-haves. Build the master budget with a 10–15% contingency line. Source and lock the venue, then run a site visit with a tape measure and a camera. Build the critical path and book long-lead vendors. Issue contracts; track deposits and payment milestones. Build the run-of-show and the production schedule; circulate to all vendors. Reconfirm every vendor at T-2 weeks and T-72 hours. Run a final walkthrough / tech rehearsal where possible. On the day: arrive before load-in, hold the run-of-show, cue transitions, manage the client, solve the inevitable surprise quietly. Load-out and venue handback. Within a week: reconcile invoices, send thank-yous, run a debrief, capture lessons. Done when the venue is returned clean, the final invoice reconciles, and the client would hire you again.</p>\n","wordCount":150},{"heading":"Common Tradeoffs","id":"common-tradeoffs","markdown":"- **Wow factor vs. reliability.** The dramatic flaming centerpiece is also the fire-marshal call and the insurance line. Spectacle adds failure points.\n- **Budget vs. buffer.** Spending the contingency on a nicer band leaves nothing for the day-of emergency. Resist.\n- **Tight schedule vs. slack.** A packed run-of-show feels efficient until the first 10-minute over-run cascades. Padding looks wasteful and saves you.\n- **Client wishes vs. guest experience.** The client wants a 25-minute thank-you speech; the guests want the bar to open. Mediate toward the room.\n- **Premium vendor vs. known vendor.** The famous caterer you've never worked with vs. the solid one who's saved you before. Familiarity is a feature.\n- **In-house AV vs. outside crew.** The venue's in-house team knows the room but may upcharge; outside crew is cheaper but doesn't know where the breakers are.","html":"<h2 id=\"common-tradeoffs\">Common Tradeoffs</h2>\n<ul>\n<li><strong>Wow factor vs. reliability.</strong> The dramatic flaming centerpiece is also the fire-marshal call and the insurance line. Spectacle adds failure points.</li>\n<li><strong>Budget vs. buffer.</strong> Spending the contingency on a nicer band leaves nothing for the day-of emergency. Resist.</li>\n<li><strong>Tight schedule vs. slack.</strong> A packed run-of-show feels efficient until the first 10-minute over-run cascades. Padding looks wasteful and saves you.</li>\n<li><strong>Client wishes vs. guest experience.</strong> The client wants a 25-minute thank-you speech; the guests want the bar to open. Mediate toward the room.</li>\n<li><strong>Premium vendor vs. known vendor.</strong> The famous caterer you&#39;ve never worked with vs. the solid one who&#39;s saved you before. Familiarity is a feature.</li>\n<li><strong>In-house AV vs. outside crew.</strong> The venue&#39;s in-house team knows the room but may upcharge; outside crew is cheaper but doesn&#39;t know where the breakers are.</li>\n</ul>\n","wordCount":142},{"heading":"Rules of Thumb","id":"rules-of-thumb","markdown":"- Book the venue and lock the date before you promise the client anything else.\n- Always add 10–15% contingency, and treat it as untouchable until 72 hours out.\n- One bartender per 75–100 guests for a standing reception; double it for a champagne toast.\n- Bathrooms and bars are where queues form — design for peak, not average.\n- Load-out always takes longer than you think and costs overtime; schedule it.\n- Build the schedule with 10–15 minutes of float per hour of program.\n- Print the run-of-show; phones die and Wi-Fi fails.\n- A site visit is worth a thousand floor plans.\n- The client's mood is part of the production. Brief them on what to expect and when.","html":"<h2 id=\"rules-of-thumb\">Rules of Thumb</h2>\n<ul>\n<li>Book the venue and lock the date before you promise the client anything else.</li>\n<li>Always add 10–15% contingency, and treat it as untouchable until 72 hours out.</li>\n<li>One bartender per 75–100 guests for a standing reception; double it for a champagne toast.</li>\n<li>Bathrooms and bars are where queues form — design for peak, not average.</li>\n<li>Load-out always takes longer than you think and costs overtime; schedule it.</li>\n<li>Build the schedule with 10–15 minutes of float per hour of program.</li>\n<li>Print the run-of-show; phones die and Wi-Fi fails.</li>\n<li>A site visit is worth a thousand floor plans.</li>\n<li>The client&#39;s mood is part of the production. Brief them on what to expect and when.</li>\n</ul>\n","wordCount":118},{"heading":"Failure Modes","id":"failure-modes","markdown":"- **No rain plan** for an outdoor event — betting the whole thing on the forecast.\n- **Single point of failure** — one DJ, one power feed, one entrance, no backup.\n- **Over-programming the timeline** so the first delay collapses everything behind it.\n- **Spending the contingency early**, leaving nothing for the real emergency.\n- **Trusting verbal confirmations** and skipping the 72-hour reconfirm.\n- **Ignoring load-out**, then paying union overtime at 02:00.\n- **Letting the client direct the floor** on the day, creating two sources of truth.\n- **Designing for the average** queue instead of the 19:30 rush, so bars and bathrooms back up.","html":"<h2 id=\"failure-modes\">Failure Modes</h2>\n<ul>\n<li><strong>No rain plan</strong> for an outdoor event — betting the whole thing on the forecast.</li>\n<li><strong>Single point of failure</strong> — one DJ, one power feed, one entrance, no backup.</li>\n<li><strong>Over-programming the timeline</strong> so the first delay collapses everything behind it.</li>\n<li><strong>Spending the contingency early</strong>, leaving nothing for the real emergency.</li>\n<li><strong>Trusting verbal confirmations</strong> and skipping the 72-hour reconfirm.</li>\n<li><strong>Ignoring load-out</strong>, then paying union overtime at 02:00.</li>\n<li><strong>Letting the client direct the floor</strong> on the day, creating two sources of truth.</li>\n<li><strong>Designing for the average</strong> queue instead of the 19:30 rush, so bars and bathrooms back up.</li>\n</ul>\n","wordCount":99},{"heading":"Anti-patterns","id":"anti-patterns","markdown":"- Booking linens and favors before the venue is locked — sequencing by fun, not by lead time.\n- Treating the floor plan as ground truth without a site visit.\n- Quoting the client a number with no contingency baked in, then \"discovering\" costs later.\n- Saying yes to a day-of change without checking the critical path or pricing it.\n- Running the show from memory instead of a written, printed run-of-show.\n- Hiring the cheapest vendor and assuming reliability comes free.\n- Building a timeline with zero slack to look \"efficient.\"\n- Hiding bad news from the client until it's a crisis instead of a heads-up.","html":"<h2 id=\"anti-patterns\">Anti-patterns</h2>\n<ul>\n<li>Booking linens and favors before the venue is locked — sequencing by fun, not by lead time.</li>\n<li>Treating the floor plan as ground truth without a site visit.</li>\n<li>Quoting the client a number with no contingency baked in, then &quot;discovering&quot; costs later.</li>\n<li>Saying yes to a day-of change without checking the critical path or pricing it.</li>\n<li>Running the show from memory instead of a written, printed run-of-show.</li>\n<li>Hiring the cheapest vendor and assuming reliability comes free.</li>\n<li>Building a timeline with zero slack to look &quot;efficient.&quot;</li>\n<li>Hiding bad news from the client until it&#39;s a crisis instead of a heads-up.</li>\n</ul>\n","wordCount":102},{"heading":"Vocabulary","id":"vocabulary","markdown":"- **Run-of-show (ROS):** the minute-by-minute master schedule of the live event, with cues and owners.\n- **Critical path:** the longest dependent chain of tasks that sets the earliest finish date.\n- **Load-in / load-out:** moving gear in to build the event and out to strike it; load-out is also called \"strike.\"\n- **BEO (Banquet Event Order):** the catering/venue document specifying menu, headcount, setup, timing, and charges.\n- **Comp / guarantee:** the guaranteed minimum headcount you pay for regardless of actual attendance.\n- **Float / slack:** schedule cushion on non-critical tasks.\n- **Gaff / gaffer's tape:** matte cloth tape used to dress cables; doesn't leave residue.\n- **Green room:** private holding space for talent or VIPs.\n- **Walk-in / walk-out:** entrance and exit music/light cue for a speaker or act.\n- **F&B minimum:** the food-and-beverage spend a venue requires.\n- **Strike:** breakdown of the event.","html":"<h2 id=\"vocabulary\">Vocabulary</h2>\n<ul>\n<li><strong>Run-of-show (ROS):</strong> the minute-by-minute master schedule of the live event, with cues and owners.</li>\n<li><strong>Critical path:</strong> the longest dependent chain of tasks that sets the earliest finish date.</li>\n<li><strong>Load-in / load-out:</strong> moving gear in to build the event and out to strike it; load-out is also called &quot;strike.&quot;</li>\n<li><strong>BEO (Banquet Event Order):</strong> the catering/venue document specifying menu, headcount, setup, timing, and charges.</li>\n<li><strong>Comp / guarantee:</strong> the guaranteed minimum headcount you pay for regardless of actual attendance.</li>\n<li><strong>Float / slack:</strong> schedule cushion on non-critical tasks.</li>\n<li><strong>Gaff / gaffer&#39;s tape:</strong> matte cloth tape used to dress cables; doesn&#39;t leave residue.</li>\n<li><strong>Green room:</strong> private holding space for talent or VIPs.</li>\n<li><strong>Walk-in / walk-out:</strong> entrance and exit music/light cue for a speaker or act.</li>\n<li><strong>F&amp;B minimum:</strong> the food-and-beverage spend a venue requires.</li>\n<li><strong>Strike:</strong> breakdown of the event.</li>\n</ul>\n","wordCount":143},{"heading":"Tools","id":"tools","markdown":"Project tools: spreadsheets for budgets and critical paths, Asana or Trello or Monday for task tracking, Aisle Planner / HoneyBook / Cvent for full event management, AllSeated or Social Tables for 3D floor plans and seating. Communications: shared docs, group chats per vendor team, walkie-talkies or radio earpieces on the day. Physical kit: the \"go bag\" — gaffer's tape, zip ties, sewing kit, stain pen, extension cords, label maker, multi-tool, batteries, printed run-of-show, contact sheet, snacks. Contracts and e-signature (DocuSign). For larger productions: CAD floor plans, lighting and AV plots from the production company.","html":"<h2 id=\"tools\">Tools</h2>\n<p>Project tools: spreadsheets for budgets and critical paths, Asana or Trello or Monday for task tracking, Aisle Planner / HoneyBook / Cvent for full event management, AllSeated or Social Tables for 3D floor plans and seating. Communications: shared docs, group chats per vendor team, walkie-talkies or radio earpieces on the day. Physical kit: the &quot;go bag&quot; — gaffer&#39;s tape, zip ties, sewing kit, stain pen, extension cords, label maker, multi-tool, batteries, printed run-of-show, contact sheet, snacks. Contracts and e-signature (DocuSign). For larger productions: CAD floor plans, lighting and AV plots from the production company.</p>\n","wordCount":96},{"heading":"Collaboration","id":"collaboration","markdown":"The planner sits at the center of a temporary organization. The caterer and venue F&B lead drive food and timing; the AV/production company owns sound, lighting, and the technical run-of-show; the florist and rentals team build the look; security and venue ops control access and crowd flow; transport handles arrivals. The client is both customer and collaborator — manage them toward decisions and away from day-of improvisation. On large shows there's a stage manager calling cues and a separate production manager handling load-in logistics; the planner coordinates the whole and stays the client's single point of contact. Clear ownership and a shared run-of-show keep handoffs clean.","html":"<h2 id=\"collaboration\">Collaboration</h2>\n<p>The planner sits at the center of a temporary organization. The caterer and venue F&amp;B lead drive food and timing; the AV/production company owns sound, lighting, and the technical run-of-show; the florist and rentals team build the look; security and venue ops control access and crowd flow; transport handles arrivals. The client is both customer and collaborator — manage them toward decisions and away from day-of improvisation. On large shows there&#39;s a stage manager calling cues and a separate production manager handling load-in logistics; the planner coordinates the whole and stays the client&#39;s single point of contact. Clear ownership and a shared run-of-show keep handoffs clean.</p>\n","wordCount":113},{"heading":"Ethics","id":"ethics","markdown":"Honor the contract and disclose costs honestly — no surprise line items, no hidden vendor kickbacks the client didn't agree to. Respect capacity and fire-code limits; never overbook a room because the client wants more guests. Take alcohol service seriously — licensed bartenders, food alongside drink, a plan for cutting people off and getting them home safely. Protect guest safety and accessibility: clear egress, ADA accommodation, allergen-aware catering. Pay vendors fairly and on time; your reputation with them is your supply chain. Keep client and guest data private. When a request crosses a legal or safety line — exceeding occupancy, unpermitted pyro, ignoring a security recommendation — say no, in writing, and document it.","html":"<h2 id=\"ethics\">Ethics</h2>\n<p>Honor the contract and disclose costs honestly — no surprise line items, no hidden vendor kickbacks the client didn&#39;t agree to. Respect capacity and fire-code limits; never overbook a room because the client wants more guests. Take alcohol service seriously — licensed bartenders, food alongside drink, a plan for cutting people off and getting them home safely. Protect guest safety and accessibility: clear egress, ADA accommodation, allergen-aware catering. Pay vendors fairly and on time; your reputation with them is your supply chain. Keep client and guest data private. When a request crosses a legal or safety line — exceeding occupancy, unpermitted pyro, ignoring a security recommendation — say no, in writing, and document it.</p>\n","wordCount":112},{"heading":"Scenarios","id":"scenarios","markdown":"**Outdoor wedding, 200 guests, 30% chance of thunderstorms on the day.** The couple is set on a garden ceremony. At contract time I require a tented backup and set a rain call: noon decision, my discretion, communicated to the couple in advance so they're not negotiating with the sky at 11:00. I book a clear-span tent on a 48-hour hold with a same-day install option and price both scenarios into the budget. The morning of, radar shows a line of storms arriving at 17:00, ceremony at 16:00. The couple wants to wait. I make the call at noon: tent goes up. It costs $4,200 from contingency. The storm hits at 16:40, mid-cocktail hour, and nobody gets wet. The couple thanks me at load-out. The lesson the client never sees: the decision was made calmly at noon, not in panic at 16:30 when the tent crew was already booked elsewhere.\n\n**Corporate product launch, 600 guests, single freight elevator.** Site visit reveals the venue has one freight elevator and a 14:00 union dock cutoff, but my AV plot needs a 40-foot LED wall, staging, and 30 catering cases — all of which want that elevator the same afternoon. That elevator is my constraint (theory of constraints). I sequence load-in by the critical path: LED wall and rigging first (longest build, six-hour focus time), then staging, then catering last because it loads through a side door. I split the catering delivery to the side door entirely, freeing the elevator. I add a $1,800 overnight rigging crew to start the LED build at 22:00 the night before rather than fighting the 14:00 cutoff. Build finishes with 90 minutes of float for a tech rehearsal. Without the site visit, I'd have discovered the one-elevator problem at load-in with trucks stacked in the alley.\n\n**Gala, client wants to add a 20-minute donor video at T-48 hours.** The board chair calls: add a tribute video before dinner. Does it touch the critical path? Yes — it pushes dinner 20 minutes, which collides with the kitchen's plated-service window and the band's contracted end time. I don't say no flatly. I price it: the band runs $900 in overtime, or I cut the video to 8 minutes and trim the two-minute walk-in music to recover the rest. I present both to the chair with the tradeoff stated plainly. They take the 8-minute version. Dinner stays on time, the kitchen fires hot food, and the band ends on contract. The client got their moment; the room never felt the squeeze.","html":"<h2 id=\"scenarios\">Scenarios</h2>\n<p><strong>Outdoor wedding, 200 guests, 30% chance of thunderstorms on the day.</strong> The couple is set on a garden ceremony. At contract time I require a tented backup and set a rain call: noon decision, my discretion, communicated to the couple in advance so they&#39;re not negotiating with the sky at 11:00. I book a clear-span tent on a 48-hour hold with a same-day install option and price both scenarios into the budget. The morning of, radar shows a line of storms arriving at 17:00, ceremony at 16:00. The couple wants to wait. I make the call at noon: tent goes up. It costs $4,200 from contingency. The storm hits at 16:40, mid-cocktail hour, and nobody gets wet. The couple thanks me at load-out. The lesson the client never sees: the decision was made calmly at noon, not in panic at 16:30 when the tent crew was already booked elsewhere.</p>\n<p><strong>Corporate product launch, 600 guests, single freight elevator.</strong> Site visit reveals the venue has one freight elevator and a 14:00 union dock cutoff, but my AV plot needs a 40-foot LED wall, staging, and 30 catering cases — all of which want that elevator the same afternoon. That elevator is my constraint (theory of constraints). I sequence load-in by the critical path: LED wall and rigging first (longest build, six-hour focus time), then staging, then catering last because it loads through a side door. I split the catering delivery to the side door entirely, freeing the elevator. I add a $1,800 overnight rigging crew to start the LED build at 22:00 the night before rather than fighting the 14:00 cutoff. Build finishes with 90 minutes of float for a tech rehearsal. Without the site visit, I&#39;d have discovered the one-elevator problem at load-in with trucks stacked in the alley.</p>\n<p><strong>Gala, client wants to add a 20-minute donor video at T-48 hours.</strong> The board chair calls: add a tribute video before dinner. Does it touch the critical path? Yes — it pushes dinner 20 minutes, which collides with the kitchen&#39;s plated-service window and the band&#39;s contracted end time. I don&#39;t say no flatly. I price it: the band runs $900 in overtime, or I cut the video to 8 minutes and trim the two-minute walk-in music to recover the rest. I present both to the chair with the tradeoff stated plainly. They take the 8-minute version. Dinner stays on time, the kitchen fires hot food, and the band ends on contract. The client got their moment; the room never felt the squeeze.</p>\n","wordCount":444},{"heading":"Related Occupations","id":"related-occupations","markdown":"- **hotel-manager** — controls the venue, F&B, and rooms the planner depends on.\n- **chef** — drives catering timing, plating, and the kitchen fire-time constraint.\n- **project-manager** — shares the critical-path, scheduling, and stakeholder-management toolkit.\n- **sommelier** — partners on wine and beverage programs for upscale events.\n- **logistics-coordinator** — overlapping discipline for load-in, transport, and supply timing.\n- **operations-manager** — adjacent in running live, time-bound operations with vendors and staff.","html":"<h2 id=\"related-occupations\">Related Occupations</h2>\n<ul>\n<li><strong>hotel-manager</strong> — controls the venue, F&amp;B, and rooms the planner depends on.</li>\n<li><strong>chef</strong> — drives catering timing, plating, and the kitchen fire-time constraint.</li>\n<li><strong>project-manager</strong> — shares the critical-path, scheduling, and stakeholder-management toolkit.</li>\n<li><strong>sommelier</strong> — partners on wine and beverage programs for upscale events.</li>\n<li><strong>logistics-coordinator</strong> — overlapping discipline for load-in, transport, and supply timing.</li>\n<li><strong>operations-manager</strong> — adjacent in running live, time-bound operations with vendors and staff.</li>\n</ul>\n","wordCount":69},{"heading":"References","id":"references","markdown":"- *The Business of Event Planning* — Judy Allen.\n- Project Management Institute, critical path method and PMBOK scheduling fundamentals.\n- Certified Meeting Professional (CMP) International Standards.","html":"<h2 id=\"references\">References</h2>\n<ul>\n<li><em>The Business of Event Planning</em> — Judy Allen.</li>\n<li>Project Management Institute, critical path method and PMBOK scheduling fundamentals.</li>\n<li>Certified Meeting Professional (CMP) International Standards.</li>\n</ul>\n","wordCount":23}],"computed":{"wordCount":2633,"readingTimeMinutes":12,"completeness":1,"backlinks":["announcer","baker","barista","bartender","chef","concierge","dungeon-master","floral-designer","funeral-director","hairstylist","hotel-manager","restaurant-manager","sommelier","travel-agent"],"verified":false,"aiDrafted":true,"unverifiedAiDraft":true},"git":{"created":"2026-06-26","updated":"2026-06-26","revisions":2,"authors":[{"name":"soul-atlas","commits":2}],"timeline":[{"date":"2026-06-26","author":"soul-atlas"},{"date":"2026-06-26","author":"soul-atlas"}]},"citation":{"apa":"soul-atlas (2026). Event Planner [SOUL]. SOUL Atlas. https://soul-atlas.github.io/occupations/event-planner","bibtex":"@misc{soulatlas-event-planner,\n  title        = {Event Planner},\n  author       = {soul-atlas},\n  year         = {2026},\n  howpublished = {SOUL Atlas},\n  note         = {SOUL.md, version 2026-06-26},\n  url          = {https://soul-atlas.github.io/occupations/event-planner}\n}","text":"soul-atlas. \"Event Planner.\" SOUL Atlas, 2026. https://soul-atlas.github.io/occupations/event-planner."}}