Performance Improvement Plan (PIP) Builder

A performance improvement plan, usually called a PIP, is a structured period in which a manager and an employee work towards a defined standard. A good one is not a formality before dismissal. It says what is wrong, what good looks like, when progress will be checked and what help is offered. This builder produces that document with the dates worked out, so the plan is concrete from the first meeting.

The inputs

Name the company, the employee and their role, and the manager. Choose the start date, a plan length of 30, 60 or 90 days, and a check-in interval of every week, every two weeks or every month. Then type the performance concerns with examples, the goals, and the support the company will give, one per line each. A switch adds an explanation of the possible outcomes.

Goals that can be measured

Each goal line has two parts separated by a bar: the goal and how it is measured. The tool prints them as a table with the numbers in a narrow first column, the goal, and the measure. “Answer 90% of tickets within the 8-hour target | weekly ticket report” is a goal a manager and employee can both check. Poor goals, such as “improve communication”, cannot be measured and lead to arguments at the end. If you omit a measure, the table says it is “Discussed with manager”, which is a signal to add one.

Dates and outcomes

The end date is the start date plus the plan length, and the check-ins are placed at each interval from the start, with the final review on the end date. With a start on 16 November 2026, a 60-day plan and check-ins every two weeks, the end is 15 January 2027 and the review dates are 30 November 2026, 14 December 2026, 28 December 2026, 11 January 2027 and 15 January 2027 (final review). The outcomes section says the plan may end with the goals met and normal performance management resuming, with an extension where there has been progress, or, if the required standard is still not met, with further action under the company’s procedure, and that progress is reviewed at each check-in and recorded in writing.

A worked example

The sample is a plan for Rohit Sen, a Support Engineer at Northwind Software Pvt Ltd, managed by Karan Mehta. The concerns are that 41% of tickets missed the 8-hour response target in September and October and that three escalations came from unanswered follow-ups. The goals are to answer 90% of tickets within the target, to close every follow-up within two working days and to complete the escalation handling course by day 30. Support includes a weekly 30-minute one-to-one, pairing with a senior engineer on escalations and paid time to take the course. The document is two pages with signature lines for manager and employee.

Running the plan

Hold the first meeting before the plan starts, explain every goal and give a copy. At each check-in, review the measures, note what has improved and what has not, and write a short summary. Offer the support you promised, since a plan without help is hard to defend. Treat the employee with respect throughout, and keep the matter confidential.

Limits

Employment law and company policy decide how performance is managed and what notice and process are needed before dismissal. The tool gives a clear structure, dates and a table, not a legal review. It is a general template, not legal advice, so consult HR or a lawyer if the case is complex or the employee is protected by special rules.

Related tools

• Warning Letter Generator records a formal warning where the problem is conduct or a policy breach.
• Appraisal & Increment Letter Generator covers positive review outcomes.
• Self-Appraisal Builder helps an employee present their own view of the same period.
• OKR Planner & Scorer turns goals into scored key results when the aim is growth, not remedy.