Code of Conduct Generator
Answer a few questions about your community, where the rules apply, how people can report problems and what the consequences are. You get a complete, plain-language code of conduct as Markdown, text or HTML, ready to publish or drop into your repository as CODE_OF_CONDUCT.md.
Last updated:
e.g. the organizers, the maintainers, the conduct team
How to use the Code of Conduct Generator
- Name your community and pick its type: open source project, online community, event, meetup or club.
- Choose where the code applies, for example online channels, events and private messages.
- Set up reporting: who handles reports, a contact email or form, and how fast you will respond.
- Pick the consequences and whether people can appeal a decision.
- Copy or download the result and publish it where everyone can find it.
What each part of a code of conduct does
| Section | Why it matters | Tip |
|---|---|---|
| Commitment | Says who the community is for and sets the tone | Keep it short and specific to your group |
| Where it applies | Avoids "it happened in DMs, so it doesn't count" | Include private messages and events if people meet there |
| Expected behavior | Gives people positive examples to follow | Write in the second person: "be", "give", "use" |
| Unacceptable behavior | Removes doubt about clear-cut cases | Say the list is not complete |
| Reporting | Without a working contact the code cannot be enforced | Use an address several moderators can read |
| Handling reports | Builds trust: confidentiality, timing, no retaliation | Promise a response time you can keep |
| Consequences | Makes decisions predictable and fair | Allow severe cases to skip steps |
| Appeals | Gives a route to fix mistakes | Have someone uninvolved review appeals |
Where to publish it
- Open source:
CODE_OF_CONDUCT.mdin the repository, plus a link from README and CONTRIBUTING. - Discord, Slack or forums: a read-only rules channel or pinned post, linked in the welcome message and in onboarding questions.
- Events and conferences: the event website, the ticket or registration page (with a checkbox to agree), the printed program and signs at the venue and registration desk.
- Meetups and clubs: the group page, the sign-up form, and a quick mention when each meeting starts.
Making it work in practice
- Name real people. List at least two contacts, and make sure each one knows how to take a report.
- Keep a private log. Record date, what happened, who handled it and the outcome. Patterns are easier to spot.
- Act consistently. Apply the same steps whether the person is new or well known.
- Follow up. Tell the reporter what was done when you can, and check on them later.
- Review yearly. Update contacts, the response time and anything you learned from past reports.
Frequently asked questions
What should a code of conduct include?
A useful code of conduct states who and where it applies to, the behavior you expect, examples of behavior that is not allowed, how to report a problem (with a real contact), how reports are handled and kept confidential, and what the consequences can be. Without a reporting method and someone to act on reports, a code of conduct is only a statement of values.
Where should I put a code of conduct for an open source project?
Save it as CODE_OF_CONDUCT.md in the root of the repository, or in a docs or .github folder. GitHub and GitLab recognize that file name, show it in the repository's community profile and link it for contributors. Mention it in your README and CONTRIBUTING file too.
Do I need a code of conduct for a small Discord server or meetup?
Even small groups benefit from one. It tells newcomers what to expect, gives moderators a fair basis for decisions and shows people who are often targeted by harassment that they will be taken seriously. A short, clear code that you actually enforce is better than a long one nobody reads.
Who should handle code of conduct reports?
Ideally two or more trusted people, so someone is always available and nobody handles a report about themselves or a close friend. Make sure they check the reporting inbox, agree on how to record reports privately and know when to involve venue security or local authorities.
What is an enforcement ladder?
An enforcement ladder lists escalating responses, for example a private correction, then a formal warning, then a temporary ban and finally a permanent ban. It makes decisions more consistent and predictable, while still allowing the team to skip straight to a ban for serious behavior such as threats.
Is this code of conduct legally binding?
A code of conduct is a community policy, not a contract or legal advice. It does not replace laws, venue rules or emergency services. For events with paid tickets, employees or minors, have the final text reviewed against your organization's other policies and local requirements.
Can I edit the generated text?
Yes. The text is generated fresh from your answers in plain language, so you can copy it and adjust the wording, add rules specific to your community, or translate it. Keep the reporting details and enforcement steps accurate whenever you edit it.
Are all the tools on FreeToolCabin tested for quality and accuracy?
Yes! Every tool on our site undergoes automated Q/A testing in real browser environments to ensure high precision, correct output, and zero errors. If you happen to spot a bug or have a suggestion, please contact us at [email protected] and our team will review it right away.