Add "Applied" as a Registration Status Option for Activities
This idea is moving to in progress and shifting from focusing on course applications to leadership permission requests. This plan is for those who apply for leaders permission will be added to the roster as "applied" with a link to their permission request stored in registration notes. This will allow 1) coleaders and mentors to all work together on these requests 2) ensure these requests are organized somewhere for leaders other than just email 3) allow users to keep track of what they have applied for and 4) allow for us to better understand application behavior across the club.
If we find that activity "applied" status is helpful we can see how we can possibly adopt this for courses but given many course applications are external to the website this would be challenging.
Becca Polglase
shared this idea
This idea is moving to in progress and is part of a website iteration in April.
In the meantime, keep up to date with web changes by checking out our technology changelog!
We have expanded our staff and volunteer development capacity and encourage our members and volunteers to continue to provide ideas. It is ideas like this one that help us improve the site for all!
-
Travis Prescott
commented
This would also be useful for regular trips where permission is requested. Often time people request permission outside the website, via messenger or a separate email. This makes it hard to process permission requests fairly. If there were simply an "Applied" status in the roster when permission was requested, then at least I, as the leader, know that someone has requested permission and when they did. It would help me ensure I get back to everyone who requested permission, which I always strive to do.
Today, because it can be so challenging to track, for trips that have a lot of requests (like climbs) I require them to use a Google Form to request permission because it is exportable to a spreadsheet which has the timestamps I need. It would be great if the website did this :)
-
Kristina Ciari Tursi
commented
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 "Permission Requested" Status, https://feedback.mountaineers.org/forums/273688-general-feedback/suggestions/44767612-add-permission-requested-status.
-
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.
-
Travis Prescott
commented
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."