Difference between revisions of "7CAV-BATT2-001"

From 7th Cavalry Wiki
Jump to navigation Jump to search
m
(1939)
Line 1: Line 1:
 
{{DocRelInfo
 
{{DocRelInfo
−
|articlenumber = 7CAV-BATT2-001
+
|articlenumber = 7CAV-BATT2-Policies
−
|scope = AWOL Tracking and Discharges
+
|scope = Battalion Specific Policies
−
|version = Version 1.0
+
|version = Version 1.0
−
|effectivedate = 20APR20
+
|effectivedate = 20APR20
−
|approvingauthority = 2BN Commanding Officer
+
|approvingauthority = 2BN Commanding Officer
−
|pointofcontact = 2BN Executive Officer
+
|pointofcontact = 2BN Executive Officer
 
}}
 
}}
 
'''''THIS DOCUMENT MAY NOT BE EDITED WITHOUT 2-7 COMMANDER APPROVAL.'''''
 
'''''THIS DOCUMENT MAY NOT BE EDITED WITHOUT 2-7 COMMANDER APPROVAL.'''''
  
−
=AWOL Tracking and Discharges=
+
=2BN Reporting Deadlines=
 +
All 2BN reporting must be consistent with the following reporting policy as a minimum. Company Staff may impose stricter guidelines at their discretion.
  
−
* '''Posting the AWOL List:'''
+
'''The 7th Cavalry Week'''
−
** Go to the [https://7cav.us/awoltracker AWOL Tracker].
+
* The 7th Cavalry week officially starts every Saturday and ends every Friday.
−
** Tick the box next to any name that is showing 3 days or more under Days AWOL.
+
** This means Roll Call postings and Section Practice attendance for that given week can only fall between Saturday to Friday to count for that week in order for a trooper to be considered accounted for that week.
−
** Go to the [https://7cav.us/forums/2nd-battalion-loa-tracking.54/ 2nd Battalion LOA Tracking] forum.
 
−
*** Check each name you have ticked to see if they are on LOA or had an LOA ending sometime in the period they have been AWOL. If they do, remove the tickmark beside their name as they should not be accounted for as AWOL.
 
−
** Go to the bottom of the list and ensure 2nd Bat is chosen in the dropdown list.  
 
−
** Tick the radio button that says Create AWOL reminder post.
 
−
** Click the Send PM button.
 
−
* This creates the AWOL list found in the [https://7cav.us/forums/absent-without-leave.37/ Absent Without Leave] forum.
 
−
** Go to [https://7cav.us/rosters/ MILPACS].
 
−
** Scroll down to the New Recruits section
 
−
** Check the forum account of any Private you find there to see when they last posted.
 
−
*** If it is more than 2 weeks ago, you will have to manually add them to the AWOL list you have created.
 
−
*** Remember that if you add an @troopername.initial to your list, it will not actually alert them.
 
−
**** So in a reply @ them so they get the alert.
 
−
* '''Sending AWOL Reminder PM's:'''
 
−
** After creating AWOL post
 
−
** Select Create AWOL reminder PM and click the Send PM button. This will send a PM to each of the individuals on the list reminding them to post or reply back to you.
 
−
*** Manually PM anyone you had to manually add to the list reminding them to post or get back to you.
 
−
* '''Discharge AWOL Members:'''
 
−
** The Sunday following, the AWOL post, you will discharge AWOL members who are still AWOL and/or who have not replied to your PM to them as to their status.
 
−
*** Remember that discharging someone AWOL has the negative impact of them losing 2 grades upon re-enlistment, so if someone replies to you requesting a discharge, discharge them separately with an Honorable Discharge.
 
−
** Go to the [https://7cav.us/awoltracker/ AWOL Tracker].
 
−
** Tick the box to the right of every name on your list if it is still on the AWOL Tracker.
 
−
*** If it isn't it's because they have made a post.
 
−
** Go to the bottom of the list and ensure 2nd Battalion is chosen in the dropdown list.
 
−
** Tick the radio button that says Create AWOL discharge post
 
−
** Click the Send PM button.
 
−
** This will create a discharge post in the [https://7cav.us/forums/discharged-from-the-regiment.38/ Discharged from the Regiment] forum.
 
−
** Go to that new discharge post and manually add the names you had to manually add to the AWOL list.
 
−
*** Ensure you include a MILPACS link to their names.
 
  
−
==All 2nd Battalion SOP's==
+
'''Roll Call Deadline'''
−
{{2BNSOP}}
+
* Squad/Section Roll Calls (RC) are always due to be posted by the appropriate staff by no later than Sunday at 0100Z (2000 Central).
 +
 
 +
'''Squad/Section Leader After Action Report (AAR) Deadline'''
 +
* Squad/Section Leader AAR's are to be submitted by no later than Monday at 0700Z (0200 Central).
 +
 
 +
'''Platoon Leader and Platoon Sergeant Note Deadline'''
 +
* Platoon Leader and Platoon Sergeant notes are to be submitted by no later than Wednesday at 0700Z (0200 Central).
 +
 
 +
'''Company Commander and Company First Sergeant Note Deadline'''
 +
* Company Commander and Company First Sergeant notes are to be submitted by no later than Friday at 0700Z (0200 Central).
 +
 
 +
=FTX Policy=
 +
 
 +
'''Policy Overview'''
 +
* 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
 +
 
 +
===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.<br>
 +
First-time Qualifiers > Members of the hosting Company > Members of the AO > All other applicants
 +
The Qualifications are to be posted in the [https://7cav.us/forums/general-announcements.376/ General Announcements] sections of the forums. <br>
 +
<b>DO NOT</b> post them in Class Announcements.
 +
 
 +
=Leadership Accountability Policy and Procedure=
 +
 
 +
The Platoon Sergeant and Platoon Leader 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 Commander, Executive Officer and First Sergeant
 +
 
 +
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 Commander, Executive Officer and Sergeant Major
 +
 
 +
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.
 +
 
 +
*Monthly:
 +
**Deliver a development session of a Company Commander (CO/XO) and First Sergeant (BSM)
 +
**Attend the Command Staff Call
 +
 
 +
*Quarterly:
 +
**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.
 +
 
 +
==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.

Revision as of 21:04, 22 September 2022

This is the Document Release Information
Article Number: 7CAV-BATT2-Policies
Scope: Battalion Specific Policies
Version: Version 1.0
Effective Date: 20APR20
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.

2BN Reporting Deadlines

All 2BN reporting must be consistent with the following reporting policy as a minimum. Company Staff may impose stricter guidelines at their discretion.

The 7th Cavalry Week

  • The 7th Cavalry week officially starts every Saturday and ends every Friday.
    • This means Roll Call postings and Section Practice attendance for that given week can only fall between Saturday to Friday to count for that week in order for a trooper to be considered accounted for that week.

Roll Call Deadline

  • Squad/Section Roll Calls (RC) are always due to be posted by the appropriate staff by no later than Sunday at 0100Z (2000 Central).

Squad/Section Leader After Action Report (AAR) Deadline

  • Squad/Section Leader AAR's are to be submitted by no later than Monday at 0700Z (0200 Central).

Platoon Leader and Platoon Sergeant Note Deadline

  • Platoon Leader and Platoon Sergeant notes are to be submitted by no later than Wednesday at 0700Z (0200 Central).

Company Commander and Company First Sergeant Note Deadline

  • Company Commander and Company First Sergeant notes are to be submitted by no later than Friday at 0700Z (0200 Central).

FTX Policy

Policy Overview

  • 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

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

The Platoon Sergeant and Platoon Leader 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 Commander, Executive Officer and First Sergeant

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 Commander, Executive Officer and Sergeant Major

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.
  • Monthly:
    • Deliver a development session of a Company Commander (CO/XO) and First Sergeant (BSM)
    • Attend the Command Staff Call
  • Quarterly:
    • 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.

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.

Retrieved from "https://wiki.7cav.us/index.php?title=7CAV-BATT2-001&oldid=8752"