Regimental Events and Meetings
  |
|---|
| This is the Document Release Information | |
| Article Number: | 7CAV-R-030 |
| Scope: | Regimental Events and Meetings |
| Version: | 1.2 |
| Effective Date: | 03OCT20 |
| Last Modified Date: | 31JAN24 |
| Approving Authority: | Regimental Chief of Staff |
| Point of Contact: | Regimental Adjutant General |
Regimental Events and Meetings
Official Regimental events and meetings include, but are not limited to:
- Section Practice (SP)
- Field Training Exercises (FTX)
- S3 Operations
- S7 Classes
- Other Regimental Leadership classes (NCOA, ODS, SAC)
- Command Staff Call (CSC)
- Regimental Meetings
- Other events and meetings as determined by the CoC
Intent
Due to the sheer number of official events, the intent of this document is to define the key official events at the Regimental level and also provide scheduling guidance for all official events to help avoid scheduling conflicts to help maximize attendance by members at all official events.
| Note: *For information about operations, please see S3 – Operations. For information about classes, please see S7 - Training. |
Command Staff Call (CSC)
The Command Staff Call (CSC) is a coordination meeting, and allows key staff and commanders face time to brief the General Staff on all matters pertaining to the operation of their unit, sub-unit, or department. The intent is to discuss any Regimental business, share information, and also get situation reports (SITREP) or status updates from each unit and department. While they used to be run monthly, starting in 2024, they are now run quarterly and combined with the Regimental Meeting to reduce meeting load, but still provide a consistent means for staff to report and communicate information and issues together. They can also be called at the discretion of General Staff.
Required Attendance
Command Staff Calls are open to Sub-Unit and Departmental HQ staff only, or their designate, to brief General Staff monthly as part of the CSC. Someone from each HQ or staff branch element must be in attendance at every meeting. As long as one member of that chain is present, not all members are required to attend. Personnel who are required to attend and consistently miss multiple meetings could face administrative or disciplinary action.
Members who are not required to attend are invited to listen to the meeting, but will not have a speaking role and must remain muted, unless otherwise determined by General Staff. If the CSC is combined with a Regimental Meeting, all members are able to attend, but only staff will have speaking roles.
Below is a list of all personnel who are required to attend.
Regimental Headquarters and Staff Branches
Below are the required staff and RHQ personnel to attend all CSC's.
| Section | Role |
| General Staff | Regimental Commanding Officer |
| Regimental Executive Officer | |
| Regimental Chief of Staff | |
| Regimental Recruiting Oversight Officer | |
| Regimental Adjutant General | |
| Regimental Command Sergeant Major | |
| S1 Personnel Administration | S1 1IC |
| S1 2IC | |
| Security Operations Department | S2 1IC |
| S2 2IC | |
| MP 1IC | |
| MP 2IC | |
| JAG 1IC | |
| S3 Operations | S3 1IC |
| S3 2IC | |
| S6 Information Systems | S6 1IC |
| S6 2IC | |
| Wiki Admin Group | WAG 1IC |
| WAG 2IC | |
| S7 Training | S7 1IC |
| S7 2IC | |
| Recruiting Oversight Office | RTC 1IC |
| RTC 2IC | |
| RRD 1IC | |
| RRD 2IC | |
| S5 1IC | |
| S5 2IC | |
| Officer Development School | ODS Lead |
| Non-Commissioned Officer Academy | NCOA Lead |
| Special Projects Division | Aide to the Chief of Staff |
Combat Unit Requirements
Below are all required personnel to attend CSC's from combat units.
| Section | Role |
| 1st Battalion HQ | Commanding Officer |
| Executive Officer | |
| Sergeant Major | |
| A/1-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| B/1-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| C/1-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| 2nd Battalion HQ | Commanding Officer |
| Executive Officer | |
| Sergeant Major | |
| A/2-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| B/2-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| C/2-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| E/2-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| 3rd Battalion HQ | Commanding Officer |
| Executive Officer | |
| Sergeant Major | |
| A/3-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| B/3-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| Auxiliary Combat Detachment HQ | Commanding Officer |
| Executive Officer | |
| Sergeant Major | |
| A/ACD CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| B/ACD CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| C/ACD CAV | Platoon Leader |
| Platoon Sergeant | |
| SP/SPD | SPD Coordinator |
| Reserves | Reserve 1IC |
| Reserve 2IC |
Meeting Format
The meeting format is at the discretion of the General Staff member running the meeting, but CSC's are generally divided into 6 stages described below. CSC's generally last 1 hour.
| Meeting Stage | Description |
| 1. Attendance/Intro | Opening remarks from General Staff and take attendance. Start recording. |
| 2. Old Business | Address all previous business left from last CSC and report on their progress. |
| 3. Departmental Reports | All Departmental HQ's brief General Staff on the status of their departments, ask questions and propose ideas. |
| 4. Line-unit Reports | All commanders brief General Staff on the status of their unit, raise issues, and ask questions. |
| 5. New Business | General Staff discuss any new Regimental business, announcements, or field questions. |
| 6. Conclusion/Closing Remarks | General Staff thank all attendees, takes any final questions, ends the meeting by dismissing everyone, as well as ending the recording. |
Regimental Meeting
The Regimental Meeting is a quarterly meeting of all 7th Cavalry Gaming Regiment Commanders, Staff, and Troopers. It allows General Staff to brief members on a broad overview of Regimental activities during the quarter. All members are permitted to provide input, questions, or discussion on topics, and it is led by the Chief of Staff or their designate. Once a quarter, they are run on the 3rd Saturday of the month. Starting in 2024, the Regimental Meeting is run as a hybrid meeting that combines both the CSC and Regimental Meeting together. When the CSC and Regimental Meeting are combined into the same meeting, Regimental Meeting policy and requirements supersedes the CSC policy in this document.
Required Attendance
While all members are invited, the Regimental Meeting is only mandatory for the personnel listed below and those that are online at the time of the meeting. Someone from each HQ or staff branch element must be in attendance at every meeting. As long as one member of that chain is present, not all members are required to attend. Personnel who are required to attend and consistently miss multiple meetings could face administrative or disciplinary action.
The Regimental Meeting takes precedence over every other official 7th Cavalry Gaming Regiment event, so members not on the invite list will be asked to join. If a member is online during the meeting in Discord, a game server, Teamspeak 3, or any other official 7CAV medium, they will be ordered to attend the meeting. This is because the Regimental Meeting is an important way for our community to come together, learn about other areas and members of the unit they would not normally interact with, hear from General Staff, and have the opportunity to ask questions or address concerns.
Below is a list of all personnel who are required to attend.
Regimental Headquarters and Staff Branches
Below are required staff and RHQ personnel.
| Section | Role |
| General Staff | Regimental Commanding Officer |
| Regimental Executive Officer | |
| Regimental Chief of Staff | |
| Regimental Recruiting Oversight Officer | |
| Regimental Adjutant General | |
| Regimental Command Sergeant Major | |
| S1 Personnel Administration | S1 1IC |
| S1 2IC | |
| Security Operations Department | S2 1IC |
| S2 2IC | |
| MP 1IC | |
| MP 2IC | |
| JAG 1IC | |
| S3 Operations | S3 1IC |
| S3 2IC | |
| S6 Information Systems | S6 1IC |
| S6 2IC | |
| Wiki Admin Group | WAG 1IC |
| WAG 2IC | |
| S7 Training | S7 1IC |
| S7 2IC | |
| Recruiting Oversight Office | RTC 1IC |
| RTC 2IC | |
| RRD 1IC | |
| RRD 2IC | |
| S5 1IC | |
| S5 2IC | |
| Officer Development School | ODS Lead |
| Non-Commissioned Officer Academy | NCOA Lead |
| Special Projects Division | Aide to the Chief of Staff |
Combat Unit Requirements
Below are all required personnel for Regimental Meetings from combat units.
| Section | Role |
| 1st Battalion HQ | Commanding Officer |
| Executive Officer | |
| Sergeant Major | |
| A/1-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| B/1-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| C/1-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| 2nd Battalion HQ | Commanding Officer |
| Executive Officer | |
| Sergeant Major | |
| A/2-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| B/2-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| C/2-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| E/2-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| 3rd Battalion HQ | Commanding Officer |
| Executive Officer | |
| Sergeant Major | |
| A/3-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| B/3-7 CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| Auxiliary Combat Detachment HQ | Commanding Officer |
| Executive Officer | |
| Sergeant Major | |
| A/ACD CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| B/ACD CAV | Company Commander |
| Executive Officer | |
| First Sergeant | |
| C/ACD CAV | Platoon Leader |
| Platoon Sergeant | |
| SP/SPD | SPD Coordinator |
| Reserves | Reserve 1IC |
| Reserve 2IC |
Meeting Format
The meeting format is at the discretion of the General Staff member running the meeting, but is run as a hybrid meeting of the CSC and Regimental Meeting. This generally combines the departmental and combat unit reporting from CSC's, followed by a question and answer session (through a questionnaire form) that attending members can submit so General Staff can answer in real time. Regimental Meetings typically last 1-2 hours.
Field Training Exercises
A Field Training Exercises or FTX is a coordinated training exercise conducted by a combat line unit or sub-unit. At the Company level, they often resemble an operation, but are intended to still include some training value or coordination of skills from multiple Platoons working together as a Company sized element. They are also conducted at the Platoon level, which are often less formal affairs, so attendance at a Platoon FTX cannot count for operational credit.
- A Company Field Training Exercise (FTX) is required to be run once every two months.
- A Platoon FTX is required to also be run once every two months and alternate months with their respective Company FTX.
- At the discretion of the Company Commander, a Company's required FTX can be run as an official operation. This includes:
- MILPAC credit to attendees
- Eligibility for combat awards
- Requires an official operation announcement posting prior to the FTX
- Should follow all applicable S3 Operations policy such as postings, OPORDs, and AAR's.
- Platoon Field Training Exercises cannot be run as an official operation.
- All FTX's are intended to be posted in the FTX portion of the forums/calendar.
- At the discretion of the Company Commander, other Company wide events, such as (but not limited to) company-wide weapon re-qualification ranges or other Company wide competitions, can also count as a Company FTX but not as an official operation.
Intent
The goal of this policy is to provide an incentive for Troopers to attend their Company FTX, as well as to provide MILPACS credit and award eligibility to events that are already run in extremely similar formats to official operations. It's also to ensure staff are leading and providing in-game content on the battlefield for their respective members.
Event Scheduling Guidance
The following event scheduling guidance is for all game areas of operations (AO) to avoid scheduling conflicts both within and between Battalions, S3, and the S7 Departments. For all game AO's, official events such as Section Practices (SP), Company FTX's, S3 operations, and S7 classes should be scheduled to avoid conflict when possible.
Arma 3 Area of Operations
This section will detail all aspects for the Arma 3 Area of Operations.
Avoiding Conflicts
Arma 3 private server priority will always go to RTC Bootcamps first, followed by Section Practice, Company FTX's, S3 operations, and S7 classes. Please see the Arma 3 Rules of Engagement for additional guidance on private server priority. While it's impossible to avoid conflict altogether, we can make sure that we schedule things in a way to minimize the impact conflicts have.
Before scheduling official Arma 3 events, the person posting it is expected to post it on the 7Cav Events Calendar. This is the tool we use to avoid conflicts.
Reserved Days
Wednesday nights between 2200 Zulu (5 PM Eastern) and 0200 Zulu Thursday (9 PM Eastern) are reserved for the following activities:
Friday nights between 2300 Zulu (6 PM Eastern) and 0200 Zulu Saturday (9 PM Eastern) are reserved for the following activities:
Saturdays between 1900 Zulu (2PM Eastern) and 2300 Zulu Saturday (6 PM Eastern) are reserved for the following activities:
Sundays between 1800 Zulu (1PM Eastern) and 0300 Zulu Monday (10 PM Eastern) are reserved for the following activities:
Arma 3 S7 Classes
All S7 classes are considered a low priority and free to be scheduled outside of the above reserved times. When scheduling at the same time as any of the above events cannot be avoided, please first get permission from S7 HQ.
Hell Let Loose Area of Operations
The following event scheduling guidance is for the Hell Let Loose area of operations to avoid scheduling conflicts between 2nd Battalion, S3, and the S7 Departments. Hell Let Loose operations, section practices, company FTX's, S7 classes, and other Hell Let Loose events should be scheduled to avoid conflict when possible.
Avoiding Conflicts
Hell Let Loose private server priority will go to section practices first, followed by: company FTX's, S3 operations, and S7 classes. While it's impossible to avoid conflict altogether, we can make sure that we schedule things in a way to minimize the impact conflicts have.
Before scheduling official Hell Let Loose events, the person posting it is expected to post it on the 7Cav Events Calendar. This is the tool we use to avoid conflicts.
Reserved Days
Tuesday Nights between 2359 Zulu (8 PM Eastern) and 0100 Zulu (9 PM Eastern) are reserved for the following activities:
Saturdays between 1900 Zulu (2PM Eastern) and 2100 Zulu Saturday (4 PM Eastern) are reserved for the following activities:
Hell Let Loose S7 Classes
All S7 classes are considered a low priority and free to be scheduled outside of the above reserved times. When scheduling at the same time as any of the above events cannot be avoided, please first get permission from S7 HQ.
Intent
Effective use of this guidance for deconfliction will create a more streamlined and organized experience for all members that maximizes attendance at all official events.
Failure to Attend Regimental Leadership Classes
Departmental Leads that teach leadership classes at the Regimental level (ODS, NCOA, SAC) have the authority to suspend students for a period of time that fail to show up to a scheduled class without notice or fail to complete assignments without notice at their discretion. This includes the ODS Lead, NCOA Lead, and MP 1IC. This is out of respect for the Instructors that volunteer their valuable time to teach these courses.
ODS Suspension Policy
Per 7CAV-R-030, the following policy will apply to any candidate who, without notification to the ODS lead via PM, fails to attend any day of ODS or does not submit their assignments. Other integrity violations such as conduct concerns, cheating, etc. will be handled on a case-by-case basis.
First offense: Suspended for the next ODS cycle, Battalion staff notified
Second offense: Consult Chief of Staff
7th Cavalry Furlough Policy
The purpose of Furlough in the Cav is to provide those members who provide daily support to the Regiment time off, free from their normal duties during the holidays of Christmas and New Years. Our hope is to allow our dedicated volunteers a break to spend this important time with friends and family, recharge, and come back refreshed for the new year.
Definition of Furlough
Furlough is a period of 2-3 weeks, starting on the Saturday one week before Christmas Day, and ending the first Friday after New Years Day. There will be an announcement post made by the Chief of Staff or their designate in the forums stating the dates of Furlough each year. There will be a Regimental Meeting to end the year and kick off Furlough on the Saturday that starts Furlough.
During this 2-3 week period the entire Regiment, including all Battalions, Support and Secondary Departments, are shut down and all duties and responsibilities are temporarily suspended. In addition to this work stoppage, there are no official events, training classes, operations, roll calls, or section practices unless they meet the following conditions:
- Approval from the General Staff is required.
- Any work required from secondary or support departments must be agreed to and coordinated at least 2 weeks prior to Furlough.
- Any required work for such events must be voluntary; Command Authorities are prohibited from requiring their members to work during Furlough.
- Any award submissions for Operations or Events that occur during Furlough are not to be submitted until Furlough has ended.