MARADMIN 436/26
REPORTING AND MANAGEMENT OF PERSONNEL TEMPO (PERSTEMPO)
R 211800Z SEP 26 MARADMIN 436/26 MSGID/GENADMIN/CMC WASHINGTON DC MRA MP// SUBJ/REPORTING AND MANAGEMENT OF PERSONNEL TEMPO (PERSTEMPO)// REF/A/MSGID/DOC/DOWI/20201228// REF/B/MSGID/LTR/CMC 1050/20250404// REF/C/MSGID/MSG/CMC WASHINGTON DC CMC/111635ZJUN01// REF/D/MSGID/MSG/CMC WASHINGTON DC CMC/291635ZOCT01// REF/E/MSGID/MSG/CMC WASHINGTON DC MP/101315ZOCT03// REF/F/MSGID/MSG/CMC WASHINGTON DC MP/030909ZNOV04// REF/G/MSGID/DOC/MCTFSPRIUM/20080819// REF/H/MSGID/DOC/TITLE 10 U.S. CODE 991// REF/I/DOC/DOWI/20260630// NARR/REF A IS DOWI 1336.07, MANAGEMENT OF PERSONNEL TEMPO (PERSTEMPO). REF B IS DELEGATION OF AUTHORITY TO DEPUTY COMMANDANT FOR MANPOWER AND RESERVE AFFAIRS ON PERSTEMPO WAIVERS. REF C IS ALMAR 026/01, MARINE CORPS DEPLOYMENT TEMPO (DEPTEMPO) POLICY GUIDANCE, CANCELLED PER THIS MARADMIN. REF D IS ALMAR 052/01, MARINE CORPS DEPLOYMENT TEMPO (DEPTEMPO) POLICY GUIDANCE AMPLIFICATION, CANCELLED PER THIS MARADMIN. REF E IS MARADMIN 481/03, DEPLOYMENT TEMPO (DEPTEMPO) AND OVERSEAS CONTROL DATE (OCD) POLICY, CANCELLED PER THIS MARADMIN. REF F IS MARADMIN 484/04, DEPLOYMENT TEMPO (DEPTEMPO) UNDER REPORTING CORRECTIVE ACTION, CANCELLED PER THIS MARADMIN. REF G IS THE MARINE CORPS TOTAL FORCE SYSTEM PERSONNEL REPORTING INSTRUCTIONS USERS’ MANUAL (MCTFSPRIUM). REF H IS THE UNITED STATES CODE GOVERNING THIS PROGRAM. REF I IS DOWI 1327.06, MILITARY LEAVE, LIBERTY, AND ADMINISTRATIVE ABSENCE.// POC/SEE PARAGRAPH 8.c.// GENTEXT/REMARKS/1. Purpose. This MARADMIN provides a comprehensive summary of reference (a) to ensure all Marines understand the key components, responsibilities, and procedures of the Personnel Tempo (PERSTEMPO) policy, to include guidance for processing PERSTEMPO waivers. 2. Cancelation. The publication of this MARADMIN officially cancels references (c), (d), (e), and (f). 3. PERSTEMPO is the amount of time individual Service members, not units, are engaged in official duties that make it infeasible for them to spend off-duty time in the housing in which they normally reside. Tracking PERSTEMPO events maintains visibility of a Service member’s time away to minimize, within operational constraints, negative impacts to readiness, quality of life, and retention. 3.a. Members of the Reserve Component (RC) shall be considered to be in a PERSTEMPO status on any day that, pursuant to orders that do not establish a permanent change of station, they are performing active duty as defined in section 101(d)(1) of title 10, United States Code, at a location that is not their permanent training site and is either 100 or more miles or 3 or more hours travel time from their permanent civilian residence. 3.b. The “Day Away” Rule. Regardless of the type, a creditable PERSTEMPO event must span more than one calendar day (i.e. it may not begin and end on the same date). A “day away” does not require a full 24 hours to be creditable. The day of departure will count as a full PERSTEMPO “day away,” while the day of return will not count as a “day away.” For example: If a Marine departs on Monday morning and returns on Tuesday afternoon, only Monday will count as a PERSTEMPO “day away.” 3.c. The Marine Corps Total Force System (MCTFS) is the official system of record for calculating and tracking all PERSTEMPO events. Marines and commands will use MCTFS or Marine Online (MOL) generated reports to monitor PERSTEMPO events. 4. PERSTEMPO events. There are two main types: Deployment Type and Non-Deployment Type. There are multiple categories within each type of PERSTEMPO event. 4.a. PERSTEMPO Deployment Event. These are events that fall under categories of operations, exercises, unit training, mission support temporary duty (TDY), home station training/local operating area of a ship or vessel, and hospitalization not at or near the Marine’s permanent duty station (PDS) or homeport (HP). 4.a.1. Operations. Includes but are not limited to contingency, counterdrug, law enforcement, security cooperation, U.S. domestic civil, humanitarian, security force assistance, peacekeeping or peace, surveillance, and forward-presence operations. 4.a.2. Exercise. Includes joint or combined exercises, Service exercises, and North Atlantic Treaty Organization (NATO) exercises. 4.a.3. Unit Training. When all or part of a unit is accomplishing training objectives at a location other than the permanent duty location. Unit training includes training at a combined training center or at a designated training area. 4.b. PERSTEMPO Non-Deployment Event. These are events that fall under categories of individual training, duty in garrison, hospitalization near the Marine's PDS or HP, disciplinary events, Reserve Component inactive duty training, muster duty, and funeral honors duty. 5. Calculating PERSTEMPO. If a PERSTEMPO deployment event is forecasted, PERSTEMPO calculation is required. The calculation will determine if the upcoming event causes the Marine’s PERSTEMPO to exceed 400-days out of the preceding 730-days (two years). A Marine’s PERSTEMPO is calculated by summing all creditable PERSTEMPO deployment “days away” within a 730-day look-back period; PERSTEMPO non-deployment events are not included for this calculation. Only PERSTEMPO deployment events are counted when determining if a servicemember’s PERSTEMPO will exceed 400-days out of the preceding 730-days. If an individual is projected to exceed the 400-day threshold, a waiver must be submitted to the Deputy Commandant for Manpower and Reserve Affairs (DC, M&RA). 5.a. To calculate and determine if a waiver is needed, first determine the projected end date for the upcoming PERSTEMPO deployment event. From that end date, look back 730-days to determine the start date for the period to be assessed. 5.b. Then, sum up all PERSTEMPO deployment events during that 730-day period to include the upcoming forecasted PERSTEMPO deployment event. 5.c. If the sum of PERSTEMPO deployment “days away” exceeds 400-days within the 730-day period, submit a waiver. 5.d. Calculation example 5.d.1. A Service member is notified of an upcoming PERSTEMPO deployment event with a projected end date of December 31, 2026. The look-back period is calculated as: January 1, 2025, to December 31, 2026 (730-days). 5.d.2. TDY Period #1: January 10, 2025 - January 12, 2025 (2-days) 5.d.3. Deployment: March 15, 2025 - August 25, 2025 (163-days) 5.d.4. TDY Period #2: October 11, 2025 – December 19, 2025 (69-days) 5.d.5. Projected Deployment: April 9, 2026 – December 31, 2026 (266- days) 5.d.6. Example PERSTEMPO deployment “Days Away” Calculation: 2 + 163 + 69 + 266 = 500-days 5.d.7. Based on the example, the Marine would cross the 400-day threshold during the planned projected deployment on September 21, 2026; the unit must request a PERSTEMPO waiver. 6. PERSTEMPO Waiver Process. Prior to an individual Marine exceeding the 400-day threshold, approval must be obtained from DC, M&RA. 6.a. Routing and format. Per reference (b), commands will submit PERSTEMPO waiver requests in standard naval correspondence format, via the Marine’s chain of command through the first Marine Corps General Court-Martial Convening Authority (GCMCA) to DC, M&RA via the Manpower Military Policy Branch (MPO) share point: https://usmc.sharepoint-mil.us/sites/dcmra_mra_mp_mpo. Only by exception will waiver packages be accepted through the MPO email address at [email protected]. 6.b. In the case of a reserve component member, the gaining command will be responsible for submitting the PERSTEMPO waiver. 6.c. Commands shall submit the PERSTEMPO waiver request at least 120-days prior to the projected date the Marine will exceed the threshold to allow for proper processing. 6.d. Each PERSTEMPO waiver request must explicitly justify why the specific Marine is essential to the mission and how the command will mitigate negative impacts on the Marine, in addition to the following information: 6.d.1. Marine’s full name, pay grade, primary military occupational specialty (PMOS), unit name, monitored command code (MCC), reporting unit code (RUC), electronic data interchange personal identifier (EDIPI), and the requested dates to be covered by the PERSTEMPO waiver. 6.d.2. Supporting evidence demonstrating that a PERSTEMPO waiver for the Marine is the only alternative available given manpower constraints and operational requirements during the requested period. 6.d.3. Include specific actions the unit will take to limit the amount of time the Marine will spend in excess of the threshold, and actions that will mitigate negative impacts to the Marine’s readiness, quality of life, and retention potential. 6.e.4. The GCMCA’s primary POC and email address. The primary POC shall not be the Marine who is the subject of the request. 6.f. Approved PERSTEMPO Waivers. MPO will forward the approved PERSTEMPO waiver to the Marine’s chain of command for reporting into the Marine Corps Total Force System (MCTFS), in accordance with section 91001 of reference (g). 7. Responsibilities. 7.a. Commanding Officers. 7.a.1. Ensure all PERSTEMPO event data is accurately and promptly reported into MCTFS. 7.a.2. Prospectively manage schedules to minimize negative impacts on readiness, quality of life, and retention. 7.a.3. Use automated reports from the MCTFS 112 remarks page to monitor PERSTEMPO levels. Projected PERSTEMPO deployment events that would cause a Marine to break the PERSTEMPO threshold should be identified 120-days before the planned event. This monitoring process will allow for the preparation, submission and consideration of the PERSTEMPO waiver request and possible Special Leave Accrual (SLA) consideration in accordance with reference (i). 7.b. Individual Marine. Marines shall periodically review their PERSTEMPO information in MOL under Personal Information, Personal Reports, PERSTEMPO Report. This will ensure accuracy and maintain personal awareness of their deployment, TDY history and possible SLA consideration in accordance with reference (i). If a Marine believes they have identified a discrepancy or if any period of TDY is missing in their report, they should contact their S-1 or local servicing Administration section. 7.c. Servicing Installation Personnel Administration Center (IPAC). In concert with command Administration Sections, ensure complete reporting of all PERSTEMPO data. 8. Administration. 8.a. The Manpower Information Systems Support Offices (MISSO), Admin Assist Unit (AAU) and Marine Corps Administrative Analysis Teams (MCAAT) are available to assist commanders with the following: 8.a.1. Verification procedures to ensure the accuracy of the number of days a Marine is in a PERSTEMPO event. 8.a.2. Conduct PERSTEMPO unit education on reporting, tracking, management tools, and analytics. 8.a.3. Assist the command with the resolution of contested accounting of PERSTEMPO days, along with steps and documentation required to adjust PERSTEMPO data, if warranted. 8.a.4. Commanding Officers may request adjudication of unresolved PERSTEMPO accounting issues from DC, M&RA (MPO). All decisions by DC, M&RA (MPO) will be final. This applies only to PERSTEMPO deployment events. 8.b. DC M&RA, Manpower Information (MI) develops and manages PERSTEMPO reporting systems and will, upon request, obtain historical PERSTEMPO data for inter-service and inter-component transfers. Manpower Military Personnel Policy (MPO) will coordinate semi-annually with MI on systems developments. 8.c. Points of Contact. 8.c.1. MPO: https://usmc.sharepoint-mil.us/sites/dcmra_mra_mp_mpo/. 8.c.2. Reserve Marines - Reserve Affairs (RA): [email protected]. 8.c.3. Data Reporting, Tracking, and Management - Manpower Information (MI): [email protected]. 8.c.4. Administrative Assistance – M&RA Secretariat: [email protected]. 9. This MARADMIN is applicable to the Total Force. 10. Release authorized by Lieutenant General William J. Bowers, Deputy Commandant for Manpower and Reserve Affairs.//