Community moderation: set clear conduct rules: A report prompts review; it does not guarantee removal.; Read the exchange before deciding; identify the rule breached and whether conduct continues.; Threats or exposure of personal details may need prompt action and safety procedure.
Image: Community Growth Desk

Moderation

Community moderation and conduct

Set community conduct expectations, review reports in context and choose proportionate responses while keeping useful disagreement open.

Moderation Desk · · 6 min read

Community moderation needs clear conduct rules and a way to review reports. Responses should fit the behaviour and the risk.

Members should be able to challenge ideas and business decisions without being personally targeted. Tell them how to report a concern, and make only response commitments the team can meet.

Set expectations before a difficult thread

State what the community is for, what belongs in it and how members should treat one another. Give examples of acceptable criticism and unacceptable personal conduct. “Be respectful” is easier to apply when members know they may challenge an idea but must not insult, threaten or repeatedly pursue the person who raised it.

Explain where reports go and what happens next. A report prompts review; it does not guarantee removal. If staff cannot watch the space at all hours, do not promise immediate review.

Cover recurring boundaries such as promotional posts, sharing another person’s details and account-specific questions. Keep the rules tied to the community’s purpose.

Set conduct expectations before a difficult thread

  • State what the community is for and what belongs in it
  • Give examples of acceptable criticism and unacceptable personal conduct
  • Explain where reports go and what happens next
  • Do not promise immediate review if staff cannot watch the space at all hours
  • Cover recurring boundaries such as promotional posts, sharing another person's details and account-specific questions
  • Keep the rules tied to the community's purpose

Review behaviour in context

Read the relevant exchange before deciding. Identify the words or actions at issue, the rule they may breach and whether the behaviour is continuing. A blunt objection to a proposal may be useful. Repeated personal remarks, unwanted contact or an invitation to target a member calls for a different response.

Do not make the person reporting harm debate the matter in public. Ask privately for missing context when needed, and limit access to reports and notes to those handling them. If several moderators are involved, record the decision and its reason so another moderator can understand it later.

Review a report in context

  1. Read the relevant exchange before deciding
  2. Identify the words or actions at issue
  3. Identify the rule they may breach
  4. Check whether the behaviour is continuing
  5. Ask privately for missing context when needed
  6. Limit access to reports and notes to those handling them
  7. Record the decision and its reason so another moderator can understand it later

Match the action to the problem

A moderator may leave a rule-compliant disagreement open, redirect participants to the question, request an edit, remove a comment or restrict further replies. Choose according to the conduct and risk, not a fixed sequence of warnings. A threat or exposure of personal details may need prompt action and the community’s safety procedure.

Preserve the substantive question where possible. A moderator might remove a personal attack while inviting a revised argument about the decision being discussed.

If the whole thread has become unworkable, pause it where the platform permits and explain what would need to change before discussion resumes. Check the controls available on the chosen service before promising a particular action.

Moderator action options by intervention level

  1. Leave a rule-compliant disagreement openUse when the exchange is robust but within the rules.
  2. Redirect participants to the questionBring discussion back to the decision or issue.
  3. Request an editAsk for a change that removes the conduct issue while preserving the point.
  4. Remove a commentRemove a personal attack or rule-breaking content.
  5. Restrict further repliesLimit further contact where behaviour is continuing.
  6. Pause the threadPause where the platform permits and the whole thread has become unworkable.
  7. Follow the safety procedureAct promptly for a threat or exposure of personal details.

Explain enough, in the right place

A brief public note can clarify a visible removal or set a boundary for an active thread. Keep it about the rule and what participants may discuss next. Explain an individual warning or account restriction privately, without naming a reporter or repeating harmful content.

Give the affected member a reason and a way to request review where the team offers one. Keep that review out of the thread. Moderators should be able to explain the rule applied without publishing private details.

Choose a workable conduct framework

A code of conduct can bring together the community’s standards, member expectations and process for addressing problems. GitHub describes these codes as a way to signal an inclusive environment and set out how to handle problems between community members.

Before adopting or adapting a code, consider whether it reflects the community’s standards and whether the team is willing and able to enforce it. GitHub advises researching codes of conduct designed for open-source projects and following attribution guidance when using another person’s or organisation’s work.

Adopting or adapting a code of conduct

  • Check whether the code reflects the community's standards
  • Check whether the team is willing and able to enforce it
  • Research codes of conduct designed for open-source projects
  • Follow attribution guidance when using another person's or organisation's work

Make reporting and decisions traceable

Set out a reporting route members can actually use, and be clear about who receives a report. Routes depend on the service: GitHub contributors can report disruptive content to GitHub Support, while contributors in organisations that opt into reported content for public repositories can also report comments to repository maintainers.

Explain which route applies in your community rather than implying every platform works the same way.

A report should start a review process, not predetermine the outcome. Use records to identify recurring concerns and assess how the framework is being applied over time.

Align community and platform expectations

Community standards operate alongside the rules of the service hosting the discussion. For example, Reddit expects moderators to uphold Reddit’s Rules and User Agreement, and says moderators and their teams can be held accountable for individual moderator actions.

Make the relationship between your community’s expectations and the platform’s requirements clear to members and moderators. Community rules should not suggest that platform standards can be ignored.

Improve the policy from decisions

Review reports, removals and threads that drew complaints but stayed open. Look for rules moderators interpret differently, unclear reporting routes and interventions that stopped useful discussion. Revise the wording, brief moderators and tell members when a material rule changes.

GitHub describes responding to disruptive behaviour in a fast and fair way as a way to build trust and help contributors feel safe and welcome. Consider whether members can find the standards and reporting route, and whether moderators can explain their decisions consistently.

Where a platform offers a community profile or similar checklist, it can make published standards visible to prospective and existing members.

Improve the policy from decisions

  1. Review reports, removals and threads that drew complaints but stayed open
  2. Look for rules moderators interpret differently
  3. Look for unclear reporting routes
  4. Look for interventions that stopped useful discussion
  5. Revise the wording
  6. Brief moderators
  7. Tell members when a material rule changes

In this guide

  1. Writing rules people can understand and followTurn community expectations into clear rules with useful examples, reporting steps and a practical review exercise.
  2. Distinguishing disagreement from harassmentAssess criticism, personal attacks and repeated targeting in context, with a moderation decision aid and a qualified Australian reporting distinction.
  3. Defining when moderators should intervene publiclyDecide when a thread needs a visible moderator note, when to contact a member privately and how to explain an intervention briefly.

More from Moderation

Moderation

Distinguishing disagreement from harassment

Assess criticism, personal attacks and repeated targeting in context, with a moderation decision aid and a qualified Australian reporting distinction.

Moderation Desk · · 2 min read