How to set a date for an offline meetup - planning to gather without revealing real names
What sets scheduling an offline meetup (an in-person gathering of people who know each other online) apart from other gatherings is that participants meet without knowing each other’s real names or workplaces. All they know is each other’s handle and the fact that they follow the same work or share the same hobby. Where people live is also invisible online, so before “who is coming,” the organizer has to decide “how much people are expected to reveal about themselves.” If you start taking attendance while this stays vague, some people will want to answer but cannot, and the turnout will look smaller than the actual interest.
Let people answer under their handles
Asking for real names in the attendance poll costs you twice. Some people hesitate to join, and on top of that, a list of real names stays on a screen anyone can open. For meetups, it is practical to specify in the invitation what to write in the name field. Adding a single line such as “Please write the name you use on social media as is” removes both the confusion over how to write it and the inconsistent spellings.
“I want to go” is not attendance
The headcount estimate for a meetup misses most badly when you count reactions to a public post as attendance. Reacting to a post is an expression of interest, not a promise to show up on that day. If you use it as the basis for how many seats to reserve, you get the accident of half the people not coming. Count interest, attendance, and confirmation as separate stages.
When timing it to an event, put out candidates as tentative
For meetups held around a concert or an exhibition, the date cannot be set until the main event’s schedule is announced. If you wait for the announcement to move, you end up looking for a venue at a time when places are booked up. It is easier to get a venue if you first put out candidates at a rough level such as “sometime in this period,” and then narrow to 1 date after the announcement.
- Put out candidates by the week first. Even at the level of “the Saturday and Sunday of the event week,” people can answer whether they can come
- Hold the venue with a tentative booking. Secure it on the assumption you will switch to a confirmed booking once the headcount is set
- Write down in advance what happens if the main event’s schedule moves. Add a line to the invitation such as “If the main event is postponed, the meetup moves by the same amount”
- Also decide whether people who lose the ticket lottery for the main event can still join. If this stays vague, you cannot read the headcount on the day
Decide the place and time based on travel time
You do not know where people you met online live unless you ask. If you assume participants are spread across the country, what drives the schedule is not the date but “the time people can get home.” Set the end time not by the station nearest the venue but by whether people from far away can catch their train home.
- Holding it from midday to early evening widens the day-trip range. If you start at night, coming from far away goes hand in hand with deciding whether to stay overnight
- State the end time clearly in the invitation. When a gathering has no visible end, people from far away drop out first
- Take sign-ups for any extension separately, as an after-party. If you close the main part on time, people leaving will not feel awkward
- Choose a venue near a major station. Some participants carry a lot of bags, so fewer transfers translate directly into easier attendance
Where to post the attendance poll URL
An attendance poll URL can be opened by anyone, and in exchange anyone can answer it. For meetups, the choice of where you share it is itself your safety measure. If you post it publicly, not only do answers from unrelated people get mixed in, but the list of participants becomes readable by anyone.
- In public spaces, post only the announcement. Stop at the date, the purpose, and a note asking people who want to join to get in touch
- Share the URL in private exchanges or closed spaces. Keep it within a range where the organizer knows who received it
- Add a line asking people not to repost it. You cannot enforce it, but just writing it reduces actual reposting
- Close answers once the deadline passes. If you leave it open, the organizer cannot catch answers added later
Confine where real names appear to one place
When real names leak from a gathering meant to be anonymous, it usually happens outside the scheduling itself: in booking and payment. A restaurant booking has to be made under a representative’s name, and a prepaid bank transfer shows the account holder’s name to the recipient. If the organizer plans ahead, the only place real names appear can be confined to the organizer alone.
- Make the booking under the organizer’s name. There is no need to give participants’ names to the restaurant
- Make paying the fee on the day the default. Asking for advance transfers creates a path where real names travel through account holder names
- If people pay by money transfer app, ask them to check their display name. The app’s default setting may still show their real name
- Write the maximum fee in the invitation. When the cost is unclear, first-timers are the most likely to drop out
Address the setup that makes last-minute absences likely
Unlike gatherings at work or school, with meetups the relationship continues even if you do not come. Because social pressure against skipping is weak, no-shows are structurally likely. Do not treat it as a matter of attitude; take action on the side of creating reasons to come.
- Hand out small roles. Kicking off introductions, reception, taking photos. People with a role are less likely to vanish at the last minute
- Send only 2 reminders. 2 days before and the morning of. Any more feels like pressure
- If there is a cap, decide the order for moving people up from the waitlist in advance. If you state it is first come, first served, later decisions will not cause disputes
- Make the organizer the single contact for absences. Things that are hard to say in the group turn into unannounced absences on the day
Systematic measures are collected in systems to prevent last-minute cancellations. For gatherings with food and drinks, much of the planning overlaps with techniques for drinking party organizers.
Keep results for next time, not a member list
If you plan to keep holding meetups, it is better to keep only the results rather than collecting participants’ contact details into a list. The place and time, how you offered candidates, the number of days from announcement to deadline, and how many people actually came. With these 4, you can quickly design the next one. Holding a member list keeps the management responsibility with the organizer, but a record of results causes no problems no matter whom you hand it to.
Once candidates are set, create an attendance poll with the PickDay creation form, and share the URL individually with participants to get it running. People answering do not need to register, and they can write their handle as is in the name field.