2BN Proposal Escalation SOP - Revision history

Cameron.J at 13:08, 23 May 2025

2025-05-23T13:08:51Z

← Older revision		Revision as of 13:08, 23 May 2025
Line 4:		Line 4:
	\|version = Version 1.0		\|version = Version 1.0
	\|effectivedate = 01OCT22		\|effectivedate = 01OCT22
	\|lastmodifieddate = ~~08SEP2023~~		\|lastmodifieddate = 23MAY2025
	\|approvingauthority = 2BN Commanding Officer		\|approvingauthority = 2BN Commanding Officer
	\|pointofcontact = 2BN Executive Officer		\|pointofcontact = 2BN Executive Officer

Cameron.J at 13:05, 23 May 2025

2025-05-23T13:05:03Z

← Older revision		Revision as of 13:05, 23 May 2025
Line 29:		Line 29:
	==Timeline==		==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.		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.

			==Proposal Template==
			*This is a suggested template:

			'''Prepared By:'''

			<Name(s) of participants who are involved in this proposal>

			'''Problem:'''

			<Short description of the problem>

			'''Actions / Request:'''

			<Describe what is needed to get the result desired>

Murdock.T: Created one of multiple separate pages for the individual SOP sections for 2-7

2025-05-07T13:39:42Z

Created one of multiple separate pages for the individual SOP sections for 2-7

New page

{{DocRelInfo
|articlenumber = 7CAV-BATT2-004
|scope = Proposal Escalation SOP
|version = Version 1.0
|effectivedate = 01OCT22
|lastmodifieddate = 08SEP2023
|approvingauthority = 2BN Commanding Officer
|pointofcontact = 2BN Executive Officer
}}
'''''THIS DOCUMENT MAY NOT BE EDITED WITHOUT 2-7 COMMANDER APPROVAL.'''''

=Proposal Escalation=
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.