How to reduce a 90 days notice period?

Short answer: Reduction means proving the business can run without you in fewer days. Combine manager sponsorship, documented KT, and optionally using accumulated leave or buyout. Target a specific last working day (LWD), not a vague “as soon as possible.”

Step-by-step approach

1. Calculate calendar days: 90 working days ≠ 90 calendar days—check if weekends/holidays count in your policy.
2. Identify low-risk period: post-release, between projects, or after major go-live.
3. Offer concrete KT: recordings, runbooks, shadow sessions, and access revocation checklist.
4. Ask HR about leave adjustment (paid leave during notice) vs buyout—policies differ by company.
5. Escalate politely if HR stalls: ask for policy reference and approval workflow in writing.
6. Keep performing normally—performance drops are a common reason managers block early release.

Real-world example

Ananya, QA lead at TCS with 90-day notice, wanted to join a Bangalore product startup in 70 days. She created Confluence pages for 40 test cases, paired a junior QA for 2 weeks, and proposed LWD after the UAT sign-off. Account manager agreed; HR reduced notice to 75 days and allowed 5 days of earned leave in the notice window.

Numbers & benchmarks

• Typical achievable reduction with good KT: 15–30 days off a 90-day notice.
• Leave during notice: many firms cap how many PTO days offset the notice period.

Mistakes to avoid

• Assuming all companies treat notice the same—MNC captives vs Indian service vs product differ widely.
• Going straight to HR bypassing your manager (manager can block silently).
• Using sick leave patterns to cut notice—can trigger compliance review.
• Sharing confidential client data in KT docs stored on personal drives.

If reduction is denied, ask: “What specific handover milestones would make a 60-day release acceptable?”