Share your idea...

Improve trip reports SD22

Improve trip reports by allowing date of trip and more photos, rich text, potential for an additional field.

Also want leaders to be able to submit trip reports that are linked to the activity as an official write up but also allow members to write trip reports.

5 votes
Sign in Sign in with The Mountaineers
Signed in as (Sign out)

We’ll send you updates on this idea

Karl Themer shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in Sign in with The Mountaineers
Signed in as (Sign out)
  • Brett Dyson commented  ·   ·  Flag as inappropriate

    the new trip report function is a disaster.
    because a much smaller percentage of leaders write them and as more time goes on, fewer people will use them.
    this needs to be fixed immediately, not later, so trip reports do not become irrelevant.

    1. trip reports need to editable. it was a terrible programming/planning not make all trip reports editable. it is too much to expect volunteer trip leaders to be able to write perfect trip reports. i for one, will not write a trip report until this is fixed.

    2. every time a trip is closed, a trip report should be cued and required. that way trip reports will actually happen.

    3. a proper form should be set up so that important data, such as the date of the trip, is included in each trip report.

    please clean up this mess.

  • Fritz Stugren commented  ·   ·  Flag as inappropriate

    A bigger problem is that a trip report, once added, can't be edited. If I make a spelling mistake how do I fix it?

  • James (Jim) Powell commented  ·   ·  Flag as inappropriate

    I have recently tried to search through trip reports to find information on conditions and found that the current page for trip reports is almost unusable. All trip reports from all activities are lumped together in one list. You are currently forced to open each report to determine what kind of trip it was and when it occurred, and maybe just maybe will it contain the type of information that you are looking for. Also currently trip leaders are not even required to write a trip report when closing a trip this is big missed opportunity for us to collect information about conditions and routes. I have the following recommendations to improve the trip reporting system.

    1. Require that a trip report is written when a leader is closing a trip.
    2. List the date of the trip in the heading of the report, not the date of the report as is currently done.
    3. Create filters for the trip report page, so trips can be found by type; climb, hike, kayak, scramble, etc. And possibly date range.
    4. Create trip report templates so more consistent information can be collected. Such as: conditions, route challenges, ascend, descent and total trip time, weather, items of interest, flora, fauna, snow level. Perhaps these templates can be managed by committee, as needs vary some by trip type.

  • Chris Williams commented  ·   ·  Flag as inappropriate

    Add a faceted search component to the trip reports page so you can filter by activity. If I want to see who has been out most recently, I have to guess at the route place or wade through all the trip reports from activities I'm not looking for.

  • John Ohlson commented  ·   ·  Flag as inappropriate

    Reduce Clutter
    One "trip report" written by Peter Hendrickson for a October 8, 2014 event shows up for every course which has multiple meetings listed in the course page occurring at the Seattle Program Center. For examples, see: AFA Scenarios, Crag Climbing Course, Glacier Climbing Course, Intense Basic Climbing Course. This provides no information to students or others. I realize this is because Seattle PC is considered a destination, but this is confusing to students.

  • Paul Mocha commented  ·   ·  Flag as inappropriate

    As a sea kayak trip leader, and on behalf of many others who have expressed the same need, there is a need for a separate, "official" trip report by and for trip leaders, so that they can plan better. The report should be easily accessed by leaders, with room for ongoing comments by leaders subsequently leading the trip.

Feedback and Knowledge Base