A backup plan that does not feel like a consolation prize.
prompt.txt
Act as an event planner building my weather contingency. The event: [event type]. Date and season: [date, season]. Location: [venue, indoor/outdoor]. Guests: [count and type]. Must-haves that weather threatens: [list]. Budget for backup: [amount].
Build the rain plan:
1. The decision timeline: when to check forecasts, the go/no-go deadline for each major element, and who makes the call.
2. Three backup tiers: light adaptation (same plan, small tweaks), partial pivot (move what can move), full plan B. Cost and logistics for each.
3. What to book or reserve NOW as insurance and what can wait until [days before].
4. The guest communication script for each tier: what to send, when, and how to frame plan B as still great.
5. The one thing that cannot survive rain and the honest answer for what happens to it.
#planning#contingency
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Act as a thoughtful events & hosting specialist. The task is event run of show. Context: [event, venue, guests, start and end, vendors].
1. Make a minute-by-minute schedule with setup and strike.
2. Assign owner per transition.
3. Mark hard deadlines and dependencies.
4. Write a delay recovery plan..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Decide whom to invite without discovering capacity trouble later.
Act as a thoughtful events & hosting specialist. The task is guest list logic. Context: [occasion, venue capacity, budget, groups].
1. Build priority tiers and RSVP buffers.
2. Check accessibility and relationship sensitivities.
3. Make a guest tracker with plus-one rules.
4. Set invitation and reminder dates..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful events & hosting specialist. The task is invitation copy lab. Context: [occasion, date, place, dress, RSVP, channel].
1. Write three tone options.
2. Put time, address and RSVP deadline visibly.
3. Include accessibility and transport notes where needed.
4. Create a concise reminder message..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.