Many nonprofits mistake a code of conduct for a punishment document. They write it when a conflict erupts, use it to justify removing someone, then shelve it. A code of conduct used this way becomes a tool for power rather than a framework for safety. It generates resentment and doesn't prevent future harm.
A real code of conduct is aspirational and preventative. It articulates what community you're building, what behaviors support that community, and what behaviors undermine it. It establishes how you'll handle violations transparently and fairly. Written well, it should rarely need to be invoked because people understand what the community expects and police their own behavior. When violations occur, a real code provides a process that feels fair to everyone involved, even the person being addressed.
Grounding Your Code in Organizational Values
A code of conduct is not a generic set of rules. It's the translation of your organization's specific values into behavioral expectations. Before writing a code, your organization needs clarity about what it actually values. Different nonprofits will have different codes because they have different missions and values.
An organization focused on racial justice might emphasize anti-racism commitments explicitly. An organization working with trauma survivors might emphasize trauma-informed practices. An open-source technology collective might emphasize meritocracy and horizontal decision-making. These are reflected in different codes with different emphasis and different unacceptable behaviors.
So the first step is not writing a code. It's getting organizational clarity about your core values. What are you fundamentally trying to build? What behaviors move you toward that vision? What behaviors move you away from it? Once leadership has this clarity, the code becomes straightforward: it describes the behaviors that align with your values and the behaviors that contradict them.
This also means no two codes need to be identical. Borrowing from other organizations' codes is fine as a starting point. But your code should be specifically yours, reflecting the particular culture and values you're building.
Behavioral Specificity Matters More Than Tone
"Treat others with respect" is a nice value statement but a useless code provision. Different people define respect entirely differently. What one culture sees as respectful directness, another sees as disrespect. Without specificity, the code becomes a Rorschach test where people see what they expect to see.
Effective codes describe actual behaviors. Instead of "be respectful," they say something like: "Listen without interrupting when someone is speaking. Assume positive intent but address impact. Acknowledge when you've caused harm and commit to doing better." These are specific enough that people know what behavior is being described.
The same principle applies to unacceptable behaviors. "Harassment" is too broad and too vague. Specific is better: "Unwelcome comments about someone's body, appearance, or sexual orientation. Repeated contact with someone after they've said they don't want it. Comments or behavior designed to intimidate someone into silence." These are specific enough that people can evaluate whether their behavior fits the description.
Specificity also prevents selective enforcement. If the code just says "be respectful," anyone can accuse anyone else of disrespect, and enforcement becomes subjective and political. If the code specifies exact behaviors, enforcement is more objective and harder to weaponize.
Building an Enforcement Structure That's Fair
The most important part of a code of conduct is not the code itself. It's the enforcement structure. A well-written code with no enforcement process is just words. A basic code with fair, consistent enforcement prevents most violations.
Enforcement needs multiple entry points. Some organizations appoint a specific person to receive reports. Some establish a committee. Some allow reports through multiple channels (in-person, email, anonymous form). The key is making reporting accessible. If the only way to report is to directly confront the person, most violations go unreported. You need alternatives.
Enforcement also needs clear process. When someone reports a violation, what happens? Typically: the report is documented, the person accused is informed and given a chance to respond, there's some form of investigation or fact-finding, and a decision is made about what happens next. The whole process should probably take 2-4 weeks. Faster than that risks not hearing all perspectives; slower than that feels like the violation is being ignored. Confidentiality matters — keep details limited to people who need to know — but the accused should always know who reported them and what behavior is being addressed.
Consequences should be graduated. A first-time minor violation might generate conversation and education. A serious first violation or repeated minor violations might generate a written warning and agreement to change behavior. Serious violations (assault, hate speech, abuse) might result in removal. The code should specify which violations fall into which category, though some judgment call is inevitable.
Build in appeals. If someone is penalized and believes the decision was unfair, they should have a process to challenge it. This appeals process doesn't need to overturn decisions frequently. The existence of an appeals process just makes people believe the initial decision was made fairly.
Accounting for Power Dynamics in Enforcement
A code of conduct applied to everyone identically can actually reinforce power imbalances. Consider: a staff member and a volunteer both interrupt repeatedly. Applied equally, both get the same conversation. But the staff member has organizational power; the volunteer doesn't. Treating them identically ignores that the staff member's repeated interruption is more serious because it comes from someone with authority.
Good codes account for power explicitly. The same violation committed by someone in power is treated more seriously than the same violation committed by someone without power. This isn't punishing people in power unfairly. It's recognizing that their violation has more impact because of the authority they hold.
Similarly, marginalized people in your community might perceive and experience violations differently. Comments that feel minor to someone in the majority culture might feel like a pattern of exclusion to someone from a marginalized group. Good enforcement processes take this into account without requiring every accusation to be immediately believed. The goal is to understand the impact, not just evaluate the individual behavior in isolation.
Creating a Code Through Inclusive Process
A code imposed from above, even a good code, generates resentment. People follow codes they helped create. So the process matters as much as the document.
Start by convening a small diverse group (different genders, races, abilities, ages, positions in the organization). This group shouldn't try to write the final code. They should first generate values: what does our organization stand for? What do we want our community to feel like? What violations have happened or could happen here? This values conversation grounds the code in actual organizational reality rather than abstract ideals.
From that values conversation, you can draft provisions. The group might propose something like: "We don't tolerate exclusion based on identity. We actively work to make space for people from marginalized backgrounds. If someone experiences exclusion, we take it seriously and investigate."
Then the process gets wider. Share the draft with the full organization or community. Get feedback. Revise. Share again. By the time the code is finalized, people have seen it multiple times and feel some ownership over it. They know it reflects community input, not just leadership preferences.
Board approval matters symbolically but doesn't require board drafting. The board should review and approve a code that the community/staff has developed, signaling organizational commitment and making enforcement an organizational responsibility, not a volunteer project.
Living With Your Code
Once adopted, a code of conduct needs active maintenance. Include it in staff onboarding. Reference it in conflict situations. Review it annually with community input. Ask: is this still reflecting our values? Are we enforcing it consistently? Are people understanding it? Has anything changed in the organization that means the code should evolve?
A code is not static. As your organization grows or changes, the code may need revision. The process for revising should be similar to the process for creating: inclusive, transparent, grounded in actual organizational experience.
For related guidance on distinguishing codes of conduct from community guidelines and terms of service, see Lecture 1.5.2. For writing specifically inclusive codes, see Lecture 1.5.3.