Responding to an Incident While Volunteering

Summary

</aside>

A brief overview of how Kink Between the Lines (KBtL) defines “incidents”
Examples of what would and would not classify as an incident
Detailed overview and step-by-step guide for KBtL Volunteers to flag incidents

What is an Incident?

</aside>

Incidents are anything that occurs out of the ordinary at KBtL (or, rarely, outside of KBtL) that is a problem, requiring staff to deal with it in some way. Incidents can cause harm to or have a detrimental effect on attendees, educators, volunteers, staff, and/or on KBtL’s reputation, safety, or security. An incident can be caused by intentional or unintentional action or inaction by one or more people.

Some Example Incidents Include…

</aside>

An educator didn’t show up to class, or was behaving improperly or inappropriately during their session
Anyone making inappropriate remarks or comments (in text, via voice, etc.)
Someone’s account is hacked and they’re spamming the server
Someone is breaking the rules (such as two people on one screen, if it’s not clear that they’re both registered).
Harassment or threat of assault

Other things could be considered an incident, this is not a complete list.

The Following are NOT Incidents:

</aside>

Political conversations with respectful discourse
Disagreements that are being handled well
A person being triggered from a session (please advise that person to open a CEC ticket on Discord)

Volunteers’ Responsibilities in Incident Flagging

</aside>

As a Volunteer, you’re responsible to help maintain KBtL.

During your volunteer shift, you represent the event, and you will often be the first point of contact should something go wrong.