A covered absence no longer hurts engagement.
This is the reason the module exists, and by far the most important one. Your engagement score measures attendance, reliability and consistency. Without absence management, it draws no distinction between the member on holiday who told you and the one who has gone silent for two months. Both lose points the same way.
With the module on, a declared and covered absence does not count as an unexcused absence. The score goes back to being what it claims to be: a measure of engagement, not a measure of availability. Your members stop being punished for having a life.
- A covered absence is neutralised in the engagement calculation
- The member who gives notice is no longer confused with the one who vanishes
- Promotion and reserve decisions finally rest on honest data
The member declares it. Taken into account immediately.
No form to request, no officer to chase. From their own space, the member declares planned unavailability — a weekend, two weeks, an exam, a deployment. The declaration takes effect immediately and they can see their upcoming and current absences at any time.
The whole thing takes ten seconds, which is the only level of effort an org can realistically expect people to sustain. A process that requires contacting someone is never followed.
Who's around this week? One screen answers it.
On the leadership side, the dashboard answers the only question that matters before planning anything: who do I have, and when. Four counters up top — available, absent, pending validation, total headcount — then the day-by-day breakdown and availability group by group.
You see at a glance that Dawn is at full strength but Eclipse loses a third of its people on Thursday. You decide beforehand, not on the night when the raid has already started.
- Day, week or month view, depending on your planning horizon
- Absentees per day across the period — the gaps show up instantly
- Availability by group, as real headcount over total headcount
- Planning tab for the calendar reading
You choose what goes through and what gets arbitrated.
Not every org treats absence the same way. A relaxed community lets everyone log whatever they want; a unit running planned operations wants a say. The module configures both ways: absences can go straight through or sit in a validation queue, with permissions by role.
That's what the dashboard's "pending" counter is for — it flags what needs a decision, without anyone having to go looking.
FAQ