Wedding Vendor Coordination Checklist for the Month Before

The month before a wedding is when loose threads get tied off or turn into problems on the day. Here's the mistake almost every couple makes: treating vendor confirmation as a formality already handled back when the contract got signed. A signed contract confirms a booking happened once, months ago, but it says nothing about whether the florist remembers bump-in is 7am, not 9am, or whether the venue ever told the band about the noise curfew.

At the scale most Australian weddings run now, dozens of guests, tens of thousands of dollars, a missed confirmation doesn't stay small. It becomes the thing people remember about the day, and not in a good way, which is why every vendor on the list needs to be treated as an open task.

Getting the financial close right before the day arrives

Most vendor contracts split payment into two or three chunks: a deposit way back when the booking was made, a balance due somewhere in the two-to-four-week window before the wedding, and a final catering adjustment once RSVPs lock. That middle payment is the one couples forget, mostly because it got agreed to months ago and buried in an inbox nobody's reopened since.

Go back through every contract this month. Check the balance due date and exact amount, the accepted payment method (bank transfer versus card, since some vendors add a surcharge for the latter), whether final guest count changes the price, and the cancellation terms, and read that last one twice before any final payment clears.

Venue and catering eat the largest share of a wedding budget, and the venue line alone can run into five figures. That means the balance payments on those two vendors can be substantial, due inside the same fortnight, arriving all at once instead of trickling in over a year. Most couples spend more than planned, and the final month is when that gap actually gets felt.

Build a tracker. Vendor name, contract total, deposit paid, balance owing, due date, confirmation received yes or no, one row per supplier, no exceptions. If a balance looks bigger than expected, call the vendor now, not the week of the wedding, since vendors would rather sort out a payment plan in week four than chase an unpaid invoice in week one.

Confirming each vendor's logistics, not just their attendance

That vendor has worked a dozen weddings since yours got booked. Most vendors expect the check-in, because they know exactly how easy it is for details to blur across bookings, and a quick call is how professional coordination actually works.

Venue. Confirm bump-in access times for the florist, cake vendor, AV crew, and photobooth. Walk through the floor plan (table positions, ceremony-to-reception flow, where the bridal table sits) and get a direct mobile number for the on-site coordinator.

Caterer. The single most sensitive handoff of the month: final guest count, per-table dietary breakdown, service timeline (entrée, mains, speeches, cake cutting). Clarify exactly where the venue's job ends and the caterer's begins, since that gap, the one nobody owns, is where service failures live.

Photographer and videographer. Share the full-day timeline: ceremony start, portrait window, reception entry. Confirm the shot list, family groupings, and where they'll stand during the ceremony, since some venues restrict flash or movement. Photography is a serious line item in most budgets, and it only pays off if the photographer has the schedule memorised.

Celebrant. Run through the ceremony script and check the legal paperwork: witness names, the signing table, documents the couple needs to bring. Confirm arrival time explicitly, since thirty minutes early is standard, but standard isn't the same as stated out loud.

Florist. Confirm delivery address, time window, and who at the venue signs for the flowers. Confirm the bridal party will actually be at the handoff location, and flag any last-minute changes to table count or centrepiece style.

Band or DJ. Confirm bump-in and sound check times, and check the venue's noise curfew directly, since the venue may know about it and never have mentioned it to the band. Share the running sheet: first dance, speech order, the do-not-play list. Confirm who's doing MC duties, since "the band's guy" and "the best man" are two very different plans.

Transport. Confirm pickup addresses, times, passenger counts per vehicle. Send a map pin, not just an address, since some venues have multiple gates that GPS doesn't sort out cleanly, and get the driver's mobile so it can be handed to the best man or another trusted contact.

Hair and makeup. Confirm start time and location, since this is often the very first appointment of the entire day for a large bridal party. Confirm the running order and make sure the bride's slot has enough buffer before the ceremony.

Every other vendor, cake, photobooth, wishing well, needs the same three answers: when to arrive, where to go, who to call on the day.

Building and distributing the day-of running sheet

The running sheet is the one document where every supplier, every action, and every contact number lives together, separate from the couple's own itinerary. Skip this step and the couple becomes the running sheet, fielding vendor texts mid-ceremony.

Build it chronologically, starting from the first vendor arrival (usually the florist or the venue bump-in crew) through to the last departure (usually the band's pack-down). Each entry needs a time, what happens, who's responsible, a direct mobile for that person on the day, and any dependency worth flagging: "flowers must be styled before the photographer arrives at 3:30pm," for instance.

Not every vendor needs the whole document. The venue coordinator, photographer, celebrant, and whoever's acting as day-of point of contact (often the best man or maid of honour) get full visibility, while everyone else just needs their own slice, not the full 40-line document with someone else's pickup times on it.

Build in slack, ten to fifteen minutes between major transitions: ceremony to canapés, canapés to reception entry. That buffer absorbs guests moving between spaces, warm weather, and venues where the ceremony site and reception room are a genuine walk apart.

Keep it live and shareable, not a PDF emailed once and forgotten. Any shift in the final week should reach every holder automatically, not sit undiscovered in an old inbox version on the day itself. Done properly, the running sheet lets the couple step back from being the coordinator: the nominated contact answers vendor questions off the sheet, and the couple gets to enjoy being, well, the couple.

Dietary requirements: locking the list and making sure it reaches the right people

Dietary requirements get collected at RSVP stage, but collecting them isn't the same as delivering them, and that gap is where most couples get this wrong: they assume the data moves itself. Unless the couple's tools connect RSVP data straight to the caterer, that information sits in an inbox doing nothing, no matter how carefully it was recorded back in month two.

Guest count typically locks in the weeks before the wedding. The dietary breakdown should go to the caterer at the exact same time, not as an afterthought the following week. What the caterer actually needs is a count by category, vegan, vegetarian, gluten-free, nut allergy, halal, and ideally a table-by-table breakdown, so waitstaff aren't reduced to asking guests to self-report mid-service.

Here's the failure mode that shows up again and again: dietary data lives in the RSVP system, the seating chart lives in a separate spreadsheet, and the caterer only ever gets a total headcount. Floor staff end up knowing there's one nut allergy somewhere in the room, but not which of the eighty-odd guests it belongs to, which is a couple problem wearing a caterer costume.

The fix is a seating plan that encodes dietary needs at the seat level, so staff serve correctly without interrogating anyone. This is the most tangled data handoff of the whole month, because it needs the RSVP list, the dietary responses, and the seating chart all pointing at the same version of the truth. When those three things live in three different tools, reconciling them by hand is slow, and slow is exactly where mistakes creep in.

Once the seating chart is final, send the caterer a per-table dietary summary alongside the totals, one line per table, then follow up separately with the venue's floor manager, since they're the one directing staff on the night and need the plan independent of whatever the caterer was told.

The vendor communications that couples forget until it's too late

Some of the most important messages of the month aren't to vendors about their own job, but introductions between vendors who've never met, and this is the piece almost everyone skips.

The florist needs to know when the photographer's arriving, so the flowers are styled before the first photos get taken. The band needs to hear about the venue's noise curfew directly, not assume the couple passed it along. The photobooth operator needs a confirmed power point, and that's a question for the venue, not the vendor.

For every supplier, get a direct mobile for the actual person showing up on-site, not the general business line and not the coordinator who handled the original booking enquiry. For any outdoor element, confirm the wet-weather plan and who has authority to activate it, and make sure the florist, photographer, and celebrant all know the backup location, not just the couple.

Parking trips people up more than it should. Confirm with the venue which vendors can park on-site and where, because a florist van circling the block at nine in the morning looking for a spot is a completely preventable disaster, and yet it happens at weddings every single weekend.

Tipping isn't expected in Australia, but if the couple wants to, prepare labelled cash envelopes in the final week and hand distribution to someone other than the couple. For every vendor conversation this month, phone or in person, send a short follow-up email recapping what got agreed. It takes two minutes, and it's the only record either side has if something goes sideways later.

Week-by-week breakdown of what to action in the final four weeks

Four weeks out. Audit every contract for balances and due dates, then send a re-confirmation message to each vendor, even a short one counts. Chase outstanding RSVPs, set a hard deadline for the guest list, and start the running sheet with whatever times are already confirmed.

Three weeks out. Lock the guest count and send it to the caterer and venue. Send the dietary breakdown, totals plus per-table detail if the seating chart's ready, and confirm the photographer's shot list and day timeline. Confirm the celebrant's script and legal paperwork, and pay any balance due in this window.

Two weeks out. Finalise the running sheet and send it to every key party, then confirm the florist's delivery window and on-site contact. Confirm transport times, addresses, and passenger lists, along with hair and makeup scheduling for the whole bridal party. Confirm band or DJ bump-in time, share the music brief, and get the venue coordinator's mobile for the day.

One week out. Check every vendor has replied and holds their section of the running sheet, then prepare tip envelopes if that's the plan, and confirm any last catering adjustments triggered by late RSVP changes.

That's the whole runway, and none of it is complicated on its own. It's just a lot of small confirmations that need to happen in the right order, to the right person, with a paper trail behind each one. Get through that list, and the only thing left to plan for on the day is the part that was always the point: standing up in front of everyone and getting married.