My Side of the Guest List Had 400 People. Here's How I Managed It.
My family is large. I say this not as a complaint — most of the time, having a large family is genuinely good — but as context for what organising my own wedding required.
My father has three brothers. My mother has four siblings. There are 22 first cousins on my father's side alone. Add extended family, family friends who have been part of every celebration for two decades, my father's professional network (he runs a business; the line between professional and personal has been porous for thirty years), and the number gets somewhere between unsettling and alarming.
My fiancée's family, meanwhile, had around 200 guests on their side.
Total expected attendance: somewhere between 580 and 640 people across five functions. My side: 400 of them.
The question was never whether I could manage this. The question was what system I would use.
The Spreadsheet Phase
I started with a spreadsheet. Everyone does.
I built it over three evenings in October — two months before the wedding. Columns for name, relationship, function (Haldi, Mehendi, Sangeet, ceremony, reception — separately), city, confirmed/pending/declined, and notes. 400 rows.
For about two weeks, the spreadsheet worked fine. I updated it after calls. I cross-referenced it against my father's list (he had his own, naturally). I noted that my cousin's family from Surat hadn't confirmed for the ceremony yet and added a reminder to follow up.
Then the RSVPs started coming in.
Not through the spreadsheet, obviously. Through WhatsApp. Through missed calls that became callbacks. Through my mother, who collected confirmations from the people she had invited and reported them to me in batches — sometimes accurate, sometimes partial. Through my uncle, who confirmed his family for "everything" and then later clarified he meant "everything except the Haldi, obviously, we're not doing the Haldi." Through a group message in Family Functions where six people confirmed in a thread I missed for three days.
The spreadsheet became a document of what I had intended to track, rather than what was actually happening.
The Specific Problem With 400 People Across Five Functions
For a wedding with one function — say, a reception — managing a guest list of 400 is manageable if chaotic. You collect confirmations however you can, make an estimate, add a buffer, tell the caterer.
Five functions changes this entirely.
The Haldi was close family: about 80 people. The Mehendi was women-dominant: around 120. The Sangeet was wider: 250. The main ceremony: close to 400 on my side. The reception: effectively everyone, 580 total.
These are not variations on one list. They are five different lists, with different populations, different venue capacities, different catering requirements. Tracking all five accurately through a single spreadsheet updated manually from scattered sources was not a coordination problem — it was several coordination problems running simultaneously.
The catering coordinator — who had done this professionally for twelve years — told me that most groom families give him "rough numbers plus 15%." He had priced in the buffer already. He was used to imprecision.
I found that unsatisfying.
Finding a Better System
My colleague, who had gotten married the previous year, mentioned that he had used a wedding guest list app that handled RSVPs per function. He'd found it made the caterer conversation completely different — instead of "around 200 to 220," he gave an actual number and the caterer treated it as a real data point.
He sent me a link to Lumhe.
I was two weeks from the wedding at this point, which I realise is not ideal timing to introduce a new system. But I set it up on a Sunday afternoon. Uploaded our digital wedding invitation — we had an image card with both sets of family details — added all five functions with their dates, times, and venues, and generated a shareable link.
Then I shared it. Same groups where I had been fielding scattered confirmations. Directly to contacts on my list. My father shared it with his network separately.
What the Link Changed
Within 48 hours, I had 140 confirmed RSVPs with per-function attendance — all arrived without any follow-up calls from me.
This was not because people suddenly became more organised. It was because the link made confirming easy. One tap per function. No need to message me. No need to find the right group. No need to remember whether they had already confirmed or not.
The wedding RSVP tracking moved from "what I'm trying to assemble from scattered sources" to "what the dashboard shows me right now."
When my mother called to relay a batch of confirmations — which she kept doing, because that is simply how she operates — I could check whether those people had already confirmed through the link. Several of them had. I didn't need to add duplicates. I just thanked her and updated my own notes for the few who hadn't used the link yet.
The Function That Mattered Most for Headcount
The reception — 580 expected, both families combined — was where precise wedding function RSVP tracking made the most practical difference.
Because this was a joint count with my fiancée's family, we were both tracking separately and then comparing notes. She was using Lumhe for her side too. When we sat down three days before the reception to give the caterer a final number, we did not compare scattered confirmations or make an estimate.
We compared dashboard counts. Her side: 191 confirmed. My side: 274 confirmed. Combined: 465 confirmed, with another 40 or so likely walk-ins from the unconfirmed list.
The caterer received 510 as our working number. He was catering for 550 to be safe. Nobody ran out of food. No excess embarrassment from clear over-ordering.
For a 580-person reception, 465 confirmed against 550 catering is an outcome I am genuinely proud of — because it came from real data, not guesswork.
What I Would Tell Other Grooms Managing Large Guest Lists
A large guest list does not require more effort if you have the right system. It requires the same amount of effort redirected usefully.
The time I spent updating a spreadsheet from secondhand information was wasted. The time I spent sharing one link and checking one dashboard was not.
The whatsapp wedding invitation model — sending a card image to a group and hoping confirmations come back in the thread — does not scale past about 50 people before the confirmations become untrackable. For 400 people across five functions, you need a system where the tracking happens automatically when people confirm, not manually after the fact.
The specific tool matters less than the principle: one link, one dashboard, per-function headcounts. Everything else is noise.
If you're managing a large guest list across multiple wedding functions, explore Lumhe here.
Lumhe lets you upload any invitation — image, video, PDF — add multiple functions, share via link, and track per-function RSVPs in real time. For weddings with large guest lists, it's the difference between an estimate and an actual number.
