hhajiri
Start using Hajiri →

LEAVE MANAGEMENT SOFTWARE IN NEPAL

Leave requests without the message chasing.

Employees see the policy and available balance before requesting leave. Managers review dates with team availability, and HR keeps the final decision connected to attendance and payroll preparation.

Clear balances · Defined reviewers · Recorded decisions
Leave requestAwaiting review
AKAarya KarkiProduct team · Kathmandu
Leave type
Annual leave
Dates
4–6 October · 3 days
Balance after request
7 days
Reason
Family commitment
Reviewer: Nisha Shrestha

BEFORE SOMEONE REQUESTS LEAVE

Show the rule, balance and next step.

A leave system should answer basic questions before an employee has to ask HR: which leave type applies, how much is available, whether documents are required, who reviews the request and what happens after approval.

  • 01Policy

    Explain eligibility, notice, limits and required information.

  • 02Balance

    Show the available amount and the effect of the request.

  • 03Approval

    Route the request to the responsible reviewer with team context.

  • 04Record

    Keep the request, decision and relevant attendance effect together.

A NORMAL LEAVE WORKFLOW

From request to an approved record.

Hajiri gives each participant one clear responsibility instead of moving the same request through chat, email and a separate spreadsheet.

  1. 01Employee chooses a leave typeThe policy, available balance and required details are visible in the request.
  2. 02Hajiri checks the requestDates, duration and applicable balance are shown before submission.
  3. 03Manager reviews team contextThe reviewer sees relevant overlap and can approve, reject or return the request.
  4. 04Approved leave updates the recordThe decision remains available for attendance review and payroll preparation.
October · Product teamTeam leave
MON 1TUE 2WED 3THU 4FRI 5SUN 7
AaryaAnnual leave
NishaHalf day
Sujal
Example team view · No live employee data

MANAGER CONTEXT

See overlap before deciding.

A manager can review relevant team availability without opening every employee’s private record. This supports an informed decision while keeping the approved policy and authorised reviewer in control.

  • Requests and approved leave in one team view
  • Half-day and multi-day duration visibility
  • Recorded comments and decision history

CONFIGURE THE WORKFLOW

Different leave types can follow different rules.

Annual leave

Balance, notice, duration and reviewer rules appropriate to your approved policy.

Sick leave

Simple employee request with any evidence requirements communicated clearly.

Half-day leave

Record the relevant portion of the workday without treating it like a full absence.

Unpaid or special leave

Use restricted, policy-led workflows and keep the payroll implication visible for review.

Hajiri helps administer the policy your organisation approves. Your organisation remains responsible for current Nepal labour requirements, employment terms and qualified legal review.

CHOOSING LEAVE MANAGEMENT SOFTWARE

Questions teams ask before implementation.

Can we configure our own leave types?+

Yes. Leave types, balances and approval workflows should be configured around your organisation’s approved policy and employee groups.

Can employees see their balance before applying?+

Yes. The request experience can show the relevant available balance and the effect of the requested duration.

Can managers see overlapping leave?+

Managers can receive an appropriate team view to understand relevant overlap before making a decision.

Does approved leave connect with attendance and payroll?+

Approved leave can support attendance interpretation and payroll preparation, subject to authorised review and your organisation’s rules.

Does Hajiri decide whether leave is legally required?+

No. Hajiri administers configured workflows. Your organisation must maintain current policies and verify legal requirements with qualified advisers.

MAKE THE NEXT REQUEST CLEARER

Put balances, approvals and attendance in one workflow.