Tier and Track Your Guest List

Here is my messy list of guests. Turn it into a clean, tiered, trackable guest list that fits my headcount ceiling — and help me handle the family politics. Read everything before you write.

MY EVENT PROFILE (fill this in once — reuse the same block for every prompt in this kit):
- Event type: [FILL: wedding / birthday / corporate / community or religious event]
- Sub-events, if multi-day: [FILL, e.g. haldi, sangeet, ceremony, reception — or "single event"]
- Date(s): [FILL]
- City + country: [FILL]
- Venue type: [FILL: indoor / outdoor / banquet hall / home / farmhouse]
- Headcount ceiling — the most people the venue and budget allow: [FILL: number, or "not sure yet"]
- Est. cost per plate, if I know it: [FILL, or "not sure"]
- Culture / religion / rituals: [FILL, e.g. Hindu Punjabi — or "secular"]
- Who's hosting / paying: [FILL]
- The vibe in one line: [FILL]

MY GUEST NAMES (paste them however they are — one per line, grouped by side/family is ideal, duplicates and all):
[PASTE NAMES]

For an Indian joint-family wedding, paste each side's must-invite list SEPARATELY and label them (e.g. "Groom's side", "Bride's side") so I can set a fair quota per side:
[PASTE PER-SIDE LISTS, or write "single list"]

Localize to my country: default to Indian norms and ₹; use R$ and Brazilian norms if I'm in Brazil, $ and US norms if the US. Reply in the language I wrote in.

If my headcount ceiling is missing and it would change the list, ask me for that one number and stop. Otherwise continue.

How to build it:
- One row per PERSON, never per household — 'The Sharmas (4)' becomes four named rows so every seat and every plate is counted.
- De-duplicate: merge the obvious repeats and tell me which ones you merged.
- Tier every guest A / B / C: A = non-negotiable, invite no matter what; B = invite if space and budget allow; C = invite only as A/B guests decline and free up seats. Rank the B and C names so the next person up the list is always obvious.
- Multi-event tagging: tag which functions each guest is invited to. For an Indian wedding keep the intimate functions (haldi, small pujas) to close family, and widen out for sangeet and reception.
- Plus-ones: apply one clear policy — spouses, engaged and live-in partners get a named plus-one; single guests get one only if I say so. Add each named plus-one as its own row.
- Headcount ↔ budget link: every extra guest = cost per plate × the number of catered functions they attend. Show me in one line what 20 more B-tier names would actually cost across the events, so the trade-off is real.

Give me:
1. A guest tracker table I can paste straight into Google Sheets or Excel, one row per person: Name | Side / Group | Tier A/B/C | Events invited to | Plus-one Y/N | Est. attending (Y/N/maybe) | RSVP status | Dietary / notes | Contact.
2. A tier summary: count and running headcount for Tier A, then A+B, then A+B+C, plus a per-event rollup (how many are invited to each function).
3. A 'does this fit?' check: projected attending vs my ceiling as a specific over-or-under number (e.g. 'A+B = 214 attending vs your 180 ceiling → 34 over; cut 34 from the bottom of B or move the overflow to C').
4. A family-politics script: 2–3 polite-but-firm lines I can send when someone pushes to add names, plus a fair per-side quota split of my ceiling (e.g. 90 groom's side / 90 bride's side) and how to hold it.
5. A cut-off date for the final list and an RSVP timeline working back from my event date.

Never invent guests, and never round a count up to look fuller. Keep the running headcount honest and always tied to my ceiling and per-plate cost. End by telling me the single number to carry into the Budget prompt: my planning headcount.