For the maid of honour with the weekend to run
A hen weekend is three days, ten women and a hundred group messages. One page holds the timeline, the dress task and the secrets — safely locked from the bride.
Every hen plan runs through a group chat that should not exist: the one the bride is not in. It starts well — a weekend in October, a town with restaurants — and by month three it is a scroll of fragments. Dinner booked for this Saturday, the dress code decided in one burst and forgotten, surprise timings negotiated in replies nobody can find again.
A locked invitation page ends the fragmentation. The weekend's plan lives on one link, every hen replies on it, and the password keeps the whole thing away from the one person it must stay away from.
Hen weekends have real sequences: trains arriving at different hours, an activity booked for Saturday morning, dinner with a reservation time, drinks somewhere that was a rumour until it was not. The page carries a multi-day schedule so everyone reads the same plan instead of the group's latest forward.
The matching something-or-other, the task nobody admits to owning, the toast the shy one volunteered for — tasks written on the page beside the schedule stop becoming chat archaeology in the week before you travel.
A birthday surprise needs its how-to; a hen party is the same problem in a bigger dress. Arrival times and the surprise moment live on the locked page, and the group's chatter carries no detail worth screenshotting into the wrong chat.
A hen page is a locked page. The password travels inside the hen group with the link, and the bride — who may well be in the other wedding chat, or borrowing someone's phone on the sofa — meets nothing. Everything sensitive sits behind it: the weekend schedule, the surprise timings, the gift collection for the present everyone agreed on.
If contributions need collecting, the gift feature records a sender and a message with whatever arrives, so the spreadsheet version of this week can retire along with the chat thread of forty receipts.
One thing plainly: My Joyfullday's dedicated, fully designed invitation sites are weddings, birthdays, baby showers and graduations. Hen parties and bridal showers ride the same page machinery — invitation, schedule, replies, reminders — built from a design you choose and words you write. Weddings do have a template library to borrow a mood from, which helps a hen page look part of the family without pretending to be its own occasion.
How it works
Build the invitation in the web app, or message Jitabi on WhatsApp with the shape: hen weekend in October, two nights, dinner booked Saturday. It drafts the page; you set the schedule and the dress task.
Switch on password protection. Set the reply so each hen marks the days she attends, her meals and allergies, and any plus-one inside the limit you chose for the last night.
Publish, then send the link and the password in the hen group — the one without the bride — and pin it there. Everyone who joins the weekend later reads one plan instead of three forwarded screenshots.
Watch the live guest list as days get claimed, remind the silent names before booking deadlines bite, and give each restaurant and activity the number on the page rather than the number the chat last guessed.
Questions
Invite through a group she is not in, or a private thread just for the hens, and keep the page password-protected. The link alone reveals nothing to anyone without the word, which is exactly what the tool is for.
Ask on the form which days each person covers. The live list then shows the weekend in layers — Friday drinks, Saturday dinner, Sunday brunch — so the bookings match the crowd rather than the loudest guess.
No. Hen weekends use the same page machinery as any gathering. The wedding library exists if you want a family look, and the schedule, the dress task and the replies matter far more than a template built for stag weekends.
The gift collection records sender and message with what arrives, which suits a shared gift or a contribution pot. Treat it as the presents version rather than a payment system, and keep any spending decisions honest in the group.
It gets its own page, same as any gathering: its replies, its deadline, its guest list. Keeping the shower and the hen weekend as separate pages stops two different crowds and two different sets of secrets colliding on one list.
Add the co-organiser as a collaborator with the access level the two of you agree. One holds the schedule edits, the other manages replies and reminders, and no decision lives in a chat message nobody saw.
Get Started
One locked page for the schedule, the dress task and the surprise; one reply list that tells you the real numbers; and a group chat free to do what group chats are for — planning nothing and celebrating everything.
