Festival Hen Do Invitations: A Line-Up, Not a Group Chat

Someone in the group chat asks whether dinner is at eight or half eight. Two people answer. A third sends a screenshot of a message from Tuesday. The bride scrolls back four days to find the address, and by the time she finds it, someone has already booked a table in the wrong town.

Festival hen do invitations work like a festival poster: the whole weekend on one page, in the order it happens. Name, city, date, set times, wristbands, dress code. One link, and nobody has to scroll back through a week of messages.

Festival hen do invitations: the poster comes first

Design the cover the way you would design a poster. Hen Fest, Brighton, 14 June, and one line underneath: bring glitter. Each piece of that goes into its own field in the editor — headline, names, date, phrase, place — with a character counter so the frame never eats the bride's name.

• Name of the weekend, city and date, for example: Hen Fest, Brighton, 14 June.
• One line of attitude under the title: bring glitter and shoes you can dance in.
• A group photo or a confetti shot as the cover; the invitation takes up to six of your own photos and frames them for you.
• A phrase field for the in-joke only your group uses — the nickname, not 'a magical weekend'.

Set times that actually get read

Build the invitation as chained scenes, like a line-up. Arrival and wristbands. Glitter session. Dinner. Last dance. Each scene carries its own time, place and photos, so the evening reads in order instead of in one long paragraph nobody finishes.

If dinner moves from 9:00 to 9:30, you edit that scene and the link stays exactly the same. No correction message, no 'ignore the last one'. You can also switch on music so the invitation plays from the first click — set up in the browser editor, nothing to install on anyone's phone.

An invitation that reads like a line-up answers most of the questions before anybody has to ask them.

Wristbands and a dress code in one line

Say how the wristbands work in the arrival scene: who is holding them, from when, and where. Wristbands at the door, 6 to 7pm. Then the dress code in one sentence, not a paragraph: festival glam, boots, sequins, a layer for later. If you want colour groups, give each group a colour inside the scene instead of hiding it in a wall of text.

Wristbands, RSVP and the last dance

Use the RSVP questions for the details that keep changing: are you coming for the first hour, are you staying for the last dance, do you want a personalised wristband. Replies land inside the invitation in one ordered list instead of scattered across the chat. And anyone opening the link late sees the newest version, because changing a time, a place, a map or the dress code doesn't mean resending a single thing.

A link for everyone, paper only if someone is keeping it

The invitation is its own webpage, not a PDF. You share the link or the QR code in the group and guests open it on a phone and reply from there, with no app to download. If the bride wants something for the album, print a few copies yourself and keep the link as the version that stays current.

Start with the cover: festival name, city, date and the line under it. Then the scenes with their times, then the wristband note and the dress code. Try a design for free at Send The Joy, personalise the cover, and publish once the whole weekend reads in order from arrival to last dance.