Wedding Weather Backup Plan: How to Tell 80 Guests
A wedding weather backup plan your guests will actually see. The exact texts to send when the venue moves indoors, plus timing across time zones.
# Wedding Weather Backup Plan: How to Tell 80 Guests
It is 9 a.m. on your wedding day in Tuscany. The forecast you have been refusing to look at all week is now real: rain by 4 p.m., right when the outdoor ceremony was supposed to start. You and the venue make the call to move everything under the loggia. Good. The plan worked. Now there is one thing standing between you and a smooth day: 80 people, scattered across three hotels and two time zones, who all still think they are walking to a garden at the bottom of the property.
The hard part of a wedding weather backup plan is almost never the plan itself. Venues have a rain plan. Your planner has a rain plan. The hard part is telling everyone, fast, in a way they will actually see before they walk out the door in the wrong shoes toward the wrong place. This post gives you the exact texts to send, the right moment to send them, and how to make the message land when your guests are spread across hotels and time zones.
How do I tell my guests the wedding venue just moved?
Send one short text to everyone at once, the moment the decision is final. State what changed, where to go now, and what time, in that order. Do not explain the weather, do not apologize, do not send a paragraph. Guests need an instruction, not a story. A two-line text read in ten seconds beats a beautiful email no one opens.
The reason texting wins here is simple. Studies commonly cite around a 98% open rate for SMS, with most messages read within minutes, compared to roughly 20% for email. On a normal day that gap is a convenience. On a day when the venue location changed four hours before the ceremony, that gap is the entire difference between guests arriving in the right place and guests standing in the rain texting your maid of honor.
Here is the message I would send first, the moment the call is made:
Quick update: with the rain, the ceremony is now indoors at the villa loggia (same property, top of the drive). Same time, 4:30 p.m. Shuttle still leaves the hotel lobby at 3:45. See you soon.
That is it. Specific place, same or new time, and the one logistical detail that changes (where the shuttle goes, where to gather). For the deeper logic on what makes a same-day message land, I wrote a full piece on wedding day guest communication that pairs well with this one.
What exactly should the venue-change text say?
Lead with the change, not the cause. A good venue-change text answers four questions in under 40 words: what moved, where to go now, what time, and what to do differently. Guests skim. If the new location is in the first line, they will get it even if they read nothing else. Save the weather explanation for the welcome dinner toast.
Use this four-part structure for any plan-B message:
- The change, in five words. "Ceremony is now indoors." Not "Due to the forecast we have made the difficult decision to..."
- The new location, named plainly. "At the villa loggia, top of the drive." Use the name guests will see on a sign or hear from a driver, not the name on the floor plan.
- The time, stated even if it did not change. "Same time, 4:30 p.m." People assume a location change means a time change. Kill that assumption.
- The one thing they do differently. "Shuttle now drops at the main entrance." One action. If there are three, you have a deeper problem than a text can fix.
If you want more sample wording for the whole timeline, not just the emergency, my wedding text message templates post has copy you can adapt, and the wedding itinerary text wording guide covers how to phrase the routine schedule so the emergency text stands out when it comes.
When do I send the backup-plan message?
Send it the instant the decision is final, and never on a "maybe." A premature "it might move indoors" text creates 80 follow-up questions you do not have time to answer on your wedding morning. Wait for the real call, then send within minutes. The morning-of message is the highest-attention moment of the entire event, so a single clear text at the right time does the work of a dozen scattered ones.
There is a timing trap worth naming. A vague heads-up the night before ("keep an eye on the weather, we will confirm in the morning") feels considerate but backfires. Guests start planning around an instruction that does not exist yet. By morning, half of them have invented their own version of the plan. One firm message at the moment of decision beats two soft ones. If you want the broader logic of when each kind of wedding text should land, when to send wedding text messages breaks down the timing for the whole arc, and wedding day timeline communication covers how the day-of cadence should feel.
Why a group chat or wedding website will not save you here
A phone group chat and a wedding website both fail at the exact moment you need them most. Group chats cap around 20 to 25 people, then trigger reply-all chaos and expose everyone's number. A website gets visited once or twice, then the URL is forgotten. Neither one reaches a guest who is already in the shuttle line. For an 80-person destination wedding, you need a channel that lands in the pocket without anyone opening anything.
I am not against websites. For a small local wedding where everyone already knows the venue, a website plus a group text is genuinely fine, and I say so plainly in my guide to wedding guest communication without an app. But "plan B" is the scenario that breaks both tools. A group chat of 80 is not a tool, it is a hostage situation. And the guest most likely to miss a venue change is the one who bookmarked your site in March and has not looked since.
Here is the honest comparison for a same-day change at scale:
| Channel | Reaches everyone at once | Read within minutes | Survives 80 people | Works while guest is in transit |
|---|---|---|---|---|
| Group text (SMS group) | Only up to ~20-25 | Yes | No, breaks down | Yes |
| Email blast | Yes | Rarely, ~20% open | Yes | No, needs inbox check |
| Wedding website update | No, they must visit | No | Yes | No |
| Individual personalized texts | Yes | Yes, ~98% open | Yes | Yes |
The bottom row is what you actually want: one message, sent individually to each guest so there is no reply-all, landing on the phone they are already holding.
How do I handle a venue change across time zones and a foreign country?
State the local time and the local landmark, and assume nothing carries over from home. At a destination wedding the cost of a missed message is not a late arrival. It is a guest stranded in a foreign country, on the wrong shuttle, in the wrong time zone, with no easy way to ask. So your plan-B text has to be readable by someone who landed two days ago and is still doing currency math in their head.
Three rules make a destination venue-change message safe:
- Use local time only, and say "local." "4:30 p.m. local time" removes the jet-lagged guest's silent question. This is the same discipline I cover in destination wedding guest coordination.
- Anchor to a landmark, not a map pin. "The covered terrace by the main entrance" beats GPS coordinates a foreign data plan may not load. Reference the same landmarks you used in your destination wedding welcome text so the language is already familiar.
- Repeat the shuttle detail every time. Transport is where destination plans actually fall apart. If the rain changes the pickup point, that detail belongs in its own line. My destination wedding travel reminder texts post has more on getting people physically to the right place.
This is also why destination RSVP deadlines run earlier, often 8 to 10 weeks out, because guests are booking flights and your final headcount drives catering minimums and shuttle vehicle size. By the time the weather turns, your list is locked and every name on it is a person who flew across the world to be there. A backup plan that does not reach all of them is not really a backup plan.
What can Dearest Guest do that a regular blast cannot
This is the part where a good wedding texting service stops being a convenience and starts being insurance. With Dearest Guest, your messages reach guests anywhere in the world, sent individually so there is no group-chat chaos and no exposed numbers. You write the whole timeline once and schedule it, and every message lands at the right local time even when your guests are spread across three time zones. When the venue moves, you edit or add a message in seconds, because messages are unlimited with no per-message fee and you can change, add, or cancel right up until one sends.
The part I care about most is delivery. I have had couples come to me after trying another wedding-texting app where the messages quietly did not arrive. At a destination wedding, a text that silently fails is not a small bug. It is a guest standing in the rain in a country they have visited once. So every message on Dearest Guest is human-reviewed. I personally read them before they go out, and I watch delivery actively so nothing fails in silence. Replies from guests get forwarded to you, so if someone is confused, you hear about it.
We guarantee your messages get delivered. Ilayda reviews every one, and support is one message away. That is a promise I can make because I am the one reading them. If you want to see the mechanics, how it works walks through the setup, pricing is one flat number with no per-message fees, and the destination weddings page is built for exactly the rainy-Tuscany scenario this post opened with.
Your plan-B checklist, before the wedding week
You do not want to be writing your first venue-change text at 9 a.m. on the day. Draft it now, while you are calm, and schedule the rest of the timeline so the emergency message is the only thing you ever have to send live. Roughly 5 to 7 messages across the whole experience keeps guests informed without nagging them, which means the one urgent text stands out instead of getting lost in noise.
- Pre-write the venue-change text now. Fill in both versions: rain plan and clear-skies plan. On the day you only choose, you do not compose.
- Confirm the landmark names with your venue. Whatever the drivers and signs say, that is the language your text uses.
- Schedule the routine messages in advance. The morning-of, the shuttle reminder, the ceremony nudge. See wedding day timeline communication for the cadence.
- Make sure you can reach everyone individually, not via a chat. Test that your channel sends one-to-one. This is the whole reason group chats fail at 80.
- Decide who pulls the trigger. You, your planner, or your coordinator. One person, one phone, one message.
If you are building the rest of your communication plan, the venue guides for Italy, Mexico, and Tahiti cover region-specific logistics, and after the day, collecting wedding photos from guests turns the same channel into the way you gather everyone's pictures of the loggia you ended up loving more than the garden.
Frequently Asked Questions
How far in advance should I prepare a wedding weather backup plan for guests?
Confirm the venue's rain plan when you book, and write the actual guest-facing texts during your wedding week, not on the day. Pre-writing both versions, indoor and outdoor, means that on the morning of, you only have to choose and send. The decision can be made in minutes when the message is already drafted and waiting.
Should I text or email guests when the wedding venue changes?
Text. SMS is commonly cited at around a 98% open rate with most messages read within minutes, versus roughly 20% for email. On a day when the location changed hours before the ceremony, you need guests to see the update while they are getting dressed or boarding a shuttle, not whenever they next check an inbox. Email is too slow for a same-day change.
Can I use a group chat to tell all my wedding guests about a venue change?
Not reliably at scale. Phone group chats cap around 20 to 25 people, trigger reply-all chaos, and expose everyone's number. For an 80-person wedding you want individual messages sent to each guest at once, so there is no chaos and no privacy problem. A group chat works for a small local wedding, not a destination headcount.
What if a destination guest is in a different time zone when I send the update?
Always write the local time and label it "local," and anchor directions to a named landmark rather than a map pin a foreign data plan may not load. The risk at a destination wedding is not a late guest, it is a guest stranded in the wrong place in a foreign country, so the message has to be readable by someone still adjusting to the time difference.
How does Dearest Guest make sure my venue-change message actually gets delivered?
Every message is human-reviewed before it sends, I read them personally, and delivery is monitored actively so nothing fails in silence. Messages reach guests anywhere in the world, sent individually rather than as a group blast, and you can edit or add one right up until it sends. We guarantee your messages get delivered, and support is one message away.
How many messages should I send my guests overall?
Roughly 5 to 7 across the whole experience keeps guests informed without feeling nagged: a welcome, travel and shuttle details, a morning-of note, the ceremony nudge, and a thank-you. Keeping the routine count low is what makes an urgent venue-change text stand out instead of blending into a stream of reminders.
The hard part is the communication. We do that part.
Dearest Guest automates the entire SMS layer of your wedding, from save-the-date through day-after thank-you. Setup is under 5 minutes.

I built Dearest Guest after my own wedding. If you have questions, I answer them personally. Ilayda
One-time $3 per guest, $99 minimum. No subscription.

Ilayda B.
Founder, Dearest Guest
Ilayda built Dearest Guest after her own wedding chaos taught her that love isn't enough. Guests need clear communication too. Read more →
