The DJ texted the bride about load-in
The bride is at hair and makeup. She has had three coffees and zero second to read a text.
The DJ had no one else to ask. The PDF he had said east gate, but the venue switched.
When the DJ texts asking about reception entrance, the answer goes to the DJ, the MC, and the photographer in one tap. The bride keeps her phone in her bag.
Free 30-day trial. No credit card. Works alongside the planning tools you already use.
Most weddings get coordinated through a wedding day group text that pings everyone with everything. By 2pm the bride is the only one who knows what the new entrance time is, and she is the one being asked.
The bride is at hair and makeup. She has had three coffees and zero second to read a text.
The DJ had no one else to ask. The PDF he had said east gate, but the venue switched.
The list changed Friday after the rehearsal. Half the vendors got the new version. Half did not.
No one knows whose version is current. The bride keeps getting screenshots.
Reception entrance was supposed to be 6:00pm. Hair ran long, so it is now 6:15pm.
No central place to ask. So the DJ asks the bride, who has to find the new time and reply.
Catering paced the apps for 60 minutes. Cocktail hour is now compressed to 50.
Nobody told catering. The pacing for the appetizers is now wrong by 15 percent.
The wedding party order changed Wednesday. The MC has Tuesday's list.
Three minutes before reception entrance, the MC realizes the order is wrong.
A DJ asks about the reception entrance. The coordinator answers once. The DJ, MC, and photographer all see the same cue. The bride's view updates silently.
Every wedding day cascade comes down to four jobs: route the answer, sync the right vendors, keep the couple out of it, and verify the handoff.
A vendor question routes to the coordinator (or helper) instead of pinging the bride or groom.
DJ asks about the reception entrance. The coordinator drafts the answer once. The DJ, MC, and photographer all see it.
The couple is not the source of truth. The shared live timeline is.
Pick the roles that need the update. Photo, DJ, MC, catering, venue, or everyone.
A first look move pings photo only. A ceremony shift pings everyone. The DJ does not get the family list change.
No more group text noise. The right people get the right cue.
No new PDF resent. No version 3 of the runsheet. The timeline updates in place.
When First Look moves to 3:10pm, every role's view shows 3:10pm. No one is reading last Tuesday's version.
Stale PDFs are how vendor coordination breaks. Live timelines are how it stays fixed.
When a vendor reads the update, you see a green dot next to their name.
Photographer Theo acknowledges the First Look move. Coordinator's vendor roster turns green. No reply text needed.
You do not have to wonder if the message landed. You can see.
Track who has arrived, who is late, and who needs a reroute, all from the same view.
DJ is at the wrong entrance. Reroute him. Mark him checked in. The vendor roster turns green when he is moving.
Coordination is about the people, not just the timeline. The roster keeps both in one place.
By default, vendor cue updates do not push a notification to the couple. Their role view still shows the new time.
Reception entrance moves to 6:15pm. DJ sees the cue. Bride sees nothing pop. She is at family portraits.
The couple hired you to absorb this layer. EventSync is how you absorb it.
Start from a template or your existing runsheet. Drag blocks. Assign roles. Anchor the ceremony and dinner.
Visual: timeline editor with role tags.Photographer gets a Photo role. DJ gets a DJ role. Each role sees only its cues. Send invite codes by email or link.
Visual: invite list with role pills.When a vendor asks, answer once. The broadcast goes to the right roles. The bride keeps her phone in her bag.
Visual: coordinator phone with a routed broadcast.If the couple is the de facto coordinator, EventSync routes vendor questions to a designated helper instead of pinging the bride. Most often a maid of honor or family member.
See setup steps →Hired coordinators use EventSync as the coordination layer their planning suite did not include. SmartRipple, role broadcasts, vendor check-in, acknowledgement receipts.
Full day-of app overview →Each wedding lives in its own day-of view. Associates run their wedding. The lead sees live status from her phone without calling for an update.
See Pro pricing →Free planning suite for the year before. Pay only for the day-of layer. Same engine across tiers, only the limits change.
Couples building the timeline through the planning year.
Couples who want vendor coordination on the day itself.
Coordinators, planners, venues, and photographers running multiple weddings.
No setup fees. No per-vendor charges. Cancel any time.
Build the timeline. Invite the vendors. Answer once. EventSync routes the rest.
Same engine as the live coordinator demo. Built for the wedding day, not the year before it.