A resignation letter changes the shape of a working relationship overnight. The employee is still on the team, still logging in, still nominally responsible for their targets, but the countdown has started, and everyone around them knows it. In India, the countdown tends to run longer than in most markets. Entry-level roles typically carry notice periods of 15 to 30 days, mid-level roles 30 to 60 days, and senior or specialist positions, especially in IT services, often run to 90 days.
That is a significant stretch of time for a manager to get right, and most managers get little guidance on how to do it. HR tracks the paperwork, the dates, and the final settlement. What happens day to day- the conversations, the workload, the team’s mood- sits with the manager.
What the Notice Period is Actually For
A notice period exists to give the organisation time to plan a replacement and the employee time to hand over cleanly. That is the whole premise. India has no single central law fixing one standard duration for private-sector employees.
The framework comes from the employment contract, read alongside the Industrial Relations Code, 2020, which took effect on 21 November 2025 and folded in the older Industrial Disputes Act, plus the state-specific Shops and Establishments Acts, according to the Ministry of Labour and Employment’s official notification. For most white-collar roles, whatever the appointment letter says is the operative rule.
Durations vary by seniority and sector:
| Seniority Tier | Typical Notice Period | Common Sectors |
| Entry-level / fresher | 15 to 30 days | Manufacturing, retail, startups |
| Mid-level (2 to 7 years) | 30 to 60 days | Most corporate roles, BFSI |
| Senior / specialist | 60 to 90 days | IT services, consulting |
| CXO / leadership | 90 to 180 days | Large enterprises, listed companies |
Nasscom’s 2024 technology sector HR report found that 67% of Indian IT companies mandate a 90-day notice period for employees with three or more years of experience. For a manager, the practical takeaway is simple: confirm what the contract actually says for that employee’s grade before the first conversation. Guessing wastes goodwill on both sides.
The First Conversation: What to Say in Week One
The manager’s first conversation after a resignation sets the tone for everything that follows. Three things need to happen, ideally within 48 hours:
- Acknowledge the decision without pressuring a reversal. A counteroffer conversation, if there is one, should come from HR or a skip-level, not from the manager trying to talk someone out of a choice they have already made.
- Confirm the exact notice period and last working day in writing, referencing the contract directly rather than relying on memory or precedent.
- Set expectations for the transition: what deliverables need to close out, who takes over which responsibility, and what attendance looks like for the remaining weeks.
Employees sometimes push back and ask whether the company can force them to serve out the full period. The honest answer is more nuanced than most appointment letters suggest, and a manager should know it before that question comes up, not during it.
What the manager should avoid is treating this as a conversation about loyalty. It is not one, and framing it that way tends to speed up the disengagement it is trying to prevent.
Building a Handover and Knowledge Transfer Plan That Works
A notice period only pays off if the knowledge inside it actually moves to someone else, and that does not happen on its own in the final week. Build the transition into the period from day one instead of leaving it to the last few days, an approach covered in more depth in our guide to notice period rules and rights in India.
A working handover plan needs to cover five things:
| Component | What It Includes | Owner |
| Task inventory | Every open task and recurring responsibility, listed with current status | Departing employee |
| Documentation | Process notes, client contacts, and where key files live | Departing employee, reviewed by manager |
| Successor briefing | A named person or interim owner for each responsibility | Manager |
| Stakeholder handoff | Client or partner introductions made before the last working day | Manager |
| Sign-off | Manager confirms handover is complete against the checklist | Manager |
Indian IT services firms formalise this through structured knowledge transfer documents built into offboarding well before the final two weeks. Smaller organisations rarely have that infrastructure, which is exactly why a manager-led checklist matters more, not less.
Deciding What Access and Responsibility to Retain
Not every departing employee should keep full access and full responsibility for the entire notice period. The decision depends on what the role touches.
- Client-facing roles: introduce the successor early and transfer relationships in stages rather than a single handoff near the end.
- Roles with sensitive access, source code, financial systems, or unreleased plans warrant a deliberate wind-down of access toward the end of the period.
- General roles: for most positions there is no operational reason to restrict access early, and doing so anyway tends to signal a distrust the employee has not earned.
The mistake to avoid is applying one access policy to every exit. A junior analyst and a departing sales head carry different risk profiles, and treating them the same either under-protects the business or needlessly punishes the employee.
Common Mistakes Managers Make During a Notice Period
Most of these mistakes do not come from bad intent. They come from a manager treating an exit like an extension of the regular working relationship, when it actually calls for a different set of instincts. The handover plan, the access decision, and the morale question covered above only hold up if the manager also avoids a handful of habits that quietly undo them, usually without the manager noticing until the damage is already visible on the team.
- Freezing the employee out of meetings and decisions right after resignation, which accelerates disengagement and makes the handover worse, not safer.
- Dumping the backlog on the departing employee in the final two weeks instead of pacing the handover across the full period.
- Skipping one-on-ones because the relationship feels awkward, removing the manager’s best tool for catching handover gaps early.
- Treating the exit as personal, including subtle badmouthing to the rest of the team, which rarely stays contained.
- Ignoring early disengagement signals that can eventually tip into an unauthorised absence. TPB’s look at why Indian employees abscond without notice points to the same root cause repeatedly: an exit that was never actively managed.
When the Notice Period Doesn’t Go to Plan
Sometimes the employee asks to leave earlier than the contract allows. Sometimes the organisation wants them gone sooner. Both are common, and both follow a defined path rather than an improvised one.
| Who Initiates | What the Manager Should Check First | Where It Routes |
| Employee requests early release | Whether the handover can genuinely be compressed, not just requested | Manager assesses feasibility; HR confirms buyout or leave-adjustment terms |
| Organisation wants early release | Whether the role is being restructured or continued presence carries more risk than value | HR documents the decision and issues revised terms in writing |
If the employee asks first, the manager’s job is to assess feasibility, not to treat the request as a bargaining chip. TPB’s guide to notice period negotiation in India covers how buyouts, leave adjustments, and remote knowledge transfer sessions can shorten a notice period without leaving the business exposed.
If the organisation asks first, perhaps because the role is being restructured or continued presence carries more risk than value, the decision should route through HR and get documented in writing before anything changes on the ground, specifying the revised last working day and settlement terms.
Either way, a verbal agreement with no paper trail is where most later disputes originate.
The Final Stretch: Exit Interview and Clean Handoff
By the last two weeks, the handover checklist should be nearly complete, not starting. The manager’s remaining job is to confirm sign-off against the plan, coordinate with HR on the exit interview, and make sure clearances, from IT access to asset return, are triggered on schedule.
A structured exit interview remains one of the more underused tools a manager and HR have together, and a list of red flags to watch for during exit interviews is worth reviewing before that conversation happens. Where exit volume is high enough, parts of this final stretch can be automated: access revocation, documentation, and settlement tracking, freeing the manager’s time for the parts that still require a human conversation.
In the End…
Managing someone through a notice period is not a compliance exercise, even though it produces paperwork. It is a short, defined window where a manager’s handling of the exit shapes three things at once: how much institutional knowledge survives the departure, how the rest of the team reads the organisation’s fairness, and what the departing employee says about the company once they are gone.
None of that requires an elaborate process. It requires a manager who has the first conversation early, builds the handover plan from day one instead of the final week, and treats the departing employee as a professional finishing a job rather than someone already halfway out the door. Get that right, and the notice period does what it was designed to do.
FAQs
How long is a notice period in India?
Notice periods in India vary by seniority and sector since there is no single labor law fixing one standard duration. Entry-level roles typically run 15 to 30 days, mid-level roles 30 to 60 days, and senior or specialist positions, especially in IT services, often extend to 90 days. CXO and leadership roles can carry notice periods of 90 to 180 days. The exact duration comes from the employment contract, read alongside the Industrial Relations Code, 2020, and applicable state Shops and Establishments Acts.
Can a company force an employee to serve the full notice period?
This depends on the terms of the employment contract, and the answer is more nuanced than most appointment letters suggest. Many contracts allow for a buyout option, where the employee pays the equivalent of the unserved notice period, or a mutually agreed early release. A manager should confirm the specific contractual terms before this question comes up in conversation, rather than during it.
What should a manager do in the first week after an employee resigns?
Three things need to happen within 48 hours: acknowledging the decision without pressuring a reversal, confirming the exact notice period and last working day in writing by referencing the contract directly, and setting clear expectations for the transition, including deliverables, ownership handoffs, and attendance.
Should a departing employee’s system access be restricted immediately?
Not universally. Access decisions should depend on what the role touches. Roles with sensitive access, such as source code, financial systems, or unreleased plans, warrant a deliberate wind-down toward the end of the notice period. For most general roles, there is no operational reason to restrict access early, and doing so anyway tends to signal a distrust the employee has not earned.
What happens if an employee wants to leave before their notice period ends?
This is common and follows a defined process rather than an improvised one. The manager’s job is to assess whether the handover can genuinely be compressed, not to treat the request as a bargaining chip. HR then confirms buyout or leave-adjustment terms. If the organisation initiates early release instead, the decision should route through HR and be documented in writing, specifying the revised last working day and settlement terms.
