Chain of Command Escalation
|
This SOP page is no longer relevant. This could be due to historical changes, the page is out of date, or been replaced. Please view our Standard Operating Procedures page for the relevant SOP's. |
|
| This is the Document Release Information | |
| Article Number: | 7CAV-POL-17 |
| Scope: | Chain of Command Escalation |
| Version: | Version 1.0 |
| Effective Date: | 14 APR 20 |
| Last Modified Date: | DDMMMYYYY |
| Approving Authority: | Regimental Commanding Officer |
| Point of Contact: | Regimental Chief of Staff |
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.
