For weekends, not evenings
Welcome dinner, ceremony, late music, goodbye brunch: a multi-day timeline reads a whole weekend on a single page, one block per day, so guests know where they belong without a spreadsheet.
Multi-day events fail in a predictable way: too much, all at once. When the plan arrives as paragraphs in a group message, guests anchor on the one moment they recognise, forget the rest, and on Friday evening still wonder whether the welcome dinner includes their branch of the family. The Lindqvist reunion proves it every year, and wedding weekends run the same risk at slightly larger scale.
A timeline section answers it by giving each day its own block: the date, a heading, the events in order, with place and time beside each one. A guest who only comes Saturday scrolls to Saturday, and reads the weekend arranged the way they will actually live it.
Friday, Saturday and Sunday as separate blocks, each opening with the day’s date and one honest line about its tone. The whole weekend fits a screen of scrolling instead of three screens of prose.
When Friday’s dinner is at the restaurant and Saturday’s ceremony is at the church, each block carries its own address and arrival note. Guests switch days without switching documents.
In plain words: welcome dinner for those already in town, brunch for everyone. Guests make plans from a labelled timeline far more readily than from a paragraph that hopes they infer it.
Get the order right and the page almost organises itself:
Weekend guests open the invitation in fragments: booking the flight, the evening before, a taxi on the day. A timeline suits that pattern; the block someone needs loads quickly on a phone and is short enough to read in a corridor. If Sunday changes, you edit Sunday, and the next guest to scroll reads the corrected brunch time while Friday’s dinner stays exactly as written.
For the host it doubles as a working schedule. The order of events, in one place, with the wording already done, can be handed to caterers and family helpers as it stands. If a partner or a parent is keeping the page alongside you, collaborators with their own access levels keep the plan in more than one pair of hands without descending into committee.
How it works
Weddings are a dedicated type with the full multi-section guest site, including the timeline; a reunion or anniversary weekend gets the same machinery on a plainer page. Jitabi will draft the blocks from a message that names the days.
Date, tone, events in order, place beside each. In-app drafting can turn a messy list of intentions into day-by-day lines; you correct the hours nobody has confirmed yet.
Guests see nothing until the site is live, so the weekend exists in full before the first message does. Publish once, then hand the link to whoever is forwarding it onward.
One page, one list of replies, counting the weekend as a yes per guest. When the final brunch time settles, change the block and every later reader gets the true plan.
Questions
Yes, that is the usual shape of a weekend. Each day’s block carries its own time and place details, so the welcome dinner and the ceremony can sit at separate addresses, and guests find the day they belong to and its directions in one scroll.
The reply lands against the invitation as a whole, with a note field beside it where a guest can say which days they will manage. If day-by-day numbers matter for catering, ask for that detail explicitly in the page wording; guests answer what they are asked.
A long weekend reads comfortably, and a full week works with headings guests can jump between. The limit is attention rather than software: once a day’s block runs far past a screen, some of its detail probably belongs in a note to that day’s guests.
Yes. Publish the change and the timeline grows a block for everyone holding the link, with nothing needing resending. If the addition genuinely changes the weekend, a short line to the group saying there is a new day on the page is fair.
Better than with paragraphs. One day per block with clear times suits a phone screen, and printing the event’s QR code on paper cards gives the same weekend, always current, to guests who like something in hand.
Get Started
Build one block per day, mark what each one is for, and put the whole thing on a single page. Start free, and the family reads one true version of the weekend instead of four remembered ones.
