From 42859b1661da52c938644827f0af85c14f2350b1 Mon Sep 17 00:00:00 2001
From: "Alex Pooley (@zuedev)" <zuedev@gmail.com>
Date: Tue, 26 May 2026 08:07:46 +0100
Subject: added Leave of Absence

---
 communities/174bg/handbook/public/index.html | 68 ++++++++++++++++++++++++++++
 1 file changed, 68 insertions(+)

(limited to 'communities/174bg/handbook/public/index.html')

diff --git a/communities/174bg/handbook/public/index.html b/communities/174bg/handbook/public/index.html
index 6be87cf..3fbf556 100644
--- a/communities/174bg/handbook/public/index.html
+++ b/communities/174bg/handbook/public/index.html
@@ -625,6 +625,74 @@
         </section>
       </article>
 
+      <article id="leave-of-absence">
+        <h2>Leave of Absence</h2>
+        <p>
+          A Leave of Absence allows members to step back from group activities
+          temporarily without losing their standing. Members are encouraged to
+          give notice rather than simply going quiet, both out of courtesy and
+          to ensure their absence is not misread as disengagement.
+        </p>
+
+        <section id="requesting-leave">
+          <h3>Requesting Leave</h3>
+          <p>
+            Members going on leave should post a notice in the designated
+            Discord channel. There is no hard notice period; as much advance
+            notice as possible is appreciated but not required. The notice
+            should include an expected return date if known, and a rough
+            duration if not.
+          </p>
+        </section>
+
+        <section id="duration">
+          <h3>Duration</h3>
+          <p>
+            There is no maximum leave duration. Members may be absent for as
+            long as necessary. If leave extends significantly beyond the
+            originally stated period, members are encouraged to post an update
+            in the leave channel so leadership can plan accordingly.
+          </p>
+          <p>
+            Members holding Rank 3 or above must check in at least once per
+            month during an extended absence. This ensures that leadership
+            positions can be managed appropriately and that the group is not
+            left without visibility over its senior members.
+          </p>
+        </section>
+
+        <section id="rank-during-leave">
+          <h3>Rank During Leave</h3>
+          <p>
+            A member's rank is held for them while on leave. Where operational
+            necessity requires it, a leadership position may be temporarily
+            filled by another member during the absence. On return, the original
+            rank is fully restored.
+          </p>
+        </section>
+
+        <section id="returning-from-leave">
+          <h3>Returning from Leave</h3>
+          <p>
+            On returning from leave, members should check in with their
+            department head or division leader before resuming normal
+            activities. This ensures they are briefed on anything that changed
+            during their absence and can be reintegrated smoothly.
+          </p>
+        </section>
+
+        <section id="unannounced-absence">
+          <h3>Unannounced Absence</h3>
+          <p>
+            If a member goes inactive without notice, a Rank 3 or above will
+            attempt to make contact before any further action is taken.
+            Unannounced absence is not treated as a conduct issue unless contact
+            goes unanswered for an extended period, at which point the matter
+            may be escalated to the disciplinary process.
+          </p>
+        </section>
+      </article>
+
       <article id="fleet-composition">
         <h2>Fleet Composition</h2>
 
-- 
cgit v1.2.3