In addition, not instead
The deputy receives new tasks, approvals and resubmissions in addition to the absent person and can act on them. On return it is visible what happened on their behalf.
Platform & AI
Absence and Deputy
Deadlines and approvals keep moving during leave, without undermining the four-eyes principle
Reporting deadlines and approvals do not follow the holiday schedule. Without a deputy, tasks sit in the absent person's inbox; with a poorly regulated deputy, someone approves their own request. The module handles both: the deputy learns that they are needed, and may only decide what segregation of duties allows. IT-Grundschutz requires exactly that: deputies are also subject to segregation of duties (ORP.1.A4).
BSI IT-Grundschutz ORP.1.A4ISO/IEC 27001 A.5.3DSGVO Art. 9
Features
Your benefits
Four eyes during deputising too
In approval stages, the deputy only applies where the stage allows it. In four-eyes approvals, the requester and the creator of the object are excluded, also as deputies.
No reason, no health data
Period and deputy are recorded, not the reason for the absence. This keeps health data out of the deputy entry.
Capabilities
All capabilities at a glance
- Enter absence yourself or via user administration
- Deputy separately for tasks, approvals and resubmissions
- Deputy notified in addition to the absent person
- Allow or block deputies per approval stage
- Four-eyes exclusion also for deputies
- Traceable who decided on whose behalf
- No deputy chains, deputy only within a shared team
Result
No deadline stalls during leave, and the four-eyes principle still holds when one pair of eyes is on the beach.
Background
Articles on Absence and Deputy
Experience Absence and Deputy live
Schedule a no-obligation demo – we will show you the module with your own use cases.