You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ICG Code of Conduct Subcommittee will document action and will protect confidentiality as much as possible (acknowledging that in some cases or depending upon how we have to report on the incident, this may not always be possible).
At Vassar, as an advocate for the Sexual Assault Response Team, I have specific language I share with people who report so that they go into a discussion knowing when I may have to break confidentiality. I think that specificity is helpful in giving those reporting the agency to make decisions about what they are willing to share (and it also makes it clear for us). Below are the parameters we share, as an example in case the CoC subcommittee is interested in adopting such language.
... the only times I would have to share this information would be:
If someone threatened you;
If a weapon was involved;
If there is a minor involved;
If there is a dangerous person on premises; or
If you mention the name of somebody who has already been mentioned to us.
(Language revised to be less student- and campus- specific.)
Thank you for considering!
The text was updated successfully, but these errors were encountered:
Thank you for your patience, @exsilica! The code of conduct subcommittee has talked this over a bit, and we appreciate you raising the importance of adding more specific language. On the other hand, we want the code to be flexible enough to address instances that we might not be able to predict. @sgoldste came up with some possible language:
The ICG Code of Conduct Subcommittee will document action and protect confidentiality as much as possible. However, depending upon the type and severity of the incident, we may not be able to keep confidentiality (such as in cases where a threat was made or a situation that involved violence); the Code of Conduct Subcommittee will determine this on a case-by-case basis.
Does that language sound okay to you, or would you propose any changes to it? After we arrive at some language that sounds good to everyone, I will add it to the agenda of the next steering committee meeting.
Hi @exsilica! Just wanted to see if this language sounds okay to you. If it does, we can propose the change at the next steering committee meeting. If you need a bit more time or want to propose changes, that's okay too.
Hi @MarthaTenney -- my apologies for the lack of response! I was not receiving updates on this issue. I agree with the need for flexibility, as the CoC scope is much larger than that of the example I shared. The proposed language addresses immediate safety concerns and I'd be happy to see that proposed to the steering committee.
Thank you for your response (and sorry for the delay in mine!).
Re: Methods of Accountability:
At Vassar, as an advocate for the Sexual Assault Response Team, I have specific language I share with people who report so that they go into a discussion knowing when I may have to break confidentiality. I think that specificity is helpful in giving those reporting the agency to make decisions about what they are willing to share (and it also makes it clear for us). Below are the parameters we share, as an example in case the CoC subcommittee is interested in adopting such language.
(Language revised to be less student- and campus- specific.)
Thank you for considering!
The text was updated successfully, but these errors were encountered: