Add "Permission Requested" Status
I wonder why we don't simply add folks who request permission to the roster as a Permission Requested status instead of the current system. When I have a bunch of permission requests in my email, if I'm not thinking about it, it's very easy to process those requests in the wrong order, starting with the most recent instead of the oldest. If the were on their own section of the roster (such as with the waitlist) and sorted by request time, it would be much easier to go down the list in the right order. It would also address another issue with "Permission Request opening date" since that would just be the registration opening date since requesting permission would be a form of registration.
Also, I usually go from permission request to manually adding folks to the roster. Rarely do I reply to them and tell them to click the box and register. This flow would make it easier to do that since I would just change their status from "Permission Requested" to "Registered" or "Waitlist."
-
Sharing on behalf of Dante Di Tommaso:
Forcing "leader permission" requests, activity-by-activity, only after registration for an activity opens does not work, since activities fill up long before trip leaders are required to and do respond to requests. There are plenty ways to fix this, most of which rely on recognizing that Mountaineers Leaders have a responsibility for inclusivity as well as safety, etc. One way is to allow all members to fairly register on a first-come basis, without favoring members that have some prior relationship with a Leader. Change to "Leader permission granted" flag to "Leader permission not yet explicitly granted". The Leader can then fairly follow up with any suspect registrants.
-
Similar to Add "Applied" as a Registration Status Option, https://feedback.mountaineers.org/forums/273688-general-feedback/suggestions/37158097-add-applied-as-a-registration-status-option-gh29.