Moving leave tracking off spreadsheets in Kenya
Kazee team · · 6 min read
Most Kenyan businesses start tracking leave in a spreadsheet. One tab per year, one row per person, a column for days taken. With five people it works. With twenty, it starts to slip: two versions on two laptops, a formula someone typed over, and a manager who approved leave on WhatsApp but never told HR.
This guide covers what the law expects your leave records to show, where spreadsheets usually go wrong, and a calm way to move to a proper system without losing anyone's balance on the way.
What the law asks you to record
The Employment Act, 2007 is clear that leave records are not optional. Section 74 lists the records every employer must keep for each employee. They include the employee's annual leave entitlement, days taken and days due, and particulars of maternity leave and sick leave.
Section 74 also lets an authorised officer ask to inspect those records for any period in the preceding thirty-six months. So the question is not only "how many days does Wanjiru have left?" but "can you show how you worked that out, three years back?"
A spreadsheet can hold that. In practice, it rarely does, because the history gets overwritten every time someone updates a balance.
The leave rules your records need to follow
These are the minimums in the Act. Contracts and collective agreements can give more, and where they do, the better terms apply (section 26). This is a summary, not legal advice, so check the current text on Kenya Law or with your lawyer before you set a policy.
- Annual leave (section 28). At least 21 working days with full pay after every twelve consecutive months of service. If employment ends after at least two consecutive months in a leave-earning period, the employee is owed at least one and three-quarter days for each completed month.
- Splitting annual leave. With the employee's consent, you can split it into parts. Unless an agreement says otherwise, one part should be at least two uninterrupted working weeks, taken within the twelve months. The rest must be taken within eighteen months of the end of the leave-earning period.
- Maternity and paternity leave (section 29). Three months of maternity leave with full pay, and two weeks of paternity leave with full pay. Taking maternity leave does not reduce annual leave.
- Pre-adoptive leave (section 29A). The Employment (Amendment) Act, 2021 added one month's pre-adoptive leave with full pay from the date a child is placed with an employee who is adopting.
- Sick leave (section 30). After two consecutive months of service, at least seven days of sick leave with full pay, then seven days with half pay, in each twelve months. The employee needs a certificate from a qualified medical practitioner and should tell you as soon as reasonably practicable.
Notice how much of this depends on dates: twelve consecutive months, two consecutive months, eighteen months from the end of a period. That is exactly the kind of arithmetic a spreadsheet gets wrong quietly.
Where leave spreadsheets go wrong
The problems are rarely dramatic. They build up over a year until someone leaves, or someone asks for their balance, and nobody trusts the number.
- Requests arrive everywhere. A message to the supervisor, a word in the corridor, an email to HR. The spreadsheet only knows about the ones someone remembered to type in.
- Approvals leave no trail. "My manager said yes" is hard to check months later.
- Staff cannot see their own balance. So they ask HR, HR opens the file, and a two-minute question takes half a morning across the team.
- The eighteen-month rule is invisible. A spreadsheet will not warn you that a part of last year's leave is close to its deadline.
- Sick notes live in a drawer. The certificate that section 30 depends on is somewhere else from the record of the days.
- History disappears. When someone corrects a balance, the old figure and the reason for the change are gone.
- Final dues become a dispute. When an employee leaves, the leave they are owed has to be settled. If the balance is uncertain, that conversation gets harder than it needs to be.
How to move off the spreadsheet
You do not need a big project. Most teams can do this in a few weeks.
- Write your leave policy down first. Your leave year (calendar year, or each person's start date), the leave types you offer, who approves each type, and how you handle leave carried over. A tool cannot fix a policy that only exists in someone's head.
- Agree opening balances with each person. Before you move anything, send every employee their current balance and ask them to confirm it. Fix disagreements now, while the spreadsheet is still in front of you.
- Decide who approves what. Usually the line manager approves and HR can see everything. Name a backup approver for when a manager is away.
- Choose a tool against a short checklist. Employees should be able to request leave and see their balance themselves. Managers should be able to approve from wherever they are. Every request should keep its history: who asked, who approved, when. You should be able to attach a sick note to the request it belongs to. And you should be able to get your data out.
- Run both for one month. Keep the spreadsheet up to date alongside the new system for a single month. If the balances match at month end, you are ready.
- Retire the spreadsheet, but keep a copy. Save a read-only copy of the old file with your records. Remember section 74 looks back thirty-six months, and your new system only starts on the day you switch.
Tell the team why you are changing. "You can see your own balance and you will not have to chase anyone for approval" lands better than "HR has a new system".
A few habits that help in any system
- Record leave when it is approved, not when it is taken.
- Use the same leave type names everywhere, so reports add up.
- Check balances before the end of each leave year, and remind people with days close to a deadline.
- Make one person responsible for the leave policy, even in a small business.
Where Kazee fits
If you want a tool for this, Kazee People is the HR app in the Kazee suite. It keeps attendance, shifts, leave, payslips and employee documents in one workspace. Employees get self-service, and HR gets approvals and an audit trail.
Whatever you choose, the steps are the same: write the policy, agree the balances, then switch. If you would like to see how Kazee People handles leave for a team like yours, book a demo and we will walk you through it.