Let me be blunt about something. In many Indian companies, a PIP is a termination process with a polite name. The manager has already decided. HR is asked to “put the person on a PIP” so the file looks clean. Thirty or sixty days later, the person is asked to resign. Everyone in the building knows it, including the person on the plan.
That is my opinion, and I will say it plainly: if you already know you will not keep the person whatever happens, do not run a PIP. Have the honest conversation, agree a separation with dignity, and spare everybody the theatre. A PIP is only worth the paper if there is a real chance of the employee coming through it.
What a PIP is meant to be
A performance improvement plan is a time-bound, written agreement between a manager and an employee. It names the gap between expected and actual performance, sets specific targets to close it, states what support the company will provide, and fixes dates when progress will be reviewed. That is all. It is not a punishment, and it is not a legal shield by itself.
Before opening one, ask a question that gets skipped constantly: is this a performance problem at all? Poor results from a person who was never told what good looks like, who changed role last month, who was given a broken tool, or who is dealing with a health or family situation, is a different conversation. Misconduct is yet another track and goes through a disciplinary process, not a PIP. Mixing them up is how companies end up in avoidable disputes.
Before the plan: three checks
- Has the employee heard the feedback, clearly, before? If the first time they learn their work is unsatisfactory is the day the PIP document arrives, you have skipped a step. Appraisal comments, emails and one-to-one notes should show the issue was raised earlier.
- Was the expectation fair and the same as for peers? If three people in the team miss the same target and only one gets a PIP, ask why.
- Is the cause skill or will? Someone who cannot do the task needs training, a mentor or a different role. Someone who can but does not needs a different kind of conversation altogether.
Writing goals that can be judged
The commonest flaw I see described in PIP documents is vagueness: “improve communication”, “show more ownership”, “be proactive”. Nobody can pass or fail those. They hand the manager a free hand to declare failure at the end, and that is exactly what a court or a labour officer will notice.
Good goals are observable. “Close at least 85% of assigned tickets within the agreed turnaround each week” can be checked. “Submit the weekly report by Friday noon without a reminder, four weeks out of five” can be checked. “Reduce rework found in code review to fewer than one in five submissions” can be checked. Keep to three or four goals at most. Ten goals is a trap, not a plan.
Be honest about duration. Thirty days is rarely enough for work that has long cycles, such as a sales employee whose deals take three months. Sixty to ninety days is more common, with the length tied to how quickly the work produces evidence. There is no statutory number here for ordinary private-sector employees; it comes from your policy and what is reasonable.
The support half that gets forgotten
Every PIP should list what the company will do. A weekly check-in of thirty minutes, put in the calendar and actually held. A named buddy or mentor. A course or a pairing session if the gap is technical. Access to the tools and information the person needs. If the plan lists only what the employee must do, it is a one-way demand.
Write notes after each check-in, and share them with the employee. Two lines is enough: what was agreed, what progress was seen. This protects both sides. The employee sees where they stand without waiting for day ninety. The manager has a record that is not reconstructed from memory.
Where HR should push back
The HR person in this process has an unglamorous job: asking the manager awkward questions. Has the person had a fair run? Is the manager’s own behaviour part of the problem? Is a goal measurable? If the employee improves but the manager still wants them out, what then? I would insist on that last question being answered before the plan begins, and I would not sign off a PIP where the honest answer is “they will be let go anyway”.
Another opinion, and I hold it firmly: a PIP should not run alongside secret recruitment of the replacement. People notice. It destroys trust in the process for everyone else on the team.
Outcomes, and the legal edge
There are three honest endings. The employee meets the goals and the plan closes, with a note that normal performance management resumes. The employee improves partly, and the plan is extended once with clear reasons. Or the employee does not meet the goals, and the company moves to the next step in its policy, which might be a role change, a notice-based separation under the contract, or, where the person is covered as a workman under industrial law, a formal process that follows the applicable rules. The route depends on the employee’s status and contract, so take legal advice for anything beyond the routine.
One more thing about fairness that has little to do with law. Employees on a PIP often resign in the first two weeks. If that happens, let them go with grace, including a proper relieving letter and clean full and final settlement. How you treat the person walking out is watched by everyone who stays.
Leave a Reply