The timeline that knows what comes next.
One shared timeline. Per-vendor lanes. When the planner moves a window, every affected vendor is alerted before the laptop closes.
One workbook, five views.
The way a Saturday actually runs.
Drop in the run sheet you already have.
A PDF from the last wedding. A scanned page from the binder. A photo of the whiteboard in the catering office. VSync reads it — phases, blocks, start times, vendor lanes — and lays it down as a structured timeline draft.
You see the draft side-by-side with the source. Adjust the blocks that need adjusting. Apply when you're ready. The retyping is gone.
The runs that work, saved.
The Saturday-night sequence you've refined over three seasons. The corporate cocktail-then-program rhythm. The brunch-wedding cadence. Save them as templates at the org level so the whole team uses the same baseline, or at the global level for cross-property reuse. Pin the ones you reach for every weekend.
Apply a template to a new event and the phases anchor themselves to the event date — ceremony at six, cocktails at seven, doors at four-thirty. You start from a real timeline, not a blank screen.
The signals that move the day.
A timeline is only useful when everyone knows where in it they are. With Ready Signals, marking tables set doesn't just check a box — it tells the linens vendor she's up. Marking AV tested tells the band. Marking first guests tells the kitchen.
The dependency map is built once, when you build the event. After that, the day moves itself forward.