Chain of Command: Difference between revisions

From 7th Cavalry Wiki
Jump to navigation Jump to search
← Older edit
 
(26 intermediate revisions by the same user not shown)
Line 4: Line 4:
|articlenumber  = 7CAV-R-001
|articlenumber  = 7CAV-R-001
|scope  = Chain of Command
|scope  = Chain of Command
|version  = 1.0
|version  = 1.1
|effectivedate  = 27JAN24
|effectivedate  = 27JAN24
|lastmodifieddate = 27JAN24
|lastmodifieddate = 31JAN24
|approvingauthority  = Regimental Commanding Officer
|approvingauthority  = Regimental Commanding Officer
|pointofcontact  = Regimental Adjutant General
|pointofcontact  = Regimental Adjutant General
Line 12: Line 12:




=Introduction=
=Chain of Command=
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.
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.


Line 22: Line 22:


=Structure=
=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:
The 7th Cavalry Gaming Regiment is structured and organized into hierarchical sub-units that are each supported by different levels of the CoC through positions called billets. 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>
<b>Regiment > Battalion > Company > Platoon > Section</b>


Each of the above line-units are supported by their respective levels of the CoC by primary billet:
Each of the above line-units are supported by their respective levels of the CoC by primary billets:


<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>
<b>General Staff</b> (Regimental CO, XO, COS, other Generals, CSM) > <b>Battalion Staff</b> (Battalion CO, XO, SGM) > <b>Company Staff</b> (Company Commander, 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:
It also typically consists of the following support or secondary department structure, whose primary purpose is to advise the Regimental CO and to manage administrative functions:


<b>Regiment > Department > Sub-Department</b>
<b>Regiment > Department > Sub-Department</b>


Each of the above departmental support units are supported by their respective levels of the CoC by secondary billet:
Each of the above departmental support units are supported by their respective levels of the CoC by secondary billets:


<b>General Staff > Department HQ</b> (Departmental 1IC, 2IC) <b>> Lead > Senior > Clerk/Trooper</b>
<b>General Staff > Department HQ</b> (Departmental 1IC, 2IC) <b>> Lead > Senior > Clerk/Trooper</b>


==Structure & CoC Flowchart==
==Billets==
[[File:7th Cavalry Gaming Regiment Chain of Command Structure.png|center|1000px]]


=Billets within the 7th Cavalry Gaming Regiment=
For information about the types of billets in the unit, please see [[Billets]].


Billets are positions used to track the responsibilities, duties, and obligations of personnel in the 7th Cavalry Gaming Regiment. The 7th Cavalry has two types of billet:
==Unit Size Requirements==
*Primary
*Secondary


==Primary Billet==
All staff members are required to adhere to the following listed minimums and maximums for Section, Platoon, and Company sub-unit sizes.
Primary Billets are those that are considered the main responsibilities, duties, and obligations of 7th Cavalry personnel.


===Types of Primary Billet===
===Procedure===


* Combat Units
# If the sub-unit falls below the minimum, it must be merged if possible in order to maintain overall parent unit health.
** [[1st Battalion]]
# If the sub-unit rises above the listed maximum, it will be split as soon as it is feasible, healthy, and possible in order to allow a good subordinate to leader ratio.
** [[2nd Battalion]]
# The Trooper numbers listed below include Section Leaders, but not Platoon or Company Staff.
** [[Auxiliary Combat Detachment]]
# General Staff reserves the right to intervene at their discretion, but barring exceptional circumstances will typically do so only when a unit is at or below critical numbers.
* [[Regimental Headquarters]]
** [[Security Operations Department]]
** [[Recruitment Oversight Office]]
** [[Special Projects Division]]
** [[Information Management Office]]


==Secondary Billets==
===Unit Numbers===
Secondary Billets are responsibilities, duties, and obligations 7th Cavalry personnel can take on in addition to their Primary Billet.  They are often considered voluntary and are intended to help support the administrative functions of the entire Regiment and each of our games.  This is why it’s called a secondary billet.
{| class="wikitable"
|+
! rowspan="2"; style ="background-color: #ffd900" |Unit
! style ="background-color: #ffd900" | Description
! colspan="2"; style ="background-color: #ffd900" |'''<big>Minimal</big>'''
! colspan="2"; style ="background-color: #ffd900" |'''<big>Critical</big>'''
! colspan="2"; style ="background-color: #ffd900" |'''<big>Nominal</big>'''
! colspan="2"; style ="background-color: #ffd900" |'''<big>Maximum</big>'''
|-
! style ="background-color: #ffd900" | Scope
!''Troopers''
!''Sub-Units''
!''Troopers''
!''Sub-Units''
!''Troopers''
!''Sub-Units''
!''Troopers''
!''Sub-Units''
|-
| colspan="2" |<big>Section</big>
|4
| -
| -
| -
|8
| -
|13
| -
|-
| colspan="2" |<big>Platoon</big>
|12
|2 Sections
|20
|2 Sections
|24
|3 Sections
|48
|4 Sections
|-
| colspan="2" |<big>Company</big>
|28
|2 Platoons
|36
|2 Platoons
|48
|2 Platoons
|96
|3 Platoons
|}


===Types of Secondary Billets===
===Waivers===
Any deviation to the above guidelines requires a waiver from the Regimental Chief of Staff (COS) or their designate. When requesting a waiver, Company Staff must submit a request by forum private message to the relevant Platoon Staff, Battalion Staff, and COS. A waiver should normally be sought if no split is planned or a planned split will require more than thirty (30) days.


* Regimental Support Departments
==Structure & CoC Flowchart==
** [[S1 - Personnel Administration]]
The following is a flow chart of the 7th Cavalry Gaming Regiment's structure and supporting Chain of Command:
** [[S2 – Intelligence and Security]]
[[File:7th Cavalry Gaming Regiment Chain of Command Structure.png|center|1000px]]
** [[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]]
** [[Leadership - Officer Development School|Officer Development School]]
** [[Non-Commissioned Officer Academy]]
* 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 a position.
 
===Requesting a Secondary Billet as a Primary Billet===
 
In order to request a Secondary Billet to become a Primary Billet for a particular individual, said individual will need to submit a request to the department's 2IC, 1IC, and General Staff oversight, with ultimate responsibility and decision making authority with the appropriate General Staff oversight . Such personnel can be found on the department's respective WIKI pages.
 
===Removal of a Secondary Billet as a Primary Billet===
General 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 discharged/retired as applicable.


=Scope, Delegation of Authority, and Orders=
=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.
All responsibilities and authority originate from the Regimental Commanding Officer billet.  All unit commanders (Battalion CO, Company Commander, 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==
==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.  
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.  


Regimental SOP always supersedes SOP or policy from a lower unit. Additional criteria can always be added to Regimental SOP for the use of a lower unit by appropriate command authorities, but the Regimental SOP is always the minimum standard.
Regimental SOP always supersedes SOP or policy from a lower unit. Additional criteria can always be added to Regimental SOP for the use of a sub-unit (such as Battalions or Departments) by appropriate command authorities, but the Regimental SOP is always the minimum standard and cannot be lowered.


=Right of Review=
=Right of Review=
Line 113: Line 129:
#Battalion Staff to Company Staff
#Battalion Staff to Company Staff
#Company Staff to Platoon Staff
#Company Staff to Platoon Staff
#Platoon Staff to Squad/Section Leadership
#Platoon Staff to Section Staff
#Squad/Section Leadership to Trooper
#Section Staff to Trooper


=Chain of Command Escalation=
=Chain of Command Escalation=
Line 132: Line 148:
==Intent==
==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.
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.
=Billet Sections=
This SOP outlines the requirements for position openings for Section Staff, Platoon Staff, Company Staff, and Battalion Staff, as well as Departmental 1IC and 2IC positions. Unfilled positions/billets should be opened to application so members can be made aware, apply, and go through a selection process before a final decision is made by the appropriate command authority.  What is required to be stated in Letters of Recommendation or Letters of Interest is at the discretion of the Staff overseeing the selection process.
==Applications==
All positions/billets need to be advertised with a relevant position opening and must include the following details:
*Overview of the position including duties and responsibilities.
*Minimum requirements.
*The outlined application process, including an interview.
*Deadlines for application.
*Deadlines for interviews to be complete and when the position will be announced.
*Whom the application should be submitted to and what it should include.
==Assistant Section Leader==
Listed below is the process for billet selection for ASL for all Troopers across the Regiment.
*Be in good standing with no active negative actions.
*Maintained MOS for a minimum of 30 days prior to selection.
*Be at the minimum rank of Specialist (E-4) or higher upon recommendation.
*Letter of Recommendation from SL to Platoon Staff for review.
*Letter of Interest from Trooper to Platoon staff for review.
*Platoon Staff reviews all candidates and their letters.
*Company Staff is the appointing authority for the position but can delegate to Platoon Staff.
==Section Leader==
Listed below is the process for billet selection for SL for all Troopers across the Regiment.
* Be in good standing with no active negative actions.
* Maintained the MOS for 30 days.
* Maintained the MOS billet of ASL for a minimum of 30 days prior to selection or submit an application as a Trooper.
* Be at the minimum rank of Corporal (E-4) or higher prior to selection.
* Submit an application upon position opening and following the application process unless Company/Platoon Staff select an ASL to fill the role.
* Candidates reviewed by Platoon and Company Staff.
* Company Staff is the appointing authority for the position but can delegate to Platoon Staff.
==Platoon Sergeant==
Listed below is the process for billet selection for PSG for all Troopers across the Regiment.
*Be in good standing with no active negative actions.
*Maintained the MOS billet of SL for a minimum of 30 days prior to application.
*Be at the minimum rank of Sergeant (E-5) or higher upon application.
*Submit an application upon position opening and following the application process.
*Applications reviewed by Company Staff.
*Company Staff is the appointing authority for the position but can delegate to the Platoon Leader.
==Platoon Leader==
Newly commissioned officers, and thus Platoon Leaders, are appointed by the Regimental Chief of Staff or their delegate.  For more information on this process, please see:
*[[Rank_Promotion and Reduction Guidelines]]
*[[Leadership - Officer Development School]]
==Company First Sergeant==
*Be in good standing with no active negative action.
*Be at the minimum rank of Sergeant (E-5).
*Letter of interest from applicant to Battalion CO, Battalion SGM, Regimental CSM, and their designate(s) for review.
*Final selection is approved by the Battalion CO.
==Company Executive Officer==
*Be in good standing with no active negative action.
*Be at the minimum rank of First Lieutenant (O-2).
*Letter of interest from applicant to Battalion CO, Regimental COS, and their designate(s) for review.
*Final selection is approved by the Battalion CO.
==Company Commanding Officer==
*Be in good standing with no active negative action.
*Be at the minimum rank of First Lieutenant (O-2).
*Letter of interest from applicant to Battalion CO, Regimental COS, and their designate(s) for review.
*Final selection is approved by the Battalion CO.
==Battalion Sergeant Major==
*Be in good standing with no active negative action
*Be at the minimum rank of Sergeant First Class (E-7)
*Letter of interest from applicant to the Regimental Command Sergeant Major, Regimental COS, and their designate(s) for review
*Final selection is approved by the Regimental COS but can be delegated to the Regimental Command Sergeant Major.
==Battalion Executive Officer==
*Be in good standing with no active negative action.
*Be at the minimum rank of Captain (O-3).
*Letter of Interest from applicant to the Regimental Chief of Staff and their designate(s) for review.
*Final selection is approved by the Regimental COS.
==Battalion Commanding Officer==
*Be in good standing with no active negative action.
*Be at the minimum rank of Captain (O-3).
*Letter of Interest from applicant to the Regimental Chief of Staff and their designate(s) for review.
*Final selection is approved by the Regimental COS.
==Departmental HQ - 1IC/2IC==
* Be in good standing with no active negative action.
* Be at the minimum rank of:
** Second Lieutenant (O-1) for Officers
** Chief Warrant Officer 2 (W-2) for Warrant Officers
** Sergeant (E-5) for Non-Commissioned Officers
* Letter of Interest from applicant to the relevant General Staff departmental oversight.
* Final selection is approved by the relevant General Staff departmental oversight.
==Minimum time to serve==
Once an assignment has been announced, the successful applicant must serve a minimum of 6 months in the assigned billet. Therefore, they will not be permitted to transfer to a lateral position (XO to XO, CO to CO) if they are within 6 months. However, they are permitted to be promoted inside their normal Chain of Command (A/1-7 XO to A/1-7 CO). Additionally, a waiver for special circumstances may be issued by the Regimental COS or their designate.
==Transfer Priority==
After six months in their position, staff may make applications for lateral transfers (i.e, Company XO to another Company XO slot). These applications will receive first review priority and will be granted the transfer if otherwise qualified for the position.
Minimum qualifications to be deemed as qualified are as follows:
# Be in good standing with no active negative action
# Posses the minimum training and skills required for the MOS/billet they wish to transfer
# Any other quantifiable standards the position’s assigning party(s) wish to see
==Minimum Rank and Rank Adjustment==
In addition to the above format, take note that those with rank and tenure will be considered before those below them unless otherwise disqualified. Brevet promotions to the minimum rank upon receiving a billet are still in effect at the approval of the Chief of Staff (CoS).
==Post Notes==
If a CO/1IC position becomes available then the incumbent XO/2IC will need to apply for the position to be considered.
Any exception to the above guidelines requires a waiver from the COS.  When requesting a waiver, Company Staff must submit a request by forum PM to the COS or the designate(s), as well as the relevant Platoon Staff and Battalion Staff.
In reference to [[Rank Promotion and Reduction Guidelines]], these ranks are not the rank minimums for being assigned any of the above billets.  These requirements are solely for being assigned to the position with no need for sign off by General Staff.


=Exceptions=
=Exceptions=
Exceptions to this CoC SOP may be made at the discretion of the General Staff depending on the needs of the Regiment.
Exceptions to this document may be made at the discretion of the General Staff depending on the needs of the Regiment.

Latest revision as of 14:54, 9 May 2024

This is the Document Release Information
Article Number: 7CAV-R-001
Scope: Chain of Command
Version: 1.1
Effective Date: 27JAN24
Last Modified Date: 31JAN24
Approving Authority: Regimental Commanding Officer
Point of Contact: Regimental Adjutant General


Chain of Command

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 through positions called billets. 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 by primary billets:

General Staff (Regimental CO, XO, COS, other Generals, CSM) > Battalion Staff (Battalion CO, XO, SGM) > Company Staff (Company Commander, XO, 1SG) > Platoon Staff (Platoon Leader, Platoon Sergeant) > Section Staff (Section Leader, Assistant Section Leader) > Trooper

It also typically consists of the following support 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 by secondary billets:

General Staff > Department HQ (Departmental 1IC, 2IC) > Lead > Senior > Clerk/Trooper

Billets

For information about the types of billets in the unit, please see Billets.

Unit Size Requirements

All staff members are required to adhere to the following listed minimums and maximums for Section, Platoon, and Company sub-unit sizes.

Procedure

  1. If the sub-unit falls below the minimum, it must be merged if possible in order to maintain overall parent unit health.
  2. If the sub-unit rises above the listed maximum, it will be split as soon as it is feasible, healthy, and possible in order to allow a good subordinate to leader ratio.
  3. The Trooper numbers listed below include Section Leaders, but not Platoon or Company Staff.
  4. General Staff reserves the right to intervene at their discretion, but barring exceptional circumstances will typically do so only when a unit is at or below critical numbers.

Unit Numbers

Unit Description Minimal Critical Nominal Maximum
Scope Troopers Sub-Units Troopers Sub-Units Troopers Sub-Units Troopers Sub-Units
Section 4 - - - 8 - 13 -
Platoon 12 2 Sections 20 2 Sections 24 3 Sections 48 4 Sections
Company 28 2 Platoons 36 2 Platoons 48 2 Platoons 96 3 Platoons

Waivers

Any deviation to the above guidelines requires a waiver from the Regimental Chief of Staff (COS) or their designate. When requesting a waiver, Company Staff must submit a request by forum private message to the relevant Platoon Staff, Battalion Staff, and COS. A waiver should normally be sought if no split is planned or a planned split will require more than thirty (30) days.

Structure & CoC Flowchart

The following is a flow chart of the 7th Cavalry Gaming Regiment's structure and supporting Chain of Command:

Scope, Delegation of Authority, and Orders

All responsibilities and authority originate from the Regimental Commanding Officer billet. All unit commanders (Battalion CO, Company Commander, 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.

Regimental SOP always supersedes SOP or policy from a lower unit. Additional criteria can always be added to Regimental SOP for the use of a sub-unit (such as Battalions or Departments) by appropriate command authorities, but the Regimental SOP is always the minimum standard and cannot be lowered.

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:

  1. Regimental CO to the Regimental Chief of Staff
  2. Chief of Staff to Battalion Staff
  3. Battalion Staff to Company Staff
  4. Company Staff to Platoon Staff
  5. Platoon Staff to Section Staff
  6. Section Staff to Trooper

Chain of Command Escalation

When submitting an issue to your 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.A, sends an issue to the Section Leader (SL). SGT.Sierra.B doesn't get around to answering it in three (3) days so PFC.Trooper.A sends it to 2LT.Papa.C. 2LT.Papa.C reviews it and tells PFC.Trooper it will never get passed and doesn't send it up. Three days pass and PFC.Trooper.A sends it to MAJ.Charlie.D. MAJ.Charlie.D concurs and sends it to LTC.Bravo.E who is on vacation. Three days pass with no notification from LTC.Bravo.E so again PFC.Trooper.A can now send it to the General Staff who will offer final say on the issue.

The order of escalation would be as such:

  1. Originator: PFC.Trooper.A
  2. SL: SGT.Sierra.B
  3. PL: 2LT.Papa.C
  4. CO: MAJ.Charlie.D
  5. Battalion CO: LTC.Bravo.E
  6. General Staff: GEN.Star.F (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.

Exceptions

Exceptions to this document may be made at the discretion of the General Staff depending on the needs of the Regiment.

Retrieved from "https://wiki.7cav.us/index.php?title=Chain_of_Command&oldid=11988"