Holiday List & Comp-Off Policy: An India HR Guide

Holiday List & Comp-Off Policy: An India HR Guide

Every HR team in India rebuilds the same two artefacts each year: the annual holiday list and the compensatory off policy that travels with it. Both look simple and both are minefields. The holiday list must reconcile central expectations, state-specific holiday laws, festival calendars that differ by region, and the operational reality of teams that cannot all be off on the same day. The comp-off policy must fairly compensate people who work when others rest — without becoming an unmanaged liability of unexpired credits, disputed approvals and payroll confusion.

This guide covers the full territory: the legal framing of holidays in India, how to build a compliant multi-state holiday calendar, how restricted (optional) holidays work, what happens when employees work on a holiday, how to design a compensatory off policy that actually functions, weekly-off rules, shift and 24/7 operations, payroll treatment, the infamous sandwich rule, and the disputes that fill HR inboxes every January and October. Sample policy clauses, a comparison table, a worked example and an FAQ are included.

Standing caveat: holidays and working-time rules in India are substantially state subjects, administered through shops and establishments legislation, national and festival holidays statutes, factory law and now the consolidated labour codes as their rules roll out. Numbers and specifics below describe common patterns — always verify your state's current notifications before finalising a calendar or policy.

Why Holidays and Comp-Off Deserve a Real Policy

Holidays look like calendar trivia until you count what rides on them:

• Compliance exposure: state holiday statutes prescribe minimum holidays and consequences for working employees on them; getting this wrong in inspected sectors (retail, factories) draws direct penalties.
• Payroll correctness: holiday pay, holiday-work premiums and comp-off credits all flow into payroll; undefined rules mean improvised payments and retro corrections.
• Fairness perception: nothing generates cross-team resentment faster than one office enjoying a festival holiday another office worked, or a manager quietly denying comp-offs a warehouse team earned.
• Attrition economics: in frontline and support businesses, predictable rest and honest comp-off credit are retention levers competitors ignore.
• Planning: sales closures, support rosters, releases and client SLAs all depend on knowing exactly who is off when.

A page of policy here prevents a year of case-by-case decisions.

The Legal Framework, in Plain Terms

National and festival holidays

Most Indian states have legislation (commonly styled as national and festival holidays acts, or provisions within shops and establishments law) that requires establishments to grant certain holidays: typically the national days — Republic Day (26 January), Independence Day (15 August) and Gandhi Jayanti (2 October) — plus a prescribed number of festival holidays chosen from state-notified lists. The total mandated count and the choice mechanics vary by state, which is why a Karnataka calendar cannot simply be photocopied for Maharashtra or Tamil Nadu.

Weekly offs

Working-time law — shops and establishments acts, factory law, and the occupational safety code as implemented — requires weekly rest days (commonly one full day per week, with defined limits on continuous working days). Weekly offs are distinct from holidays; both must be respected in rostering.

Working on a holiday

Where employees are required to work on a notified holiday, statutes commonly require either premium wages (often expressed as twice the ordinary rate for the day, mechanics varying by statute and state) or a substituted holiday/compensatory off within a defined window — sometimes both elements in defined combinations. The precise entitlement depends on the applicable statute, the employee's coverage and the state's rules: this is the single most state-sensitive area of the whole topic, so verify before setting your premium and comp-off mechanics.

Who is covered

Statutory holiday protections are strongest for employees covered by shops and establishments and factory-type legislation. Managerial and supervisory staff are often outside parts of these protections, governed instead by company policy. Best practice: run one generous policy for everyone rather than mining exemptions — the goodwill is worth more than the saved holiday.

Building the Annual Holiday Calendar: Step by Step

Step 1: Fix your legal baseline per state

For each state where you have employees (including remote employees working from that state), identify: the mandatory national holidays, the required number of festival holidays, any state-specific compulsory days (several states mandate particular regional days), and the notification/display requirements — some states expect the chosen list to be filed with or displayed to authorities and communicated by a deadline.

Step 2: Choose festival holidays deliberately

Where the state allows choice from a notified list, choose using three inputs: workforce demographics (which festivals your people actually observe), business rhythm (avoid giving away days your busiest week needs, where legally permissible), and regional parity (so no location feels like the afterthought). Involve location leaders; publish the reasoning in one line per contested choice.

Step 3: Add restricted (optional) holidays

Most mature calendars pair the fixed list with 2–3 restricted holidays (RH): a menu of additional observances from which each employee picks a personal quota. RH days respect India's diversity without multiplying company-wide closures — and they materially reduce "why is X a holiday but not Y" tickets.

Step 4: Handle multi-state reality

Build one master calendar with state-wise layers, not one national compromise list. A common structure: 3 national days + state-mandated days per location + company-common festival days + RH quota. Teams see their own location's calendar in the HRMS; managers of cross-state teams see overlays for planning.

Step 5: Publish early and formally

Notify by the deadline your states require (often before the year begins), display/file where mandated, load the calendar into your HRMS and payroll, and freeze it. Mid-year changes should be rare, documented and communicated with lead time.

Restricted Holidays: Running Them Well

• Quota: commonly 1–3 per year per employee, non-carryable.
• Booking: through the leave system like any leave type, with manager visibility but minimal grounds for refusal — an RH denied twice stops being a benefit.
• Coverage logic: where a whole team observes the same RH, treat it like planned leave concentration: minimal staffing by rotation, volunteers first.
• Payroll: RH is a paid day; it should map to its own leave type so reports distinguish it from privilege leave.
• Culture note: the RH menu is a cheap, visible inclusion statement. Review it annually against your actual workforce, not a template.

Working on a Holiday: Premium Pay and Comp-Off

When operations require holiday work — support rosters, retail peaks, production runs, releases — three design questions decide everything:

1. Who can be asked? Define roles subject to holiday rostering; make it known at hiring for those roles. Voluntary sign-up with incentives beats conscription everywhere it can work.
2. What do they get? Per applicable statute and your policy: premium pay, a compensatory off, or a defined combination. Your policy must meet or exceed the statutory floor for covered employees in each state — and should say explicitly what non-covered (managerial) employees receive, because silence there breeds resentment.
3. How is it recorded? Holiday work must be captured in attendance (not "adjusted informally") so premiums and comp-offs are system-generated, not manager-remembered.

Designing a Compensatory Off Policy That Works

Comp-off is where good intentions go to die in most companies: credits granted verbally, tracked in spreadsheets, expiring silently, denied at redemption. Design it like a real system.

Eligibility and trigger

Define precisely what earns a comp-off. Common triggers: working a notified holiday; working a weekly off; and (in some policies) substantial extra hours on a working day beyond a defined threshold — though many companies handle that via overtime instead, and mixing the two carelessly creates double-payment claims. State the minimum hours on the holiday required to earn the credit: full-day credit for a full shift is typical; define the half-day rule explicitly.

Credit mechanics

• Accrual: credit created automatically from attendance data when holiday/weekly-off work is approved — pre-approval, not retrospective discovery.
• Validity: credits commonly expire 30–90 days from accrual. Short enough to ensure rest actually happens near the exertion; long enough to be usable. Pick one number and enforce it with system reminders at 14 and 7 days before lapse.
• Redemption: booked like leave, with manager approval governed by normal coverage rules; a comp-off cannot be "denied until it expires" — build an escalation path when redemption is refused twice.
• Lapse rule: decide honestly — lapse with reminder, auto-encash, or extend-on-denial. For statutorily covered employees, ensure your mechanics respect the substitution windows your state prescribes; for everyone else, pick the rule your culture can defend.
• Encashment: some companies pay out unexpired credits at basic or gross rate on exit or lapse; if you do, define the rate and tax it as salary. If you don't, say so.

Approval workflow

Holiday work request (manager) → employee consent where required → attendance capture → automatic credit → redemption booking → payroll sync. Every arrow is a place spreadsheets fail and systems don't.

What to exclude explicitly

• Comp-off for "checking messages" or incidental remote work — define holiday work as scheduled, approved duty.
• Stacking comp-off on top of holiday premium where your framework treats them as alternatives (or state clearly when both apply, if your statute so requires).
• Transfer of credits between employees; cash-conversion on demand mid-tenure unless policy says so.

Comp-Off vs Overtime: Keep Them Straight

Covered workers can be entitled to overtime premium and rest-day substitution per their statute — your policy must not use one to cancel the other where the law requires both. Take state-specific advice for factory and retail populations.

Weekly Offs and Rostering

• Publish rosters in advance with the weekly off visibly assigned; late roster changes are the top source of weekly-off violations.
• Respect maximum continuous working days per your applicable law when designing rotations.
• If a weekly off must be worked, treat it with the same rigour as a holiday: approval, capture, premium or substituted rest per rules.
• For six-day-week establishments moving to five, document whether the second off is a company off (policy) or statutory weekly off — the distinction matters if you ever ask people to work it.

Shift Workers and 24/7 Operations

Continuous operations cannot close for holidays; they can still be lawful and fair:

• Roster the holiday consciously: minimum crews by rotation, with the holiday premium/comp-off applied automatically to everyone rostered.
• Rotate festival burden year over year — the same team should not lose the same festival two years running; keep a simple fairness log.
• Night shift overlaps: define which calendar day a night shift "belongs to" for holiday purposes (start-of-shift date is the common convention) and apply it consistently.
• Regional swaps: multi-city operations can route work to the city not on holiday — plan capacity in the calendar phase, not the night before.

Payroll Treatment and the Sandwich Rule

Holiday pay basics

Notified holidays are paid days; they do not reduce monthly wages. Holiday work premiums enter payroll from attendance records with their own pay head — never merged into "incentives". Comp-off redemption is a paid absence mapped to its leave type; lapse-encashment, where offered, is a taxable earning line.

The sandwich rule

The sandwich question: if an employee takes leave on Friday and Monday, do the intervening Saturday–Sunday (or a holiday adjoining leave) count as leave too? Law does not impose one universal answer for private establishments; it is a policy choice with fairness constraints. Common positions:

• No sandwiching: offs and holidays adjoining leave are never counted as leave — simplest, most generous, easiest to defend.
• Sandwich on both sides: intervening offs count as leave only when leave is taken on both adjacent working days — the most common middle path.
• LOP-only sandwiching: intervening offs count only when the adjacent days are unpaid (LOP) — protects pay for funded leave, discourages unpaid stretching.

Whichever you choose: write it with worked examples in the policy, configure the leave system to apply it automatically, and apply it identically to everyone. Sandwich disputes are almost always consistency disputes.

Communication and Tooling

• Publish the state-wise calendar in the HRMS before the year starts; push reminders before each holiday (with "who is rostered" clarity for 24/7 teams).
• Show every employee their own view: holidays for their work state, RH quota and balance, comp-off credits with expiry dates.
• Give managers a team overlay for planning around multi-state holidays.
• Keep the policy document — calendar rules, holiday-work mechanics, comp-off system, sandwich rule — as one page in the handbook, versioned and dated.
• Automate the boring failure points: credit creation from attendance, expiry reminders, payroll sync of premiums and redemptions.

Worked Example: Retail Chain Across Three States

"UrbanBasket", a fictional 400-employee grocery retail chain, runs stores in Karnataka, Maharashtra and Telangana, a Bengaluru head office, and a 24/7 dark-store operation.

Calendar build: HR maps each state's mandated national and festival holiday requirements and deadlines; store calendars carry their state's mandated days plus company-common festivals; head office follows the Karnataka retail calendar; every employee gets 2 RH days from a 14-option menu. The consolidated calendar is filed/displayed where required and loaded into the HRMS in December.

Holiday operations: stores stay open on several festival days per state law where permitted; store staff who work a notified holiday automatically receive the state-required premium and a comp-off credit valid 60 days, both generated from the rostering system. Dark-store night crews follow the start-of-shift convention; festival rosters rotate so no crew repeats last year's worked festival.

Comp-off flow in practice: a Hyderabad store associate works Independence Day; her attendance record auto-creates a credit; the app reminds her at day 46 and day 53; her manager's first refusal (staffing) auto-escalates on the second attempt; she redeems in week eight; payroll shows the redemption as a paid comp-off day. No spreadsheet, no memory, no dispute.

The result: three inspections across two states pass without observations; festival-season attrition in stores drops against the prior year; and the HR inbox's January holiday-question volume falls to a trickle — because every answer is visible in the app.

Common Disputes and How to Prevent Them

1. "The other office got that holiday." Prevent with published state-wise logic and RH quota. Different states genuinely have different laws; say so upfront.
2. "My comp-off expired." Prevent with automatic credits, visible balances and two timed reminders; allow extension where redemption was refused for staffing.
3. "I worked the holiday informally." Prevent by requiring pre-approved holiday work for credit; educate managers that informal asks create formal liabilities.
4. "Sandwich leave ate my weekend." Prevent with worked examples in the policy and automatic system application.
5. "Managers are exempt from nothing but get nothing." Decide and state what non-covered staff receive for holiday work; parity of respect even where statute is silent.
6. "Holiday premium missing in payroll." Prevent with a single pipeline: roster → attendance → pay heads; no manual premium entries.

Sample Comp-Off Policy Clauses You Can Adapt

Use these as drafting starters; align them with your states' statutory floors and your own culture before adoption.

Eligibility and trigger:

"A compensatory off ('comp-off') is earned when an employee, with prior written approval of their manager, performs scheduled duty on (a) a notified holiday, or (b) their assigned weekly off. A full-day credit accrues for duty of [6] hours or more; a half-day credit accrues for duty of [3–6] hours. Incidental or unscheduled work, including responding to messages or calls, does not create comp-off credit."

Accrual and validity:

"Comp-off credits are generated automatically from approved attendance records within [3] working days of the duty performed and are visible in the employee's leave balance. Credits are valid for [60] days from accrual. The system will remind employees [14] and [7] days before expiry."

Redemption:

"Comp-offs are availed through the leave system with manager approval, subject to normal coverage requirements. Where a redemption request is declined [twice] for business reasons, the validity of the credit shall be extended by [30] days and the second decline shall be escalated to the HR partner."

Lapse and encashment:

"Credits unavailed on expiry shall [lapse without payment / be encashed at the rate of one day of basic salary per credit in the following payroll]. Credits outstanding on the date of separation shall [be encashed in the full and final settlement / lapse]. Encashment, where applicable, is taxable as salary."

Statutory precedence:

"For employees covered by applicable shops and establishments, factories or other legislation prescribing premium wages and/or substituted rest for holiday or weekly-off work, this policy shall be read subject to those requirements, which shall prevail where more beneficial."

Five clauses, one page — and every recurring comp-off argument in your company now has a written answer.

Special Situations Your Policy Should Answer

Real calendars generate edge cases. Decide these in advance and write them down:

• Holiday falling on a weekly off: is a substitute holiday granted? Many employers do not substitute (the days simply coincide); some states or standing orders may direct otherwise for covered categories. State your rule.
• Holiday during earned leave: a notified holiday inside a leave stretch should not be debited as leave (subject to your sandwich rule for offs). Configure the leave system to skip holidays in debit calculations and say so in the policy.
• Holiday during LOP: conversely, most policies do not pay holidays that fall inside an unauthorised or unpaid absence stretch; if that is your position, document it — this is a frequent dispute.
• Holiday in the notice period: notice periods run through holidays; holidays do not extend notice unless your contract says otherwise. Write it to pre-empt exit-week arguments.
• Mid-year joiners and RH quota: full quota regardless of joining date, or prorated (e.g., 1 RH if joining after 30 June)? Either is defensible; pick one.
• Comp-off earned just before exit: allow redemption during notice subject to coverage, or encash in F&F per policy — silent lapse on exit is the least defensible option.
• Client-site employees: deputed staff often face the client's working calendar; state whether they follow the client calendar with comp-offs for differences, or your calendar with client-day adjustments. Never leave deputed employees to negotiate holidays individually.
• Transferred employees mid-year: an employee moving from Maharashtra to Karnataka mid-year switches calendars from the transfer effective date; reconcile any material difference through RH or comp-off adjustments rather than clawbacks.

The Annual Holiday Governance Timeline

Treat the calendar as a yearly project with owned milestones rather than a December scramble:

• October: collect next year's state notification drafts and festival dates; poll location leaders on choice-based days; review this year's dispute log for policy fixes.
• November: finalise state-wise lists; legal check against each state's mandated days and filing requirements; leadership sign-off; RH menu refresh.
• December: file/display where required; publish to all employees; load calendars, RH quotas and comp-off rules into the HRMS and payroll; brief managers of 24/7 teams on festival rosters.
• January: answer-week — a short FAQ push in the first week eliminates most calendar tickets for the year.
• Quarterly: audit comp-off ledgers (accruals vs attendance, expiries, refused redemptions), verify premium pay heads posted correctly, and check remote-employee state mappings for movers.
• After each major festival cluster: 30-minute retro with operations — roster fairness, premium accuracy, coverage gaps — feeding next year's October review.

Companies that run this loop stop rediscovering holiday chaos annually; the calendar becomes settled infrastructure.

Metrics: How to Know the System Is Working

A handful of numbers, reviewed quarterly, tells you whether policy is functioning or performing:

• Comp-off utilisation rate: credits redeemed ÷ credits accrued. Healthy systems run high; a low rate means rest is being earned but not taken — a fatigue and liability signal, not a savings.
• Expiry rate with refusal history: credits that lapsed after one or more refused redemptions should be near zero; each one is a process failure with a name attached.
• Holiday-work concentration: hours of holiday duty by team and by person; the same names recurring every festival is a rostering fairness problem in the making.
• Premium accuracy: sampled holiday-work records vs payroll premium lines; target zero manual corrections.
• Calendar query volume: tickets in January and around major festivals, trending down year over year as communication improves.
• Roster advance notice: average days between roster publication and the holiday — visibility your frontline can plan lives around.

None of these require analysis talent; all of them fall out of an HRMS that captures roster, attendance, credits and payroll in one pipeline.

Frequently Asked Questions

How many holidays is an employer required to give in India?

It varies by state. The national days — Republic Day, Independence Day and Gandhi Jayanti — are near-universally required, and states prescribe additional festival holidays (numbers and selection mechanics differ under each state's holidays or shops and establishments law). Verify your state's current notification; multi-state employers need state-wise calendars.

Can a company stay open on a national holiday?

Some establishments operate under exemptions or sectoral permissions, and where covered employees work such days, premium pay and/or substituted holidays per the applicable statute are required. Do not improvise here — check your state's rules for your establishment type.

What is a restricted holiday (RH)?

An optional holiday chosen by the employee from a company-notified menu, within an annual quota (commonly 1–3). It lets a diverse workforce observe different festivals without closing the company for all of them.

How long should comp-offs remain valid?

Common practice is 30–90 days from accrual. Statutory substitution windows (where they apply to covered employees) set the floor; within policy discretion, pick a single validity, remind before expiry, and define what happens on lapse.

Is comp-off encashable?

Only if your policy says so. Where offered, define the rate (basic vs gross), the events (lapse, exit) and tax it as salary. Where not offered, state that clearly — silent policies create implied promises.

What is the sandwich rule for holidays and weekends?

It is the policy choice of whether offs/holidays falling between leave days count as leave. There is no single statutory answer for private establishments; pick a position, document worked examples, configure your leave system to apply it, and be consistent.

Do remote employees follow the office calendar or their home-state calendar?

Best practice — and the safer compliance reading — is the state where the employee actually works. Map every remote employee to a work state and serve them that calendar; it also keeps PT/LWF and other state-linked payroll items consistent.

Are interns and contract staff covered by the holiday list?

Interns typically follow the establishment's calendar by policy. Contractor personnel follow their employer's obligations — but principal employers in regulated sectors should ensure vendor compliance, since holiday violations inside your premises become your reputational problem.

Conclusion: Boring by Design Is the Goal

A great holiday and comp-off system is one nobody talks about: the calendar arrives early and matches the law of every state you touch; holiday work is scheduled, consented and premium-paid; comp-offs appear automatically, get used, and never die silently; payroll reflects all of it without a single manual entry. That is not bureaucracy — it is respect, encoded in process.

Getting there manually across states, shifts and spreadsheets is the hard way. CozyHR makes it the default: state-wise holiday calendars, restricted-holiday quotas, roster-linked comp-off credits with expiry reminders, sandwich-rule automation and payroll sync, all in one system your employees can see. If your January still starts with holiday-list confusion, start a free CozyHR trial and make next year's calendar the least controversial document you publish.

This article is general guidance for HR practitioners, not legal advice. Holiday entitlements, premium mechanics and working-time rules vary by state and sector and continue to evolve under the labour codes — verify current state notifications before finalising policy.