Absence
Here staff request holiday and report absences (sickness, home office, special leave, maternity, parental leave); the back office approves or rejects them – with an optional stand-in. The per-person, per-year leave account shows entitlement, taken, planned and remaining days.
Live preview — real view with sample data
M28 · Absence
| Person | Type | From | To |
|---|---|---|---|
| Entry 2 | Done | 08/06/2026 | 06/06/2026 |
| Record 3 | Reviewed | 19/06/2026 | 17/06/2026 |
| Item 4 | Open | 30/06/2026 | 28/06/2026 |
| Entry 5 | In progress | 11/07/2026 | 09/07/2026 |
| Record 6 | Done | 22/07/2026 | 20/07/2026 |
Not a screenshot: the same interface you get in production.
What you do here
Use „Request absence“ to pick a type, period and optionally a stand-in. The request starts as „Requested“; management or HR approve or reject it. The board shows requests by status, the calendar shows who is away when, the list filters open and approved requests. The detail page shows the person's leave account alongside.
Leave account & net days
Per person and year the account tracks entitlement, carry-over from the previous year, taken and planned days plus the remaining balance. Counting uses net working days: weekends and configured public holidays are excluded, half days are honoured. Carry-over usually expires on 31 March of the following year (BUrlG) – the expiry date sits on the account and is flagged. Account bookings (correction, bonus, expiry, payout) run through a governed, immutable entry.
Sickness & data protection
Sickness reasons are health data (GDPR Art. 9). Put protected details and the sick-note (AU/eAU) evidence under „Evidence“ – that block is visible only to the affected person, approvers and administration, not team-wide. The short „Reason“ field stays for non-critical notes (e.g. a bridge day). Since 2023 sick notes run electronically (eAU) via the health insurer; here you track the case.
What's inside
- Requests
- Absences
- Calendar
- Absence
- Leave accounts
- Leave account
- Public holidays
- Public holiday
- Request absence
- Approve
- Reject
- Set status
- Assign stand-in
- Book account entry
Fits together with
Other blocks from the same area.
Client master
The central client record for care: one person with everything around them – master data, home access, relatives and legal guardianship, payers, care level with history, physician's order. The basis for routes, visits and care documentation.
M30Employee master
The central employee master: maintain all staff with their core data, employment and contact details in one place – independent of the app login.
M31Member master
The central member master for clubs: core data, membership, offices and divisions in one place – plus a real fee account (charge/payment/open balance) with SEPA direct debit, independent of the app login.
M32Shift planning
Plan shifts per staff member here – as a calendar, planning board or list. Dispatch sets the demand, assigns shifts and publishes the roster; the team sees its own roster, confirms shifts and can offer shifts for swap.