Staff Procedure For Incident Response

Be sure to have a good understanding of our Code of Conduct, which can be found here: - [Code of Conduct](/2018/about/code-of-conduct/) Also have a good understanding of what is expected from an attendee that wants to report an incident. These guidelines can be found here: - [Attendee Procedure For Reporting Code of Conduct Incidents](/2018/about/code-of-conduct/attendee-procedure/) ### When taking an incident report: 1. Ask the reporter if they want to go to a quiet space 1. Be an active listener and don't use judgement words 1. Ensure the reporter's safety 1. Seek additional emergency resources as needed (consult the volunteer guide) 1. Take down the report and ask any clarifying questions 1. Thank the reporter for reporting the incident 1. Report the incident to the lead incident responders listed below. In case of a conflict of interest, you can individually contact: * Ewa Jodlowska * Python Software Foundation - Director of Operations * <> * Ernest W. Durbin III * PyCon US - Conference Chair * <> ### While gathering information from the reporter: 1. Do not invite them to withdraw the incident report 1. Do not ask for their advice on how to immediately respond to the incident 1. Do not offer them input into the long-term response to the incident 1. Do not promise any particular response, since it may differ from the official response decided by the lead incident responders Try to get as much of the incident in written form by the reporter. If you cannot, transcribe it yourself as it was told to you. The important information to gather include the following: * Current date and time * Date and time of the incident * Location of incident * Description of the incident * Identifying information of the reported person: name, physical appearance, height, clothing, voice accent, identifying badge information such as company name, ribbons, or badge number * Additional circumstances surrounding the incident * Reporter’s name and contact information. If the reporter wants to make an anonymous report, allow them to do so. If responding to the incident would reveal who reported the incident (e.g. a microaggression in one-on-one conversation) ask the reporter if they have safety concerns about this. * Other people involved in or witnesses to the incident and their contact information or description * Do not prompt the reporter for suggestions of how to handle the incident, but record their suggested responses if they offer them Assess whether an immediate response is necessary. This initial response is very important and will set the tone for PyCon. Depending on the severity/details of the incident, please follow these guidelines: * If there is any general threat to attendees or the safety of anyone including conference staff, consult the volunteer guide for emergency and crisis resources. * If everyone is presently physically safe, involve law enforcement or security only at a reporter’s request. * After taking the report, assess whether you need a lead incident responder to immediately respond to the incident. If so, ask the reporter to stay with you and call the lead incident responders. Respond to reporter needs. You can: * Thank the reporter for making the incident report * Reassure them that the incident report will be reviewed by the lead incident responders * Gather their contact information to send a follow-up after the incident is resolved * Offer to get them water * Tell them where the Safety Room is. Offer to escort them if desired. * Ask, "Is there a friend or trusted person who you would like to be with you?" If so, arrange for another incident responder to get this person. * Ask them, "How else can I help?" * Provide them with specific non-emergency or crisis contacts from the volunteer guide if necessary. Once something is reported, the event coordinator, the conference chair, and the lead incident responders should meet. The main objectives of this meeting is to: * Review report documentation to determine what happened * Consult documentation of past incidents for patterns of behavior * Discuss appropriate response(s) to the incident * Assign a person to make those reponse(s) * Determine the follow up actions for any impacted people and/or the reporter * Assign a person to follow up with the impacted people After the staff meeting and discussion, a staff member (preferably the conference chair or event coordinator if available) may choose to communicate with the reported person. When following up with a reported person: * Explain what happened * Focus on the impact of their behavior * Reiterate the Code of Conduct and that their behavior was not appropriate * Give them concrete examples of how they can improve their behavior * Remind them of the consequences of their behavior, or future consequences if the behavior is repeated People who are reported often get upset, defensive, or deny the report. Allow them to give any additional details about the incident. However, remember: * It does not matter if they did not intend to hurt anyoneTheir behavior still impacted attendees negatively * It is not your job to reassure or forgive them * Do not allow the reported person to make an apology to the reporter or impacted person. Often an apology centers the reported person’s feelings and not the person who was impacted. You may accept their apology and offer to pass it on (but you’re not required to if you think it would negatively impact the reporter). What follows are examples of possible responses to an incident report. This list is is not inclusive, and PyCon reserves the right to take any action it deems necessary. Possible responses to an incident include: * Nothing, if the behavior was determined to not be a Code of Conduct violation * A verbal or emailed warning * Requiring that the reported person avoid any interaction with, and physical proximity to, another person for the remainder of the event * Requiring the reported person not attend evening events * Refusal of alcoholic beverage purchases at events * Ending a talk that violates the Code of Conduct early * Not publishing the video or slides of a talk that violated the Code of Conduct * Not allowing a speaker who violated the Code of Conduct to give (further) talks at the event now or in the future * Immediately ending any event volunteer responsibilities and privileges the a person holds * Requiring that a person not volunteer for future events your organization runs (either indefinitely or for a certain time period) * Requiring that a person refund any travel grants and similar they received (this would need to be a condition of the grant at the time of being awarded) * Requiring that a person immediately leave the event and not return * Banning a person from future events (either indefinitely or for a certain time period) * Removing a person from membership of relevant organizations * Publishing an account of the incident and calling for the resignation of a person from their responsibilities (usually pursued by people without formal authority: may be called for if the person is the event leader, or refuses to stand aside from the conflict of interest, or similar, typically event staff have sufficient governing rights over their space that this isn't as useful) If a reported person wants to appeal the decision, notify them that they may contact the Python Software Foundation Board <>. Keep in mind that it is not a good idea to encourage an apology from the reported person. It is very important how we deal with the incident publicly. Our policy is to make sure that everyone aware of the initial incident is also made aware that it is not according to policy and that official action has been taken - while still respecting the privacy of individual attendees. When speaking to individuals (those who are aware of the incident, but were not involved with the incident) about the incident it is a good idea to keep the details out. Depending on the incident, the conference chair or their designate may decide to make one or more public announcements. If necessary, this will be done with a short announcement either during the plenary and/or through other channels. No one other than the conference chair or someone delegated authority from the conference chair should make any announcements. If some attendees were angered by the incident, it is best to apologize to them that the incident occurred to begin with. If there are residual hard feelings, suggest to them to write an email to the conference chair or to the event coordinator listed below. It will be dealt with accordingly. * Ewa Jodlowska * Python Software Foundation - Director of Operations * * Ernest W. Durbin III * PyCon US - Conference Chair * If contact cannot be made via phone or email, please proceed to the staff room. --- This procedure has been adapted from the Ada Initiative’s guide titled "[Conference anti-harassment/Responding to Reports](" and has been updated by [Otter Tech]( [Revision 2f4d980]( of the PyCon Code of Conduct