Document NumberRAAC-R-003
VersionVersion 1.0
ScopeAll Members — LOA, ELOA, AWOL
Effective Date08 JAN 2026
Last Modified04 APR 2026
Approving AuthorityCO TerminalLance1775
Chapter 1 — Leave of Absence (LOA)
1.1 Definition
A Leave of Absence (LOA) is a declared absence that excuses a member from their duties and responsibilities for a period of up to 14 days. During an LOA, the member is exempt from all operational requirements, mandatory training, roll call posting, and billet duties.
LOA is designed for short personal absences — holidays, exams, work commitments, or other brief life events. It is not a mechanism to avoid activity requirements indefinitely.
1.2 Requirements
To be placed on LOA, a member must:
- Notify their direct Chain of Command (TC or FC) via Discord DM before the LOA begins where possible.
- Submit a Personnel Action Form (PAF) selecting "Leave of Absence (LOA)" with the expected start and return dates.
- Specify a return date. Open-ended LOAs are not permitted.
LOA does not require formal approval — notification is sufficient. However, if the absence exceeds 14 days without an ELOA being submitted, it will be reclassified as AWOL.
1.3 Limitations
- Maximum duration: 14 days per LOA.
- Maximum frequency: No more than 1 LOA per calendar month.
- No more than 2 LOAs in any 3-month period.
- Consecutive LOAs to extend a period beyond 14 days are treated as ELOA abuse and may result in disciplinary action.
Chapter 2 — Extended Leave of Absence (ELOA)
An Extended Leave of Absence (ELOA) covers any planned absence exceeding 14 days. Members on ELOA are removed from active billets and placed on the ELOA roster. They are not considered active duty personnel during this period.
2.1 Types of ELOA
Real-Life Service ELOA is for members serving in the Australian Defence Force, emergency services, or equivalent. Members on this ELOA remain eligible for any statutory promotions that would have occurred.
2.2 Requesting ELOA
- Notify TC and FC via Discord DM before the ELOA begins.
- Submit a PAF selecting "Leave of Absence (LOA)" and specifying ELOA in the justification field with type, expected start, and expected return date.
- ELOA is not effective until approved by CO or 2IC. Do not go absent before receiving confirmation.
- Extensions to ELOA must be submitted via PAF before the current ELOA expires. Extensions beyond 45 days for Standard ELOA require CO authorisation.
2.3 Returning from ELOA
- Submit a PAF selecting "Return from LOA" with your return date.
- Contact the 2IC or CO via Discord to confirm re-activation.
- TIS adjustment (for Standard ELOA) will be applied at CO discretion upon return.
- Billet reinstatement is at CO discretion — your prior billet may have been filled during your absence.
Chapter 3 — AWOL & Abandonment
A member is considered Absent Without Leave (AWOL) if they fail to participate in any RAAC activity, submit any LOA/ELOA, or communicate with their chain of command for a period of 21 or more days.
3.1 AWOL Procedure
- After 14 days of inactivity without communication, the TC will make a good-faith contact attempt via Discord DM.
- If no response within 7 more days (21 total), the member is flagged AWOL in MILPAC.
- After 30 days AWOL, the member is subject to administrative discharge.
- AWOL discharge is recorded as Administrative Discharge in MILPAC. The member may re-enlist within 90 days at prior rank (CO discretion) or at Recruit thereafter.
3.2 AWOL — Effect on TIS / TIG
Time spent AWOL does not count toward TIS or TIG. Upon return to active duty, TIS and TIG calculations resume from the date of re-activation, not from the date of going AWOL.
Members who go AWOL without notification during a declared operation or mandatory training event may be subject to accelerated disciplinary review at CO discretion.