Multi-Event Bangladeshi Wedding Guest Lists: Managing Different Attendees Per Ceremony
If you’ve already had the conversation where your khala says “but of course the whole family is coming to everything”, you know the guest list is where Bangladeshi wedding planning gets real. With a holud, a nikah, a reception and maybe a bou bhat, you’re not managing one guest list. You’re managing several that overlap, and every one of them decides a venue size, a catering bill and a seating plan. This guide shows you how to build them, keep them straight and stop them growing out of control.
The short answer
Keep one master list of names and add a column for each event. Tick who’s invited to what, collect a separate reply for each event, and count the people eating at each meal on its own. Decide early who holds each list and who can add to it, and agree a cut-off date with both families. Then give the venue and caterer one number per event, on their deadline.
Why it’s several lists, not one
A Bangladeshi wedding can be a run of gatherings: Banglapedia’s list of wedding customs runs from the days before the wedding, through the wedding itself, to the days after. Each has its own crowd. The holud may be close family and friends. The nikah may be smaller still: one service in east London, for example, says the maximum number of guests at its venue is seven. The big reception can be the largest gathering of all. One east London venue describes the bou bhat as potentially the biggest gathering of the whole wedding, and a London photographer describes his neighbour’s Bangladeshi walima with around 800 guests.
Hosting splits too. A Birmingham fatwa notes that in some Asian cultures the bride’s family provides a meal on the wedding day and the husband hosts the walima afterwards. When different sides host different events, each host may want a say in its list.
Your planning flow: first, second, next
- Write the event list. Every gathering, its host, date and rough size.
- Build one master list. One row per person: name, household, contact, which side, and any dietary needs.
- Add a column per event. Tick who’s invited to what. Wedvisa’s guest list manager keeps names, RSVPs and dietary notes in one place.
- Name the list-holder for each event. One person decides additions for that event, and everyone knows who it is.
- Set the cut-off. A date by which each side sends actual names, not “the cousins”.
- Send invitations with a reply for each event. So you know who’s coming to what.
- Give numbers per event to each venue and caterer, on their deadline, then build the seating plan.
A rough timeline
Use these as working dates and line them up with each caterer’s deadline.
- 12 to 18 months out: rough numbers per event, so you can book venues of the right size.
- 6 to 9 months out: both sides send names by an agreed date; the master list is built.
- 3 months out: invitations go out with a reply for each event.
- 6 weeks out: chase missing replies; check dietary needs.
- Two to four weeks out: final numbers to each caterer by their deadline.
- The week of: seating plans printed; a list for the door at each event.

How to build the lists
The master list
Start with households, not individuals, because invitations go to households. For each person, record which side they’re from, which events they’re invited to, whether they’ve replied for each one, and any dietary needs or access needs. Children need their own line too, since caterers count them differently.
Getting names from both families
Ask each side for actual names by a date. “The cousins” is not a headcount, and “everyone from the mosque” isn’t either. If a parent has a long list, ask them to mark the must-invites and the would-be-nices. That makes cuts easier later, and nobody has to be the villain.
When the lists don’t match
Disagreements happen. If one side’s list is much bigger, agree whether each side has its own allowance per event, or whether the host of each event decides. If someone is invited to the reception but not the holud, decide how the invitation will make that clear so nobody turns up to the wrong door.
The tricky cases
A few situations are worth deciding early rather than one phone call at a time.
- Plus-ones. Decide a rule per event, such as partners of married or engaged guests only, and apply it to both sides.
- Children. Are children invited to every event, some events or none? Say so on the invitation, and count them separately for the caterer.
- Relatives from abroad. Find out early who’s travelling and when, because their dates may decide whether they can come to the holud as well as the reception.
- Elders who need help. If a grandparent needs a carer or a family member alongside them, count that person too.
- Community and colleagues. If parents want to invite people from the mosque, the community centre or work, agree which event they’re invited to. Ask the host which event they want those guests at, and record it in that column.
- The “just this event” guests. If someone is invited to one event only, make sure their invitation shows only that event.
Using the tools together
Build the master list first, then use each event’s column to produce that caterer’s number and that invitation’s replies. Move only confirmed guests into the seating plan. In Wedvisa’s guest list manager, keep each event’s replies and dietary notes alongside the names. When replies come in, the number for each event is the number for that event’s caterer. Once numbers settle, move each event’s confirmed guests into the seating plan, event by event. Keep the latest version in one place, so the bride’s side and the groom’s side aren’t working from different spreadsheets.
Invitations and replies
With several events, the invitation has to do more work. One UK stationery company describes one main invitation with separate insert cards for each event, so different guests can receive different inserts.6 That way, the reception guests get the reception card, the close family get the holud card as well, and nobody gets an invitation to an event they’re not on the list for.
Whatever the format, collect a reply for each event. One UK digital invitation service, for example, describes collecting a yes or no for each event, with headcounts and dietary notes. A guest who accepts the reception and declines the holud is two answers, not one.
Each invitation or insert should say what the event is, where, what time food will be served, and who to reply to by when. “Dinner with the groom’s family to welcome our new bou” tells an elderly relative far more than a single word.
Numbers for the caterer and venue
Final numbers and deadlines
Every caterer has its own deadline, so ask when you book. Table Food, a caterer in Northern Ireland, says final numbers must be confirmed two weeks before the event and that it can accommodate increases up to three days before.8 Find out what yours does about late changes, especially decreases, before you sign.
Children and supplier meals
Count children and supplier meals separately, because they change the bill. Kwaku’s Kitchen, a London caterer, lists vendor meals at £20 per person. Your photographer, videographer, DJ and decorator may all be on site through a meal, so ask each one whether they expect to be fed.
Capacity and dietary needs
Check every list against the room. White Abbey Ballroom in Bradford, for example, lists space for up to 500 guests and 140 parking spaces; ask any venue for the seated capacity once the stage, buffet and dance floor are in. Pass dietary needs to the caterer as a list, not a headcount. If they’re serving a buffet in England, Wales or Northern Ireland, they must give allergen information for each dish, not for the buffet as a whole.
Family decisions, extra guests and money
The guest list is where money and feelings meet. Agree who pays for each event, because whoever pays will want a say on its numbers. When someone wants to add guests after the numbers have gone in, it’s worth knowing that every extra guest changes more than the food: chairs, tables, parking, transport, favours and photographs too.
A few rules that help:
- One list-holder per event. Additions go through them.
- A cut-off date. After it, additions are only by agreement.
- A short waiting list. If people decline, the next names are ready.
- A buffer. Ask the caterer whether late additions are possible and whether unused places are charged before you hold any spare places.
If the total is too high, look at the events before the individual names. A smaller holud or a combined walima and bou bhat is worth comparing before you cut individual names.
On the day
Give each event a door list and a person who holds it. At a big reception, a seating chart by the entrance and a couple of cousins guiding guests to tables saves a queue. Seat the elders near the stage and the toilets, and families with young children near the door. Make sure the caterer and the person in charge have the same final number.
Quick answers
Should we send one invitation or several? Either works if each guest only sees the events they’re invited to. A main card with an insert per event is one tidy way to do it.
How do we stop the list growing after we’ve given numbers? Name one list-holder per event, set a cut-off date, and keep a short waiting list for when people decline.
What number do we give the caterer? The confirmed adults for that event, plus children and supplier meals counted separately, by the caterer’s deadline.
Safety, in brief
- Dietary needs and allergies go to the caterer as a list.
- Allergen information for each dish at a buffet.
- Capacity: check the seated number after layout, not the headline figure.
Guest list checklist
- Event list with hosts and rough sizes
- Master list by household, with sides, contacts and dietary needs
- A column per event, with replies for each
- A list-holder named for each event
- A cut-off date agreed with both families
- Invitations or inserts per event, with clear wording
- Children and supplier meals counted
- Final numbers to each caterer by their deadline
- Seating plans and door lists ready
Tick these off in Wedvisa’s wedding checklist.
Your guest lists at a glance
| The structure | One master list, a column per event |
|---|---|
| Replies | A separate yes or no for each event |
| Who decides | One list-holder per event |
| Invitations | One main card with an insert per event works well |
| Count separately | Adults, children and supplier meals, per event |
| Deadlines | Each caterer’s final-number deadline; one caterer checked asks for two weeks |
| Wedvisa tools | Guest list manager, seating plan, checklist |
