Member Relations Flow Chart

1
Did the issue happen at a DCS event? Is the perpetrator using DCS membership to stalk, harass, or otherwise mistreat another member? Can the incident be corroborated by eye witnesses or with other evidence? Is the issue characterized by unsafe or offensive behavior, including (but not limited to) intoxication? NO NO YES YES Not a DCS issue. Parties should resolve on their own. YES NO Action: None 1. Ask for evidence. 2. Meet to discuss. 3. Consider: Is this causing an unsafe environment for one or more DCS members? 1. Assign committee members to review incident with both / all involved parties. 2. Meet to review details with committee. 3. Discuss. 4. Vote: Did the incident occur as reported? YES NO 1. Assign committee members to review details of incident with both / all involved parties. 2. Meet to review details with committee. 3. Vote: Was the incident a clear and legitimate threat to the safety or wellbeing of one or more DCS members? Was there a physical conflict (fighting, sexual harassment, etc.) YES NO YES 1. Let offended party know that DCS cannot take action without documented evidence. 2. Log incident and circle back if there are additional complaints and/or evidence against this DCS member. Action: None at this time. NO Have there been other similar confirmed incidents involving this member? YES Action: Remove from membership. Allow to reapply for membership in six months. Action: TBD None Warning Removal YES Have there been other similar confirmed incidents involving this member? Action: Vote on removal of member or alternate course of action. YES NO Action: Issue warning and follow up as needed. Action: TBD by committee Was a DCS rule broken? YES NO Was a member made to feel unsafe? NO Action: Use standard email templates to inform violators of the DCS rules, and point out their infraction. Refer to manual for further details. YES Action: Institute Time Out NO NO

Transcript of Member Relations Flow Chart

Page 1: Member Relations Flow Chart

 Did the issue happen at a DCS event? 

Is the perpetrator using DCS membership to stalk, 

harass, or otherwise mistreat another member? 

Can the incident be 

corroborated by eye witnesses 

or with other evidence?

Is the issue characterized by unsafe or offensive 

behavior, including (but not limited to) intoxication?

NO

NO

YES 

YES

Not a DCS issue. 

Parties should 

resolve on their own.

YES NO

Action: None

1. Ask for evidence. 

2. Meet to discuss. 

3. Consider: Is this 

causing an unsafe 

environment for one 

or more DCS 

members? 

1. Assign committee members to review 

incident with both / all involved parties. 

2. Meet to review details with committee.   

3. Discuss. 

4. Vote: 

Did the incident occur as reported? 

YES  NO

1. Assign committee members to review details of incident with 

both / all involved parties. 

2. Meet to review details with committee.   

3. Vote:  Was the incident a clear and legitimate threat to the 

safety or wellbeing of one or more DCS members? 

Was there a physical 

conflict (fighting, sexual 

harassment, etc.) 

YES 

NOYES

1. Let offended party 

know that DCS 

cannot take action 

without 

documented 

evidence. 

2. Log incident and 

circle back if there 

are additional 

complaints and/or 

evidence against 

this DCS member. 

Action: None  

at this time.

NO

Have there been 

other similar 

confirmed 

incidents involving 

this member? 

YES

Action: 

Remove from 

membership. 

Allow to re‐apply 

for membership 

in six months. 

Action: TBD 

None  Warning 

Removal

YES

Have there been other 

similar confirmed 

incidents involving this 

member? 

Action: 

Vote on removal of member or alternate course of action.YES

NO Action: 

Issue warning and follow up as needed.

Action: TBD 

by committee 

Was a DCS rule broken? 

YES  NO

Was a member made to feel unsafe? 

NO

Action: 

Use standard email templates to inform 

violators of the DCS rules, and point out 

their infraction.  Refer to manual for 

further details.   

YESAction: 

Institute 

Time Out 

NO

NO

owner
Typewritten Text
MRC Flow Chart
owner
Typewritten Text
2016
owner
Typewritten Text