An employee leave management system, and the rules it has to encode
Almost every version of this starts as a request for a leave request form with an approve button. The form is the easy half and the part nobody argues about. What makes these systems fail is the arithmetic underneath, and in the Gulf a good deal of that arithmetic is set by law rather than by your HR policy.
The shared spreadsheet works until two things happen at once: somebody leaves mid-year with untaken days, and somebody else asks whether last year's balance is still available. At that point the sheet stops being a record and becomes an argument, because the numbers in it were never computed, they were typed.
So the brief arrives as a form with an approval button. That is the visible part, and it is not where the work is. The work is in deciding what a day of leave is worth, when it comes into existence, and what happens to it when it is not used.
What the system is actually for
A leave system has one job that a spreadsheet cannot do: compute a balance that nobody has to trust. Everything else, the form, the calendar view, the email, is convenience. If the balance is computed from rules and events, the system is useful on its first day. If the balance is a number somebody maintains by hand, you have built a nicer spreadsheet and bought yourself the same argument later.
The entitlement is not one number
This is where most briefs are wrong, and the correction is free because the rules are published. In the UAE private sector the entitlement is set by Federal Decree Law No. 33 of 2021, and the government's own portal states the bands plainly on its types of leaves page.
| Length of service | Annual leave entitlement | What the system must do |
|---|---|---|
| Under 6 months | No annual leave entitlement | Accrue nothing, but show the date it starts |
| 6 to 12 months | 2 days per month of service | Accrue monthly, not as a yearly block |
| Over 1 year | 30 days per year | Switch bands on the anniversary, not on 1 January |
| Leaving mid-year | Paid for the fraction of the last year worked | Pro-rate on exit, at basic salary |
Read the third row carefully. The band changes on the employee's own anniversary, which means a system built around a calendar year will be wrong for everybody who did not join in January. That single assumption is the most common defect we see in leave tools that were written quickly, and it is expensive to unpick later because the historical balances were all computed under it.
Saudi Arabia sets different numbers under its own Labour Law, widely cited as 21 days rising to 30 after five continuous years. We have not read that on the ministry's own page, so treat it as a reason to make the bands configurable per country rather than a figure to encode from here. Either way: across two Gulf countries, entitlement is a table, not a constant.
Accrual, carry-over and the two year rule
Carry-over is the feature people ask for last and argue about most. The UAE portal is specific: unused leave can be carried into the following year only with the employer's consent and under company regulations, and the employee is then paid for unused days based on basic salary. It also states that an employer cannot stop an employee from using accrued leave after two consecutive years.
Three design consequences follow, and none of them is obvious from the form.
- Carry-over is a decision, not an automatic rollover. The system needs somewhere to record consent, with who gave it and when, or the balance is a claim nobody authorised.
- Balances need a vintage. If days can be carried and can also expire, the system has to know which year each day came from, which means a balance is a set of dated buckets rather than one integer.
- The two year rule is a warning the system should raise by itself. Anyone sitting on accrued days approaching that boundary is a compliance problem your tool can see and your HR lead cannot.
That third one is the clearest argument for building this at all rather than buying a form. The value is not in collecting requests, it is in the system noticing things on a schedule. The same logic appears in a purchase request approval workflow, where the thresholds matter more than the form, and in internal tools for a small business, which is the broader question of when a spreadsheet stops paying.
The holiday calendar you cannot hardcode
A leave system has to know which days are working days, and in the Gulf that calendar is not knowable a year in advance. The UAE's official public holidays page states that Islamic holidays are determined according to moon sighting. The Gregorian dates for Eid are therefore announced, not calculated, and your system has to accept them late.
Two further details from that page change the code rather than the content. Eid Al Fitr runs from 1 to 3 Shawwal, and the page notes that if Ramadan lasts 30 days, day 30 is also an official holiday, so the break can be four days instead of three. And citing Article 3 of Cabinet Resolution No. 27 of 2024, the page says a public holiday cannot be transferred to another day if it coincides with another public holiday or falls on the weekend.
That last rule is the useful one, because it removes a feature. There is no day in lieu to compute. A holiday landing on a weekend is simply absorbed. Teams that have worked on systems for other jurisdictions tend to build the substitution logic by reflex, and here it would be wrong as well as wasted.
What happens when someone leaves
The exit case is where a leave system either earns its keep or produces the dispute it was bought to prevent. The UAE portal states that an employee who leaves before taking leave is paid for unused annual leave regardless of its duration, plus pro-rated leave for the partial year, based on basic salary.
Note the phrase basic salary. If your payroll figure includes allowances, the leave payout is computed on a different base than the one the employee sees on a payslip, and a system that uses the wrong one produces a number that is both confidently displayed and incorrect. Store both, label which is which, and compute the payout from the right one.
The approval chain, and where it actually breaks
Approval is the part everybody specifies and it is rarely where the system fails. It fails on absence: the approver is on leave, and the request sits. Any chain with one approver and no fallback will stall in its first month, usually in the same week everybody wants off.
Two rules handle most of it. Every approver has a named delegate, and every request has a time after which it escalates rather than waits. Neither is hard to build and both are usually missing from the brief, which is an argument for writing the brief properly before anyone starts. What a usable one contains is in how to write a software requirements document.
The second failure is quieter: the manager approving has no idea who else is already off that week. An approval screen that does not show team coverage is a form, and it will approve three people out of a four person team. Put the overlap on the approval view itself, not on a separate calendar page somebody has to think to open.
What to build first, and what to leave out
If you want this useful in weeks rather than months, the order matters more than the feature list. Entitlement rules and the balance derivation come first, because everything else is a view over them. Then the holiday calendar as editable data. Then request and approval with a delegate. Then the exit calculation.
Leave out, for now: self-service document uploads, leave types beyond annual and sick, integrations with payroll, and anything resembling a dashboard. Those are real eventually and none of them is what makes the first version trustworthy. The same staging argument, applied to a different internal tool, is in an internal tool for employee onboarding, scoped to day one.
Honest limits
We have verified the UAE figures and not the Saudi ones. The entitlement bands, carry-over rules, exit payment and holiday rules above were read from the UAE government portal's own pages on 16 November 2026. The Saudi 21 and 30 day figures are widely reported and attributed to Article 109, and we did not read them on the ministry's site, so we have not presented them as established here.
This is not legal advice and the law moves. We are describing what a system has to compute, not advising you on compliance. Cabinet resolutions change holiday rules, and the holiday page above cites one from 2024. Have somebody who is accountable for employment law sign off the rules before they go into production, and keep them as data so the sign-off does not require a deploy.
Free zones and specific contracts can differ. Some UAE free zones operate their own employment regulations, and an individual contract can be more generous than the statutory floor though not less. A system that assumes one national rule for every employee will be wrong for somebody, which is another reason entitlement belongs in a table.
And buying may be right here. Leave management is one of the better served categories in off the shelf HR software, and if you have no unusual rules and no integration needs, a subscription will beat a build on cost and on time. The question to settle before commissioning anything is in custom software versus off the shelf. Build when the rules are genuinely yours, not when the forms are.
Describe it. We build it.
Seven or twelve days, pay on delivery, a year of maintenance included. Bring the problem, not a spec.
Book a meetingRead next
A phased software rollout plan, and the order that holds
A phased software rollout plan borrowed from reliability practice: why one branch goes first, the few signals worth watching, and keeping a way back.
ReadThe cost of downtime for an online business, calculated
The cost of downtime for an online business, worked out from four inputs you already have, plus what your hosting agreement has actually promised you.
Read