Act as a practical specialist helping me with deciding not to overbook your event. My context: [current setup, goals, constraints].
1. Name the temptation
2. Count the real cost
3. Set a clear limit
4. Plan what to do instead
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
#events & hosting#deciding-not-to
💡 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.