Performance Improvement Plan: A Fair PIP Guide for India

Performance Improvement Plan: A Fair PIP Guide for India

A performance improvement plan, or PIP, is one of the most consequential documents an HR team ever issues. Done well, a performance improvement plan gives a struggling employee a genuine, structured chance to succeed — clear goals, real support, a fair timeline — and protects the company with clean documentation if things do not work out. Done badly, a PIP is a paper trail for a decision already taken, and everyone involved knows it: the employee disengages, the manager goes through the motions, and the company inherits legal risk, glassdoor damage and a demoralised team.

This guide is a complete, practical playbook for designing and running PIPs in Indian companies — startups, SMBs and growing mid-market firms alike. It covers when a PIP is the right tool, how to write one, how to have the conversation, how to run the plan week by week, what the law in India expects, and how to handle every possible outcome with fairness and dignity. Sample structures, example goal language, a comparison table and an FAQ are included so you can put it to work immediately.

A quick framing note: performance management in India sits at the intersection of contract law, labour law and basic principles of natural justice. Specific obligations vary with the employee's role and coverage under labour statutes, and the legal landscape continues to evolve under the consolidated labour codes. Keep your process fair and documented, and verify current legal requirements for termination in your state and sector with counsel before acting on a failed PIP.

What a PIP Is — and What It Is Not

The honest definition

A performance improvement plan is a time-bound, written program that: identifies specific performance gaps against previously communicated expectations; sets measurable improvement goals; commits the company to defined support (coaching, training, resources); schedules regular check-ins; and states the consequences if improvement does not happen.

Every element in that sentence matters. Remove "previously communicated expectations" and the PIP is an ambush. Remove "measurable" and it is a mood. Remove "support" and it is a countdown clock. Remove "consequences" and it is a suggestion.

What a PIP is not

• Not a disciplinary tool. Misconduct — absenteeism without leave, policy violations, harassment, dishonesty — belongs in the disciplinary process, which in India may require a domestic enquiry for covered employees. Mixing conduct issues into a performance plan contaminates both processes.
• Not a substitute for management. If a manager has never given feedback, never set targets and never reviewed work, the first corrective step is management, not a PIP.
• Not a severance negotiation in costume. If the organisation has already decided to exit the person, a sham PIP is worse than an honest, respectful separation conversation — legally and ethically.
• Not a tool for engineered attrition. Using PIPs in bulk to manage headcount without calling it a layoff corrodes trust faster than any layoff would, and creates pattern evidence that can be used against the company.

When a PIP Is the Right Tool

Use a simple decision filter before initiating any PIP.

The four-question filter

1. Is this a performance gap or a conduct issue? Skills, output, quality and deadlines are performance. Behaviour, integrity and policy violations are conduct. Only performance belongs in a PIP.
2. Were expectations clear and communicated? Can you point to a goal sheet, KRA document, job description or written feedback that predates the problem? If not, fix expectations first and give the employee a fair runway before any formal plan.
3. Has informal correction been tried? A PIP should rarely be the first conversation about a problem. One-on-ones, feedback notes and an informal improvement window usually come first.
4. Is the gap within the employee's control? If the miss is caused by broken tooling, impossible targets, missing headcount or organisational churn, a PIP will not fix it — and will be seen as scapegoating.

If the answers are performance / yes / yes / yes, a PIP is appropriate. Anything else, address the failing answer first.

Signals that justify a PIP

• Sustained shortfall against quantified targets over multiple review periods
• Repeated quality failures documented in reviews or client escalations
• Consistent missed deadlines with impact on dependent teams
• Skill gaps that persist after training and feedback

Alternatives to consider first

• Coaching cycle: 4–6 weeks of structured 1:1s with written notes — often resolves the issue without formal machinery.
• Role recalibration: sometimes the person is mis-slotted; an internal move can convert a failing employee into a solid one.
• Workload and support audit: verify the person actually has the tools, access and bandwidth their goals assume.

The Legal Context in India

You do not need to be a lawyer to run a fair PIP, but you do need to respect the framework around it.

Key principles to build into your process

• Contract first. The appointment letter and HR policies form the baseline: probation clauses, notice periods, performance expectations. A PIP process that contradicts your own policy manual is a gift to opposing counsel.
• Employee category matters. Employees who qualify as "workmen" under industrial disputes law have stronger statutory protection around termination, including notice and compensation requirements, and disputes can end up before labour authorities. Managerial and supervisory employees are governed mainly by contract. Classify carefully — designation alone does not decide the category; actual duties do.
• Natural justice travels everywhere. Even where statute is silent, Indian courts consistently expect fairness: the person should know the case against them, get a genuine opportunity to improve or respond, and be judged without bias. A well-run PIP is essentially natural justice, operationalised.
• State and sector variation. Shops and establishments legislation, standing orders where applicable, and the evolving labour codes all shape termination mechanics — notice, final settlement timelines, documentation. Verify current requirements in your state before executing an exit.
• Discrimination and retaliation risk. A PIP issued shortly after a maternity announcement, a POSH complaint, a whistleblower report or a disability disclosure will be scrutinised as potential retaliation. Timing is evidence. If performance concerns predate the protected event, your documentation must prove it.

Documentation: your only witness

In any later dispute, the record is what testifies. Maintain: the pre-PIP feedback trail, the PIP document with acknowledgement, check-in notes signed or emailed after each session, work product samples, and the closure summary. Contemporaneous, boring, specific documentation wins cases; reconstructed narratives lose them.

Before the PIP: The Pre-PIP Checklist

Run through this list before drafting anything. Every "no" is a gap to fix first.

• Expectations for the role exist in writing and were shared before the shortfall
• The shortfall is measurable and you can show data or examples
• The manager has given documented informal feedback at least once
• Causes outside the employee's control have been ruled out or accounted for
• The employee's tenure context is considered (a 90-day probationer follows the probation process, not necessarily a full PIP)
• No protected event (maternity, medical leave, complaint filed) makes timing legally sensitive — if one exists, take advice before proceeding
• HR has reviewed the draft for specificity, fairness and tone
• The manager is committed to the support plan, with time blocked for check-ins

Designing a Fair PIP

Duration

Common practice ranges from 30 to 90 days. Choose based on the role's output cycle: a sales role with monthly quotas can show change in 60 days; a software engineer's improvement may be visible in 30–45 days of sprint work; a strategic role may need a quarter. Too short signals predetermination; too long prolongs stress without added signal. State the exact start and end dates.

Goals: the SMART discipline

Every PIP goal must be specific, measurable, achievable, relevant and time-bound. The achievability test is the one most often failed — goals set above the level expected of peers convert the PIP into a trap, and tribunals notice.

Weak goal: "Improve communication with stakeholders."

Strong goal: "Send a written project status update to the product and QA leads every Friday by 5 pm, covering progress, blockers and next week's plan, for each of the six weeks of this plan."

Weak goal: "Increase sales performance."

Strong goal: "Achieve at least 80% of the standard monthly qualified-demo target (16 of 20) in each of the two months of this plan, using the same lead pool and territory as peers."

Three to five goals is the sweet spot. One goal is too narrow to be fair; eight is a checklist designed for failure.

Support: the half everyone forgets

For each goal, write down what the company will provide: training modules, shadowing sessions, tooling access, a mentor, reduced non-core load, weekly manager coaching. If the support column is empty, the plan is not an improvement plan. Support commitments are also the company's proof of good faith.

Check-in cadence

Weekly is the default: 30 minutes, same slot, with a written summary after each session recording progress against every goal, support delivered, and any obstacles raised. A formal mid-point review halfway through gives the employee a clear read on trajectory — nobody should learn their outcome for the first time on the last day.

Writing the PIP Document

A structure that works

1. Header: employee name, role, manager, HR partner, plan start and end dates.
2. Background: two or three sentences describing the performance gap factually, with references to prior feedback dates. No adjectives about attitude; only observable shortfalls.
3. Goals table: each goal with its metric, target, evidence source and review checkpoint.
4. Support plan: the specific resources, training and coaching the company commits to.
5. Check-in schedule: dates of weekly reviews and the mid-point review.
6. Standards during the plan: normal policies continue to apply; the employee remains eligible for support channels.
7. Possible outcomes: successful completion and closure; extension in defined circumstances; redeployment where a suitable role exists; or separation per the employment contract and applicable law if goals are not met.
8. Acknowledgement: signature or e-acknowledgement of receipt — noting explicitly that acknowledgement means "received and understood", not "agreed I am underperforming". Offer the employee space to add written comments; their perspective belongs in the record.

Tone rules

Write like a professional adult addressing a professional adult. No euphemisms ("growth journey"), no threats, no legalese. The document should read as: here is the gap, here is the bar, here is the help, here is the timeline, here is what happens next.

The PIP Conversation

The delivery meeting determines whether the plan gets a fair chance.

How to run it

• Setting: private, 45–60 minutes, manager leads, HR present. Never on a Friday evening, never by surprise calendar invite titled "Discussion".
• Open plainly: "This is a formal conversation about performance. We're placing you on a structured improvement plan, and I want to walk you through exactly what it says and what support you'll get."
• Walk the document: gaps, goals, support, cadence, outcomes. Pause for questions after each section.
• Listen genuinely: the employee may surface causes you missed — health issues, unclear priorities, a broken dependency. Note them; where valid, adjust the plan. A plan amended after listening is stronger, not weaker.
• Close with the schedule: first check-in date, what to prepare, who to contact with questions.
• Follow up in writing the same day with the document and a neutral summary of the discussion.

What managers must not say

• "This is just a formality." (It is either untrue or an admission of bad faith.)
• "HR is making me do this."
• "Honestly, I'd start looking." (This converts the plan into constructive dismissal evidence.)
• Any comparison with named colleagues.

Running the Plan Week by Week

• Week 1: confirm the employee has every promised resource. A support commitment delivered late invalidates the week it was missing.
• Each check-in: review every goal against its metric, using the evidence sources named in the plan. Record status in three states: on track, partially on track, off track. Send the written summary within 24 hours.
• Mid-point review: a formal trajectory statement — "based on the first three weeks, you are on track on goals 1 and 3, and off track on goal 2; here is what closing that gap requires." Adjust support if needed.
• Manager discipline: cancelled check-ins are the most common way companies sabotage their own PIPs. Treat the check-in as an immovable commitment; HR should audit that summaries exist each week.
• Employee obstacles: if the employee raises a blocker, resolve it and document the resolution. Unresolved, documented blockers become the employee's defence and the company's problem.

Outcomes and How to Handle Each

1. Successful completion

Close formally, in writing: goals met, plan closed, standard expectations resume. Then actually reintegrate the person — a passed PIP that leaves the employee permanently stigmatised is a slow-motion resignation. The manager's job in the following quarter is to rebuild confidence and visibility.

2. Partial improvement — extension

Where trajectory is positive but incomplete, a single, defined extension (often 30 days) can be fair, especially if any support arrived late or external disruption occurred. Document the rationale. Serial extensions, by contrast, signal an unfair bar or an unwilling decision-maker; avoid more than one.

3. Redeployment

Sometimes the plan reveals a skills-role mismatch rather than a capability void. If a suitable open role exists and the employee is a cultural asset, an internal move with a fresh goal sheet can save institutional knowledge and morale. Do this deliberately, not as a way to dodge a hard call.

4. Separation

If goals are not met, proceed to separation under the employment contract and applicable law: notice or pay in lieu per contract and statute, leave encashment, full and final settlement within required timelines, and the relieving and experience letters the person is entitled to. Conduct the conversation with dignity — short, factual, humane. Offer a reference protocol and, where feasible, outplacement help. How you exit people is watched by everyone who stays.

Protected Situations: Proceed With Care

Treat these scenarios as amber lights requiring legal review before initiating or concluding a PIP:

• Pregnancy and maternity leave: maternity protection in India is strong; adverse action during protected periods carries serious risk.
• Ongoing POSH proceedings: a PIP for a complainant or witness invites a retaliation claim; sequence carefully and document independent justification.
• Disclosed disability or serious illness: consider reasonable accommodation and adjusted goals before any formal plan.
• Whistleblower reports: same retaliation logic as POSH; independent, pre-existing documentation is essential.
• Long medical leave: pause PIP clocks during approved leave; an employee cannot improve while legitimately absent.

PIP vs Disciplinary Action vs Role Change

A Worked Example

Meera is a customer success manager, eight quarters in, historically solid. Over two quarters her renewal book slips well below target, QBR decks go out late, and two clients escalate. Her manager has given verbal feedback twice and one written note; the gap persists.

Pre-PIP check: expectations exist (quarterly goal sheet), data exists (CRM renewals, escalation tickets), informal feedback happened, no protected situation, no external cause — her book and tooling match her peers'. A PIP is appropriate.

The plan (60 days): three goals — (1) deliver all QBR decks at least two business days before each scheduled QBR, evidenced by upload timestamps; (2) complete renewal playbook actions for 100% of accounts entering the renewal window, evidenced by CRM task completion; (3) zero unanswered client emails older than one business day, evidenced by help-desk SLA reports. Support: renewal playbook refresher, weekly 30-minute coaching, temporary transfer of two low-fit accounts, and a senior CSM shadow for two client calls.

Execution: weekly check-ins with written summaries. Mid-point: goals 1 and 3 on track; goal 2 partially — Meera flags that half the pending playbook actions were blocked on a pricing approval queue. The manager fixes the queue and documents it; the goal window for those accounts is adjusted by one week. Final review: all three goals met. The plan closes in writing; next quarter Meera renews at target, and the retention of a trained CSM costs the company exactly one management effort instead of one replacement hire.

The counterfactual — a vague "improve client management" plan with no support — would likely have produced a resignation, a dispute, or both.

Metrics: Is Your PIP Program Fair?

Track these at the program level, reviewed half-yearly by HR leadership:

• Completion rate: what share of PIPs end in successful closure? A rate near zero says PIPs are exit paperwork; near 100% says managers use PIPs to outsource feedback they should give informally. Healthy programs sit meaningfully in between.
• Distribution: PIPs by manager, department, gender, age band and tenure. Clusters are smoke; investigate them.
• Support delivery: percentage of support commitments delivered on time — audit a sample.
• Post-PIP survival: how many PIP completers are still employed and rated satisfactory a year later? This measures whether closure is real.
• Voluntary exit during PIP: a high quit-rate mid-plan suggests plans are experienced as verdicts, not opportunities.

Remote and Hybrid PIPs

Distributed work changes execution, not principles:

• Run every check-in on video with cameras on where culturally acceptable; record summaries in writing as always.
• Use system-of-record evidence (tickets, commits, CRM entries, shared docs) rather than "visibility" impressions — remote PIPs fail legal and fairness tests when they punish low visibility rather than low output.
• Deliver the initial conversation live on video, never by email; the document follows in writing.
• Watch time-zone fairness in goal deadlines.

Sample PIP Language You Can Adapt

Concrete language is where most teams get stuck, so here is a fuller skeleton you can adapt. Replace bracketed text; delete anything that does not apply.

Background section:

"Over the review periods of [Q1 and Q2], your delivery against the goals communicated in your [goal sheet dated —] has fallen short in the following areas: [area 1 with metric]; [area 2 with metric]. These gaps were discussed in one-on-one meetings on [dates] and summarised in writing on [date]. Because the shortfall has continued, we are initiating a structured performance improvement plan from [start date] to [end date]."

Goal row (example, engineering):

"Goal 2 — Code quality: over the plan period, maintain a defect reopen rate at or below the team's standard threshold of [X]% on tickets you close, as measured in [tool]. Checkpoint: reviewed weekly; formally assessed at mid-point and closure."

Support row:

"The company will provide: [a] a weekly 30-minute coaching session with [manager]; [b] enrolment in [named course/module] to be completed by [date] during working hours; [c] pairing with [senior colleague] for [two] sessions per week for the first [three] weeks; [d] reprioritisation of [non-core duty] for the duration of the plan."

Outcomes section:

"If the goals above are met at the closure review, this plan will be closed in writing and normal performance management will resume. If progress is substantial but incomplete, the company may at its discretion extend the plan once, by up to [30] days. If the goals are not met, the company may proceed to actions up to and including separation of employment in accordance with your employment contract and applicable law."

Acknowledgement block:

"I acknowledge that this plan was shared and explained to me on [date]. My acknowledgement confirms receipt and understanding; it does not necessarily indicate agreement with the assessment. I understand I may submit written comments, which will be kept on record with this plan."

Adapt tone to your culture, but keep the architecture: factual background, measurable goals, named support, dated cadence, explicit outcomes, honest acknowledgement.

Training Managers for the Hardest Conversation

A PIP program is only as good as the managers who deliver it, and most first-time managers have never been taught how. Build a short internal enablement module covering:

• The fairness mindset: the purpose of a PIP is a genuine chance, not a paper trail. Managers who cannot honestly say "I want this person to pass" should escalate to HR before initiating.
• Delivering the message: practice the opening two minutes out loud. The most common failure is softening the message until the employee leaves the room unsure whether anything formal happened.
• Separating person from performance: language stays about output and evidence, never character. "The last four releases missed the agreed dates" rather than "you're careless".
• Running check-ins: how to review evidence, how to record status honestly (including good news — a check-in record that only ever logs failure looks like case-building), and how to respond when the employee pushes back.
• What not to promise: managers must not guarantee outcomes in either direction — no "you'll be fine" and no "start looking". Both create liability.
• When to call HR: any mention of health conditions, harassment, discrimination or resignation mid-plan goes to HR the same day.

A two-hour workshop with role-play, run twice a year, changes PIP outcomes more than any template improvement. Record attendance; it is also evidence of institutional good faith.

Running PIPs in a Small Company Without an HR Department

Founders and ops leads in companies under 50 people often assume PIPs are corporate machinery they can skip. The opposite is true: in a small team, one mishandled exit can consume the leadership bandwidth of a quarter and poison the culture for longer. A lightweight version of the same discipline:

1. Write expectations down early. Even a one-page goal note per person per quarter gives you the baseline that makes any later conversation fair.
2. Use a simplified plan. A two-page document — gaps, three goals, support, weekly check-in, outcomes — is entirely sufficient. Fairness scales down; sloppiness does not.
3. Founders take the HR role. The manager runs the plan; a co-founder or senior leader not in the reporting line reviews it for fairness and sits in on the opening conversation.
4. Keep the same documentation bar. Written summaries after each check-in, stored where they will survive laptop changes and departures.
5. Take advice before exits. One hour of employment counsel before a separation is the cheapest insurance a small company can buy, especially for employees who may hold workman-status protections.

Small companies actually hold an advantage: feedback distances are short, and a well-run 45-day plan with genuine founder attention rescues a high percentage of struggling early employees — each of whom is disproportionately expensive to replace.

How HR Software Changes PIP Execution

None of this playbook requires software, but the failure modes it prevents — lost feedback trails, skipped check-ins, inconsistent templates, timing disputes — are precisely the ones software eliminates:

• Timestamped goal and feedback history establishes the pre-PIP record automatically, closing the "I was never told" gap.
• Templated plans keep structure and tone consistent across managers, which is also your consistency defence against discrimination claims.
• Scheduled check-ins with logged summaries create the contemporaneous record tribunals trust, without relying on manager memory.
• Acknowledgement workflows capture receipt, comments and refusals cleanly.
• Program analytics — completion rates, distribution by manager and demographic, support delivery — surface fairness problems while they are still fixable.
• Access controls keep an inherently sensitive process confidential to the people who need to know.

If your current PIP process lives in email threads and a shared drive, moving it into your HRMS is a one-week project that upgrades both fairness and defensibility permanently.

Frequently Asked Questions

How long should a performance improvement plan last in India?

There is no statutory duration; 30, 60 or 90 days are common, chosen to match the role's output cycle. The test is fairness: the period must allow a genuine demonstration of improvement on the stated goals.

Is a PIP legally required before terminating for poor performance in India?

Statute does not generally mandate a "PIP" by name, but fair process before termination is strongly advisable and, for employees with workman-status protections, procedural and compensation requirements apply. A documented PIP is the cleanest evidence of fair process. Verify current requirements for your state and employee category with counsel.

Can an employee refuse to sign a PIP?

Yes, and it does not block the process. Record that the document was presented and explained, note the refusal, and proceed. Acknowledgement is about receipt, not agreement — say so explicitly in the document.

Can someone resign during a PIP?

Yes. Resignation follows the normal contractual notice process. Do not pressure resignation as the intended outcome of a PIP; engineered resignations underpin constructive dismissal claims.

Should probationers be put on a PIP?

Usually not in full form. Probation is itself an assessment period with its own confirmation/extension mechanics — use documented feedback and the probation process. A formal PIP for a 60-day-old hire mostly signals a hiring error.

Does a PIP have to end in termination if goals are missed?

No. Outcomes include closure, one defined extension, redeployment, or separation. What a fair plan cannot do is state one set of outcomes and secretly permit only one.

How is a PIP different from a disciplinary warning?

A PIP addresses capability and output with goals and support. A warning addresses conduct and precedes disciplinary escalation. Running conduct issues through a PIP, or performance issues through disciplinary machinery, weakens both records.

Who should own the PIP — HR or the manager?

The manager owns the performance judgment, the goals and the check-ins. HR owns process integrity: fairness review, documentation standards, protected-situation screening and outcome consistency. Plans fail when either tries to do the other's job.

Conclusion: Fair Process Is the Whole Point

A performance improvement plan is not paperwork; it is a promise — that your company tells people the truth about their performance, gives them a real chance with real support, and makes decisions based on evidence rather than politics. Companies that keep that promise get something valuable either way: an employee restored to performance, or a defensible, dignified separation that the rest of the team respects.

The operational backbone matters: goal records, feedback trails, check-in summaries, acknowledgements and closure documents, all in one place. That is exactly what an HRMS like CozyHR provides — goal tracking, documented reviews, letter templates and a complete performance record for every employee, so your PIPs run on evidence instead of memory. If you are formalising performance management this year, start a free CozyHR trial and give your managers the system their hardest conversations deserve.

This article is general guidance for HR practitioners, not legal advice. Termination-related requirements vary by state, sector and employee category and continue to evolve under India's labour codes — verify current law or consult counsel before acting.