Start with the community’s purpose
Before writing rules, describe why the community exists and what members should be able to do there. A discussion group for beginner creators may need room for basic questions and constructive feedback. A space for sharing finished work may need clearer limits on unsolicited promotion. The purpose helps you decide which expectations matter, rather than borrowing a long list of rules that may not fit.
Open the guidelines with a short welcome and a plain statement of intent. For example: “This is a place to share your work, ask questions, and help others improve.” Then connect the expectations to that intent. Members are more likely to understand a rule about giving useful feedback when they can see how it supports the space they joined.
Describe actions, not just values
Words such as “respectful” and “positive” can set a tone, but people may interpret them differently. Turn each broad value into an action someone can recognize. Instead of only saying “Be kind,” ask members to address ideas without insulting people, give feedback on the work rather than the creator, and leave room for others to disagree. These descriptions give members something they can do.
Include examples for situations likely to come up. If self-promotion is allowed, say where and how often it belongs, or explain that it should be relevant to the conversation rather than dropped into unrelated replies. If members can share screenshots of discussions, clarify whether they should ask permission or remove identifying details first. Examples should illuminate a rule, not attempt to predict every possible case.
Keep the language direct. Short sentences and familiar words make guidelines easier to scan on a phone and easier to recall during a tense exchange. When a rule needs a specialist term, define it. You can be firm without sounding hostile: “Do not post someone else’s private information” is clearer than a vague warning to “use good judgment.”
Explain boundaries and what happens next
Members need to know both how to participate and where the boundaries are. Cover the issues that matter for your space, such as harassment, personal attacks, unwanted messages, repetitive promotion, or sharing private information. Separate firm boundaries from preferences. “Do not target other members with insults” is a rule; “Add context when you share a link” may be a participation norm. That distinction makes the document easier to apply fairly.
Give a simple account of moderation. Tell members how to flag a concern and what kinds of responses moderators may use, such as a reminder, removing a post, limiting participation, or removing an account. You do not need to promise a fixed response in every case. Explaining that context and severity matter gives moderators room to respond appropriately while making the process less mysterious. If there is a way to ask about a decision, say where members can do so without restarting the dispute in a public thread.
Make the guidelines easy to find and use
Even well-written guidelines cannot help if members only encounter them after a problem. Put them where people join, post, and seek help. A brief version near a posting box can remind members of the most relevant expectations, while a fuller version can explain examples and moderation. Use the same terms in both places so they do not appear to be different sets of rules.
Structure the page for quick reading. Group related rules under descriptive labels, put the most important boundaries near the top, and avoid hiding exceptions in dense paragraphs. Invite members to pause before posting with a practical prompt such as, “Would the person you are replying to know what they can do with your feedback?” A useful guideline helps someone make a better choice in the moment, not just understand a decision afterward.
Test the draft and revise it as the community grows
Before publishing, ask a few people unfamiliar with the draft to read it. Can they explain what a constructive reply looks like? Do they know whether they may share their own projects? Can they find out how to report a concern? Their questions may reveal gaps that are easy for a moderator to miss. You can also test the wording against common situations from your own community, without exposing members’ private details.
Treat guidelines as a working document, not a one-time announcement. When the same misunderstanding keeps appearing, first ask whether the wording, placement, or example needs improvement. When you change a rule, explain the change in ordinary language and apply it consistently. Clear guidelines cannot prevent every disagreement, but they can give members and moderators a shared starting point for handling one.
