To manage entry for a wedding with 1,500 guests, load the guest list into a guest app before invitations go out, give every guest a personal QR entry pass, set a scan rule for each function, and keep a manual lookup at every gate for anyone whose phone fails. The pass identifies people; the rules decide who enters which function.
Why wedding entry is harder than conference entry
A conference has one badge and one door. An Indian wedding has a sangeet on one evening, a haldi in the morning, a baraat that assembles outside the venue, pheras with a restricted audience and a reception with the widest guest list. The Confederation of All India Traders projected 46 lakh weddings between 1 November and 14 December 2025 (CAIT, 10 Nov 2025). In a season that compressed, venues run back-to-back functions, and the family cannot afford a queue at the gate while a cousin searches a printed list.
The second difficulty is social. The person at the gate is often a relative or a hired steward who does not know every guest. Nobody wants to refuse a distant uncle, and nobody wants an uninvited crowd in the pheras enclosure. A digital pass takes the awkward judgement away from the steward and puts it in a rule agreed by the family beforehand.
Step 1: build one guest list with function tags
Start with a single sheet: name, mobile number, side (bride or groom), city, number of companions, and a column for each function with a yes or no. Resist keeping separate lists per function. One list, many columns, is what lets a rule be applied later.
Three details save trouble on the day:
- Use the mobile number the guest actually answers on. OTP login depends on it, and a guest who gets the OTP on a parent’s phone will not enter.
- Record companions as their own rows where you can, because a companion needs a pass of their own.
- Mark a short list of family-only guests, such as those invited to the pheras, so the rule for that function is a short allow-list rather than a long exclusion.
Step 2: choose how guests join
You have two sensible models. In an invite-only model, the guest list is the whitelist: a number not on it cannot log in. In an approval model, guests sign up and the family approves or rejects each request. Weddings usually suit the first; large community receptions with open invitations suit the second. Pick one deliberately, because mixing them at the last minute creates two truths about who is invited.
Step 3: set a scan rule per function
A pass is only as useful as the rules behind it. Decide, for each function, the following:
| Function | Who may enter | Scan rule | Fallback |
|---|---|---|---|
| Haldi or mehndi | Family and close friends | Allow-list group, one scan per person | Steward searches by name |
| Sangeet | All out-of-town and local guests | Time window from evening start, one entry scan | Search by mobile number |
| Baraat assembly | Groom side only | Group-restricted, no repeat scan | Family coordinator confirms |
| Pheras | Short family list | Allow-list group, scan to enter and to exit | Senior family member at gate |
| Reception | Everyone on the list plus companions | Time window, repeat scans flagged | Manual add with approval |
The aim of a repeat-scan limit is not to catch people; it is to stop a single screenshot of a QR passing from guest to guest.
Step 4: tell guests what to carry
In the invitation message, say plainly: open the wedding app, log in with your mobile number, and open the Entry Pass tile. Ask guests to save a screenshot as a back-up only if you accept screenshots; if you do not, tell them the live pass refreshes in the app. Mention that the QR must be shown on a bright screen, because dim phones in a dark baraat lane are the most common reason for a failed scan.
Step 5: staff the gates
For 1,500 guests, think in terms of lanes rather than a head count. One lane for the guests who scan quickly, one lane for lookups, and one lane for family VIPs who should not queue at all. Brief each steward on three phrases: how to scan, how to search a name, and whom to call when a person is not on the list. A steward who can say “please wait one minute, I will check with the family desk” avoids a scene.
Give the lookup lane a quiet corner. People whose phones have died, who have a new number or who are walking in without a QR are best served away from the main queue.
Step 6: run the day and read the numbers
Watch the scan count against the expected list during the function. If the reception has 1,200 expected and the count stalls at 400 an hour after the muhurat, you know to send a push or WhatsApp nudge, or to check whether a gate scanner has lost signal. After the event, export the scan record: it shows who attended which function, which is useful for thank-you messages and for the next family occasion.
When something goes wrong at the gate
Prepare for the three most common failures. If the phone has no signal, the steward can still search the guest list by name or mobile number and mark the guest in, so keep the lookup path working even when the QR scan does not. If a guest arrives with a new phone number, the family desk can update the number on the list and the guest can log in again. If a guest shows a screenshot of a pass that has already been scanned, the steward should not argue at the gate: take them to the lookup lane, confirm identity with the family coordinator and decide quietly. Brief everyone that the goal is a calm entry, not a perfect catch.
How Sociana handles this
Sociana’s entry pass and personal QR puts the pass on the guest’s Home screen and keeps the personal QR in Profile, as one identity rather than separate codes. Guest lists and approvals let the family choose between a whitelist and approval-based registration. Each function is an attendance activity with its own rules, which is how the QR attendance and activities feature handles time windows, group eligibility and repeat-scan limits.
The Tanvi & Rutwik wedding app (a three-day Pune wedding, planned, not yet run) is the closest example: it shows guest document status to organisers at attendance and uses bride-side and groom-side groups. Sociana provides a QR entry pass, organiser scan and self check-in; it does not print badges or supply kiosk hardware, so the family or planner arranges steward devices.
For the wider picture, see wedding apps for families and planners and the glossary entries for plus-one and QR entry pass.
Frequently asked questions
Do all 1,500 guests need to install the app?
No. Guests need the app or login to show a pass, but a family can keep a manual lookup lane for anyone who has not installed it. Most hosts send the invitation with a clear instruction and a reminder two days before.
How do we handle guests with no smartphone?
Add them to the guest list with a family member’s number as a companion, or record them for manual entry. The steward finds the name and marks them in through the scanner screen, so the attendance record stays complete.
Can one guest’s QR let several people in?
Only if you allow it. Treat each person, including children above the age you choose, as a row with their own pass, and set a repeat-scan limit so a shared screenshot is flagged on the second scan.
What if the venue has poor signal at the gate?
Plan for it. Test the gate scanner on the venue network the day before, keep a printed short list for the pheras enclosure, and make sure stewards know the manual lookup path. Do not make the entire entry process depend on one weak connection.