Leave Policy by Location: Setting Up Different Rules in One HRMS

Here is a conversation that happens in some version at hundreds of Indian companies every January.

The HR manager in Gurugram publishes the year's holiday list and leave policy. Two days later the Jaipur showroom manager calls: "Madam, Gangaur isn't on the list. Everyone here takes it." The Ludhiana plant supervisor messages next: "Lohri kahan hai? And why does it say 12 casual leaves? Our workers are on earned leave under the factory rules." Then the Bengaluru sales office asks why Kannada Rajyotsava is missing and points out that their state's shop rules calculate earned leave differently anyway.

By February the company has three unofficial leave policies running on three Excel sheets, one official policy nobody follows, and a leave register that will not reconcile with attendance when someone finally checks.

This post explains why leave management in India is a location problem before it is a policy problem, what breaks when you ignore that, and how to set up location-wise leave rules inside a single HRMS without creating a monster.

Why leave is different in every location?

A leave policy feels like a company decision. In India, roughly half of it is decided for you, and decided differently in each state and each type of establishment. Five things drive the variation.

1. State Shops & Establishments rules. Offices, showrooms, clinics, warehouses and most non-factory workplaces are governed by the Shops & Establishments law of the state they sit in, not the state where your head office is. These laws set minimum leave, and the minimums differ. Delhi's rules, for instance, have traditionally provided for privilege (earned) leave, casual leave and sick leave as three separate entitlements. Karnataka's rules accrue earned leave in proportion to days worked, with a cap on how much can be carried forward, and treat sick leave separately. Other states blend casual and sick leave into one bucket, or set different accrual rates and carry-forward limits.

The company minimum you write in the handbook has to be at least each state's minimum. If your Gurugram-designed policy is below Karnataka's floor, your Bengaluru office is non-compliant no matter how generous the policy looks on paper.

2. Factory versus non-factory under the OSH Code. A manufacturing unit is not a shop. Under the Occupational Safety, Health and Working Conditions Code, adult workers in a factory earn leave with wages at a defined rate, commonly one day for every twenty days worked, with rules on how much can be carried forward to the next year. This is a different construct from the "15 earned + 12 casual + 12 sick" pattern of an office. A company with a factory in Ludhiana and an office in Gurugram has two legally different leave systems on the same payroll.

3. State holiday lists. National holidays are common, but each state notifies its own list of public and festival holidays, and companies typically follow the list of the state where each location sits. Lohri and Baisakhi matter in Punjab. Rajasthan observes its own state day and festivals like Gangaur and Teej carry weight in local practice. Maharashtra has Maharashtra Day and Gudi Padwa. Tamil Nadu has Pongal. Kerala has Onam. Karnataka has Rajyotsava. A single company-wide holiday list either gives the wrong days off in most locations or, worse, gives everyone every location's holidays and quietly adds a week of paid leave nobody budgeted.

4. Weekly off and closure norms. Weekly off is a right everywhere, but the day and the rules around it are shaped by local trade practice and, in some states, by shop-closure norms. A showroom in one city may close on Tuesday; a factory runs a rotating weekly off by shift; an office is Saturday–Sunday. A leave policy that assumes Sunday off will mis-count "sandwich leave" and leave balances in every location that doesn't work that way.

5. Local practice and expectations. Beyond law, there is what people in a place consider normal. Chhath is not a listed holiday in many states, but a Delhi NCR factory with a large workforce from Bihar and eastern UP will see 40% absence that week regardless. Local hiring competition also matters: if every other unit in an industrial area gives a particular festival off, your policy that doesn't will show up in attrition.

Put those five together and the conclusion is unavoidable. Location is a dimension of your leave policy, not an exception to it.

What goes wrong with one policy for everyone?

Most companies discover this the expensive way. The failure modes are predictable.

You under-grant somewhere and become non-compliant. Your policy was written for the head-office state. A location in another state has a higher minimum, a different accrual rule or a mandatory holiday you don't give. Under the Labour Codes, the Register of Leave with Wages is a prescribed record, and it must reconcile with attendance. A leave register built on the wrong rules is a compliance finding waiting to happen.

You over-grant everywhere and pay for it. The opposite fix, "give everyone the most generous version," is common and quietly expensive. Merging three states' holiday lists into one can add five to eight paid days per employee per year. Across 300 people, that is a meaningful salary cost for days most of them don't need.

Managers invent local rules. When the official policy doesn't fit, the location head does what's sensible for his people and doesn't tell HR. Now the company has policies it doesn't know about, approvals that don't follow the documented chain, and balances that exist only in a branch Excel.

Balances break on transfer. An employee moves from the Jaipur showroom to the Gurugram office. His earned-leave balance was accrued under one rule and is now being consumed under another. If the system has no concept of location, the balance is either carried over wrongly or reset to zero by a frustrated admin.

Month-end reconciliation becomes a fight. Attendance says present, the branch sheet says on leave, the holiday list says it was a holiday in that state but not in HQ's file. Whoever prepares the payroll input spends three days on WhatsApp resolving it.

The framework: leave policy as layers

The way out is not twelve policies. It is one policy structure with a few layers, applied per location. Think of it as four layers, from broadest to most specific.

Layer 1 — Location. Everything that is decided by where the workplace is: the state's minimum leave entitlements, the state holiday list, the standard working week and weekly off, and the working-hours pattern. Every employee inherits these from the location they are mapped to.

Layer 2 — Establishment type. Within a location, is this a factory under the OSH Code or a shop/office under state rules? A company can have both in the same city: a plant in Manesar and a corporate office in Gurugram are in the same district and on different leave constructs. This layer decides the kind of leave types and accrual logic that apply.

Layer 3 — Employee category. Permanent staff, factory workers, contract workers, fixed-term employees, trainees and probationers. The Labour Codes require parity for fixed-term employees, so this layer is less about giving different entitlements and more about handling probation rules, accrual start dates, and whether contract workers' leave sits with you or the contractor.

Layer 4 — Individual adjustments. Maternity leave (26 weeks under the Maternity Benefit Act, and notably the same everywhere in India, which is a useful contrast), paternity leave if your company offers it, long-service additions, negotiated balances for senior hires, and one-off credits like compensatory off.

The power of the layered approach is that you write the company's philosophy once (how carry-forward works, how encashment works, who approves what, how sandwich leave is treated) and let the location and establishment layers supply the numbers and the calendars.

Setting Different Leave Policies in one HRMS: step by step

Here is the practical sequence. It works in any reasonably capable HRMS; the field names will differ.

Step 1-List every location as a separate entity, even small ones. A three-person Kochi sales office is still in Kerala and still gets Onam. Don't fold small sites into the nearest big one. Each location should carry its state, its establishment type, and its working-week pattern.

Step 2-Attach a holiday calendar to each location. Build one calendar per state you operate in, using the state's notified list plus the national days. Then add company-specific optional or restricted holidays if you offer them. Attach each calendar to its locations. When a Rajasthan employee opens the app, she should see Rajasthan's holidays, not a union of everyone's.

Step 3-Define leave types per establishment type. For offices and shops: earned/privilege leave, casual leave, sick leave (or a combined casual-sick bucket where the state does that), comp-off, maternity, unpaid/loss-of-pay. For factories: leave with wages under the OSH Code, plus festival/national holidays, comp-off and the statutory maternity entitlement. Give each leave type a clear code so registers are readable.

Step 4-Set accrual rules per location. This is where the state minimums live. Monthly accrual versus annual credit; whether leave accrues during probation; whether accrual is pro-rated for joiners; the factory rate of one day per twenty days worked. Enter the state's floor as the location minimum and layer your company's more generous policy on top if you have one.

Step 5-Set carry-forward, lapse and encashment rules. Different states cap accumulation differently, and factory leave has its own carry-forward limit. Decide company-wide how lapse and encashment work, then set the cap per location. Make the year-end rollover automatic; manual rollovers are where balances get corrupted.

Step 6-Configure weekly off and sandwich rules per location. Define the weekly-off pattern for each location (fixed days for offices, rotational by shift for plants and stores). Then decide, once, how your company treats a leave that spans a weekly off or holiday. Apply that rule everywhere, but let each location's own weekly off and holidays feed into it.

Step 7-Build the approval chain per location. The Jaipur showroom manager approves Jaipur leave. The Ludhiana shift supervisor approves his line's leave, with the plant HR as escalation. Head-office HR sees everything but approves only its own. Approval should reach the approver where he already is; for supervisors in India, that increasingly means WhatsApp, not an inbox.

Step 8-Define what happens on transfer. When an employee moves location, the system should freeze the balance accrued under the old rules, carry it forward as a lump, and start accruing under the new location's rules from the transfer date. Write this down as a policy before anyone moves.

Step 9-Reconcile with attendance, automatically. Leave approved should mark attendance as leave on those dates, in that location's calendar. Under the Labour Codes, your Register of Leave with Wages and your muster roll are expected to agree. If leave and attendance live in one system, they can't disagree.

Step 10-Report by location, roll up by company. Each location head needs his own balances, his own absence trend and his own register. Finance and the payroll person need one consolidated file. The system should produce both from the same data, not from two exports someone merges by hand.

Suggested: How Manual leave can cost your company higher?

A worked example: three locations, one company

Consider a mid-sized company with a corporate office in Gurugram (Haryana, shop/establishment), a showroom in Jaipur (Rajasthan, shop/establishment) and a plant in Ludhiana (Punjab, factory).

Gurugram office

Jaipur showroom

Ludhiana plant

Governing rules

Haryana S&E rules

Rajasthan S&E rules

OSH Code (factory)

Leave types

EL, CL, SL, comp-off, maternity

EL, CL, SL, comp-off, maternity

Leave with wages, comp-off, maternity

Accrual

Per state minimum, company top-up

Per state minimum, company top-up

1 day per 20 days worked

Holiday calendar

Haryana list

Rajasthan list (incl. state day, Gangaur/Teej as practised)

Punjab list (incl. Lohri, Baisakhi)

Weekly off

Sat–Sun

Tuesday (fixed)

Rotational by shift

Approver

Reporting manager → HR

Showroom manager → Regional head

Shift supervisor → Plant HR

Carry-forward cap

Per state rule

Per state rule

Per OSH Code limit

Notice what is common: the leave-type codes, the sandwich rule, the encashment philosophy, the maternity entitlement, the reporting format. Notice what is per location: the numbers, the calendars, the approvers. That is the whole design.

(We build HR software, not legal advice. Leave entitlements are set by state rules and by the Labour Codes. Confirm specifics with your labour consultant for each state you operate in.)

Common mistakes to avoid while setting leave system

Copying the head-office policy to every location "for consistency." Consistency is in the structure, not in the numbers. Equal treatment across states is often unequal compliance.

Building the holiday list as a union. Everyone gets every festival, the company pays for it, and nobody remembers why April has four holidays.

Treating the factory like an office. Applying casual/sick leave buckets to workers who should be on OSH-Code leave with wages produces a register an inspector will not recognise.

Leaving contract workers out. With principal-employer liability under the Codes, you want a record of contract workers' attendance and leave at your site, even if the contractor administers their entitlements.

Manual year-end rollovers. The single biggest source of wrong balances. Automate it, run it per location, and keep the log.

How ZenflowHR handles this?

ZenflowHR is a HRMS with multiple leave settings built around one idea: one company account, location-wise everything. Each location carries its own holiday calendar, working week, shifts and approval chain, and leave types and accrual rules can be set per location and per employee category [confirm scope of per-category rules]. Employees see only their own location's calendar and balances in the app, in Hindi if they prefer. Supervisors approve leave with one tap in WhatsApp, and the approval writes directly to attendance, so the leave register and muster roll come from the same events. At month-end, each location's leave register and the company roll-up export as files your CA or payroll tool takes from there [confirm export formats].

We don't do payroll. We make sure the leave and attendance data that feeds it is right in every location.

Ready to run every location's leave from one account?

Start a 14-day free trial-no card, free migration from Excel or any HRMS, and a onboarding call so you're live in an hour. Or WhatsApp us "Hi" for a leave management HRMS demo.

FAQ

Can one leave policy legally cover offices in two states?

The company's policy can be one document, but it must meet each state's minimum entitlement and follow each state's holiday list for the employees in that state. In practice that means location-specific numbers inside one policy.

Do factory workers and office staff in the same city get the same leave?

Usually not. A factory is governed by the OSH Code's leave-with-wages provisions; an office by the state's Shops & Establishments rules. They are different constructs even in the same district.

What happens to leave balance when an employee transfers to another state?

Best practice is to freeze the balance accrued under the old location's rules, carry it forward, and start accruing under the new location's rules from the transfer date. Write this into the policy before your first transfer.

How many holiday calendars do we need?

One per state you operate in, plus optional company-specific additions. Attach each calendar to the locations in that state rather than building a separate calendar per site.