HR — Approve, reject, or override leave
How the leave queue works, what each decision does, and when to use HR override.
/hr/leave is the single queue for every leave request in your workspace. Reach it from HRMS in the sidebar → "For HR" → Leave queue card (which also shows the pending count as a badge so you know there's something to decide on). Anyone with HR access can decide on any request. The page surfaces filter pills for status and leave-type so you can narrow down by what you actually need to act on.
Page layout
- Stat tiles — Pending review count, Total requests count, and the current filter.
- Status pills — Pending (default active), Approved, Auto-approved, Rejected, Canceled, Overflow LWP. Click any to filter; click "All" to clear.
- Leave-type pills — All, SL, CL, EL, LWP, CEL, CTL, RH, COMP_OFF. Combine with the status filter.
- Request cards — one row per request, with the applicant's avatar + name, the leave code badge, the current state badge ("Pending · awaiting manager (stage 1 / 2)" for multi-stage), date range, day count, and the reason.
The Approve flow
- Click Approve on a request card.
- For single-stage workflows the request goes immediately to Approved status, the days are deducted from the applicant's balance, and they get an in-app notification + email.
- For multi-stage workflows (Manager → HR) the first approver moves the request to "stage 2 / 2 — awaiting HR". The second approver finalizes it. You can see the current stage on the card badge.
The Reject flow
- Click Reject. A reason field appears — this is required; the applicant will see it on their History card so don't leave it blank or vague.
- Type a one or two-sentence explanation. Examples: "Already two people out that week — please reschedule", "Sick leave requires a doctor's note attachment for stretches over 2 days", "Use COMP_OFF for this — you have credit available".
- Confirm. The request moves to Rejected, the applicant's balance is restored, and they're notified.
HR override
The third button on multi-stage requests — HR override — lets HR skip the manager stage and decide directly. Use sparingly; the standard workflow exists for a reason. Good use cases:
- Manager is themselves on leave and the request is time-sensitive.
- The applicant is the manager (nobody to approve them otherwise).
- A clear emergency where waiting for stage 1 would harm the employee.
Override actions are tagged in the activity log so the decision is auditable later.
Auto-approved requests
Some types — typically RH Optional Religious Holiday — are configured to auto-approve on submit. These never appear in the "Pending" filter; they go straight to "Auto-approved" state with the decision timestamp recorded as the moment of submission. They still show in the queue under the Auto-approved filter so you have visibility into them; they just don't need your action.
Overflow LWP
When an employee asks for more days than their available quota (typically Sick Leave), the system can split the request — the within-quota portion uses SL, the excess converts to Leave Without Pay. The single request shows the Overflow LWP status with both leave types listed. Approve once and both balances move correspondingly. If you don't want to grant the LWP excess, reject the whole request with a reason and let the applicant resubmit a smaller one.