Designing a leave policy that scales: carry forward, comp-off and leave without pay

Most leave policies start as a paragraph in the offer letter: so many days of earned leave, so many casual days, a few sick days. That works for twenty people. At two hundred, the questions pile up. Does unused leave roll over? How many days can someone build up? Who decides whether Saturday's release work earns a day off? What happens when someone applies for five days with only two in the balance?

A policy that scales answers these questions in writing, applies the answers the same way to everyone, and connects leave to attendance and payroll so nobody has to reconcile them by hand. This guide covers the decisions to make and a sample policy you can adapt. Leave entitlements are also governed by state Shops and Establishments Acts and, for factories, the Factories Act, so check the minimums that apply to you.

Start with the leave year and the leave types

Pick one leave year and stick to it. The calendar year (January to December) is the simplest choice for most companies: employees understand it, and year-end processing does not collide with financial year-end in March. Some companies align leave with the financial year instead; either works if it is consistent.

Then define a small set of leave types, each with a clear purpose:

• Earned or privileged leave: planned time off, accrued through the year. Usually the only type that carries forward and is encashed on exit.
• Casual leave: short, unplanned absences. Usually lapses at year end.
• Sick leave: illness, sometimes with a medical certificate after a set number of consecutive days. Policies differ on whether it carries forward.
• Comp-off: time off in lieu of extra hours worked. It starts at zero and is earned, not allocated.

Resist adding a new type for every situation. Bereavement, marriage or paternity leave may well deserve their own types, but each one adds rules for HR to explain and apply.

Decide what carries forward, and how much

Carry forward is where leave policies most often go wrong. With no limit, balances grow year after year into a large liability that becomes encashment on exit. With no carry forward at all, employees rush to take every day in December, and your delivery calendar suffers.

The usual middle ground is to allow carry forward for earned leave up to a maximum, and let everything else lapse. Set the rule per leave type:

• Does it carry forward? Yes or no.
• If yes, what is the maximum that carries? Days above it lapse.
• Types with no yearly limit (unpaid leave, for example) never carry, because there is nothing to carry.

A new year's balance is then the year's allocation plus whatever carried in. Show the carried amount separately (for example, "18 days, including 3 carried from last year") so employees can see where the number comes from.

Sample policy

An example only. Adjust the numbers to your business and the law that applies to you.

In Techno Team Via, the admin sets carry forward and its maximum for each leave type, and the system previews, per employee and type, what is left, what carries and what lapses before the year is closed.

Comp-off: earn it from hours actually worked

Comp-off is the leave type most open to disagreement, because it depends on hours worked rather than a fixed allocation. The fair way to run it is to tie every request to the attendance record for that day.

Which hours count

• On a week off or a holiday, every hour checked in counts.
• On a working day, only the hours beyond a full day count. If a full day is 8 hours and someone works 12, 4 hours count.
• Days still open (no check-out) or closed automatically by the system do not count until the attendance is corrected.

Turning hours into leave

Convert hours into leave in half-day steps, rounded down. With an 8-hour full day and a 4-hour half day, 4 hours earns half a day, 8 hours earns one day, and 12 hours earns one and a half. Six hours earns half a day, not three quarters. Half-day steps keep the balance simple to apply against.

Approval and time limits

Ask employees to raise a request for a specific day, within a set window (30 days is common), with one request per day. The reporting manager approves; some companies add HR as a second step. Only when the final approval is given are the days added to the employee's comp-off balance. From then on, comp-off is applied for like any other leave.

Techno Team Via checks each comp-off request against that day's attendance, converts the hours in half-day steps, and sends it through the approval chain the admin sets before adding anything to the balance.

Leave beyond the balance becomes Leave Without Pay

Many systems simply refuse a leave application that exceeds the balance. It feels tidy, but it does not match reality. The employee still takes the day off because they are unwell or have a family emergency, and the absence ends up unrecorded or recorded as something it is not.

A better rule: the balance covers what it can, and the rest is Leave Without Pay (LWP). If someone with two days of casual leave applies for five, the application shows two days from the balance and three days LWP. The split should be worked out when they apply, so they see it before submitting, and again when the leave is approved, because the balance may have changed in between.

LWP days do not reduce the leave balance (there is nothing to reduce). They should show clearly as LWP on leave lists and on the attendance calendar, so managers and HR are never surprised.

How LWP reaches payroll

LWP affects pay, so it must reach payroll, but it should not change payroll on its own. Late approvals, cancellations and corrections all happen near month end. The safest pattern is to show the month's approved LWP to Accounts as a suggestion next to the unpaid leave field. Finance reviews it, applies it with one click or adjusts it, and the decision stays with a person.

The same approach suits half days and short days. If attendance shows someone worked under the half-day threshold, Accounts sees that as a suggested deduction to confirm, not an automatic one. Techno IQ works this way: approved LWP appears as a suggestion for Accounts and never changes payroll by itself.

Half days and how balances are shown

Allow half-day leave for every type except where it makes no sense, and define the half-day hours once (commonly 4 of an 8-hour day). Use the same definitions for leave, attendance and comp-off, so the numbers agree everywhere.

Visibility does more for trust than any policy wording. Each employee should see, for each leave type: the allocation, what carried in, what is used, what is pending approval, and what is left. Managers should see the same for their team, alongside a calendar of who is away. HR should be able to see every balance and make documented adjustments. When employees can see their balance themselves, they stop asking HR.

A year-end checklist

Closing the leave year is a short, repeatable task. Do it a few weeks into January, once December's approvals have settled.

1. Clear pending applications for the old year: approve, reject or cancel every leave and comp-off request dated in it.
2. Check attendance corrections for late December, since they affect comp-off and LWP.
3. Review the carry forward preview: per employee and type, what is left, what carries and what lapses.
4. Confirm the rules: if you are changing a carry forward maximum, decide whether it applies to the year being closed, and communicate it.
5. Close the year, so carried amounts are fixed. A late change after closing should be a deliberate reopen, not a silent edit.
6. Tell employees their new balances, including what carried and what lapsed.
7. Load the new year's holiday calendar before anyone applies for leave against it.

Bringing it together

A scalable leave policy rests on a few firm decisions: one leave year, a short list of leave types, a carry forward rule and maximum for each, comp-off earned from real hours, and LWP in place of refusals. Connect leave to attendance and payroll so the numbers agree, keep people in charge of pay decisions, and close each year deliberately. Review the policy against your state's rules with your legal adviser before you publish it.

To see carry forward, comp-off and LWP handled in one place, book a demo of Techno Team Via.