Why transport turns a simple RSVP into a logistics problem
Adding a shuttle to your wedding is a genuine kindness. It keeps guests safe, solves the parking puzzle at a remote venue, and means nobody has to choose between the open bar and driving home. But the moment you offer transport, your RSVP stops being a simple yes or no. Now you need to know who is riding, from where, in which direction, and at what time, and you need that information locked down early enough to book the right number of seats. Vague wording here creates a headcount you cannot trust, and a shuttle that leaves half empty or badly oversold.
The fix is to treat transport as its own question on the reply, separate from attendance. If you are building your invitation now, you can design one on InviteDrop and add a distinct shuttle question so a guest saying "yes, I am coming" and "yes, I need a seat" are recorded as two different answers rather than one muddy one.
What you actually need to collect
Before you write a word, decide what the shuttle answer must tell you. At minimum you need whether each guest wants a seat, and for how many people in their party. If you are running pickups from more than one location, such as a couple of hotels, you need to know which pickup point each rider will use. If the shuttle runs both directions, confirm whether they need the return trip too, because plenty of guests catch a ride there and leave with someone else.
The mistake couples make is asking "will you need transportation?" as a single yes or no. That tells you a rider exists but not how many seats, from where, or in which direction, so you end up emailing people individually to fill the gaps. Ask for the specifics up front and the follow-up disappears.
Wording for a single-pickup shuttle
When there is one pickup point, keep it clean and factual. Something like: "A complimentary shuttle will run from [Hotel Name] to the venue and back. Please let us know if you would like seats, and for how many in your party, so we can reserve enough space." Then give the reply a small number field for party size rather than a plain checkbox.
Include the practical detail guests will ask about anyway: the approximate departure time and where exactly to gather. "The shuttle departs the hotel lobby at [time] and returns after the reception ends" answers the two questions every rider has and stops a flood of texts on the day.
Wording for multiple pickup points
With more than one pickup location, the reply needs to route each guest to the right one. Try: "We are offering shuttles from two hotels. If you would like a seat, please tell us which pickup point works for you: [Hotel A] or [Hotel B]." A digital RSVP makes this painless because you can offer the pickup options as selectable choices, so guests cannot accidentally leave it blank or invent a third location you are not serving.
Be explicit that seats are tied to a specific pickup, not a general pool, because a guest who picks the wrong hotel will be standing on the wrong curb. A short confirming line, "your seat is reserved from [Hotel A]," removes that ambiguity.
Handling the return trip separately
Return transport is where counts fall apart, because attendance to the venue does not predict who needs a ride home. Some guests will book a car, some will leave early, and some will stay to the very end. Ask the return question on its own: "Will you also need a return shuttle to the hotel after the reception?" Treat the yes count as your real return number, and pad it only if you know your crowd tends to stay late.
If your reception has a firm end time and a single return run, say so plainly, because a guest who assumes shuttles loop all night will be stranded. "The final return shuttle leaves 30 minutes after the last dance" sets the expectation cleanly.
For weddings with accessibility needs
If any guest uses a wheelchair, walker, or has mobility needs, your shuttle wording should invite them to tell you privately so you can arrange an accessible vehicle or an alternative. A simple line works: "If you have any accessibility needs for transport, please note them here and we will make sure you are looked after." Collecting this on the RSVP rather than discovering it on the day is the difference between a guest feeling cared for and a guest feeling stuck.
It also helps to give riders a single point of contact for the day itself. A short line such as "questions about the shuttle? Text [name] at [number]" means a guest who is running late or standing at the wrong door can sort it out in seconds, rather than calling the couple minutes before the ceremony. Put that same contact on any signage at the pickup point so nobody is left guessing which vehicle is yours.
Keeping the transport count reliable
The whole point of good wording is a number you can hand to your transport provider with confidence. That means keeping the shuttle answers in the same place as the rest of your RSVPs, not scattered across texts and a side spreadsheet. When your reply flow records attendance, party size, pickup point, and return need together, you can read off exactly how many seats each run requires and when.
On InviteDrop, transport answers land in the same live RSVP dashboard as everything else, so your seat count updates the moment a guest replies, and you can filter for riders by pickup point without rebuilding a list by hand. That is far steadier than trying to reconcile paper cards, group chats, and half-remembered conversations the week before the wedding.
A short template you can adapt
Here is a compact version that covers the common case: "We are so glad you are celebrating with us. A complimentary shuttle runs from [Hotel] to the venue and back. Will you need seats? If so, how many, and will you also want the return trip after the reception? The shuttle departs at [time] from the lobby." Adapt the pickup and timing details to your setup, and split the questions so each one is answered on its own.
Nail the transport wording and the rest of the day gets quietly easier, because nobody is left guessing where to stand or whether there is room. When you are ready to build it, you can design one on InviteDrop, add a clear shuttle question to your reply, and let the live dashboard turn a fuzzy transport estimate into a real seat count you can actually book against.
