Leave

Overview

What it solves

Balances are tracked in a sheet, approvals happen on WhatsApp, and nobody can see who is out next week.

Why it helps

• Every employee gets a balance automatically, pro-rated from their hire date; it renews each January with the carry-over rules the company chose.
• Balances move on their own: requested days become pending, approved days become used, cancellations give them back.
• The form shows the real day count before you submit: weekends, holidays and half days are taken into account.
• Sick leave can require a certificate, and emergency leave can be approved on filing.
• Approvals can run through a multi-step workflow with an SLA and escalation.

Used by

EmployeeManagerHR Admin

Availability

Every plan

123

1. 1Start a request
2. 2Days left per leave type
3. 3Report a wrong balance

Quick answers

What you can do

• Request leave (type, start, end, notes)
• Automatic leave balances for every employee
• Yearly renewal with carry-over, monthly accrual, carry-over expiry and service tiers
• Unpaid and no-balance leave types
• Half-day leave (first or second half of a one-day request)
• Supporting document and approval rules per leave type
• Day count preview before submitting
• Working-day count excludes weekends and holidays; a request needs at least one working day
• Overlapping pending or approved requests are refused
• Balance check per calendar year, split across a year boundary
• Approve / reject (reason required) / cancel
• Cancelling a request withdraws its approval and tells the right person
• New request notifies the approvers
• Bulk approve or reject
• HR files leave on behalf of an employee; managers file their own leave
• Leave calendar (company and my team)
• Leave types with Arabic name, days per year, paid, approval, document, colour
• Public holidays, recurring yearly; country holidays seeded on signup
• Add next year’s public holidays with one click
• Balance correction requests, answered by HR
• Leave conflict check (AI)

Screens

123

1. 1Start a request
2. 2Days left per leave type
3. 3Report a wrong balance

123

1. 1Leave type: the balance is checked automatically
2. 2First day off
3. 3Last day off: weekends and holidays are not counted

123

1. 1File leave for an employee
2. 2Approve a pending request
3. 3Reject with a reason

123

1. 1Approve straight from the dashboard
2. 2Reject with a reason
3. 3Who is out in the next two weeks

123

1. 1Create a leave type
2. 2Yearly entitlement
3. 3Whether it needs approval

12

1. 1Add a public holiday
2. 2Repeats every year

Workflows

Leave request

flowchart TD
  A[Employee: Request leave · preview shows the day count] --> B{Valid?}
  B -- "terminated / no working day / overlap / no balance / document missing / too far back" --> X[Refused with a reason]
  B -- yes --> K{Approval needed?}
  K -- no, type auto-approves --> G
  K -- yes --> C[Pending · days added to pending]
  C --> D{Approval workflow active?}
  D -- yes --> E[Workflow steps · SLA · escalation]
  D -- no --> F[Approver decides]
  E --> F
  F -- Approve --> G[Approved · pending → used]
  F -- Reject + reason --> H[Rejected · pending released · reason shown]
  C -- Employee cancels --> I[Cancelled · days returned · approval withdrawn]
  G -- Cancel --> I
  G --> N[Employee notified: email + in-app]
  H --> N

• Working days exclude weekends (set in the company work schedule) and company holidays. A one-day request can be a half day.
• The request form shows how many days will be counted before you submit.
• A request crossing 31 December is split per year and each year’s balance is checked. Balances are created automatically from the hire date and renew each January.
• Some leave types need a supporting document, such as a medical certificate, and some can only be filed a few days after they started; HR can record older leave.
• Nobody can approve their own leave, and a manager cannot approve a request directly once its start date has passed; HR can.
• Cancelling a request withdraws it from the approver’s list and returns the days.

How-to guides