The timeline
A timeline for the whole weekend that stays true as plans change.
A wedding day timeline is the half-hour-by-half-hour schedule of your wedding, and the good ones cover the whole weekend, from the rehearsal dinner to the farewell brunch. Juno's timeline builder lays out each day in lanes, in your venue's local time. June keeps it honest: when a vendor email or contract moves a time, they propose the update instead of letting the schedule quietly drift out of date.
Scope
Weddings are weekends, not days.
The ceremony gets the attention, but the schedule that actually needs managing starts earlier: welcome drinks, the rehearsal, vendor load-ins, hair and makeup windows, the gap where someone has to move flowers from the ceremony to the reception. Juno's timeline holds every day of the weekend, each laid out chronologically, with overlapping events side by side in lanes so a 30-minute collision is visible before it's a problem.
Days label themselves relative to your wedding date ("Day Before," "Wedding Day," "Day After"), and if the date moves, the labels move with it.
The hard part
The timeline that's wrong is worse than no timeline.
Every couple builds a timeline. The failure is upkeep: the photographer moves first-look by 30 minutes over email, the caterer's contract says service starts at 6:00 not 6:30, and the beautiful document from two months ago is now confidently wrong.
This is June's job. They read your forwarded vendor threads and uploaded contracts, and when an agreed time differs from what's on the timeline, they propose the correction, source attached, waiting for your approval. The timeline stays in step with what's actually been agreed, not what was true in March.
- Times are venue-local, always: you type 4:30pm, everyone sees 4:30pm, regardless of what time zone anyone opens the app from.
- Events carry start and end times, so duration collisions surface instead of hiding.
- Both partners edit the same timeline: no "final_v3_ACTUAL.xlsx" in two inboxes.
Build the weekend once, and let it stay right.
Start with the times you know, and June fills in and corrects as the vendor paperwork lands.
Questions
Asked, answered.
When should we build our wedding day timeline?
Rough it in as soon as the venue and ceremony time are booked; those anchor everything else. Expect it to change: the point of keeping the timeline in software rather than a document is that vendor confirmations keep reshaping it right up to the final month, and updates should cost seconds, not a reformatting session.
Will the timeline shift if we travel across time zones?
No. Juno treats every time as the venue's wall-clock time: if the ceremony is at 4:30pm at the venue, it reads 4:30pm whether you're checking from home, the office, or the plane. No silent time zone math on the schedule for your wedding day.
Can June build the timeline for us?
They draft it from what they read. Upload contracts and forward vendor threads, and June proposes timeline events from what's agreed there: load-in windows, service start, send-off. You approve each one, and the running order stays yours to arrange.
Keep reading