Hybrid & Work From Home Policy: An India Guide

Hybrid & Work From Home Policy: An India Guide

Most Indian companies did not choose their hybrid setup. It happened to them. A work from home policy that started as a temporary arrangement quietly became permanent, and now half the team comes in on Tuesdays, one engineer has moved to Indore, the sales team has never seen the inside of the office, and HR is fielding the same three questions every week: who is allowed to work remotely, how is attendance being counted, and why did that person get promoted when they are never in the office?

If that sounds familiar, this guide is for you. It is not an argument for or against remote work. It is a practical manual for turning an informal arrangement into a written, fair, measurable and reasonably compliant hybrid work policy that an Indian SMB can actually operate — including how to handle a return to office push without burning trust.

We will cover model selection, eligibility rules, attendance and time capture for distributed teams, output-based performance management, allowances and reimbursements, data security, the India-specific compliance surface, proximity bias, remote onboarding, monitoring boundaries, a full policy template you can adapt, the metrics that matter, and a 60-day rollout plan.

---

Why an Unwritten Hybrid Arrangement Eventually Breaks

Informal hybrid works beautifully for about eighteen months. Then it does not. The failure is predictable, and it usually arrives through one of six doors.

1. Fairness drift. Without written eligibility rules, remote access becomes a function of manager generosity. One team lead is relaxed, another insists on five days. Employees compare notes. What was once a perk becomes evidence of favouritism, and HR inherits a morale problem it did not create.

2. The attendance vacuum. Payroll needs a defensible record of days worked, leave taken and unpaid absence. If the office biometric device is the only source of truth, every remote day is invisible. Teams start "adjusting" attendance manually at month end, and the audit trail becomes fiction.

3. Leave leakage. When nobody can see who is working, people stop applying for casual leave for short absences. They "work from home" instead. Leave balances stay untouched, encashment liability grows, and managers lose visibility into who is actually available.

4. The scaling break. A ten-person team can coordinate over WhatsApp. At forty, informal coordination collapses. Meetings get scheduled at 8 pm because nobody agreed on core hours. Someone is always missing context.

5. The compliance surprise. An employee relocates to another state. Six months later, someone asks whether professional tax is being deducted correctly, whether the Shops and Establishments registration covers them, and what happens if they raise a POSH complaint about a colleague they have only met on video.

6. The RTO collision. Leadership decides the office needs to be busier. Because nothing was ever written down, employees genuinely believed remote work was a permanent term of employment. The announcement lands as a betrayal rather than a policy change, and the best people — the ones with options — leave first.

A written policy does not prevent disagreement. It converts disagreement from a personal grievance into a process question, which is a far more manageable thing.

---

Choosing a Hybrid Work Model: The Six Realistic Options

Before writing clauses, decide what you are actually running. Most Indian SMBs land in one of six patterns. Pick deliberately rather than drifting.

The six models explained

Fully remote. No office, or a small co-working presence for occasional meetings. Everyone works from wherever they are. Common in early-stage product companies, agencies and services businesses with distributed clients.

Remote-first. An office exists and is available, but all processes assume remote is the default. Documentation is written, decisions are recorded, meetings are video-first even when some people are in a room together.

Anchor days. The company or each team fixes specific days when everyone is in the office — say Tuesday and Thursday. The remaining days are flexible. This is the most common Indian hybrid pattern because it preserves collaboration without daily commuting.

Team-choice. Each team decides its own in-office rhythm within a company-wide minimum. Engineering may choose one day, sales three. Flexible, but requires a floor to prevent complete divergence.

Office-first with flex. The office is the default. Employees get a defined allowance of remote days per month — typically four to eight — to be used with manager approval.

Role-based eligibility. Remote entitlement is attached to the role, not the person. Roles are classified as fully remote-eligible, hybrid-eligible or onsite-required based on objective job requirements.

Comparison of hybrid work models

A practical recommendation

For most Indian SMBs between 25 and 300 employees, anchor days layered on role-based eligibility is the strongest combination. Role-based eligibility answers "who can work remotely and why" objectively. Anchor days answer "when are we together" predictably. The two together remove almost all the discretion that causes resentment.

---

Defining Role Eligibility Without Manager Discretion

The single most damaging design flaw in a work from home policy is making eligibility a manager decision. It guarantees inconsistency, and inconsistency in India — where teams talk, and where perceived unfairness travels fast — is what turns a policy into an attrition driver.

Replace discretion with a test. Score every role against objective criteria, then let the score determine the category.

The eligibility scoring framework

Score each role from 0 to 3 on five factors:

1. Physical presence requirement. Does the work require physical access to premises, equipment, inventory, cash, laboratory apparatus or secure hardware? (0 = essential daily, 3 = never required)

2. Data sensitivity. Does the role handle regulated, confidential or customer-identifying data that contractually requires a controlled environment? (0 = highly restricted, 3 = low sensitivity)

3. Collaboration intensity. How much of the work depends on unplanned, high-bandwidth interaction with others? (0 = constant, 3 = largely independent)

4. Output measurability. Can the output of this role be assessed on deliverables rather than presence? (0 = presence is the output, 3 = fully deliverable-based)

5. Supervision and development stage. Is the person in the role newly hired or early-career and dependent on observational learning? (0 = first 90 days or first job, 3 = experienced and autonomous)

Mapping scores to categories

Publish the scores. Not the individual manager conversations — the actual role classification list. When a customer support associate asks why the backend developer works remotely full-time and they do not, you want the answer to be a published matrix, not "that's what their manager agreed."

Handling the exceptions

Objective rules still need an exception path, or they become brittle. Build one deliberately:

• Medical and accessibility exceptions — temporary or ongoing remote arrangements supported by documentation, approved by HR rather than the line manager.
• Caregiving exceptions — time-bound arrangements for employees managing elder care, a new child or a family medical situation.
• Relocation requests — a formal application route for employees who want to move cities, with a defined review process.
• Probation overrides — new joiners in remote-eligible roles may still be required onsite for the first 30 to 60 days.

Every exception should have a written end date or review date. Permanent undocumented exceptions are how the whole system unravels.

---

Core Hours, Availability and Response-Time Expectations

Flexibility without structure produces two failure modes at once: people who are always online and burning out, and people who are impossible to reach. A good remote work policy defines a shared spine of availability and leaves the rest genuinely flexible.

Define three availability tiers

Core hours. A window — commonly 11:00 to 17:00 IST — when everyone in a given team is expected to be reachable and available for meetings. Outside this window, employees manage their own schedule.

Flexible hours. The remaining working hours, which employees may arrange around their circumstances, subject to completing their contracted daily or weekly hours.

Quiet hours. A defined period — say after 20:00 and before 08:00, plus weekly offs — when no response is expected. Messages may be sent, but nobody is obliged to reply. This matters more than most employers realise: unbounded availability is the fastest route to remote burnout, and it disproportionately affects your most conscientious people.

Response-time expectations by channel

Ambiguity about response times is a leading cause of remote friction. Write it down.

Time zones and distributed teams

Even domestic Indian teams hit scheduling issues once you add clients in other regions or employees working night shifts for international accounts. Three rules keep it sane:

1. Publish everyone's working window in the HR system so schedulers can see it without asking.
2. Rotate the pain. If a recurring call is inconvenient for one group, alternate the timing rather than permanently disadvantaging the same people.
3. Record decisions, not just meetings. A written decision log means someone who could not attend is not excluded from the outcome.

---

Attendance and Time Capture for Hybrid Teams

This is where hybrid policies most often collapse in practice. Payroll needs data. Employees resent surveillance. Both concerns are legitimate, and the design choice you make here shapes how the policy feels more than any other clause.

The four common approaches

Self check-in / check-out via app or web. The employee marks start and end of day in the HRMS. Simple, respectful, and works everywhere. Relies on honesty, which is generally fine — but produces weak evidence if a dispute arises.

Geofencing. The app records a check-in only when the device is within a defined radius of an approved location. Useful for field staff and multi-site operations. For home-based work it means collecting home location data, which most employees find intrusive and which raises genuine privacy questions.

IP or network-based capture. Attendance is recorded when the employee connects to a company VPN, SSO or approved network. Low-friction and reasonably objective. Works well for knowledge roles. Does not capture time spent on offline work.

Honour system with output tracking. No clock at all. Presence is inferred from delivery, standups and calendar. Cleanest culturally, but leaves gaps for statutory records, leave accounting and any dispute about absence.

Trade-offs at a glance

A privacy-respectful default

Our recommended baseline for a hybrid Indian SMB:

• Office days: existing biometric or access-card capture continues.
• Remote days: self check-in and check-out through the HRMS app, with an optional device or network signal for corroboration.
• Field roles only: location capture, and only at the moment of check-in and check-out — not continuously through the day.
• No continuous location tracking, no screenshot capture, no keystroke logging, and no webcam monitoring for regular office roles.

State this stance in the policy in plain language. Telling employees what you will not do is as important as telling them what you will. It converts a control mechanism into a trust signal.

The regularisation loop

Whatever method you pick, build a correction path. Devices fail, networks drop, people forget. A workable loop:

1. Employee raises a regularisation request with a reason.
2. Manager approves or rejects within two working days.
3. Unapproved and unregularised absences flow to leave or loss of pay per policy.
4. HR runs an exception report monthly on employees with repeated regularisations — not to punish, but to identify whether a device, a location or a process is broken.

An HRMS such as CozyHR that combines geo-flexible check-in, approval workflows and direct linkage to leave and payroll removes the manual reconciliation that otherwise eats two days of every payroll cycle.

---

Measuring Output Instead of Hours

If your work from home policy is enforced primarily through attendance data, you have not built a hybrid model — you have built remote surveillance. The stated goal of most hybrid programmes is flexibility with accountability, and accountability has to come from output.

Why hours are a poor proxy

Hours logged tell you about presence, not contribution. In knowledge work they measure the least interesting variable. Worse, hour-based management rewards visible busyness, which is exactly the behaviour that makes remote employees anxious and performative — the person who replies to messages at 11 pm to prove they were working.

Hours still matter for statutory records, overtime calculation, leave accounting and shift-based or wage-board roles. Keep capturing them for those purposes. Just stop using them as the primary performance signal for roles where they are not the output.

Building an output framework

Step 1 — Define the deliverables. For each role, list three to six recurring outputs. A recruiter: qualified candidates presented, offer acceptance rate, time-to-fill. A support associate: tickets resolved, first-response time, CSAT. A developer: shipped scope against commitment, defect escape rate, review turnaround.

Step 2 — Set a cadence. Weekly commitments, monthly reviews, quarterly goals. The weekly loop is what makes remote work legible.

Step 3 — Make work visible by default. Tasks in a shared tool, decisions in writing, documents in shared drives. Visibility of work replaces visibility of person.

Step 4 — Standardise the check-in. A short written weekly update from every employee, remote or onsite: what I completed, what I am doing next, what is blocked, and where I need help. Fifteen minutes to write, and it makes hybrid management possible.

Step 5 — Review by evidence. In appraisals, require managers to cite delivered work, not impressions. "Always available" is not evidence. "Closed the migration two weeks early and documented the runbook" is.

Worked scenario 1: The two support associates

Anjali works from the Pune office five days a week. Rohit works from Nashik and comes in one day a month. Their manager rated Anjali higher last cycle, describing her as "more involved."

When HR asked for the underlying data, the picture changed. Over six months Rohit resolved 18 percent more tickets, with a marginally better resolution quality score. Anjali's advantage was in escalation handling — she picked up floor escalations because she was physically present when they happened.

The correct response was not to overturn the rating. It was to fix the structure: escalation duty was made a rotating assignment, routed through the ticketing system rather than by tapping whoever was nearby, and made available to remote staff. Two cycles later the gap had closed.

The lesson is that proximity bias usually hides inside a process, not inside a manager's prejudice. Fix the process and the bias mostly disappears.

---

Equipment, Internet and Home-Office Support

A home is not automatically a workplace. If you expect professional output, you have to fund a workable setup — and you have to be explicit about what the company provides, what it reimburses and what remains the employee's responsibility.

What to provide

Structuring the support

Three common structures, each with different administrative weight:

One-time setup allowance. A fixed amount paid once when an employee becomes remote-eligible, intended for desk, chair and peripherals. Simple. Consider a pro-rata recovery clause if the employee exits within a defined period.

Monthly connectivity allowance. A recurring amount for internet and electricity, paid through payroll. Predictable for both sides, minimal paperwork.

Actual-cost reimbursement. The employee submits bills and gets reimbursed up to a cap. More accurate, more administration, and it requires a clear list of eligible expenses.

Many companies run a hybrid of the three: company-owned computing hardware, a one-time setup allowance, and a monthly connectivity reimbursement against a declaration or bill.

On tax treatment — get advice

The tax treatment of allowances and reimbursements is genuinely fact-specific in India. Whether a payment is treated as a taxable allowance or a non-taxable reimbursement depends on how it is structured, what documentation is maintained, and the applicable rules and interpretations at the time. Company-owned assets used for work are treated differently from cash paid to an employee.

Do not design your allowance structure from a blog post — including this one. Decide what you want to give employees, then have your chartered accountant or payroll advisor confirm the correct treatment, documentation and payroll configuration before you roll it out. Getting this wrong creates a retrospective tax exposure that is unpleasant to unwind.

What you should do in the policy document is state clearly: which payments are allowances and which are reimbursements, what documentation is required, the applicable caps, the payment cycle, and that statutory deductions will be applied as required by law.

---

Data Security, Devices and Confidentiality

Remote work moves your data perimeter into hundreds of homes. Most SMB breaches are not sophisticated attacks — they are a shared home laptop, a personal email forward, or a device left in a cab.

The device policy decision

Company-provided devices are the cleaner option: you control the build, encryption, patching and remote wipe, and you can enforce policy technically rather than by request. Higher upfront cost, dramatically lower risk.

BYOD is cheaper but requires a written agreement covering acceptable use, mandatory security software, the company's right to wipe corporate data, and the employee's privacy expectations regarding personal data on the same device. If you allow BYOD, restrict it to lower-sensitivity roles.

Minimum security requirements to write into policy

• Full-disk encryption enabled on any device used for company work.
• Screen lock with a maximum idle timeout.
• Company VPN required for access to internal systems.
• Multi-factor authentication on email, HRMS, finance systems and code repositories.
• No storage of company data on personal cloud accounts or personal email.
• Approved password manager; no shared credentials.
• Prompt reporting of lost or stolen devices, with a defined reporting channel and time limit.
• Prohibition on allowing family members or others to use the work device.
• A clean-desk equivalent for home: confidential documents not left visible, video calls not taken in shared public spaces when sensitive matters are discussed.

Confidentiality in a home setting

Add clauses that address the specific realities of home working:

• Use headphones for calls involving personal data, customer information or commercially sensitive discussion.
• Do not photograph or screen-record internal systems containing personal data.
• Avoid working on confidential material in cafés, co-working lounges or airports without a privacy screen.
• Where a household includes someone employed by a competitor or a customer, disclose it so a sensible arrangement can be agreed.

Offboarding remote employees

Build a checklist and enforce it. Device return logistics (courier pickup and insured transit), access revocation on the last working day, mailbox handling, recovery of company data from personal storage, and a signed confirmation that no company property or data remains. Handling this loosely is how organisations lose customer lists.

---

India Compliance Angles for Remote and Hybrid Teams

This section is general orientation, not legal advice. Employment obligations in India sit across central legislation, state-level rules and, in several areas, notifications that change. Every point below should be verified with your legal or compliance advisor against current rules for your states and your headcount.

Registered place of work and Shops and Establishments

Most non-factory Indian employers register their establishment under the applicable state Shops and Establishments legislation. The registration attaches to premises. A settled hybrid model raises practical questions:

• Which establishment is each employee attached to for record-keeping?
• If you have opened, closed or shrunk offices, are your registrations current?
• If a large share of your workforce now sits in a state where you have no registered premises, what does that imply for your obligations there?

There is no single national answer; state rules differ in how they treat remote and home-based work. Some states have moved to accommodate work-from-home arrangements more explicitly than others. The practical step is to maintain a clear register of where every employee actually works and to review it with an advisor at least annually.

Professional tax and other state-linked obligations

Professional tax is levied by states, with different rates, slabs, registration requirements and filing calendars. Some states do not levy it at all. When an employee lives and works in a different state from your registered office, the questions become:

• Which state's professional tax applies, and does the company need registration there?
• Are labour welfare fund contributions applicable in that state?
• Do state-specific leave entitlements or holiday requirements differ from your policy?

Under-deducting or mis-allocating professional tax across states is one of the more common payroll errors in distributed Indian companies. It is usually easy to fix prospectively and awkward to fix retrospectively. A payroll system that supports state-wise professional tax configuration by employee work location removes most of the manual risk.

Provident fund, ESI and other statutory contributions

Contribution obligations generally follow the employment relationship rather than the physical work location, but coverage thresholds, applicability and reporting can be affected by establishment registration and by where employees are located. Where you have employees in a new state or a new establishment, confirm applicability rather than assuming continuity.

POSH obligations extend to remote work

This is the compliance point most often missed. The law on prevention of sexual harassment at the workplace in India defines the workplace broadly, and the widely accepted position is that it extends to virtual and remote working environments — video calls, chat platforms, email, and work-related interactions outside physical premises.

Practically, this means:

• Your Internal Committee must remain properly constituted, including the external member, regardless of whether anyone comes to an office.
• Employees must be able to file complaints remotely, through a channel that does not require walking into an office.
• Inquiry proceedings may need to be conducted over video; document the process and safeguards for confidentiality and fairness.
• Awareness training must reach remote employees, and should explicitly address conduct on chat and video platforms.
• Annual reporting obligations continue.

Treat "we are a remote company" as a reason to strengthen POSH infrastructure, not to relax it.

Working hours, overtime and rest

State Shops and Establishments rules typically specify maximum daily and weekly hours, spread-over limits, intervals for rest, weekly off entitlement and overtime treatment. These do not evaporate because the work happens at home.

For hybrid employers this creates two practical duties:

1. Keep hour records for roles where statutory hour limits and overtime apply. "We don't track hours, we track output" is a defensible management philosophy and a weak compliance position for covered roles.
2. Discourage habitual overwork. If your systems show an employee routinely logging twelve-hour days, that is both a wellbeing signal and a potential compliance question.

Duty of care, insurance and safety

Employers retain a general duty of care toward employees performing work. In a home setting, this is usually discharged through reasonable steps rather than inspection:

• Provide guidance on safe home-workstation setup — screen height, chair support, lighting, breaks.
• Ask remote employees to confirm that their workspace is reasonably safe and free of obvious hazards.
• Review your group medical and personal accident insurance wording to understand how remote work and travel to office are treated.
• Have a clear process for reporting a work-related injury or incident that occurs while working from home.
• Include mental health support, employee assistance access or counselling in your benefits if you can — isolation is a real cost of remote work.

Contracts and policy documents

Your employment contracts, appointment letters and employee handbook should be consistent with how you actually operate. Three specific points to review with your advisor:

• Place of work clause. Does it name a fixed location, permit remote work, and reserve the right to require attendance at a designated workplace?
• Change of location. Is there a process for an employee to request relocation, and for the company to require attendance where the role needs it?
• Policy variation. Does the handbook state that policies may be amended with reasonable notice, and is a change-notification process actually followed?

Ambiguity here is what makes return-to-office changes legally messy and reputationally expensive.

---

Performance, Promotion and Proximity Bias

Proximity bias is the tendency to rate, trust and promote the people you physically see more often. It is rarely deliberate. It is a by-product of how human attention works, and it is the reason hybrid models quietly fail even when the policy document is excellent.

If remote employees come to believe that career progression requires being in the office, your work from home policy is decorative. People will commute to protect their careers, resent it, and eventually leave for a company that does not make them choose.

Where proximity bias actually enters

• Informal information flow. Decisions made in corridors and over lunch, communicated to the room and never written down.
• Opportunity allocation. The interesting project goes to whoever the manager saw that morning.
• Recency in reviews. Managers recall recent visible interactions more vividly than six months of remote delivery.
• Sponsorship. Senior leaders advocate for people they have spent unstructured time with.
• Escalation and crisis roles. As in the earlier scenario, the person nearby gets pulled in — and crisis work is disproportionately career-visible.

Structural countermeasures

Write down decisions. Any decision affecting more than one person goes into a channel or document within the same working day. This single habit does more for remote equity than any training programme.

Rotate high-visibility work. Maintain a list of the assignments that build reputations — client presentations, incident leadership, new-hire mentoring, cross-functional projects — and rotate them explicitly across the team, including remote members.

Require evidence in appraisals. Build the rating form so managers must attach specific delivered outcomes. Ban presence-based language.

Audit outcomes by work location. Once a year, compare average performance ratings, promotion rates, increment percentages and attrition between predominantly-remote and predominantly-onsite employees. If a gap exists, investigate the mechanism. A modern HRMS makes this a report rather than a project.

Give remote employees senior exposure deliberately. Structured skip-level conversations, rotating presentation slots in leadership reviews, and named mentors. Do not rely on it happening organically, because it will not.

Train managers on distributed management specifically. Managing people you cannot see is a distinct skill: writing clearly, running structured one-on-ones, giving feedback over video, and noticing disengagement without body language cues. Most managers were never taught it.

---

Running Hybrid Meetings Without Excluding Anyone

The worst meeting format ever invented is six people in a conference room with one laptop, and three people dialling in. The remote participants cannot hear the side comments, cannot read the room, cannot interject, and eventually stop trying.

Rules that fix hybrid meetings

1. One person, one screen. If anyone is remote, everyone joins from their own device with their own camera and microphone — even the people sitting in the same room. It feels absurd for the first week. It equalises participation permanently.
2. Written agenda circulated in advance. No agenda, no meeting.
3. A named facilitator. Their job includes actively pulling in remote voices: "Priya, you had a view on this."
4. Chat is a first-class channel. Questions raised in chat get read aloud and answered.
5. Decisions and actions written up within the day, in a place everyone can find.
6. Recordings for anything informational, so people in other time zones or on leave are not disadvantaged.
7. Default to shorter. Twenty-five and fifty minutes instead of thirty and sixty, so people can move between calls and take a break.

Reduce the meeting load itself

Hybrid teams often over-correct by adding meetings to compensate for lost hallway contact. Resist it. Replace status meetings with written updates. Reserve synchronous time for genuine discussion, decision-making, relationship-building and conflict resolution — the things that actually need real-time bandwidth.

---

Onboarding Remotely: The First 30 Days

Remote onboarding is where hybrid companies most reliably underperform. A new joiner who spends their first month confused, under-connected and unsure whether they are doing well will either leave within six months or settle into permanent underperformance.

The 30-day plan

Before day one - Laptop, peripherals and access credentials delivered and tested at the employee's location, ideally three days before joining. - Offer letter, policies, ID proofs and bank details collected digitally in advance. - Calendar invites for the first week already sent. - A named buddy assigned and introduced by email.

Days 1 to 5 — orientation and access - Live video welcome with HR covering policies, leave, attendance, security and the hybrid model itself. - Manager one-on-one on day one defining the role, first-30-day expectations and how success will be judged. - Introductions to five to eight people the person will work with, scheduled as short individual calls rather than one large meeting. - One small, completable task by day three. Early completion builds confidence more than any welcome kit. - Where feasible, at least one in-person day or a team lunch in the first week.

Days 6 to 15 — context and first contribution - Deep-dive sessions on product, customers, systems and internal processes. - Shadowing: sitting in on customer calls, support queues or code reviews. - First real deliverable assigned with a clear definition of done. - Buddy check-in twice a week, informal and low-stakes.

Days 16 to 30 — independence and feedback - Owning a defined piece of work end to end. - A structured 30-day feedback conversation, both directions: how the joiner is doing, and what the onboarding got wrong. - Confirmation of goals for the remainder of probation. - HR pulse check separate from the manager, so problems with the manager surface early.

Worked scenario 2: The disappearing new joiner

A 60-person analytics firm hired a data engineer based in Coimbatore, fully remote. The laptop arrived on day four. VPN access took nine days. He attended standups where he understood nothing and asked no questions. His manager, busy with a client deadline, met him twice in three weeks.

At the 30-day mark, HR ran a pulse check and found a person who had written almost no code, had spoken to three colleagues, and had already started interviewing elsewhere.

The recovery was mechanical, not heroic. A named buddy for daily 15-minute calls for two weeks. A small, well-scoped ticket with an explicit definition of done. Two customer calls to listen in on. A written 60-day expectation document. Two travel-funded office days in week six.

He stayed, and became a strong performer. But the company also fixed the system: hardware and access provisioning became a pre-joining checklist with a hard deadline, every remote joiner got an assigned buddy, and the 30-day HR pulse check became mandatory rather than occasional. That is the real lesson — the individual rescue matters less than closing the process gap that created the problem.

---

Leave, Comp-Off and Holidays in a Hybrid Setup

Hybrid changes how leave behaves, and most companies do not update their leave policy to match.

The "working from home instead of taking leave" problem

The most common leave distortion in hybrid companies: an employee has a family situation, a plumber visit or a mild illness, and instead of applying for leave they work from home at 40 percent capacity. Everyone pretends this is fine.

It is not fine for either side. The employee burns goodwill and gets no rest. The company gets unreliable output and loses visibility into actual availability.

Fix it with clarity:

• Work from home means working. Same availability, same output expectations, same core hours.
• If you cannot work, apply for leave. Sick leave exists for sickness. Casual leave exists for personal matters.
• Short-notice remote days are not leave. Define how they are requested and approved so people do not feel forced into deception.
• Half-day options for genuinely partial availability, rather than forcing an all-or-nothing choice.

Holidays across states

Distributed teams cross state boundaries, and public holidays differ by state. Two workable approaches:

Fixed national list plus optional/floating holidays. Publish a common list of national holidays, then give every employee a set number of floating holidays to use for regional festivals relevant to them. Simple and inclusive.

Location-based holiday calendars. Each employee is mapped to a state calendar. More faithful to local norms, more administrative overhead, and it means teams have different working days.

Whichever you choose, publish the calendar at the start of the year and make each employee's holiday list visible in the HRMS so schedulers can see it.

Comp-off in a hybrid model

Compensatory off is where hybrid gets murky. If someone answers a customer escalation for three hours on a Sunday from home, does that earn comp-off?

Write the rule explicitly:

• Comp-off accrues only for pre-approved work on a weekly off or holiday, above a defined minimum duration.
• Approval must be recorded before the work happens, except for genuine emergencies which are regularised within two working days.
• Comp-off has an expiry — commonly 30, 60 or 90 days — and the policy should state whether it lapses or converts.
• Ad hoc after-hours messaging on a normal working day does not earn comp-off. If it is happening regularly, that is a workload problem, not a comp-off problem.

Without this clause, comp-off claims in remote teams become a source of constant, unwinnable argument.

---

Return to Office: Changing the Deal Without Breaking Trust

At some point many companies decide they need more in-office presence. Sometimes the reasoning is good: onboarding is failing, collaboration has thinned, a client requires it, the culture feels transactional. Sometimes it is weaker: an expensive lease, or a senior leader who feels better when the floor looks full.

Either way, a return to office policy is a change to something people have organised their lives around — school runs, elder care, relocations, second incomes. Handle it as a serious change management exercise, not an announcement.

Both sides are reasonable

The employer's case: informal knowledge transfer is genuinely faster in person; junior employees learn by observation; some cultures do thin out when nobody meets; certain client and regulated work needs controlled premises; and coordination costs are real.

The employee's case: commutes in Indian metros routinely consume two to three hours a day and real money; households have restructured around flexibility; caregiving arrangements are fragile; and for many roles, the output evidence genuinely does not support a presence requirement.

Both are true. A policy that acknowledges only one side will be rejected by the other.

How to do RTO well: eight steps

1. Be specific about the problem. "More collaboration" is not a reason. "New joiners are taking five months to reach productivity versus two months previously" is. State the problem, the evidence you have, and what you expect the change to fix.

2. Consult before deciding. Run a short survey and small group conversations. Ask about constraints, not preferences: commute time, caregiving, current arrangements, what would make office days useful. This is not a referendum — you are gathering the information that determines whether your plan is workable.

3. Give real notice. A minimum of 60 days, preferably 90, for anything that changes someone's routine. People need to rearrange childcare, transport and in some cases housing.

4. Phase it. Move from one day to two to three across quarters rather than jumping. Phasing lets you observe whether the intended benefit actually materialises.

5. Make the office days worth the commute. Nothing destroys an RTO faster than commuting ninety minutes to sit on video calls alone. Coordinate anchor days by team, schedule collaborative work on those days, ensure enough desks and meeting rooms, and make sure managers are actually present.

6. Publish an exceptions process before the mandate. Medical, accessibility, caregiving, distance and role-based exceptions, with a named decision-maker who is not the line manager, a defined response time, and an appeal route. Exceptions decided quietly and inconsistently do more damage than the mandate itself.

7. Protect people who were hired remote. Someone recruited explicitly as a remote employee, who moved cities on that basis, is in a different position from someone who drifted into remote work. Grandfather them, or negotiate individually with genuine options — including relocation support if you want them in the office.

8. Measure and report back. Publish what you observe after two quarters: attendance patterns, attrition, engagement, and whether the original problem improved. If it did not, say so and adjust. Willingness to revise is what makes people believe the reasoning was honest.

RTO approaches compared

---

Monitoring and Surveillance: What Is Proportionate

Remote work creates an anxiety in some managers that gets expressed as monitoring software. It is worth being blunt: heavy surveillance of knowledge workers is usually a symptom of unclear expectations, not a cure for low output.

A proportionality test

Before deploying any monitoring, answer four questions in writing:

1. What specific risk or problem does this address? Not "we want to know people are working" — an actual, evidenced problem.
2. Is there a less intrusive way to address it? Usually there is: clearer deliverables, a weekly check-in, better task tracking.
3. Is the data collection proportionate to the risk? Continuous screenshots to solve a suspicion about one employee is not proportionate.
4. Would you be comfortable explaining this to the whole company in a town hall? If not, do not do it.

Generally proportionate

• Attendance check-in and check-out records.
• Access logs to company systems, retained for security purposes.
• Task and project tracking in shared tools.
• Aggregate, anonymised usage analytics for capacity planning.
• Location capture at check-in only, for genuinely field-based roles.
• Call recording for customer-facing roles, with disclosure to all parties and a defined retention period.

Generally disproportionate for regular office roles

• Continuous screenshot capture.
• Keystroke logging.
• Webcam monitoring or random photo capture.
• Continuous GPS tracking through the working day.
• Reading personal messages on personal devices.
• Idle-time detection used as a performance metric.

If you monitor, disclose

Whatever you deploy, tell employees clearly: what is collected, why, who can see it, how long it is retained, and how it is used in decisions. Put it in the policy and in the onboarding pack. Covert monitoring that later surfaces causes damage far out of proportion to any benefit it delivered — and India's evolving data protection framework makes transparency and purpose limitation increasingly important. Have your advisor review your monitoring practices against current data protection requirements.

---

Hybrid Work Policy Template (Ready to Adapt)

Below is a structured template you can adapt to your organisation. Replace the bracketed placeholders, delete what does not apply, and have your legal and payroll advisors review the final version before it is issued.

---

HYBRID AND WORK FROM HOME POLICY — [COMPANY NAME]

Effective date: [DD Month YYYY] Applies to: All permanent employees of [Company Name] in India, unless stated otherwise Policy owner: [Head of HR / People Operations] Review cycle: Annually, or earlier if business needs change

1. Purpose

1.1 This policy sets out how [Company Name] operates hybrid and remote working. It defines eligibility, working hours, attendance, equipment, security, conduct and performance expectations for employees who work from a location other than a Company office.

1.2 The Company is committed to flexibility that is fair, consistent and consistent with our obligations to customers and under applicable law.

2. Scope and definitions

2.1 Company office means any premises owned or leased by the Company and notified as a place of work.

2.2 Remote working means performing contracted duties from a location other than a Company office, including the employee's registered home address.

2.3 Hybrid working means a pattern combining Company office attendance with remote working.

2.4 Designated remote location means the address recorded by the employee in the HR system as their usual remote working location.

2.5 This policy applies to permanent employees. Interns, contractors and consultants are covered by their engagement terms.

3. Working model

3.1 The Company operates a [anchor-day hybrid / remote-first / office-first with flex] model.

3.2 Employees in hybrid-eligible roles are expected to attend a Company office on [number] day(s) per week, on [days], unless an alternative is approved.

3.3 Anchor days may be varied by a team head with [two weeks'] notice to accommodate project needs, subject to HR notification.

3.4 The Company may require attendance at a Company office for specific business needs, including client visits, training, audits, performance discussions, disciplinary or inquiry proceedings, and team events, with reasonable notice.

4. Eligibility

4.1 Remote eligibility attaches to roles, not individuals. Each role is classified as Remote-eligible, Hybrid-eligible, Limited flex or Onsite-required, using the Company's published role classification framework.

4.2 The classification list is maintained by HR and published on [system/intranet]. It is reviewed [annually] and when a role's requirements materially change.

4.3 Employees in their first [60/90] days of employment may be required to work primarily from a Company office regardless of role classification, to support onboarding.

4.4 Employees under an active performance improvement plan may be required to work from a Company office for the duration of the plan.

4.5 Requests for arrangements outside the standard classification — including for medical, accessibility or caregiving reasons — are made to HR under clause 15.

5. Working hours and availability

5.1 Standard working hours are [X] hours per day, [Y] days per week, in line with applicable law and the employee's contract.

5.2 Core hours, during which all employees are expected to be available, are [11:00 to 17:00 IST].

5.3 Outside core hours, employees may arrange their schedule flexibly, subject to completing contracted hours and meeting business commitments.

5.4 Quiet hours are [20:00 to 08:00 IST] and weekly offs. Employees are not expected to respond during quiet hours except where they are on a notified on-call rota.

5.5 Employees must record their working schedule in the HR system and update it if it changes.

5.6 Response-time expectations by communication channel are set out in Annexure A.

6. Attendance and time records

6.1 Employees working from a Company office record attendance through [biometric / access card / mobile check-in].

6.2 Employees working remotely record check-in and check-out through the Company HR system on each working day.

6.3 Attendance records are used for payroll processing, leave accounting and statutory record-keeping.

6.4 Where a check-in is missed, the employee must raise a regularisation request within [two] working days, stating the reason. The reporting manager will approve or reject within [two] working days.

6.5 Unapproved absence without leave application will be treated in accordance with the Leave Policy and may result in loss of pay.

6.6 Location data is captured only at the point of check-in and check-out and only for roles designated as field-based. The Company does not carry out continuous location tracking, screenshot capture, keystroke logging or webcam monitoring of employees.

7. Change of remote location

7.1 Employees must maintain a current designated remote location in the HR system.

7.2 Employees intending to relocate to a different city or state must inform HR at least [30] days in advance and obtain written confirmation before relocating.

7.3 Relocation may affect statutory deductions, applicable holidays, insurance arrangements and role classification. The Company will confirm any changes in writing.

7.4 Working from outside India requires prior written approval from [designated authority] and may not be permitted for all roles.

8. Equipment and Company property

8.1 The Company will provide a laptop and [list of peripherals] to employees in remote-eligible and hybrid-eligible roles.

8.2 Company equipment remains Company property, is recorded in the asset register, must be used primarily for Company work, and must be returned on the last working day or as instructed.

8.3 Employees must take reasonable care of Company equipment and report loss, theft or damage to [IT helpdesk] within [24] hours.

8.4 Company equipment must not be used by family members or any third party.

9. Allowances and reimbursements

9.1 Eligible employees may receive a one-time home-office setup allowance of [amount], subject to the conditions in Annexure B.

9.2 A monthly connectivity allowance/reimbursement of [amount] is payable to employees in [eligible categories], processed through payroll.

9.3 All payments under this clause are subject to applicable statutory deductions and to the documentation requirements set out in Annexure B.

9.4 Where an employee resigns or is separated within [12] months of receiving a setup allowance, the Company may recover a pro-rated amount from final settlement, subject to applicable law.

10. Information security and confidentiality

10.1 Employees must comply with the Company Information Security Policy at all times, regardless of work location.

10.2 Minimum requirements include device encryption, screen lock, multi-factor authentication, use of the Company VPN for internal systems, and use of the approved password manager.

10.3 Company data must not be stored on personal cloud accounts, personal email or personal removable media.

10.4 Employees must not discuss confidential matters in public spaces, and must use headphones for calls involving personal or confidential information.

10.5 Suspected security incidents, including lost devices and phishing attempts, must be reported to [security contact] immediately.

11. Health, safety and wellbeing

11.1 Employees are responsible for ensuring their designated remote location is reasonably safe and suitable for work.

11.2 The Company will provide guidance on ergonomic workstation setup and encourages regular breaks.

11.3 Any injury or incident occurring while performing work duties must be reported to HR within [24] hours.

11.4 Employees have access to [medical insurance / employee assistance / counselling support] as described in the Benefits Policy.

12. Conduct, POSH and grievance

12.1 All Company policies on conduct, anti-harassment and code of ethics apply equally to remote work and to virtual interactions including video calls, chat platforms and email.

12.2 The Company's Policy on Prevention of Sexual Harassment applies to the virtual workplace. Complaints may be raised with the Internal Committee through [email address / portal] from any location.

12.3 Grievances relating to this policy may be raised with [HR contact] and will be responded to within [10] working days.

13. Performance management

13.1 Performance is assessed on delivered outcomes against agreed goals, not on physical presence.

13.2 Employees are required to submit a weekly written update in [tool] covering completed work, planned work and blockers.

13.3 Managers must conduct documented one-on-ones at least [fortnightly] with each direct report, irrespective of work location.

13.4 The Company will review performance ratings, promotions and increments annually for any disparity linked to work location, and will act on findings.

14. Leave and holidays

14.1 Remote working is not a substitute for leave. Employees who are unable to work must apply for the applicable leave type.

14.2 The Company publishes an annual holiday calendar comprising [fixed holidays] and [number] floating holidays.

14.3 Compensatory off is granted only for pre-approved work performed on a weekly off or public holiday exceeding [4] hours, and must be availed within [60] days.

15. Exceptions

15.1 Employees may apply for an exception to this policy on medical, accessibility, caregiving or other substantial personal grounds.

15.2 Applications are made to HR in writing, with supporting documentation where relevant.

15.3 Decisions are made by [HR Head, in consultation with the function head] within [10] working days, and are communicated in writing with a review date.

15.4 An employee may request a review of a decision by [named escalation authority] within [10] working days.

16. Changes to this policy

16.1 The Company may amend this policy. Material changes affecting an employee's regular working pattern will be communicated with at least [60] days' notice, save where a shorter period is required by law, regulation or client contract.

16.2 The Company will consult employee representatives or run a feedback process before implementing material changes wherever practicable.

Annexure A — Response-time expectations by channel Annexure B — Allowance eligibility, caps and documentation Annexure C — Role classification list Annexure D — Home workstation safety checklist

---

Metrics to Track for a Hybrid Work Policy

Without measurement, hybrid policy discussions become a contest of anecdotes. Track a small, honest set of indicators and review them quarterly.

Review these with leadership quarterly, and publish a summary to employees. Transparency about the numbers is what makes the policy feel like a system rather than a set of rules imposed from above.

---

Common Mistakes in Hybrid and Work From Home Policies

Copying a policy from a global company. A policy written for a US or European employer will not address Shops and Establishments registration, professional tax across states, POSH obligations or Indian leave conventions. Use structure from anywhere; write the substance for India.

Leaving eligibility to manager discretion. The fastest route to perceived favouritism. Classify roles, publish the classification, and run exceptions through HR.

Tracking hours but managing on vibes. Collecting attendance data while making performance decisions on impressions gives you the administrative cost of measurement with none of the benefit.

Treating work from home as informal leave. If someone cannot work, they should take leave. Blurring this corrupts both attendance data and workload planning.

Never writing the policy down at all. The most common mistake of all. If it is not documented, it is not a policy — it is a set of individual arrangements that will eventually conflict.

Announcing RTO without consultation or notice. A change that affects childcare, commuting and household budgets deserves more than a Friday email.

Deploying surveillance software instead of clarifying expectations. Monitoring rarely fixes a performance problem, and it reliably damages the trust of the people who were performing well.

Forgetting POSH applies to virtual workplaces. Internal Committee composition, remote complaint channels, virtual inquiry procedures and remote training all need to work.

Ignoring the state dimension. Employees living in states where you have no registration or presence create real questions about professional tax, holidays, and applicable rules. Review it before someone else does.

Underinvesting in remote onboarding. The joiner who was never properly inducted becomes an attrition statistic six months later, and the cost lands in recruitment rather than in the onboarding budget where it belongs.

No exception process. Every objective rule needs a documented, consistent way to handle the cases it did not anticipate.

Not reviewing the policy. Business needs change, offices move, the workforce redistributes. An annual review keeps the policy connected to reality.

Making office days pointless. If people commute to sit on video calls at an empty desk, they will stop coming and they will be right to.

Assuming everyone has a workable home setup. Not every employee has a quiet room, reliable power or good broadband. Ask, and fund the gap where you can.

---

A 60-Day Rollout Plan

If you are formalising your hybrid arrangement for the first time, or replacing an informal one, here is a workable sequence.

Days 1 to 10 — Assess

1. Map the current reality: who works where today, how often, and under what informal agreement.
2. Pull existing data: attendance records, leave patterns, attrition by work pattern, engagement scores.
3. Run a short employee survey on constraints — commute time, home setup quality, caregiving responsibilities, current arrangement.
4. Interview six to ten managers about what is and is not working.
5. Identify the compliance surface: which states employees live in, current registrations, professional tax position, contract clauses.

Days 11 to 20 — Decide

1. Leadership workshop to choose the working model and articulate the reasoning in one paragraph.
2. Run the role classification exercise across every job in the company.
3. Decide the attendance and time capture approach, and the explicit monitoring boundaries.
4. Decide the equipment, allowance and reimbursement structure at a high level.
5. Brief your legal, payroll and tax advisors on the intended design and get their input before drafting.

Days 21 to 35 — Draft

1. Draft the policy using the template above, adapted to your decisions.
2. Draft supporting annexures: response-time expectations, allowance rules, role classification list, home safety checklist.
3. Review the draft with legal and payroll advisors.
4. Test the draft with a small cross-functional group — a sceptical manager, a fully remote employee, a junior joiner, someone with caregiving responsibilities. Their objections are free quality assurance.
5. Revise.

Days 36 to 45 — Configure

1. Configure the HRMS: work locations, shift and core-hour definitions, remote check-in, regularisation workflows, approval chains.
2. Configure payroll for allowances, reimbursements and state-wise statutory deductions where applicable.
3. Set up the reporting you will need for the metrics table.
4. Update the employee handbook, offer letter templates and appointment letter clauses.
5. Prepare the manager toolkit: FAQ, talking points, escalation routes.

Days 46 to 55 — Communicate

1. Brief managers first, in a live session, at least a week before the general announcement.
2. Publish the policy with a plain-language summary and a clear effective date.
3. Hold an all-hands with genuine question time — including the uncomfortable questions.
4. Open a dedicated channel for policy questions and answer publicly so everyone sees the same answers.
5. Open the exception process and commit to a response time.

Days 56 to 60 — Launch and stabilise

1. Go live with the new attendance and approval flows.
2. Run daily checks in the first week on check-in completion and regularisation volumes.
3. Fix friction fast — a broken check-in flow in week one poisons the whole rollout.
4. Schedule the 30-day and 90-day reviews now, with named owners.
5. Publish the first metrics summary at 90 days, including what is not working.

---

Frequently Asked Questions

Do we legally need a written work from home policy in India?

There is no single provision that says "you must have a work from home policy document." However, several obligations become much harder to meet without one: maintaining attendance and hour records, applying leave rules consistently, demonstrating fair treatment, and evidencing that employees were informed of security and conduct expectations. A written policy is also your primary defence when an arrangement is disputed. Treat it as practically necessary even where it is not explicitly mandated, and have your advisor confirm what your state's rules require for record-keeping.

Can an employer require employees to return to the office?

Generally, an employer can determine where work is performed, subject to the employment contract, any specific commitments made to the individual, and applicable law. The practical risk is rarely legal — it is retention and reputation. Where an employee was hired explicitly as remote, or where the contract names a remote location, the position is weaker and the change should be negotiated rather than mandated. Review your contract wording and any written commitments with your advisor before issuing a return to office mandate.

How should we track attendance for hybrid employees without being intrusive?

The workable default is self check-in and check-out through an HRMS app on remote days, combined with existing biometric or card capture on office days, plus a documented regularisation route for missed punches. Reserve location capture for genuinely field-based roles, and only at check-in and check-out. Avoid continuous tracking, screenshots and keystroke logging for regular office roles — they generate resentment far out of proportion to the assurance they provide, and they do not solve performance problems.

What happens if a remote employee lives in a different state from our office?

It can affect several things: which state's professional tax applies and whether you need registration there, labour welfare fund applicability, applicable public holidays, and how your Shops and Establishments registration relates to that employee. There is no single national answer because these are state-level matters. Maintain an accurate register of where every employee actually works, and review the position with your payroll and legal advisors at least annually and whenever someone relocates.

Are internet and home-office allowances taxable for employees in India?

The treatment depends on how the payment is structured, what documentation is maintained, and the applicable rules at the time. Company-owned equipment provided for work is treated differently from cash paid to an employee, and a reimbursement against bills is treated differently from a fixed allowance. This is genuinely fact-specific, so decide what you want to provide and then have your chartered accountant or payroll advisor confirm the correct treatment and payroll configuration before rollout.

Does POSH apply to remote employees and virtual meetings?

The prevailing position is that workplace obligations under India's sexual harassment law extend to the virtual workplace, including video calls, chat platforms, email and other work-related interactions outside physical premises. Practically this means keeping your Internal Committee properly constituted including the external member, providing a remote complaint channel, being able to conduct inquiries over video with appropriate safeguards, delivering awareness training to remote employees, and continuing annual reporting. Confirm the current requirements with your legal advisor.

How do we stop remote employees being passed over for promotion?

Attack it structurally rather than through good intentions. Write decisions down so information does not live only in the office. Rotate high-visibility assignments explicitly. Require evidence of delivered outcomes in appraisal forms and ban presence-based language. Give remote employees deliberate senior exposure through skip-levels and presentation slots. Then audit annually: compare ratings, promotions, increments and attrition between predominantly-remote and predominantly-onsite employees, and investigate any gap you find.

---

Bringing It Together

A hybrid model is not a compromise between office and remote work. It is a distinct operating model with its own requirements: explicit eligibility rules, defined availability windows, attendance capture that people accept, performance management based on output, deliberate equity mechanisms, and a compliance posture that accounts for employees living across multiple states.

The companies that make hybrid work well in India are not the ones with the most permissive policy or the strictest mandate. They are the ones that wrote it down, applied it consistently, measured what happened, and adjusted when the evidence said they should.

Start with the two decisions that determine everything else: which model you are actually running, and how role eligibility will be determined. Everything in this guide follows from those. Write the policy, get it reviewed by your legal and payroll advisors, configure your systems to match, and communicate it properly — with real notice and a real exception process.

If your current constraint is operational rather than editorial — attendance that does not reconcile, leave that lives in a spreadsheet, allowances that have to be keyed in manually each month, or no way to see who worked where — that is a solvable problem. CozyHR brings attendance, leave, allowances, reimbursements and payroll into one system built for Indian SMBs, with flexible check-in for hybrid and remote teams, approval workflows for regularisation and exceptions, and state-aware payroll configuration.

Take a look at CozyHR and see whether it makes your hybrid model easier to run than it is today.