Skip to content

Leave Management

Kazisafi provides a comprehensive leave management system designed around the Kenya Employment Act while remaining flexible enough to support custom leave policies.

Leave management overview

The leave system is built on four core concepts:

  1. Leave types define what kinds of leave are available and their rules.
  2. Leave policies bundle entitlements across leave types into a single, date-bound set of rules.
  3. Leave balances track each employee’s allocation, usage, and availability per leave type per year.
  4. Leave requests are how employees apply for time off, triggering approval and balance updates.

Six standard leave types aligned to the Kenya Employment Act, 2007 are set up for every new company.

Leave typeShort nameDefault daysPaidCarryoverRequires reason
AnnualAL21YesYes (maximum 5 days)No
SickSL14YesNoYes
MaternityML90YesNoNo
PaternityPL14YesNoNo
CompassionateCL5YesNoYes
UnpaidULUnlimitedNoNoYes

Each leave type can be toggled active or inactive without removing historical data.


Beyond the defaults, you can create custom leave types tailored to your organisation.

Go to Settings > Leave Types and click New Leave Type. Give it a name and short code, choose whether it’s paid or unpaid, and set any limits on days per year. You can also decide whether requests need manager approval, whether employees must give a reason, and whether unused days carry over to the next year.

Some leave types support different pay rates depending on how many days are taken. This is useful for types like sick leave where the Employment Act provides different pay rates as more days are used.

SettingDescription
Full Pay DaysNumber of days at full salary before switching to half pay
Half Pay DaysNumber of days at half salary after full pay days are used up

Any days beyond both levels are recorded as unpaid. The pay rate is determined automatically based on how many days the employee has already taken in the current year.


A leave policy bundles entitlements for multiple leave types into a single set of rules. Only one active policy can be in effect at a time.

SettingDescriptionDefault
NamePolicy name (e.g., “Standard Policy 2026”)Required
Effective From / ToDate range the policy is in effectRequired / Optional
Probation PeriodDays before new employees are eligible for leave90 days
Allow During ProbationWhether employees on probation can take leaveNo
Maximum Consecutive DaysMaximum consecutive working days per requestOptional

Each policy defines entitlements per leave type, including days per year, when days become available, and whether the type is available during probation.

OptionHow it works
AnnualFull allocation available from the start of the year
MonthlyDays become available proportionally each month (days per year / 12)
Probation EndFull allocation becomes available only after probation completes

Employees submit leave requests from the Employee Portal:

  1. Click Request Leave.
  2. Select the leave type, start date, and end date.
  3. Optionally enable Half Day for a partial day absence (counts as 0.5 days, single day only, must specify morning or afternoon).
  4. Enter a reason if required by the leave type.
  5. Review working days and available balance, then submit.

Kazisafi automatically calculates working days, excluding weekends and public holidays.

Managers and HR administrators can submit requests on behalf of employees from the employee’s profile. The employee is notified, and the request follows the standard approval workflow.

Before a request can be submitted, Kazisafi checks:

  • Sufficient balance: The employee must have enough available days.
  • No overlapping requests: No other pending or approved request can overlap the same dates.
  • Past date limit: The start date cannot be more than 2 days in the past.
  • Probation compliance: The leave type must be allowed during probation if applicable.
  • Consecutive days limit: The request cannot exceed the policy’s maximum consecutive days.
  • Half-day constraints: Half-day requests must be for a single day with a specified period.

StatusDescriptionAvailable actions
PendingAwaiting approval. Days reserved from balance.Approve, Reject, Withdraw, Cancel, Edit
ApprovedApproved by an approver.Cancel (before start date only)
RejectedDeclined. Rejection reason required. Days restored.None
CancelledCancelled after submission. Days restored.None
WithdrawnWithdrawn by the employee while pending. Days restored.None
TakenLeave period has passed.None

  1. Department manager first. Requests are routed to the approvers assigned to the employee’s department.
  2. Escalation to HR. If the department has no designated approvers, or all approvers are unavailable, the request escalates to HR managers and company administrators.

To approve, review the request details and click Approve. To reject, click Reject and provide a reason (required). The employee is notified by email in both cases.


Managers who will be away can temporarily delegate approval authority (maximum 90 days) to another active employee from Leave > Delegations.

  • The delegate receives leave request notifications that would normally go to the delegating manager.
  • All approvals by the delegate are recorded as “approved by [delegate] on behalf of [manager]” for audit purposes.
  • The delegation can be revoked at any time.

Kazisafi maintains a real-time balance for each employee, per leave type, per year.

ComponentDescription
AllocatedDays granted for the year from the policy entitlement
CarryoverDays carried forward from the previous year
TakenDays already used
PendingDays in pending requests
Approved FutureDays in approved requests not yet occurred
Available(Allocated + Carryover) minus (Taken + Pending + Approved Future)

Balances update automatically as requests move through the process:

EventEffect
Request submittedAvailable decreases, Pending increases
Request approvedPending moves to Taken or Approved Future
Request rejected or cancelledDays restored to Available

When leave days are used, carryover days are used first before the current year’s allocation.


Unused leave days can carry forward to the following year, subject to rules you set per leave type: whether carryover is allowed, a maximum days cap, and an expiry period (number of months into the new year).

At the start of each year, Kazisafi automatically calculates unused days, applies the cap, and creates the carryover allocation with an expiry date. Employees receive an email notification 30 days before their carryover days expire. On the expiry date, unused carryover days are automatically removed from the balance.

Example: Annual leave allows up to 5 days carryover with a 3-month expiry. An employee has 7 unused days at year-end. 5 days (the maximum) carry over to the new year and expire on 1 April. Any unused carryover days are removed on that date.


Leave duration is calculated in working days, excluding weekends and public holidays. The calculated count is shown on the request form before submission.

Example: A request from Monday 3 February to Friday 14 February spans 12 calendar days, but only 8 working days (after excluding 4 weekend days). If a public holiday falls in that range, the count drops to 7.

Manage public holidays from Settings > Public Holidays. Holidays can be marked as recurring for automatic yearly inclusion. Each company manages its own holiday calendar.


Managers can view a consolidated calendar showing approved and pending leave within their department. This helps with workforce planning, conflict prevention, and identifying coverage gaps.


Kazisafi sends email notifications at every step — when a request is submitted, approved, rejected, or cancelled. Approvers receive reminders for outstanding requests, and employees are notified 30 days before any carryover days expire.