A code of conduct is a document that defines expected behavior for people in your community — whether members, volunteers, staff, or participants. It sets expectations, protects people from harm, and gives you tools to address violations.
Many nonprofits skip this because it feels bureaucratic or potentially exclusive. But a good code of conduct actually creates safer, more inclusive spaces. It's a commitment to standards that benefit everyone.
Why a Code of Conduct Matters
1. Safety. Clear expectations reduce harassment, discrimination, and harm. People know what's acceptable and what's not.
2. Legal protection. If you have enforcement procedures in place and someone violates them, you have documentation to defend any actions you take (removing them from events, terminating membership).
3. Inclusivity. A good code of conduct signals you take inclusion seriously. It says: "We don't tolerate discrimination, harassment, or exclusion based on identity."
4. Clarity. Everyone (including staff and leadership) knows what's expected. This prevents "well, I thought that was okay" disagreements.
Code of Conduct Structure
A good code has these sections:
1. Purpose and Values
Start by stating what your organization values and why the code exists. Example:
"Our community is built on respect, inclusion, and safety. This Code of Conduct defines the behavior we expect from all members, volunteers, staff, and guests. We are committed to providing a welcoming environment for people of all backgrounds and identities."
2. Scope
Who does this apply to? Everyone? Just members? Staff and volunteers? Events only or also online?
Example: "This Code applies to all members, volunteers, staff, board members, and guests at our events, programs, and online spaces. Violations may result in removal from events, termination of membership, or employment termination."
3. Expected Behavior
Describe behaviors you want:
- Treat others with respect and dignity
- Listen to understand, not to respond
- Respect others' boundaries and consent
- Acknowledge and work to address power imbalances
- Use people's correct names and pronouns
- Offer and accept feedback gracefully
4. Unacceptable Behavior
Be specific about what's not tolerated:
- Harassment, discrimination, or exclusion based on race, ethnicity, gender identity, sexual orientation, disability, age, religion, or any other identity
- Unwelcome sexual contact or advances; sexual harassment
- Intimidation, threats, or hostile behavior
- Disruptive behavior that prevents others from participating
- Retaliation against someone who reports a violation
- Violation of others' privacy (sharing someone's personal information without consent)
5. Reporting Procedure
Tell people how to report violations. Be specific:
- Who can they report to? (A specific staff member, a committee, email address)
- How will reports be handled? (Confidentiality, investigation timeline, documentation)
- What support is available to the person reporting? (Emotional support, safety planning, etc.)
Example: "If you experience or witness behavior that violates this Code, report it to [name/email] or [alternative reporter]. Reports are treated seriously and investigated promptly. Confidentiality is maintained to the extent possible."
6. Consequences
Be clear about what happens if someone violates the code. This might include:
- Verbal warning and conversation
- Written warning and agreement to change behavior
- Temporary removal from events/programs
- Permanent removal or membership termination
- Referral to law enforcement (if criminal behavior)
Specify that consequences are proportionate to the violation. Minor offenses don't result in immediate removal. Severe violations (violence, sexual assault, hate speech) may.
7. Appeals Process
Give people the right to appeal if they're penalized. This is important for fairness.
Example: "If you believe the decision to enforce this Code against you was unjust, you may appeal in writing to [committee] within 30 days. The appeal will be reviewed and you will receive a written decision."
Common Mistakes to Avoid
1. Too vague. "Be respectful" is meaningless. What does that look like? Be specific.
2. Treating it as purely punitive. A code of conduct should be about creating safety, not just punishment. Include support processes and restorative approaches where possible.
3. Not making it accessible. Write in plain language. Avoid jargon. Translate into languages your community speaks. Make it available in multiple formats (online, print, audio).
4. Enforcement inconsistency. If you let some violations slide but enforce others strictly, you lose credibility. Be consistent.
5. Ignoring power dynamics. A violation by someone in power (staff, board member) should be taken more seriously than the same violation by someone without power. The person with power has more responsibility.
Creating Your Code: A Process
1. Start with values. What does your organization stand for? Write those down first. Your code flows from your values.
2. Gather input. Interview staff, volunteers, and community members. What do they care about? What violations have they witnessed? Use this to shape content.
3. Draft collaboratively. Don't write this in isolation. Involve a diverse group (different races, genders, abilities, backgrounds) in drafting. Homogeneous groups miss important perspectives.
4. Get feedback from community. Share the draft. Get feedback. Revise. Do this at least twice.
5. Board approval. Once community is satisfied, get board approval. This signals organizational commitment.
6. Launch and communicate. Don't just post it on your website. Hold a community meeting explaining it. Make it real, not just a document.
Implementation
Once your code is approved, embed it in your culture. Include it in volunteer orientation, staff onboarding, membership agreements. Reference it regularly. Make enforcement consistent and fair. Review it annually — is it still reflecting your values? Is it working?
For related guidance, see Lecture 1.5.2: Community Guidelines vs. Code of Conduct vs. Terms of Service and Lecture 1.5.3: Inclusive Community Guidelines.