Internal Job Posting (IJP) and Internal Mobility — Building a Policy That Works in India 2026

 

I've sat in enough leadership meetings to know the sentence that kills internal mobility before it starts: "Let's just find someone external, it's cleaner." It usually isn't cleaner — it's slower, more expensive, and it tells your best internal people that growth here means waiting for someone to notice you, not raising your hand. The organisations that get internal mobility right treat it as a retention strategy first and a recruitment channel second.

Internal Job Posting (IJP) is the practice of advertising open roles to existing employees before, or alongside, external recruitment, giving them a structured, transparent way to apply for growth opportunities within the organisation. Internal mobility is the broader practice this sits within — the deliberate movement of employees across roles, functions, and levels to develop them and retain their expertise, rather than losing it to external employers.

Why Internal Mobility Deserves Real Investment

Replacing a mid-level employee costs a significant multiple of their salary once recruitment, onboarding, and lost productivity are accounted for — a cost that internal moves largely avoid, since the employee already understands the organisation's systems, culture, and relationships. Beyond cost, employees who see genuine internal growth paths are measurably more likely to stay, and organisations with strong internal mobility practices consistently report lower attrition among their most capable people — the group most expensive and most damaging to lose.

Yet in many Indian organisations, internal mobility remains informal and inconsistent — dependent on whether a manager happens to know someone in another team, or whether an employee is confident enough to ask. That inconsistency quietly disadvantages employees who are excellent at their jobs but less visible or less networked.

Building an IJP Policy That's Genuinely Used

1. Define Which Roles Are Posted Internally

Decide the scope upfront: will all open roles be posted internally, or only roles above a certain level, or only within specific functions? Many organisations adopt a "post internally first" principle — giving internal candidates a window (commonly 5-10 working days) to apply before external recruitment opens, rather than running both simultaneously from day one.

2. Set Clear, Fair Eligibility Criteria

Common eligibility conditions include minimum tenure in the current role (commonly 12-18 months, to avoid destabilising teams with very frequent moves), a satisfactory performance rating, and no active disciplinary action. Whatever criteria you set, apply them consistently and publish them — informal, case-by-case eligibility decisions are where employees start to lose trust in the process.

3. Require Manager Notification, Not Manager Approval

This is where many IJP policies quietly fail. If an employee needs their current manager's approval before even applying, managers who don't want to lose a strong performer can block internal mobility entirely — invisibly, and often with the employee never learning why they didn't get the opportunity. Best practice is manager notification (the manager is informed the employee is applying) rather than manager approval (the manager can prevent the application). The hiring manager, not the losing manager, decides whether the employee is right for the new role.

4. Build a Fair, Consistent Selection Process

Internal candidates should go through a process with the same rigour as external candidates — structured interviews against defined criteria — rather than an informal conversation that can feel like a formality either way. This protects both the credibility of the process and the quality of the placement decision.

5. Give Genuine, Constructive Feedback to Unsuccessful Internal Candidates

An internal candidate who doesn't get the role, and receives no feedback on why, often disengages — sometimes more than they would after an unsuccessful external application, because the rejection feels closer to home. A short, honest feedback conversation, ideally including what development would strengthen a future application, turns a difficult moment into a retention opportunity rather than a trigger for the employee to start looking outside.

6. Manage the Transition Fairly

Define a reasonable handover period for the employee's current role and a clear transition timeline communicated to both the losing and gaining manager upfront. Ambiguity about "when exactly can they start" is one of the most common sources of friction between managers in internal moves, and poorly managed transitions create exactly the kind of manager resistance that discourages future postings.

The Manager Resistance Problem

The single biggest threat to a healthy internal mobility culture is managers who quietly discourage their best people from applying elsewhere internally, because they don't want to lose them. This is a completely understandable instinct and also one of the most corrosive things a manager can do to organisational trust. Address it directly:

• Make internal mobility a visible part of how managers themselves are evaluated — a manager whose team consistently loses good people to internal moves is doing something right, not something wrong, and should be recognised for developing talent that others want
• Equip managers with a standard process for backfilling a role quickly when a team member moves internally, reducing the operational pain that drives resistance
• Have senior leadership visibly model support for internal mobility — including moving their own strong performers into other parts of the organisation

Internal Mobility Beyond IJP

A mature internal mobility approach goes beyond reactive job postings to include proactive talent marketplaces (matching employees to stretch projects, not just permanent role changes), cross-functional rotation programmes for high-potential employees, and regular career conversations where managers proactively discuss internal growth options with their team — rather than employees only discovering opportunities when a posting happens to appear.

Internal Mobility and IJP — HR Checklist

• Scope of roles posted internally defined and communicated
• Post-internally-first window established before external recruitment opens
• Eligibility criteria set, published, and applied consistently
• Manager notification (not manager approval) process in place
• Structured, consistent selection process used for internal candidates
• Feedback process defined for unsuccessful internal applicants
• Fair transition and handover timelines agreed between losing and gaining managers
• Manager evaluation includes recognition for developing talent that moves internally

Frequently Asked Questions

Q: Should managers be able to block an employee from applying for an internal role? A: No — this is one of the most common ways internal mobility policies fail in practice. Managers should be notified when a direct report applies internally, but the decision to consider the candidate should sit with the hiring manager for the new role, based on fair selection criteria, not with the losing manager's willingness to let them go.

Q: How soon after joining should an employee be eligible to apply for an internal role? A: Most organisations set a minimum tenure of 12-18 months in the current role before internal mobility eligibility, to allow the employee to establish themselves and avoid excessive team disruption from very frequent moves. Exceptions can be built in for genuinely exceptional circumstances, with clear approval criteria.

Q: How do we prevent internal mobility from becoming a way for underperformers to escape a difficult manager relationship rather than genuinely grow? A: Tie eligibility to a satisfactory performance rating, and ensure the new hiring manager conducts a genuine, rigorous selection process rather than accepting an internal transfer at face value. A well-run selection process filters for genuine fit regardless of why the employee is seeking the move.

For internal mobility policy templates and HR documentation, visit our Stores and Services page.

Related reading: Talent Management Framework for Indian Organisations 2026 — Complete Guide

Related reading: Employee Referral Programme — How to Build One That Actually Works in India 2026

Compensation Benchmarking — How to Build a Fair Pay Structure in India 2026

 

I once inherited an organisation where compensation had been decided almost entirely by negotiation strength — the loudest, most confident negotiators earned meaningfully more than quieter colleagues doing identical work. Nobody had designed it that way deliberately. It happened because there was no structure, and where there's no structure, the gaps fill themselves in with whatever bias is present. Fixing it took over a year. Building it right the first time takes a fraction of that effort.

Compensation benchmarking is the process of comparing an organisation's pay levels against the external market to ensure they are competitive, while a pay structure is the internal framework — pay grades, bands, and progression logic — that ensures compensation is applied consistently and fairly within the organisation. Together, they determine whether an organisation can attract and retain talent, and whether it can defend its pay decisions as fair if ever challenged.

Why This Matters More Than Most HR Teams Treat It

Compensation is consistently one of the top reasons employees leave, and pay structure gaps are one of the most common sources of internal equity complaints and, increasingly, legal and regulatory scrutiny in India as pay transparency expectations rise. Yet many Indian organisations, particularly outside of large, mature companies, still set compensation informally — anchored to what the previous person in the role earned, what the candidate was able to negotiate, or rough guesswork about market rates.

Step 1: Conduct Market Benchmarking

Choose Reliable Data Sources

Salary survey providers (Mercer, Aon, Willis Towers Watson, and several India-focused providers) offer the most reliable benchmarking data, segmented by industry, function, level, and location. Job portals and informal salary-sharing platforms can supplement this but shouldn't be the primary source — self-reported data tends to skew toward more vocal, often more senior or specific-industry respondents.

Benchmark by Role, Not Just Title

Job titles vary enormously in scope across organisations — a "Senior Manager" in one company may be equivalent to a "Director" in another. Benchmark based on actual role scope, responsibility level, and impact, using a consistent job leveling framework, rather than matching titles directly.

Account for Location

Compensation for the same role varies significantly across Indian cities — Bengaluru, Mumbai, and Delhi NCR typically command a premium over Tier 2 cities for comparable roles, particularly in technology and financial services. Build location-adjusted benchmarks rather than a single national number, especially for organisations with a distributed workforce.

Decide Your Market Positioning

Most organisations don't aim to match the market exactly — they choose a deliberate positioning: below market (for organisations competing on other factors like stability, brand, or work-life balance), at market (the median or 50th percentile), or above market (typically the 75th percentile or higher, for organisations competing aggressively for scarce talent). Document this decision explicitly so pay decisions can be evaluated consistently against it.

Step 2: Build the Internal Pay Structure

Define Job Levels and Grades

Group roles into levels based on scope, complexity, and impact — not tenure or title alone. A clear leveling framework (often 6-10 levels for most mid-sized organisations) is the foundation everything else is built on.

Set Pay Bands for Each Level

For each level, define a minimum, midpoint, and maximum pay range, informed by your market benchmarking and chosen positioning. Bands should be wide enough to allow for experience and performance differentiation within a level, but not so wide that two people at very different points in the band are doing genuinely different work — if that's the case, the level itself may need to be split.

Manage Band Overlaps Deliberately

Some overlap between adjacent bands is normal and healthy — a highly experienced employee at one level may earn more than someone newly promoted to the next level. Excessive overlap, however, undermines the incentive to take on greater scope and responsibility, so review overlap percentages as part of your structure design.

Build in Progression Logic

Define how an employee moves through their pay band over time — typically through a combination of annual merit increases (based on performance) and market adjustments (based on updated benchmarking data). Keep the two separate and clearly communicated; conflating "you got a raise because the market moved" with "you got a raise because you performed well" confuses the signal to employees.

Step 3: Audit for Pay Equity

Once the structure is built, audit actual pay against it — by gender and other relevant dimensions, for employees at the same level doing comparable work. Unexplained gaps should be corrected as part of the structure rollout, not left to be "fixed gradually" through future increments, which rarely closes gaps as quickly or completely as a direct correction.

Step 4: Communicate and Govern

Decide How Much Transparency to Provide

Indian organisations vary widely in pay transparency practices — from full band disclosure to employees, to no disclosure of ranges at all. At minimum, most organisations benefit from communicating the existence of a structured framework and the logic behind increments, even without disclosing exact band figures, since this itself builds trust and reduces perceived arbitrariness.

Govern New Hire Offers Against the Structure

Without governance, new hire negotiations can quietly erode the structure — a strong external candidate negotiated in above the band undermines both internal equity and the credibility of the framework. Require sign-off for offers outside the defined band, with clear criteria for when an exception is genuinely justified.

Refresh Benchmarking Regularly

Market rates shift, sometimes quickly in high-demand functions like technology and data roles. Refresh external benchmarking at least annually, and more frequently for functions experiencing rapid market movement.

Compensation Benchmarking and Structure — HR Checklist

• Reliable market benchmarking data sourced by role, level, and location
• Market positioning (below/at/above market) explicitly decided and documented
• Job levels and grades defined based on scope and impact, not title or tenure
• Pay bands set for each level, with deliberate management of band overlap
• Progression logic (merit vs. market adjustment) defined and clearly communicated
• Pay equity audit conducted and unexplained gaps corrected
• Governance process in place for offers outside defined bands
• Benchmarking refresh scheduled at least annually

Frequently Asked Questions

Q: How often should we refresh our compensation benchmarking? A: At least once a year for most functions, and every six months for high-demand, fast-moving functions like technology, data science, and specialised sales roles, where market rates can shift meaningfully within a single year.

Q: Should we disclose pay bands to employees? A: There's no single right answer — it depends on organisational culture and readiness. Full transparency (sharing exact bands) builds trust but requires the underlying structure to be genuinely fair and well-governed, since any inconsistency becomes immediately visible. Partial transparency (communicating that a structured framework exists, without exact figures) is a reasonable middle ground for organisations building toward full transparency over time.

Q: What do we do if a valued current employee is being paid significantly below the new structure's band minimum? A: This is a common outcome when introducing structure to previously ungoverned pay. Correct it — ideally in a single adjustment rather than spreading it across several increment cycles, both because it's the fair outcome and because retention risk is highest for employees who discover, through the new structure, that they've been underpaid relative to peers.

For compensation structure templates and HR policy documentation, visit our Stores and Services page.

Related reading: HR Budgeting — How to Build an HR Budget for Indian Organisations 2026

Related reading: Talent Management Framework for Indian Organisations 2026 — Complete Guide

Data Privacy for HR — DPDP Act 2023 Compliance Guide for Indian HR Teams 2026

 

HR holds more sensitive personal data than almost any other function in an organisation — health records, salary details, disciplinary history, background verification reports, biometric attendance data, even bank account information. For years, most Indian HR teams handled this data carefully out of professional instinct, without a formal legal framework requiring it. That's changed. The Digital Personal Data Protection Act means data handling practices that were once just good practice are now legal obligations, with real penalties attached.

The Digital Personal Data Protection Act 2023 (DPDP Act) is India's comprehensive data protection law, establishing rules for how organisations collect, process, store, and share the personal data of individuals ("Data Principals"). HR functions, by the nature of their work, are among the heaviest processors of personal data in any organisation — making DPDP compliance a direct and significant HR responsibility, not just an IT or legal one.

What the DPDP Act Means for HR Specifically

Employee Data Is Personal Data

Names, contact details, salary information, PAN and Aadhaar numbers, bank details, performance records, health and medical information, biometric data (for attendance systems), disciplinary records, and background verification reports are all personal data under the Act. HR processes nearly all of these categories routinely.

The Employment Exemption — What It Covers and What It Doesn't

The DPDP Act includes a specific exemption allowing processing of employee personal data for employment-related purposes — safeguarding the employer from liability, provision of benefits, recruitment, and termination — without needing to obtain separate explicit consent for each processing activity. This is significant relief for standard HR operations. However, the exemption does not remove the underlying obligations around data security, purpose limitation, and data minimisation — it primarily addresses the consent requirement for legitimate employment purposes. Using employee data for purposes unrelated to employment (for example, sharing data with unrelated third parties or using it for purposes the employee wouldn't reasonably expect) falls outside the exemption's protection.

Consent and Notice for Non-Employment Purposes

For any HR data processing that goes beyond core employment purposes — marketing communications to former employees, sharing data with unrelated third-party vendors, or use in ways not reasonably connected to employment — standard consent and notice requirements under the Act apply.

Practical DPDP Compliance Steps for HR

1. Map What Personal Data HR Actually Holds

Before anything else, inventory the personal data HR collects and processes — recruitment data, employee master data, payroll data, performance data, health data, biometric attendance data, background verification reports, exit data. Identify where each category is stored, who has access, and how long it's retained.

2. Apply Purpose Limitation

Collect and use data only for the specific purpose it was gathered for. A common gap: biometric attendance data collected for time tracking being repurposed for other analytics without a clear connection to the original purpose. Review current practices for this kind of scope creep.

3. Build Data Minimisation Into HR Processes

Don't collect data "just in case it's useful later." Review recruitment application forms, background verification scope, and onboarding data collection for fields that aren't genuinely necessary. Excess data collection increases both compliance exposure and breach impact without adding value.

4. Secure Third-Party Data Sharing

HR routinely shares employee data with external parties — payroll processors, background verification agencies, insurance providers, HRMS vendors, recruitment agencies. Ensure data processing agreements are in place with each vendor, specifying purpose limitation, security obligations, and breach notification requirements. The employer remains accountable for how these processors handle the data, not just the vendor.

5. Define Retention and Deletion Practices

Personal data should not be retained indefinitely "just in case." Define retention periods for each category of HR data — recruitment data for unsuccessful candidates, exited employee records, performance history — based on legal requirements (many statutory records must be retained for specific periods) and genuine business need. Build a deletion process for data that has passed its retention period.

6. Prepare for Data Principal Rights Requests

Employees, as Data Principals, have rights under the Act including the right to access their personal data and, in some circumstances, correction and erasure. Build a process for HR to respond to these requests within statutory timelines — this typically requires coordination between HR, IT, and any relevant vendors holding employee data.

7. Have a Breach Response Plan

If HR systems holding personal data are breached, the Act requires notification to the Data Protection Board and, in significant cases, to affected individuals. HR should be part of the incident response plan — not informed after the fact — since HR data is often among the most sensitive data an organisation holds.

8. Train HR Teams Specifically

General organisational data privacy training doesn't cover the specific scenarios HR teams face daily — handling background verification reports, sharing performance data in calibration discussions, storing health information from medical leave requests. Build HR-specific data handling guidance into onboarding for HR team members themselves.

Where DPDP Intersects With Other HR Compliance Areas

Data privacy considerations now touch nearly every HR process — recruitment (candidate data), performance management (appraisal data shared in calibration), workplace mental health support (health disclosures, which require particular care given their sensitivity), and HR due diligence during M&A (transfer of large volumes of employee data between organisations). Building DPDP awareness into these existing processes is more effective than treating data privacy as a separate, standalone initiative.

DPDP Compliance — HR Checklist

• Personal data inventory completed across recruitment, employee master, payroll, performance, and health data
• Purpose limitation reviewed for each category of data collected
• Data collection forms reviewed for unnecessary fields
• Data processing agreements in place with all third-party vendors handling employee data
• Retention and deletion schedule defined for each data category
• Process in place for responding to employee data access and correction requests
• HR included in the organisation's data breach response plan
• HR-specific data privacy training delivered to the HR team

Frequently Asked Questions

Q: Do we need separate consent from every employee to process their HR data? A: For core employment purposes — payroll, benefits, performance management, safeguarding against misconduct — the DPDP Act's employment exemption generally removes the need for specific consent. For processing outside these core purposes, standard consent requirements apply. When in doubt, apply purpose limitation carefully and seek legal advice on borderline cases.

Q: How long can we retain data on candidates who weren't hired? A: There's no single fixed period specified for all candidate data under the Act. Best practice is to define a reasonable retention period (commonly 6-12 months) based on genuine business need — for example, considering candidates for future roles — and delete data beyond that unless the candidate has separately consented to longer retention.

Q: What happens if our background verification or payroll vendor has a data breach? A: The employer typically remains accountable to affected employees even when a third-party processor causes the breach, which is why data processing agreements with clear security and breach notification obligations are essential. Review vendor contracts to ensure they include these obligations and specify vendor liability.

For HR policy documentation and data privacy compliance templates, visit our Stores and Services page.

Related reading: Workplace Mental Health Policy India 2026 — A Complete Guide for HR

Related reading: HR Due Diligence in Mergers and Acquisitions India 2026 — Complete Guide

Exit Interview Process — How to Run One That Actually Generates Insight (India 2026)

 

For years, exit interviews at most places I've worked were a formality — a form emailed to the departing employee, filled in half-heartedly, filed away, and never looked at again. The turning point for me was realising that exit interview data, taken seriously and analysed properly, was consistently more honest than our engagement surveys. People who are already leaving have nothing left to lose by being candid — if you actually create the conditions for candour.

An exit interview is a structured conversation or survey conducted with a departing employee to understand why they're leaving, what their experience of the organisation was, and what could be improved. Done well, it's one of the richest sources of honest organisational feedback HR has access to. Done as a compliance formality, it generates data nobody trusts and nobody uses.

Why Most Exit Interviews Fail to Generate Real Insight

• Timing is wrong — conducted on the employee's last day, when they're mentally already gone and unwilling to invest energy in candid feedback
• The wrong person conducts it — the departing employee's own manager, who is often the reason they're leaving, is the worst-placed person to hear honest feedback
• No real anonymity or safety — employees fear that critical feedback could affect their reference, final settlement, or reputation in a small industry
• Data isn't analysed — responses are collected and filed, with no aggregation, trend analysis, or action taken
• Generic questions — a standard form with no follow-up misses the specific, actionable detail that makes exit feedback useful

Building an Exit Interview Process That Works

1. Time It Right

Conduct the exit interview roughly a week before the employee's last day — after the decision to leave is settled and emotions around the notice period conversation have calmed, but before the employee has mentally checked out entirely. Conducting it on the very last day typically produces the most guarded, least useful responses.

2. Choose the Right Interviewer

HR — not the departing employee's direct manager — should conduct the exit interview. A skip-level manager or a neutral HR business partner who wasn't closely involved in day-to-day management gets more candid responses than someone the employee may hold responsible for their decision to leave.

3. Combine a Survey With a Conversation

A structured survey ensures consistent, comparable data across all exits — useful for trend analysis. A follow-up conversation allows for the specific, contextual detail that a form alone misses. The best exit interview processes use both: a short survey completed independently, followed by a 30-45 minute conversation.

4. Ask the Right Questions

Move beyond "why are you leaving" to more specific, actionable questions:

• What was the primary reason you started looking for another opportunity?
• Was there a specific moment or event that triggered your decision to leave?
• How would you describe your relationship with your manager?
• Did you feel you had a clear path for growth here? If not, what was missing?
• Was your compensation competitive relative to what you're moving to?
• What would have needed to change for you to stay?
• Would you recommend this organisation to a friend as a place to work? Why or why not?

5. Protect Confidentiality — and Say So Explicitly

Tell the employee explicitly how their feedback will be used — typically aggregated and anonymised for trend reporting, with specific, attributable feedback shared with leadership only with the employee's consent, or only after enough time has passed that it can't be traced back to them. Employees who don't trust the confidentiality of the process will give you the version of the truth that's safe, not the version that's useful.

6. Actually Analyse the Data

Exit interview data is only valuable in aggregate. Track reasons for leaving by department, manager, tenure, and level over time. A single exit citing "poor management" is an anecdote. Five exits from the same manager's team citing similar concerns within six months is a pattern that needs intervention — and exit data is often the earliest reliable signal of a manager problem, well before it shows up in engagement survey scores.

7. Close the Loop

Share aggregated, anonymised exit trends with senior leadership regularly — quarterly is a reasonable cadence for most organisations. Where a clear, addressable pattern emerges (a specific team, a specific policy, a specific stage in the employee lifecycle), take visible action and — where appropriate — communicate that action back to the organisation. Exit data that never visibly changes anything trains future departing employees to not bother being honest either.

What to Do With Difficult Feedback

Not all exit feedback will be fair or fully accurate — departing employees sometimes rationalise their decision in ways that aren't the complete picture. Treat individual exit feedback as one data point, not gospel, but take patterns across multiple exits seriously even when they're uncomfortable to hear, particularly when they point to a specific manager or team.

Exit Interview Process — HR Checklist

• Exit interview scheduled roughly one week before the last working day, not on the final day
• Conducted by HR or a skip-level manager, not the departing employee's direct manager
• Combines a structured survey with a follow-up conversation
• Questions go beyond "why are you leaving" to specific, actionable detail
• Confidentiality approach explained clearly to the employee before the conversation
• Data tracked and aggregated by department, manager, tenure, and level over time
• Trends reviewed with leadership on a regular cadence
• Clear examples of action taken based on exit feedback, communicated where appropriate

Frequently Asked Questions

Q: Should exit interviews be mandatory? A: Strongly encouraged rather than strictly mandatory. Employees who are compelled to participate against their wishes tend to give guarded, low-value responses. A genuinely voluntary process, framed as an opportunity to be heard rather than an obligation, generally produces more honest and useful feedback.

Q: What if an employee is leaving on bad terms — is an exit interview still worth doing? A: Often especially worth doing. Employees leaving on difficult terms sometimes provide the most candid — if emotionally charged — feedback about underlying issues. Approach these conversations with genuine curiosity rather than defensiveness, and separate the emotional tone of the feedback from the substance of what's being said.

Q: How is an exit interview different from a stay interview? A: A stay interview is conducted with current, engaged employees to understand what's working and proactively address retention risks before someone decides to leave. An exit interview happens after the decision is already made. Organisations with mature retention practices use both — stay interviews to prevent departures, exit interviews to understand the ones that happen anyway.

For exit process documentation and HR policy templates, visit our Stores and Services page.

Related reading: Notice Period Rules India 2026

Related reading: Full and Final Settlement in India 2026 — Complete HR Guide

Gig and Platform Worker Compliance in India 2026 — What HR Must Know

 

A few years ago, "gig worker" meant delivery riders and cab drivers in most HR conversations. That's changed fast. I now see gig arrangements used for content creation, specialised consulting, sales overlays, and short-term project work across industries that never touched the gig economy before. The compliance framework has changed to catch up — and a lot of HR teams haven't caught up with the compliance framework yet.

Gig and platform workers are individuals who earn income outside a traditional employer-employee relationship, typically engaged through digital platforms or on a project/assignment basis. India's Social Security Code 2020 formally recognised this category for the first time, creating specific obligations for organisations that engage them — obligations that are distinct from both regular employment and traditional contract labour.

Defining the Categories Correctly

Getting the classification right matters because the compliance obligations differ significantly:

• Gig worker: A person who performs work outside a traditional employer-employee relationship and earns from such activities, as defined under the Social Security Code 2020.
• Platform worker: A subset of gig workers whose work is facilitated through an online platform — the platform connects them with customers or clients for a fee.
• Independent contractor / consultant: An individual engaged for a specific deliverable or expertise, typically on a service agreement, outside the gig/platform framework entirely.
• Contract labour: Workers supplied through a licensed contractor under the Contract Labour Act — a distinct and older framework with its own compliance regime.

Misclassifying an employee as a gig worker or independent contractor to avoid statutory obligations is one of the highest-risk compliance areas in Indian HR today, and it's coming under increasing scrutiny.

What the Social Security Code 2020 Requires

The Code, once fully notified and operational across states, requires:

• Aggregator contribution: Platforms and aggregators engaging gig and platform workers must contribute 1-2% of their annual turnover (subject to a cap of 5% of the amount paid to gig and platform workers) toward a social security fund.
• Registration: Gig and platform workers must be registered on the government's designated portal to access social security benefits.
• Social security schemes: Benefits potentially available include life and disability cover, accident insurance, health and maternity benefits, old age protection, and creche facilities — implemented through schemes notified by central and state governments.
• Welfare boards: State governments can set up welfare boards specifically for gig and platform workers to administer benefits and grievance mechanisms.

Implementation timelines and specific scheme details vary by state, and organisations engaging gig workers at scale should track state-level notifications closely rather than assuming a single national rollout date.

Practical Compliance Steps for HR

1. Get the Classification Right, Documented

For every non-traditional work arrangement, document why the person is classified as they are — gig worker, platform worker, independent contractor, or employee. Base this on the actual nature of the relationship (control over how work is performed, exclusivity, integration into core operations, provision of tools and equipment) rather than what the contract label says. Courts and authorities look at substance over form.

2. Avoid the Misclassification Trap

The clearest red flags for misclassification are: fixed working hours dictated by the organisation, work that is core and perennial rather than project-based, exclusivity requirements preventing the person from working elsewhere, and day-to-day supervision indistinguishable from how employees are managed. If several of these apply, the arrangement is at real risk of being reclassified as employment — with significant retrospective liability for PF, ESI, and other benefits.

3. Build Fair Engagement Terms Even Where Not Legally Mandated

Even before every provision of the Social Security Code is fully operational in your state, building fair terms into gig worker engagement — transparent payment terms, reasonable notice for termination of engagement, a basic grievance mechanism — reduces both reputational risk and the likelihood of disputes escalating to legal claims of misclassification.

4. Track State-Level Notifications

Because the Social Security Code's gig worker provisions are being operationalised progressively by state, organisations engaging gig or platform workers across multiple states need a tracking mechanism for which obligations are live in which state, rather than a single national compliance date.

5. Prepare for Aggregator Contribution Obligations

If your organisation operates a platform that engages gig workers directly (rather than simply contracting with an intermediary), budget and prepare for the aggregator social security contribution obligation as state schemes come into force.

Where This Intersects With Existing HR Processes

Organisations that use freelancers, project consultants, or platform-sourced talent alongside traditional contract labour should review all three categories together — the boundaries between contract labour, gig work, and independent contracting are not always intuitive, and a workforce audit that only looks at one category can miss significant exposure in the others.

Gig and Platform Worker Compliance — HR Checklist

• All non-traditional work arrangements classified and documented with clear rationale
• Classification reviewed against actual working conditions, not just contract language
• Misclassification risk assessed for arrangements with fixed hours, exclusivity, or core/perennial work
• State-level Social Security Code notifications tracked for every state of operation
• Fair engagement terms (payment, notice, grievance mechanism) built into gig worker contracts
• Aggregator contribution obligations assessed if your organisation operates a platform
• Gig worker registration and benefit access processes reviewed where schemes are live

Frequently Asked Questions

Q: Is a gig worker entitled to PF and ESI like a regular employee? A: No — gig and platform workers are covered under the Social Security Code's separate framework for gig workers, not the standard PF and ESI schemes that apply to employees. However, if a gig worker is later found to actually be functioning as an employee based on the real nature of the relationship, standard employee benefit obligations can apply retrospectively.

Q: Can we engage a former employee as a gig worker or consultant immediately after they resign? A: This is high-risk if the working relationship remains effectively unchanged — same hours, same supervision, same core duties. Authorities view this pattern as a classic misclassification red flag. If genuinely engaging them for project-based or advisory work with real independence, document the change in the nature of the relationship clearly.

Q: Do platform aggregators need to register with the government? A: Yes, under the Social Security Code framework, aggregators engaging gig and platform workers are expected to register and contribute to the social security fund as state schemes come into force. Requirements and timelines vary by state and by the specific scheme notified.

For HR policy documentation and workforce classification support, visit our Stores and Services page.

Related reading: Contract Labour Management in India 2026 — Complete Compliance Guide for HR

Related reading: New Labour Codes India 2026 — What Every HR Professional Must Know

The 90-Day Employee Onboarding Program — A Complete Guide for Indian HR Teams 2026

I once tracked exit interview data across two years at a previous organisation and found something uncomfortable: nearly a third of voluntary attrition happened within the first six months. Almost none of those employees left because of compensation. They left because nobody had a plan for their first ninety days, and they quietly concluded the organisation didn't either. Onboarding is not orientation. Orientation is a day. Onboarding is a programme.

Onboarding is the structured process of integrating a new employee into the organisation — covering role clarity, relationship building, cultural integration, and early productivity. Most Indian organisations still treat onboarding as a one- or two-day induction covering policies, IT setup, and paperwork. That covers compliance, not onboarding. A genuine onboarding programme runs for the first 90 days and is designed to get a new hire to full productivity and genuine belonging as quickly as possible.

Why the First 90 Days Matter So Much

New hire attrition in the first six months is expensive and highly preventable — it represents a sunk cost in recruitment with almost no return, and it often signals a process failure rather than a hiring mistake. Beyond retention, the speed at which a new employee reaches full productivity directly affects team output, and a new hire's early experience shapes how they describe the organisation to their network for years afterward — good or bad.

The Three Phases of Onboarding

Phase 1 — Pre-Boarding (Offer Acceptance to Day 1)

The period between offer acceptance and the start date is often ignored, and it's exactly when a competing offer or counter-offer is most likely to pull a candidate away. Use this window actively:

• Send a welcome communication within 48 hours of offer acceptance
• Share practical joining information early — reporting time, location, dress code, documents required
• Introduce the new hire to their manager and one or two future teammates before Day 1, even briefly
• Complete background verification and documentation well before the start date, not on it
• Ship any equipment (laptop, ID card, access credentials) so it's ready on arrival

Phase 2 — First Week (Structure and Clarity)

The first week should establish role clarity, basic systems access, and early relationships — not just compliance paperwork.

• A structured Day 1 agenda — not a full day of HR forms with nothing else planned
• Manager one-on-one within the first two days, covering role expectations, immediate priorities, and how success will be measured in the first 30/60/90 days
• Introductions to key stakeholders and cross-functional partners, not just the immediate team
• Systems and tools access working from Day 1 — nothing kills early momentum like a new hire unable to log in for three days
• A named onboarding buddy — a peer (not the manager) the new hire can ask "obvious" questions without hesitation

Phase 3 — First 90 Days (Integration and Early Wins)

This is where most onboarding programmes fall short, because they stop at the first week.

• 30 days: Role fundamentals understood, key relationships established, first small deliverable completed
• 60 days: Operating with growing independence, contributing meaningfully to team objectives, feedback given and received at least once formally
• 90 days: Fully integrated, contributing at expected level, clear on career path and development expectations within the organisation

Schedule formal check-ins at each milestone — not just an informal "how's it going" but a structured conversation covering role clarity, relationship quality, and any obstacles.

Building the Onboarding Programme

Assign Clear Ownership

Onboarding fails when everyone assumes someone else owns it. HR typically owns policy, compliance, and the programme framework. The hiring manager owns role clarity, goal-setting, and performance feedback. The onboarding buddy owns informal cultural integration. Make this explicit — a RACI for onboarding responsibilities is a simple, effective tool.

Personalise by Role and Level

A graduate trainee, a lateral mid-level hire, and a senior leader need very different onboarding journeys. Senior hires in particular are often under-onboarded because organisations assume seniority means they'll figure it out — but senior hires who fail typically fail due to political and cultural misreads, not skill gaps, and a structured stakeholder mapping and relationship-building plan in the first 90 days significantly reduces that risk.

Use Technology Without Losing the Human Element

HRMS-driven onboarding workflows (document collection, task checklists, e-signatures) remove administrative friction and free up time for the parts of onboarding that actually require human interaction — manager conversations, team integration, and culture. Automate the paperwork; don't automate the relationship-building.

Collect Feedback and Iterate

Run a short onboarding experience survey at 30 and 90 days. Ask what worked, what was unclear, and what they wish they'd known earlier. New hires give the most honest, useful feedback about onboarding gaps precisely because they're experiencing the process for the first time and haven't yet become numb to its shortcomings.

Common Onboarding Mistakes

• Treating onboarding as a single Day 1 event rather than a 90-day programme
• No manager involvement beyond the first meeting
• New hire unable to access systems or tools in the first week
• No defined success criteria for the first 30/60/90 days, leaving the new hire guessing at expectations
• Identical onboarding journey for every role and level, regardless of seniority or function

Onboarding Programme — HR Checklist

• Pre-boarding communication plan in place, starting within 48 hours of offer acceptance
• Equipment, access, and documentation ready before Day 1
• Structured first-week agenda designed, including manager one-on-one
• Onboarding buddy assigned for every new hire
• 30/60/90-day milestones and success criteria defined by role
• Ownership for each phase of onboarding clearly assigned
• Feedback collected at 30 and 90 days and used to improve the programme

Frequently Asked Questions

Q: How long should a formal onboarding programme run? A: Most effective programmes run for 90 days, with the most intensive structure in the first 30. Some organisations extend light-touch check-ins to six months or a full year for senior or critical roles, where cultural integration takes longer.

Q: Who should be the onboarding buddy — a peer or the manager? A: A peer, ideally in a similar role or team, but not the direct manager. New hires are often reluctant to ask their manager "basic" questions for fear of appearing unprepared; a peer buddy removes that hesitation and provides informal cultural context a manager may not think to share.

Q: How do we onboard effectively for remote or hybrid new hires? A: The same 90-day structure applies, but deliberate effort is needed to replace the informal relationship-building that happens naturally in an office. Schedule more frequent, shorter virtual check-ins, actively facilitate introductions rather than relying on hallway encounters, and consider bringing remote new hires on-site for at least the first week if operationally feasible.

For onboarding templates, induction checklists, and HR policy documentation, visit our Stores and Services page.

Related reading: Employee Referral Programme — How to Build One That Actually Works in India 2026

Related reading: HRMS Selection Guide 

Diversity, Equity and Inclusion (DEI) in Indian Workplaces 2026 — A Practical Guide for HR

Early in my career, I sat in a leadership meeting where someone asked why we needed a DEI programme when "we hire the best person for the job anyway." That question, asked in good faith, is exactly why DEI programmes exist — because "the best person" is judged through filters we don't always notice we're applying. Ten years on, the organisations getting DEI right in India aren't the ones with the most polished mission statements. They're the ones that changed how they hire, promote, and pay.

Diversity, Equity and Inclusion refers to the practices an organisation puts in place to build a workforce that reflects a range of backgrounds (diversity), ensure fair access to opportunity regardless of background (equity), and create a workplace where every employee feels genuinely able to contribute and belong (inclusion). In India, DEI has moved from a nice-to-have reputational initiative to a genuine business and talent priority — but it remains one of the most inconsistently implemented areas of Indian HR.

Why DEI Matters for Indian Organisations Specifically

India's workforce diversity challenges are distinct from those in Western markets. The most significant gaps in Indian organisations are typically:

• Gender representation, particularly in senior and technical roles — women's labour force participation and progression to leadership remain well below population parity in most sectors
• Regional and linguistic diversity, especially in organisations concentrated in a few metro hubs
• Disability inclusion, where accessibility and hiring practices lag significantly behind stated intent
• Socioeconomic and educational background, where hiring practices that favour a narrow set of premier institutes can quietly exclude strong candidates from other backgrounds
• LGBTQ+ inclusion, an area many Indian organisations are still building policy and practice around

A credible DEI strategy addresses the gaps that are actually present in your organisation's data — not a generic template borrowed from a global parent company's programme.

Building a DEI Strategy That Isn't Just Optics

1. Start With Data, Not Intentions

Before setting any DEI goals, understand your current state: representation by gender, level, and function; pay equity by gender and other relevant dimensions; attrition rates by group; promotion rates by group. Without this baseline, DEI goals are guesses, and progress can't be measured credibly.

2. Fix Hiring Before Fixing Culture

Representation problems are often hiring problems in disguise. Common issues include job descriptions with unnecessarily exclusionary requirements, sourcing that relies on a narrow set of channels or referrals (which tend to replicate the existing workforce), and interview panels that lack diversity themselves. Structured interviews with standardised, job-relevant criteria reduce the influence of unconscious bias significantly more than sensitivity training alone.

3. Address Pay Equity Directly

Conduct a pay equity audit — comparing compensation for employees in similar roles, levels, and experience across gender and other relevant groups. Where unexplained gaps exist, correct them. Pay equity is one of the few DEI metrics that is entirely within HR's control to fix directly, and it sends a stronger signal than almost any other initiative.

4. Build Genuinely Flexible Policies

Policies that assume a single "default" employee — able-bodied, without caregiving responsibilities, comfortable with long in-office hours — quietly exclude people who don't fit that mould. Review leave policies, work-from-home eligibility, facilities, and even meeting scheduling norms for whether they work for everyone or only for some.

5. Train Managers, Not Just Employees

Generic DEI awareness sessions for the whole workforce have limited impact on their own. The highest-leverage training is for managers — on how to run fair performance conversations, how to interrupt bias in calibration discussions, and how to build genuinely inclusive team norms. Managers make the day-to-day decisions that determine whether DEI intent translates into DEI outcomes.

6. Set Accountable Goals

DEI goals should be specific, time-bound, and owned by business leaders — not just HR. "Increase women in engineering leadership from 12% to 20% over three years, with quarterly progress reviewed by the CTO" is accountable. A generic statement of commitment to diversity is not.

Common Pitfalls

• Treating DEI as a communications exercise — a policy document and a few social media posts, with no change to hiring or promotion practices
• Setting representation targets without addressing the pipeline or retention issues that caused the gap in the first place
• Running one-off training with no reinforcement or manager accountability
• Measuring only hiring diversity while ignoring promotion and attrition data, which often tell a very different story
• Importing a DEI framework wholesale from a global headquarters without adapting it to India-specific diversity dimensions

DEI Implementation — HR Checklist

• Baseline representation, pay equity, and attrition data collected and analysed by group
• Hiring process reviewed for exclusionary requirements and panel diversity
• Pay equity audit conducted, with corrective action plan for identified gaps
• Leave, flexibility, and facilities policies reviewed for inclusivity
• Manager training on fair performance and calibration practices delivered
• Specific, time-bound DEI goals set and owned by business leaders
• Progress reviewed at least twice a year, with data shared transparently within the organisation

Frequently Asked Questions

Q: Are diversity hiring quotas legal in India for private employers? A: Private employers can set voluntary internal diversity goals and targets, but these must operate within the framework of the Equal Remuneration Act and broader non-discrimination principles — meaning selection should still be based on merit within a deliberately widened and fairer pool, not a rigid quota that displaces qualified candidates. Public sector reservation rules are a separate legal framework and do not apply to private employers in the same way.

Q: How do we measure whether our DEI programme is actually working? A: Track representation trends over time (not just a single snapshot), promotion rates by group relative to representation, voluntary attrition by group, and pay equity year over year. An improving hiring number alongside flat or worsening promotion and retention numbers usually means the programme is only working at the entry point, not throughout the employee lifecycle.

Q: What's the difference between diversity and inclusion in practice? A: Diversity is about who is in the room — representation across dimensions like gender, background, and ability. Inclusion is about whether everyone in the room has genuine influence, opportunity, and psychological safety. An organisation can be diverse without being inclusive — hiring a varied workforce that then experiences unequal access to opportunity, mentorship, or voice.

For HR policy templates and inclusive hiring documentation, visit our Stores and Services page.

Related reading: Workplace Mental Health Policy India 2026 — A Complete Guide for HR

Related reading: HR Due Diligence in Mergers and Acquisitions India 2026 — Complete Guide