Posted on Dec 7, 2025
If your unit gets tasked, but your CoC isn't tracking it and hasn't notified you, what defense do you have if someone tries to punish you?
1.5K
12
3
4
4
0
On a Saturday, at 1237pm, a DA 6 is digitally sent from BDE. Your unit is tasked with a duty but NO ONE in your unit CoC is tracking nor has anyone from BN/BDE notified you. Not one call. Not one text. Nada. Zip. Zilch.
If someone higher decides to bring the heat on you, what defense do you have?
If someone higher decides to bring the heat on you, what defense do you have?
Edited 8 d ago
Posted 8 d ago
Responses: 2
Edited 8 d ago
Posted 8 d ago
Message sent does not equal message received. THAT is the defense. If you don't get an acknowledgement, you haven't issued an order. Here's an illustration of that from Hitchhiker:
“But the plans were on display…”
“On display? I eventually had to go down to the cellar to find them.”
“That’s the display department.”
“With a flashlight.”
“Ah, well, the lights had probably gone.”
“So had the stairs.”
“But look, you found the notice, didn’t you?”
“Yes,” said Arthur, “yes I did. It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard.”
That said, like COL Cudworth is saying, if you had a duty to monitor whatever communications channel they used to transmit the order on Saturday, you're in the wrong, even if them actually using the channel on the weekend is rare.
“But the plans were on display…”
“On display? I eventually had to go down to the cellar to find them.”
“That’s the display department.”
“With a flashlight.”
“Ah, well, the lights had probably gone.”
“So had the stairs.”
“But look, you found the notice, didn’t you?”
“Yes,” said Arthur, “yes I did. It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard.”
That said, like COL Cudworth is saying, if you had a duty to monitor whatever communications channel they used to transmit the order on Saturday, you're in the wrong, even if them actually using the channel on the weekend is rare.
(4)
Comment
(0)
Edited 7 d ago
Posted 8 d ago
I think the elements in your question are the possible key to your rebuttal.
First, the question needs a bit more context about why your higher would take anyone to task. From your wording, my assumptions are:
• The duty was not performed;
• The digital message was an email;
• The timestamp of the email is from an after-the-fact dive through the mailbox it was sent to after your unit received a "WTF!?" type of call from your higher headquarters.
Going with those assumptions:
• Was the message sent to your unit through the normal/official channels (whatever they may be via SOP) or was it sent through a nonstandard/unofficial route?
• Was the message sent to a 'group inbox' that is regularly checked or was it sent to an individual (aka 'single point of failure') that wasn't available (leave? out of communications?)
• If it was sent to an unavailable individual, did higher know that 'single point of failure' would be unavailable (i.e., they were notified that certain senior leadership was on leave or an out of office response was turned on)?
Obviously there was a screw-up somewhere between the decision by higher to task your unit and the tasking being accepted by your unit. It comes down to if the standard process was followed or not. If it was, what was the unanticipated glitch in the system?
Bottom line: Did higher do what they were supposed to do and did your unit do what they were supposed to do? If the answer is that they both did appropriate actions, then you have identified a shortfall in the process and it needs to be addressed, minus the finger pointing (for example, if it isn't standard for formal taskings to be acknowledge, then a tracking should be set up to ensure that "message sent" isn't mistaken for "message received").
However, IF the message was sent via the standard/official route, such as a group mailbox that on-duty personnel were supposed to be checking or the operations NCO's personal account, and the personnel at your unit didn't do what they were supposed to do (nobody checked the group mailbox ... the Operations NCO was on leave but nobody told the higher headquarters to send messages to someone else and/or the Ops NCO didn't turn on an out of office response) ... Throw yourself on the mercy of the court.
First, the question needs a bit more context about why your higher would take anyone to task. From your wording, my assumptions are:
• The duty was not performed;
• The digital message was an email;
• The timestamp of the email is from an after-the-fact dive through the mailbox it was sent to after your unit received a "WTF!?" type of call from your higher headquarters.
Going with those assumptions:
• Was the message sent to your unit through the normal/official channels (whatever they may be via SOP) or was it sent through a nonstandard/unofficial route?
• Was the message sent to a 'group inbox' that is regularly checked or was it sent to an individual (aka 'single point of failure') that wasn't available (leave? out of communications?)
• If it was sent to an unavailable individual, did higher know that 'single point of failure' would be unavailable (i.e., they were notified that certain senior leadership was on leave or an out of office response was turned on)?
Obviously there was a screw-up somewhere between the decision by higher to task your unit and the tasking being accepted by your unit. It comes down to if the standard process was followed or not. If it was, what was the unanticipated glitch in the system?
Bottom line: Did higher do what they were supposed to do and did your unit do what they were supposed to do? If the answer is that they both did appropriate actions, then you have identified a shortfall in the process and it needs to be addressed, minus the finger pointing (for example, if it isn't standard for formal taskings to be acknowledge, then a tracking should be set up to ensure that "message sent" isn't mistaken for "message received").
However, IF the message was sent via the standard/official route, such as a group mailbox that on-duty personnel were supposed to be checking or the operations NCO's personal account, and the personnel at your unit didn't do what they were supposed to do (nobody checked the group mailbox ... the Operations NCO was on leave but nobody told the higher headquarters to send messages to someone else and/or the Ops NCO didn't turn on an out of office response) ... Throw yourself on the mercy of the court.
(3)
Comment
(0)
MSG (Join to see)
7 d
The email was sent to all Command Teams within the BN here. After speaking with my BN Assistant S3, even his office was not tracking this Tasker from BDE. The person that sent the email (the NCOIC for BDE S3) didn't follow proper protocol in sending the Duty Roster in a Formal Tasker. It was just a boom, here is the DA 6.
My unit is so small....I only have 7 pax (including myself) that I can't afford to have 24 hour Ops.
Luckily, I was able to get this issue resolved.
My unit is so small....I only have 7 pax (including myself) that I can't afford to have 24 hour Ops.
Luckily, I was able to get this issue resolved.
(1)
Reply
(0)
Read This Next


Duty
Company Commander
1SG
CSM
Battalion Commander
