The Rain Plan That Only Holds 650
You are producing a 1,200-guest outdoor awards dinner in a tent on a waterfront lawn in mid-September, in a region that has seen three named storms in that month over the past decade. The tent seats 900; the contracted indoor backup ballroom holds 650 theater-style or 500 banquet. Your event cancellation policy carries a 72-hour weather waiting period and excludes any named-storm advisory already issued at binding - none was. The keynote is a television personality flying in same-day. A further 180 guests are international. The catering contract guarantees 1,100 covers. The total budget is $640,000 and cancellation would recover roughly 40%.
1. Build the go/no-go framework before anything is on the forecast. What has to be decided, by whom, and by when?
Read the worked answer
Work backwards from the longest lead time, not forward from the weather.
| Task | Lead time |
|---|---|
| Ballroom flip + catering replan | 10 hrs |
| Catering guarantee change (contractual) | 72 hrs |
| Tent strike or reinforcement | 24–36 hrs |
| Keynote flight re-accommodation | 24 hrs |
| International guest notification | 48 hrs |
The binding constraint is the 72-hour insurance waiting period. The policy responds to weather occurring after that window, so your first documented gate must sit at T-96, ahead of the clock.
Gates: T-96 activate contingency spend → T-72 final guarantee change and insurer notice → T-24 execute the indoor move or cancel.
One decision owner, named in writing, with a named alternate of equal authority. A committee cannot make a weather call at 2 a.m.
Pre-agree numeric triggers, not adjectives: sustained wind above 25 mph in the event window; any lightning within 10 miles during load-in or the event; an active NWS watch for the site.
Timestamp every gate decision. That record is what the insurer and the board will test six months later.
2. The backup ballroom holds 650 and you have 1,200 confirmed. What are the real options, and how do you choose between them?
Read the worked answer
Two seatings in the ballroom. Doubles labor and F&B, and destroys the single shared moment the awards exist for. Reject.
Full simulcast - 650 seated, 550 under cover. Needs a second production chain, two hosts, and a design that makes the overflow space feel like the room rather than a waiting area. Cost ≈ $45,000–$60,000.
Relocate to a convention centre. Destroys the waterfront premise that justified the event, needs 20 coaches and $80,000+ at short notice. Reject unless the tent itself is condemned.
Re-scope to a standing reception. Holds 1,200 under cover, drops the seated dinner, moves the awards to a 650-seat VIP dinner the following night. Cheapest, but splits the audience across two nights.
How to choose: on purpose, not on cost. If the event exists so that 40 awardees are honoured in front of the whole community, the simulcast preserves the purpose and the reception re-scope does not. Identify the purpose first, then take the cheapest option that preserves it.
3. Who is told what, and in what order?
Read the worked answer
Internally first, with one script. Staff get a single approved line and an explicit instruction not to speculate. Assume anything said in a staff chat group reaches an attendee within the hour.
Decision sequence: executive sponsor → venue and caterer (contractually obligated, and they need the lead time) → keynote's management → board chair → sponsors (they bought visibility and need an option to reallocate) → attendees.
Attendees get two messages, not one: a "we are monitoring, here is the plan" at T-72, and a definitive instruction at T-24. Silence until the last minute is what causes the reputational damage - not the rain.
International guests get the T-72 message with a named contact and the hotel's change policy, because their rebooking window closes before everyone else's. Treating them as a subset of the local audience guarantees a complaint spike you will still be answering in January.