ENSIS WAR THUNDER SQUADRON

Dispute & Escalation Guide

This defines how conflicts, rule violations, and disagreements inside Ensis get resolved, so issues don't sit unresolved or get dumped straight on Commander every time.

Roles in the Chain Who handles what, in order
Level Role Handles
1 Deputy First point of contact for any dispute between Private/Team members; day-to-day discipline
2 Recruitment Staff Recruitment-specific disputes only (rejected applicants, trial extensions, application appeals)
3 Sergeant Escalations Deputy can't resolve; disputes involving a Deputy; policy interpretation questions
4 Commander Final authority; roster removals, external/inter-squadron disputes, Sergeant-level conflicts, appeals of any decision below
Escalation Flow Step-by-step process, VC-first
  1. Direct resolution (24h window). The two parties are encouraged to resolve it themselves first, ideally by hopping into a VC and talking it out, not in public text chat.
  2. Deputy mediation. If unresolved, either party pings the on-duty Deputy. Deputy pulls both parties into a VC, hears both sides, checks server rules, and issues a ruling within 48 hours. Deputy logs the outcome in the mod-log channel (one line: date, parties, issue, ruling).
  3. Recruitment track (if applicable). Disputes about applications, trials, or promotion decisions go to Recruitment Staff instead of Deputy, following the same 48-hour rule and VC-first approach.
  4. Sergeant review. If either party disputes the Deputy/Recruitment Staff ruling, or if a Deputy is one of the parties involved, it escalates to Sergeant. Sergeant pulls everyone into a VC to review the mod-log entry and hear both sides directly, then issues a binding ruling within 72 hours.
  5. Commander final call. Only escalates here if the Sergeant ruling is disputed, the case involves a roster removal or ban, it involves another squadron/external party, or it involves the Sergeant themselves. Commander's ruling is final — no further appeal inside the server.
Rules for Every Stage Applies to Deputy, Recruitment Staff & Sergeant
  • No public callouts or airing disputes in general/team channels — take it to a VC with the handling officer instead.
  • The handling role (Deputy/Recruitment Staff/Sergeant) must hear both sides in VC before ruling — no one-sided decisions.
  • Every ruling gets one line in the mod-log channel for transparency and precedent, even if details of the VC conversation stay private.
  • Retaliation against someone for raising a dispute is itself a violation, escalated directly to Sergeant regardless of the original issue's stage.
  • If a handling role has a conflict of interest (friend, squad-mate involved), they must pass it to the next level immediately instead of ruling.
What Does NOT Go Through This Process Handled outside the escalation chain

In-Match Strategy

  • Settled by whoever holds shot-caller/IGL duty for that scrim, not by escalation.

Routine Moderation

  • General banter/rule-breaking messages are handled in real time by normal moderators — escalation is only for unresolved interpersonal or decision disputes.