My Son's Wedding Had 6 Functions. I Tracked Every RSVP From My Phone.
My son got married last November. Six functions over four days — Haldi, Mehendi, Sangeet, the main ceremony, a family lunch the next morning, and the reception in the evening.
Four days. Six events. Four hundred and twelve guests across all functions combined. Different guests at different events. Some travelling from other cities. Some attending just one function. Some attending all six.
I am a retired school principal. I managed a staff of 60 and a school of 1,800 students for 22 years. I know how to organise things. I know how to track information. I know that if you do not write something down, it does not exist.
So when my son said, "Amma, don't worry, we'll manage the guest list," I smiled and said nothing. And then I quietly started my own system.
The First Notebook
I bought a new notebook specifically for the wedding. Ruled, A4, 200 pages — the kind I used to use for staff meeting minutes. I divided it into sections: one for each function. Under each function, I wrote the names of the guests we intended to invite.
By the time I finished the first draft, I had written 347 names across the six functions, with some names appearing in multiple sections. I had also used 34 pages.
My daughter-in-law — a software engineer, bless her — looked at the notebook with the expression of someone trying to be respectful and failing slightly. "Amma," she said carefully, "what happens when people confirm or cancel? How do you update it?"
I showed her the pencil I had been using. She nodded slowly.
"And if someone confirms for Haldi but cancels for Sangeet?"
I showed her the eraser.
She suggested we try something on her phone.
The Spreadsheet My Daughter-in-Law Built
She built a spreadsheet that weekend. It was genuinely impressive — columns for each function, colour-coded cells, drop-down menus for confirmed/cancelled/pending, a formula that calculated the total headcount per event automatically.
I learned to use it. Slowly. With reading glasses and considerable patience from my son, who sat with me for two evenings teaching me how to navigate it on my phone.
The problem was not the spreadsheet. The spreadsheet was excellent. The problem was the wedding function RSVP process itself — how we collected the confirmations in the first place.
Every RSVP came through a different channel. My husband's brother's family confirmed by phone call to my husband, who told me, and I updated the spreadsheet. My son's college friends confirmed in a WhatsApp group that my daughter-in-law was tracking separately. My sister-in-law's family sent a message to my sister, who called me. The caterer's venue contact kept asking for "final numbers" for each function, and every time I gave him a number, someone else confirmed or changed their plans within 48 hours.
Wedding RSVP tracking through a spreadsheet works if the confirmations come in cleanly. Ours did not come in cleanly. They came in the way water comes through a roof that needs repair — from multiple unexpected directions, at unpredictable times.
By the third week, my son had started calling it the "living spreadsheet" because it was never in a final state. It was always in the process of becoming accurate.
The Function Nobody Could Keep Track Of
The family lunch on the morning after the ceremony was the function that caused the most confusion. It was smaller — maybe 80 guests, immediate family and closest friends only — but because it was not the "main" event, people were uncertain whether they were invited, whether they were expected, and whether they needed to confirm separately.
We had 80 people on the list. By the morning itself, we had 94 show up. Fourteen extra people, because relatives who had attended the ceremony assumed the family lunch was included. The kitchen managed. Just. But it was not graceful.
After that, I became very focused on per-function clarity. Every function needed its own confirmed headcount, separate from every other function. The Haldi number and the reception number were completely different populations. Tracking them together was like tracking apples and mangoes in the same column.
What My Daughter-in-Law Found
About six weeks before the wedding, my daughter-in-law came to me with her phone.
"Amma, I found something. Can we try it for the digital wedding invitation for the reception at least?"
It was Lumhe. She showed me how it worked: you upload your invitation — in any format, image or video or PDF — add the event details, and share it as a link. Guests open the link, see the invitation, and confirm their attendance with one tap. You see all confirmations in one place, in real time, per function.
"Each function is separate," she said. "Haldi RSVPs here. Reception RSVPs here. They don't mix."
I looked at the screen for a moment. Then I looked at my 200-page notebook.
"Show me how to use it," I said.
We used it for the reception — our largest function, 280 guests on the list. My daughter-in-law set it up. I sent the link to the guests on my side. My son sent it to his list. My husband's side received it from my brother-in-law, who forwarded the link.
The link worked for everyone. When guests opened it, they saw the invitation card, the venue details, the time, and a simple button to confirm. Every confirmation appeared on the screen immediately. No phone calls to relay. No spreadsheet to update manually. No erasing.
The Difference It Made
I want to be honest about this. Lumhe did not save the wedding — the wedding was wonderful regardless. But it changed one specific thing significantly: I stopped being anxious about the reception headcount.
For every other function, I was managing wedding rsvp tracking through a combination of phone calls, WhatsApp messages, notebook entries, spreadsheet updates, and the occasional relay through four family members. By the time a confirmation reached me, I was never fully certain it was current.
For the reception, I looked at my phone. I saw 247 confirmed. Then 251. Then 259. I knew, at any moment, the actual number — not an estimate, not a "we think approximately," but the actual number of people who had said yes. When the caterer called three days before the reception asking for the final count, I told him 271. He said he needed it by tomorrow. I said I would call him tomorrow with the updated number. The next morning it was 278. I called him. He was surprised I had an exact number.
"Most families give me a range," he said.
I had a number.
What I Would Tell Other Mothers
If you are the mother — of the bride or the groom — and you are the one actually managing the logistics of this wedding, here is what I learned:
The guest list is not one list. It is six lists, or four, or however many functions you have. Each function is its own event with its own headcount. Tracking them together is how you end up with 14 unexpected guests at the family lunch.
A wedding guest list app that handles per-function RSVPs separately is not a luxury. For a multi-function Indian wedding, it is the only way to have accurate numbers for each event without spending every evening on the phone.
You do not have to use it for everything from the beginning. We used it for one function — the reception — and it made that function the most cleanly organised event of the four days. Next time — my daughter, whose wedding is in three years — we start from the Haldi.
Upload your invitation once. Add each function separately. Share the link. Track wedding RSVPs in real time.
Your notebook is for other things. I still have mine. It has 34 pages of names in pencil, many of them half-erased. I am keeping it. It is, in its own way, a record of how much went into those four days.
But next time, I am using Lumhe from the beginning.
If you are planning a multi-function wedding and want to manage every wedding function RSVP in one place, explore Lumhe here.
Lumhe lets you upload any invitation, manage RSVPs per function separately, and share via link on any platform — for weddings, engagements, birthdays, and every occasion worth organising properly.
