Requesting leave
The Leave screen opens on your balances, with the leave policy’s rules summarised beside them — that block is the reason to visit, and it renders even before your first request.
Request leave opens the form: pick a type, pick a date range (public holidays are shaded in the picker and never counted), and the math previews live: “You have X — this leaves Y”. Not enough balance is said straight — “Needs X — you have Y remaining” — and submitting it is refused.
A request runs Pending → Approved / Rejected, or you withdraw it yourself (Cancelled). Opening a request’s panel shows the approval chain — whose desk it is on right now — and a request still Pending is withdrawn there, with the consequence stated in full: whoever was reviewing it will no longer see it.
Manager: Who’s off
Who’s off is the branch’s absence view: who is away in a date range — staff, type (with its colour), dates, amount, status. It is read-only, and it opens on every status because approved leave is what decides next week’s roster. Decisions happen in the approvals inbox; clicking a row here opens the request’s own panel, its chain inside.
Configuring: types, holidays, policy
Leave settings is three blocks, and each one’s on-screen hint is worth reading verbatim:
- Types — what staff can request. Statutory types are set by law and cannot be deleted; types you add are requestable immediately.
- Holidays — “this is more than a marker”: the roster flags scheduling on those days, and payroll prices them at a different rate. One calendar, three modules.
- Policy — when annual leave recalculates (calendar year or hire anniversary), how many minutes one day converts to (whole hours — multiples of 60), extra non-statutory days, and “allow one carry-forward by agreement”.