Hybrid Work Policy for Indian SMBs: Rules & Template (2026)

If your team works from the office some days and from home on others, you already run a hybrid workplace — whether or not anyone has written it down. A hybrid work policy turns that informal arrangement into a clear, fair, enforceable set of rules: who can work remotely, on which days, how attendance is captured, what the company pays for, and how performance is judged. For Indian SMBs and startups in 2026, this document has quietly become as essential as the leave policy. Without it, you get scheduling chaos, payroll disputes, resentment between "office people" and "home people," and managers improvising rules on WhatsApp at 9 p.m.

This guide walks you through designing a hybrid work policy from scratch — the models, the eligibility rules, attendance handling, presence equity, legal notes for India, a rollout plan, and a complete copy-adaptable template you can put in front of your leadership team this week.

What Is a Hybrid Work Policy — and Why SMBs Need One

A hybrid work policy is a formal HR document that defines how employees split their working time between company premises and remote locations (usually home), and the rules that govern both modes. It typically covers:

• Which roles and employees are eligible for hybrid work
• The hybrid work model the company follows (fixed days, flexible, remote-first, or office-first)
• How working hours and attendance are recorded on remote days
• Communication expectations, availability windows, and meeting norms
• Equipment, internet, and expense reimbursement rules
• Data security and confidentiality obligations outside the office
• How performance is measured when managers can't see everyone daily
• What happens when the policy is violated

Why an unwritten arrangement eventually breaks

Plenty of Indian SMBs drifted into hybrid work after 2020 and never formalised it. That works fine at 15 people. It stops working somewhere between 30 and 80 employees, for predictable reasons:

• Payroll disputes. An employee works from home on a day the biometric device obviously never saw them. Is that present, absent, or leave? If your attendance system and your policy disagree, payroll becomes a monthly argument.
• Manager inconsistency. One team lead allows three remote days, another allows none. Employees compare notes, and HR inherits the fallout.
• Hiring promises vs. reality. Recruiters say "we're flexible" to close candidates; the joining manager expects five days in office. New hires feel misled and leave early.
• Client and audit questions. Enterprise clients, especially in IT services and finance, increasingly ask vendors how remote access, confidentiality, and attendance are governed. "We manage it informally" is not an acceptable answer in a vendor security questionnaire.
• Legal exposure. Working hours, overtime, and attendance records are regulated under state Shops and Establishments legislation. If you can't show consistent records, you're carrying avoidable risk.

Hybrid work policy vs. remote work policy vs. work from home policy

These terms overlap, and Indian HR teams use them loosely, but it helps to be precise in your documentation:

• A work from home policy traditionally covered occasional, exception-based WFH — a plumber visit, a sick child, a monsoon flood day. It assumes office is the default.
• A remote work policy (in India, often written for fully distributed roles) covers employees who rarely or never come to an office, including those in cities where you have no premises.
• A hybrid work policy assumes a structured split — employees regularly work from both locations under defined rules.

For most Indian SMBs, one well-structured hybrid work policy can absorb all three cases: it defines the standard hybrid pattern, carves out fully-remote exceptions, and retains an ad-hoc WFH clause for emergencies. That's the approach the template later in this article takes.

Choosing Your Hybrid Work Model

Before writing a single clause, decide which hybrid work model your company actually runs. Everything else — attendance logic, desk planning, meeting norms — flows from this choice.

The four common hybrid work models

How to choose, practically

Ask four questions:

1. What work genuinely requires co-location? Whiteboard-heavy product design, hardware testing, client walk-ins, cash handling, and physical inventory need presence. Code reviews, report writing, and payroll processing mostly don't.
2. Where does your talent live? If half your engineers commute 90+ minutes across Bengaluru or Gurugram, a 5-day office mandate is a silent attrition programme. If everyone lives within 5 km, generous office time is cheap.
3. What can your office hold? If you've already downsized to 60 seats for 100 people, a "everyone in on Wednesday" rule will physically fail. Model peak-day occupancy before committing.
4. What is your management maturity? Flexible hybrid demands managers who set clear goals and measure outcomes. If your managers still supervise by line-of-sight, start with fixed anchor days and evolve.

A worked example

Take a 60-person Pune SaaS company: 35 engineers, 10 sales, 8 support, 7 in ops/HR/finance. A sensible mixed design:

• Engineering: flexible hybrid, minimum 2 office days/week, with Wednesday as a company-wide anchor day for sprint reviews.
• Sales: office-first when not in the field; field visits logged as on-duty, not remote.
• Support: fixed hybrid on a roster, because coverage windows (9 a.m.–9 p.m.) must be staffed and some calls need the office VoIP setup.
• Ops/HR/finance: flexible hybrid, but payroll week (25th–1st) is office-preferred for document handling.

Notice that a good hybrid work policy is rarely one rule for everyone. It's one framework with role-level parameters — and the policy document should say exactly that, so nobody reads team-level differences as favouritism.

Eligibility and Role Suitability Under a Hybrid Work Policy

The fastest way to poison hybrid work is to be vague about who qualifies. Vague eligibility reads as "managers' pets get flexibility." Explicit eligibility, even when restrictive, reads as fair.

Build a role suitability matrix

Assess every role (not every person) against objective criteria. A simple scoring approach:

Then map roles to tiers:

• Tier A — Hybrid by default: engineering, design, content, finance analysts, recruiters (non-interview days).
• Tier B — Hybrid with conditions: support (roster-based), sales (field + office), HR ops (document-cycle constraints).
• Tier C — On-site: admin/front office, IT hardware support, facility and inventory roles.

Publish the tier mapping. When a Tier C employee asks "why not me?", the answer is a documented, role-based reason — not a manager's mood.

Individual eligibility conditions

Beyond role suitability, most Indian SMBs add person-level conditions:

• Probation: many companies require new joiners to work primarily from office for the first 60–90 days for onboarding and culture absorption. If you do this, say it in the offer letter, not after joining.
• Performance standing: employees on a performance improvement plan may be asked to work from office temporarily. Frame this as support and supervision, not punishment, and time-bound it.
• Infrastructure: a stable broadband connection, a reasonably quiet workspace, and power backup where feasible. Some companies verify via a simple self-declaration form.
• Disciplinary status: ongoing disciplinary proceedings can suspend remote eligibility, at HR's discretion.

Handling exceptions without breaking the system

Exceptions are inevitable — a caregiver who needs an extra remote day, an employee relocating to their hometown for six months. Route every exception through a single channel (HR, with manager endorsement), document it with an end date, and review quarterly. The moment exceptions live in private chats, your policy is fiction.

Scheduling Rules and Anchor Days

Why anchor days matter

The most common hybrid failure isn't too much remote work — it's uncoordinated office days. People commute an hour, badge in, and spend the day on video calls with teammates who stayed home. That's the worst of both worlds: commute cost with zero collaboration benefit.

Anchor days fix this. An anchor day is a designated day when a whole team (or the whole company) is expected in office, and the calendar is deliberately loaded with the work that benefits from co-location: sprint planning, design critiques, onboarding sessions, all-hands, difficult one-on-ones, team lunches.

Scheduling rules that work at SMB scale

• Set one company anchor day and one team anchor day. For example: Wednesday is company-wide; each team picks a second day. This guarantees two high-density days without mandating three.
• Require schedule declaration in advance. Employees mark their planned office days for the coming week (or month) in your HRMS or a shared calendar by Friday. This lets facilities plan seating and lets teammates plan collaboration.
• Protect remote days for deep work. Discourage managers from calling ad-hoc "come to office today" demands except for genuine emergencies. If office presence can be demanded at four hours' notice, remote days are unusable — employees can't plan childcare, travel, or focus time.
• Define core hours. Regardless of location, everyone is reachable during a core window — say 11 a.m. to 4 p.m. — for meetings and quick responses. Outside core hours, teams flex.
• Cap consecutive remote stretches if needed. Some SMBs add "no more than 10 consecutive working days fully remote without approval" to prevent silent relocation to another city (which has tax, insurance, and compliance implications — more on that below).

Worked example: a week in a flexible-hybrid team

An 8-person marketing team, minimum 2 office days, Wednesday company anchor:

• Monday: everyone remote. Weekly kickoff on a 30-minute video call. Deep work day.
• Tuesday: 3 members in office (their chosen day), rest remote.
• Wednesday (anchor): all 8 in office. Campaign review, brainstorm, 1:1s stacked in person.
• Thursday: team anchor day. All 8 in again; cross-functional syncs with sales scheduled today.
• Friday: remote for most. No internal meetings after 2 p.m. — a "meeting hygiene" rule the team adopted.

Total: everyone hits their 2-day minimum on high-value days, the office peaks predictably (facilities can plan), and remote days stay protected.

Hybrid Attendance Tracking: Getting the Mechanics Right

Attendance is where hybrid work policy meets payroll reality. In an office-only world, one biometric device settled everything. In a hybrid setup, you need attendance capture that works in both modes, feeds one unified muster, and doesn't turn into surveillance theatre.

The capture methods, compared

The design principle: one muster, two modes

Whatever mix you choose, the non-negotiable requirement is a single attendance register that consolidates office punches and remote check-ins into one view per employee per day, tagged by work mode (Office / Remote / Field / On-duty / Leave). This matters because:

• Payroll needs one source of truth for present days, LOP, and overtime.
• Compliance requires you to produce working-hour records regardless of where the work happened.
• Managers should see mode patterns ("Priya has been fully remote for 3 weeks") without spreadsheet archaeology.

A modern HRMS handles this natively: the biometric device syncs office punches, employees use the mobile app or employee self-service (ESS) portal to check in on remote days, and geo-tagging switches on only for field roles. If you're currently reconciling a biometric export against a WFH Google Form every month, that reconciliation job alone justifies better hybrid attendance tracking tooling.

Attendance rules to write into the policy

Be explicit about the boring cases — they cause most disputes:

• Remote check-in window: e.g., check-in by 10:30 a.m. on remote days; late check-in beyond grace follows the same late-mark rules as office days. Same rules, both modes — this symmetry is what makes hybrid attendance feel fair.
• Missed check-in: a regularisation request within 48 hours, approved by the manager, capped at (say) 3 regularisations per month before HR review.
• Half-day logic: define minimum logged hours for full-day credit (e.g., 8 hours) and half-day credit (e.g., 4 hours), identical for office and remote.
• Mode mismatch: if someone marked "office" but only has a remote check-in (or vice versa), the system flags it for manager confirmation rather than silently defaulting.
• Field and travel days: client visits and travel are "on-duty," captured via geo-tagged app check-in or manager attestation — never forced into fake "remote" or unfair "absent" buckets.
• What attendance is NOT: state plainly that check-in/out records working presence for payroll and compliance — it is not minute-by-minute monitoring, and the company does not track location outside check-in events. Writing this down builds more trust than any town hall speech.

Avoid the surveillance trap

Some vendors will happily sell you keystroke loggers, random webcam snapshots, and always-on GPS. For a typical SMB knowledge-work team, these tools destroy far more value in trust and attrition than they recover in caught slackers. If an employee's output is fine, their mouse movement is irrelevant; if their output is poor, the performance process — not spyware — is the answer. Reserve heavier verification (geo-fencing, photo check-in) for roles where location genuinely is the job, like field sales and on-site service.

Presence Equity: Avoiding Proximity Bias

Here's the risk nobody writes into the policy but everybody feels: the people who come to office more get noticed more, staffed on better projects, and promoted faster — regardless of actual performance. This is proximity bias, and in a hybrid company it quietly recreates inequality along lines of commute distance, caregiving load, and gender.

Presence equity means an employee's visibility, evaluation, and opportunities do not depend on how often their manager physically sees them. It doesn't happen by intention; it happens by mechanism. Build these into your hybrid work policy and manager training:

• Outcome-documented reviews. Require every appraisal input to reference recorded deliverables, metrics, or artefacts — not impressions. "Always around and helpful" is not an appraisal data point.
• Hybrid-blind staffing. When assigning stretch projects, the staffing decision-maker should look at skills and workload, not at who happens to sit nearby. A simple rule: high-visibility opportunities must be posted to the whole eligible team, not handed to whoever's at the next desk.
• One-remote, all-remote meetings. If even one participant joins a meeting remotely, everyone joins from their own laptop — no conference-room huddle with a single sad speakerphone for the remote person. This one norm does more for presence equity than any slogan.
• Structured manager check-ins. Mandate a recurring 1:1 for every direct report at the same frequency regardless of mode. Remote employees shouldn't have to earn conversations that office employees get by walking past.
• Promotion audits. Twice a year, HR reviews promotions, increments, and top ratings split by average office attendance. If the fully-in-office cohort consistently outperforms in ratings but not in measurable output, you have bias, and you now have the data to confront it.
• Leadership models the behaviour. If founders are remote on Fridays and say so openly, remote work is legitimate. If leadership is in office five days and jokes about "the WFH crowd," no policy clause will save you.

For Indian SMBs specifically, presence equity has a retention dimension: hybrid flexibility is one of the strongest levers for retaining experienced women professionals through caregiving years, and for accessing talent in tier-2 cities. If proximity bias makes remote work career-limiting, you'll lose exactly the people the flexibility was supposed to keep.

Communication Norms and Meeting Hygiene

A hybrid work policy that only covers attendance is half a policy. The other half is how people work together across locations. Write these norms down — briefly, plainly — because "common sense" is not commonly distributed.

Channel discipline

Define which channel is for what, so nothing urgent dies in email and nothing trivial explodes on calls:

• Chat (Slack/Teams): default for quick questions; response expected within core hours, not instantly.
• Email: decisions, approvals, external communication, anything needing a record.
• Calls/meetings: discussion and decisions that genuinely need real-time back-and-forth.
• Project tool (Jira/Asana/ClickUp): task status lives here, not in chat. "What's the status?" pings mean the tool isn't being used.
• Phone/WhatsApp: genuine emergencies only. If everything is on WhatsApp, nothing is a record and everything is an interruption.

Availability and the right to disconnect

• Core hours (e.g., 11 a.m.–4 p.m.) are for meetings and fast responses; outside them, response within the working day is acceptable.
• After-hours messages should carry no expectation of reply unless flagged urgent. Encourage scheduled-send. Hybrid work must not silently become 24/7 work — burnout among remote-heavy Indian teams is real, and it shows up as attrition six months later.
• Status hygiene: calendar blocked for focus time is respected; being remote is never a reason to expect someone to absorb extra meetings.

Meeting hygiene rules worth adopting

• Every meeting has an owner, an agenda (even two lines), and a decision or action list posted afterward — so absent and remote colleagues aren't dependent on hallway retellings.
• Default meeting lengths of 25/50 minutes instead of 30/60, so back-to-back calls get breathing room.
• Recurring meetings are audited quarterly; any meeting that could be a written update becomes one.
• Anchor days carry the collaboration-heavy meetings; remote days are protected for maker time.
• Record or minute key decisions in a shared, searchable place. In hybrid teams, written-first is the tax you pay for flexibility — and it's a tax that also buys you better onboarding and fewer "I never knew about this" surprises.

Equipment, Expenses, and Reimbursement Clauses

Ambiguity about money breeds resentment fast. Your hybrid work policy should answer, in writing, exactly what the company provides, what it reimburses, and what it doesn't.

What most Indian SMBs provide

• Laptop and accessories: company-issued laptop is standard; many add a mouse, headset, and on request a monitor or laptop stand for the home setup. Track all of it in an asset register with signed acknowledgment — recovering assets at exit is much easier when issuance was documented.
• Software and connectivity tools: VPN, password manager, licensed software. Never let employees run company work through personal, unlicensed tools to save cost.

Common reimbursement approaches

Whatever you choose, state it precisely: the amount or ceiling, the claim process, the proof required, and the payout cycle. Also state what is not covered — coffee, printer ink, the family's Netflix — with a touch of humanity rather than legalese. And route claims through your HRMS or ESS portal rather than email chains, so finance gets a clean, auditable trail.

The tax note

Allowance structuring (fully taxable allowance vs. reimbursement against bills vs. company-provided assets) has income-tax implications for both employer and employee. These rules evolve; have your CA or payroll consultant confirm current treatment before finalising the clause, and revisit annually.

Data Security and Confidentiality Outside the Office

Every remote workday extends your security perimeter into dozens of homes, cafés, and co-working spaces. For SMBs handling client data — and especially those with enterprise or overseas clients — this section of the hybrid work policy gets read by auditors, so write it properly.

Minimum controls to mandate:

• Company devices only for company work, or a formal BYOD policy with device management if you allow personal devices. Half-measures ("mostly company laptops") are the worst position.
• Access controls: VPN or zero-trust access for internal systems, SSO with multi-factor authentication on all SaaS tools, role-based access, immediate revocation at exit.
• Device hygiene: full-disk encryption, automatic screen lock, OS and antivirus updates enforced via device management where feasible.
• Physical rules: lock screens when stepping away, no confidential calls in public places on speaker, no company data on personal USB drives, privacy screens for sensitive roles working in public.
• Public Wi-Fi: either prohibited for company systems or permitted only through VPN — pick one and say it.
• Household disclosure: employees must ensure family members don't use company devices; confidential documents at home are stored out of casual view and shredded, not binned.
• Printing: discourage or prohibit printing confidential material at home; if unavoidable, require secure disposal.
• Incident reporting: lost device, suspected phishing, or accidental data exposure must be reported to IT within a defined window (commonly 24 hours), with an explicit no-blame framing for prompt self-reporting — you want fast reports, not cover-ups.

Also acknowledge India's data protection law: with the Digital Personal Data Protection Act regime operational, companies handling personal data have real obligations around safeguards and breach handling. Keep the policy language general ("the Company complies with applicable Indian data protection law, and employees must follow the IT security guidelines issued from time to time") and keep the detailed, changeable rules in a separate IT security annexure you can update without re-issuing the whole HR policy.

Measuring Performance by Outcomes, Not Optics

Hybrid work forces a healthy question many companies dodged for decades: how do we know someone is doing a good job, other than seeing them at a desk?

Shift the unit of measurement

• From hours to outcomes. Define, for each role, what "delivered" looks like: features shipped and defect rates for engineers, qualified pipeline and closures for sales, ticket resolution and CSAT for support, close-cycle timeliness and error rates for finance.
• Goals with owners and dates. Whether you use OKRs, KPIs, or a simple quarterly goal sheet, every hybrid employee should be able to answer: "What are my three priorities this month, and how will my manager know they're done?" If that answer is fuzzy, the problem is goal-setting, not remote work.
• Visible work products. Encourage teams to work in shared documents and project tools so progress is observable without anyone asking. This isn't surveillance — it's the professional habit of showing your work.

Manager cadence in a hybrid team

• Weekly or fortnightly 1:1s per direct report, same frequency regardless of work mode.
• A lightweight weekly team update (written or 15-minute call): what shipped, what's blocked, what's next.
• Quarterly reviews anchored in the goal sheet, with evidence — not vibes.

Handling underperformance fairly

When output slips, the response sequence should be identical for office-heavy and remote-heavy employees: diagnose (skill, clarity, workload, or personal circumstance?), support, set a documented improvement plan, and only then consider consequences — one of which may be temporarily increased office presence for closer coaching. What you must never do is respond to one person's underperformance by revoking remote work for the whole team. Collective punishment is the fastest way to convert a performance problem into an attrition problem.

Legal and Compliance Notes for Indian SMBs

Hybrid work sits inside India's existing labour-law framework — there's no single "hybrid work statute," so your obligations come from the general rules, applied thoughtfully. This section is general guidance, not legal advice; state rules differ and change, so verify current requirements with a labour-law professional or your compliance consultant before finalising your policy.

Key areas to think through:

• Shops and Establishments Acts. Most SMB offices are registered under their state's Shops and Establishments Act, which governs working hours, weekly offs, overtime, leave, and record-keeping. These obligations don't evaporate when an employee works from home — the employment relationship, and your duty to maintain attendance and hours records, continues regardless of work location. This is a strong practical argument for unified hybrid attendance tracking: your muster should be producible for any employee, any day, any mode.
• Working hours and overtime. Statutory daily/weekly hour limits and overtime provisions apply to covered employees wherever they work. Hybrid setups blur start and end times, so define standard hours in the policy and ensure your records reflect reality. Be especially careful with rostered and support staff.
• Employee category distinctions. Some protections apply differently to different categories of employees under various laws. If you employ staff in categories with stronger statutory protections, get specific advice rather than applying one blanket clause.
• Location and registrations. If employees permanently work from a state where you have no registered presence, questions can arise around professional tax, state-specific registrations, and labour-welfare contributions. This is why the policy should require employees to declare and seek approval for their primary remote work location and any long-term relocation.
• PF, ESI, gratuity, and payroll statutes. These obligations follow the employment relationship, not the desk. Nothing about hybrid work exempts you — but address-linked details (such as ESI applicability zones) can be affected by where an employee is based, so keep employee address records current.
• Insurance and workplace injury. Check what your group personal accident and workmen's compensation-equivalent coverage says about injuries during working hours at home. Coverage language varies; ask your insurer directly.
• POSH compliance. The Prevention of Sexual Harassment framework extends to virtual interactions and, in practice, to any place visited by the employee arising out of employment. Your Internal Committee's remit and your POSH training should explicitly cover online conduct — chat, video calls, and after-hours messages included.
• Documentation. Reflect hybrid terms in appointment letters or a signed policy acknowledgment. If your standard contract says "place of work: Mumbai office" with no flexibility clause, update your templates.

The overall posture for an SMB: keep the policy's statutory language general, keep meticulous records, and do an annual compliance review — states have been updating establishment rules, and the consolidation of labour codes continues to evolve. What was true when you wrote the policy may not be true two years later.

Rolling Out Your Hybrid Work Policy: A 6-Step Plan

A policy announced by surprise email will be resented; one built with visible consultation will be owned. Here's a rollout sequence sized for a 30–300 person company.

Step 1: Diagnose (Week 1–2)

• Survey employees: current patterns, commute times, home-setup quality, preferences.
• Interview managers: what's working, where the friction is, what they fear.
• Pull data: office occupancy by day, meeting load, attrition exit-interview themes.

Step 2: Design (Week 2–4)

• Choose the model and role tiers using the frameworks above.
• Draft the policy (start from the template below), including attendance mechanics and expense clauses.
• Pressure-test with finance (cost of allowances), IT (security readiness), legal/CA (compliance and tax), and 3–4 candid managers.

Step 3: Decide and document (Week 4–5)

• Leadership signs off on the contentious calls: minimum office days, probation rules, allowance amounts.
• Finalise the document, an FAQ, and a one-page summary. The one-pager is what most employees will actually read — invest in it.

Step 4: Enable the systems (Week 4–6, parallel)

• Configure your HRMS: work-mode tagging, remote check-in via app/web, geo-fencing for field roles, regularisation workflows, manager dashboards.
• Set up the schedule-declaration mechanism and seating plan for anchor days.
• Update offer letter and contract templates.

Step 5: Pilot (Month 2–3)

• Run the policy with 1–2 teams for 4–8 weeks. Track attendance data quality, regularisation volume, meeting-load changes, and sentiment.
• Fix what breaks — check-in windows that don't fit support shifts, anchor days colliding with client schedules — before company-wide launch.

Step 6: Launch and iterate (Month 3+)

• Announce at an all-hands, with leaders explaining the "why," not just the rules.
• Train managers separately: proximity bias, outcome-based goal setting, hybrid meeting facilitation. Managers make or break this policy.
• Collect signed acknowledgments (your ESS portal makes this painless).
• Commit publicly to a review at 6 months, then annually. A hybrid work policy is a living document; version it and change-log it like one.

Common Hybrid Work Policy Mistakes to Avoid

• Copy-pasting a US-corporate policy. References to at-will employment, foreign statutes, and 401(k)s in an Indian SMB policy signal that nobody read it. Write for Indian law and your actual company.
• Policy without enforcement mechanics. "Employees must maintain attendance" is meaningless without check-in tools, grace rules, and regularisation flows.
• Rules for individuals, silence for teams. A 2-day minimum with no anchor coordination gives you full commutes and empty collaboration.
• Treating remote days as a favour. If the tone is "we generously permit," managers will feel entitled to revoke it whimsically, and employees will hoard resentment. It's a work arrangement, governed by rules, changeable with notice — not charity.
• Surveillance overreach. Screenshot-monitoring your accountant erodes trust worth far more than the theoretical loafing it prevents.
• Ignoring the on-site workforce. Office assistants, drivers, and lab staff watch colleagues get flexibility they can't have. Acknowledge it openly and offer what you can — shift-swap flexibility, additional leave consideration, allowances — so hybrid doesn't create a caste system.
• No end-date on exceptions. Every "temporary" arrangement without an expiry becomes permanent, unequal precedent.
• Announcing before systems are ready. If remote check-in doesn't work on launch day, the policy's credibility never recovers.
• Never revisiting the policy. Team size doubles, a second office opens, a big client demands on-site presence — and the policy still describes a company that no longer exists.

Metrics to Track After Launch

You can't manage a hybrid work model on anecdotes. Track a small dashboard monthly or quarterly:

• Office attendance rate vs. policy minimum, by team — spotting both non-compliance and teams drifting fully remote by stealth.
• Anchor-day density — what percentage of a team is actually present on its anchor day? Below ~70%, the anchor isn't anchoring.
• Remote check-in compliance and regularisation volume — high regularisation suggests either a clunky tool or a habit problem; find out which.
• Meeting load per employee — hybrid gone wrong shows up as calendar sprawl.
• Ratings/promotions split by attendance pattern — your presence-equity audit.
• Attrition and offer-acceptance rates before vs. after — flexibility should show up in retention and hiring within two or three quarters.
• eNPS or pulse-survey items on flexibility, fairness, and burnout.
• Space utilisation and cost per seat — if you're paying for 100 seats and peaking at 55, that's a lease conversation worth lakhs.

Review these with leadership twice a year and let the data drive policy revisions — including relaxing rules that turned out to be unnecessary.

Hybrid Work Policy Template for Indian SMBs (Copy and Adapt)

Below is a complete skeleton you can adapt. Replace bracketed placeholders, delete clauses that don't apply, and have it reviewed by your legal/compliance advisor before issuing.

---

[Company Name] — Hybrid Work Policy Version: 1.0 | Effective date: [date] | Owner: Human Resources | Applies to: All employees of [Company Name], per eligibility below

1. Purpose. This policy defines how employees of [Company Name] may split working time between Company premises and approved remote locations, and the rules governing attendance, conduct, security, and expenses in both modes.

2. Definitions. Office day: a working day performed primarily at Company premises. Remote day: a working day performed at the employee's approved remote location. Anchor day: a designated day on which in-office presence is expected. Approved remote location: the residential address declared by the employee and approved by HR.

3. Work model. The Company follows a [flexible hybrid / fixed hybrid / office-first / remote-first] model. Eligible employees shall work from the office a minimum of [2] days per week, including the company anchor day ([Wednesday]) and their team anchor day. Managers may require additional office presence for specific business needs with at least [24/48] hours' notice, used sparingly.

4. Eligibility. Hybrid eligibility is determined by role tier as published by HR: Tier A (hybrid by default), Tier B (hybrid with conditions), Tier C (on-site). Individual eligibility additionally requires: completion of [90] days of service (unless the offer letter states otherwise); satisfactory performance standing; a self-declared adequate remote workspace and internet connection; and no active disciplinary proceedings. Exceptions require written HR approval with a defined end date.

5. Working hours and availability. Standard working hours are [9:30 a.m.–6:30 p.m.], [Monday–Friday], identical for office and remote days. All employees must be reachable during core hours of [11:00 a.m.–4:00 p.m.]. Statutory limits on working hours and overtime apply regardless of work location.

6. Scheduling. Employees shall declare their planned office days for the following [week/month] in the [HRMS/calendar] by [Friday 5 p.m.]. Changes must be updated in the system. Team anchor days are set by team leads in consultation with HR.

7. Attendance. On office days, attendance is recorded via [biometric device/access card]. On remote days, employees must check in and out through the [HRMS mobile app/ESS portal] by [10:30 a.m.]. Field visits are recorded as on-duty via [geo-tagged app check-in/manager attestation]. Late marks, half-day rules, and leave-without-pay rules apply identically to office and remote days as per the Attendance Policy. Missed check-ins may be regularised within [48 hours] with manager approval, subject to a cap of [3] per month. Attendance records exist for payroll and statutory compliance; the Company does not conduct continuous location tracking or covert monitoring.

8. Remote location and relocation. Remote work must be performed from the approved remote location within [city/state/India]. Working from any other location for more than [5] consecutive working days, or any permanent relocation, requires prior written approval, as it may affect tax, insurance, and statutory registrations.

9. Equipment and expenses. The Company provides a laptop and standard accessories, recorded in the asset register and returnable on exit. Eligible hybrid employees receive [an internet allowance of ₹_ per month / reimbursement of ₹ against bills], claimed via [ESS/finance process]. [Optional: one-time home-office setup support of ₹, recoverable pro-rata on exit within _ months.] Commuting costs, utilities, and other home expenses are not reimbursed unless expressly stated.

10. Data security and confidentiality. Employees must use Company-issued devices and approved software for all Company work; connect to internal systems only via [VPN/approved access]; enable screen lock and keep devices updated; refrain from using public Wi-Fi without VPN; prevent household members from accessing Company devices; avoid printing confidential material at remote locations; and report lost devices or suspected security incidents to IT within [24 hours]. The Company's IT Security Guidelines and obligations under applicable Indian data protection law apply at all locations. Breach of this clause may result in withdrawal of remote eligibility and disciplinary action.

11. Communication norms. Employees shall keep calendars current, use [project tool] for task status, respond to messages within [core hours/the working day], and follow the Company's meeting guidelines. If any participant attends a meeting remotely, all participants join via their own devices.

12. Performance. Performance is assessed on outcomes against agreed goals, not on work location or office attendance beyond the policy minimum. Managers shall hold [weekly/fortnightly] one-on-ones with each direct report irrespective of work mode.

13. Health, safety, and conduct. Employees are expected to maintain a safe working environment at the remote location and report any work-related injury promptly. All Company policies — including the Code of Conduct and the Policy on Prevention of Sexual Harassment — apply fully to remote work and virtual interactions.

14. Non-compliance. Repeated attendance irregularities, misuse of remote work, or breach of security obligations may result in withdrawal of hybrid eligibility and disciplinary action per the Company's disciplinary process.

15. Review and amendment. This policy does not form a contractual entitlement to remote work. The Company may amend, suspend, or withdraw it with [30 days'] notice, subject to applicable law. The policy will be reviewed at least annually.

Acknowledgment: I have read and understood the Hybrid Work Policy and agree to comply. — [Name, Employee ID, Signature/e-sign, Date]

---

Policy clause checklist

Before you publish, verify the document covers every row:

Frequently Asked Questions

Is a hybrid work policy legally required in India?

No law specifically mandates a hybrid work policy. But laws that do apply — state Shops and Establishments Acts, working-hour rules, payroll statutes, POSH — apply to hybrid work too, and a written policy plus clean attendance records is how you demonstrate compliance. Practically, once you cross a few dozen employees, a written policy is the only way to keep arrangements consistent and defensible. Verify your state's current requirements with a professional.

How many office days should an Indian SMB mandate?

There's no magic number, but 2–3 days per week is the most common band for knowledge-work SMBs, typically structured around one company anchor day plus one team day. The better question is which days and what happens on them: two well-designed anchor days beat four uncoordinated ones. Choose based on your work's real collaboration needs, commute realities, and office capacity — then commit and review in six months.

How do we track attendance on work-from-home days without spying on people?

Use a simple web or mobile check-in/check-out through your HRMS, governed by the same grace and half-day rules as office days, feeding the same unified muster as your biometric device. That satisfies payroll and statutory record-keeping. Reserve geo-fencing for field roles where location is the job, and skip keystroke or webcam monitoring entirely for typical roles — the trust cost far exceeds the benefit.

Can we deny hybrid work to specific employees or teams?

Yes, if the basis is documented and role-related: on-site job requirements, coverage rosters, probation, or a time-bound performance intervention. Publish role tiers so restrictions read as policy, not favouritism, and route individual exceptions through HR with end dates. What creates legal and morale risk is arbitrary, inconsistent, or discriminatory application — the same request approved for one employee and denied for a similarly-placed colleague without a stated reason.

What should we pay for when employees work from home?

The common SMB package: company laptop and accessories, a modest monthly internet allowance or bill reimbursement, and sometimes a one-time home-setup grant with a recovery clause. Electricity and commute costs are usually excluded. Whatever you decide, write exact amounts and claim processes into the policy, and confirm the current tax treatment of allowances versus reimbursements with your CA.

How do we stop remote employees from being overlooked for promotions?

Engineer against proximity bias rather than hoping managers rise above it: require appraisal inputs to cite documented outcomes, post stretch opportunities to whole teams instead of handing them to whoever's nearby, mandate equal 1:1 cadence for all reports, run one-remote-all-remote meetings, and audit ratings and promotions against attendance patterns twice a year. If leaders themselves visibly work remotely sometimes, the message lands.

What happens if an employee quietly moves to another city while "working from home"?

This is why the policy requires an approved remote location and prior approval for extended stays elsewhere. Undisclosed relocation can affect professional tax, state registrations, ESI applicability, insurance coverage, and your ability to require office presence. Handle discovered cases through conversation first — often it's a genuine family need you can formalise — but make the declaration requirement and its rationale explicit in the policy.

How often should the hybrid work policy be reviewed?

Review formally at six months after launch, then at least annually — and immediately upon triggers like headcount doubling, a new office, new state hires, major client contractual requirements, or changes in labour regulations. Version the document, keep a change log, and re-collect acknowledgments when material terms change.

Conclusion: Write It Down, Then Make It Effortless

A good hybrid work policy is not a culture manifesto and not a surveillance regime. It's a clear, humane operating agreement: here's the model, here's who's eligible, here's how we track attendance fairly in both modes, here's what we pay for, here's how we keep data safe, and here's the promise that your career depends on your output — not on how often your manager sees your face.

Start with the template above, adapt it with your managers and your compliance advisor, pilot it with one team, and commit to reviewing it honestly. The companies that get hybrid right in 2026 aren't the ones with the cleverest rules — they're the ones whose rules are written down, applied consistently, and revised without ego.

And when you're ready to make the mechanics effortless — one attendance muster across biometric and remote check-ins, geo-tagged field attendance, leave and regularisation workflows, and policy acknowledgments through an employee self-service portal — a purpose-built HRMS like CozyHR can take the spreadsheet reconciliation off your plate entirely. It's built for Indian SMBs, it plugs attendance straight into payroll, and you can see it working with your own policy in a free trial before you commit. Write the policy first; then let the software carry it.