Incidents and reports

When something goes wrong, it shouldn't drown in an email

In any association with activity, something happens now and then: an injury at practice, an accident on a trip, an episode that has to be handled properly. This kind of thing often ends up as a spoken word to a coach or a single email to the chair, and then it's up to that particular person to remember to do something about it.

Incidents give the association one channel to report injuries, accidents and episodes in the same place. Each report becomes a case with an owner, a status and follow-up, so it doesn't depend on whoever happened to get the message.

One channel to report, that everyone can find

Because reporting happens in the same place every time, members and volunteers know where to go when something has happened. They don't need to consider whether it's the chair, the coach or the treasurer who should be told; they report in one place, and the case ends up in the right place on its own.

That lowers the barrier to speaking up. Small things that would otherwise never be mentioned get written down, and the association gets a real picture of what actually happens, instead of only the cases that grew big enough to reach the board.

Every case follows a fixed process

A report isn't just a message to be read and forgotten. Each case follows a fixed process from report to follow-up, with an owner and a status along the way. You can see what has been dealt with and what is still open, without digging through inboxes.

That gives the association a documented handling of what happens: what was reported, who took care of it, and how the case ended. For a board that has a responsibility for safety and responsible operation, that's the difference between being able to stand behind things and having to guess afterwards.

Sensitive information handled responsibly

A report can contain sensitive information: a person's injury, a conflict, something that shouldn't be left out in the open. So a report isn't visible to everyone. You control who can see a case, so the information is only available to those who need to handle it.

Because the incidents sit in the platform alongside the rest of the association's data, the same access control and data processing apply as for member information. You avoid sensitive cases sitting in private inboxes or message threads where you have no control over who can read along.

A history that makes the association wiser

The reported cases gather over time. You can see patterns you would otherwise miss: that the same type of accident recurs, that a particular place or activity leads to more injuries. That makes it possible to prevent rather than only react once something has already happened.

At the same time, the documentation is there if a case later has to be revisited, in front of an insurer, a federation or simply a new board that needs to understand what has been handled before. The association's memory doesn't hang on one person remembering.