When to send what, and when to chase replies.

1. Work back from the RSVP deadline

The RSVP deadline is the anchor everything else hangs from. Set it 2–3 weeks before the wedding — enough time to chase late replies, confirm the final headcount with the caterer, and adjust seating without panic. In Indian weddings, where guest lists can shift until the last moment, a 3-week buffer is safer than 2.

Once the deadline is fixed, the rest of the timeline writes itself: reminders go out one deadline-cycle before it, invitations go out roughly 8–10 weeks before it, and save-the-dates go out months earlier for guests who need to arrange travel. Working backwards removes the guessing and keeps every send date purposeful.

• ✓Set the RSVP deadline 2–3 weeks before the wedding.
• ✓Work every other send date backwards from that anchor.
• ✓Share the deadline clearly on every invite and reminder.

2. Save-the-dates at 5–6 months

Save-the-dates are not a formality — they are a travel warning. For out-of-town family, friends flying in from other cities, and anyone juggling work leave, 5–6 months is the minimum heads-up that a wedding is coming and a trip needs planning. In India, where weddings often span multiple events over several days, early notice matters even more.

The save-the-date needs almost no detail: names, the city, the rough date, and a note that the formal invitation will follow. A wedsite link is useful here — guests can bookmark it and check back as details firm up. Send physical cards to the closest elders and digital versions to everyone else; the split is common and accepted.

• ✓Send 5–6 months out, earlier for destination or multi-event weddings.
• ✓Include city, rough date, and a wedsite link — nothing more.
• ✓Use physical cards for key elders and digital for the wider list.

3. Invitations at 8–10 weeks

The formal invitation carries the real details: date, time, venue, dress code, and exactly how to RSVP. Eight to ten weeks gives guests enough time to respond without feeling rushed, and gives you enough time to chase the stragglers before the deadline. For very large weddings, lean toward ten weeks; for smaller or local-only lists, eight is usually enough.

In the Indian context, this is also when you share logistics that matter: parking near the venue, nearby hotels for out-of-town guests, and any event schedule that spans multiple days. A wedsite is the cleanest way to centralise all of this — one link replaces five paragraphs of cramped card text.

• ✓Send 8–10 weeks before the wedding.
• ✓Lead with date, venue, dress code, and RSVP method.
• ✓Point guests to a wedsite for travel, schedule, and registry details.

4. Reminders at 3–4 weeks

A polite reminder 3–4 weeks before the RSVP deadline nudges guests who opened the invite, meant to reply, and forgot. The tone should be warm and helpful — not pushy. A short message repeating the deadline and the reply method, with the wedsite link again, is usually enough.

For Indian weddings, where WhatsApp is the dominant communication channel, a broadcast or group message works well for the wider list, with a personal follow-up for the closest family. The reminder is also a useful checkpoint for you: if half your list has not responded, you know the chase phase is coming.

• ✓Send a warm reminder 3–4 weeks before the RSVP deadline.
• ✓Repeat the deadline and the reply method clearly.
• ✓Use WhatsApp for the wider list and personal calls for close family.

5. Feed responses into the final headcount

As RSVPs arrive, record them in one place — not scattered across chat threads, email inboxes, and verbal promises. The goal is a single guest list with every response marked: yes, no, maybe, plus-one confirmed, dietary restrictions noted. This list becomes the final headcount you hand to the caterer and venue.

Close the list firmly one week before the deadline, then chase only the remaining late responders once. After the deadline passes, lock the number. A small buffer of 3–5% is sensible for Indian weddings, where a late uncle or a cousin's new friend often appears at the last minute, but the core number should be fixed.

• ✓Record every RSVP in one master list as it arrives.
• ✓Chase late responders once, firmly, one week before the deadline.
• ✓Lock the headcount at the deadline and add a small buffer for late surprises.

6. One owner for the invite list

Guest list ownership is the single most common source of invitation chaos. When both partners, both mothers, and a sibling are all adding names, the list balloons, duplicates multiply, and the RSVP tracking becomes impossible. Name one person to own the master list — who is invited, who has replied, who needs chasing — and make every update route through them.

That owner should also be the one who shares the final headcount with the caterer and venue. One voice, one number, no confusion. Whether you use a shared spreadsheet or a planner like Vowably, the rule is the same: one list, one owner, reviewed weekly from the invitation send date through the final headcount.

• ✓Name one person to own the master guest and RSVP list.
• ✓Route every addition, deletion, and status update through them.
• ✓Review the list weekly from invitation send until final headcount.