Create More Robust Safety Committee Data Analysis SD52/465/466
Currently, participants submit incident reports to the Safety Committee, which then compiles the data and looks for trends in the aggregate (it does a lot more than that as well, but this aspect of its work is onerous). If we connected incident reporting with routes/places and even illustrated on a map, committees could analyze trends and information much more rapidly and wouldn't have to wait for Safety Committee reports. Safety Committee efforts could then be more available for training and prevention work now that the data crunching burden has been reduced. Members and Leaders could then have information about incident "hot spots" available to them in deciding what level of risk they are comfortable with. Data could be filtered by activity, committee, location, type of incident, etc.
Nick Block is investigating a 3rd party platform. When we have details, we can consider building website functionality or integrating the third party.
Mike Courts commented
Below are some draft incident reporting classes/categories we have played around with in the Tacoma Branch Kayaking Club. I think the same thought process could be applied to other activities. From an incident reporting standpoint, I took this concept from my 30 years in Army Aviation. I believe establishing classes or categories of incidents would encourage incident reporting but also help the reading audience understand the severity of the event right off the bat.
Kayak Safety Reporting Classes:
Class A: Loss of Life
Class B: Injury requiring external evacuation/medevac
Incident or equipment damage requiring external evacuation
Class C: Injury not requiring external evacuation but causing internal evacuation
Incident or equipment damage that significantly impacts paddle
Class D: Minor Injury not requiring evacuation
Minor incident or equipment damage that does not impact paddle
Class E: Unintended wet exit requiring self/assisted rescue in a non-training