Moderation Reference Card
Paid community moderation guide — three-tier norm framework, dispute resolution ladder, five rule properties, essential rules, and wrong moderation patterns
This page is a structured reference card for paid Slack community operators who want the moderation framework, resolution ladder, rule properties, essential rules, and wrong patterns in scannable table form. It covers: a three-tier norm framework table (community norms, posting norms, interpersonal norms — example violation, correct response type, wrong response, result of wrong response for each); a four-step dispute resolution ladder table (step, action, when to use, what it includes, percentage of situations resolved); a five-properties-of-enforceable-rules table (property, definition, enforceable example, non-enforceable example, why it fails); a three-essential-rules table (value-before-promotion, DM consent, feedback solicitation — specific requirement, enforcement trigger, wrong alternative, failure mode); and a five-wrong-moderation-patterns table (pattern, what it looks like, why it fails, failure signal, fix). For the strategic reasoning behind the moderation framework — why reactive moderation produces inconsistency, how the three-tier classification prevents mismatched responses, and why the five wrong patterns erode trust among members who were never directly involved in a dispute — see the companion post: Paid community moderation guide: the three-tier norm framework. This card is for the operator who understands the reasoning and needs the framework, ladder, rule properties, and pattern identification in quick-reference form.
TL; DR
Match the response type to the norm tier: community norm violations get private DM only; posting norm violations get public redirection plus private DM; interpersonal norm violations get private DM only. Work the four-step ladder in sequence: private message resolves ~80%, temporary limit for documented repeat patterns, permanent removal only after the ladder is exhausted or for first-offence behaviour immediately harmful to another member. Write rules that are specific, behavioural, consistent, graduated, and operator-modelled. The three rules most paid communities need but don’t have: value-before-promotion (numeric threshold), DM consent (visible in-thread consent required before a pitch DM), and feedback solicitation (critique only when requested). Avoid first-offence banning, no-rules enforcement, legalese standards, public call-outs, and inconsistent-by-tenure application.
Table 1 — Three-tier norm framework
Most paid community moderation problems are not caused by not knowing what to do — they are caused by choosing the wrong response type for the type of norm being violated. A community norm violation handled with public redirection produces different damage than a posting norm violation handled the same way, because the context is different, the audience is different, and the member’s experience of the correction is different. The three-tier framework does one thing: it assigns a correct response type to each norm category so the operator is not making a fresh judgment about communication channel at each moderation instance. The three tiers cover the vast majority of situations in paid Slack communities. Situations that fall outside the three tiers — a member who has found a gap in the written rules, a situation that involves two members simultaneously — follow the same private-first principle that governs all three tiers.
| Norm type | Example violation | Correct response type | Wrong response | Result of wrong response |
|---|---|---|---|---|
| Community norms (cultural expectations: what is valued, how critique is given, relationship to status and self-promotion) |
Member frames their #intros post as a promotion for their product rather than a peer introduction. The member describes what they sell rather than who they are, what they are working on, and what they hope to contribute or learn. | Private DM only. The DM names the specific behaviour (the promotional framing in the intro), explains the community’s expectation for #intros (member situation, goals, what they’re working on), and asks the member to repost in a way that introduces them as a peer. No public correction. No in-thread reply. The private DM is the only channel for a community norm correction. | Public redirection in the intro thread: “Thanks for joining! We keep #intros for member backgrounds — you might want to edit your post to share what you’re working on and what you’re hoping to get from the community.” | The operator has corrected the member’s first public post in front of the entire community. The member feels called out in a space where they were expected to introduce themselves. Churn risk elevates significantly: paid members who are publicly corrected before they have made a second post have a dramatically lower Week-4 retention rate than members who receive the same correction privately. Every other new member who reads the thread learns that the operator will correct them publicly on their first post, which suppresses the marginal posting behaviour that is already the hardest thing to produce from new members. |
| Posting norms (logistical expectations: right channel, right format, right topic for a given post) |
Member posts a specific question about pricing strategy in #tools-and-resources rather than #ask-anything. The post is substantive and well-formed; the problem is purely channel placement, not content or tone. | Public redirection + private DM. One sentence in the channel: “Great topic for #ask-anything — you’ll get more eyes on it there.” Immediately followed by a private DM explaining the channel taxonomy briefly: which topics belong where, why the split exists, and that the operator moved (or would like them to re-post) the question to the right channel. The public redirection is logistically useful to other members. The private DM ensures the member understands the reason and does not feel corrected without explanation. | No response. The operator sees the misplaced post but does not redirect it, treating it as not worth addressing. | The absence of redirection functions as implicit permission. The member repeats the pattern; other new members who see the post with no correction adopt the same behaviour. Channel taxonomy degrades over time as the community learns that the stated organisation is not enforced. The operator faces a larger structural cleanup problem six months later: channels that have accumulated off-topic content are significantly harder to reorganise than channels that were maintained from the start. |
| Interpersonal norms (behavioural expectations between members: DM consent, feedback solicitation, pitch-before-connection sequences) |
Member sends a DM to another member pitching their consulting services without any prior in-thread interaction and without the recipient having indicated any interest or invitation to discuss it privately. | Private DM only. The DM to the pitching member names the specific action (cold pitch DM to [member] without in-thread consent), cites the DM consent rule, establishes that this is the first documented instance, and explains what consent looks like (a public thread reply inviting a DM, a specific request for information that the member has). No public announcement. No in-thread reference. No general reminder message triggered by the event. | Public general announcement in #announcements: “Friendly reminder that DMs should not be used for pitching products or services to other members. Please connect with members in public channels before moving conversations to DM.” | The announcement is clearly triggered by a recent event. Every member who has recently had DM conversations with other members reviews their own behaviour to determine whether the announcement was about them. The member who sent the pitch DM knows it was about them but receives no private guidance about what they did specifically or what consent looks like, which means the next iteration of the same behaviour (a more indirect pitch, a longer warm-up period before the same ask) is likely. The operator has addressed the pattern publicly without correcting the specific member privately, which is the least effective combination available. |
The DM-first rule is absolute for community norm and interpersonal norm violations. The only exception to public communication is logistical posting norm violations where the redirection is genuinely useful to other members — and even then, the private DM still happens. Operators who create exceptions to the DM-first rule (“this needed to be addressed publicly,” “it’s easier to tell everyone at once”) are optimising for their own comfort rather than the community’s health. The private conversation is harder; it is also the one that produces behaviour change in the specific member without suppressing everyone else.
Table 2 — Four-step dispute resolution ladder
The resolution ladder applies in sequence. Step 1 is not optional even when the violation is clear — the documentation from Step 1 is what gives Step 3 and Step 4 their procedural legitimacy in a paid community where members are paying for access. An operator who skips directly to Step 4 for a severe but first-time violation has no documented process to point to if the removed member disputes the decision. The exception is first-offence behaviour that is immediately and directly harmful to another specific member — behaviour where graduated response is genuinely inappropriate because the severity of the first instance makes a second instance unacceptable. That exception is narrow. Most situations that feel like they require immediate removal actually fit within the ladder if the operator is applying Step 1 well: a private DM that is specific about the severity of the violation and the consequences of repetition is often sufficient to prevent a second occurrence without requiring any further steps.
| Step | Action | When to use | What it includes | Resolves % of situations |
|---|---|---|---|---|
| Step 1 Private message |
Send a private DM to the member who crossed the line. Do not mention it in any public channel. Do not tell the member that other members reported the issue (even if they did). | First response to any norm violation that has not immediately and directly harmed a specific member. This is the universal first step for community norm violations, posting norm violations (in addition to the public redirection), and interpersonal norm violations. It is also the first step for any situation that is ambiguous about which tier it belongs to. | The specific behaviour, quoted or described precisely enough that there is no ambiguity about what the DM refers to. The rule or norm the behaviour conflicts with, cited by name if it is written or described by the cultural standard if it is not. What the operator would like to see instead. The fact that this is the first documented instance. The operator’s expectation that the member can adjust, combined with genuine confidence that they will — the DM is informational, not punitive. No CC to other members, no report to a moderation team, no announcement that a DM was sent. | ~80%. Most members who cross a line in a paid community did not know where the line was. A private DM that is specific, non-punitive, and forward-looking (describing what the correct behaviour looks like) is sufficient to change the behaviour permanently in approximately four out of five situations. The operator who skips Step 1 because the violation seems obvious loses the benefit of this resolution rate and escalates immediately to more severe and costly responses for situations that a DM would have resolved. |
| Step 2 Public redirection |
Post a brief, neutral logistical correction in the channel where the posting norm violation occurred. Always accompanied by a private DM explaining the reason. | Posting norm violations only, where the correction is logistical (wrong channel, wrong format, off-topic for the channel) and genuinely useful to other members. Not applicable to community norm violations or interpersonal norm violations. Public redirection is a tool for channel taxonomy maintenance, not for social correction. | One sentence in the channel, framed as logistical guidance: “Great topic for #channel-name — more eyes there.” Never a social correction in public (“we don’t pitch in this channel”). The private DM follows immediately: brief explanation of the channel taxonomy, why the post belonged elsewhere, and the operator’s expectation that the member will use the right channel going forward. | Not a standalone step. Used in combination with Step 1 for posting norm violations. On its own, the public redirection without a private DM resolves the immediate logistical issue but does not ensure the member understands the reason, which reduces the probability that the behaviour changes on the next post. |
| Step 3 Temporary channel limit |
Apply a specific channel posting restriction to the member for a defined period. Document the limit to the member in a DM. Log the action in the internal moderation record. | After the same behaviour has been documented in two separate Step 1 DMs and the member has repeated the behaviour after the second DM. Step 3 is not applied after one DM unless the violation after the first DM was significantly more severe than the first. The two-DM threshold is the standard minimum for demonstrating that the graduated process was followed. | The specific channels restricted (not a full mute across all channels — only the channels where the pattern occurred). The specific duration: 7 days is the minimum for a first temporary limit; 14 days for a second. A written DM to the member naming the behaviour pattern (quoting both prior DMs), the specific limit applied, the period, and what happens when the limit is lifted. The internal moderation log entry with date, behaviour, prior steps documented, limit duration, and the date the limit expires. | ~15% of situations remaining after Step 1. Most members who did not respond to two private DMs will respond to a documented temporary limit, both because the consequence is concrete and because the documentation signals that the process has a defined endpoint. The small number of members who continue after Step 3 are the cases that reach Step 4. |
| Step 4 Permanent removal |
Remove the member from the workspace. Notify them by DM. Document the decision. Make and communicate the refund decision. | Two categories: (a) after Step 3 has been applied, the limit has been lifted, and the behaviour continues or a new harmful pattern emerges, demonstrating that the graduated process has been exhausted; (b) first-offence behaviour that is immediately and directly harmful to a specific member — behaviour where the severity of the first instance makes a second instance unacceptable and graduated response inappropriate. Category (b) is narrow. Most violations that feel severe enough to justify immediate removal actually fit within the ladder. | A DM to the removed member naming the specific behaviour, the steps that preceded the decision (or the severity rationale for first-offence removal), the fact that the removal is permanent, and the refund decision. An internal moderation log entry with: date, specific behaviour documented, all prior steps and dates applied (or severity rationale for first-offence), refund amount and reason, and the confirmation that the DM was sent. No public announcement of the removal. No discussion of the reason with other members. | Final step. All remaining cases after Step 3 reach Step 4. In paid communities, permanent removal is estimated at 1–3% of the member base annually in well-moderated communities — communities that follow the ladder consistently have lower rates than communities that skip steps or apply no formal process. The documentation from Steps 1–3 is the procedural basis for Step 4’s legitimacy if a removed member disputes the decision. |
Table 3 — Five properties of enforceable rules
Rules that fail the five-property test are not rules — they are statements of values or intentions that have no moderation basis. The most common failure mode for paid community operators is writing rules that feel comprehensive but are grounded in value words (respectful, professional, supportive) that cannot be observed, measured, or consistently applied. A rule that the operator cannot cite to a specific observable action in a Step 1 DM and have the member agree that the action happened is not enforceable. The test for enforceability is simple: could two different operators, reading the rule and observing the same member action, produce the same enforcement decision? If the answer depends on interpretation of intent, the rule fails the test.
| Property | Definition | Enforceable example | Non-enforceable example | Why it fails |
|---|---|---|---|---|
| Specific | The rule names a concrete, observable action — not a value, an internal state, or a general category of behaviour. A specific rule describes something that happened, not something the member intended or how the member made another member feel. | “No unsolicited direct messages about paid products, services, or consulting engagements to other members. Unsolicited means without visible in-thread consent from the recipient in a public channel before the DM is sent.” | “Be respectful of other members’ time and attention.” | “Be respectful” describes an internal state that cannot be observed and therefore cannot be cited in a Step 1 DM. The member who receives a DM citing this rule can always dispute whether their action violated the value: they were being respectful from their perspective. The operator must now argue about interpretation of intent rather than document a specific observable action. Every enforcement action grounded in a value word becomes an argument about meaning rather than an application of a documented standard. |
| Behavioural | The rule describes a specific sequence or category of observable actions. It describes what the member did, not what they intended, how they came across, or how the recipient felt. | “Do not follow a first introduction in a public thread with a private DM mentioning paid products, services, or engagements within 30 days of the introduction. A pitch DM requires that the recipient has indicated explicit interest in the topic in a public thread.” | “Don’t be pushy or aggressive in your interactions with other members.” | “Don’t be pushy” requires the operator to make a judgment about the member’s communication style and intent, both of which the member will dispute in good faith if they did not experience themselves as pushy. The behavioural version describes a specific sequence (cold intro followed by pitch DM within 30 days) that is observable without any judgment about intent: the actions either happened in that sequence or they did not. |
| Consistent | The same rule applies to all members regardless of tenure, contribution history, relationship with the operator, or perceived community status. The rule is enforced the same way when violated by a founding member as when violated by a member who joined last week. | Rules are published in a pinned document, referenced in onboarding, and the Step 1 DM cites the same specific rule text for every member who violates the standard — including members the operator knows personally and members who have contributed significantly to the community. | Tenured or vocal members receive a casual mention in a private conversation; newer members receive a formal Step 1 DM citing the rule, for the same category of behaviour. | Every member in a small paid community observes the operator’s enforcement behaviour, even without appearing to. When inconsistency is noticed — and it always is — the operator’s reputation for fairness is damaged permanently. The most visible consequence is a reduction in direct challenge and critique of established members: newer members learn that tenure produces protection and adjust their participation accordingly. The community gradually converts from a peer network into a social hierarchy, which reduces the contribution density that makes the community worth paying for. |
| Graduated | The rule specifies what happens at each step of the resolution process: first occurrence, second occurrence, temporary limit, and permanent removal. The operator is applying a documented process, not making a unilateral decision at each moderation instance. | “First violation of the value-before-promotion rule: private DM documenting the specific post and the rule. Second violation: private DM referencing the first DM and warning that a third violation triggers a temporary posting limit. Third violation: 14-day posting restriction in #tools-and-resources and #self-promotion with written documentation. Continued pattern after limit: permanent removal.” | “Members who violate community standards may be removed at the administrator’s discretion.” | “May be removed at discretion” preserves the operator’s flexibility to make any enforcement decision at any time, which is counterproductive: the goal is to replace discretionary decisions with a documented process that is applied consistently. Discretionary enforcement means every action is a fresh judgment call, the member never knows where they stand, and the operator has no basis for arguing that the process was fair if a removal is disputed. Graduated documentation also has a practical value: the majority of members who know that a specific step will result in a specific consequence respond to the earlier steps. Operators who communicate consequences clearly have fewer escalations to the later steps. |
| Operator-modelled | The operator’s own visible behaviour in the community demonstrates the standard before it is required of members. The operator does not do things they would moderate other members for doing. | Operator’s own posts follow the value-before-promotion threshold (three non-promotional contributions before any mention of their own paid products). Operator DMs members before correcting them publicly. Operator asks before offering feedback on member projects. Operator’s intro post and channel contributions follow the same framing they expect from new members. | Operator posts promotional announcements for their own services in channels where member self-promotion is restricted (“I just launched a new cohort — check it out” in #tools-and-resources). Operator publicly corrects a member’s post before attempting a private DM. | When the operator does not follow the rules they enforce, enforcement actions feel political. Members observe that the standard applies to some people and not others, even when the written rule nominally applies to everyone. The operator’s own modelling is the most visible and most credible demonstration of what the community’s standards actually are in practice — more credible than any written document, because members infer from observed behaviour rather than written claims. An operator who enforces a value-before-promotion rule but posts their own promotional content is communicating that the rule exists for members, not for the operator. |
Five to eight rules that pass all five property tests are worth more than twenty rules that fail one or more. The goal is not comprehensiveness — it is giving the operator a written basis for consistent enforcement. Every rule that fails the specific or behavioural test produces an argument at enforcement time rather than a documented standard. Operators who feel the need for a long rulebook are usually trying to cover edge cases that would be better handled by a strong DM-first policy and a well-documented resolution ladder.
Table 4 — Three essential rules most paid communities lack
These three rules address the moderation situations that appear most frequently in paid Slack communities and that operators most commonly lack written standards for. They are not a complete rulebook; they are the three gaps most likely to produce repeated Step 1 DMs about the same categories of behaviour in communities that have not written them down. A community with these three rules plus a clear DM-first policy and the four-step ladder covers the majority of paid community moderation situations with a documented framework rather than fresh judgment calls. The wording below is template language — each community’s rules should be adapted to their specific context, member expectations, and the community’s relationship to self-promotion and paid content.
| Rule name | Specific requirement | Enforcement trigger | Wrong alternative | Failure mode of wrong alternative |
|---|---|---|---|---|
| Value-before-promotion | A member must make at least three non-promotional contributions — a substantive reply to another member’s question, a specific question about their own work, or a resource share that is not the member’s own product — before they may mention any paid content, product, service, or consulting engagement they sell, either in a public channel or a direct message to another member. The three-contribution threshold resets on a 90-day rolling basis: a member who has not posted in 90 days must re-establish three non-promotional contributions before their next mention of paid content. | A member’s first or second post in the community mentions their own paid product, service, or consulting offer. Or a member who was previously active but has been absent for 90+ days returns with a promotional mention without re-establishing the contribution threshold. Or a member meets the numeric threshold but all three contributions are shares of their own free content (blog posts, newsletter issues, tools they built) rather than genuine peer contributions. | “No self-promotion in this community.” | “No self-promotion” is ambiguous about when self-promotion has been earned through contribution and about what counts as promotion (is sharing a free resource self-promotion? Is mentioning a side project promotion?). Without a numeric threshold, the rule produces interpretation disputes at every enforcement instance. Members who want to promote interpret the rule generously (“I’ve contributed a lot”); operators who enforce interpret it differently at different times (“that was too soon”). A numeric threshold eliminates the interpretation layer: the count is observable and the standard is the same for every member. |
| DM consent | A member may send a direct message about paid products, services, consulting engagements, or business pitches to another member only after the recipient has indicated visible consent in a public channel — a public reply inviting a DM, an explicit request for information the member has, or participation in a thread where both members have established a relevant mutual interest in discussing the topic privately. A cold DM to a member the sender has not previously interacted with is not permitted regardless of how the DM is framed. | A member sends a pitch DM to another member without prior public interaction that constitutes consent. Or a member follows up a cold interaction in a public thread with a pitch DM within 30 days of the thread, without the recipient having indicated explicit interest in discussing the topic privately. Or a member uses a general channel post (“feel free to DM me if you want to learn more about X”) as a proxy for obtaining consent, which is not equivalent to the recipient indicating consent through a public thread reply. | No explicit DM policy; relying on members to self-moderate based on general “be respectful” rules. | Without a DM consent rule, DM pitches proliferate because members who understand that public channels are not for pitching look for the next available channel. Members who receive unsolicited pitch DMs rarely surface the issue; they cancel citing general dissatisfaction with the community’s culture. The operator never identifies DM proliferation as a churn cause because it is invisible in public channels and members who feel their DMs have been treated as a prospecting environment do not explain this when they cancel. The operator notices only that retention in months 3–5 is lower than expected, with no identifiable cause. |
| Feedback solicitation | Critique, critical analysis, suggestions for improvement, and feedback about another member’s work, decisions, business, or public statements may only be given in response to an explicit request for it in a public channel. A member who has not asked for feedback on their post, their work, or their approach is not a target for unsolicited critique, regardless of how well-intentioned the critique is or how obviously wrong the operator believes the member’s approach to be. A member who wants to give feedback on something not yet publicly requested may ask publicly whether the member wants feedback before offering it. | A member offers specific, critical, or directional feedback on another member’s post, decision, or approach in a channel where the member did not explicitly request feedback. Or a member replies to a thread with a correction of something the original poster said without the original poster having asked whether others agreed or had additional input. The threshold is whether feedback was requested, not whether the feedback is accurate, constructive, or useful. | No specific rule about feedback solicitation; handling it as a moderation judgment call based on “tone” or “intent.” | In practitioner communities where members are accustomed to critiquing each other’s work, unsolicited critique is often the most common interpersonal norm violation — and because the member offering the critique typically believes they are being helpful, they do not experience themselves as crossing any line. Handling it as a judgment call requires the operator to evaluate whether the critique was constructive enough to be acceptable, which the critiquing member will dispute. A written rule removes the judgment layer: feedback was either solicited or it was not, regardless of how helpful the critic believes it was. Members who know the rule exists self-moderate more effectively: they ask before offering rather than offering and having to be corrected after. |
Table 5 — Five wrong moderation patterns
These five patterns are widespread in paid communities and each produces damage that extends beyond the specific member involved. The common thread is that all five treat moderation as a reactive problem-elimination task rather than a trust-maintenance practice. In a paid community where members are paying for access, the operator’s reputation for fairness, consistency, and private-first communication is one of the community’s primary retention assets. Patterns that erode that reputation — especially patterns that do so visibly, in front of other members — affect renewal rates and referral behaviour among members who were never directly involved in a moderation event. See also the companion post on paid community retention strategies for the direct connection between perceived fairness of governance and months-2–3 churn.
| Wrong pattern | What it looks like | Why it fails | Failure signal | Fix |
|---|---|---|---|---|
| First-offence banning | A member’s first rule violation results in immediate permanent removal. The operator justifies it as “protecting the community,” “setting an example,” or “zero tolerance for this type of behaviour.” The removal often follows a violation that provoked a strong emotional response from the operator rather than a violation that was immediately and directly harmful to a specific member. | Most first-time violations are failures of awareness, not failures of intent. A member who does not know the rules cannot follow them; removing that member without a private DM means the operator has never told them what the standard is. First-offence banning produces the maximum outcome (permanent removal) without providing any of the documentation that gives that outcome procedural legitimacy. Every member who observes or hears about a first-offence removal updates their model of the community’s safety accordingly — their own membership now carries a perceived risk of unexpected termination that was not in their model when they joined. | Members begin self-censoring in ways that reduce contribution value: posts become shorter and safer, questions become less specific, challenges to ideas reduce. Referral rate from existing members drops: members who are uncertain whether a single misstep results in removal do not recommend the community to peers who might also violate an unstated rule. New member activation rates may appear unaffected while long-term contribution density quietly falls. | Apply Step 1 first. Even when the violation feels egregious, send the private DM before taking any other action. Document what you sent and when. If the behaviour continues after Step 1, apply the ladder. Reserve first-offence removal exclusively for behaviour that is immediately harmful to a specific other member — the narrow category where graduated response is genuinely inappropriate. Every other situation benefits from at least one documented private DM before escalation. |
| No posted rules | The community has strong cultural expectations and the operator moderates actively, but there is no written moderation standard pinned anywhere in the community. Rules exist in the operator’s head and are communicated through enforcement actions rather than proactively. New members are expected to infer the standards from observing how others behave. | When members encounter moderation without a documented standard, every enforcement action feels arbitrary — even members who agree with the decision may feel the process was unfair because they were not informed of the standard before being held to it. In paid communities specifically, a moderation action that feels arbitrary is a challenge to the member’s investment: they are paying for access to a community that has rules they were not told about. The member’s sense that their membership is conditionally safe on standards they cannot access is a direct driver of churn in months 2–3. | Members ask privately “what are the actual rules?” rather than looking them up. When a moderation action occurs, discussion in private channels or among member subgroups focuses on process fairness rather than the specific violation. New members request clarity about community standards in onboarding-adjacent channels or DMs to other members. The operator notices inconsistency in how new members behave in the first week, without recognising that the inconsistency reflects the absence of a clear signal about expectations. | Write five to eight specific, behavioural rules using the property test from Table 3. Pin them in #start-here. Reference them explicitly in the Day-0 onboarding DM (see onboarding checklist). When issuing a Step 1 DM, cite the specific rule by name and include the rule text. The documentation changes enforcement from a judgment call about the operator’s preferences to an application of a standard the member agreed to when they joined. |
| Legalese rules | Community rules are written as terms-of-service language: “The operator reserves the right to remove any member for any reason at the sole discretion of the administrator. Members agree to abide by all community standards as determined by the operator from time to time.” The rules read as legal protection rather than behavioural guidance. | Members do not read legalese rules and cannot apply them to their own behaviour because the rules contain no specific behavioural standards. Legalese preserves the operator’s maximum flexibility (which is counterproductive — the goal is to replace discretion with documented standards) while providing zero self-moderation value to members. A member who wants to know whether they can share their product in #resources cannot answer that question by reading “all community standards as determined by the operator from time to time.” They ask another member instead, and the answer they get reflects that individual member’s inference rather than a documented standard. | No member has cited the community rules when deciding how to post — because the rules contain no specific guidance about posting decisions. Members ask each other “is it okay to...” rather than reading the rules. Enforcement actions are treated as expressions of operator preference rather than applications of a documented standard. The operator who has legalese rules and an active enforcement practice is perceived as autocratic rather than principled, because the rules provide no visible basis for the enforcement decisions. | Rewrite rules in specific, behavioural language addressed to the member in the second person: “You may mention your paid products or services only after making three non-promotional contributions.” Five to eight rules that a member can check before posting and answer the question “does my planned action fall within the standard?” are worth more than a paragraph of legal coverage that provides flexibility for the operator but zero guidance for the member. |
| Public call-outs | The operator corrects member behaviour in the public channel where it occurred, either by addressing the member directly (“@member, we don’t pitch in this channel”) or by posting a general reminder clearly triggered by a recent event (“Friendly reminder that #tools-and-resources is for resources, not promotions” posted immediately after a promotional post). The operator intends the correction as helpful community maintenance; members experience it as a public call-out. | Public corrections force every member in the channel to witness a moderation event. The member being corrected is humiliated in the space where they were trying to contribute: they posted something and received a public correction as the visible result of that post. Members who observe the correction learn that being corrected publicly is a risk of participation, which suppresses the marginal posting behaviour — the exploratory posts, the uncertain questions, the partially-formed ideas — that generates the community’s most valuable interactions. Public call-outs do not change the behaviour of the member being corrected more effectively than a private DM; they change the behaviour of every member who observes them, and the change is toward less posting. | Members reduce posting frequency after a public correction incident, not only the member who was corrected. Thread responses in channels become shorter and more cautious. DM conversations between members increase as people move discussions to channels where public correction cannot be observed by others. If the pattern continues, the community develops a “safe topics” norm where members only post on subjects where they are highly confident, which narrows the range of discourse and reduces the community’s value to members who joined for diverse practitioner perspectives. | Apply the DM-first rule absolutely. The only acceptable public correction is a logistical posting norm redirection (“great topic for #ask-anything”) that is (a) logistically useful to other members, (b) neutral rather than corrective in tone, and (c) immediately accompanied by a private DM. Social corrections — corrections about how a member behaved toward other members, toward the operator, or toward community standards — are always private first, with no exception for “this needed to be said publicly.” That judgment is almost always the operator optimising for their own need to be seen enforcing the standard rather than the community’s need for the correction to happen in the most effective channel. |
| Inconsistent-by-tenure application | The operator applies rules differently depending on how long the member has been in the community, how much they have contributed, or whether they have a personal relationship with the operator. A founding member who promotes their product in #tools-and-resources receives a casual mention in a private conversation; a member who joined last month receives a formal Step 1 DM citing the value-before-promotion rule for the same action. The difference in treatment is not visible in any written policy but is observable in the community’s enforcement behaviour over time. | Every member in a small paid community monitors the operator’s enforcement behaviour, even without appearing to do so. When inconsistency is noticed — and in a community of practitioners who pay attention to patterns, it is always noticed — the operator’s reputation for fairness is damaged permanently. The most common outcome is not confrontation but adjustment: members update their model of how the community works. New members learn that the rules have an unstated tenure clause. High-contributing members learn that their status provides protection. Both updates are corrosive: the community’s value depends on members believing that the standards apply equally, which is the condition under which members are willing to engage at peer level rather than at status level. | Long-tenured members make the same category of posts that result in Step 1 DMs for newer members, without visible consequence. When a new member receives a moderation action, they ask peers whether the standard is applied consistently and receive mixed answers. High-contributing members begin subtly advocating for their own exceptions (“I think what I’m doing is different because...”) rather than accepting the standard as applying to them. The operator notices that referral behaviour from long-tenured members is lower than expected, without identifying that tenure-based enforcement inconsistency has reduced those members’ confidence in the community’s governance. | Apply the same documented ladder step — the same specific step — to the same category of behaviour regardless of who committed it. Document each enforcement action in an internal moderation log, which creates a reviewable record of consistency. When applying Step 1 to a long-tenured or high-contributing member, acknowledge the relationship explicitly in the DM: “I know you’ve been here from the start and your contributions are a foundational part of what makes this community work — that doesn’t change. But I have to apply the same standard I’d apply to anyone, and that starts with this DM.” The acknowledgement maintains the relationship while demonstrating that the standard applies consistently. See also the member churn by tenure guide for the connection between perceived governance fairness and months-4–6 renewal decisions. |
Frequently asked questions
What is the three-tier norm framework for paid community moderation?
The three-tier framework organises moderation situations by norm type to ensure the response channel matches the situation. Community norms (cultural expectations about what is valued, how critique is given, the relationship to status and self-promotion) are corrected by private DM only — never in public channels, never as general announcements. Posting norms (logistical expectations about right channel, format, or topic) are corrected by public redirection plus a private DM explaining the reason — the public component is logistically useful to other members; the private component ensures the specific member understands why. Interpersonal norms (behavioural expectations between members: DM consent, feedback solicitation, pitch-before-connection sequences) are corrected by private DM only — never as general announcements, even when the announcement does not name the member. Choosing the wrong response type for the norm tier is the most common moderation error in paid communities: a community norm violation corrected in public produces the same damage as a public call-out, even when the operator intended the public correction as logistical rather than social. See Table 1 for example violations, correct response types, wrong responses, and the result of wrong responses for each tier.
What are the four steps in the paid community dispute resolution ladder?
The four-step ladder applied in sequence: Step 1 is a private DM that names the specific behaviour, cites the rule or norm, describes what the operator would like instead, and documents that this is the first instance — resolves approximately 80% of disputes because most violations are failures of awareness, not intent. Step 2 is public redirection, used only for posting norm violations where the correction is logistical and useful to other members, always accompanied by a private DM; it is not a standalone step. Step 3 is a temporary channel limit applied after the same behaviour has been documented in two separate Step 1 DMs and repeated — the limit is specific to the channels where the pattern occurred, defined in duration, and documented in writing to the member and in the internal log. Step 4 is permanent removal applied after Step 3 has been exhausted, or for first-offence behaviour immediately and directly harmful to another member — always communicated by private DM, always documented in the internal log, never announced publicly. In paid communities, the documentation from Steps 1–3 is the procedural basis for Step 4’s legitimacy. See Table 2 for when to use each step, what it includes, and the resolution rate at each level.
What are the five properties of an enforceable paid community rule?
Five properties: Specific — the rule names a concrete, observable action, not a value word (“be respectful” has no enforcement basis because it describes an internal state the member can always dispute). Behavioural — the rule describes something observable without requiring interpretation of intent (“don’t be pushy” fails; the specific sequence of a cold intro followed by a pitch DM within 30 days passes). Consistent — the same rule applies to all members regardless of tenure, contribution history, or relationship with the operator; inconsistent-by-tenure application is the most corrosive pattern in small paid communities. Graduated — the rule specifies what happens at first, second, and escalated occurrence so the operator is applying a documented process rather than making a unilateral decision in the moment. Operator-modelled — the operator’s own visible behaviour demonstrates the standard before requiring it of members. Rules that fail any of these five properties produce enforcement disputes rather than consistent standards. See Table 3 for enforceable examples, non-enforceable examples, and why the non-enforceable version fails for each property.
What are the most important rules a paid community should have?
Three rules address the situations most frequently handled by ad-hoc judgment in paid communities that lack written standards. The value-before-promotion rule requires a numeric threshold (three non-promotional contributions) before any mention of paid products or services — a numeric threshold eliminates the interpretation disputes that arise from “no self-promotion” rules with no clear earning mechanism. The DM consent rule establishes that pitch DMs require visible in-thread consent from the recipient before any private message about paid content is sent — without this rule, DM proliferation is invisible in public channels and silent churn in months 3–5. The feedback solicitation rule establishes that critique and suggestions may only be given when explicitly requested — the most frequent interpersonal norm violation in practitioner communities, and the one most commonly disputed because the critiquing member genuinely believes they were being helpful. These three rules, combined with the four-step ladder and the DM-first policy, cover the majority of paid community moderation situations with a documented framework rather than fresh judgment calls at each instance. See Table 4 for specific requirements, enforcement triggers, wrong alternatives, and failure modes for each rule.