How to Build Your 2027 Holiday Calendar

Building the 2027 holiday calendar looks like a thirty-minute job and turns into a three-month project the moment you take it seriously. A holiday calendar quietly sets your payroll rules, attendance logic, shift rosters, client commitments, and a meaningful part of how employees feel about working at your company. September is the right time to start, because the inputs you need arrive between now and December, and approvers get harder to reach as the year closes. This guide walks through the full build — the legal layers, the design choices, the coverage maths, the policy language, and the HRMS configuration.

Why the Holiday Calendar Is a Bigger Decision Than It Looks

Most HR teams inherit the holiday calendar as an annual chore. Someone opens last year's list, shifts the dates, gets a signature, and posts a PDF on the intranet. That works right up until the year it doesn't.

Here is what a single line on your company holiday list India-wide actually controls:

• Payroll. A declared holiday is normally a paid non-working day. If someone works it, you have triggered a second set of rules — compensatory off, premium pay, or both.
• Attendance. Your attendance engine has to know the day is a holiday, or it marks the whole location absent. Trivial, until one of three locations was never loaded into the system.
• Leave accounting. Whether a holiday sandwiched inside a leave spell is deducted depends entirely on your written policy. Without one, you will be arguing about it in March.
• Client SLAs. For IT services, BPO and GCC work, your holiday list is effectively a contractual document. Closing on a day your client is working, unannounced, is a service incident.
• Shift rosters. In manufacturing, retail, healthcare and 24x7 support, the holiday calendar is a rostering input, not a wall poster.
• Sentiment. Employees compare holiday lists across companies and across their own offices. A calendar that visibly favours one region or one faith generates resentment no engagement survey will surface.

None of this is hard. It just needs to be done deliberately, in the right order, at the right time of year.

The Three Layers of an Indian Holiday List

A holiday calendar in India is three stacked layers, each with a different source of authority and a different amount of discretion available to you.

Layer 1: National Holidays

A small set of days is observed essentially everywhere in India, across states and establishment types. These anchor your calendar and are the easiest part of the build.

Even here, do not assume. Whether these days are paid, whether working on them attracts a premium, and whether they can be substituted is governed by the rules applicable to your establishment type and state. Read the actual notification.

Layer 2: State-Declared Holidays

This is the layer that catches people out. State governments issue holiday notifications each year, and the days they declare vary considerably. The applicable framework depends on what kind of establishment you run.

• Shops and commercial establishments — most offices, retail outlets, IT and services firms — are governed by the Shops and Establishments Act of the relevant state and the rules made under it.
• Factories and industrial establishments may fall under a different set of state rules, often with a separate notification mechanism and different obligations for declared holidays.
• Some states use a two-tier structure, distinguishing compulsory holidays from a wider list from which employers or employees select a smaller number. The vocabulary differs — "compulsory," "declared," "optional" and "restricted" are used differently in different notifications.

Three consequences matter more than any general guidance an article can give you.

The number of holidays you must grant differs by state and establishment type. Do not carry an assumed number across state lines. What is correct for a Bengaluru office may be wrong for a Pune plant.

The 2027 notification does not exist until the state publishes it. Most states publish in the latter part of the preceding year. Your process has to accommodate designing a calendar before all inputs are confirmed.

Verify against the official source. The state labour department or official gazette is the authority — not an aggregator site, not last year's list, not what a vendor told you. When the 2027 notifications are released, someone must open each applicable notification, read it, and record what it says. Make that a named task with a named owner.

Layer 3: Company-Chosen, Optional and Restricted Holidays

This is your discretionary layer, and where calendar design actually happens. Depending on the state framework and your policy, it can include additional fixed holidays beyond the requirement, a pool of optional or restricted holidays from which each employee selects a set number, company closures such as a year-end or maintenance shutdown, and location-specific festival days.

This layer is where you solve for fairness, coverage and cost. It also generates the most policy questions, so it needs the clearest documentation.

Who Decides What

A holiday calendar one person builds alone is a holiday calendar that will be challenged. Decide the decision rights before drafting.

Where a works committee, union or long-standing settlement exists, treat consultation as a required step with its own timeline. Changes to the number or identity of holidays in a unionised establishment are exactly the kind of change that generates disputes when made unilaterally.

The Step-by-Step Build Process

This is the spine of the work. Run it in order — most of the pain in leave calendar planning comes from doing step 6 before step 2.

Step 1: Set the Design Principles First

Write down four or five principles and get them agreed. It takes an hour and saves weeks, because every later disagreement can be settled by pointing at a principle rather than relitigating the calendar.

• Representation. The fixed list should reflect the actual composition of the workforce at each location across faiths and regions; the optional pool absorbs the rest.
• Predictability. Employees should be able to plan personal travel — publish early and do not move dates afterwards.
• Coverage. No holiday design leaves a critical function uncovered without a named plan.
• Parity with explained variance. Total holiday count should be broadly comparable across locations, with differences driven by legal requirements rather than accident.
• Cost discipline. Every paid non-working day has a real cost, especially in shift operations where holiday working attracts premium pay.

State them in the calendar document itself. It changes the tone of every conversation that follows.

Step 2: Gather Inputs

Start collecting in September, because several inputs have long lead times.

• 2027 state notifications for every state where you have an establishment. Track them and set follow-ups with a named owner per state.
• Your 2026 calendar per location, plus what actually happened — which optional days were taken, which holidays saw people working, which generated complaints.
• Client holiday calendars for top accounts. Ask in October; clients publish at different times.
• Festival and observance dates for 2027 from a reliable, verifiable source. Many festival dates follow lunar or regional calendars and are not fixed in the Gregorian year. Do not guess or carry forward from a previous year.
• Employee demographics by location at an aggregate level, to inform which national and festival holidays matter at which site.
• Operational calendars — shutdown windows, financial year-end close, audit periods, peak retail seasons, release windows.
• 2026 attendance and roster data showing how many people actually worked each declared holiday, and what it cost.

Step 3: Fix the Non-Negotiables

Lay down the days you have no discretion over — the skeleton of the calendar. National holidays applied everywhere; state-declared compulsory holidays per the applicable 2027 notification; anything fixed by a settlement or contract; any day the establishment must legally remain closed.

Mark each one with its source. When someone asks in February why a day is on the Pune list but not Noida's, you want to answer in ten seconds.

Step 4: Design the Optional or Restricted Holiday Pool

The optional pool separates a good calendar from a mediocre one. Decide:

• How many optional days each employee gets — often two or three, depending on your state framework and total count.
• How wide the pool is. Ten to fifteen candidate days lets employees across faiths and regions find days that matter. Four does not.
• How days enter the pool — from the state notification's optional or restricted list, or because employees asked.
• Selection mechanism and a hard cut-off. See the sample policy below.
• Blackout dates, if any.
• What happens to unused days. Almost always they lapse. Say so explicitly.

Step 5: Model Coverage Per Location and Per Team

This step is skipped more than any other, and it is what turns a calendar into an operational plan. For each holiday and location, answer: which teams must still deliver, how many people that needs, whether those people are on the same holiday, whether coverage can come from another location on a different calendar, and what that coverage costs in comp-off or premium pay.

Cross-location coverage is the most underused lever in multi-state companies. If Bengaluru is closed for a Karnataka-declared holiday and Noida is open, Noida is the natural coverage plan — provided the skills exist and the client accepts it.

Step 6: Map Long Weekends and Bridge Days

Once fixed days are placed, map them against 2027's weekends. Three patterns emerge.

Natural long weekends — a holiday adjacent to a weekend. Flag them early so delivery teams plan around them.

Bridge days — a single working day trapped between a holiday and a weekend. Productivity is genuinely low and absenteeism genuinely high. Three sensible options: declare it a holiday and accept the cost; keep it working but pre-approve leave generously; or make it optional-holiday-eligible so employees choose individually. Pick one and apply it consistently. The worst option is deciding ad hoc in the same week.

Holidays falling on a weekend. Some 2027 holidays will land on a Saturday or Sunday. Decide the rule now, because this is a guaranteed January question.

Whether a substitute holiday must be granted when a declared holiday falls on a weekly off can depend on the applicable state rules and establishment type. Check the position per state rather than applying one assumption everywhere.

Step 7: Consult and Communicate the Draft

Circulate the draft in October or early November to site heads, delivery leads, payroll, legal, and any works committee or employee forum. Give them a deadline and a specific question — not "any comments?" but "does this leave your function uncovered on any date, and which?"

Where employee input helps, a short structured survey on which optional days matter at each location works well. Keep it advisory and say so, otherwise you create an expectation of a vote.

Step 8: Approve, Publish, Load and Lock

Get formal approval from whoever holds the decision right. Then publish, load into the HRMS, and lock the calendar against edits except through a defined change process.

Locking matters. An unlocked holiday master gets edited in March by someone fixing one employee's attendance issue, and the edit silently changes payroll for a whole location.

Multi-Location and Multi-State Companies

Once you have more than one office, the hardest question is not which days go on which list. It is which list applies to which employee.

Build Location-Specific Calendars, Not One Merged List

Resist the merged calendar with footnotes. Merged calendars are hard to read, hard to configure, and produce attendance errors. Build a distinct calendar per location on a shared national core: core calendar (national holidays, everywhere), location calendar (core plus state-declared days), optional pool (common or location-specific), and special calendars for shift or plant employees whose working pattern genuinely differs.

Assigning a Calendar to an Employee Record

This needs one written rule applied mechanically. The cleanest version: the holiday calendar follows the employee's registered work location on the employee master — the establishment under which they are engaged — not where they happen to be sitting on a given day. Then handle the edge cases explicitly.

Two implementation notes. Make "holiday calendar" a mandatory field with no blank default — a blank field silently inherits something and nobody notices until payroll. And run a quarterly report listing employees whose assigned calendar does not match their location.

Don't Forget the Satellite Office

The most common multi-location failure is the office with eleven people that nobody remembers. It sits in a state whose notification nobody checked, on a calendar copied from headquarters, and it either works on days it should be closed or closes on days never approved.

Maintain an establishment register — every registered location, its state, establishment type, headcount and calendar owner — and reconcile the 2027 calendar against it line by line.

Designing the Optional Holidays Policy

A one-sentence optional holidays policy generates a hundred questions. A complete one answers: how many days, whether entitlement is pro-rated for mid-year joiners, how selection works, the cut-off date, whether selections are auto-approved or manager-approved, which dates are blacked out, whether changes are permitted after the cut-off, whether unused days lapse, how availed days interact with leave balances, and what happens if business needs force someone to work on a day they selected.

Advance annual selection is stronger for coverage planning; rolling selection is more flexible for employees. Pick one, state it, enforce it.

Sample Policy Text You Can Adapt

Lift this into your policy document and edit it. Review against your applicable state rules and your leave policy before publishing.

Optional Holidays Policy — Calendar Year 2027 1. Entitlement. Each confirmed and probationary employee on the rolls may select two (2) optional holidays during calendar year 2027 from the Optional Holiday Pool published with the Company Holiday Calendar for their assigned location. An optional holiday, once availed, is a paid non-working day and is not deducted from any leave balance. 2. Pro-rating. Employees joining on or after 1 July 2027 are entitled to one (1) optional holiday for the remainder of the year. Employees whose last working day falls before a selected optional holiday forfeit that selection; no encashment or payment in lieu applies. 3. Selection and cut-off. Employees must record their selections in the HRMS on or before 31 January 2027. Selections received later will be considered only where the requested day falls at least fifteen (15) calendar days after the request and the reporting manager approves. Employees who make no selection by the cut-off forfeit the entitlement for the year. 4. Approval. Selections made by the cut-off and not falling within a published blackout period are auto-approved. Selections within a blackout period, or made after the cut-off, require reporting-manager approval. 5. Blackout periods. Optional holidays may not be availed during the periods published in Annexure B (financial year-end close, statutory audit window, and any release or peak-season windows notified by the business at least thirty days in advance). 6. Changes. An employee may change one selection after the cut-off with reporting-manager approval, provided the request is made at least fifteen (15) calendar days before both the original and the replacement date. 7. Working on a selected optional holiday. Where business requirements require an employee to work on a day they selected, the employee may select an alternative day from the Pool for the remainder of the year, subject to availability and manager approval. Alternatively, the day may be treated as holiday working under the Leave and Holiday Policy. 8. Lapse. Optional holidays not availed within calendar year 2027 lapse on 31 December 2027. They may not be carried forward, encashed, converted to leave, or compensated in any form. 9. Shift employees. Employees on rotating shift rosters may avail optional holidays subject to roster coverage, with selections recorded in the HRMS at least thirty (30) days before the requested date. Where the selected day coincides with a rostered weekly off, no substitute day is granted. 10. Interpretation. Where a state notification for 2027 differs from the Pool published here, the state notification prevails for employees assigned to establishments in that state. Questions of interpretation will be decided by the Head of Human Resources.

Adapt the numbers and dates. The important part is that every question an employee could ask has an answer in the text.

Working on a Holiday

Every company that thinks it closes on holidays has people who work on them — support engineers, maintenance crews, retail staff, hospital rosters, security, and anyone covering an offshore client. Design for it rather than discovering it in the payroll run.

Holiday working comes in distinct flavours, and fairness expectations differ across them: planned roster coverage, client-driven coverage under contract, continuous-process operations, unplanned incident response, and deadline-driven work like a release or a statutory filing. Planned roster duty is part of the job; a 2 a.m. incident call is not.

Compensatory Off Versus Premium Pay

Statutory rate requirements for working on a declared holiday, and any requirement to grant a substituted holiday, depend on the applicable state rules and establishment type. There is no single national rate that applies to every employer. Confirm the position for each of your states with your legal or compliance advisor before finalising the policy, and repeat the check annually.

Approval Workflow and Records

1. Pre-approval. For planned coverage, the published roster is the approval.
2. Request. For unplanned work, the manager raises a holiday-working request in the HRMS before the day where possible, or within a defined window after.
3. Capture. Actual working is evidenced — biometric, system login, ticket record, or manager attestation for field roles.
4. Second-level approval for anything generating premium pay above a threshold.
5. Election. The employee chooses comp-off or premium where policy permits, within a stated number of days.
6. Posting. Comp-off is credited with an expiry date; premium flows into that month's payroll input.

Keep a per-instance record: employee ID, date, hours worked, reason category, approver, and compensation outcome, retained for the period your compliance team specifies. That record is what you produce in an inspection, an audit or a dispute — and reconstructing it after the fact is nearly impossible.

Shift and Coverage Planning for 24x7 Operations

For shift operations, the holiday calendar is a rostering input. A few principles keep shift and coverage planning fair and manageable.

Publish rosters early. If the calendar is out in November, the January–March roster can be out in December. Shift employees plan their personal lives around this more than anyone else.

Rotate holiday duty deliberately. Track holiday duty per employee across the year. Without tracking, the same reliable people get rostered on every major festival — unfair, and a retention risk. A year-to-date counter visible to the roster planner solves most of it.

Weight the big days. Working on the biggest festival of an employee's own community is a bigger ask than a routine holiday. Weight those days more heavily in the rotation counter or in the compensation.

Allow swaps, with rules. Both employees agree, the swap is recorded before the date, skills are equivalent, and no overtime or rest-period breach results.

Define minimum coverage per holiday. Agree the headcount and skill mix required on each holiday and publish it. This turns an argument into an arithmetic problem.

Respect rest rules. Holiday rosters are where consecutive-working-day and weekly-rest requirements quietly get breached. Build whatever rules apply to your establishment into the roster tool as hard constraints.

How Holidays Interact With Leave

This produces more tickets than any other part of holiday policy. Decide each rule, write it down, and configure it so it applies automatically.

Holidays Inside a Leave Spell

If an employee takes leave on Thursday and Monday and Friday is a holiday, is Friday deducted? There is no universal answer. Most companies apply a non-sandwich rule to earned leave — intervening holidays and weekly offs are not deducted — and a stricter rule to unpaid or unapproved absence.

The LOP and unapproved-absence rows deserve careful verification — the treatment of holidays inside an unpaid absence period has legal implications and should be confirmed for your establishment type. Configure the rule in the HRMS rather than leaving it to manual calculation. Inconsistent manual application of a sandwich rule is a genuine grievance generator.

Notice Period, Joiners, Leavers and Long Leave

• Notice period. Holidays falling within the notice period normally count as part of it and do not extend the last working day. State this in the policy. Garden leave or waived notice should be spelt out in the separation letter.
• Joiners. No claim to a holiday that falls before the joining date. Optional entitlement is pro-rated per policy.
• Leavers. Holidays after the last working day are not payable or encashable. Where the last working day is itself a holiday, define whether the exit is effective on that day or the preceding working day — it affects full-and-final settlement dates.
• Maternity and statutory long leave. These have their own rules on how holidays and weekly offs are counted. Do not apply your general sandwich rule without checking; configure it as a separate leave-type rule.
• Extended LOP. The treatment of holidays inside a long unpaid period affects both pay and statutory contribution calculations. Test it in a parallel payroll run before January.

Client and Delivery Considerations for Services, IT and BPO

If you sell time, your holiday calendar is a commercial document.

Send your 2027 calendar to key clients in November or December, per delivery location. Late publication is what turns a planned closure into a service failure. For each client, agree in writing which holidays mean full unavailability, which carry reduced coverage and what "reduced" means numerically, which are covered normally, the escalation contacts and response expectations on closed days, and how incidents are handled when the primary team is off. Put this in the delivery plan, not an email thread.

The "We Are Closed But the Client Is Not" Problem

This is the structural tension in Indian services delivery. Your team observes Indian holidays; your client observes theirs. Neither calendar is wrong. Practical mitigations:

• Skeleton coverage on the largest holidays, staffed by a small rotating roster with premium or comp-off, agreed with the client in advance.
• Cross-location coverage where you have sites on different state calendars.
• Follow-the-sun handoff if you have offshore or nearshore presence.
• Advance batching — move deliverables ahead of a known closure rather than promising same-day work.
• A published escalation path with named people and numbers for days you are closed.
• Reciprocity. Ask for the client's calendar too, and plan your team's low-demand days around it.

Be honest in the sales cycle. A calendar shared during contracting is a normal commercial fact. The same calendar discovered in month three is a credibility problem.

A Worked Example: 250 People Across Three Cities

Consider a fictional 250-person IT services company with offices in Bengaluru (140), Pune (70) and Noida (30), plus an eighteen-person support team running two shifts, six days a week, covering European and North American clients.

Total count. Leadership approves a target of twelve fixed holidays plus two optional days per employee — in September, before the specific dates exist. Decoupling the cost decision from the date decision is why it works.

Structure. Four calendars: BLR-2027, PNQ-2027, NOI-2027 and SUPPORT-2027. The support calendar carries the same holidays as the employee's registered location but different working rules — support staff are rostered on holidays and receive comp-off or premium rather than an automatic day off.

Optional pool. Twelve candidate days drawn from the relevant state notifications' optional and restricted lists plus a few employee requests. Selection in the HRMS by 31 January, auto-approved outside blackouts.

Bridge days. Not declared as holidays, but leave on bridge days is pre-approved for up to 60% of each team, allocated through the HRMS from 1 December 2026.

The Trade-Offs

Parity versus local relevance. State-declared days genuinely differ across Karnataka, Maharashtra and Uttar Pradesh. The answer: equal total count everywhere, varying composition. Where a location's state list produced fewer days than the target, the gap was filled from the optional pool as a location-specific fixed day.

Full closure versus skeleton coverage. Four holidays were designated full closures with emergency-only on-call; the rest became reduced-coverage days with a published minimum headcount. Clients were told which was which in December 2026.

Comp-off versus premium. Support staff on rostered holiday duty receive premium pay per the applicable rules for their establishment; delivery employees pulled in for a release receive comp-off with a 60-day expiry. Two rules, each documented, applied by employee group.

The client-site exception. Three Noida employees work at a client's premises under a contract specifying the client's calendar. This was handled as a documented exception on the employee master referencing the contract clause, with the total paid holiday count reconciled so it was not less favourable than their Noida colleagues'.

The bridge-day gamble. The pre-approved-leave approach worked for three of four bridge days. On the fourth, demand exceeded the 60% cap in one pod and the excluded employees were unhappy. The fix for next year: allocate bridge-day leave by a rotation that considers who got it last time, rather than first-come-first-served.

The whole build cost roughly forty hours of HR time across four months, two hours of legal review per state, six hours of payroll configuration and testing, and one leadership meeting. Against the cost of one mis-declared holiday across 250 people, that is a good trade.

Communication Plan: What to Send and When

A calendar nobody knows about is a calendar that does not exist.

The publication pack should contain the calendar per location in a readable one-page format, the optional pool with selection instructions and the cut-off date, the rule for holidays falling on weekly offs, the bridge-day policy, a holiday-working summary linking to the full text, blackout dates, and a named contact for questions.

Publish a calendar file (ICS) per location that employees can subscribe to. A subscribed feed updates if anything changes; an emailed PDF does not. If your HRMS supports calendar feeds, use them.

Configuring the 2027 Calendar in Your HRMS

Publishing and configuring are two different projects. Do the configuration in December, not January.

Holiday master. Create a 2027 master with, per entry: date, name, type (national / state-declared / company / optional), applicable calendar, paid or unpaid, and whether holiday working is permitted and how it is compensated. Do not overwrite the 2026 master — keep it for historical attendance and audit.

Calendar-to-employee mapping. Assign every active employee before the year starts. Then check: zero blank assignments, every calendar matching the registered location or carrying a documented exception, December and January joiners assigned on day one, and employees on long leave assigned rather than skipped.

Attendance and payroll rule links. Confirm holidays are never marked as absence; the sandwich rule is configured per leave type exactly as written; shift employees follow roster rules rather than office rules; LOP interaction is configured; and comp-off credits carry the correct expiry.

Holiday-working capture. Configure the request, approval, compensation election and reporting. Test the full path end to end.

Optional-holiday workflow. Configure the pool, entitlement, cut-off, blackouts, auto-approval, change rule and year-end lapse — then test the failure cases specifically: a blacked-out date, a post-cut-off request, a third selection when two are permitted, and a second change.

Test before January. Run a test payroll with the new calendar loaded, covering at least these cases.

Log the results. Fix failures in December, when the stakes are zero.

Your 2027 Holiday Calendar Build Checklist

September 2026

1. Name a single owner for the 2027 holiday calendar build.
2. Agree and document the design principles.
3. Get leadership agreement on the target total holiday count per location.
4. Compile the establishment register: every location, state, establishment type, headcount and calendar owner.
5. Pull the 2026 calendar per location, plus actual holiday-working data.
6. Set up a tracker for 2027 state notifications with a named owner per state.
7. Review last year's holiday-related grievances and payroll corrections for patterns to fix.

October 2026

1. Request holiday calendars from your top clients.
2. Run an advisory employee survey on the optional holiday pool.
3. Confirm 2027 festival and observance dates against a reliable, verifiable source.
4. Draft the fixed-holiday skeleton per location, marking the source of each day.
5. Draft the optional holiday pool and its blackout dates.
6. Identify all 2027 long weekends and bridge days; decide the bridge-day approach.
7. Decide and document the rule for holidays falling on weekly offs, per location.
8. Model coverage per holiday per location; identify uncovered critical functions.

November 2026

1. Collect and read each applicable 2027 state notification as it is published; record what it says.
2. Have legal confirm the required holiday count and treatment per state and establishment type.
3. Confirm holiday-working pay and substitution requirements per state and establishment type.
4. Circulate the draft to leads, payroll, legal and any works committee with a firm deadline.
5. Consult the works committee or union where the applicable framework or settlement requires it.
6. Reconcile total holiday count across locations; document and justify any variance.
7. Finalise the optional holidays policy, including cut-off, blackouts and lapse.
8. Finalise the holiday-working policy, including approval flow and records to be kept.
9. Obtain formal leadership approval of the calendar and policies.

December 2026

1. Publish the calendar to all employees, per location, with the full publication pack.
2. Send the calendar to key clients with agreed coverage commitments per account.
3. Load the 2027 holiday master into the HRMS.
4. Assign every active employee to a calendar; clear the blank-assignment report to zero.
5. Configure attendance rules, sandwich rules per leave type, and shift-holiday rules.
6. Configure the optional-holiday workflow, cut-off, blackouts and lapse.
7. Configure holiday-working capture, approval and compensation flows.
8. Run the test cases above; log results and fix failures.
9. Publish Q1 2027 shift rosters and open optional-holiday selection.
10. Publish location-wise calendar (ICS) files for subscription.
11. Lock the holiday master; define the change-request process.
12. Brief managers on the rules they will be asked about in January.
13. Diarise a tracker review in case any state issues a supplementary or revised notification.
14. In January, close selection at the cut-off and audit holiday attendance postings across all locations.

Common Mistakes

Copy-pasting last year's calendar. Festival dates move, notifications change, and your locations change. Rebuild from the notifications every year.

Missing a state notification. The most expensive single mistake. Maintain the establishment register and reconcile against it. A new office opened in 2026 puts a new state on your list this year.

Ignoring a satellite office. Ten people in an unchecked state eventually becomes a compliance conversation.

Publishing in January. By then employees have booked travel, clients have planned sprints, and rosters are set. December is the minimum; November is better.

No rule for holidays falling on weekends. Guaranteed to be asked in the first week of January. Decide it in November and check whether any substitution requirement applies in your states.

No optional-holiday cut-off. Without a deadline, selections trickle in all year, managers cannot plan coverage, and December brings a rush.

No record of holiday working. If you cannot produce, per employee per instance, what was worked and how it was compensated, you have an audit problem and no defence in a dispute.

Unlocked holiday master. One well-meaning edit in March changes payroll for a whole location.

Assuming one national rule for holiday-working pay. The applicable rate and any substitution requirement depend on your state and establishment type. Verify each, every year.

Blank calendar field on the employee master. Silent defaults cause most holiday-related payroll corrections. Make the field mandatory.

Frequently Asked Questions

When should we start building our 2027 holiday calendar?

September or early October 2026. That gives you time to collect state notifications as they are published, gather client calendars, consult internally, and configure and test the HRMS. Target publication in early December 2026 at the latest.

How many holidays are we legally required to give?

It depends on your state and establishment type. There is no single national number that applies to every employer in India. The requirement comes from the Shops and Establishments Act and rules of the relevant state for commercial establishments, or from the applicable framework for factories and industrial establishments. Confirm it for each state against the official 2027 notification and with your legal advisor, and do not carry an assumed number across state lines.

Where do we find the official state holiday notification for 2027?

From the relevant state government's labour department or official gazette. Most states publish in the latter part of the preceding year, though timing varies. Track each state you operate in, assign an owner, and read the notification when released rather than relying on aggregator websites or last year's list.

What is the difference between an optional holiday and a restricted holiday?

In everyday Indian workplace usage, both refer to a day drawn from a wider published list that an individual employee may choose to take off, as distinct from a fixed holiday when the whole establishment closes. The exact terminology and treatment vary by state notification and by company policy, so define the term in your own policy and state how many days an employee may select, how selection works, and what happens to unused days.

If a holiday falls on a Sunday, do we have to give another day off?

That depends on the applicable state rules, your establishment type, and your own policy. Some frameworks contemplate substitution; others do not. The practical approaches are to let the day lapse, declare a substitute working day as a holiday, or move the day into the optional pool. Decide the rule per location before publishing, verify whether a substitution requirement applies in each of your states, and write the answer into the calendar document.

How should we handle a fully remote employee who lives where we have no office?

Assign them to the calendar of the nearest company establishment, or to a designated default calendar, and record the assignment on the employee master at onboarding. Make the holiday calendar field mandatory so no employee ever has a blank assignment, and publish the rule so remote employees know which calendar governs them before they plan travel.

Are holidays deducted from leave if they fall in the middle of a leave spell?

That is entirely a matter of your written policy, applied per leave type. Most companies do not deduct holidays or weekly offs falling inside an approved earned-leave spell, but many apply a different rule to loss of pay and unapproved absence. Document it per leave type, configure it in the HRMS so it applies automatically, and verify the treatment for statutory leave such as maternity leave with your compliance advisor rather than applying a generic rule.

What should we pay someone who works on a declared holiday?

The statutory position depends on your state and establishment type, so verify it for each location before setting policy. Beyond the statutory floor, most companies use compensatory off, premium pay, or a choice between the two, applied differently to planned roster duty and unplanned incident work. Whichever model you pick, capture every instance in the system with date, hours, approver and compensation outcome.

Bringing It Together

A good 2027 holiday calendar is not a document. It is a set of decisions — about coverage, fairness, cost and predictability — that happen to be expressed as a list of dates. Made deliberately in September, those decisions cost a few dozen hours. Made reactively in January, they cost client escalations, payroll corrections and a quarter of avoidable grievances.

Three things matter most: verify every state notification for 2027 against the official source rather than reusing last year's list, decide the edge cases in writing before you publish, and get the calendar into your HRMS and tested in December rather than discovering configuration gaps in the first payroll run.

If your holiday calendar currently lives in a spreadsheet and a PDF on the intranet, the configuration work is where most of the friction sits. CozyHR handles location-wise holiday masters, calendar-to-employee mapping, optional-holiday selection with cut-offs and blackouts, sandwich-rule configuration per leave type, and holiday-working capture that flows into payroll — so the rules you write in November are the rules that actually run in January. If that is the part of this project you would rather not do by hand, it is worth a look while you are building the 2027 calendar anyway.

Either way: start in September, verify against the official notifications, decide the edge cases in writing, and publish early. Your January self will be grateful.