Difference between revisions of "Event Commander Guidelines"
From COALITION Wiki
| Line 27: | Line 27: | ||
* [https://docs.google.com/document/d/1tUpG-gmp0ukJapdQHPAn0wWZwEHFFi3dvCWPFcoNLiU/edit Example OPORD] | * [https://docs.google.com/document/d/1tUpG-gmp0ukJapdQHPAn0wWZwEHFFi3dvCWPFcoNLiU/edit Example OPORD] | ||
** Operations order template required for your side | ** Operations order template required for your side | ||
* Example Radio Codebook | * [Example Radio Codebook https://docs.google.com/document/d/1SC-keWdtsVgm-DrnGXvB6XTEGCZ6sQN7-QKpt-xprgs/edit] | ||
Revision as of 18:49, 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
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
- Example OPORD
- Operations order template required for your side
- [Example Radio Codebook https://docs.google.com/document/d/1SC-keWdtsVgm-DrnGXvB6XTEGCZ6sQN7-QKpt-xprgs/edit]