Difference between revisions of "Event Commander Guidelines"

Latest revision as of 18:53, 19 February 2023

Commander Duties

Chronologically in order of importance:

Meeting with Commanders and Event Creator to finalize rosters, review Coalition Community Events Rules, and answer any questions Commanders may have.
Company-level operations order (OPORD) 1 week prior to mission.
Planning meetings with leadership (at least 2 preferred) leading up to missions.
Platoon Leaders should have their Platoon-level plans ready at least 2 days before mission.

Timelines

Immediately upon election as a Commander:
- Review event rules
- Meet with event creator to clarify event specifics
Two weeks prior:
- Begin to build a Miro or PLANOPs board for wargaming and strategy
- Publish a WhenIsGood to set up leadership meetings
One week prior:
- Publish Operations Order (OPORD)
- Conduct at least one meeting with leadership to relay plan and game play specifics
- Adapt Miro/PLANOPs board as necessary
Two days prior:
- Ensure Platoon Lead(s) have pushed out their platoon plans and conducted briefings with their squad leaders
- Adapt as necessary

Resources

Miro or Planops
- Tools for collaborative planning and mapping prior to the event
WhenIsGood?
- Scheduling tool for finding the best time to meet with your leaders
OPORD Template
- Operations order template required for your side
Example Radio Codebook
- If espionage is enabled, this is an example of a radio code book

@@ Line 1: / Line 1: @@
 == Commander Duties ==
+Chronologically in order of importance:
-Meeting with Commanders and Event Creator to finalize rosters, review [[Coalition Community Events Rules]], and answer any questions Commanders may have
+# Meeting with Commanders and Event Creator to finalize rosters, review [[Coalition Community Events Rules]], and answer any questions Commanders may have.
+# Company-level operations order (OPORD) 1 week prior to mission.
+# Planning meetings with leadership (at least 2 preferred) leading up to missions.
+# Platoon Leaders should have their Platoon-level plans ready at least 2 days before mission.
-Company-level plans (OPORD) 1 week prior to mission [https://docs.google.com/document/d/1tUpG-gmp0ukJapdQHPAn0wWZwEHFFi3dvCWPFcoNLiU/edit Example OPORD]
+== Timelines ==
-Planning meetings with leadership (at least 2 preferred) leading up to missions
-Platoon Leaders should have their Platoon-level plans ready at least 2 days before mission
+* Immediately upon election as a Commander:
+** Review event rules
+** Meet with event creator to clarify event specifics
+* Two weeks prior:
+** Begin to build a Miro or PLANOPs board for wargaming and strategy
+** Publish a WhenIsGood to set up leadership meetings
+* One week prior:
+** Publish Operations Order (OPORD)
+** Conduct at least one meeting with leadership to relay plan and game play specifics
+**Adapt Miro/PLANOPs board as necessary
+*Two days prior:
+**Ensure Platoon Lead(s) have pushed out their platoon plans and conducted briefings with their squad leaders
+**Adapt as necessary
 == Resources ==
-[https://miro.com/ Miro] or [https://maps.plan-ops.fr/ Planops] are both great tools for collaborative planning and mapping
+* [https://miro.com/ Miro] or [https://maps.plan-ops.fr/ Planops]
+** Tools for collaborative planning and mapping prior to the event
-[https://whenisgood.net/ WhenIsGood?] great for finding the best times for leadership meetings
+* [https://whenisgood.net/ WhenIsGood?]
+** Scheduling tool for finding the best time to meet with your leaders
+* [https://docs.google.com/document/d/1tUpG-gmp0ukJapdQHPAn0wWZwEHFFi3dvCWPFcoNLiU/edit OPORD Template]
+** Operations order template required for your side
+* [https://docs.google.com/document/d/1SC-keWdtsVgm-DrnGXvB6XTEGCZ6sQN7-QKpt-xprgs/edit Example Radio Codebook]
+**If espionage is enabled, this is an example of a radio code book