How to coordinate twelve vendors across three time zones without a planner

The first sign of trouble was a florist in Auckland texting a photographer in New York at 2 AM Auckland time. It wasn’t anyone’s fault. The florist thought she was answering a question about peonies. The photographer thought she was being asked to book a rehearsal dinner. By the time the confusion cleared, three hours of the florist’s sleep and a whole morning of the photographer’s had been sacrificed to a misread time zone.

This is the kind of thing that happens when a couple decides to plan a wedding themselves, across multiple regions, with no one to manage the flow of communication. It’s not impossible. It just requires a system that accounts for the fact that no two vendors are on the same schedule, and that the person who needs to confirm the cake delivery time might be asleep when the person who needs to approve it is wide awake.

The system that works best is built around a single, well-structured spreadsheet, used as a central command hub rather than a passive record. It doesn’t need to be fancy. It needs to be specific, shareable in a way that avoids version chaos, and designed to push information outward rather than just store it.

Build the master contact sheet before anything else.

The spreadsheet begins with a tab called “Vendors.” Not “Contacts.” Not “Planning.” Vendors. Every single person or company that will do anything on the day — the caterer, the photographer, the videographer, the florist, the DJ or band, the venue coordinator, the baker, the rental company, the transportation provider, the officiant, the hair and makeup team, and any assistants or second shooters. List them all, even the ones who seem like they won’t need coordinating. The baker’s assistant who drops off the cake might need to know where the back entrance is.

Each vendor gets a row. The columns should include: company name, primary contact name, email, phone (with country code), time zone, preferred method of contact, secondary contact name and number, contract start date, contract end date, total cost, deposit paid, balance due date, and payment status. Then add a column for “response time expectation” — whether they reply within an hour, within 24 hours, or only on weekdays. This alone prevents the frustration of sending an urgent message at 9 PM on a Friday and wondering why nobody answers until Monday.

The time zone column is the most critical. Write the UTC offset clearly: UTC+12 for New Zealand, UTC-5 for New York, UTC+1 for London. Do not rely on abbreviations like EST or NZDT, because daylight saving changes at different times in different hemispheres. A spreadsheet cell reading “UTC+12” stays true all year.

Create a shared schedule with local times visible for everyone.

The second tab is “Timeline.” This is the day-of schedule, broken into fifteen-minute increments from the start of setup to the end of teardown. Every event gets a row: “Bride arrives for hair,” “Florist delivers bouquets,” “Caterer sets up buffet,” “First dance begins.” For each event, list three columns: the local time at the venue, the UTC equivalent, and the local time in each vendor’s home zone.

This does two things. It gives every vendor a reference point they can check against their own watch. And it means that when the photographer in New York asks “what time do I need to be on the call at 8 AM,” the answer is right there in her local time without anyone doing the math for her. The spreadsheet does the math once, and it’s done.

The fifteen-minute increments may feel obsessive. They aren’t. A delay of thirty minutes at one step — a florist arriving late, a caterer needing extra setup time — can cascade into a photographer missing key moments, a DJ starting late, a cake melting in the sun. The timeline needs to be tight enough that a single delay is visible, and loose enough that a fifteen-minute shift doesn’t break anything. Fifteen-minute blocks hit that balance.

Set up a single source of truth for decisions.

The third tab is “Decisions.” This is where the couple logs every choice that affects multiple vendors: the exact shade of blue for the bridesmaids’ dresses, the final song list for the DJ, the dietary restrictions for the caterer, the number of tables and their arrangement, the timeline for speeches and toasts, the order of processional and recessional music, the parking arrangements for vendors who need to load equipment.

Each decision gets a row with columns for: the decision itself, the date it was made, who made it (if more than one person), which vendors it affects, and whether it has been communicated to those vendors. A checkbox column for “communicated” is essential. Without it, a decision can live in the spreadsheet for weeks without anyone noticing it hasn’t been shared.

This tab prevents the most common multi-vendor disaster: two different vendors receiving different instructions from two different family members. The spreadsheet becomes the reference point. If the florist says “the mother of the bride told me to use cream roses,” the couple can look at the Decisions tab and say “no, it’s white roses, confirmed on February 14th.” There is no argument. The spreadsheet wins.

Use conditional formatting to flag urgency.

The spreadsheet needs to do more than store data. It needs to signal what matters. Conditional formatting rules — green for confirmed, yellow for pending, red for urgent — applied to columns like “payment due date,” “response needed by,” and “deadline approaching” turn a static grid into a live dashboard.

A payment due in seven days turns yellow. A payment due tomorrow turns red. A vendor who hasn’t confirmed their arrival time within 48 hours of the wedding turns red. A timeline item that conflicts with another vendor’s schedule — the baker and the caterer both needing the same kitchen counter at the same time — turns red instantly. The couple doesn’t need to scan every row. The colors do the scanning.

This is where the spreadsheet becomes more useful than a planner. A human planner has to remember to check. The spreadsheet, with conditional formatting and a little bit of date math, never forgets.

Establish a communication protocol, not just a contact list.

The biggest source of friction in multi-vendor, multi-time-zone weddings is not the complexity of the tasks. It’s the chaos of who talks to whom, when, and through which channel. The spreadsheet should contain a “Communications” tab that defines this explicitly.

For each vendor, specify: who on the couple’s side is the primary contact for that vendor (one person, not two), whether that vendor should copy the other contact on emails, whether text messages are acceptable for urgent issues, and what qualifies as urgent (venue change, vendor cancellation, power outage — not “can I substitute blush for champagne on the napkins”).

Then define the chain of command for questions that affect multiple vendors. If the caterer needs to know the final headcount, does she call the venue coordinator, the couple, or the wedding party contact? If the photographer needs to adjust the timeline because of sunset timing, does he tell the DJ directly or go through the couple? The spreadsheet answers these questions before they come up.

One practical detail: share the spreadsheet as a link with view-only access for all vendors, and give edit access only to the couple and, if desired, a single trusted friend or family member serving as de facto logistics lead. No vendor should be able to delete a row or change a contact number. Version control matters.

Build in a buffer for cross-time-zone communication.

A vendor in Auckland sends an email at 3 PM local time. The couple, based in London, sees it at midnight. They reply at 8 AM London time, which is 7 PM Auckland time — just before the vendor’s day ends. The next day, the vendor reads the reply and answers at 10 AM Auckland time, which is 1 AM London time. The couple wakes up to the answer at 7 AM, and the cycle repeats.

This two-day lag per exchange is normal when working across three time zones. The spreadsheet accounts for it by adding a buffer column for every time-sensitive decision: “latest response needed by” set to 72 hours before the actual deadline. If the caterer needs a final headcount by April 1st, the spreadsheet sets the “latest response needed by” to March 29th. That gives three full days for the cross-time-zone ping-pong to resolve.

Include a “day of” cheat sheet.

The final tab is “Day Of,” formatted to print on a single piece of paper. It includes: the venue address, the start and end times for each vendor in the venue’s local time, the phone numbers of every vendor’s on-site contact, the location of the power outlets and loading docks, the parking situation, the nearest hospital, and a list of who to call first in an emergency (venue coordinator, then the caterer’s emergency contact, then the couple’s designated logistics person).

This sheet lives in a physical folder, printed three times — one for the couple, one for the venue coordinator, one for the designated logistics lead. It is not digital. If the Wi-Fi goes down, if a phone dies, if someone’s device gets left in a car, the information is still there.

Rehearse the timeline with every vendor, separately.

Two weeks before the wedding, schedule a fifteen-minute call with each vendor — at a time that works in their time zone, not the couple’s — and walk through the timeline tab together. Confirm each item. Ask if anything conflicts with their own notes. Ask if they’ve received all the information they need from other vendors. Ask if they have any special requirements (a specific power outlet, a place to store equipment, access to a sink, a clear path for rolling carts).

This call is where mistakes surface. The florist says “I thought the ceremony was at 3 PM, not 4 PM.” The photographer says “I need twenty minutes to set up, not fifteen.” The baker says “I need refrigeration space, and nobody told me.” Every one of these is a problem that can be fixed with two weeks’ notice. Every one of them is catastrophic on the day itself.

The calls also build goodwill. The vendor sees that the couple has done the work. The couple sees that the vendor has read the spreadsheet. Trust forms, and trust is the lubricant that makes multi-vendor coordination work.

Prepare for one thing to go wrong, and have a plan for it.

Something will go wrong. A vendor will be late. A delivery will be delayed. A power outlet will be occupied. A family member will change the seating chart without telling anyone. The spreadsheet cannot prevent every problem, but it can shorten the response time.

The “Day Of” cheat sheet should include a section labeled “Contingencies.” For each major vendor, list one likely failure mode and the solution: “If florist is delayed more than 30 minutes, move first look to 15 minutes later and adjust photographer’s timeline accordingly.” “If caterer’s van breaks down, the backup caterer (contact: name, number) has agreed to step in within 60 minutes.” “If venue loses power, the band has a battery-powered PA system and will switch to acoustic.”

These contingencies should be discussed with each vendor during the two-week calls, and noted in the spreadsheet. They are not meant to cover every possible disaster. They are meant to cover the most likely one, and to give everyone a clear, immediate action step rather than a panicked phone call.

Let the spreadsheet go on the day.

The day of the wedding, the spreadsheet is closed. The printed cheat sheet is in the physical folder. The designated logistics lead has the folder. The couple does not have a phone in their hands. They do not check email. They do not open the spreadsheet. The system has been tested. The vendors have been briefed. The contingencies have been planned. The spreadsheet has done its job: it made itself unnecessary.

It’s the kind of thing seasoned planners know to do. The couple who built the spreadsheet and ran the two-week calls can walk down the aisle without a notebook in sight, because the coordination work has already happened. The florist knows the time. The photographer knows the shot list. The caterer knows the dietary restrictions. The baker knows the back entrance. The spreadsheet is in a cloud somewhere, untouched, and everything is happening exactly as it was built to.

The one thing that matters most is the one thing the spreadsheet cannot control: whether the couple trusts the system enough to stop coordinating and start celebrating. The spreadsheet that works is the one that makes that trust feel earned, not borrowed.