Human Capital Managementlifecycle
Leave Management
How are leave requests submitted, checked against balances, and approved — down to the individual day?
A leave request names the type and date range and is stored as per-day records, checked against the employee’s balance for that type. Approval runs at two levels: the request as a whole, and each individual day, both with comments.
One request
The request is the record. The days are what get decided.
Annual leave
14 – 18 July · 5 days
- Balance, this type
- 12 days
- Used this period
- 6 days
Supporting document attached
- Mon14 JulApproved
- Tue15 JulApproved
- Wed16 JulRejectedCover unavailable on this day
- Thu17 JulApproved
- Fri18 JulApproved
Request Approved
16 July Rejected — comment recorded
The per-day outcome is visible as a leave summary on the request.
How it works
Leave types are lookup-driven per organization, so the catalog matches local rules rather than a fixed list. Before submission, the request screen shows balance and usage statistics for the employee and the selected type over the chosen period, and supporting documents can be attached to the request and managed alongside it.
The request decomposes into per-day records, which is what makes the second approval level possible: a manager can approve the request overall and still reject a specific day, each decision carrying a comment. A leave summary per request shows the outcome day by day.
Entitlement configuration lives in vacation settings, and the holiday calendar is maintained in the module so public holidays are known to scheduling and leave alike. Carry-over structures exist in the data model; continON does not publish an accrual formula, and entitlement policy remains the organization’s configuration.
What that gives you
- Per-day decomposition
- Requests are stored day by day, enabling partial approval without editing the request.
- Two approval levels
- Whole-request and per-day decisions are separate actions, each with a recorded comment.
- Balance shown before submit
- Employees and managers see balance and usage for the type and period before deciding.
- Lookup-driven leave types
- The type catalog is organization configuration, not a hard-coded list.
- Documents on the request
- Evidence files attach directly to the leave request and stay with it.
What this touches
- Duty roster & scheduling
Approved leave and the roster describe the same days from two sides. - My continON — my schedule & leave
Employees submit and follow their leave from self-service. - Time & attendance
Attendance views sit alongside approved absence for the same period. - Document management
Supporting documents ride the shared document store.