Leave Management Setup Checklist for Nepal HR Teams

Leave management becomes difficult when the policy sits in one document, employee balances sit in a spreadsheet, and approval requests arrive through several different channels. A clear setup does not need to be complicated. It needs a shared source of truth, a visible process, and decisions people can understand.

This guide is for HR and operations teams in Nepal that want to make leave requests, approvals and balances easier to manage. It is an operating checklist, not legal advice. Your organisation should confirm its own policy, employment contracts and current obligations before publishing a leave rule.

1. Start with the leave types your team actually uses

Do not create a long list of leave types just because a system allows it. Start with the categories employees and managers need to use in normal work. For each leave type, define the name employees will see, who is eligible, whether a balance is accrued or allocated, when it resets, whether a request needs approval, and how the balance is treated when someone joins or leaves.

The important test is simple: can a new employee read the policy and know what to request without asking HR to interpret it? If the answer is no, improve the wording before configuring the workflow.

2. Establish one balance record for every employee

A leave balance should not be reconstructed from email threads. Record the opening balance, entitlement, approved leave, adjustments and remaining balance in one place. Keep a reason for every manual adjustment. This is useful for employees, but it is equally useful when HR needs to answer a manager’s question months later.

Hajiri’s leave management software keeps requests, balances and approval history close to the employee record. Before importing any historical numbers, decide a clear cut-off date and validate a small sample with managers and employees.

3. Design approvals around availability, not hierarchy alone

Approval routing should reflect the work. A direct manager may be best placed to review team coverage; HR may need visibility for exceptions, longer absences or policy questions. Finance or payroll may need an approved record only after a period closes. Map those responsibilities before turning on notifications.

Give managers the context they need: dates requested, the employee’s remaining balance, overlapping team leave and a clear place to approve or decline. A short note on a declined request is much more useful than an unexplained status change.

4. Connect leave to attendance and payroll preparation

Leave is not a separate administrative task. Once it is approved, it should be visible alongside planned schedules and attendance records. That reduces the chance that an approved absence appears as an unexplained attendance exception. At the end of a payroll period, the payroll team should work from approved records rather than collecting another list of changes.

Set a monthly or pay-period review point. HR can check pending requests, managers can confirm exceptions, and payroll can use a consistent approved cut-off. This is where connected attendance records and payroll preparation save the most rework.

5. Make the employee experience predictable

Employees should be able to see their balance, submit a request, understand its status and find the policy without chasing someone. Managers should see only the information they need to make a fair decision. HR should be able to answer, “What changed?” from the record rather than from memory.

Before launch, ask a few employees to submit test requests on mobile and web. Ask a manager to approve one, decline one and request clarification. Those small tests reveal unclear labels and missing handoffs before the whole team depends on the process.

A simple launch checklist

• Write leave types in plain language.
• Confirm opening balances and an import cut-off date.
• Assign the right manager and HR approvers.
• Explain approval timing and escalation paths.
• Test requests, approvals, corrections and reporting.
• Set the recurring attendance and payroll review date.

Keep improving from real questions

The best policy is not the longest one. It is the one your team can use consistently. Track the questions employees repeatedly ask, the requests managers frequently send back, and the adjustments HR makes most often. Each pattern is a signal that a policy sentence or workflow step needs to be clearer.

If your team is still reconciling leave in messages and spreadsheets, start with one shared workflow. Start Hajiri free for up to 10 people and use the setup to make the policy visible, the approval path clear and the record dependable.