Performance Improvement Plans: A Manager's Guide

A performance improvement plan is the most misused instrument in people management. In theory, it is a structured second chance: clear expectations, real support, a defined period, and an honest assessment at the end. In practice, it is too often a paperwork exercise run after the decision has already been made, which everyone involved recognises and nobody says out loud.

That gap matters. A PIP run properly saves employees who are genuinely recoverable — and a surprising proportion are, because underperformance frequently has causes that management can fix. A PIP run as theatre damages the manager's credibility, unsettles the wider team, produces a weaker record than doing nothing, and often ends in a dispute.

This guide is for managers and HR teams in India who want to run performance improvement plans that are useful rather than performative: how to decide whether a PIP is the right instrument, how to write one, how to run the conversations, and how to close it either way.

Verify before you act: the legal position on termination, notice, settlement and applicable protections depends on the employee's category, the applicable state rules and your contractual terms. Take advice from a labour law advisor before any separation decision, and do not treat a PIP as a substitute for that advice.

Diagnose before you prescribe

The first question is not "how do I write a PIP?" It is "why is this person underperforming?" Answer that wrongly and every subsequent step is wasted effort.

Underperformance almost always has one of six causes, and only two of them are addressed by a performance improvement plan.

1. Unclear expectations. The person does not know what good looks like, or believes they are doing well on the dimensions that were emphasised to them. Extremely common, and entirely a management failure. Fix: define expectations. A PIP is not needed and its use here is unjust.

2. Skill or knowledge gap. They understand what is required and cannot yet do it. Fix: training, coaching, pairing, a scoped-down role for a period. A PIP is appropriate only if targeted development has already been tried and has not closed the gap.

3. Wrong role fit. Genuinely capable person, wrong job — a strong individual contributor promoted into management, a detail-oriented person in an ambiguous strategic role. Fix: role change or internal move if one is available. A PIP will not turn one person into a different person.

4. Motivation and engagement. They can do it and are not doing it. Causes range widely: a bad manager relationship, being passed over, burnout, a competing offer, disengagement from the company's direction. Fix: an honest conversation first. A PIP applied to a disengaged high performer usually accelerates their exit, which may not be what you want.

5. Personal circumstances. Illness, caregiving, bereavement, financial or family crisis. Fix: support, flexibility, leave. Applying a PIP here is both inhumane and potentially risky, particularly where a health condition is involved. Talk to HR before proceeding.

6. Systemic or environmental. Insufficient resources, blocked dependencies, an unrealistic target, a broken process, a territory that cannot deliver the number. Fix the system. If three of five people in a role are failing the same target, the target is the problem.

Before initiating any PIP, write down which of these applies and the evidence for it. If you cannot, you are not ready. A useful discipline: ask the employee directly what they think is getting in the way, and take the answer seriously. Managers are frequently surprised, and the surprise is usually informative.

When a PIP is the right instrument

A performance improvement plan is appropriate when all of the following are true:

• The performance gap is specific, observable and material to the role
• Expectations have been communicated clearly and the employee has acknowledged them
• Feedback has been given previously, more than once, and documented
• Reasonable support has already been provided
• The gap has persisted despite that support
• The gap is capable of being closed within a defined period
• You would genuinely retain the employee if it closed

That last condition is the honesty test. If the answer is no — if the relationship is beyond repair, or a decision has already been taken — then a PIP is the wrong instrument. Consider a direct conversation about separation, negotiated exit or a role change instead, with proper legal advice. Running a PIP to build a file is transparent to the employee, corrosive to the team's trust, and produces a record that a reviewer can see through.

A PIP is also not appropriate for misconduct. Misconduct — dishonesty, harassment, policy breach, insubordination — follows the disciplinary process, which has different steps, different evidentiary standards and different outcomes. Conflating the two weakens both.

The pre-PIP conversation

Before any formal plan, have one clear, documented conversation. Many performance issues resolve here, and going straight to a formal PIP without it is both unfair and tactically poor.

Structure it in five steps:

1. State the gap specifically. "In the last two quarters, four of your six deliverables missed their agreed dates by more than a week, and two required rework after review." Not: "Your delivery has been disappointing."
2. Explain the impact. What it costs the team, the customer, the business. Impact converts a personal criticism into a business problem.
3. Ask, then listen. "What's your read on this? What's getting in the way?" Then stop talking. This is where you learn whether the cause is skill, clarity, motivation, circumstances or system.
4. Agree specific changes. Two or three concrete things, with dates. Include what you will do, not only what they will do.
5. Set a review date. Two to four weeks. Confirm in writing the same day — a short email summarising the conversation, the agreed actions and the review date.

That email is important. If the situation later escalates, it is evidence that feedback was given and support offered. If it does not escalate, it is a useful shared reference. Either way it costs five minutes.

Writing the plan

If the gap persists after the informal stage, move to a formal plan. A good PIP document is short — two to three pages — and specific enough that a neutral third party could read it and determine, at the end, whether the standard was met.

The essential components

1. Header information. Employee name, role, manager, HR contact, plan start date, plan end date, review dates.

2. Purpose statement. One paragraph explaining that this is a structured plan to help the employee meet the expectations of their role, what will happen at the end in either outcome, and that the plan will be reviewed at defined points. Do not soften this into vagueness. The employee is entitled to know the stakes.

3. Performance gaps. For each gap: the expectation, the current performance, the evidence, and the impact. Use a table.

4. Improvement objectives. This is the heart of the plan, and where most PIPs fail. Each objective must be specific, measurable, achievable within the plan period, relevant to the role, and time-bound. Three to five objectives maximum — more than that is a signal that the role is wrong, not the person.

Weak objective: "Improve quality of work." Strong objective: "All deliverables submitted from 1 October pass review with no more than two correction items, measured across all submissions in the plan period."

Weak objective: "Be more proactive in communication." Strong objective: "Provide a written status update on each active project every Friday by 17:00, flagging any risk to timeline at least five working days before the due date."

5. Support provided. What the company will do: training, coaching sessions, shadowing, reduced scope, mentor assignment, tooling, weekly one-to-ones. Name the person and the frequency. A PIP with no support column is not a plan; it is a countdown.

6. Review schedule. Weekly or fortnightly check-ins with dates, plus a formal midpoint review and an end review. Put the dates in the document and in calendars.

7. Consequences. State plainly what happens if the objectives are met, partially met, or not met. Ambiguity here is unfair to the employee and unhelpful to the company.

8. Signatures and acknowledgement. Employee, manager, HR. If the employee declines to sign, note that they received it and declined to sign, and provide a copy anyway. Refusal to sign does not invalidate the plan; concealment of the plan would.

9. Employee comments. A section for the employee to record their own view. This matters more than it appears: it makes the process two-way, and an employee who has recorded a disagreement about resources or workload has given you information you need.

How long should a PIP run?

Long enough for measurable change, short enough to remain meaningful. Common practice:

Match the period to the natural cycle of the work. A 30-day PIP for a role with a four-month sales cycle measures nothing, and both parties know it.

Running the plan: the part that determines the outcome

The document is 20% of the work. The conversations are the rest.

The initiation meeting

Manager and HR both present. Keep it to thirty minutes. Cover: why we are here, the specific gaps, the objectives, the support, the review dates, the consequences, and their questions. Give them the document to read before signing — offer a day if they want it.

Tone matters enormously. The message should be: "I want this to work, here is exactly what 'working' looks like, and here is what I am doing to help." Not: "This is a formality." Not: "You've left me no choice."

Expect emotion. Shock, anger, tears, or complete silence are all normal. Do not fill the silence with reassurance that contradicts the plan. Acknowledge that it is difficult, restate the intention, and offer a follow-up conversation in a day or two once they have processed it.

The check-ins

Weekly, short, specific, documented. A workable format:

• What was achieved against each objective this week — evidence, not impression
• What got in the way
• What support is needed
• Any adjustment to the plan and why
• A one-line summary emailed the same day

Two failure modes to avoid. First, the disappearing manager: the plan is issued and then nothing happens until the end date, at which point the outcome is announced. This is the single most common defect in PIP practice, and it makes the process indefensible. Second, the moving target: adding new objectives mid-plan because new problems have appeared. If genuinely new issues arise, note them separately; do not retrofit them into a plan the employee is already working against.

Adjusting mid-plan

Sometimes the plan needs to change — a project is cancelled, a dependency collapses, the employee's circumstances change. Adjust openly, in writing, with the reason recorded. Adjustment for legitimate reasons strengthens the process. Silent adjustment, in either direction, undermines it.

Documentation discipline

Keep a running file: the plan, every check-in summary, evidence against each objective, support delivered, and any adjustments. Store it in the HR system against the employee record with restricted access, not in the manager's mailbox. If the manager leaves mid-plan, their successor needs to be able to pick it up — and a plan that dies because a manager changed is worse than no plan at all.

A worked example: a PIP that was designed to succeed

Abstract structure is easier to follow with a case. The details below are illustrative, not drawn from any real organisation.

The situation. Rohan, a customer success manager with fourteen months' tenure, was managing 32 accounts. Renewal rate in his portfolio had fallen to 71% against a team average of 88%. Two escalations had reached the head of department in one quarter. His manager's initial framing was "he isn't proactive enough."

The diagnosis. Before writing anything, the manager and HR looked at the data rather than the impression. Three things surfaced. Rohan's portfolio contained a disproportionate number of accounts inherited from a departed colleague, several already at risk when transferred. He had never received the product certification the rest of the team completed during onboarding, because he joined between cohorts. And his weekly account review notes showed he was spending most of his time firefighting support tickets that should have been routed to the support team.

Two of those three were organisational failures. Only the third — the pattern of absorbing work that was not his — was something he could change directly, and even that was partly a routing problem.

What happened. The manager did not issue a PIP. She rebalanced the portfolio, enrolled Rohan in the next certification cohort, fixed the ticket routing with the support lead, and set a 60-day informal improvement period with weekly check-ins and a documented summary email each Friday. Renewal rate in his portfolio recovered to 84% over the following two quarters.

The counterfactual. Had a PIP been issued at the original framing — "be more proactive" — Rohan would have been measured on an unmeasurable objective, in a portfolio structurally worse than his peers', without the training the role required. He would very likely have failed it, left, and been replaced by someone who would have inherited exactly the same three problems.

The lesson. The diagnostic step is not a formality that precedes the real work. It frequently is the work. Where the diagnosis points to organisational causes, fixing them is faster, cheaper and considerably more effective than performance-managing an individual through a problem they did not create.

The corollary matters too. When the diagnosis genuinely does point to individual capability or effort — and sometimes it does — a manager who has already ruled out the organisational causes can say so with confidence, and the resulting plan carries far more weight with the employee.

The conversation scripts managers actually need

Most managers do not struggle with the document. They struggle with the first sixty seconds of each conversation. Three short scripts, adapted to circumstance, remove most of that difficulty.

Opening the pre-PIP conversation: > "I want to talk about something specific and I'd like your view on it. Over the last two quarters, four of six deliverables have gone past their agreed dates, and two needed rework. That's affecting the team's commitments to the client. I want to understand what's driving it before we decide what to do about it — what's your read?"

Short, factual, ends with a genuine question. It avoids both the vague opener ("how do you think things are going?") that wastes ten minutes, and the accusatory opener that closes the conversation immediately.

Issuing the plan: > "We talked six weeks ago about delivery timelines and agreed some changes. Those changes haven't held — here's what the last six weeks look like. So we're moving to a formal improvement plan. I want to be direct about what that means: it's a 60-day plan with three specific objectives, weekly check-ins with me, and the training we discussed. If the objectives are met, the plan closes and we carry on. If they're not, we'd be looking at whether this role is the right fit. I'd much rather be in the first situation, which is why the support in here is real. Take the document, read it properly, and let's talk again on Thursday with your questions."

It names the stakes without threatening, states what the company is contributing, and gives the person time to absorb it.

Closing a plan that has not succeeded: > "We've reached the end of the 60 days. On objectives one and three, the standard wasn't met — here's the summary against each. I know you've put effort in, and I don't dispute that. But the gap is where it was at the start, and I've concluded this role isn't the right fit. Let me take you through what happens now, practically."

No relitigating, no false comfort, no ambiguity about whether the decision is open. The practical detail that follows — dates, settlement, handover, documents — is what the person will actually need, and delivering it clearly is a form of respect.

Give managers these in the briefing pack. The quality of a PIP is determined far more by how these three conversations go than by the wording of the document.

Closing the plan

If objectives are met

Say so clearly, in writing, and mean it. Confirm the plan is closed successfully, thank them for the effort, and set expectations for sustaining the standard. Do not attach shadow conditions — informally treating a successful PIP graduate as still on probation is both unfair and quickly detected.

Then watch for regression with normal management attention, not surveillance. If performance drops again within a short window, that is a different conversation and may proceed more quickly, but it should still be an honest one.

Successful PIPs are more common than the folklore suggests, particularly where the underlying cause was clarity, skill or a fixable systemic issue. Track your own success rate. If nobody in your organisation has ever completed a PIP successfully, the process is being used as a separation mechanism and everyone knows it.

If objectives are partially met

The hardest case. Options: extend once with revised objectives, move the employee to a different role where the gap is not material, or proceed to separation. Extension is defensible once, where genuine progress is visible and the trajectory suggests the gap will close. Repeated extension is not — it becomes indefinite performance management, which is unfair to the employee and unhelpful to the team.

Whatever you decide, write down the reasoning at the time.

If objectives are not met

Take advice before acting. The lawful route depends on the employee's category, applicable state rules, your contract terms, and the circumstances. In India, employees in certain categories have specific procedural protections, and even where they do not, contractual notice, settlement of dues and process fairness matter. Points to work through with your advisor:

• Whether the process followed was fair and documented
• Notice or payment in lieu, per contract and applicable rules
• Full and final settlement, including leave encashment and gratuity if eligible
• Documents to be issued and their wording
• Whether a mutually agreed separation is preferable
• What the employee will be told, and what the team will be told

Handle the conversation itself with dignity. Short, clear, private, with HR present. State the decision, the effective date, the settlement terms, and what happens next practically — system access, handover, documents, references. Do not relitigate the performance history in that meeting; that conversation has already happened, repeatedly, which is precisely the point of having run the process properly.

Legal and fairness considerations in the Indian context

Some principles hold regardless of category:

Process fairness is the core defence. Documented expectations, documented feedback, documented support, a reasonable period, and an honest assessment. Most disputes turn on process, not on whether the performance judgement was correct.

Consistency across employees. If two people have comparable performance gaps and one gets a PIP while the other is separated immediately, be able to explain why. Inconsistency is where discrimination claims find purchase.

Do not use a PIP as retaliation. Initiating performance management shortly after an employee raises a grievance, reports harassment, takes protected leave or acts as a whistleblower creates an obvious inference. If performance concerns genuinely predate the complaint, your documentation should show it. If they do not, wait and take advice.

Health, disability and pregnancy require particular care. Where a performance issue may relate to a health condition, disability or pregnancy, involve HR before proceeding and consider accommodation obligations. This is an area where getting it wrong is both harmful and legally significant.

Be careful with wording. Nothing in the plan should suggest a decision has already been made, and nothing should promise employment beyond the plan period. Avoid characterising performance as misconduct.

Confidentiality. The plan is confidential to the employee, their manager, the skip-level where necessary, and HR. Discussing it with the wider team is a serious breach and creates real exposure.

What HR should own

The manager runs the plan; HR owns the system. Specifically:

• Gatekeeping. Review every proposed PIP before issue. Test it against the diagnostic above and against the honesty question. Push back on plans that are separation dressed as improvement, plans with unmeasurable objectives, and plans with no support.
• Template and training. A standard template and a short manager briefing. Most first-time PIP managers have never seen one done well.
• Presence at the initiation and closing meetings. For fairness, consistency and record.
• Monitoring. Track active plans, check that check-ins are actually happening, and intervene when a manager goes quiet.
• Pattern analysis. Which managers issue the most PIPs? Which functions? What is the success rate? A manager with five PIPs in a year and no successful outcomes is a management development issue, not a talent quality issue.
• Quality of documentation. Reviewing files before any separation decision.

Measuring whether your PIP process is healthy

Individual plans are managed by managers. The process as a whole should be managed by HR, using a handful of indicators reviewed quarterly.

Two of these deserve particular weight. A success rate near zero is the clearest possible evidence that the process has become theatre, and it should trigger a review of how plans are approved rather than a review of hiring quality. And a concentration of plans in employees with under a year of tenure almost always points to a selection, onboarding or expectation-setting problem — problems that are considerably cheaper to fix at the source than one PIP at a time.

Share the aggregate view with leadership annually. Performance management is one of the areas where organisational patterns are invisible from inside any single team and obvious the moment the data is pooled.

Alternatives worth considering before a formal plan

A PIP is one instrument among several, and it is not always the most effective. Depending on the diagnosis, these often work better and faster.

Role rescoping. Narrow the role to the parts the person does well and redistribute the rest. This is not a demotion if the compensation and title hold; it is a rational allocation of work. It is particularly effective where someone strong has been given an over-broad role during a growth phase.

A lateral move. An internal transfer to a role that fits better. This preserves institutional knowledge, keeps a capable person, and costs far less than replacement hiring. It requires a receiving manager who has the full picture — transferring a problem without disclosure destroys trust between managers and ends badly.

Reversion after promotion. Where someone was promoted into management and is struggling, an honest conversation about returning to a senior individual contributor role, without loss of pay, is frequently welcomed. Many people accept management promotions because that is the only advancement path on offer, not because they want the job. A dual career track prevents this problem at source.

Intensive coaching for a defined period. Structured, time-boxed, with a specific skill focus and a named coach. This is a PIP without the jeopardy — appropriate when the gap is clearly skill-based and the person's engagement is high.

A frank conversation about fit. Sometimes the most respectful option is to say plainly that the role does not look like the right one, and to ask what the person wants. A surprising number of these conversations end with the employee expressing relief, and a managed transition on agreed terms serves both sides better than sixty days of measured jeopardy followed by the same outcome.

Fixing the system. Where the constraint is resources, targets, tooling or process, fix that first and reassess. Performance-managing an individual through a systemic constraint is the most common and most wasteful error in this entire area.

The decision rule is straightforward: choose the instrument that matches the diagnosis. A PIP is the right answer for a specific and reasonably narrow set of situations — persistent, material, individually-caused underperformance that has survived clear feedback and genuine support. Used there, it works. Used everywhere, it stops working anywhere.

Frequently asked questions

Is a performance improvement plan legally required before termination in India? There is no general statutory requirement to run a PIP before ending employment for performance. However, the lawful route depends on the employee's category, applicable rules and contract terms, and demonstrable process fairness materially strengthens the employer's position in any dispute. Take specific legal advice for each case rather than relying on a general rule.

How long should a PIP be? Typically 30 to 90 days, matched to the natural cycle of the role. A period too short to allow measurable change is unfair and unconvincing; a period so long it drifts is unhelpful to everyone.

Can an employee refuse to sign the PIP? Yes. Record that the document was provided and that the employee declined to sign, give them a copy, and proceed. Refusal to sign is not refusal to be bound by role expectations. It is, however, worth asking why — the reason sometimes reveals a legitimate objection to the plan's content.

What is the difference between a PIP and disciplinary action? A PIP addresses capability and performance: the person is trying but not delivering to standard. Disciplinary action addresses conduct: rule-breaking, dishonesty, harassment, insubordination. The processes, evidentiary approach and outcomes differ, and they should not be blended.

Should we tell the team someone is on a PIP? No. It is confidential. If workload is being redistributed, communicate the operational change without the reason. Team members will often infer something; that is different from HR or the manager confirming it.

Can an employee be put on a PIP during their notice period? It serves no purpose. If they have resigned, manage the handover and let them leave professionally. Initiating performance management after a resignation reads as punitive and creates unnecessary risk.

What if the employee's performance is affected by their manager? Investigate before initiating. Look at the manager's other direct reports, past performance in previous roles, and any feedback the employee has given. A PIP issued by the cause of the problem will fail, and you will lose someone who might have thrived elsewhere in the organisation.

Can a PIP be extended? Once, where genuine progress is evident and the trajectory suggests the gap will close, with revised objectives and a documented reason. Repeated extension turns a defined process into indefinite jeopardy and undermines the credibility of the whole mechanism.

What documentation should be retained, and for how long? Retain the plan, all check-in records, evidence, support provided and the closing assessment, against the employee record with restricted access. Retention should follow your standard employment record policy, which typically extends for a period after employment ends. Confirm the period applicable to your organisation.

Does a completed PIP need to appear in future references? No. References should state the facts you are prepared to confirm — typically role, dates and, where your policy permits, eligibility for rehire. Performance management history is not normally included, and disclosing it creates risk.

Conclusion: run it honestly or not at all

The value of a performance improvement plan comes entirely from being real. A real plan names a specific gap, sets objectives a neutral observer could assess, provides support the company actually delivers, holds weekly conversations that genuinely happen, and reaches an outcome that could plausibly have gone either way.

Everything that makes a PIP feel safer to the company — the vague objectives, the absent support column, the silent middle weeks, the predetermined ending — is precisely what makes it weaker, both as a management tool and as a record. Employees can tell the difference immediately. So can the rest of the team, and so, later, can anyone reviewing the file.

Get the diagnosis right first. Fix clarity problems with clarity, skill problems with training, fit problems with role changes, and system problems with system changes. Reserve the PIP for the narrower set of cases it actually addresses, run those cases properly, and accept that some will succeed. Those are the ones that pay for the whole process.

CozyHR keeps goals, review records, feedback notes and performance documentation against each employee, with controlled access and a clear timeline — so managers can see the history before they act, and HR can see whether check-ins are actually happening. If your performance records currently live in mailboxes and memory, take CozyHR for a spin.