Leave requests
The Leave requests page acts as the centralised administrative workspace for overseeing and adjudicating employee absences. While employees typically submit these requests via the Employee self service portal, HR administrators utilise this view to process and formally record the outcomes.
Viewing requests
Navigate to Absence management > Leave requests. The grid provides a comprehensive overview of all pending and historical requests, detailing:
- Employee: The individual requesting the absence.
- Leave type: The qualitative category of the absence (e.g., Maternity Leave, Unpaid Leave).
- Unit: The granular measurement (e.g., Days, Hours) inherited from the Leave type configuration.
- Start date & End date: The chronological boundaries of the requested absence.
- Reason: Contextual justification provided by the employee.
- Status: The current state of the request within its lifecycle.
Processing workflows
From the actions toolbar, administrators can select a target request and execute one of the following state transitions:
- Approve: Formally sanctions the absence. Depending on the system's integration architecture, this action may automatically post a Usage transaction against the employee's Leave bank ledger.
- Decline: Formally rejects the request, notifying the employee that the absence is not sanctioned.
- Cancel: Retracts a request before it has been fully adjudicated, typically used if the employee's plans change prior to approval.
To maintain ledger integrity, a Leave request employs a rigid state machine.
Administrators can only Approve, Decline, or Cancel a request if its current status is strictly Created (pending). Once a request transitions out of the Created state, the decision is immutable. This architectural constraint prevents accidental double-processing and preserves the integrity of the audit trail.