Add Registration Closed Date to Ongoing, Custom & Recurring Shifts
Hi Eli!
This is a helpful tip - I'd like to add a product suggestion to make this task easier/more streamlined. We have some initiatives with 30-50 opportunities attached. It's currently very time consuming to manually change the capacity for each opportunity. My suggestion is that there would be a way to change the capacity in a bulk action - preferably at both the Agency/Program Manager level and Site Manager. Something like "Mark As Full." And of course an action to undo it when a mistake is made. :)
Thank you!
Cristy - National MS Society
Eli Poulos
Hi Adrienne!
I have added your support for this product suggestion to the list, and will make sure to bring it to the team next time we discuss enhancements!
In the meantime, I have been doing some thinking on this, and have a workaround that might be helpful in preventing this situation.
If you want to close registration for a specific shift the day before it is set to happen, one thing I would look into is going into the need, and editing the shift capacity so that there are no open slots left. This will block new volunteers from responding to the need, so you can maintain an accurate headcount from the day before the shift up until it actually happens.
I hope that helps, and thanks as always for writing in!
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:)
Thank you!
Maia Price
Hi, Bethany and Angie,
I appreciate your addition here! I'll make sure to add this support to the documented enhancement.
Best,
Maia Price
Galaxy Digital CX
Bethany, agreed. Was hoping to have a solution by the time I had to create a weeklong event with approx. 50 shifts...
Any updates on this? It seem that a lot of us feel that this is an essential function for planning for our volunteers.
Caitlin Lowe
Hi Stephanie,
Thank you for voicing your support for this enhancement! I've add your feedback to our enhancement board so that our developers can review.
Keep up the great work!
All the best,
Caitlin
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.
Option 2 would work for us as well.
Option 2 would work best for us as well. Thanks for prioritizing this enhancement. We really need it!
Eli Poulos
Thank you for your feedback, Yvonne! This seems to be a solution that most people in this thread like, and I will make sure to bring this up to my team in our next product enhancement meeting to review.
If anyone else has a preference for one option over the other, I'd like to hear your thinking we well.
I hope you all have a great holiday!
I prefer the blanket rule with the ability to set how far in advance all shifts are closed.
Eli Poulos
Hello everyone!
Thank you as always for your feedback. We know that this is an issue for a number of our site managers, and that many of you would like to see a way to close shift/need registration. As I promised in my last post here, I brought the request in front of my team in our enhancement review meeting last week. We recognize that this is important to a lot of you, and I am going to continue to think through the scope of adding this, any technical barriers we might run into, and how this might impact other areas of the software.
I see that Emily and Angie like solution 2 from my last post, and I would like to hear feedback from others who are invested in this to make sure that we are able to deliver the best solution here!
If anyone else has a strong preference on how they would like to see this problem solved, I would encourage you to post which of the two potential solutions that have come up in this forum you like best. The two that have emerged are :
1. 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.
2. 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.
Thanks everyone for engaging with this, I look forward to hearing what you think!
This is my first opportunity that I need to close the registration for and just realized I can't....I stumbled upon this thread and agree that I need a way to make that happen, and option 2 seems to be the best. Thanks for considering this!
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