Someone in your community violates the code of conduct. They post hateful content, harass another member, or repeatedly go off-topic. Your instinct might be immediate removal — ban them, problem solved. But enforcement without process breeds resentment and damages community trust. People will think: "If it happened to them, could it happen to me?" Effective enforcement is transparent, graduated, documented, and fair. This lecture provides the framework.
Before Violations Happen: Clear Codes
You can't enforce a code that doesn't exist or is vague. Before your first enforcement issue, write a clear code of conduct.
What a Code Should Include
Values: What behavior you're trying to cultivate. "We value respect, inclusion, and good faith." These set tone.
Specific prohibitions: Not just "be nice." Be specific: "Harassment includes repeated unwanted contact, personal attacks, and targeting based on identity." Specific means people know what crosses the line.
Context nuance: Not every violation is the same. A first-time misunderstanding is different from intentional harassment. Your code can acknowledge this: "We welcome disagreement. We don't welcome personal attacks."
Enforcement process: How will violations be handled? What are steps? What's the appeals process?
Examples: "Harassment includes: repeated @ mentions with aggressive intent, gendered slurs, coordinated attacks on a single member." Examples clarify intent.
Make It Public
Post your code of conduct prominently. New members should see it during onboarding. People can't follow rules they don't know exist.
The Graduated Response Framework
Instead of ban-first, use graduated responses. Most violations can be addressed with conversation. Escalate only when necessary.
Level 1: Private Conversation
Situation: Minor violation, appears unintentional or first offense. Off-topic post. Tone-deaf comment. Accident.
Response: Private message to the member: "Hey, we noticed you posted about [X] in [channel]. That's a bit off-topic. Here's the better place for it: [channel]. No worries — just helping everyone stay organized!"
Tone: Helpful, not punitive. Assume good intent.
Outcome: Member usually complies and apologizes. No formal record needed (but you're documenting it mentally for pattern detection).
Level 2: Warning with Documentation
Situation: Second offense of the same minor issue OR a single more serious violation (intentional rudeness, mild harassment).
Response: Private message: "We've had to redirect you on this a couple times. I want to flag that our code of conduct says [specific rule]. I see you did [specific behavior]. I'm noting this conversation as a warning. Going forward, we need you to [specific corrected behavior]. We're here to help, but we do need to enforce our community standards."
Documentation: Keep a record. Date, what happened, what you said, member's response.
Outcome: Most members course-correct. If they don't, you have a record for the next level.
Level 3: Temporary Removal
Situation: Pattern of violations despite warnings, OR serious single violation (harassment, hate speech, coordinated abuse).
Response: "We have a code of conduct in our community. Over the past [timeframe], we've had multiple conversations about [specific behaviors]. This is a temporary removal from the community for [specific timeframe, e.g., 7 days]. We'd like to re-engage when [specific condition, e.g., 'you're ready to follow our guidelines']. Here's what needs to change: [list specific behaviors]."
Communication: Be clear about the reason, duration, and what needs to change for reinstatement.
Appeals: They can appeal to staff. Staff reviews the record and makes a final call (the temporary removal holds or is lifted).
Level 4: Permanent Removal
Situation: Repeated violations despite warnings and temporary removals, OR egregious single violations (threatening violence, repeated targeted harassment).
Response: "We've had to address multiple violations of our code of conduct. [Reference specific incidents and previous warnings]. We've determined that this community isn't a good fit and we're permanently removing your membership. You can appeal this decision to [staff contact] within 30 days. The appeal will be reviewed by [specific people]."
Documentation: Extensive. Timeline of violations, warnings, conversations.
Appeals process: Clear path to challenge. Someone other than the person who initiated the ban reviews the appeal.
Documentation and Transparency
What to Record
- Date and time of violation
- Specific behavior (quote the post, describe the action)
- Code provision violated
- Response taken (warning, removal, etc.)
- Member's response (if any)
- Follow-up actions
Keep these in a spreadsheet or enforcement log. Not for public display, but so you can detect patterns and ensure consistency.
When to Be Transparent with the Community
You don't need to announce every warning. But public removals create questions. If you permanently ban someone, a brief public statement ("We had to remove a member for violating our code of conduct") prevents rumors and shows you take enforcement seriously. You don't need to name the person or detail the violation (privacy), but transparency about enforcement signals that rules matter.
Protecting the Accused Member
During investigation, keep details confidential. After enforcement, the member's right to privacy depends on what they did. Someone removed for accidental off-topic posts shouldn't have their name posted. Someone removed for hate speech — the community may need to know for safety.
The Appeals Process
Every enforcement decision should be appealable. This protects against moderator bias.
Who hears appeals: Someone other than the moderator/staff who enforced. Ideally someone respected in the community.
Timeline: They can appeal within 30 days of removal. Staff reviews within 7 days.
Scope: Did the person actually violate the code? Was the response proportional? Were procedures followed correctly?
Possible outcomes: Uphold the decision. Overturn it. Modify it (e.g., 7-day removal becomes 3 days).
Communication: Staff explains the decision in writing. "We reviewed your appeal. We found that [behavior] did violate [provision]. We maintain the [consequence]. If you have further questions, please reply to this email."
Common Enforcement Mistakes
Mistake 1: Inconsistent enforcement. You ban someone for a slur but let someone else's slur slide because they apologized. This breeds resentment. Enforce consistently or explain why context matters.
Mistake 2: Emotion-driven enforcement. Someone annoys you and you ban them. You're angry and overshoot the response. Sleep on major enforcement decisions when possible. Let emotions cool.
Mistake 3: Secret enforcement. You remove someone and don't tell them why. They're confused and angry. Always explain: the violation, the code, the consequence, the appeals process.
Mistake 4: Arbitrary codes. Your code says "be respectful" but doesn't define it. You end up enforcing based on gut feeling instead of principle. Write specific codes.
Mistake 5: One-person enforcement. One staff member makes all decisions. They get burnt out and biased. Distribute enforcement among multiple people. Cross-check decisions.
Handling Difficult Cases
The repeat violator who apologizes every time: Apologies are good, but patterns matter. If someone keeps violating and apologizing, they're not changing. Escalate even if apologies come.
The person who says "I was just joking": Intent doesn't matter as much as impact. "I was joking" doesn't excuse harassment. "Your joke caused harm. We need different behavior going forward."
The conflict between two members: This isn't a code violation issue — it's interpersonal conflict. Don't ban for disagreement. Address the actual problematic behavior (personal attacks, harassment). See Lecture 2.4.3 for conflict resolution frameworks.
What to Do Next
If you don't have a code of conduct, write one this week. Be specific. Make it public. If you have enforcement decisions to make, use the graduated response framework. Start with private conversation. Document everything. If someone appeals, genuinely reconsider. Move to Lecture 2.4.3: Managing Volunteer Conflict for frameworks that go beyond enforcement into genuine conflict resolution and de-escalation.