The legal framework for remote employees in India
India does not yet have a dedicated remote work legislation, which means employers must navigate existing labour laws that were designed for traditional office-based employment. The primary legal framework governing employment conditions — including working hours, leave entitlements, and establishment registration — is the Shops and Establishments Act, which is a state-level legislation. Each Indian state has its own version of this Act, and the rules vary significantly. The critical question for remote employers is: which state's Shops and Establishments Act applies when an employee works from home in a different state than where the company is registered? The emerging legal consensus, supported by several state labour department advisories, is that the Act of the state where the employee is physically located applies.
This has practical implications. If your company is registered in Karnataka but you hire a remote employee working from Maharashtra, you may need to obtain a separate Shops and Establishments registration in Maharashtra or ensure that your existing registration covers employees in that state. Some states (like Karnataka and Telangana) have amended their Acts to recognise remote work arrangements, while others have not explicitly addressed the issue. The safest approach is to register in every state where you have employees, maintain records of each employee's work location, and comply with the most protective provisions when there is ambiguity. For companies scaling remote hiring rapidly, this state-by-state compliance requirement is one of the most operationally demanding aspects of distributed workforce management.
PF and ESI compliance for multi-state remote teams
Provident Fund compliance for remote employees is relatively straightforward because EPF is a central legislation with uniform rules across states. The employer's PF registration covers all employees regardless of their physical location, and contributions are remitted to a single EPFO regional office based on the company's registered address. However, if the company has separate establishments or branches registered in different states, each establishment may have its own PF code, and employees should be mapped to the correct establishment for contribution purposes. For remote employees who do not physically report to any office, they are typically mapped to the head office or the establishment where their reporting manager is based.
ESI (Employees' State Insurance) compliance is more complex because ESI is administered at the state level with regional offices. The ESI Act applies to employees earning up to ₹21,000 per month in gross salary. For remote employees, the employer needs to register with the ESI office in the state where the employee is located, because ESI benefits (medical treatment, sickness benefits) are delivered through dispensaries and hospitals in the employee's area. This means a company with remote employees across five states might need ESI registrations in all five states. The employer's contribution rate (3.25% of wages) and employee contribution rate (0.75%) remain the same regardless of the state. Practically, many remote employees in the tech industry earn above the ESI threshold and are not covered, but companies hiring remote employees in operational roles, customer support, or entry-level positions need to address this compliance requirement proactively.
Employment contracts and policy modifications for remote work
Standard employment contracts drafted for office-based work need significant modifications for remote employees. Key clauses to add or update include: work location (specifying the employee's home address as the designated workplace and requiring advance notice for any change in location), working hours and availability (defining core hours during which the employee must be reachable, while respecting the state-specific rules on maximum working hours and overtime), equipment and infrastructure (clarifying who provides and maintains the laptop, monitor, internet connection, and ergonomic furniture), expense reimbursement (covering internet costs, electricity, and home office setup — many companies offer a monthly work-from-home allowance of ₹2,000-5,000), and data security obligations (especially important under the DPDP Act).
The contract should also address intellectual property, confidentiality in a home environment (for example, restrictions on working from public spaces when handling sensitive data), and the employer's right to recall the employee to the office if business needs change. Include a clause specifying which state's labour laws govern the employment relationship — this is important for dispute resolution. Many companies also draft a separate Remote Work Policy that covers day-to-day expectations: video call etiquette, response time standards, mandatory in-person meetings (if any), and performance evaluation methods. This policy should be acknowledged by the employee in writing. For Indian companies, it is also advisable to include clauses about professional tax deduction (which varies by state and is levied based on the employee's work location, not the employer's registered state) and whether the company will assist with state-specific tax registrations.
Data security and DPDP Act compliance for remote workers
Remote work introduces additional data security considerations that are amplified by the Digital Personal Data Protection Act, 2023. When employees access personal data of candidates, customers, or other employees from their home networks, the risk surface expands significantly compared to a controlled office environment with managed firewalls and network monitoring. Under the DPDP Act, the employer as Data Fiduciary must implement "reasonable security safeguards" for personal data — and this obligation extends to data accessed by remote employees. Practically, this means enforcing VPN usage for all work-related access, implementing endpoint security software on employee devices, enabling multi-factor authentication for all systems containing personal data, and establishing clear policies on data storage (no personal data on local drives, no screenshots of sensitive information, no use of personal email for work communications).
Consent management also has a remote work dimension. If remote employees are conducting video interviews with candidates, recording those interviews for evaluation purposes, or using AI tools to assess candidate responses, the DPDP Act requires that candidates are informed about the specific data processing activities and provide consent. The consent notice should mention that the interview is being conducted remotely, that recordings may be stored on cloud platforms, and that AI tools may process the conversation. Companies should audit their remote work tool stack for DPDP compliance — collaboration tools, video conferencing platforms, and cloud storage services all process personal data and should have appropriate data processing agreements in place. Recruitment platforms like Workro handle much of this complexity by centralising candidate data processing with built-in consent management, audit trails, and access controls that work regardless of whether the HR team member is in the office or working remotely.
Practical tips for remote interviews and onboarding
Remote interviewing requires deliberate process design to match the effectiveness of in-person interviews. Start with the technical basics: ensure the video platform works reliably, test the candidate's connectivity before the scheduled interview (a brief five-minute pre-check call eliminates most technical disruptions), and have a backup plan (phone interview) if video fails. Structure the interview with clear time blocks — introduction (5 minutes), behavioural questions (15 minutes), technical assessment (20 minutes), candidate questions (10 minutes) — and communicate this structure to the candidate upfront. Use a standardised evaluation rubric that all interviewers complete immediately after the interview, while impressions are fresh. For technical roles, use collaborative coding platforms or screen-sharing for live problem-solving rather than relying solely on verbal descriptions of past work.
Remote onboarding demands even more structure than in-office onboarding because the new hire lacks the ambient learning that happens naturally in a physical workspace. Ship equipment well before the joining date — a new hire staring at a blank screen on Day 1 because the laptop was dispatched late is a terrible first impression. Schedule virtual onboarding sessions across the first week rather than cramming everything into Day 1. Assign a buddy who is available for quick video calls throughout the first month. Create a detailed onboarding document that the new hire can reference independently — covering tool access, team structure, key contacts, and common workflows. Schedule daily 15-minute check-ins with the hiring manager for the first two weeks, tapering to weekly after that. Workro's AI interview system is particularly valuable for remote hiring because it provides a consistent, structured assessment experience regardless of the interviewer's or candidate's location, eliminating the variability that often creeps into remote interview processes.