Absence
Here staff request holiday and report absences (sickness, home office, special leave); the back office approves or rejects them – with an optional stand-in.
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 calendar shows who is away when; the list filters open and approved requests.
Tips
Staff may create and change their own requests while they are not yet approved. For half days tick „Half day“. The stand-in helps to plan handovers cleanly.
What's inside
- Absences
- Absence
- Request absence
- Edit
- Delete
- Approve
- Reject
- Cancel
Fits together with
Other blocks from the same area.
Client master
The central client master for care: maintain all clients with their core data, contact, address and care level in one place – the foundation for routes, visits and 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: maintain all club members with their core data, membership, fee and contact details in one place – independent of the app login.
M32Shift planning
Plan shifts per staff member here – as a calendar or list.