Guest logistics · Bangalore, Goa & Kerala
Guest hospitality at an Indian wedding: RSVPs, transfers, rooming lists and the hospitality desk
Guest hospitality works when one register holds everything about every guest — RSVP, dietary needs, arrival and departure, room and transfer requirement — and one named person owns it. At a wedding we run, that is the hospitality lead, and the families feed the register rather than each keeping their own list. Everything else follows from it: the transfer manifest, the rooming list, the welcome hamper count, the itinerary cards and the desk in the lobby that answers the questions nobody anticipated.
This page sets out what the register holds, how transfers and rooming lists are built from it, what the desk does hour by hour, and what changes in Bangalore, Goa and Kerala. It quotes no property's policy, rate or check-in rule as fact; early check-in, block release dates and transfer inclusions must be confirmed in writing with the property.
Updated 20 September 2026
One register, one owner
The single most common failure in guest hospitality is not a missed pickup. It is three lists: the bride's family's spreadsheet, the groom's family's WhatsApp thread and the planner's version, none of which agree in the final week. Merge them into one register the day invitations go out, and keep it in one place everyone can see.
What the register holds, per guest or family unit
- Name, side of the family, relationship, and who in the family is responsible for chasing them.
- RSVP status per function, not just for the wedding — numbers differ between mehendi, sangeet, muhurtham and reception, and catering is ordered against them.
- Arrival and departure: date, time, flight or train number, and airport or station.
- Room requirement: nights, category, who shares, whether the family is paying or the guest is.
- Dietary needs and allergies, written as instructions a chef can use rather than as labels.
- Special needs: mobility, a ground-floor room, medication that must be refrigerated, a child who needs an early meal.
How families feed it matters as much as what it holds: one collector per side, one sheet to submit into, one weekly deadline. Our hospitality lead maintains the register and circulates a status summary — who has not replied, who has no room, who has no flight — so chasing is done by the family member closest to each guest.
Airport pickups when guests arrive on different flights
Guests will not arrive in a convenient wave. They arrive across a long day, from several airports, on flights that shift. Transfers are therefore a manifest problem, not a car-booking problem.
How the manifest is built
- Collect every flight number in the register, and re-confirm in the final week; airlines move timings and guests rebook without telling anyone.
- Group arrivals into slots rather than treating each as a separate run, then decide per slot whether it is a car, a tempo traveller or a coach. A coach is cheaper per head and slower for everyone; use it where a group truly lands together.
- Build a buffer into every arrival: domestic and international arrivals clear at very different speeds, and the car waits for the guest, not the other way round.
- Name the meet-and-greet point per airport and per terminal, and put it in the guest's message with a photograph if the airport is large.
- Give every driver a named passenger list, the guest's phone number, the property name and a hospitality desk number. Give every guest the driver's name, vehicle number and phone.
- Plan luggage honestly — wedding guests carry outfit trunks. A sedan that fits four people does not fit four people's luggage.
| Item | What to ask |
|---|---|
| Vehicle inventory | Exact vehicle types, seats and luggage capacity, and whether the same fleet covers all days |
| Waiting time | How long a driver waits free of charge on a delayed flight, and the charge after it |
| Charges | Whether pricing is per trip, per day or per kilometre, and how airport parking, tolls and night charges are billed |
| Redundancy | What happens if a vehicle breaks down mid-run, and how fast a replacement reaches the airport |
Rooming lists, early check-ins and guest-paid rooms
A rooming list is not a guest list with hotel names beside it. It is an allocation, category by category, night by night, that the property loads into its system and that the desk works from on arrival day.
The decisions a rooming list forces
- Categories: who gets which room type, and on what principle. Decide the principle before the names — elders and immediate family first, distance travelled second — because it is far easier to defend a principle than a choice.
- Host-paid versus guest-paid. State clearly, in the invitation, which nights the family covers and which the guest pays, and whether incidentals are on the room or settled by the guest.
- Sharing. Ask, do not assume. A shared room allocated without a conversation is the most reliable way to upset a relative.
- Early check-in and late check-out. Standard times rarely match wedding arrivals; ask the property what it can commit to for how many rooms, in writing, and where guests can change and freshen up if it cannot.
- The release date on any room block, which is when unbooked rooms return to the hotel and your guests lose the rate. Set your own guest booking deadline before it.
Send the property a final rooming list on an agreed date, in its own format, with names spelled as they appear on ID, arrival and departure dates, and the payment instruction against each room. Then send an updated version the day before arrivals. The desk's first hour on arrival day depends entirely on whether that document is right.
What the hospitality desk actually does
The desk is a staffed table in the lobby or arrival area with a printed guest list, the rooming list, the run sheet, itinerary cards, spare hampers, a phone that is always answered and someone who knows where everything is. It exists so that two hundred small questions do not reach the couple or their parents.
| Phase | What the desk is doing |
|---|---|
| Arrival day | Meeting cars, handling check-in with the front office, handing over keys, itinerary cards and hampers, fixing room problems quietly, briefing guests on the next function's timing, dress and travel |
| Function days | Answering questions, managing shuttle departures to each venue, holding spare outfits, chargers, umbrellas, safety pins and medicines, tracking who has not come down, and relaying to the run sheet team |
| Departure day | Bill settlement guidance, luggage, check-out timings, departure transfers against flight times, and lost property |
Staffing follows the guest count, the number of properties in use and the shape of the arrival day rather than a formula. The logic we use: the desk is covered continuously from the first arrival to the last departure, with more people in the arrival window and the hour before each function departure than in the quiet middle of a day; anyone on the desk in the morning is not also running the evening function; and there is always one person whose only job is the phone. A desk split across two properties is two desks, not one desk walking between them.
Elderly guests and guests with limited mobility
Plan this into the layout at design stage, not into the kindness of your cousins on the day. Ask on the RSVP form rather than waiting to be told; most families will not volunteer it.
What actually helps
- Ground-floor rooms, or rooms near a working lift, allocated first and confirmed with the property rather than requested on arrival.
- A route with no steps from the car to the seat, checked by walking it. Beach sand, lawn edges, temporary flooring joins and cable ramps are where wheelchairs and walking sticks fail.
- Seating near the aisle and the exit, with shade or cover, in chairs with arms and backs rather than benches.
- Meal timing. Late Indian dinners are hard on people with medication schedules and on children; arrange an earlier meal option and tell the family it exists.
- Heat and standing. Ceremonies at midday in an open space are the single most common cause of trouble; provide water, shade, fans or coolers and somewhere to sit within sight of the ritual.
- A named medical contact: nearest hospital, a doctor on call if the property has one, and an ambulance number on the run sheet.
- One desk person assigned to the elders' group for each function — collecting them, seating them, and making sure someone knows when they have gone back to their room.
Welcome hampers, room drops and itineraries
This is production work with a delivery window, and it is entirely delegable — families are rarely surprised by the cost, but often surprised by the labour.
How a room drop is run
- Fix the hamper contents and count early, with a margin above the rooming list for late additions and damaged items. Perishables and anything that melts need a different plan from dry goods.
- Produce the itinerary card per family, not per guest: function names, timings, venue, dress note, transfer time and a desk number. Print more than you need.
- Agree the drop with housekeeping: which rooms, when, before or after arrival, and who carries them. Pre-arrival placement looks best and needs the rooming list to be correct.
- Hold back a labelled set at the desk for guests whose rooms changed, guests who arrive late, and the ones who will say they never received it.
- Run one WhatsApp group per function group or family cluster, administered by the desk, not by the couple. Announcements go out from the desk; questions come back to the desk.
Our team handles hamper production and room drops as part of hospitality scope when it is agreed in the proposal, alongside the desk and the transfer manifest. On arrival day the family should be receiving people, not counting boxes.
Bangalore: local guests, traffic and multi-venue movement
In Bangalore most of your guests sleep at home, which sounds simpler and is not. Instead of one property to manage, you have a city to move people across.
What the desk does differently here
- Plan around traffic, not distance. A guest coming from Jayanagar to a Whitefield hotel for a morning muhurtham is leaving in the dark; say so in the itinerary rather than letting them discover it.
- Run shuttles from two or three collection points for local guests rather than one, and publish the departure times as departures, not as suggestions.
- Parking and drop-off are the arrival experience at a city hotel or a kalyana mantapa: valet capacity, where cars wait, and how the drop-off lane clears when two hundred cars arrive within half an hour.
- Venues beyond the airport and the Nandi Hills belt need a full transport plan and often overnight rooms for the elders, because the return journey after an evening function is long.
- Outstation relatives flying in usually land at Kempegowda International (BLR) at Devanahalli, north of the city; a venue near the airport can cut an hour of travel off their arrival, while a south or east Bangalore venue adds one.
Goa: two airports, long transfers and the room block
Goa is the destination where hospitality and commercial terms are the same conversation, because the room block is usually the reason you have the venue at all. We have produced 80+ weddings there, and the desk work is shaped by geography.
What the desk must get right in Goa
- Ask every guest which airport they are landing at. Dabolim (GOI) sits south-central near Vasco; Manohar International at Mopa (GOX) is in far North Goa. A guest landing at the wrong one for your venue faces well over an hour on the road, more on a peak-season evening.
- Publish the transfer time honestly in the invitation and the itinerary card. Guests plan their own flights around what you tell them.
- Work the room block: one booking route, a guest deadline before the property's release date, and a running pick-up report so you know who has actually booked rather than who has promised to.
- Beach and coastal sites need a mobility plan of their own: sand is impassable for wheelchairs, so plan firm pathways, and keep seating and shade for elders off the open sand.
Kerala: several airports, boat access and sadya sittings
Kerala spreads guests further than either of the others, because the airports are spread and the venues are not all in one kind of place.
Kerala hospitality specifics
- Collect the airport, not just the flight. Cochin International (COK) at Nedumbassery is about 30 km from Kochi city, Trivandrum (TRV) about 15 km from Kovalam, with Kozhikode (CCJ) and Kannur (CNN) serving the north; Bekal and Kasaragod are usually reached from Mangaluru (IXE) or Kannur.
- Some backwater resorts are reached by boat or a narrow approach road. That means last-boat times, jetty meeting points, luggage handled twice and a genuine access problem for elderly guests — check it before allocating rooms, not after.
- Sadya is served in sittings on banana leaf. Confirm with the caterer how many sittings your guest count needs, then sequence guests through them from the desk, taking elders and families with small children first.
- If the wedding runs across a church or temple and then a reception property, the desk is managing movement between them: timings set by the institution, parking at both, and a guest group who may not know the area.
- Humidity and rain: keep umbrellas at the desk, plan covered waiting at drop-off, and tell guests what the weather is likely to do rather than leaving them to pack blind.
Kerala sits under both monsoons — the south-west roughly June to September, with normal onset over Kerala on 1 June, and the north-east from October to December (IMD). Guest comfort planning in those windows means covered walkways and a wet-weather arrival plan, not just a backup venue.
What the desk needs from the family
Ten things to hand over, and when
- One named contact per side of the family, with authority to answer questions about their own guests.
- The guest list in one file, with duplicates resolved, as soon as invitations are decided.
- RSVP status per function, updated weekly, not a single number for the wedding.
- Flight and train details as they are booked, with the airport named.
- Room requirements per family unit, including who shares and who is paying.
- Dietary needs and allergies in usable language, plus anyone needing an early meal.
- Mobility and medical needs, asked for on the form rather than waited for.
- The invitation and itinerary wording, so the desk's messages match what guests were told.
- Sign-off on hamper contents and counts in time for production and delivery.
- A decision on who is not to be disturbed on function days — usually the couple and both sets of parents — so the desk can hold the line for you.
Give the desk those ten and the rest is ours to run. Panigrahana's planning fee is quoted for the agreed scope; venue, hospitality and vendor costs are separate, and hospitality staffing, transfers and hampers are scoped in the written proposal rather than assumed.
Questions couples ask
Who should collect RSVPs, dietary needs and arrival details for our destination wedding?
One person should own one register, and at a wedding we run that is the hospitality lead. The families feed it rather than each keeping a separate list: one named contact per side, one format to submit into, and a weekly deadline. The register holds RSVP status per function, arrival and departure with flight numbers, room requirement and who pays, transfer requirement, dietary needs and allergies, mobility or medical needs, and a phone number that works in India. Chasing is then done by the relative closest to each guest, which is faster than a planner calling a stranger.
How should we plan airport pickups when wedding guests arrive on different flights?
Treat it as a manifest, not a car booking. Collect every flight number in the register and re-confirm in the final week, group arrivals into slots and decide per slot whether it is a car, a tempo traveller or a coach, and build a buffer into each arrival because domestic and international halls clear at different speeds. Name the meet-and-greet point per terminal, give drivers a passenger list and guests the driver's details, and plan luggage honestly since wedding guests carry outfit trunks. Assign one desk person per arrival window to close every handover.
How can we manage rooming lists, early check-ins and guest-paid rooms?
Decide the allocation principle before the names — elders and immediate family first, distance travelled second — because a principle is easier to defend than a choice. State in the invitation which nights the family covers and which the guest pays, and whether incidentals go on the room. Ask before allocating shared rooms. Ask the property in writing what early check-in and late check-out it can commit to and for how many rooms, and where guests can freshen up if it cannot. Send a final rooming list on an agreed date, then an updated one the day before arrivals.
What should a wedding hospitality desk handle, and how many shifts do we need?
The desk meets cars, handles check-in with the front office, hands over keys, itinerary cards and hampers, fixes room problems, manages shuttle departures, holds the spares everyone needs, and answers the phone so questions never reach the couple or their parents. On departure day it runs bills, luggage and flight-timed transfers. Cover it continuously from the first arrival to the last departure, with more people in the arrival window and before each function departure, one person whose only job is the phone, and nobody on the morning desk also running the evening function.
How do we plan a wedding that is comfortable for elderly guests and people with limited mobility?
Ask on the RSVP form rather than waiting to be told. Allocate ground-floor rooms or rooms near a working lift first and confirm them with the property. Walk the route from car to seat and remove every step, cable ramp and stretch of sand. Seat elders near the aisle and the exit, in chairs with arms and backs, under shade. Offer an earlier meal option for people on medication schedules and for children, plan for heat at midday ceremonies, put a named medical contact and hospital on the run sheet, and assign one desk person to the elders' group for each function.
Can our planner coordinate welcome hampers, room deliveries and guest itineraries without us handling everything ourselves?
Yes, and it is normal scope when it is agreed in the proposal. Contents and counts are fixed early with a margin above the rooming list, assembly happens in a space arranged at the property, itinerary cards are produced per family with timings, dress notes, transfer times and a desk number, and the drop is agreed with housekeeping for pre-arrival placement. A labelled reserve stays at the desk for changed rooms and late arrivals. The desk also administers the guest WhatsApp groups, so announcements go out and questions come back without passing through the couple.
How many hospitality staff does a 250-guest destination wedding need?
There is no formula worth printing, because it depends on how many properties are in use, how spread the arrivals are and how many functions run in parallel. The logic to apply: cover the desk continuously from first arrival to last departure; weight staffing towards the arrival window and the hour before each function departure; keep one person on the phone at all times; do not ask the morning desk team to run the evening function; and treat a second property as a second desk rather than one desk walking between them. Scope it in the proposal against your actual arrival pattern.
Sources
The sources above are the pages this guide relies on; where a source publishes no figure, this page prints none. Check-in and check-out times, early check-in availability, block release dates, transfer inclusions and accessibility at each venue must be confirmed in writing with the property.
Guest hospitality
Tell us how many guests are travelling.
Send the dates, the rough guest number and how many are flying in. We will come back with how we would run the register, the transfer manifest and the desk for a wedding of that size, and what the property needs to confirm in writing.