Chain of Command Escalation - Revision history

Tharen.R at 21:34, 19 February 2024

2024-02-19T21:34:55Z

← Older revision		Revision as of 21:34, 19 February 2024
Line 1:		Line 1:
	[[Category:~~Regulations~~]]		[[Category:Obsolete]]
			{{Obsolete}}
			<center>'''Reason:''' New Page = [[Chain of Command]]</center>

	{{DocRelInfo		{{DocRelInfo
	\|articlenumber = 7CAV-POL-17		\|articlenumber = 7CAV-POL-17

Czar.J: clean up, typos fixed: doesn’t → doesn't (2)

2020-04-23T23:12:56Z

clean up, typos fixed: doesn’t → doesn't (2)

← Older revision		Revision as of 23:12, 23 April 2020
Line 10:		Line 10:
	<br>		<br>

	===Regarding Chain of Command Escalation===		==Regarding Chain of Command Escalation==
	When submitting an issue to your Chain of Command ('''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'''.		When submitting an issue to your Chain of Command ('''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====		===An Example===
	Originator sends an issue to the SL. SGT.Trooper ~~doesn’t~~ get around to answering it in three (3) days so PFC.Lombardi sends it to LT.Smith. LT.Smith reviews it and tells Lombardi it will never get passed and ~~doesn’t~~ send it up. Three days pass and Lombardi sends it to MAJ.Chair. MAJ.Chair concurs and sends it to LTC.Desk who is on vacation. Three days pass with no notification from LTC.Desk so again Lombardi can now send it to General Staff who will offer final say on whatever issue is.		Originator sends an issue to the SL. SGT.Trooper doesn't get around to answering it in three (3) days so PFC.Lombardi sends it to LT.Smith. LT.Smith reviews it and tells Lombardi it will never get passed and doesn't send it up. Three days pass and Lombardi sends it to MAJ.Chair. MAJ.Chair concurs and sends it to LTC.Desk who is on vacation. Three days pass with no notification from LTC.Desk so again Lombardi can now send it to General Staff who will offer final say on whatever issue is.

	The order of escalation would be as such:		The order of escalation would be as such:
Line 24:		Line 24:
	# Regiment GEN.Star (This is the final level)		# Regiment GEN.Star (This is the final level)

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

Czar.J: Czar.J moved page CoC Escalation to Chain of Command Escalation: less abbreviation on main title

2020-04-16T23:55:03Z

Czar.J moved page CoC Escalation to Chain of Command Escalation: less abbreviation on main title

← Older revision	Revision as of 23:55, 16 April 2020
(No difference)

Czar.J at 23:54, 16 April 2020

2020-04-16T23:54:16Z

← Older revision		Revision as of 23:54, 16 April 2020
Line 1:		Line 1:
	[[Category:Regulations]]		[[Category:Regulations]]
	{{DocRelInfo		{{DocRelInfo
	\|articlenumber = 7CAV-R-17		\|articlenumber = 7CAV-POL-17
	\|scope = Chain of Command Escalation		\|scope = Chain of Command Escalation
	\|version = Version 1.0		\|version = Version 1.0

Czar.J at 23:54, 16 April 2020

2020-04-16T23:54:05Z

← Older revision		Revision as of 23:54, 16 April 2020
Line 1:		Line 1:
	[[Category:Regulations]]		[[Category:Regulations]]
	{{DocRelInfo		{{DocRelInfo
	\|articlenumber = 7CAV-R-~~021~~		\|articlenumber = 7CAV-R-17
	\|scope = Chain of Command Escalation		\|scope = Chain of Command Escalation
	\|version = Version 1.0		\|version = Version 1.0

Czar.J at 23:53, 16 April 2020

2020-04-16T23:53:21Z

← Older revision		Revision as of 23:53, 16 April 2020
Line 2:		Line 2:
	{{DocRelInfo		{{DocRelInfo
	\|articlenumber = 7CAV-R-021		\|articlenumber = 7CAV-R-021
	\|scope = ~~CoC~~ Escalation		\|scope = Chain of Command Escalation
	\|version = Version 1.0		\|version = Version 1.0
	\|effectivedate = 14 APR 20		\|effectivedate = 14 APR 20

Czar.J at 23:53, 16 April 2020

2020-04-16T23:53:06Z

← Older revision		Revision as of 23:53, 16 April 2020
Line 1:		Line 1:
	[[Category:Regulations]]		[[Category:Regulations]]
	{{DocRelInfo		{{DocRelInfo
	\|articlenumber = 7CAV-R-~~020~~		\|articlenumber = 7CAV-R-021
	\|scope = CoC Escalation		\|scope = CoC Escalation
	\|version = Version 1.0		\|version = Version 1.0

Czar.J at 11:22, 14 April 2020

2020-04-14T11:22:16Z

← Older revision		Revision as of 11:22, 14 April 2020
Line 12:		Line 12:
	===Regarding Chain of Command Escalation===		===Regarding Chain of Command Escalation===
	When submitting an issue to your Chain of Command ('''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'''.		When submitting an issue to your Chain of Command ('''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====		====An Example====

Czar.J: Created page with "Category:Regulations {{DocRelInfo |articlenumber = 7CAV-R-020 |scope = CoC Escalation |version = Version 1.0 |effectivedate = 14 APR 20 |approvingauthority = Regiment..."

2020-04-14T11:21:49Z

Created page with "Category:Regulations {{DocRelInfo |articlenumber = 7CAV-R-020 |scope = CoC Escalation |version = Version 1.0 |effectivedate = 14 APR 20 |approvingauthority = Regiment..."

New page

[[Category:Regulations]]
{{DocRelInfo
|articlenumber = 7CAV-R-020
|scope = CoC Escalation
|version = Version 1.0
|effectivedate = 14 APR 20
|approvingauthority = Regimental Commanding Officer
|pointofcontact = Regimental Chief of Staff
}}
<br>

===Regarding Chain of Command Escalation===
When submitting an issue to your Chain of Command ('''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 sends an issue to the SL. SGT.Trooper doesn’t get around to answering it in three (3) days so PFC.Lombardi sends it to LT.Smith. LT.Smith reviews it and tells Lombardi it will never get passed and doesn’t send it up. Three days pass and Lombardi sends it to MAJ.Chair. MAJ.Chair concurs and sends it to LTC.Desk who is on vacation. Three days pass with no notification from LTC.Desk so again Lombardi can now send it to General Staff who will offer final say on whatever issue is.

The order of escalation would be as such:
# Originator: PFC.Lombardi.M
# SL SGT.Trooper
# PL LT.Smith
# CO. MAJ.Chair
# Battalion LTC.Desk
# Regiment GEN.Star (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.