Difference between revisions of "Chain of Command"
Line 22: | Line 22: | ||
The 7th Cavalry Gaming Regiment is structured and organized into hierarchical sub-units that are each supported by different levels of the CoC. It typically consists of the following line-unit or combat unit structure, whose primary purpose is to provide a unit level organization to support our games: | The 7th Cavalry Gaming Regiment is structured and organized into hierarchical sub-units that are each supported by different levels of the CoC. It typically consists of the following line-unit or combat unit structure, whose primary purpose is to provide a unit level organization to support our games: | ||
+ | <b>Regiment > Battalion > Company > Platoon > Section</b> | ||
− | + | Each of the above line-units are supported by their respective levels of the CoC: | |
+ | |||
+ | <b>General Staff</b> (Regimental CO, XO, CoS, other Generals, CSM) > <b>Battalion Staff</b> (Battalion CO, XO, SGM) > <b>Company Staff</b> (Company CO, XO, 1SG) > <b>Platoon Staff</b> (Platoon Leader, Platoon Sergeant) > <b>Section Staff</b> (Section Leader, Assistant Section Leader) > <b>Trooper</b> | ||
+ | |||
+ | It also typically consists of the following support department or secondary department structure, whose primary purpose is to advise the Regimental CO and to manage administrative functions: | ||
+ | |||
+ | Regiment > Department > Sub-Department | ||
+ | |||
+ | Each of the above departmental support units are supported by their respective levels of the CoC: | ||
+ | |||
+ | <b>General Staff > Department HQ</b> (Departmental 1IC, 2IC) > <b>Lead > Senior > Clerk/Trooper</b> | ||
+ | |||
+ | ==Structure & CoC Flowchart== | ||
+ | [[File:7th Cavalry Gaming Regiment Chain of Command Structure.png|center|1000px]] | ||
− | + | =Billets within the 7th Cavalry= | |
+ | |||
+ | Billets are used in order to track the responsibilities, duties, and obligations of personnel to the 7th Cavalry. The 7th Cavalry has two types of billet, primary and secondary. | ||
+ | |||
+ | ==Primary Billet== | ||
+ | Primary Billets are those that are considered the main responsibilities, duties, and obligations of 7th Cavalry personnel. | ||
+ | |||
+ | ===Types of Primary Billet=== | ||
+ | |||
+ | * Combat Units | ||
+ | ** [[1st Battalion]] | ||
+ | ** [[2nd Battalion]] | ||
+ | ** [[Auxiliary Combat Detachment]] | ||
+ | * [[Regimental Headquarters]] | ||
+ | ** [[Information Management Office]] | ||
+ | ** [[Security Operations Department]] | ||
+ | ** [[Recruitment Oversight Office]] | ||
+ | ** [[Special Projects Division]] | ||
+ | |||
+ | ==Secondary Billets== | ||
+ | Secondary Billets are responsibilities, duties, and obligations 7th Cavalry personnel can take on in addition to their Primary Billet. | ||
+ | |||
+ | ===Types of Secondary Billets=== | ||
+ | |||
+ | * Regimental Support Departments | ||
+ | ** [[S1 - Personnel Administration]] | ||
+ | ** [[S2 – Intelligence and Security]] | ||
+ | ** [[S3 – Operations]] | ||
+ | ** [[S5 - Public Affairs]] | ||
+ | ** [[S6 – Regimental Information Management Systems]] | ||
+ | ** [[S7 - Training]] | ||
+ | * Regimental Secondary Departments | ||
+ | ** [[Wiki Admin Group]] | ||
+ | ** [[Military Police]] | ||
+ | ** [[Judge Advocate General Corps]] | ||
+ | ** [[Regimental Recruiting Department]] | ||
+ | ** [[Recruit Training Command]] | ||
+ | * Battalion Support Staff | ||
+ | |||
+ | ==Secondary Billets as a Primary Billet== | ||
+ | |||
+ | In some cases, the work being done within a Secondary Billet by a particular individual may be more than what would be considered an additional duty. As such, a particular individual may request that their Secondary Billet become their Primary Billet, and transfer into such position. | ||
+ | ===Requesting a Secondary Billet as a Primary Billet=== | ||
− | + | In order to request a Secondary Billet, as listed above, to become a Primary Billet for a particular individual, said individual will need to submit a request the department's 2IC, 1IC, and Regimental Oversight Staff. Such personnel can be found on the department's respective WIKI pages. | |
+ | ===Removal of a Secondary Billet as a Primary Billet=== | ||
+ | Regimental Oversight Staff may remove personnel that are in a Secondary Billet as a Primary Billet at any time. Personnel will be then transferred back into an available and appropriate Primary Billet, as listed above, of their choice. If they fail to transfer to any suitable position within fourteen days they will be retired/discharged as applicable. | ||
− | + | =Scope, Delegation of Authority, and Orders= | |
+ | All responsibilities and authority originate from the Regimental Commanding Officer billet. All unit commanders (Battalion CO, Company CO, Platoon Leader, and Departmental 1IC’s) are considered command authorities within their own scope of command. All reasonable orders and tasks from a superior are expected to be carried out by their subordinates in the CoC. | ||
+ | ==Orders & the Wiki== | ||
+ | Anything that is not in writing as policy/SOP on the 7th Cavalry Gaming Regiment Wiki should be delegated to the discretion of the appropriate command authority and/or sent up the appropriate Chain of Command for review. All staff/leaders (decision making authorities/command authorities) are encouraged to exercise their discretion and best judgment within the bounds of the 7th Cavalry Code of Conduct, General Orders, and Chain of Command, when no written SOP exists for a particular situation. Reasonable orders should always be followed by subordinates. Otherwise, all active written Regimental policy and SOP should be followed and enforced by all members on this Wiki. | ||
− | Regiment | + | =Right of Review= |
+ | All personnel who are higher in billet in their respective CoC have the right to undertake a review of any level below their billet and within their scope of command. The Regimental Commanding Officer has the authority to review any billet and member across the Regiment. | ||
+ | The intent behind this directive is to declare that every higher billeted level is delegating responsibility and authority to every lower billeted level they directly or indirectly supervise through subordinates. | ||
+ | An example of the order of authority in the CoC is: | ||
+ | #Regimental CO to the Regimental Chief of Staff | ||
+ | #Chief of Staff to Battalion Staff | ||
+ | #Battalion Staff to Company Staff | ||
+ | #Company Staff to Platoon Staff | ||
+ | #Platoon Staff to Squad/Section Leadership | ||
+ | #Squad/Section Leadership to Trooper | ||
− | + | =Regarding Chain of Command Escalation= | |
+ | When submitting an issue to your Chain of Command (CoC) each level will have three (3) calendar days to take appropriate action on said issue. If three (3) days pass and the issue has not been dealt with to the satisfaction of the originator, the originator may then send it to the next level in their CoC. | ||
+ | ==An Example== | ||
+ | Originator, PFC.Trooper, sends an issue to the Section Leader (SL). SGT.Sierra doesn't get around to answering it in three (3) days so PFC.Trooper sends it to LT.Papa. LT.Papa reviews it and tells PFC.Trooper it will never get passed and doesn't send it up. Three days pass and PFC.Trooper sends it to MAJ.Charlie. MAJ.Charlie concurs and sends it to LTC.Bravo who is on vacation. Three days pass with no notification from LTC.Bravo so again PFC.Trooper can now send it to the General Staff who will offer final say on the issue. | ||
+ | The order of escalation would be as such: | ||
+ | Originator: PFC.Trooper | ||
+ | SL: SGT.Sierra | ||
+ | PL: LT.Papa | ||
+ | CO: MAJ.Charlie | ||
+ | Battalion CO: LTC.Bravo | ||
+ | General Staff: GEN.Star (this is the final level) | ||
− | + | ==Intent== | |
+ | The intent behind this directive is to give every level adequate time to address an issue as well as give the trooper who has an issue or new idea a speedier process to get it addressed. |
Revision as of 02:09, 28 January 2024
This is the Document Release Information | |
Article Number: | 7CAV-R-001 |
Scope: | Chain of Command |
Version: | 1.0 |
Effective Date: | 27JAN24 |
Last Modified Date: | 27JAN24 |
Approving Authority: | Regimental Commanding Officer |
Point of Contact: | Regimental Adjutant General |
Introduction
As a gaming community based on military simulation and tactical realism, the 7th Cavalry Gaming Regiment follows a customized military chain of command structure that all members must follow. Our chain of command and structure are loosely modeled on the United States Army, and adapted to meet the needs of our gaming community.
Definition
The 7th Cavalry Gaming Regiment’s Chain of Command (CoC) is a series of positions in order of authority and responsibility along which orders are passed. This structure ensures clear lines of authority and communication, allowing for effective command and control, administration, and reporting relationships within the Regiment.
Purpose
The purpose of the Chain of Command (CoC) is to promote morale, maintain discipline, unity of effort, and mission success. The CoC works by ensuring that authority flows down from the top, and information and feedback flow up. This structure enables clear decision-making, coordination of resources, and effective communication. It also establishes accountability, as individuals at each level are responsible for the tasks and orders they receive from their superiors. Violating the CoC can lead to confusion, inefficiency, and a loss of communication and accountability.
Structure
The 7th Cavalry Gaming Regiment is structured and organized into hierarchical sub-units that are each supported by different levels of the CoC. It typically consists of the following line-unit or combat unit structure, whose primary purpose is to provide a unit level organization to support our games:
Regiment > Battalion > Company > Platoon > Section
Each of the above line-units are supported by their respective levels of the CoC:
General Staff (Regimental CO, XO, CoS, other Generals, CSM) > Battalion Staff (Battalion CO, XO, SGM) > Company Staff (Company CO, XO, 1SG) > Platoon Staff (Platoon Leader, Platoon Sergeant) > Section Staff (Section Leader, Assistant Section Leader) > Trooper
It also typically consists of the following support department or secondary department structure, whose primary purpose is to advise the Regimental CO and to manage administrative functions:
Regiment > Department > Sub-Department
Each of the above departmental support units are supported by their respective levels of the CoC:
General Staff > Department HQ (Departmental 1IC, 2IC) > Lead > Senior > Clerk/Trooper
Structure & CoC Flowchart
Billets within the 7th Cavalry
Billets are used in order to track the responsibilities, duties, and obligations of personnel to the 7th Cavalry. The 7th Cavalry has two types of billet, primary and secondary.
Primary Billet
Primary Billets are those that are considered the main responsibilities, duties, and obligations of 7th Cavalry personnel.
Types of Primary Billet
- Combat Units
- Regimental Headquarters
Secondary Billets
Secondary Billets are responsibilities, duties, and obligations 7th Cavalry personnel can take on in addition to their Primary Billet.
Types of Secondary Billets
- Regimental Support Departments
- Regimental Secondary Departments
- Battalion Support Staff
Secondary Billets as a Primary Billet
In some cases, the work being done within a Secondary Billet by a particular individual may be more than what would be considered an additional duty. As such, a particular individual may request that their Secondary Billet become their Primary Billet, and transfer into such position.
Requesting a Secondary Billet as a Primary Billet
In order to request a Secondary Billet, as listed above, to become a Primary Billet for a particular individual, said individual will need to submit a request the department's 2IC, 1IC, and Regimental Oversight Staff. Such personnel can be found on the department's respective WIKI pages.
Removal of a Secondary Billet as a Primary Billet
Regimental Oversight Staff may remove personnel that are in a Secondary Billet as a Primary Billet at any time. Personnel will be then transferred back into an available and appropriate Primary Billet, as listed above, of their choice. If they fail to transfer to any suitable position within fourteen days they will be retired/discharged as applicable.
Scope, Delegation of Authority, and Orders
All responsibilities and authority originate from the Regimental Commanding Officer billet. All unit commanders (Battalion CO, Company CO, Platoon Leader, and Departmental 1IC’s) are considered command authorities within their own scope of command. All reasonable orders and tasks from a superior are expected to be carried out by their subordinates in the CoC.
Orders & the Wiki
Anything that is not in writing as policy/SOP on the 7th Cavalry Gaming Regiment Wiki should be delegated to the discretion of the appropriate command authority and/or sent up the appropriate Chain of Command for review. All staff/leaders (decision making authorities/command authorities) are encouraged to exercise their discretion and best judgment within the bounds of the 7th Cavalry Code of Conduct, General Orders, and Chain of Command, when no written SOP exists for a particular situation. Reasonable orders should always be followed by subordinates. Otherwise, all active written Regimental policy and SOP should be followed and enforced by all members on this Wiki.
Right of Review
All personnel who are higher in billet in their respective CoC have the right to undertake a review of any level below their billet and within their scope of command. The Regimental Commanding Officer has the authority to review any billet and member across the Regiment.
The intent behind this directive is to declare that every higher billeted level is delegating responsibility and authority to every lower billeted level they directly or indirectly supervise through subordinates. An example of the order of authority in the CoC is:
- Regimental CO to the Regimental Chief of Staff
- Chief of Staff to Battalion Staff
- Battalion Staff to Company Staff
- Company Staff to Platoon Staff
- Platoon Staff to Squad/Section Leadership
- Squad/Section Leadership to Trooper
Regarding Chain of Command Escalation
When submitting an issue to your Chain of Command (CoC) each level will have three (3) calendar days to take appropriate action on said issue. If three (3) days pass and the issue has not been dealt with to the satisfaction of the originator, the originator may then send it to the next level in their CoC.
An Example
Originator, PFC.Trooper, sends an issue to the Section Leader (SL). SGT.Sierra doesn't get around to answering it in three (3) days so PFC.Trooper sends it to LT.Papa. LT.Papa reviews it and tells PFC.Trooper it will never get passed and doesn't send it up. Three days pass and PFC.Trooper sends it to MAJ.Charlie. MAJ.Charlie concurs and sends it to LTC.Bravo who is on vacation. Three days pass with no notification from LTC.Bravo so again PFC.Trooper can now send it to the General Staff who will offer final say on the issue. The order of escalation would be as such: Originator: PFC.Trooper SL: SGT.Sierra PL: LT.Papa CO: MAJ.Charlie Battalion CO: LTC.Bravo General Staff: GEN.Star (this is the final level)
Intent
The intent behind this directive is to give every level adequate time to address an issue as well as give the trooper who has an issue or new idea a speedier process to get it addressed.