Leave approvals that don't get stuck in WhatsApp: a simple workflow for growing teams
Leave requests sent by chat get lost, double-booked and disputed. Here is a simple manager-then-HR approval workflow, the policy points to write down, and how self-service cuts HR's inbox.
In many organisations, leave approval works like this: an employee sends a WhatsApp message to their supervisor, the supervisor says "ok", and HR hears about it when the person is already away. Then payroll asks how many days were taken, and nobody is sure.
A clear leave approval workflow fixes this without adding bureaucracy. Here is a structure that works for teams from 20 to 2,000 people.
Write the policy down in one page
Before any system, agree the rules. Keep it short enough that staff will read it.
- Leave types you offer: annual, sick, maternity, paternity, compassionate, study, unpaid.
- How many days each type allows, and when entitlement starts.
- How much notice staff must give for planned leave.
- Whether unused days carry over, and the limit.
- Who approves, in what order.
Check your policy against the Labour Act and your employment contracts, and keep it consistent across branches unless there is a good reason not to.
Use a two-step leave approval: manager, then HR
The manager knows whether the team can cope with the absence. HR knows the policy and the balance. Splitting the decision this way keeps both checks without either person doing the other's job.
- The employee submits a request with dates and leave type.
- The line manager approves or declines, with a reason if declined.
- HR confirms the balance and policy, then gives final approval.
- The employee is notified and the leave appears on the team calendar.
Some organisations add a third step for senior staff or long absences. A good system lets you configure the chain per leave type rather than forcing one route for everything.
Make balances visible to staff
Half of HR's leave questions are "how many days do I have left?" When employees can see their own balances, history and pending requests, those questions disappear. This is what YAD HR's My Space portal is for: staff request leave, check balances and see payslips without messaging HR.
Handle urgent and sick leave without breaking the process
Not every absence can be requested in advance. Someone wakes up ill, or a family emergency happens overnight. The workflow should bend without disappearing.
- Let staff log sick or emergency leave on the day, even after the fact.
- Notify the manager immediately so they can arrange cover.
- Ask for supporting documents, such as a medical note, within an agreed number of days.
- Let HR confirm the record afterwards so balances stay accurate.
The goal is the same as for planned leave: one record, with a date and a name attached to every decision, instead of a screenshot of a chat message.
Plan around a shared calendar
Managers should see who is away before they approve another request. A team calendar prevents three nurses from the same ward being on leave in the same week, and it helps HR plan cover around public holidays.
Connect leave to attendance and payroll
Approved leave should flow into attendance records and payroll automatically. When it doesn't, unpaid leave gets paid, approved leave gets marked as absence, and every month-end becomes a reconciliation exercise.
What changes in the first month
- Requests stop disappearing in chat threads.
- Managers decide with the calendar in front of them.
- Disputes drop because every decision has a date and a name attached.
- HR spends less time answering balance questions.
YAD HR includes leave types, balances, portal requests, multi-step approvals, a leave calendar and manager decision tools, connected to attendance and payroll. Book a demo and we'll configure your leave policy live.