**COMMAND ACTIVITY & LEAVE OF ABSENCE POLICY**
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**PURPOSE**
This policy establishes clear expectations for Command member activity and provides structured pathways for time away when needed. The goal is to distribute workload fairly, prevent burnout, and maintain momentum while recognizing that life happens.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**ACTIVITY REQUIREMENTS**
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Quarterly Individual Requirements:**
Every Command member should meet the following per quarter (every 3 months):
**GREEN Status (Normal Operations):**
- Host or co-host 1 event, AND
- Participate in 2 events hosted by others
**YELLOW Status (Reduced Operations):**
- Host or co-host 1 event, AND
- Participate in 1 event hosted by others
**RED Status (Game Broken/Non-Functional):**
- Event requirements suspended
- Active Discord engagement and community presence required
**What Counts as Hosting:**
- Event announced in Discord (event channels or VC announcement)
- Impromptu events count if announced and involve 3+ people (including host)
- Counts even if attendance is low - effort matters
- Counts even if game crashes or technical issues occur
- Co-hosting with another Command member counts for both
**What Counts as Participating:**
- Joining an event someone else organized
- Active engagement (not idle presence)
- Helping with event prep, setup, or coordination
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Semi-Annual Collaborative Requirement:**
Every 6 months, all active Command members collaborate on 1 major org-wide event:
- **Q2 (April-June):** Major collaborative event
- **Q4 (October-December):** Major collaborative event
These are signature operations (Strike Groups, large-scale FPS events, cross-functional industrial ops) designed to showcase Command working together.
**Participation Options:**
- Attend and participate in the event
- Contribute to planning and coordination
- Provide prep work, logistics support, or post-event follow-up
- Alternative contribution via planning/prep if unable to attend due to schedule conflicts
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Quarterly Tracking Schedule:**
**Q1 (January - March):** Host 1 + Participate 2
**Q2 (April - June):** Host 1 + Participate 2 + Collaborative event
**Q3 (July - September):** Host 1 + Participate 2
**Q4 (October - December):** Host 1 + Participate 2 + Collaborative event
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Backend Work Recognition:**
Backend contributions (website development, strategic planning, systems administration, content creation, operations coordination) are valuable and recognized. However, they do not reduce the baseline community presence requirements above. Command is a leadership role that requires visibility.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**OPERATIONAL STATUS SYSTEM**
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**GREEN Status (Normal Operations):**
- Game is stable and playable
- Full activity requirements apply
**YELLOW Status (Reduced Operations):**
- Major bugs, unplayable patches, or content drought
- Activity requirements reduced
- Command coordinates to establish agreed-upon standards for YELLOW triggers
**RED Status (Critical/Non-Functional):**
- Game is fundamentally broken or unplayable
- Event requirements suspended
- Focus shifts to Discord engagement, planning, and backend work
**Status Change Process:**
**When votes occur:**
- Any Command member may call for status vote at any time
- Mandatory reviews occur quarterly, within 2 weeks of major patches, and during Command meetings
**Vote requirements:**
- Simple majority of active Command members (not on LOA)
- Current status announced in Command chat and logged
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**LEAVE OF ABSENCE (LOA) POLICY**
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Standard LOA (Game Burnout/Personal Reasons):**
Command members may take up to **4 months of LOA per year**.
Can be structured as:
- 1 x 4-month LOA
- 2 x 2-month LOAs
- 4 x 1-month LOAs
**Requirements:**
- Communicate to Command in advance when possible
- Cannot exceed 4 consecutive months without Command review
**After 4 consecutive months:**
- Return to active status, OR
- Request extension with timeline (requires Command vote), OR
- Step down to Paragon with priority reapplication rights
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Protected LOA (Life Events):**
The following warrant automatic extended LOA with role protection:
- Military deployments
- Medical emergencies (member or immediate family)
- Birth/adoption of a child
- Major life transitions (moving, new job, family emergencies)
- Significant work travel
- Other major circumstances determined case-by-case
**Communication:**
Communicate ahead of time when possible. For unexpected situations, notify Command as soon as reasonably able.
**During Protected LOA:**
- Status updated to "Command LOA"
- Role protected for duration
- Member notifies Command when ready to return
**Extended Protected LOA (beyond 6 months):**
Command conducts check-in to assess timeline and maintain communication. Does not jeopardize standing.
**Important:** Protected LOA has no time cap and does not count toward the 4-month annual Standard LOA allowance.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**LOA and Command Voting:**
Members on LOA are temporarily removed from Command voting:
- Do not count toward quorum
- Cannot vote during LOA period
- Voting rights restore upon return
This ensures decisions are made by active, engaged members present for context and execution.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**IMPLEMENTATION**
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
This policy takes effect upon Command vote approval.
**Activity tracking:**
- Event logging and Command oversight
- Transparent documentation
**Current Status:**
- Operational Status: GREEN
- First tracking period: Q2 2026
- First collaborative event: Q2 2026
Questions should be directed to Command leadership.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**SUMMARY**
✅ Clear quarterly expectations
✅ Pathways for time away (Standard and Protected LOA)
✅ Fair workload distribution
✅ Flexibility during game issues or life circumstances
✅ Effort counts even when outcomes are imperfect
**The goal:** Show up when you can, communicate when you can't, and help carry the load so no one burns out.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━