Return-to-Office Mandates: A Policy Guide for India

Return-to-Office Mandates in 2026: A Policy Playbook for Indian Employers

Five years after the pandemic first sent employees home, the conversation inside Indian boardrooms has quietly flipped. Where HR leaders once debated how much remote work to permit, many are now debating how much in-office time to require. Through 2025 and into 2026, a growing number of global and Indian organisations have tightened hybrid policies, introduced fixed office days, or asked employees to return full-time. For HR managers, founders, and payroll teams, this shift raises a practical question that goes well beyond sentiment: how do you design and roll out a return-to-office (RTO) policy that is fair, legally sound, operationally workable, and doesn't trigger a wave of resignations or grievances?

This article is a practical playbook. It does not assume every company should mandate RTO, nor does it claim remote work has "failed." Instead, it lays out the considerations, models, legal context, and step-by-step process Indian HR teams need if their leadership has decided — or is considering — that more in-person time is the right call for their organisation.

Why Companies Are Mandating Return-to-Office in 2026

The push toward more in-office time is not driven by a single factor. It is usually a combination of business, cultural, and financial pressures that build up over a year or two of hybrid or remote operation.

Collaboration and speed of decision-making

Leaders across sectors have observed that certain kinds of work — early-stage ideation, cross-functional problem solving, onboarding new hires into a team's unwritten norms — happen faster and with fewer misunderstandings in person. Video calls are excellent for status updates and structured meetings, but they compress the informal, ad-hoc conversations that often unblock decisions: the two-minute hallway clarification, the whiteboard sketch, the "can you look at this for a second" moment. When teams are fully distributed, these interactions either don't happen or get formalised into another meeting, which slows things down.

Culture, mentorship, and early-career development

This is one of the most commonly cited reasons for RTO mandates, and it deserves to be taken seriously rather than dismissed as nostalgia. Junior employees — especially those in their first two to three years of a career — learn a large part of their craft by observing how experienced colleagues handle ambiguity, client pushback, or a difficult stakeholder conversation. That kind of tacit, observational learning is hard to replicate over video calls, where interactions are scheduled, agenda-driven, and stripped of the surrounding context. Many organisations mandating RTO explicitly frame it as an investment in their pipeline of future managers and specialists, not just a productivity lever.

Culture-building follows a similar logic. Shared rituals, spontaneous celebrations, cross-team friendships, and a general sense of "we're in this together" are harder to sustain purely through digital channels, particularly as organisations scale and onboard people who have never met most of their colleagues face to face.

Real estate utilisation and cost justification

Many Indian companies — particularly those with large offices in cities like Bengaluru, Gurugram, Pune, Hyderabad, and Mumbai — signed long leases before or during the pandemic and have been paying for space that sits mostly empty on a given day. Boards and CFOs increasingly ask a fair question: if we're paying for the square footage, shouldn't we be using it? RTO mandates in some organisations are as much a real estate and cost-utilisation decision as they are a cultural one.

Management visibility and performance concerns

Some leaders have genuinely struggled to manage distributed teams effectively — not because remote employees perform worse, but because many managers were never trained to set clear outcomes, run asynchronous check-ins, or evaluate work by output rather than presence. Rather than investing in better remote management practices, some organisations have taken the simpler (if blunter) route of requiring physical presence, on the theory that visibility solves the management gap. This is a legitimate driver, even if it isn't always the most sophisticated solution.

Balancing this against employee expectations

None of this erases the fact that employees — across seniority levels, but especially those with long commutes, caregiving responsibilities, or health considerations — have come to genuinely value flexibility. For many, remote or hybrid work isn't a perk; it's what allows them to manage a household, avoid two to three hours of commuting in traffic-heavy Indian metros, or work effectively despite a disability or chronic health condition.

The honest starting point for any HR team designing an RTO policy is to acknowledge this tension directly rather than pretend it doesn't exist. A policy that only serves the employer's real estate spreadsheet, without addressing the employee's daily reality, will generate resentment and attrition risk regardless of how it's communicated. The best RTO policies are the ones that are explicit about the business rationale, honest about the trade-offs, and generous with the mechanisms that make the transition livable for employees.

Models of Return-to-Office: Choosing the Right Structure

There is no single "correct" RTO model. The right choice depends on the nature of the work, the maturity of the organisation, client expectations, and the geographic spread of the workforce. Broadly, Indian employers are choosing between four models.

1. Full return (five days a week in office)

Employees are expected in the office every working day, with exceptions handled on a case-by-case basis. This model is most common in client-facing roles, manufacturing-adjacent operations, regulated industries, and organisations that tried hybrid and found coordination difficult to sustain.

• Pros: Maximum predictability, easiest to manage, no scheduling complexity, full utilisation of real estate, strongest immersion for new hires.
• Cons: Least attractive to talent that has come to expect flexibility, highest commute burden, hardest to defend if a large portion of the work is genuinely location-independent, likely to trigger the most pushback and attrition risk if introduced abruptly.

2. Hybrid with fixed anchor days

The organisation designates specific days (for example, Tuesday, Wednesday, and Thursday) as mandatory in-office days for everyone, or for specific teams, with the remaining days flexible.

• Pros: Predictable for collaboration and meeting scheduling, easier to plan facilities and catering, ensures teams overlap in person rather than each person choosing different days, simpler to track and audit than flexible models.
• Cons: Doesn't account for individual circumstances (a fixed Tuesday may clash with a caregiving commitment every week), can lead to overcrowded offices on anchor days and empty ones on other days, employees may feel the fixed days are arbitrary if not tied to a clear rationale.

3. Hybrid with flexible days

Employees are required to be in office a set number of days per week or month (for example, "at least 3 days a week") but can choose which days, sometimes in coordination with their manager or team.

• Pros: Gives employees more autonomy, can better accommodate personal circumstances, spreads office usage more evenly across the week.
• Cons: Harder to guarantee that the "right" people are in the office on the same day, more complex to track and report on, risk of employees consistently choosing the quietest days and defeating the collaboration goal unless team-level coordination is layered on top.

4. Team-based or role-based scheduling

Rather than a company-wide rule, individual teams or functions set their own in-office cadence based on the nature of their work. A customer support team that collaborates constantly might choose four days; a specialised engineering team that works asynchronously might choose one.

• Pros: Most tailored to actual work patterns, likely to have the highest buy-in because teams have a voice in the decision, avoids a one-size-fits-all mandate that doesn't fit every function.
• Cons: Requires strong manager judgment and consistent application within a team to avoid perceptions of unfairness, harder for HR and payroll to standardise policy language and tracking, can create visible disparities between teams that employees compare against each other.

Many organisations that get this right choose a hybrid of these models: a company-wide minimum (say, hybrid with fixed anchor days for cross-functional alignment) combined with team-level discretion on the remaining days. The key is to make the rationale for whichever model is chosen explicit, so it doesn't read as an arbitrary number picked to satisfy a real estate lease.

Designing a Fair, Clearly Communicated RTO Policy

Once a model is chosen, the real work begins: turning it into a policy that people can actually follow, that treats employees consistently, and that survives scrutiny if challenged.

Start with eligibility criteria

Define clearly which roles, levels, and locations the policy applies to. Some organisations apply RTO mandates only to employees within a certain commuting radius of an office; others apply it uniformly and offer relocation or commute support. Be explicit about:

• Which job families or roles are covered (and which, if any, remain fully remote by design — for example, roles hired explicitly as remote before the policy existed).
• Whether the policy applies uniformly across levels, or whether senior leaders are expected to model the same in-office presence as everyone else (this matters enormously for credibility — a policy that visibly exempts leadership breeds cynicism fast).
• How the policy applies to employees based in cities without a company office, and whether they are grandfathered as remote or expected to relocate.

Build a real exceptions process, not a token one

A policy that has no exceptions process, or one that exists only on paper, is the single biggest driver of grievances and discrimination claims. HR teams should build a structured, documented exceptions process covering at minimum:

• Caregivers: Employees with primary responsibility for young children, elderly parents, or family members with health conditions. Consider whether a modified schedule (rather than a blanket exemption) is workable.
• Disability and medical conditions: Employees whose health conditions make daily commuting or full-time office presence difficult. This should be handled with medical documentation processes that respect privacy, and considered alongside reasonable accommodation principles even where Indian law does not mandate the exact framework used in some other countries.
• Location constraints: Employees who were hired as remote and live far from any office, or who relocated with company knowledge during a period when remote work was permitted.
• Temporary circumstances: Pregnancy, recovery from surgery or illness, a family emergency, or similar time-bound situations.

Whatever the exceptions framework, the critical design principle is consistency. Every exception request should go through the same process, be evaluated against the same criteria, and be documented the same way — not decided informally by whichever manager happens to like or dislike the employee asking.

Communicate the "why," not just the "what"

Employees tolerate policies they disagree with far better when they understand the reasoning. A communication plan should include:

• A clear, honest statement of why the organisation is making this change (business rationale, not vague language about "culture").
• What specifically is changing, effective when, and for whom.
• What support is available (commute allowances, transition periods, exception processes).
• Who to contact with questions or hardship requests, and by when.

Phase the rollout

Very few RTO mandates land well if they are announced with immediate effect. A phased approach — announcing the policy, giving a lead time of several weeks to months before enforcement begins, and potentially stepping up the required days gradually (for example, one day a week for the first month, then two, then the target) — gives employees time to adjust commutes, childcare, and routines. It also gives facilities teams time to prepare the physical office for higher occupancy.

Legal and HR Policy Considerations in India

RTO mandates are not just a communication exercise — they intersect with employment law and contractual obligations in ways Indian HR teams need to think through carefully. This section covers general considerations; specific situations should always be reviewed with qualified legal counsel, since employment law varies by state and the facts of each case matter.

Check the appointment letter and employment contract

The starting point for any RTO decision is the language already in the employee's appointment letter or employment contract.

• If the contract specifies a work location (a particular office address or city), unilaterally requiring the employee to work from a different location, or changing their designated place of work fundamentally, may require formal consent or a contract amendment — not just a policy announcement.
• If the contract or appointment letter was silent on location, or if it explicitly stated the role was "remote" or "work from home," changing that arrangement is a more material change and should be handled with a formal addendum, mutual agreement, or at minimum, clear written communication and a reasonable transition period.
• For employees hired after a company had already adopted a hybrid or remote model, check whether the offer letter or any subsequent communication (including emails, HR portal confirmations, or policy documents) created an expectation of continued flexibility. Even informal commitments made during recruitment can matter if a dispute arises.

As a general practice, any material change to work location or attendance expectations should be reflected in an updated appointment letter, HR policy manual, or a signed acknowledgment from the employee — not left as an unwritten expectation communicated only via a team chat message or town hall.

Apply the policy consistently to avoid discrimination claims

Indian employment law does not have a single omnibus "return to office" statute, but general principles of fair and non-discriminatory treatment apply across service conditions, standing orders (where applicable), and the broader legal framework governing employment relationships, including protections against arbitrary or discriminatory treatment. Inconsistent application of an RTO policy is the most common way employers expose themselves to grievances, internal complaints, or legal claims. Concretely, this means:

• The same exceptions criteria should be applied to every employee in a comparable situation, regardless of seniority, gender, or personal relationship with the manager.
• Decisions to grant or deny an exception should be documented with a clear, defensible rationale — not left to memory or informal conversation.
• HR should audit exception approvals periodically to check for patterns that could look discriminatory (for example, if requests from women employees or employees with disabilities are being denied at a noticeably higher rate than others).
• Special care should be taken with employees on maternity leave, and with pregnant employees or those who have recently returned from maternity leave, given the specific statutory protections around maternity benefits in India. RTO expectations for this group should be handled with particular sensitivity and, where relevant, in line with applicable maternity benefit provisions.

Update the HR policy manual and internal documentation

The RTO policy should not live only in a slide deck or an email announcement. It needs to be formally incorporated into:

• The HR policy manual or employee handbook, with a clear effective date.
• The attendance and leave policy, since RTO expectations interact directly with how attendance is tracked and reported.
• Any policies on remote work, flexible work, or work-from-home that currently exist and may now be outdated or contradictory.
• Onboarding materials for new hires, so expectations are set correctly from day one rather than needing to be walked back later.

Keeping these documents in sync avoids a common and entirely avoidable problem: an employee pointing to an old work-from-home policy that HR forgot to formally retire.

Consider works councils, unions, or employee representative bodies where applicable

In organisations with recognised unions or employee representative bodies — more common in manufacturing, certain PSU-linked entities, or larger industrial employers — any change to working conditions, including attendance requirements, may need to go through a consultation process before implementation. Even where not legally mandated, consulting employee representatives early tends to produce a smoother rollout and surfaces practical problems before they become policy failures.

Attendance and HRMS Implications

A return-to-office mandate is only as good as an organisation's ability to track it fairly, transparently, and without creating a surveillance culture that undermines the trust the policy is trying to rebuild.

Tracking in-office days without overreach

Most Indian employers use one or more of the following methods to track office attendance under a hybrid policy:

• Badge-in / access card systems: Physical entry logs tied to office access cards, which double as a security control and an attendance record.
• HRMS check-in/check-out: Employees mark attendance through a mobile app or web portal, sometimes combined with geofencing that confirms the check-in happened within a defined radius of the office.
• Geofencing: Useful for confirming location without requiring constant location tracking — typically triggered only at check-in/check-out rather than continuous monitoring, which is an important distinction to communicate to employees who may otherwise worry about being tracked throughout the day.
• Calendar and meeting-room booking data: A softer signal, sometimes used as a supplementary indicator rather than a primary attendance record.

Whichever method is chosen, transparency matters. Employees should know exactly what is being tracked, how the data is used, who can see it, and how long it is retained. Overly invasive tracking (continuous location monitoring, for instance) tends to generate far more distrust than it's worth and should generally be avoided in favour of simple check-in/check-out mechanisms.

Hybrid attendance reporting

For a hybrid policy to function, HR and managers need visibility into:

• Individual compliance with required in-office days, ideally visible to the employee themselves (self-serve dashboards reduce disputes far more effectively than surprise reports).
• Team-level patterns, so managers can see whether their team is actually overlapping on anchor days or whether people are quietly avoiding the office on the days that matter for collaboration.
• Exceptions and approved deviations, so attendance reports don't unfairly flag someone who has a documented accommodation.

A modern HRMS platform that combines attendance, leave, and policy management in one place makes this dramatically easier than trying to reconcile spreadsheets, badge logs, and manager emails after the fact.

Linking attendance to performance or perks — proceed cautiously

Some organisations are tempted to tie RTO compliance directly to performance ratings, bonuses, or promotion eligibility. This can be effective as a lever, but it carries real risk if not designed carefully:

• Attendance is an input, not an outcome. Tying it too tightly to performance ratings risks penalising strong performers who have legitimate, approved exceptions, and rewarding weak performers who simply show up.
• If attendance-linked consequences are introduced, they should be applied only after employees have had clear notice, a reasonable transition period, and a functioning exceptions process — never retroactively.
• Any perks tied to office attendance (preferred parking, better desks, free meals on in-office days, team lunch budgets) are generally safer and less legally fraught than tying attendance to compensation or ratings, since they function as incentives rather than penalties.
• If compliance issues are severe and persistent for a specific employee, they should be handled through the normal disciplinary or performance management process — with documentation, warnings, and an opportunity to explain — rather than through blanket automated penalties.

The safest approach for most organisations is to use attendance data to inform conversations (between manager and employee, and between HR and business leaders) rather than to feed it directly and automatically into compensation or rating outcomes.

Managing Pushback: Change Management and Communication

Even a well-designed RTO policy will face resistance. How that resistance is managed determines whether the organisation experiences a rough month of adjustment or a lasting dip in engagement and a spike in attrition.

Treat this as a change management project, not an announcement

The single biggest mistake organisations make is treating an RTO mandate as a one-time announcement rather than an ongoing change process. Effective change management for RTO typically includes:

1. Early signalling. Where possible, give employees advance notice that a change is being considered, rather than having the final policy arrive as a surprise.
2. Multiple communication channels. A single email is not enough. Use town halls, manager cascades, FAQs, and one-on-one conversations for those with specific concerns.
3. Manager enablement. Frontline managers will field most of the questions and pushback. Equip them with talking points, a clear escalation path for hardship cases, and the authority to handle routine exception requests without escalating every single one to HR.
4. A genuine feedback channel. Give employees a way to raise concerns — anonymously if needed — and commit to reviewing that feedback and communicating what changed as a result, even if the core policy doesn't move.

Addressing commute concerns

Commute time and cost are the most commonly cited employee objections to RTO, particularly in traffic-heavy cities. Practical mitigations include:

• Shuttle services or transport allowances for employees travelling long distances.
• Flexible start and end times so employees can avoid peak traffic windows while still completing their required in-office hours.
• Satellite or co-working space options for employees who live far from the main office, allowing them to fulfil an "in-person" requirement without the full commute.
• Reviewing whether the number of required days can be reduced for employees above a certain commute-distance threshold, as a documented exception category rather than an ad hoc favour.

Addressing childcare and caregiving concerns

For employees with young children or elderly dependents, a rigid five-day mandate can be genuinely difficult to absorb without support. Options worth considering:

• Partnering with, or subsidising, childcare or daycare services near the office.
• Allowing flexible in-office days for caregivers rather than fixed anchor days, where operationally feasible.
• Building a formal, well-publicised hardship exception process specifically for caregiving situations, rather than leaving it to informal manager discretion.

Phased timelines reduce shock

Rolling out the full requirement immediately tends to produce the sharpest resistance and the highest short-term attrition risk. A phased timeline — for example, starting with two in-office days for the first month, moving to three after a review period, and reaching the final target over a quarter — gives employees, facilities teams, and managers room to adjust and gives HR a chance to catch problems (overcrowded offices, inadequate meeting rooms, parking shortages) before they become widespread complaints.

Measuring Success: Beyond Just "Who Showed Up"

Attendance percentage is the easiest metric to track, but it is a poor proxy for whether an RTO policy is actually achieving its underlying goals. A more complete measurement framework includes:

Engagement surveys

Run pulse surveys before, during, and after the rollout to track sentiment specifically related to the RTO policy — not just general engagement. Ask targeted questions about perceived fairness, clarity of communication, and whether employees feel the exceptions process is being applied consistently. Trend this over time rather than relying on a single snapshot.

Attrition tracking

Monitor voluntary attrition closely in the months following an RTO announcement, broken down by team, tenure, level, and demographic where legally and ethically appropriate to do so. A spike in regretted attrition (departures of high performers you wanted to keep) is a much more urgent signal than overall attrition ticking up slightly. Exit interviews should explicitly probe whether RTO was a factor in the decision to leave, so HR has real data rather than anecdotes.

Productivity and collaboration signals

Depending on the function, useful signals include project delivery timelines, client satisfaction scores, internal mobility and promotion rates for newer employees (a proxy for whether mentorship is actually improving), and qualitative manager feedback on team cohesion. Avoid relying on any single proxy metric in isolation — combine quantitative signals with qualitative manager input.

Manager feedback loops

Set up a regular (monthly or quarterly) structured feedback loop with people managers specifically about how the RTO policy is functioning on the ground: Are anchor days actually achieving cross-functional overlap? Are exception requests being handled fairly and promptly? Are there operational friction points (desk shortages, meeting room availability, noise) undermining the intended benefits? Managers are often the first to notice when a policy that looks fine on paper isn't working in practice.

Be willing to adjust

The organisations that handle RTO best treat the initial policy as a starting point, not a final answer. Building in a formal review point — for example, a structured assessment at the 90-day and 180-day marks — signals to employees that the policy is being taken seriously as an evolving practice, not imposed and forgotten.

A Step-by-Step 90-Day Rollout Plan

The following plan is a general framework HR teams can adapt to their own timeline and organisational context.

Days 1–15: Design and alignment

• Finalise the RTO model (full return, fixed hybrid, flexible hybrid, or team-based) in consultation with business leaders and, where relevant, employee representatives.
• Draft the policy document, including eligibility, exceptions criteria, and enforcement approach.
• Review and update appointment letter templates and the HR policy manual to reflect the new expectations.
• Consult legal counsel on any location-specific contractual or regulatory considerations.
• Prepare the HRMS to support attendance tracking, geofencing (if used), and reporting for the new policy.

Days 16–30: Leadership and manager readiness

• Brief senior leadership and ensure they commit to visibly following the same policy themselves.
• Train people managers on the policy details, the exceptions process, and how to handle difficult conversations.
• Finalise support mechanisms: commute allowances, shuttle services, childcare support, satellite office options.
• Prepare FAQ documents and communication materials.

Days 31–40: Announcement

• Announce the policy company-wide through a town hall or equivalent forum, led by senior leadership, with a clear explanation of the business rationale.
• Distribute the written policy, FAQ, and exceptions request process to all employees.
• Open a dedicated channel (email alias, HR ticketing category, or portal) for questions and hardship requests.
• Give employees a defined window (at least two to four weeks) to submit exception requests before enforcement begins.

Days 41–60: Transition period

• Begin a phased implementation — for example, starting at a reduced number of required days before ramping to the full target.
• Process exception requests promptly and consistently, with documented rationale for each decision.
• Monitor early attendance data and facilities readiness (desk availability, meeting rooms, parking, connectivity).
• Run a first pulse survey to capture early sentiment and identify emerging friction points.

Days 61–75: Full enforcement begins

• Move to the full target attendance requirement as originally communicated.
• Continue tracking attendance data and flag patterns (not individuals) for review — for example, whether certain teams are consistently under-complying, which may indicate an operational or communication gap rather than individual non-compliance.
• Hold manager check-ins specifically focused on how the policy is landing within their teams.

Days 76–90: Review and adjust

• Conduct a structured 90-day review combining attendance data, survey results, attrition figures, and manager feedback.
• Identify what's working (which anchor days are driving genuine collaboration, which support mechanisms are being used) and what isn't.
• Make adjustments where warranted — this could mean refining the exceptions process, adding support for a specific group, or revisiting the required number of days for a particular function.
• Communicate the review findings and any resulting changes back to the organisation, reinforcing that the policy is being actively managed rather than set and forgotten.
• Set the cadence for ongoing review (for example, quarterly) going forward.

Comparison Table: RTO Models at a Glance

Practical Tips for SMBs and Startups

Smaller organisations often face RTO decisions with fewer resources than large enterprises, but also with more room to move quickly and personalise the approach. A few practical pointers:

• Don't copy a large company's policy wholesale. A five-day mandate that makes sense for a 5,000-person company with dedicated facilities teams may be operationally and financially unworkable for a 40-person startup with a small shared office.
• Use RTO as a culture-building tool, not just a compliance exercise. Smaller teams can get outsized value from even one or two well-designed in-office days a week — team lunches, structured collaboration sessions, or informal mentorship time — without needing a rigid five-day mandate.
• Be honest about the real driver. If the real reason is a lease commitment or investor pressure around office utilisation, say so. Startup employees are usually sophisticated enough to respect a transparent business rationale far more than a vague culture argument that doesn't match reality.
• Keep the exceptions process lightweight but real. A startup doesn't need an elaborate HR bureaucracy, but it does need a documented, consistent way to handle requests — even if that's a simple form and a same-week manager decision, rather than a multi-week enterprise approval chain.
• Invest in a proper HRMS early. Many small companies track attendance in spreadsheets or informal chat check-ins, which becomes unmanageable and legally risky as headcount grows. A lightweight HRMS with attendance and policy tracking built in pays for itself quickly once you're managing hybrid schedules across more than a handful of people.
• Watch for founder exceptionalism. In small companies, it's especially visible and damaging if founders or early employees are seen skipping the same rules they've imposed on newer hires. Consistency matters even more in a small, tightly connected team.

Frequently Asked Questions

1. Can an Indian employer legally require employees to return to the office if their offer letter didn't specify a location?

Generally, yes — but it depends on the specific language in the offer letter and any subsequent communication. If the appointment letter is silent on location or gives the employer discretion over workplace, requiring office attendance is usually within the employer's rights, provided it's communicated clearly and applied fairly. If the offer letter or later communication explicitly designated the role as remote, changing that is a more material change and should ideally be handled through a formal addendum or documented mutual agreement rather than a unilateral policy change alone. When in doubt, consult legal counsel before enforcing a mandate against employees whose contracts suggest a remote arrangement.

2. What happens if an employee simply refuses to comply with an RTO mandate?

This should be handled through the organisation's standard performance and conduct management process, not through informal or inconsistent responses. Typically this means: a documented conversation explaining the requirement and hearing the employee's reasons, an opportunity to apply for a formal exception if one exists, and only then — if there is genuinely no valid exception and the refusal continues — escalation through standard disciplinary steps with appropriate documentation at each stage. Consistency and documentation are critical, since inconsistent enforcement is the most common source of disputes.

3. Do we need to give employees advance notice before enforcing a new RTO policy?

There's no single fixed legal notice period that applies universally in India, but reasonable advance notice is both good practice and a practical risk-reduction measure. Employees need time to arrange commutes, childcare, and daily logistics. Most organisations that roll out RTO successfully give at least a few weeks to a couple of months of lead time, often paired with a phased implementation rather than immediate full enforcement.

4. How should we handle employees who moved to a different city during the remote-work period?

This is one of the trickier situations HR teams face. Options include: grandfathering these employees as remote if the relocation happened with the company's knowledge and implicit or explicit approval; offering relocation assistance if they're expected to return to the original office city; or creating a hybrid arrangement tied to a satellite office or co-working space near their new location, if one exists. The fairest approach usually depends on whether the company was aware of and effectively condoned the relocation at the time it happened — this history should be checked before deciding how to handle the case.

5. Should attendance data be linked to performance ratings or bonuses?

Proceed carefully. Attendance is an input, not a direct measure of output or quality of work. Many HR practitioners recommend using attendance data primarily to inform manager conversations and flag patterns worth discussing, rather than feeding it automatically and directly into compensation or rating decisions. If a link to performance consequences is introduced, it should come with clear advance notice, a functioning exceptions process, and consistent application — not a retroactive or informally applied penalty.

6. How do we handle RTO policy for employees with disabilities or chronic health conditions?

These situations should go through a documented accommodation process — reviewing the specific condition (with appropriate medical documentation and respect for privacy), the nature of the role, and what reasonable adjustments would allow the employee to work effectively, whether that's a modified attendance schedule, equipment support, or continued remote work for that individual. Blanket application of an RTO mandate without an accommodation pathway for this group carries meaningful legal and ethical risk.

7. What's a realistic timeline for rolling out an RTO mandate without triggering a wave of resignations?

There's no universal number, but a rushed rollout — announcing a policy with immediate or near-immediate effect — is consistently associated with sharper pushback and higher short-term attrition than a phased approach. A 60–90 day runway from announcement to full enforcement, combined with a genuine exceptions process and visible leadership buy-in, tends to produce a smoother transition than a sudden mandate, even if the ultimate policy is exactly the same.

8. How is RTO different for startups versus large enterprises in India?

Startups typically have smaller offices, tighter budgets for commute or childcare support, and less HR infrastructure — but they also have more flexibility to design a policy that fits their specific team rather than adopting a rigid enterprise-style mandate. Large enterprises usually have more resources to offer support mechanisms (shuttles, childcare tie-ups, satellite offices) but face more complexity in applying policy consistently across many teams, locations, and levels. Both need the same underlying discipline: a clear rationale, a documented exceptions process, and consistent enforcement — just implemented at different scales.

Conclusion

Return-to-office mandates are neither inherently right nor inherently wrong — they're a business decision with real trade-offs, and how well they land depends far less on the specific number of days chosen than on how thoughtfully the policy is designed, communicated, and applied. Indian employers navigating this in 2026 need to balance genuine business reasons — collaboration, mentorship, culture, real estate utilisation — against equally genuine employee needs around commute, caregiving, and flexibility. Getting the legal foundations right, building a real exceptions process, communicating with honesty about the "why," and rolling out changes in phases are what separate RTO mandates that stick from ones that trigger an exodus of good people.

None of this is easy to manage on spreadsheets and email threads. If your team is preparing for an RTO rollout, CozyHR's attendance tracking, geofencing, and policy management tools are built to help Indian HR teams track hybrid attendance accurately, manage exceptions consistently, and keep policy documentation up to date — all in one place. If you're planning a return-to-office transition this year, it's worth seeing how CozyHR can make the operational side of the rollout considerably easier.