A leave management system is software that takes staff leave requests, sends them to the right approver, counts the working days, keeps each person's balance and shows who is away. It replaces the leave tracker spreadsheet and the WhatsApp message. The test is simple: can anyone explain, line by line, why a balance is the number it is?
Key takeaways
- Spreadsheet balances drift because they are typed over, not recorded. A system keeps a line for every movement, so a number can always be explained.
- Working-day counts go wrong in Nigeria because public holidays, especially Sallah dates, are declared with little notice.
- A request needs an approver, a back-up when that approver is away, and a rule that silence is never approval.
- Two people off at once is a visibility problem first. Today Rople shows who is away each day; hard limits on how many can be off are not built yet.
- Approvals, balances and leave rules are on Rople's Pro plan. Recording your own time off works on every plan.
Why do spreadsheet leave balances drift?
An annual leave tracker in Excel works for the first month. It starts to fail for five ordinary reasons.
- Balances are typed over. Someone changes 14 to 11 and nobody can say why. There is no trail, so a dispute is one person's memory against another's.
- Days are counted by hand. A request from Monday to Friday is five days until a public holiday lands inside it. Declared a few days ahead, a Sallah holiday or a state holiday can change the count after the form was approved.
- Carry-over is forgotten. Unused days that were meant to expire on 31 March are still sitting in the cell in June.
- Approvals live somewhere else. The request is in WhatsApp, the yes is a thumbs-up in a different chat, and the sheet is updated, if at all, a week later.
- Several versions exist. The one HR holds, the one the manager holds, and a screenshot someone sent in January.
None of this is a failing of the person keeping the sheet. A spreadsheet stores numbers; it does not record what happened to them.
What should a leave management system do?
Use this as a checklist when you trial any tool, Rople included.
- Count working days for you, skipping weekends, your own days off and public holidays, and show the balance before and after the request.
- Keep a ledger, not just a total: earned, carried over, taken, adjusted by HR with a reason.
- Route the request: the manager first, HR where your rules say so (maternity, unpaid leave, very long requests), and a named alternative when the approver is away.
- Never approve by silence. A request that waits too long should chase the approver, then offer the decision to the next person up.
- Hold the legal floor. Section 18 of the Labour Act sets at least six working days of annual leave for a worker after twelve months, and section 16 sets 12 paid working days of certified sick leave a year. An employer may give more by contract or policy. A tool for Nigerian teams should not let you save a policy below the Act's minimum.
- Keep health private. A manager needs to know someone is off sick; they do not need the diagnosis.
- Show who is away, in the places the team already looks.
- Reach payroll, so unpaid days are not a separate job. On Pro, Rople sends days approved as unpaid to that month's payroll.
Spreadsheet or leave management system: which fits?
| Spreadsheet or leave tracker file | Leave management system | |
|---|---|---|
| Balance | A typed number | A ledger of every earn, take and adjustment |
| Working days | Counted by hand | Counted from the calendar, with holidays skipped |
| Public holiday declared late | Someone notices, maybe | The request is recounted and the day goes back |
| Approval | A message somewhere else | In the system, with a record of who decided |
| Approver away | The request waits | Delegation, then the next person up |
| Carry-over | Remembered, or not | A rule with an expiry date |
| Sick notes | A photo in a chat | Held privately, opened only by named people |
| Cost | Free, plus the time of whoever keeps it | A subscription |
A spreadsheet is a fair choice for a team of five with one person who owns it and a policy that rarely changes. The case for a system grows with every extra approver, location and kind of leave.
Who should approve leave, and what if they are away?
The line manager should decide first, because they know the work. HR should decide next where the stakes are higher: maternity and paternity, unpaid leave, study leave, very long requests and sick leave beyond the paid days. A manager can be allowed to decide alone up to a limit you set.
Plan for absence. Rople lets an approver choose who decides for them, and for which dates, from Your approvals while you're away. The delegate is told, their decisions carry both names, and a delegation does not chain from one person to another. If the approver set nothing, the request is offered to the next person up, and the panel explains why it reached them.
Nobody approves their own request. The owner's request goes to an HR admin or another executive.
How do I stop two people being off at the same time?
Start by making it visible. Rople's manager view shows the next two weeks of the people who report to you, and a team grid shows who is away each day and which requests are still waiting. The same approved leave shows as away on the Schedule and in Workload & capacity (Starter and Pro), so nobody keeps a second list.
Be clear about what it does not do yet. Team limits and blackout dates, such as "no more than two people off in December", are not built into the request sheet or the manager's view. Until they are, state the rule in your leave policy and let the approver apply it with the team grid in front of them. Name cover on the request: Rople lets the person say who is covering for them, and your workspace can require it.



