Writing · Templates
A function-by-function checklist before you build your wedding website
Every function on a Vowframes site needs its own venue, timing, invited list and RSVP target, gathered before you start building. Copy the four sections below and fill them in function by function — the details, the guest split, the RSVP number each vendor needs, and what the photo gallery needs before the wedding, not after.
Most of the delay in building a multi-function wedding site happens after the site is already live, when someone notices that Saturday's guest list was never actually separated from Friday's. Vowframes treats every function as its own event with its own venue, timing and invited list, but it can only hold what you hand it. Gather that once, function by function, and the build itself takes an afternoon rather than two weeks of edits.
Copy the four sections below into your own document. A blank field is a task to chase down. A guessed one is a mistake you fix later, usually during the week you have the least time for it.
One block per function, not one for the whole week
For each function — Haldi, Mehendi, Sangeet, the ceremony, the reception, whichever apply — write down: the name, the date, the time guests should actually arrive if it differs from the time on the card, the venue with a map link, any dress code or colour theme, and two plain sentences describing what happens there for a guest who has never been to one before.
Repeat the block once per function rather than adding rows to a single table. A wedding with five functions needs five separate answers to almost every field, and a shared table quietly encourages you to leave the differences out.
Split the guest list the same way
For each guest, note a name, one reliable way to reach them, and which functions they belong to — the column that matters most. Someone invited only to the reception should not appear on the Mehendi list even as a maybe.
While you're at the list, decide one thing for the site as a whole: open to anyone who has the link, or restricted to the people on it. Vowframes supports both, and every guest you add gets a link tied to them rather than a shared address, so this is a decision you make once rather than guest by guest.
Set an RSVP target for each function, not the wedding
Vowframes collects RSVPs once per function rather than once for the whole event, so write down, function by function, the number each vendor actually needs and by when. The Sangeet caterer's deadline is not the ceremony venue's deadline, and the reception's headcount is not either of them. Responses come back to you as a usable number per function, so the target you write here is what you'll be checking arrivals against as they come in.
Settle the photo gallery before the wedding, not after
The gallery attaches to the site and stays restricted to the guests who were invited, which leaves one thing worth settling in advance rather than three weeks later: who is uploading. Write down your photographer's contact and whether images go straight into the gallery or through you first. If you also want guests' own phone photographs collected, decide that now — each guest can find the photographs they appear in once the gallery is populated, so the earlier the pictures land in it, the sooner people stop messaging you asking for the one from Thursday night.
This checklist deliberately leaves out travel logistics, a gift registry and seating charts. Plan those on your own timeline — they don't belong to the function-by-function picture above, and nothing here depends on having them settled first.