Types and balances
Paid and unpaid leaves with an annual balance checked before acceptance. Staff submit with duration, and the system checks the balance before routing for decision. The practical limit: over-balance requests are refused before reaching a manager.
Carryover, expiry, and encashment
Policy-based carryover per scope with seniority, cap, and expiry, plus cash encashment on approval. Only eligible balances carry over; what exceeds the cap or period expires. The practical limit: each scope has its own limits, so carryover is never open-ended.
Recurring and conversion
Recurring requests and conversion of leave to absence when needed. Managers create recurring patterns for known breaks, and unjustified absence is routed to its correct path. The practical limit: conversion is a documented management decision.
Cancellation, approval, and rejection
Submit and cancel before decision; the authorized role approves or rejects. Staff cancel their own pending requests, and managers decide the rest with one decision. The practical limit: cancelling an approved request follows an authorized management path.
Each request is decided once with one documented decision by the authorized role — no public multi-step chain.
Conflicts
Approved-leave conflicts with attendance are detected and resolved before payout. When attendance conflicts with approved leave, management reviews the conflict and resolves it within the controls before approval/payout. The practical limit: no payout before the conflict is resolved.
Start here
Submit your request from the app, and the authorized role decides from management.