Employee Leave Management: How to Set Policies, Manage Requests and Track Time Off

An HR manager in Abuja gets a WhatsApp message from a staff member asking for three days off starting tomorrow. She checks a spreadsheet, cannot tell if he has enough balance left, and approves it anyway because asking him to wait feels awkward. Two weeks later, payroll flags the same employee for taking 22 days against an 18-day entitlement. Nobody remembers why.

Employee leave management is the system a company uses to set time-off policies, let staff request leave, route those requests for approval, and track balances accurately. Done well, it removes the guesswork above: everyone knows the policy, requests move through a clear approval chain, and balances update automatically. Done on a spreadsheet or through informal WhatsApp approvals, it quietly creates payroll errors, morale problems, and compliance exposure.

What Employee Leave Management Actually Involves

Leave management has three moving parts: policy design, request handling, and balance tracking. Policy design covers how many days each leave type carries, who is eligible, and how leave accrues. Request handling covers how an employee asks for time off and who approves it. Balance tracking covers what happens to unused days, how rollover works, and how the company sees who is out at any given time.

Most companies get policy design roughly right. They write a number in an offer letter and call it done. Where things fall apart is request handling and balance tracking, because both require consistent enforcement over time, not a one-time decision.

Why Leave Management Breaks Down in Growing African Companies

Given budget limits in most Nigerian HR teams, leave tracking is often handled by whoever has time, not a dedicated system. That works fine at 10 employees. At 50, it starts producing errors that nobody catches until payroll runs.

In a culture where hierarchy makes it uncomfortable to question a manager's verbal leave approval, requests often bypass any written record entirely. An employee tells their manager in a hallway conversation, the manager agrees, and HR finds out only when the employee does not show up.

Section 18 of Nigeria's Labour Act sets a statutory minimum of 6 working days of paid annual leave after 12 months of continuous service, but most formal-sector employers offer far more, typically 15 to 21 days for professional staff. That gap between the legal floor and market practice is exactly where undocumented policy creates disputes: an employee assumes one number, a manager remembers another, and there is no written record to settle it.

A 2023 study cited by NASME found that more than 65% of Nigerian MSMEs still run HR on manual methods, spreadsheets, handwritten files, and siloed systems, which is the same infrastructure most companies use for leave tracking specifically. When you are running leave with no dedicated HR staff, that manual approach does not scale past a certain headcount, and the point where it breaks is usually earlier than founders expect.

Step 1: Set Up Your Leave Policies

Start by listing every leave type the company recognises: annual leave, sick leave, maternity and paternity leave, compassionate leave, and any wellness or unpaid categories. For each, decide the annual entitlement, who is eligible, and whether probation employees can access it immediately or must wait until a probation period ends.

Choosing an Accrual Method

Leave typically accrues in one of three ways: monthly, daily, or full allocation upfront. The table below breaks down how each works and which situation it fits best.

Whichever method you choose, decide upfront how rollover works. Some companies allow no rollover at all, some cap it at a fixed number of days like 3 or 5, and some allow a full balance to carry over with an expiration window, such as 90 days into the new leave year.

Tiering Policies by Role or Seniority

Not every leave policy needs to apply equally to everyone. It is common, and legitimate, to give leadership 30 days while interns receive 10, as long as the tiers are written down and applied consistently by group, not negotiated individually per employee.

Step 2: Build a Request and Approval Workflow

A request workflow needs three things: a clear notice period, a defined approval chain, and an exception path for emergencies. Notice periods typically run one to two weeks for planned leave, though some companies waive the requirement for short wellness days.

Approval chains generally follow one of three patterns: manager-only approval, manager and admin approval where both must sign off, or manager or admin approval where either can finalise the request. If a manager declines a request, it should end there. Sending a declined request onward to a second approver just creates confusion about who has final say.

Emergency leave needs its own path. When you are dealing with a genuine unplanned situation, a rigid notice-period rule punishes the employee for something outside their control. The better approach is to let the employee flag the request as emergency, state a reason, and leave the approval decision with the manager rather than auto-rejecting it.

Step 3: Track Balances, Rollover, and Team Absence

Balance tracking is where manual systems fail most visibly. A spreadsheet does not automatically subtract a half-day request, apply rounding rules, or flag that three people from a six-person team are out the same week. All of that has to happen by hand, and it usually does not happen at all until someone notices a problem.

Rounding matters more than most HR teams realise. A common convention is to round decimal balances between 0.25 and 0.74 down to the nearest half day, and 0.75 or above up to a full day. Without a written rounding rule, two employees with nearly identical service length can end up with different balances for no defensible reason.

Talstack's Leave Management module lets HR teams configure tiered policies, choose an accrual method, set rollover rules, and route approvals through sequential or parallel workflows, with balances updating automatically instead of by hand.

Common Leave Management Mistakes to Avoid

• Approving leave verbally without a written record, which leaves no audit trail when a dispute arises
• Using one blanket policy for all employee levels instead of tiering by role or seniority
• Forgetting to define what happens to unused leave at year end, which forces an awkward improvised decision every December
• Not accounting for public holidays that fall inside an approved leave period, which can shortchange employees
• Skipping a documented rounding rule for accrual, which creates inconsistent balances across the team
• Letting a manager's decline silently disappear instead of notifying the employee with a reason
• Assuming spreadsheet tracking will scale past the first 15 to 20 employees

Quick Checklist

• List every leave type your company recognises and its annual entitlement
• Choose an accrual method: monthly, daily, or full allocation
• Write a rollover rule, including any expiration window
• Set a notice period for standard requests and a separate path for emergencies
• Decide your approval chain: manager-only, both, or either
• Document a rounding rule for accrual balances
• Confirm probation and eligibility rules are written down, not assumed
• Put the whole policy somewhere every employee can access it

Copy-Paste Script: Opening a Leave Policy Announcement

"Starting this month, all leave requests go through [system name] instead of WhatsApp or verbal approval. This protects your balance, gives you a written record, and means approvals will not get lost in a busy week. Your current balance is already loaded. If anything looks off, flag it to HR before your first request so we can fix it early."

FAQ

What is employee leave management?

Employee leave management is the process of setting time-off policies, letting staff request leave, routing those requests for approval, and tracking balances so a company always knows who is out and how much leave each person has left. It covers annual leave, sick leave, maternity and paternity leave, and any other paid or unpaid time off a company recognises.

How many annual leave days must Nigerian employers give by law?

Under Section 18 of Nigeria's Labour Act, workers are entitled to a minimum of 6 working days of paid annual leave after 12 months of continuous service. In practice, most private sector employers in Nigeria offer 15 to 21 days for professional staff and up to 30 days for managerial roles, since the statutory minimum is a floor, not a competitive benchmark.

What is the difference between accrued and allocated leave?

Accrued leave builds up gradually, typically monthly or per day worked, so an employee only has the balance they have earned so far. Allocated leave is granted in full at the start of the leave year or upon hire, sometimes prorated by join date, so the employee sees their full entitlement immediately.

Can a manager and HR both need to approve a leave request?

Yes. Many companies use a sequential approval flow where a manager must approve first before HR or an admin reviews the request, or a parallel flow where either party can approve or decline and their decision is final. The choice usually depends on how much HR wants to stay involved in day-to-day leave decisions.

How do you track employee time off without expensive software?

Small teams can start with a shared spreadsheet or calendar that logs leave type, dates, and approval status, but this quickly breaks down past 15 to 20 employees because balances have to be recalculated by hand. A dedicated leave management system automates accrual, approval routing, and balance tracking so errors do not compound as the team grows.

What happens if an employee requests leave with less notice than the policy requires?

Most leave systems will not hard-block a late request. Instead, they flag it and warn the employee that a manager may decline it for falling short of the required notice period, unless the request is marked as emergency leave with a stated reason.

Conclusion and Next Step

Leave management fails quietly. Nobody notices a broken spreadsheet until payroll disagrees with an employee, or until three people from the same team disappear the same week with no visibility. Writing down your policy, defining a clear approval chain, and tracking balances automatically fixes most of it before it becomes a dispute.

If your team has outgrown spreadsheets, Talstack's Leave Management module is built for exactly this handoff, with local currency pricing and workflows designed for African HR teams running lean.