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.
Thanks for the feedback! Sorry to see that you are still struggling with the same issue 2+ years later. I am new to Galaxy Digital but noticed immediately that I was unable to add a registration cutoff time. At first I thought I just needed to learn the system but unfortunately that is not the case.
Great. Thanks so much!
You're very welcome!
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!
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!
I would say that it would be best if a date could be specified to allow for each agency to determine what works best for them.
Unless we'd have to manually add a date for each recurring shift, because that would be a lot of work so in that instance I would say being able to choose X days prior would be best. I'm available to chat over the phone if that would be easier to talk out how this process might best work.
Hi - Thanks for asking...we would rather have option to specify a date that the registration is closed for each shift. A bigger issue is the ability of volunteers to check-in and out multiple times for the same "Recurring" and "Custom" shifts. Makes sense that they can do it for "On-going" shifts but not for other types...it causes all sorts of issues for our organization. Anything you can do about limited the ability to check in and out multiple times for these shifts?
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!
Thanks for the details on how you'd like this feature to work Tony! I'll make sure to update our records to add your voice.
All the best,
Can you tell me a little more about how you envision this working? One of the main advantages of recurring shift needs is the time saving aspect of being able to create multiple shifts at once. Are you thinking of setting a registration closed date for each shift, or something else?
For example, say we have 10 shifts, one on every Tuesday for the next 10 weeks. Would you like to be able to say "registration 24 hours before the shift" for every shift in the series?
For custom shifts, this may be as straightforward as setting a registration closed date for each shift, but I doubt anyone would want to set a registration closed date for each shift in a series of 100 recurring shifts. Let me know what you are thinking!
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.