Strikes
Track disciplinary actions for staff members. Strikes help maintain accountability and document issues.
What are Strikes?
Strikes are formal warnings for staff members:
- Document performance issues or rule violations
- Track patterns of behavior
- Support progressive discipline
Viewing Strikes
On Staff Management Page
Each staff member shows their active strike count in the list.
Individual Staff
Click on a staff member to see their full strike history.
Issuing a Strike
- Find the staff member in Staff Management
- Click the menu icon
- Select "Issue Strike"
- Fill in the strike details:
| Field | Description |
|---|---|
| Reason | Why the strike is being issued |
| Evidence | Links, screenshots (optional) |
| Severity | Minor, Moderate, or Severe (optional) |
| Notes | Additional context |
- Click "Issue Strike"
The staff member can be notified via Discord DM.
Strike Information
Each strike records:
| Field | Description |
|---|---|
| Date Issued | When the strike was given |
| Issued By | Who gave the strike |
| Reason | Why it was issued |
| Severity | Minor, Moderate, or Severe |
| Evidence | Attached proof |
| Status | Active or Removed |
Removing Strikes
Strikes can be removed if:
- Issued in error
- Appealed successfully
- Management decision
To remove:
- View the staff member's profile
- Find the strike
- Click "Remove"
- Add a reason for removal
- Confirm
The strike is marked as removed but preserved in history.
Strike Severity
Minor
- First-time issues
- Small mistakes
- Low impact
Moderate
- Repeated minor issues
- More significant problems
- Pattern emerging
Severe
- Major violations
- Serious misconduct
- May lead to demotion/removal
Using Strikes Effectively
Progressive Discipline
Typical progression:
- Verbal warning - Informal conversation
- Strike 1 - First formal warning
- Strike 2 - Second warning, increased severity
- Strike 3 - Final warning, consider demotion
- Removal - If behavior continues
Documentation
Good strike documentation includes:
- Specific incident description
- Date and time of occurrence
- Evidence if available
- Previous related warnings
- Expected improvement
Example Strike Reasons
- "Inactive for 2 weeks without notice"
- "Used inappropriate language in staff chat"
- "Unfair moderation action against user"
- "Shared confidential information"
- "Failed to follow moderation guidelines"
Best Practices
Be Specific
- Describe exactly what happened
- Include dates and context
- Reference specific rules violated
Be Consistent
- Same offense = same treatment
- Document similar situations similarly
- Review past strikes for consistency
Communicate
- Talk to the staff member about the issue
- Explain what went wrong
- Discuss how to improve
- Follow up on progress
Keep Records
- Strikes create an audit trail
- Useful for promotion/demotion decisions
- Protects against disputes