Signed Up Doesn't Mean Showing Up: Event RSVP and Check-In for Your Vibe Project
200 sign-ups, 96 arrivals — where did the missing half go? This guide covers the event page, sign-up form, waitlist promotion, reminders and confirmation, and door check-in, connecting every step from sign-up to arrival. All example projects, people, and numbers in this guide are fictional.

A-Jiao runs a Saturday woodworking class on "Street Corner Workshop": 120 seats, and sign-ups opened to 200 registrations in three days — the extra 80 went on a waitlist. On Saturday morning at 9, she arrived half an hour early, set out 120 tool kits, bought 120 lunches, and printed 120 name badges. At 9:30, when the class started, only 96 people were sitting in the room: 24 seats empty, 24 lunches uneaten, name badges sitting in a pile on the table. Meanwhile, 18 of the 34 people on the waitlist had received a "a seat has opened up" message the night before — but it was sent at 1 a.m., they only saw it in the morning, and there was no time to get there. Her strongest feeling that day was not "not enough people", but "there were enough people, and the process lost them": registered people did not come, people who wanted to come never got the message, seats sat empty, lunches went to waste, tools sat idle — all three sides wasting at once.
Two things to make clear first. First, the walkthrough project "Street Corner Workshop", the operator "A-Jiao", the participants "Lao Zhou" and "A-Li", and every time, quantity, and number in this guide are fictional, invented only to make the process clear. Second, boundaries: this site has already published several guides that look similar but are not the same thing — "Waitlist in Practice: Gathering Your First Users in the 30 Days Before Launch" covers the pre-launch waitlist; "Don't Rush the Launch Event: A Private Beta Playbook for Your Vibe Project" covers how to hand out beta access; "Time Zones Are Where Booking Features Go to Die: Calendar Booking for Your Vibe Project" covers one-to-one calendar bookings; "Two-Way Calendar Sync: Bringing Google and Outlook Calendars Into Your Vibe Project" covers syncing external calendars. This guide does not repeat any of them. It covers one thing only — how to handle every step between someone signing up for an event and someone actually showing up. One more note: the "door check-in" in this guide means checking people in at the event itself, which is not the same as the daily check-in streaks in "Don't Let One Missed Day Ruin Everything: Check-Ins and Streaks for Your Vibe Project". Two "check-ins" that only share a name.

1. First, the reality: signing up is not showing up — where does the missing half go?
People who run events tend to stare at the sign-up count: 200 sign-ups, so they assume 200 people will come on Saturday. The sign-up count is the easiest number to get, and the most misleading one — tapping "Sign up" takes three seconds and costs almost nothing; getting up on Saturday morning, getting dressed, travelling, and arriving on time costs a whole morning. Between signing up and showing up lies an entire week of life: sudden overtime, a sick child, rain, oversleeping, simply forgetting. Preparing the venue and the lunches based on sign-ups, and the empty seats are the price.
The fictional example numbers in this guide are: 200 people signed up, 156 opened the reminder before the event, 118 confirmed they would come, and 96 actually showed up. These numbers are fictional, and they make one point: people do not drop out in one place, but in three — the reminder was never opened, the confirmation was never answered, and even confirmed people did not come. Each step converts at 78%, 76%, and 81% — none of them low on its own — but multiplied together, 200 people become 96, an attendance rate of 48%. The number to prepare for is 96, not 200. Prepare for 200 and you double the venue, lunches, and tools; prepare for 96 and you worry there will not be enough seats if more show up. The next sections take that dilemma apart, one piece at a time.
Here is another fictional comparison: without a confirmation step, 200 sign-ups brought 71 arrivals, an attendance rate of 36%; with a pre-event confirmation step, 200 sign-ups brought 96 arrivals, an attendance rate of 48%. Both numbers are fictional. The point is not 36% versus 48%, but what confirmation is worth: confirmation does not burden users — it turns "might come" into "probably will come", and turns the basis for preparation from a guess into a calculation. Among people who confirmed, attendance was 81% — 118 confirmed, 96 came. The confirmation list is the most reliable attendance forecast there is, far more reliable than the sign-up list.
So the first rule of event sign-ups and attendance is: signing up, reminding, confirming, and showing up are four separate jobs — do not do only the first one. Doing only sign-ups means building an entrance and leaving the next three stretches of road for users to walk, remember, and struggle through on their own. The smoother the entrance and the emptier what follows, the more people drop out. Sign-ups, reminders, confirmation, and attendance have to be designed as one pipeline: every step knows what comes next, and every step makes the next one easier.
2. The event page: six facts, stated once, clearly — before users find out something is wrong after signing up
When users open an event page, there are really only six things they want to know: when, where, what, how much, how long, and what to bring. Miss one of the six, and users sign up with a question hanging over them; miss two or more, and they either do not sign up, or sign up and only discover at the venue that something is wrong — the time does not work, the place is too far, they were supposed to bring tools they did not bring. The event page has one job: state all six facts clearly, before showing the sign-up button.
First, time: give the date, the day of the week, and the start and end times — for example, "Saturday 14 November, 9:30–12:00" — not just "Saturday morning". Second, place: give the venue name, the full address, and how to get there — which subway line and exit, where to park, any obvious landmark at the entrance. A shopping mall name with no floor or entrance is the same as no address at all. Third, content: say in two or three sentences what actually happens — "Build a small wooden stool, from choosing the timber to sanding and oiling, with the teacher guiding you throughout" — not empty phrases like "an exciting event awaits".
Fourth, cost: if it is free, write "Free"; if it costs money, write how much, what it includes, and whether it can be refunded. For paid events, put the refund rule on the page — do not let users discover "no refunds within 24 hours of the start" only when they try to cancel. Fifth, duration: state how long it lasts, whether there is a break, and whether people can leave early — "2.5 hours, a 10-minute break in the middle, you can leave once you finish" — so users can plan their half-day. Sixth, what to bring: list what to bring and what not to bring — "Tools and materials are provided on site; just bring a water bottle." Once the six facts are written, show the sign-up button. Add one small line next to it: "You can cancel for free up to 24 hours before the event." That one line halves the psychological cost of signing up.
One line must not be crossed: the numbers on the event page must be real. If there are 120 seats, write 120 — do not write "Only 3 seats left" to rush sign-ups. When it is full, write "Full — join the waitlist"; when it is not, write honestly "86 signed up, 34 seats left". Fake urgency buys one sign-up and loses the next attendance: when users arrive and find half the seats empty, the next time they see your event their first thought will be "Last time it said full, and half the people never came."
3. The sign-up form: ask only what you must know at the moment of signing up — everything else can wait
The sign-up form is the second place people drop out — not because they do not want to sign up, but because the form asks too much and they give up halfway. The most common fault is stuffing in everything the organiser "might want to know one day": name, phone, age, occupation, how they heard about the event, how many times they have attended before, allergies, an emergency contact — a dozen fields, and by the end the user's enthusiasm for signing up has been ground away by the form. A sign-up form asks one thing only: what the organiser must know at the moment of signing up. Everything else can wait.
The fictional example number in this guide is a maximum of 5 fields on the sign-up form. The number is fictional; the point is that there must be a clear cap: name, phone number, party size, whether lunch is needed, and any special requirements — 5 fields, one minute to finish. Why must party size be asked? Because some people sign up for friends too, and whether it is 1 person or 3 decides how many seats and lunches to prepare. Why must lunch be asked? Because lunches are bought per head — too many is waste, too few is shortage. Why must special requirements be asked? Because someone uses a wheelchair, or is allergic to sawdust, and the organiser has to know that in advance, not discover it at the venue.
Every other field moves to after sign-up. Age, occupation, how they heard about the event — those are things the organiser wants for the retrospective, not things the event needs, so ask them in the feedback form after the event. Allergies and emergency contacts are for on-site safety, but not every event needs them: a woodworking class does, an online talk does not. And when they are needed, ask after the user has confirmed they are coming, not at the moment of signing up. The fewer the fields, the higher the sign-up completion rate; the higher the completion rate, the larger the base for reminders and confirmation later.
One more thing that is easy to miss: right after signing up, the page must tell users "You are signed up" and give them three things at once — a one-line summary of the time and place, an "Add to calendar" button, and a "Cancel sign-up" link. Do not show only "Sign-up successful" and nothing else: users close the page after signing up, and a week later they have long forgotten where they are supposed to go on Saturday. The sign-up success page is the first stop of the reminder pipeline — if it does not give users everything, the next three stops all have to make up for it.
4. Seats and the waitlist: what happens after it fills up matters more than what happens before
120 seats, 200 sign-ups — what happens to the extra 80 people? The easiest option is to show "Full" and turn 80 people away. Easy, but wasteful: of the 200, only 96 showed up in the end, and the 24 empty seats could have gone to waitlisted people. The rule for seats and waitlists is: full is not the end — it is where the waitlist begins. After it fills up, the sign-up button should not disappear; it should become "Join the waitlist". The waitlist must publish its queuing rule — first come, first served, in sign-up order — with no hidden "internal priority".
The fictional example numbers in this guide are: 200 sign-ups, 120 regular seats, 80 on the waitlist; during the week before the event, 20 regular seats opened up through cancellations, 18 waitlisted people were promoted, and the remaining 2 seats only opened up within 24 hours of the event, too late to hand to anyone. These numbers are fictional; the point is that "promote early": the earlier a cancellation happens, the more a promotion is worth — a seat freed 3 days before the event gives the waitlisted person time to rearrange plans; a seat freed 24 hours before is useless even if offered, because there is no time to get there. So set the cancellation deadline at 24 hours before the event: cancellations before that point immediately promote the first person on the waitlist; cancellations after that point forfeit the seat without promotion — not because the organiser is ungenerous, but because promoting it would be pointless anyway.
Promotion messages need rules too. First, send them immediately: the moment a seat opens up, message the first person on the waitlist — do not save them up and send them in the evening batch. Saving them up leaves the seat empty while waiting, wasting all that time. Second, give a reply deadline: the fictional example number in this guide is 12 hours to reply "coming" or "not coming" after receiving a promotion message; no reply within 12 hours, and the seat automatically goes to the next person. The number is fictional; the point is that there must be a deadline: without one, a seat sits stuck in one person's hands while everyone behind them waits on that one person. Third, do not send the message only once: if there is no reply after 6 hours, send one reminder — the lesson from A-Jiao's event in the opening story is exactly this: the promotion message went out at 1 a.m., users saw it in the morning, and it was already too late. Promotion messages should go out while users are awake; a message sent at midnight is the same as a message never sent.
One more set of seats should be held back separately: do not release all 120 seats to sign-ups. Hold 10 seats for walk-ins — people passing by who see the event and want to come in; hold 5 seats for staff and volunteers. Release everything, and walk-ins get turned away at the door while the organiser watches empty seats and people outside at the same time. If the held-back seats are still unused when the event starts, release them to the waitlist and walk-ins 15 minutes after the start — do not leave them empty forever.
5. Reminders and confirmation: two rounds of reminders plus one confirmation — do not make users rely on memory to show up
Users sign up, and a week later it is another story: they may have long forgotten there is an event on Saturday. Reminders solve "don't forget"; confirmation solves "are you actually coming". Do not mix the two up: a reminder is a one-way message from the organiser, while confirmation is an interaction that needs the user to answer. Send reminders without confirmation, and the organiser has no idea how many people will come until the doors open; ask for confirmation without reminders, and users have forgotten which day the event is — what would they confirm?
Send two rounds of reminders. The first goes out 3 days before the event: time, place, and what to bring, plus an "Add to calendar" button. The second goes out 3 hours before the event, and says only two things — "Today 9:30, second floor of Street Corner Workshop, don't forget your water bottle" — plus a "Confirm I'm coming" or "Can't make it" button. The two timings are the fictional example rule in this guide; the point is "one early, one late": the 3-day reminder leaves users time to rearrange plans, and the 3-hour reminder gives them a push to leave the house. Do not send too many reminders: the sign-up confirmation counts as one round, plus these two makes three in total, and that is enough. A fourth or fifth reminder only annoys users; annoyed users turn notifications off, and next time they will not even receive the first round.
Put confirmation inside the second reminder: the 3-hour message carries two buttons — "Confirm I'm coming" and "Can't make it". Tapping "Confirm I'm coming" changes the user's status to "Confirmed", and the organiser prepares lunches and tools based on the confirmed count; tapping "Can't make it" releases the seat to the waitlist at once — a seat released 3 hours before the event will not reach a waitlisted person in time, but the held-back walk-in seats can take a few more people. The fictional example numbers in this guide are: 118 people confirmed they would come, 96 showed up, a confirmed-to-arrived conversion of 81%. These numbers are fictional; the point is that "the confirmation list is the most reliable attendance forecast": prepare the venue and lunches based on the confirmed count plus a 10% margin, not on the sign-up count.
Reminder channels should be separated too: at sign-up, let users pick their most-used channel — text message, in-app message, or email — pick one, and do not blast all three at once. If users picked text messages, send only text messages; if they picked in-app messages, send only those. Sending the same reminder through three channels at once does not make users think "how thorough" — it makes them think "why again". Once a channel is chosen, do not switch it on your own: users picked text messages, and the organiser should not switch to in-app messages because "texts cost money" — if users turned off in-app notifications, that reminder will never reach them.
6. Door check-in: 8 seconds per person, and no queue stretching out the door
Users have finally arrived, and the last hurdle is check-in at the door. Slow check-in means a queue out the door, and users' first impression is "this event is a mess"; fast check-in means users sit down, and the event starts on time. The fictional example number in this guide is an average of 8 seconds to check one person in. The number is fictional; the point is that "check-in must be fast enough that users never feel they are queuing": 120 arrivals at 8 seconds each, with two check-in desks running at once, and everyone is inside in 8 minutes; one desk at 30 seconds each, and 120 people queue for an hour — the event starts at 9:30, the last group walks in at 10:30, and the first half-hour is wasted.
Check-in does three things only: verify identity, hand over the name badge, and tell users where to sit. The fastest way to verify identity is a QR code: the sign-up success page already contains a check-in QR code, and users show it at the door — one scan, and the screen shows their name and seat number, done in 8 seconds. Do not make users recite a phone number at the door, dig through sign-up records, or wait while staff search a printed list name by name — searching a list takes at least 30 seconds per person, and the queue only grows. Send the QR code early: it is on the sign-up success page, and attached again in the 3-hour reminder, so users show it at the door without searching for it.
Name badges and seats should be prepared in advance too: print badges from the confirmed list — 118 confirmed means 118 badges, not 200 from the sign-up list. Printing 82 extra is waste, and printing too few means handwriting them on the spot. Put the seat number on the badge, so users know where to sit at a glance instead of standing at the door asking "where do I sit". After check-in, one more action: change the user's status from "Confirmed" to "Checked in", and sync it to the organiser's dashboard immediately — A-Jiao is on stage teaching, glances at her phone, and sees "96 checked in", so she knows whether to start now or wait another 10 minutes.
There is one more kind of check-in: "people who show up without signing up". The 10 held-back walk-in seats exist for them. Walk-ins scan a walk-in sign-up code at the door, fill in a name and phone number, and finish signing up and checking in within 30 seconds. Do not make them sign up online first and then come back and queue for check-in — people willing to queue for check-in are not willing to stand at the door filling in a long form. The walk-in form is even shorter than the online one: name and phone number, two fields, and that is enough. Everything else can wait.
7. No-shows and the retrospective: how many came, why the rest did not, and what to do next time
When the event ends, only half the work is done. The other half is the retrospective: 200 signed up, 96 showed up — where did the 104 in between go? Without a retrospective, the next event will again be prepared for 200 and attended by 96. A retrospective looks at three numbers: the attendance rate, the cancellation rate, and the no-show rate. The attendance rate is arrivals divided by sign-ups — in the fictional example, 96 divided by 200, or 48%. The cancellation rate is people who cancelled before the event divided by sign-ups — people who cancelled at least told the organiser, and their seats could go to the waitlist. The no-show rate is the one that hurts most: people who signed up, never cancelled, and never came, divided by sign-ups. Cancelling is polite; no-showing is waste: a cancelled seat can be passed on, a no-show seat can only sit empty.
No-shows should be handled case by case, not with one blunt rule. After the first no-show, send a light reminder: "We missed you yesterday. You can cancel for free up to 24 hours before the next event, and a cancelled seat can go to someone else." After the second, remind them again and state the rule: "After 2 consecutive no-shows, your next sign-up goes to the waitlist." After the third, enforce it: the next sign-up goes to the waitlist automatically, and regular seats go to others first. The fictional example number in this guide is that 2 consecutive no-shows trigger the waitlist rule. The number is fictional; the point is that "the rule must be written down in advance and enforced consistently": it is on the event page, so users know it when they sign up; and enforcement must not depend on who it is — letting regulars off after three no-shows while sending newcomers to the waitlist after one kills the rule.
A retrospective should also ask the people who did not come why they did not. On the day the event ends, send them a feedback form: three options plus one blank field — "Something came up", "Forgot", "Too far away", "Other reason" — plus "What time would work better for you next time". Keep feedback short: three options to tap and submit, the blank field optional. The fictional example numbers in this guide are: of the 104 people who did not come, 41 replied — 18 said "something came up", 11 said "forgot", 7 said "too far away", and 5 wrote other reasons. These numbers are fictional; the point is that "some of the people who did not come are willing to tell you why" — the 11 who "forgot" can be won back with one more round of reminders next time; the 7 who found it "too far away" can be won back with a venue closer to a subway stop. A retrospective is not about blaming anyone; it is about losing fewer people next time.
The last job in a retrospective is the money: venue, lunches, tools, name badges — how much did it all cost; 96 arrivals — how much per person; for paid events, how much was collected and whether it covered the cost. Do the sums per person: lunches prepared for 200 but eaten by 96 means the cost of 104 uneaten lunches is waste; preparing for the confirmed count plus 10% next time cuts that waste in half. Write the results in the retrospective document, and read it before organising the next event — running an event without reading the last retrospective is paying the same tuition twice.
8. Pre-launch checklist
Tick every item on this list before shipping event sign-ups and attendance. First, the event page states all six facts: time, place, content, cost, duration, and what to bring, all at once; seat numbers are real — when full, it says "Full — join the waitlist"; next to the sign-up button it states "Free cancellation up to 24 hours before the event". Second, the sign-up form has at most 5 fields (fictional example number): name, phone number, party size, whether lunch is needed, and any special requirements; other fields move to after sign-up or to post-event feedback; the sign-up success page gives the time-and-place summary, an "Add to calendar" button, and a "Cancel sign-up" link all at once. Third, the seats-and-waitlist rules are in place: after filling up, the sign-up button becomes "Join the waitlist", queued in sign-up order; cancellations stop being promoted 24 hours before the event; promotion messages go out immediately, need a reply within 12 hours (fictional example number), and get one reminder after 6 hours without a reply (fictional example number); hold 10 walk-in seats and 5 staff seats, and release unused ones to the waitlist and walk-ins 15 minutes after the start. Fourth, two rounds of reminders plus one confirmation: 3 days before, send time, place, and what to bring; 3 hours before, send "Today 9:30, don't forget" with "Confirm I'm coming" and "Can't make it" buttons; the sign-up confirmation plus two reminders makes three rounds in total — no fourth round; one reminder channel per user, never all three at once. Fifth, door check-in takes 8 seconds per person (fictional example number): the QR code is on the sign-up success page and in the 3-hour reminder; badges are printed from the confirmed list with seat numbers on them; check-in status syncs to the organiser's dashboard immediately; walk-ins scan a code and fill in two fields, done in 30 seconds. Sixth, no-shows and the retrospective: attendance rate, cancellation rate, and no-show rate are calculated after every event; after 2 consecutive no-shows the next sign-up goes to the waitlist (fictional example number), the rule is on the event page and enforced consistently; on the day the event ends, people who did not come get a three-option-plus-one-blank feedback form; venue, lunch, tool, and badge costs are calculated per person and written in the retrospective document.
Six pitfalls, once more. First, do not treat the sign-up count as the attendance count: 200 sign-ups, 96 arrivals (fictional example numbers) — prepare for the confirmed count plus 10%. Second, do not turn the sign-up form into a census: at the moment of signing up, ask only what must be known; the rest can wait. Third, do not turn people away once it is full: the waitlist is a second sign-up form, and promotion messages must go out immediately with a reply deadline. Fourth, do not send reminders without confirmation: the confirmation list is the most reliable attendance forecast, and without it you will not know how many people are coming until the doors open. Fifth, do not let the check-in queue stretch out the door: QR codes at 8 seconds per person (fictional example number) — one desk at 30 seconds each means 120 people queue for an hour. Sixth, do not treat the event as finished when it ends: remind the no-shows, ask the absentees why, do the sums per person, and read the retrospective document before the next event.

Back to A-Jiao at the start. For the next Saturday woodworking class, she changed her approach: the event page stated all six facts at once, the sign-up form had only 5 fields, 120 seats filled up and the waitlist opened automatically. Three days before the event she sent one round of reminders, and 3 hours before she sent another, with a "Confirm I'm coming" button inside — 118 people confirmed. On Saturday morning she prepared lunches and tools for 118 people plus 10%, two check-in desks scanned QR codes at 8 seconds per person, the class started on time at 9:30, and 96 people were sitting in the room, 18 of them promoted from the waitlist. On the day the event ended, she sent feedback to the 104 people who did not come, and 41 replied: 18 had something come up, 11 forgot, 7 found it too far away. She wrote "Next time, pick a venue closer to a subway exit, and send one more round of reminders" in the retrospective document. Sign-ups were still 200, arrivals were still 96 — but this time A-Jiao knew before the doors opened how many people were coming, did not buy 104 extra lunches, and the 18 waitlisted people did not make a wasted trip. That is what event sign-ups and attendance do: connect every step between "signed up" and "showed up", so people who want to come can come, people who cannot come say so early, and the organiser knows what to expect before the doors open.
Comments (0)
Related articles
localStorage only stores strings and has no indexes. IndexedDB is a real database in the browser: structured data, far larger capacity, indexes, and transactions. Following MDN's Using IndexedDB, IDBDatabase, and IDBObjectStore: the five-step routine, opening, upgrades, keys, indexes, transactions, add versus put, get, cursors, ranges, and multi-tab upgrades.
You already call functions every day; this guide names what you have been doing. Following MDN's Functions, Arrow function expressions, and Rest parameters: declarations versus expressions, parameters and arguments, default values, rest parameters, spread syntax, return values, arrow function shorthand, the this trap, callbacks, and scope.
One page should stand up on a phone, a tablet, and a computer. This guide follows MDN's Responsive web design, Using media queries, and the viewport meta reference: fluid HTML, the viewport tag, fluid grids and max-width, images that never burst their container, media query syntax, breakpoints set by content, mobile first, responsive type, testing capability instead of width, and a pre-launch checklist.