Build a sorority formal guest guide that answers key questions

Build the invitation around decisions

Include date, time, venue address, RSVP instructions, guest rules, dress guidance, food information, and a contact. If the event spans a weekend, distinguish the required formal event from optional activities and name who books each part.

• Mark tentative details plainly until confirmed.
• Give a date when the final itinerary will be shared.
• Use an accessible format people can open on a phone.

Publish a return plan as clearly as the arrival plan

Provide hotel check-in, transport pickup points, accessible options if needed, expected end time, and the safe route home. Tell guests whom to contact if plans change. Review the guide with someone who did not plan the event; their questions show what is missing.

Send an early note and a confirmed itinerary separately

An early message can state the date window, city or venue if selected, RSVP method, and what remains tentative. Once contracts and transport are confirmed, send one final guide with the address, arrival time, dress guidance, meal information, hotel booking responsibility, pickup point, return plan, and a day-of contact. Label optional weekend activities so guests can distinguish them from the chapter event.

Build a one-page guest card

Keep the essentials together: event date and address; RSVP method and deadline; arrival and check-in; attire and venue conditions; food and accessibility contact; hotel booking responsibility; outbound and return rides; and a contact if plans change. Remove fields that do not apply. Do not publish a private guest list or sensitive requests in this guide.

Test it with someone who did not plan the event

Give the draft to a member or guest outside the committee. Ask them to find the check-in point, the last return option, and which bookings they must make. Their unanswered questions reveal work the committee still owns. Update one authoritative copy of the guide rather than sending disconnected corrections.