Standard Moderation Workflow¶
Purpose¶
A consistent moderation process helps ensure that similar situations receive similar outcomes, regardless of which staff member handles the case.
Following a standard workflow improves fairness, documentation quality, and confidence in moderation decisions.
Overview¶
Every moderation case should follow the same general process:
- Receive the report.
- Assess urgency.
- Gather evidence.
- Identify the applicable rule.
- Consider context.
- Determine the appropriate response.
- Communicate the decision.
- Document the action.
- Request review if required.
- Close the case.
Not every situation will require every step, but skipping steps should be the exception—not the rule.
1. Receive the Report¶
Reports may originate from:
- Player reports
- Discord tickets
- Staff observation
- Server logs
- Automated systems
- Other staff members
Read the entire report before taking action.
Avoid making assumptions based on the initial description alone.
2. Assess Urgency¶
Determine whether immediate intervention is necessary.
Examples of urgent situations include:
- Active cheating
- Severe harassment
- Hate speech
- Ongoing disruption
- Staff impersonation
- Security concerns
Urgency may justify rapid intervention, but it should never replace evidence gathering.
3. Gather Evidence¶
Whenever possible, collect and preserve evidence before taking disciplinary action.
Evidence may include:
- Server logs
- Chat logs
- Screenshots
- Video recordings
- Witness statements
- Staff observations
- Previous disciplinary history
Ensure evidence is sufficient to support the intended action.
4. Identify the Applicable Rule¶
Determine which server rule applies.
Ask yourself:
- Was a rule actually violated?
- Which specific rule applies?
- Does the evidence support that conclusion?
Avoid stretching rules to fit a situation.
If no rule applies, disciplinary action may not be appropriate.
5. Consider Context¶
Context helps determine the appropriate response.
Consider factors such as:
- Intent
- Severity
- Previous history
- Cooperation
- Impact on other players
- Whether the behavior appears accidental or deliberate
Context influences the response—not whether rules exist.
6. Determine the Appropriate Response¶
Choose the least severe action that effectively resolves the issue.
Possible outcomes include:
- No action
- Education
- Reminder
- Warning
- Strike
- Temporary removal
- Temporary ban
- Permanent ban
The goal is correcting behavior while protecting the community.
7. Communicate Clearly¶
Whenever practical, explain:
- Which rule applies.
- Why action was taken.
- What behavior should change.
- How to appeal if applicable.
Professional communication reduces confusion and unnecessary conflict.
8. Document the Action¶
Document all significant moderation actions promptly.
Documentation should include:
- Players involved
- Date and time
- Applicable rule
- Summary of events
- Evidence
- Action taken
- Reasoning
- Review status
Documentation protects both staff and players.
9. Request Review¶
Some actions require additional review.
Examples include:
- Trial Administrator actions
- Permanent bans
- Appeals
- Staff disciplinary matters
- Complex investigations
- Cases involving unclear policy
Seeking review is a sign of professionalism—not weakness.
10. Close the Case¶
Before closing the case, confirm that:
- The appropriate action has been completed.
- Documentation is complete.
- Evidence has been preserved.
- Required reviews have been requested.
- Players have been informed when appropriate.
Once complete, the case may be considered closed.
Guiding Principle¶
A good moderation process should produce the same outcome regardless of which qualified staff member handles the report.
Consistency is one of the strongest indicators of a healthy moderation team.