Add Registration Closed Date to Ongoing, Custom & Recurring Shifts
This is a common sense addition that would be very beneficial and streamlined for agency managers. I hope the development team agrees!
Option 2 would work best for us as well. Thanks for prioritizing this enhancement. We really need it!
Option 2 would work for us as well.
Any updates on this? It seem that a lot of us feel that this is an essential function for planning for our volunteers.
Bethany, agreed. Was hoping to have a solution by the time I had to create a weeklong event with approx. 50 shifts...
Eli Poulos
Hello everyone! I am happy to see that this thread is so active, and I wanted to let everyone know that we appreciate your feedback, and we hear your concerns.
I believe that I am understanding your ideas clearly, but I want to repeat it back here to make sure I am capturing it all correctly: as a volunteer manager, you all need to be able to solidify your plans for a given shift ahead of time so that you can make the necessary preparations, and the fact that people can sign up last minute can cause issues because it prevents you from doing so.
As with any solution that may involve updating multiple things at once, or establishing a blanket rule, we want to make sure that we implement something like this in a way that is going to be useful to as many of our clients as possible. For this reason, a large part of this thread has been devoted to gathering feedback on how our site managers would like a feature like this to work in an ideal world, so that we can make informed decisions on the best way to build something that has broad implications for creating needs and shifts.
So far, there have been a couple of solutions suggested here:
- An option to set the registration closed date for each individual shift. This makes sense for custom shifts shifts, but could be extremely time-consuming for recurring shifts.
- A blanket rule that applies to all shifts in a need, for example "close registration 2 days out". This would be the most efficient way of setting up a registration close date, but would be a bit less flexible in that you would have the same rule apply to all custom shifts in a a need.
From what I am seeing in this thread, it seems like the second solution (a blanket rule for all shifts) would work well for most people who are requesting this feature, but please let me know if there is anything I am missing about this.
I have made sure to consolidate everyone's feedback about this into a single enhancement request in our list, and will be sure to bring this up in our next enhancement planning meeting. Thank you all for your ideas we strive to make shifts (and all of our other features) as accessible as possible to our clients!
This is something that my organization also needs. I am sad to see that this has been consistently requested for so long. I am hoping by adding my support this will finally get prioritized.
Hello! This CLOSED option would be tremendously helpful to our organization. A simple "closed" option in the drop down menu where we see Active, Pending, and Inactive would be helpful for us.
Thanks for your response, Nina. A blanket "two days before shift" would probably be the easiest and most efficient solution.
The issue with simply Cloning a Need is that someone would still have to edit each need's specific date. Our organization is a food pantry. We distribute food four days a week at the same time each day, thus making the Food Distribution Need a recurring shift.
Please let me know if any further clarification would be helpful. Thank you for your consideration.
-Emily
This is an absolute must-have for our organization. We need to close signups a day in advance so volunteers don't just show up for a shift. It is cumbersome for us to set up multiple Happens On needs on the same day.
Has there been any progress or updates on this?
Nina Rogers
Emily, thanks for the additional clarification! I dug through our enhancement archives and found that someone else has requested this in the past, so I've updated that request with your comments and will bring it back up for discussion in our next enhancement meeting. Thanks!
Nina
Hello,
I would also agree, that having some kind of registration close date for shifts would be very beneficial for our volunteer needs. This way if a shift was not full someone could not register the night or morning before a shift. For what we do, we need to be able to confirm volunteers before a shift as well as assign them a "job" or position" if we have people showing up that we are not prepared for. It puts us in a bad position and does not allow for an easy volunteer experience due to the security protocols we have at the stadium.
Hello,
I am experiencing the same issue. It is not efficient not to be able to effectively communicate with a volunteer that registers the night before the event and can create logistical chaos the day of, no one has time to give them duty details and orientation during the event. The option to establish a cut-off date for recurring shifts would solve this issue.
Thanks for listening:)
Emily Holder
There is no Registration Closed Date option for ongoing, custom or recurring shifts. My agency has a recurring shift, but I need to know at least a week in advance if someone has signed up so that I can find another volunteer if the need is unfilled. I cannot effectively communicate with new volunteers if they sign up on the day of a shift. Communicating with volunteers prior to when they are supposed to volunteer is essential in managing volunteers effectively and ensuring they have the best volunteer experience possible, while also making the best use of my time and my organization's resources.
As it is now, in order to create a need with a Registration Closed Date I will have to create multiple Happens On Needs for the same task that happens at the same time on the same day each week.
If you think this feature would be helpful for your agency, please 'like' this post so that it gets upvoted for the development team to actually consider.
Thank you.
28 people like this idea