Freeze changes to RSVPs after deadline
Once a deadline for RSVP has passed, also allow organizers to then freeze all RSVPs at that point in time. Currently members can still change a "yes" to a "no" even after an important deadline has passed, making it difficult to find out who may still owe for fees, etc.
Bernardine
shared this idea
52 comments
-
Berenice
commented
100% agree. Freezing RSVPs when the event starts would help organisers keep track of no-shows - which is particularly important for events where like restaurant and theatre bookings, and sports events like bushwalking, where headcounts are essential.
This feature would also encourage certain participants to take RSVPs more seriously, as they know they'll be counted as a no-show if the don't turn up.
-
Jim
commented
Another terrific idea that should have been implemented a long time ago.
-
Steven Morrisroe
commented
This is so obvious and basic it is a sad sign of the quality and common sense of the people running this site. We, the CUSTOMERS, have been asking for this FOREVER, even longer than "Bernardine shared this idea · Jun 17, 2010". Does anyone do their job at Meetup? Seems like government employee quality work and timeliness.
-
Shoshie
commented
Allowing the system to accept changes after the event deadline undermines the ability of organizers to control acceptable amount of time to RSVP and encourages members not to take responsibility for their own actions. We've been raising this issue to Meetup for years (my personal recollection) and it's time to make this a priority.
-
A top rated Meetup Organizer commented
A last minute RSVP is a NO Show and should be counted as one.
If someone changes their RSVP after I have closed the event they are taking a spot away from someone who could have gone and costing me money for supplies, food and drink that are not needed.
-
Grrrr
commented
I like Monica's idea of allowing people to include a reason for their "No Show" when they switch from "Yes" after the deadline. It would make it easy for organizers to browse down and see who had a legit reason and if there is a pattern.
-
Steven C
commented
I addition... the text should say "No spaces left" once the deadline arrives. Otherwise people say "let me in, there is space left".
By the way, I see no problem with letting people mark themselves "no" after the deadline provided it says "No show" and is tracked as such.
-
Monica
commented
It seems so simple. If the deadline has passed then the only change someone can make to a "yes" RSVP is to "no show." Meetup could even provide a space for the user to include a reason for their no show, noting that the organizer has the ability to change their no show to a "no" upon review. If a group decides to allow no shows then it's no big deal. But I only allow members one free no show, and this would be very helpful to me.
-
Shoshie
commented
I put a reasonable deadline of 2 days ahead of my event so I could grocery shop and prepare for the event. I even posted my "no cancellations" policy on the event page, and I still had last-minute RSVP changes after the deadline. The system also shows the event as having spaces left. We have been asking for this change for some time and hope it will be addressed soon.
-
Neil MacG
commented
I have no way of knowing if somebody changes their RSVP after the deadline as by then I am on my way to the event. I am therefore waiting for them at the venue, thinking that they are simply running late & meaning that others members are inconvenienced. I am often left feeling guilty in case they werre in fact there but I simply missed them. I totally agree therefore that changes should be frozen at the RSVP deadline so that anybody not then attending is a "No Show".
-
Neil MacG
commented
I have no way of knowing if somebody changes their RSVP after the deadline as by then I am on my way to the event. I am therefore waiting for them at the venue, thinking that they are simply running late & meaning that others members are inconvenienced. I am often left feeling guilty in case they werre in fact there but I simply missed them. I totally agree therefore that changes should be frozen at the RSVP deadline so that anybody not then attending is a "No Show".
-
Neil MacG
commented
I have no way of knowing if somebody changes their RSVP after the deadline as by then I am on my way to the event. I am therefore waiting for them at the venue, thinking that they are simply running late & meaning that others members are inconvenienced. I am often left feeling guilty in case they werre in fact there but I simply missed them. I totally agree therefore that changes should be frozen at the RSVP deadline so that anybody not then attending is a "No Show".
-
Becca
commented
We really need RSVP info to be frozen so we can see who changed their RSVP and how it affected the event. Please!
-
Jessica
commented
Please see "159376 is your incident number". Thank you!
-
Jessica
commented
@Meetup: Also assume several of your Use Case scenarios (or Storyboards) are Pre-pay events. Please! (Similar issues, but a few more: direct-pays, maybes, no-show policy, vendor overcharging, etc.) Thanks for listening!!
-
Jessica
commented
@Meetup: Please!
(Add a little in your code's case statement. And the gui.)
@Adam: Yes, I filter. Thank you, yet YMMV and I find there is NO workaround as "cumbersome" for larger events approaches "inhuman".
@Paul: (And I have no printer. NOT killing a tree for all these events.) Where is the checkbox allowing Event Orgs to please choose by default 'no late cancels'='freeze all changes to rsvps after deadline' or 'late cancels'='no show' or 'late cancel'='excused absence', when cancels are past-deadline?!
I've not seen it. Thank you all for the responses! Thank you! -
Adam David Marcus commented
@Paul - You're not getting it. Unless you enable the Email hosts when members RSVP option and then check your email to see when people actually changed their RSVP (or go the low-tech route of printing out the RSVP hours/days/weeks before the event), there's no way to distinguish between someone who changed their RSVP within an excuseable amount of time and someone who changed it at the last minute (like 5 mins before you printed out your "final" RSVP list the night before an event). My suggestion deals w/ the problem for a wide variety of situations and means that @Jessica and others like her don't have to enable the "Email Hosts when members RSVP" box.
@Jessica - You can always create an email filter to automatically move those messages from your inbox and only look at them once after the event is over.
-
Jessica
commented
If members change RSVP to "No" after the deadline, equate it to "No Show", please. Thank you! (OR please give Event Hosts the option to set 'late cancels' to either "No Show" or "Excused Absence".) Thank You!!
-
Jessica
commented
@Adam: Please understand I disable "Email Hosts" on EVERY event, to avoid 150+ YES email per event in the inbox. (The proposed workaround may work for 5-person events, but quickly fails to scale!)
-
Meetup organizers: The cumbersome way to deal w/ this problem is to make sure you check the "Email Event Hosts when members RSVP" box on the Edit your Meetup page. You can also implement the Automatic wait list option to have Meetup automatically give any spots that open up to people on the waitlist. Then, after the event, you can go through your emails to see when people changed their RSVP from "Yes" to "No" and edit the attendance for the event to mark people who dropped out at the last minute as no-shows.
Meetup Developers: If you could just display the date/time each person last changed their RSVP status on the "Edit Attendance" screen (and maybe sort the list by that), that would basically solve this problem. That can't be hard to do, right?
