Posted on Oct 10, 2024
How can I respectfully request to have my DD 368 process expedited?
4.86K
21
9
7
7
0
I am currently working on my DD 368. Current reservist with ETS 12/2025, want to go Active AMEDD -got AMEDD board approval for 66S. However, having a restart to my DD 368.
Reason: I first submitted my DD368 almost 8 months ago. Last month (08/2024) my S1 deleted the request. His reason "I though you no longer needed it"
No i have to resubmit it - square 1.
What can i do to expedite it?
Respectfully seeking any guidance.
Reason: I first submitted my DD368 almost 8 months ago. Last month (08/2024) my S1 deleted the request. His reason "I though you no longer needed it"
No i have to resubmit it - square 1.
What can i do to expedite it?
Respectfully seeking any guidance.
Posted 13 d ago
Responses: 2
The first step that should be done is have the S1 (or someone else in their section with a HR professional account) submit a CRM to see if the PAR for the DD368 can still be recovered. If not, then you'll have to restart the PAR.
If that's the situation, then about the only influence you hold in expediting the new request is to leverage the mistake your S1 committed and get their assistance in pushing it through the process (that and fully understanding the process and what should be done at each level).
Typically DD368s take about three to six months in the USAR, although it SHOULD be processed within 90 days according to AR 140-10*. The current OCAR guidance* (still in effect from the previous Chief of the Army Reserve, LTG Daniels) is that Conditional Releases are to be processed expeditiously (not necessarily 'approved', just processed).
As your DD368 was almost eight months old, I have to assume that either a) it was stalled somewhere and not being acted upon or b) it had encountered a few snags in the processing but was towards the end of the approval process.
So, if the PAR cannot be recovered, create and submit a new one and make absolutely sure that everything required is included in it (refer to the OCAR memo). Once submitted, notify the S1 so they can do everything to get it out of the unit to your higher headquarters for processing. After that, periodically check on it and if it isn't moving, start tapping on your S1's shoulder to check on their end (occasionally remind about the deleted action that was eight months in processing).
-------------------------------------------
* AR 140-10 (Assignments, Attachments, Details, and Transfers) - https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN30735-AR_140-10-000-WEB-1.pdf
* Memorandum, OCAR, DAAR-HR, 4 Apr 17, Subject: Army Reserve Conditional
Release Policy - https://www.usar.army.mil/Portals/98/CAR%20Policy%2020-01%20Army%20Reserve%20Conditional%20Release%20Policy%20-%2023%20Dec%2020.pdf
If that's the situation, then about the only influence you hold in expediting the new request is to leverage the mistake your S1 committed and get their assistance in pushing it through the process (that and fully understanding the process and what should be done at each level).
Typically DD368s take about three to six months in the USAR, although it SHOULD be processed within 90 days according to AR 140-10*. The current OCAR guidance* (still in effect from the previous Chief of the Army Reserve, LTG Daniels) is that Conditional Releases are to be processed expeditiously (not necessarily 'approved', just processed).
As your DD368 was almost eight months old, I have to assume that either a) it was stalled somewhere and not being acted upon or b) it had encountered a few snags in the processing but was towards the end of the approval process.
So, if the PAR cannot be recovered, create and submit a new one and make absolutely sure that everything required is included in it (refer to the OCAR memo). Once submitted, notify the S1 so they can do everything to get it out of the unit to your higher headquarters for processing. After that, periodically check on it and if it isn't moving, start tapping on your S1's shoulder to check on their end (occasionally remind about the deleted action that was eight months in processing).
-------------------------------------------
* AR 140-10 (Assignments, Attachments, Details, and Transfers) - https://armypubs.army.mil/epubs/DR_pubs/DR_a/ARN30735-AR_140-10-000-WEB-1.pdf
* Memorandum, OCAR, DAAR-HR, 4 Apr 17, Subject: Army Reserve Conditional
Release Policy - https://www.usar.army.mil/Portals/98/CAR%20Policy%2020-01%20Army%20Reserve%20Conditional%20Release%20Policy%20-%2023%20Dec%2020.pdf
(7)
(0)
COL Randall C.
SPC (Join to see) - Sounds like you are likely to have a determination by the GO commander within 30 days or so. Keep in touch with the AMEDD recruiter on seat vacancy so you can balance how much you should be pushing (or having your S1 push for you).
(1)
(0)
SPC (Join to see)
COL Randall C. thank you so much for the guidance sir. I will continue keeping an eye on the IPPS-A tracker and loop in the recruiter.
I have another question Sir.
On the IPPS-A tracker, it shows the individuals where the document is currently at including their contacts and email (some of them). Would you advise I send a follow-up email?
I have another question Sir.
On the IPPS-A tracker, it shows the individuals where the document is currently at including their contacts and email (some of them). Would you advise I send a follow-up email?
(1)
(0)
COL Randall C.
SPC (Join to see) - In a word - No. Give the process time to ... process.
The caveat to that is if it has been "stuck" with that individual for much longer than it should be (discuss with your S1 to determine what the process is at that level). In that situation it's acceptable to send an inquiry to them checking on the status.
The caveat to that is if it has been "stuck" with that individual for much longer than it should be (discuss with your S1 to determine what the process is at that level). In that situation it's acceptable to send an inquiry to them checking on the status.
(1)
(0)
SPC (Join to see)
1SG (Join to see) it is still unresolved sir. As advised, I'm still waiting. Any guidance would be greatly appreciated
(0)
(0)
Read This Next