7CAV-BATT2-001

This is the Document Release Information
Article Number:	7CAV-BATT2-001
Scope:	2nd Battalion Policies
Version:	Version 1.0
Effective Date:	01OCT22
Last Modified Date:	DDMMMYYYY
Approving Authority:	2BN Commanding Officer
Point of Contact:	2BN Executive Officer

This is the Document Release Information
Article Number:	7CAV-BATT2-001
Scope:	2nd Battalion Policies
Version:	Version 1.0
Effective Date:	01OCT22
Last Modified Date:	DDMMMYYYY
Approving Authority:	2BN Commanding Officer
Point of Contact:	2BN Executive Officer

This is the Document Release Information
Article Number:	7CAV-BATT2-001
Scope:	2nd Battalion Policies
Version:	Version 1.0
Effective Date:	01OCT22
Last Modified Date:	DDMMMYYYY
Approving Authority:	2BN Commanding Officer
Point of Contact:	2BN Executive Officer

THIS DOCUMENT MAY NOT BE EDITED WITHOUT 2-7 COMMANDER APPROVAL.

Event Policy

FTX

• At the discretion of the Company Commander, a company's required FTX may be run as an official operation.
• Any operations seeking official credit must follow all regimental SOPs, with the exception of slotting priority given to members of the Company at the discretion of the Company Staff in order to best facilitate the training.
• At the discretion of the Company Commander, Platoon FTXs may be run in place of a Company FTX, but are not eligible for official operational credit.
• FTXs may be credited as SP at the discretion of Company Commander
• FTX scheduling reservations will be given in the following order taking precedent over all S3 and S7 events.

• 1st weekend (Starting on Friday) of even months will be reserved for Charlie Company

Last weekend (Starting on Friday) of even months will be reserved for Alpha Company 3rd weekend (starting on Friday) of odd months will be reserved for Bravo Company

• Companies may schedule outside there reserved weekends, however, must not conflict with any other FTX within 2-7.

Weapon Qualifications

• Weapons Qualifications must be run by either Platoon or Company Staff, this includes being the instructor, grader, and poster of the final qualifications on the forums.
• Anyone may requalify for skills 90 days after their previous qualification date for that specific award.
• The actual qualification test should be kept at the Company and Platoon level and never passed down any lower in the CoC. Troopers may only know the targets right before the test is executed.
• Platoon or Companies can run weapon qualifications as frequently as they would like.
• The priority of members attending the qualifications goes as follows.
  

First-time Qualifiers > Members of the hosting Company > Members of the AO > All other applicants

The Qualifications are to be posted in the General Announcements sections of the forums.
DO NOT post them in Class Announcements.

Leadership Accountability Policy and Procedure

Platoon Staff

The Platoon Leader and Platoon Sergeant shall ensure they update the Battalion Accountability Tracker each week by 2359Z (1859 Central) Friday, being the end of each Cav Week, with the following elements of their job description (addressed during the Initial Counseling Statement):

• Weekly:
  • Attend a 1Hr Section Practice activity.
  • Participate in 1Hr Public Server activity.

• Monthly:
  • Deliver a development session of a section leader or assistant section leader.
  • Publish a monthly training plan.

• Quarterly:
  • Recommend the “Of the Quarter” by the 4th of the new quarter, in conjunction with Company Staff.

All entries must be supplemented by a response to the thread in which the Accountability Tracker is displayed for the full view of the entire Battalion, to illustrate what specific requirement they have met and demonstrate their activity to their troopers.

Company Staff

The Company Commander, Executive Officer and First Sergeant shall ensure they update the Battalion Accountability Tracker each week by 2359Z (1859 Central) Friday, being the end of each Cav Week, with the following elements of their job description (addressed during the Initial Counseling Statement):

• Weekly:
  • Attend a 1Hr Section Practice activity.
  • Participate in 1Hr Public Server activity.

• Monthly:
  • Deliver a development session of a Platoon Sergeant (1SG), Platoon Leader (XO and CO), Executive Officer (CO, if a PL is not developed that month)
  • Attend the Command Staff Call

• Bi-Monthly
  • Deliver a Field Training Exercise once every two months in accordance with Regimental / Battalion Policy – to include one being public each quarter.

• Quarterly:
  • Recommend the “Of the Quarter” by the 4th of the new quarter, in conjunction with Platoon Staff.
  • Host a weapons qualification for the company.
  • Attend the Regimental Meeting

All entries must be supplemented by a response to the thread in which the Accountability Tracker is displayed for the full view of the entire Battalion, to illustrate what specific requirement they have met and demonstrate their activity to their troopers.

Battalion Staff

The Battalion Commander, Executive Officer and Sergeant Major shall ensure they update the Battalion Accountability Tracker each week by 2359Z (1859 Central) Friday, being the end of each Cav Week, with the following elements of their job description (addressed during the Initial Counseling Statement):

• Weekly:
  • Attend a 1Hr Section Practice activity
  • 1 Hr of public play

• Monthly:
  • Deliver a development session of a Company Commander (CO/XO) and First Sergeant (BSM)
  • Attend the Command Staff Call
  • Attend 1 Op or S7 Class

• Quarterly:
  • Attend the Regimental Meeting
  • Audit of the BattleMetrics Admins/VIP roles

All entries must be supplemented by a response to the thread in which the Accountability Tracker is displayed for the full view of the entire Battalion, to illustrate what specific requirement they have met and demonstrate their activity to their troopers.

Proposal Escalation SOP

All proposals must meet the minimum requirements set out by the regiment. Additional requirements of a billet may only ever be added to the requirements sent out by regiment, you may not remove requirements that are set by the regiment.

The proposal must be considered reasonable by every link in the Chain of Command impacted up to and including the Battalion Commander when applicable.

What is considered "reasonable" is up to the staff to decide, but the following should be considered.

• Does the proposal have buy-in from those who will be executing said proposal?
• Does this fit the within scope of the chain of command or possibly infringe on other departments in some way?
• How much additional paperwork, tracking, or bureaucracy does this add to the position and adjacent positions?
• How will the benefit to the unit upon execution be tracked for cost/benefit analysis?

Use these and any other relevant questions to consider if the proposed change is a good fit.

Procedure

A written proposal can be created from anywhere in the chain from Battalion Commander to Assistant Squad Leader. The proposal must then be sent up the Chain of Command and approved at every appropriate level up to the Battalion Commander when applicable. Once it reaches the Battalion Commander they have the final authority of the approval and content of the proposal. They may make any changes they see fit or deny it all together. If the proposal is approved the expectation will be its execution with failure resulting in potential counseling.

Timeline

A written response to a proposal is required within a three day period. A response does not equate to a decision, however, a decision or escalation must be made within a reasonable timeframe. If after a three day period there is no response, the proposer may bump the proposal in writing to their respective CoC. If no response is granted after a bump and an additional four day period (total of one week since initial proposal), the proposer may elevate the proposal to the next level of the CoC. If a proposal is denied by any level of the CoC, the proposer may consider elevating the request, however, this should be avoided whenever possible as only in extreme cases will the next level in the CoC overturn a decision by lower level leaders.