How to plan leave cover around the festival season
A practical way to handle the festival leave crush: publish the window early, cover single points of failure, and decide what work simply pauses.
Everybody wants the same fortnight
Most Indian businesses lose large chunks of their team in uneven blocks through the festival months. The crush is rarely evenly spread. A Kolkata office empties around Durga Puja. A Delhi team empties around Diwali. A Chennai team books travel around Pongal and a Kerala team around Onam. Draw your staff from several states and you face four or five separate crunches rather than one.
The failure mode is predictable. Leave gets approved one request at a time in the order requests arrive. By mid October somebody notices that the only person who can release a payment or sign off a dispatch is on a train.
What a cover plan costs and what it cannot fix
A cover plan cannot create capacity. If seven of twelve people are away then five people are doing the work of twelve and no rota changes that arithmetic. It also will not stop customers expecting their usual response. Decide which commitments you will miss rather than discovering it on the day.
The direct costs are modest and real. Cross-training takes a few hours per critical task. Paying somebody to stay back through a festival costs more than an ordinary day whether in overtime or compensatory leave. Temporary cover carries its own fee and service fees in India carry GST at 18%. The bigger cost is planning time in September which competes with the sales push landing in the same weeks.
Who needs a rota and who should simply shut
A business whose customers also go quiet should not build an elaborate rota. A firm selling to Indian corporates often finds its own buyers unreachable through the same fortnight. Running a skeleton crew to answer a phone that does not ring wastes goodwill. Close properly instead. Announce the dates in advance and let the team travel.
A rota earns its keep when demand rises rather than falls through the season. Retail, logistics, hospitality, gifting and anything in the wedding supply chain all peak exactly when staff want to leave. The same applies to any service business holding a written response commitment, and to statutory or payment duties that do not pause for a holiday. A business of three or four people should keep this very light. One shared message naming who is away which week is enough. Formal cover documentation at that size is theatre and the team will ignore it.
How to build the plan
Publish the window before anyone books travel. Name the weeks you consider peak and the date by which leave requests must be in. Requests arriving later compete for what is left rather than jumping the queue by surprise.
Then list tasks rather than people. Write down every task that must happen regardless of who is present: payments released, invoices raised, dispatches confirmed, statutory submissions, client escalations, premises access. Name a primary and a deputy for each. Any task with one qualified name is a single point of failure and that is where your cross-training hours belong. Sitting the deputy beside the primary for one real run beats any written note.
Allocate leave by festival rather than by seniority or request order. Somebody who observes Diwali has a weaker claim on the Puja week and saying so openly is fairer than it sounds. Then decide what pauses and tell clients in the same message that announces your dates.
How to judge whether the plan held
Headcount present flatters. A rota showing six people available daily looks like coverage and says nothing about whether those six could do the work that arrived.
What matters is the list of things that went wrong because the right person was away. Keep a running note through the window of every moment somebody said we cannot do this until he is back. Review it in January. It is the most accurate map of your dependency risk you will ever get and it costs nothing to collect. Track late client commitments alongside it since those carry a cost you can see.
The common mistake
Approving leave first come first served. It feels even handed and it reliably strands the business, because the people who book earliest tend to be the organised senior people whose work has no deputy. The expense shows up as a stalled payment or a dispatch error during your busiest fortnight and sometimes as a client who quietly moves on afterwards.
The related error is forgetting the owner. Final approval on money often sits with one person who has not delegated it. That person then spends their own festival answering calls. Giving a deputy a bounded approval limit for the window costs one afternoon of thought.
A note on leave entitlement
Holiday and leave entitlement for Indian employers is not one national rule. It comes from state level shops and establishments legislation plus any factory or industry specific rules that apply to you, and the list of paid festival holidays genuinely differs by state. Rules on carrying leave forward follow the same pattern. A qualified professional should confirm what applies to your establishment and your state before you set policy on it. The practical consequence is that a company with offices in two states may owe different holidays to two employees doing identical jobs.
This guide explains how something works. It is not legal, tax or financial advice, and rules change. Confirm anything regulatory with a qualified professional before you act on it.