How accurate is a Nigerian wedding RSVP?

Roughly 70–85% of "yes" RSVPs actually show up. ~15–25% of "no" RSVPs show anyway (with a plus-one). Plan catering for "yes count × 0.85 + buffer 10%". You'll be close.

When should I send invites?

Save-the-date 4–6 months out. Formal invite 8–10 weeks out. RSVP deadline 4 weeks out. Final headcount to caterer 2 weeks out. Compressing this only hurts your accuracy.

What about plus-ones?

Decide your policy BEFORE you send invites. The three viable rules: (1) plus-ones for engaged/married only, (2) plus-ones by invite text only, (3) plus-ones everyone — pick one. Mixed signals destroy guest lists.

How do I handle uninvited guests?

Pre-empt with a discreet security brief — they're trained to check the link/name list and politely redirect. A real system (vs WhatsApp) gives you a check-in list bouncers can search by name.

Can I cap an RSVP link so it auto-closes?

Yes. Owa Planner's RSVP forms have a capacity field — once submissions hit the cap, the link shows a "list is full" page instead of accepting more. Per-group links can have separate caps.

RSVP for 600+ Guests at a Nigerian Wedding: The System That Actually Works

If your guest count is under 80, a WhatsApp thread works. Under 200, a spreadsheet survives if you're diligent. Above that, you need a real system or you lose a week to RSVP chasing — and that week is the one you needed for the venue tour, vendor briefings, and the gele rehearsal.

This is the system. Tested across Lagos weddings of 400, 600, and 1,200+ guests.

In short: Run separate RSVP links per group (family, friends, work) with auto-tagging. Cap each link at the actual seat count. Send the link 8–10 weeks out, deadline 4 weeks out, hard close 2 weeks out. Treat "yes" attendance as 75–85% of the count, not 100%.

The four problems a real system solves

"Did Tomiwa RSVP yet?" With WhatsApp you don't know. With a real system, you search a name. 4 seconds vs 40 minutes scrolling.
"My list went from 400 to 600 in two weeks." Open invites + casual forwards = explosive growth. Capacity caps stop it at the source.
"Who's bringing a plus-one?" Tracking 200 plus-ones in a spreadsheet is the dictionary definition of regret. RSVP forms ask the question for you.
"The bouncers don't know who's invited." A real list = a check-in page. Anyone can search by name on the day.

The system in 5 pieces

Piece 1 · A single source of truth

One list. Not a WhatsApp thread + a spreadsheet + a Notes app. Pick the canonical place and never duplicate.

Owa Planner's Guests module does this — every RSVP, however it came in (form, manual add, CSV import) lands on one list. You can filter by status, search by name, export the whole thing. See it →

Piece 2 · Separate links per group

Send different RSVP links to different groups. This solves three problems at once:

Tracking. You can see who came from where without asking anyone.
Different messaging. Family gets warmer copy; work colleagues get the formal version.
Different rules. Family gets plus-ones; work doesn't.

Owa's per-group RSVP forms auto-tag every submission with the group label. Family RSVPs land as "family", friends as "friends", etc. Filtering the master list is one click.

Piece 3 · Capacity caps

This is the underrated lever. Your venue seats 500. Your list will swell to 700 if you let it. Cap each group's link at the count you actually planned for:

Link	Cap	Reason
Bride's family	120	Pre-allocated by mum
Groom's family	120	Same
Bride's friends	80	The actual close circle
Groom's friends	80	Same
Work / colleagues	50	Wider but lighter touch
Open / extras	50	Buffer for stragglers
Total	500	Matches venue capacity

When a link fills, it auto-closes — guests see a "this list is full" page and message you directly instead of silently doubling your count. Owa's RSVP forms have this cap built in.

Piece 4 · The cadence (8 weeks of communication)

Week 10 — Save-the-date sent. No RSVP needed yet.
Week 8 — Formal invite + RSVP link. First send.
Week 6 — Soft reminder to non-responders. Different copy per group.
Week 4 — Deadline reminder. Last call to be on the formal list.
Week 2 — Hard close. Anyone who responds after this is "best efforts" only.
Week 1 — Final headcount to caterer + venue.
Day before — Check-in list exported, given to bouncers + ushers.

Piece 5 · The "yes" attendance reality

Plan catering for 85% of your "yes" count. That's the Nigerian RSVP truth. Some yeses don't show (illness, traffic, work conflict), some "no"s show anyway (changed mind, plus-one upgrade), some "didn't respond" appear unannounced.

The math:

500 yeses → plan catering for 500 × 0.85 = 425 + 10% buffer = ~470 plates.
Round up if you're risk-averse — leftover food is a smaller pain than running out.

What goes wrong (and how to fix it)

"My uncle invited 30 people he didn't tell me about." Welcome to Nigerian weddings. Pre-empt: ask each parent to confirm their list IN WRITING. Once it's on the spreadsheet, anyone they add later goes on a separate "uncle's invitees" list you don't owe a seat.

"Plus-ones doubled my count." Plus-ones happen because the rule wasn't clear. Print the rule on the invite. Print it on the RSVP form. If you don't allow plus-ones, the form doesn't let them add one.

"I have 200 'didn't respond'." Don't chase 200. Pick the 30 you actually care about and follow up personally. The other 170 are coming or not — your catering buffer covers the swing.

"Two days before, 80 more people 'confirmed'." This is why the hard close exists. Late confirmations are best-effort seating, not guaranteed.

What changes for diaspora couples

If you're collecting RSVPs across time zones, the cadence matters more:

Send invites with 12+ weeks of runway (not 8) — your guests need to book flights.
Stagger reminders by region (US guests get reminded on US-friendly days).
Pre-book hotel blocks BEFORE confirming RSVPs; release the unused ones at week 4.
Build a "Travel" section on your event website with airport pickup logistics. Owa's event website has this section by default.

The diaspora playbook covers the full version.

The Owa Planner RSVP module — in 60 seconds

If you're picking a tool for this, here's what Owa does that WhatsApp + spreadsheets can't:

Per-group named RSVP links with auto-tagging. "Bride's family → tag: family" so every submission is sorted at intake.
Capacity caps per link. List auto-closes when full.
Public RSVP page at /r/<your-link> — branded, mobile-fast, asks about each ceremony separately (intro, traditional, white).
One master list that combines form submissions + manual adds + CSV import. Search, filter, export to Excel.
Default emails to guests on submit + on approval — no automation setup needed.
Approval flow for guests who need bride/groom sign-off.
WhatsApp broadcasts to the RSVP list, segmented by group tag or RSVP status.

Try it free → — the AI Planner gets you a real event set up in 8 minutes; the RSVP module is on the next screen.

What to do this week

If you haven't sent invites: lock the per-group link strategy before you do. Don't send a generic link and try to backfill the groupings.

If invites are out: turn on capacity caps now if your tool supports it. Decide the per-group caps based on what your venue actually seats.

If you're past the deadline: don't be precious. Hard-close the link and run with the count you have. Stragglers are best-effort.