Wedding day logistics without a hundred phone calls

A wedding is a logistics event wearing a dress. Two venues, a tight schedule, suppliers with arrival windows, a photographer paid by the hour, and eighty guests who have never been to this village.

The single most useful principle: the couple should not be coordinating anything. Every question that reaches them is a failure of the plan.

Nominate the point people

Not one coordinator - several, by group:

• One for the wedding party, responsible for getting the right people to the right place on time.
• One for family, especially older relatives and anyone who needs help getting between venues.
• One for suppliers, who takes the calls from the florist and the band.

Put their numbers on the invitations and the order of service. Not the couple’s. This alone removes most of the day’s noise.

Write the day down, and give it to everyone

Every point person should have a printed timeline: what happens, when, where, and who is responsible. Printed because venues have poor signal, phones die, and hands are full.

Guests need less, but they need it clearly:

• Full addresses of both venues, on the invitation and again on a sign at the ceremony exit.
• What time to be seated, which should be earlier than you think.
• How to get between venues, and whether transport is provided.

Assume a meaningful fraction of guests have read nothing.

Plan the group photos properly

This is the reliable disaster. The photographer has a shot list; the shot list needs twelve named relatives; those relatives are spread across a garden, a bar, and a toilet queue. Twenty minutes evaporates per group shot.

What works:

• A written shot list with actual names, not “bride’s family”.
• One loud, organised person whose entire job during that window is rounding people up. Ideally someone who knows both families by sight.
• An announcement before people scatter, telling the named people to stay in one area.
• A fixed location for photos that everyone is told about in advance.

The gaps where people get lost

• Ceremony to reception. Guests wander, smoke, take photos, and drift to the wrong car park.
• Before the ceremony, when the wedding party is split across houses and hotels.
• Late evening, when people are moving between a venue, a hotel, and taxis.

These are the moments when someone is always on the phone trying to find someone else.

Where a shared map helps

Specifically for the wedding party and the point people, not for eighty guests.

The wedding party is genuinely spread out on the morning, often between two or three addresses, and the question “has the car left yet?” is asked constantly. Making that visible removes a lot of calls at a moment when everyone is already stressed.

It is also useful for the venue-to-venue gap, where a couple of guests inevitably need directing.

Where Nearby fits

We build Nearby, so read this as interested, and with a clear limit: it holds up to ten people, so it is for the wedding party and the point people, not the guest list.

For that group, the fit is decent. Drop a pin on the ceremony venue, share one link, and everyone from the bridesmaids to the best man to the driver is on one map - joining from a browser, with a name, no install and no account, which matters when half of them are getting ready and nobody is downloading an app.

Then a second meetup for the reception venue if the day moves.

Everything else - the printed timeline, the point people, the shot list - is the real system. This just removes the “where is everyone” calls.

The wedding checklist

1. Point people per group; their numbers on the invitations, not the couple’s.
2. Printed timeline for everyone with a job.
3. Both full addresses everywhere, plus a sign at the ceremony exit.
4. Named shot list and one person rounding people up.
5. A shared map for the wedding party, not for the guests.

---

Nearby is free on Google Play, and the wedding party joins from any browser.