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.
Personally, a blanket registration close date such as "5 days before shift" would be ideal. So when I set up a recurring shift I just select how many days before the shift date it would need to be unavailable for people to register for.
And to your point about setting a registration close date for custom shifts, you are exactly right, I would not want to go in and edit 100 shifts that are essentially recurring.
Thanks for clarifying, Emily. The more specific we get with requests like this, the better we can request the feature from our developers. I will be sure to add your voice and these specifications to the enhancement request. Please reach out if you have any additional ideas in the meantime!
I had a perfect example this week of why the registration close date for ongoing, custom and recurring shifts is needed.
A new volunteer registered for a need with a shift occurring on 5/15/19 at 11:30am. the volunteer registered at 5:38pm on 5/14/19, after I had left the office for the day. I was out of the office the morning of her shift start and could not respond with instructions on where to park, to wear closed toe shoes, etc. Without that prior communication it could mean a negative experience for the volunteer, and leave staff in a pinch to orient the volunteer in a timely manner if they are not expecting someone. Unfortunately as an agency manager I do not have the ability to craft an automatic reply message in Get Connected to send out when someone registers for a need so it is left up to me to send the details once I receive a notification that someone has signed up. Because I am not watching my email every minute, this means that there is a delay in when I can get critical information to a new volunteer.
Hi Emily, I really appreciate this post, it will definitely help me tell the story of why we should implement this in a future round of enhancements.
With your help, we will keep working to make the volunteer and agency manager experience better and more streamlined.
Thanks for reaching out!
For those of you who would also like this change but are looking for a temporary "solution", I have started pasting the following statement in my Needs Descriptions:
"**YOU MUST REGISTER AT LEAST 3 BUSINESS DAYS IN ADVANCE OF YOUR DESIRED VOLUNTEER SHIFT**"
If you are a Volunteer Manager then you probably realize that this statement will not be read, or if it is read, it will not be applied. I am simply using it as a disclaimer for when people do register for a need last minute and then don't understand why they did not receive confirmation and details from me about their volunteer shift.
Thank you so much for sharing the disclaimer that you are using to try and mitigate some of the issues with last minute responses. We appreciate your voice and will continue to advocate for changes to be made that will work for all of our organizations.
We have made sure that your voice is added to the enhancement request, and our entire team will continue to push for a change to be made. Have a great day!