1st lvl = Verbal Warning
2nd lvl = Written Warning
3rd lvl = Unit Board
or for members on probation = removal from the unit
[...]disciplinary actions will remain on your record for 3 months, after 3 months, you will lose ONE level [...]
~ Taken from 1.4 S.O.P
Do not argue with the dsciplinary recipiant. Just escalate it to the next level.
"At no point are you to plead your case to the member of command that created the ticket as once it’s created and contested, it is no longer their problem."
Please close this ticlet, if don't want to dispute the disciplinary.Any member of leadership is authorised to create a disciplinary against members of their Command, they are not allowed to create disciplinary actions against anyone outside of their chain of command. They must handle this internally via other command procedures.
Task Force Commander or 2IC (Second In Command) can request HR to open disciplinary ticket.
They will give a reason and who it needs to be issued to.
These are created in the when OP attendance is being processed. They are opend for people who did not put in a ticket prior to the OP.
Exemptions:
If the disciplinary recipient has a valid reason the process needs to be reversed.
Validity decided by Task Force Commander, 2IC or HeadHR, so ping them and wait their respons.
#task-force-hr./add user @username.Please close this ticlet, if don't want to dispute the disciplinary.@usernameAdditionally you have been moved to BCR, so you need to make a Transfer-Ticket to return to your old slot.You have been found to be in breach of unit SOP's 2.2 and 2.3. You have failed to attend the last operation with it being an unauthorized absences.
Your disciplinary is being raised to level 1
Level 1 disciplinary wont affect you in any way and will go away after 3 months, however I want to remind you that it is important in this unit for everyone to notify HR in case that they cant attend.
So that the mission/ training planers can plan for the correct amount.
Additionally you have been moved to BCR, so you need to make a Transfer-Ticket to return to your old slot.
From a welfare perspective is everything okay at the moment and if not is there anything we can do to support you.
https://wiki.taskforcejackal.com/en/arma3/a3dgeneral/a3dsops
You have been found to be in breach of unit SOP's 2.2 and 2.3. You have failed to attend the last event with it being an unauthorized absences.
Your disciplinary level is being raised to 2
**If you failed to attend another operation with out informing us, you will be removed, because you are still on probation.**
Additionally you have been moved to BCR, so you need to make a Transfer-Ticket to return to your old slot.
If you wish to contest this please state it so and it will be escalated.
From a welfare perspective is everything okay at the moment and if not is there anything we can do to support you.
https://wiki.taskforcejackal.com/en/arma3/a3dgeneral/a3dsops
You have been found to be in breach of unit SOP's 2.2 and 2.3. You have failed to attend the last event with it being an unauthorized absences.
Your disciplinary level is being raised to 2
**If you failed to attend another operation with out informing us, one of the following consequences will be decided by a Unit Board.**
- Promotion Ban
- Event Accruement Ban
- Court Marshal
- Removed from specialised role and subsequently your squad
- Removed from the unit
Additionally you have been moved to BCR, so you need to make a Transfer-Ticket to return to your old slot.
If you wish to contest this please state it so and it will be escalated.
From a welfare perspective is everything okay at the moment and if not is there anything we can do to support you.
https://wiki.taskforcejackal.com/en/arma3/a3dgeneral/a3dsops
You have been found to be in breach of unit SOP's 2.2 and 2.3. You have failed to attend the last event with it being an unauthorized absences.
Your disciplinary level is being raised to level **3**
**You will now be removed, because you are still on probation.**
If you wish to contest this please state it so and it will be escalated.
https://wiki.taskforcejackal.com/en/arma3/a3dgeneral/a3dsops
You have been found to be in breach of unit SOP's 2.2 and 2.3. You have failed to attend the last event with it being an unauthorized absences.
Your disciplinary level is being raised to level **3**
**Unit Board will be held, it can resoult in the following consequences.**
- Promotion Ban
- Event Accruement Ban
- Court Marshal
- Removed from specialised role and subsequently your squad
- Removed from the unit
Additionally you have been moved to BCR, so you need to make a Transfer-Ticket to return to your old slot.
If you wish to contest this please state it so and it will be escalated.
https://wiki.taskforcejackal.com/en/arma3/a3dgeneral/a3dsops
As ticket-nummber always use the nummber of the disciplinary ticket.
Event Date = the date of the OP they missedCampaign = The Campaign/ Training they missedAction = Unauthorised AbsenceRefer to the corresponding guids, if unsure on how to use these tables.
The ticket should be closed by the recipant.
So give them ~ 2-4 days before sending the reminder.
If they dont close or respond, remind them with this message
You can the ticket 48h after the reminder message.
If you do not wish to contest this disciplinary.
Close this ticket please.
Otherwise write your reason for contesting the ticket.
Use the same submission tabels to revers the changes.
If you need some one reinstated ping @HeadHR.
The following excerpts might be usfull in edge-cases.
I’d also like to point out, that once you’ve made your decision and issued the disciplinary, AKA you’ve sent the message, that’s you done until HR @‘s you again in the ticket. They aren’t to plead their case to you, or give you bullshit responses, it’s fully taken over by HR if they wish to argue their point across.
/add user Pleb that you’re giving discipline to
/add role Human Resources
Hello <@&1392587671557243031>,
Due to your actions on the operation dated 01/01/01, I am placing you on a level 2 disciplinary as per the units discipline policy.
Example 1 of why what you did is wrong.
Example 2 of why what you did is wrong.
Video footage of you doing something wrong.
Complaint from other member of unit about you doing something wrong.
Please acknowledge your disciplinary or if you feel as though this is wrong, you are free to contest this with a member of HR inside this ticket, not with me.
Link to units SOP’s.
Screenshot of discipline policy.
Polite reminder that anything inside tickets is confidential and not to be discussed with members outside of this ticket, failure to comply with this will result in further disciplinary action.
@Human Resource please process this once @dickhead has acknowledged their disciplinary. (edited)
If you want to jump straight to removal from specialised role, make sure you provide as much detail as possible and why they are not a good fit for that role anymore. If they don’t contest it, it goes through at your discretion, if they contest it, someone else will double check to make sure it’s justified.
Appreciate this is a lot of information so if you still have questions, just give me a shout.
I would also recommend that if you wish to continue with the disciplinary, you make another ticket and start fresh
You have been found to be in breach of unit SOP's 2.2 and 2.3. You have failed to attend the last event with it being an unauthorized absences.
This is your official written warning as per the disciplinary procedure, as your level has been raised to level **2**. If you wish to contest this please state it so and it will be escalated.
Additionally you have been moved to BCR, so you need to make a Transfer-Ticket to return to your old slot
From a welfare perspective is everything okay at the moment and if not is there anything we can do to support you.
https://wiki.taskforcejackal.com/a3dgeneral
For PJs who are not up to snuf
Due to your continued poor attendance you are being removed from 24th STS and placed into Rangers BCR.
Once you improve your attendance you can then request to move into 24th STS or a ranger medic slot.
Please close this ticket.
| Date | Name | Affected parts | Change |
|---|---|---|---|
| 2026-08-26 15:15 | D.Dover | All | Inital Commit |
| 2026-08-27 20:40 | D.Dover | 4. | Added 4.2 |
| 2026-09-28 20:00 | D.Dover | 1. | Added info |