Digital invitation for dance-only wedding guests

It's Friday afternoon and your cousin texts: "What time should we come for the dancing?" She isn't staying for dinner. She doesn't want to sit through three courses to reach the part she actually came for, and she doesn't want to guess. A Digital invitation answers that in one line: the time the floor opens, what to wear, and a way to say yes. For dance-only wedding guests, that line is the whole invitation. You can build one today from the collection and send the link before the weekend.

The problem isn't the dancing. It's the wording. Write "dinner at 9, dancing after" and your cousin guesses, arrives during the speeches and stands by the bar looking for a seat she doesn't have. Most of the confusion around dance-only guests comes from one missing line: the hour the floor opens.

A Digital invitation gives dance-only guests an exact time

Treat the dancing as its own scene, not a footnote. Dinner and dancing get separate lines with separate times. Dinner at 9:00 and the floor opening at 10:30 are two different moments, and the invitation should say both. Then nobody has to work out whether they're late, and nobody turns up at table 7 asking where to sit. In the editor the scenes sit one after the other — a long dinner, then a last dance — so the evening reads in the order it happens.

• Dance floor opens at 10:30 — a time, not "after dinner".
• An end time you can plan around, such as until 3:00, so people can book a taxi or a sitter without messaging you.
• If there's a cocktail hour first, write it as "Cocktails 9:00, dancing 10:30".
• No table number for anyone who isn't eating. Their meeting point is the bar or the floor.

How to word it for dance-only wedding guests

"Dance-only guest" reads like a category on a list, and the word "only" does the wrong job. Write what you mean instead: "We'd love to see you on the dance floor from 10:30." Same information, no ranking, and one detail people actually need. The hour says more about their place in the evening than any label can.

If you share the link on WhatsApp, keep the message plain: "Your part starts at 10:30, no need to come for dinner." Then set your RSVP question as "Will you be joining us for the dancing?" The answers arrive in one list inside the invitation, so you're not counting yeses across three group chats. Guests don't install anything: they open the link in a browser and reply from their phone.

Give dance-only guests a time and a dress code, not a label. That is the whole etiquette.

One dress code for the whole night

Don't split the dress code by arrival time. "Formal for dinner, casual for dancing" tells your cousin her outfit doesn't fit. Keep one code for the night and make it practical: "formal, comfortable shoes for grass" if the floor is in the garden. If the dancing runs to 3:00, a line about coats or air conditioning settles more questions than any etiquette paragraph. Everything sits in the same invitation — times, dress code, RSVP question — and you can edit any of it after sending, without resending anything. Start with a design from the collection and send one link that answers the questions you'd otherwise get at 11pm.