Solutions

The 90-day notice period is costing India ~$6B a year. Here's how to fix it.

Every year, hundreds of thousands of Indian professionals accept job offers and then disappear before their join date. The culprit is a 90-day notice period that creates a three-month vacuum between "yes" and "day one" — a window where counter-offers land, competing recruiters circle, and candidates silently re-evaluate their decisions. The result is a systemic, industry-wide problem that costs Indian employers an estimated $6 billion annually in wasted hiring spend, lost productivity, and restarted searches. This page breaks down why the problem exists, what it actually costs, and what companies can do about it today.

Why the 90-day window exists

Contrary to popular belief, there is no Indian labor law that mandates a 90-day notice period. The Industrial Disputes Act of 1947 and the Industrial Employment (Standing Orders) Act set out notice requirements for workmen and factory employees, but these typically range from 30 days to three months depending on the category. For white-collar professionals in IT, consulting, BFSI, and management roles, the notice period is purely a contractual obligation written into the employment agreement.

The 90-day norm became entrenched in the Indian IT services industry during the rapid growth years of the 2000s. Companies like Infosys, TCS, and Wipro handled projects with thin bench strength and needed long notice periods to backfill roles, complete knowledge transfer, and transition client relationships without disruption. A departing engineer working on a banking client's core system might need four to six weeks just to document their work and hand over to a replacement.

Over time, what started as a practical measure for services companies became an industry-wide default. Product companies adopted it. Startups adopted it. Even companies with strong bench strength and minimal knowledge transfer requirements imposed 90-day clauses simply because "everyone else does." The result is a contractual norm that persists across the Indian white-collar economy — not because of legal necessity, but because of institutional inertia and the genuine (if often overstated) need for orderly transitions.

The irony is that the very mechanism designed to ensure stability has become the primary source of instability in Indian hiring. Those 90 days create a window of vulnerability that neither the current employer nor the future employer is equipped to manage.

What actually happens during those 90 days

Once a professional submits their resignation, a predictable sequence of events unfolds — and almost none of it favors the company that made the offer.

The counter-offer barrage begins within 48 hours. The current employer, now alerted to the resignation, escalates to the reporting manager, then to HR, then to the business head. In competitive roles — data engineering, full-stack development, product management — candidates routinely receive two to five counter-offers within the first two weeks. These are not token gestures. They often include 20-40% salary hikes, accelerated promotions, team changes, or relocation flexibility that the employee had been requesting for months without success.

Competing recruiters intensify their outreach. The moment a candidate updates their LinkedIn status or word travels through professional networks, external recruiters make contact. A candidate who was passively open to one opportunity now receives three to four additional interview requests. Some of these come from companies offering higher compensation, closer commutes, or more exciting mandates. The candidate, already in "evaluation mode," engages.

The emotional pendulum swings. Around week three to four, the initial excitement of the new offer fades. The candidate begins to experience what behavioral economists call "status quo bias" — the familiar team, the known commute, the established relationships at the current company start to outweigh the uncertain promise of a new environment. Counter-offers amplify this effect.

Communication goes dark. Somewhere between day 30 and day 60, many candidates stop responding to the hiring company's messages. They have either accepted a counter-offer, taken a competing offer, or are simply avoiding an uncomfortable conversation. The hiring company, meanwhile, has no mechanism to detect disengagement — they are simply waiting for join day.

Join-day no-shows. On the scheduled start date, 20-40% of candidates in Indian IT simply do not show up. No email. No call. No explanation. The hiring manager discovers the dropout at 10 AM when the new hire fails to arrive. The recruiter then begins a frantic outreach that is almost always too late.

The cost math

Let us build the estimate from publicly available data points and reasonable industry assumptions.

The hiring volume: India's IT sector employs approximately 5.4 million professionals (NASSCOM 2024-25). Annual voluntary attrition in Indian IT has ranged between 13% and 17% over the past three years — meaning 700,000 to 900,000 positions turn over each year in IT alone. Each of these hires goes through the 90-day notice period cycle.

The dropout rate: Industry-reported offer dropout rates during notice periods range from 20% to 40%, depending on role seniority and market conditions. Using a conservative midpoint of 28%, that gives us approximately 196,000 to 252,000 failed hires per year in IT.

The cost per failure: The average salary for these roles sits between 8 and 12 LPA (lakhs per annum). Research from SHRM and Indian recruitment firms consistently places the total cost of a failed hire at 30-50% of annual salary when you factor in recruiter time, interview hours across the panel, background verification costs, the restart cycle (job posting, sourcing, screening, interviews, offer), lost productivity from the unfilled role, and opportunity cost for the hiring manager.

The arithmetic: Take 220,000 failed hires (midpoint) at an average cost of 3-5 LPA per failure (35-40% of an average 10 LPA salary). That gives us 660 billion to 1.1 trillion rupees, or roughly $8-13 billion at current exchange rates. Even halving this for conservative assumptions — not all roles are IT, not all carry the full replacement cost — puts the number firmly in the $4-6 billion range.

Our internal estimate of ~$6 billion accounts for the IT sector specifically and uses a 30% dropout rate with a 35% replacement cost multiplier. This is not a speculative number. It is the unavoidable output of multiplying India's hiring volume by its dropout rate by the well-documented cost of restarting a search.

And this only counts direct costs. It excludes the downstream effects: delayed project timelines, team morale impact, client delivery slippage, and the compounding effect of multiple dropouts on the same team within a quarter.

Why nobody is solving this

The 90-day notice period problem sits in a gap that no existing tool is designed to address. To understand why, look at where each category of HR technology stops working.

Job boards (Naukri, LinkedIn, Indeed) end at application. Their business model is connecting candidates to job openings. Once the candidate applies and enters your pipeline, the job board's involvement is over. They have no visibility into what happens between application and join date — and no incentive to build it.

Applicant Tracking Systems end at the signed offer letter. Tools like Greenhouse, Lever, Freshteam, and Zoho Recruit are designed to manage the funnel from sourcing through interview to offer acceptance. The moment a candidate signs the offer letter, they move into a "closed" state. Most ATSs have no concept of a "pre-joining" stage, no engagement workflows for the notice period, and no mechanism to flag disengagement signals.

HRMS platforms start at day one. Systems like Darwinbox, greytHR, and Keka are built for employees — people who have already joined. Their onboarding modules assume the person has shown up. They cannot engage someone who is still serving notice at another company.

The gap is structural. Between "offer accepted" and "first day of work" lies a 60-90 day window that is owned by nobody. Recruiters consider their job done. HR is waiting for the join date to begin onboarding. The hiring manager is busy with their existing team. The candidate is left alone with their doubts, their counter-offers, and their competing recruiters.

This is not a feature gap in existing tools. It is a category gap in the HR tech market. The notice period requires a dedicated engagement layer — something that sits between the ATS and the HRMS, keeping the candidate warm, informed, and committed during the most vulnerable window of the hiring process.

Pre-boarding engagement: what it looks like

Effective pre-boarding engagement is not about sending a welcome email and waiting 90 days. It is a structured, intentional program of touchpoints designed to maintain and strengthen the candidate's commitment throughout the notice period. Here is what a well-designed pre-boarding program includes:

Week 1: Immediate post-offer warmth. Within 24 hours of offer acceptance, the candidate receives a personalized welcome message from their future manager — not a templated HR email, but a genuine note that references something from their interview. The candidate is added to a private pre-joiner portal where they can access company information, team details, and their onboarding timeline.

Weeks 2-4: Role context drip. Over the next three weeks, the candidate receives carefully paced content about their upcoming role. This might include the team's current OKRs, a brief on the projects they will contribute to, recommended reading or courses relevant to their work, and a summary of the tech stack or tools they will use. The goal is to help the candidate mentally "start" the job before they physically arrive.

Weeks 3-6: Team introductions. The candidate is introduced to two or three future colleagues through brief, informal video calls or chat conversations. These are not interviews — they are low-pressure social connections that create bonds before day one. A candidate who knows three people on their future team is significantly less likely to ghost than one who knows nobody.

Bi-weekly manager check-ins. Every two weeks, the hiring manager has a brief (15-minute) call with the candidate. The agenda is deliberately light — how is your notice period going, any questions about the role, anything we can help with. The real purpose is to maintain a human connection and to detect early signs of disengagement. A candidate who starts declining these calls is a candidate at risk.

Weeks 8-12: Logistics and anticipation. In the final month, the focus shifts to practical preparation — confirming the join date, sharing day-one logistics (where to go, what to bring, who will greet them), setting up equipment, and building excitement about their first week. The candidate should arrive feeling expected, prepared, and valued.

The key principle across all of these touchpoints is consistency without pressure. The candidate should feel engaged and valued, not surveilled or pressured. Every interaction should add value to their experience, not extract a commitment confirmation.

What you can do today even without software

You do not need a dedicated platform to start reducing notice-period dropouts. Here is a practical checklist that any hiring team can implement this week using tools you already have:

1. 1. Send a personal manager note within 24 hours of offer acceptance. Not an HR template. A direct message from the hiring manager that references something specific from the interview — a project they discussed, a shared interest, a problem the candidate was excited to solve. This sets the relational tone immediately.
2. 2. Create a shared Google Doc or Notion page as a "pre-joiner hub." Include the team's current priorities, key Slack channels they will join, a reading list, and a FAQ about logistics. Share it within the first week. Give the candidate something tangible to engage with.
3. 3. Schedule bi-weekly 15-minute check-in calls with the hiring manager. Put them on the calendar immediately for the entire notice period. Keep the agenda light: "How is your notice period going? Anything we can help with? Any questions about the role?" If the candidate starts declining or rescheduling these, treat it as an early warning signal.
4. 4. Introduce the candidate to two future teammates. Arrange brief, informal calls — not interviews, just introductions. "Hey, you will be working closely with Priya on the payments team. She wanted to say hi and answer any questions." Social bonds are the strongest glue.
5. 5. Share one piece of role-relevant content every two weeks. A blog post about a technology they will use. A recording of a recent team all-hands. A product roadmap overview. The goal is to make the future role feel real and present, not abstract and distant.
6. 6. Confirm logistics 10 days before join date — not the day before. Send a clear email with: reporting time, office address, who to ask for at reception, what documents to bring, laptop setup timeline, and the day-one schedule. Uncertainty about logistics is a surprisingly common reason candidates get cold feet at the last moment.
7. 7. Assign a "pre-joining buddy" from the team. Someone who is not the manager and not from HR — a peer who can answer candid questions about team culture, work-life balance, and what the first few weeks actually look like. Make the buddy introduction in week two.
8. 8. Track engagement signals in a simple spreadsheet. Create a tracker for all candidates in notice period: last contact date, response time trend, check-in attendance, and a simple red/amber/green risk score. Review it weekly as a team. This is crude, but it is infinitely better than discovering a dropout on join day.

None of this requires software. It requires intentionality. The hiring manager and recruiter need to agree that their job is not done at offer acceptance — it is done at successful day-one attendance. Until that mindset shift happens, tools alone will not solve the problem.

Where Talentlo fits in your stack

Everything described above works. But it is manual, inconsistent, and difficult to scale beyond a handful of hires. When you are managing 20, 50, or 200 candidates in parallel notice periods, spreadsheets break down and personal outreach becomes impossible to sustain.

Talentlo is building a dedicated pre-boarding engagement layer that automates structured touchpoints during the notice period, flags disengagement signals before they become dropouts, enables hiring managers to maintain personalized connections at scale, and integrates with your existing ATS to pick up exactly where "offer accepted" leaves off.

This capability is on our active roadmap. Today, Talentlo helps companies streamline candidate evaluation with AI-powered assessments and structured interviews — reducing time-to-offer so you reach strong candidates before competitors do. The pre-boarding engagement module extends that philosophy past the offer letter, treating "offer accepted" as the midpoint of the hiring journey rather than the end.

If you are losing candidates during the notice period and want to be among the first to use Talentlo's pre-boarding tools when they launch, start a free trial today to get on the early access list and experience how Talentlo is rethinking the hiring process end-to-end.