We're an NRI Family Planning a Wedding in India — This Is How We Coordinated
My brother's wedding was in Pune. We were in Toronto.
There are twelve and a half hours between Toronto and Pune, depending on the time of year. There are also seventeen family WhatsApp groups, three different aunts who each believe they are the primary coordinator, and one very detailed spreadsheet my mother had been maintaining since the engagement — which, by the time we arrived two weeks before the wedding, had not been updated in three months.
This is the story of how we planned a wedding from the other side of the world, what worked, what absolutely did not, and what we would do differently.
The Timezone Problem Nobody Warns You About
When you are planning a wedding in India from abroad, the first thing you discover is that there is no good hour to take a call.
If I called Pune in my evening — which is the reasonable time to make personal calls — it was 6:30 AM in Pune. My mother is an early riser. My future sister-in-law's mother is not. Half the important conversations I needed to have were not possible until I stayed up until midnight Toronto time, which is 12:30 PM Pune time, which is the middle of the working day for everyone I was trying to reach.
We eventually settled on a standing call on Sunday mornings, Toronto time — Sunday evening in Pune. My brother. My mother. Me and my husband. Sometimes my brother's fiancée. Forty-five minutes, once a week, trying to compress everything that needed discussion into one call before the WhatsApp groups took over again with contradictory information.
The calls were good. The WhatsApp groups were chaos.
The WhatsApp Group Situation
There were seventeen groups. I am not exaggerating.
Rishta Group (original, from when the match was discussed). Wedding Planning Core (added when the engagement happened). Wedding Planning Extended (added when the core group got too large). Venue Options (added and abandoned within a week). Invitation Design (added for the card). Guest List Mama Side (my uncle's contribution). Guest List Papa Side. Friends and Cousins Sangeet. Caterer Coordination. And so on.
My husband, who had married into this situation, counted the groups one evening and showed me the number on his phone with the expression of a man who has accepted his circumstances.
The problem with seventeen groups is not the volume — it is the fragmentation. Important decisions got discussed in one group and missed by everyone in the other groups. The venue was confirmed in Wedding Planning Core but the information never reached Wedding Planning Extended, so we spent an entire Sunday call discussing something that had already been decided three weeks earlier.
Guest confirmations were scattered across every group. Someone would write "we are coming for sure, all four of us" in Rishta Group — a group my brother had left six months ago because the original purpose was over. Their confirmation existed, technically. But nobody who needed to act on it had seen it.
The Invitation Problem
My brother handled the digital wedding invitation from Pune. He used a design tool to make a beautiful card — our family colours, the traditional motifs my mother wanted, both English and Marathi text. It looked exactly right.
The problem was distribution. He sent the card to me on WhatsApp. I shared it in my contacts. My husband shared it in his. My mother had her own list. The card was going out, but there was no single record of who had received it, who had opened it, and critically — who had confirmed.
I was tracking RSVPs for the Canadian guests — three families in Toronto, one in Vancouver, two in the UK who were also technically our responsibility. I was doing this in a Notes app on my phone because I could not access the Pune spreadsheet reliably on my phone, and every time I tried to update it, there was a version conflict with whatever my mother had updated from her end.
The Vancouver family confirmed — to my brother directly, on a call. He forgot to tell me. I spent two weeks thinking they were pending and following up with them twice. They were very gracious about it.
What Made the Difference
My sister-in-law's younger brother — 24, works at a startup in Bangalore — suggested Lumhe three weeks before the wedding.
He set it up. Uploaded the invitation card in about ten minutes. Added all four functions: the Haldi (close family only, 60 people), the Sangeet (150 people), the main ceremony (240 people), and the reception (310 people). Each function separate, with its date, time, and venue.
Then he shared a link. One link. Anyone who received it could open it, see the full invitation with all the function details, and confirm which events they were attending — from anywhere in the world, on any phone, in any timezone.
For me, sitting in Toronto, this changed everything.
I sent the link to the Canadian families. They opened it, saw the invitation card (the same beautiful card my brother had designed — it was just uploaded to Lumhe), saw the function details, and confirmed directly. No forwarding chains. No version confusion. No wondering if they had received the right information.
I could see their confirmations in real time. Not through a relay of WhatsApp messages and a call to my brother who called my mother who checked the spreadsheet. I opened the app and saw: Vancouver family — confirmed, 3 attending, ceremony and reception. UK family — confirmed, 2 attending, reception only. Toronto families — all confirmed.
Wedding RSVP tracking across three countries and four timezones, from one screen.
The Function That Almost Went Wrong
The Haldi was close family — 60 people, Pune and nearby only. We were coming from Toronto and arriving two days before. We were on the list.
At some point in the coordination, our names got dropped from the Haldi headcount. Not maliciously — just lost in the seventeen-group noise. My mother thought my brother had confirmed us. My brother thought my mother had. The Haldi venue coordinator had 58 names. Not 60.
We caught it because we could see the wedding function RSVP counts in Lumhe and noticed our names were missing — two days before the event. A quick correction, and it was fine.
Without that visibility, we would have walked into a Haldi that had not planned for us. It sounds like a small thing. At a wedding, nothing is a small thing.
What We Would Do Differently
If we were doing this again — and we will be, my cousin's wedding is next year, also coordinated from abroad — this is what we would change:
Start with one coordination system. Not seventeen WhatsApp groups. One system where invitations are managed, confirmations tracked, and information accessible to everyone who needs it regardless of timezone.
Send the invitation as a link, not a file. A link works identically whether the recipient is in Pune or Vancouver. A forwarded image loses quality, arrives without context, and creates no record of who has confirmed.
Track per function from the beginning. The 60-person Haldi and the 310-person reception are completely different events with different logistics. They should never share a headcount.
Designate one coordinator abroad. For our wedding, I was the Canada coordinator. But I didn't have access to the same information as the India coordinators, so my coordination was always slightly out of sync. With Lumhe, the information is the same for everyone — no matter where they are.
NRI weddings in India are uniquely complicated — not because the families are difficult, but because distance and timezone genuinely create coordination problems that no amount of goodwill can fully solve without the right system.
Planning a wedding in India from abroad? Upload your invitation to Lumhe, add your functions with their details, and share a single link that works for guests in every city and every country. RSVPs come in from everywhere. You see everything in one place, in real time.
Lumhe lets you upload any invitation, manage RSVPs per function, and share via link on any platform — for NRI families planning weddings in India and every multi-city celebration.
