Many of our leaders want to wait for snow reports or weather forecasts a week or so before an activity before they post the activity, but the current process for centralized review and posting creates a time lag that makes this virtually impossible. Can you train and empower a small group of route-place administrators out in the branches to increase the ability to process these submissions more quickly? Considering the wide range in quality of the 'reviewed' routes-places showing up now, I think that you could set up a group of trained and accountable volunteers who would do at least as well and take their responsibility just as seriously as the staff does. Also, can you offer an option for a leader to put up an activity to an unreviewed route-place with the idea that the route-place wouldn't go into the official database until it had been reviewed?

We've been told that we have to use a generic route-place for an activity going to a particular locale even if that generic route-place is a poor fit to what we plan to do and may turn off potential participants. For example, a route-place may be listed as a scramble or climb and I want to list a hike or backpack there - it will show up in the activity search as a scramble and hikers won't want to do it. Or sometimes a route-place is listed as a hike and I want to do it as a backpack but the route-place description is very specific to a hiking itinerary. Can you allow us to enter separate routes-places to a similar locale for very different activity types, or allow multiple activity-type tags on the route-place? Likewise it might be listed as strenuous but my pace will make the activity moderate; could you possibly display the leader rating for the activity rather than the difficulty rating for the route-place on the search listing for activities?

Incident reporting appears as just an embedded email link in the trip report
when a leader closes an activity. Its output are the emails that appear
from those trip leaders sending the email. That makes it harder for the
Safety Officer to identify and group them in mail. Basic metadata like
which branch this pertains to is not appended in the body. That makes it
hard to determine who is accountable for follow up. It would be really nice
if we could re-institute a form that writes to the DB and generates an email
FROM a single incident reporting address and contains the metadata from the
trip entry. Logging it in the DB will make it easier for audit reporting.

Here's a screenshot of what appears to the trip leader when closing out the
activity. This is pretty easy to miss. IMO, we've taken a big step back in
our tools for incident reporting and the process to gather this business
intelligence with the new website UX.

When submitting a new Route/Place request I’d like an Activity Type for meetings, lectures, and other indoor activities. I just need one so you pick the terminology that serves best. I asked for this before and was rejected because the PC’s understanding for our outing takes precedence over ours. Now I’ve run into the issue again and I reiterate that we have indoor activities, like lectures for our courses and we need a suitable activity type to classify them.

Thankfully, activity type is optional now, so we no longer need to describe a meeting room as an “urban adventure”. But the real need is to get a check box filter on “meeting” or “indoor gathering” or something like that in the Routes/Places search so that we can bring all of them up at once and see what’s available.

I’ve already had two volunteers give up on trying to add needed Route/Places because there wasn’t a suitable activity type. What’s the harm in adding one more for this type of activity and lessening the confusion amongst our volunteers?

Submitting a room reservation for the Seattle Program Center is incredibly time consuming and there is a lot of room for error. For example, the calendar does not show which room is reserved, so you have to click on each event so you can see if the room you want is available. If you're looking for a room in a future month (which is often the case), each time you go back to the calendar, it defaults to the current month, so you then have to scroll again to the date you're looking for and click on the next event to see which room its in. If you forget to click "all events" on the side navigation first, or if you mess up the tag, then you risk submitting a request, thinking it was submitted but later learning that Shauna never received it. Also, all of the date drop-downs are time consuming - can we get rid of past years? The search function for "Seattle Program Center" makes it very difficult to find as well. All of the steps are time consuming, and there are a lot of steps and a lot of room for mistakes. It would be great to make all of this easier.