Performance improvement plan, Support Analyst, Solent Data Services
Performance improvement plan letter with measurable targets
A performance improvement plan letter sets measurable targets, the support offered and the date performance will be judged. This two page letter from a data services firm puts a support analyst on a 60 day plan, states the gap in numbers, lists three objectives with targets and sets four review dates.
The document, page by page
Every page as it renders and as it prints, with nothing summarised. Read the wording before you reuse it.
Section by section
What each section is for, so you can keep the ones you need and drop the rest.
- Underline letterhead and footer
- The firm's name and contact line, and a confidential footer with page numbers.
- Addressee and subject
- Private and confidential, the employee and the plan's start and end dates.
- Where performance stands
- Three months of results against the standard, with one strength noted.
- Key figures
- 58 percent, the 75 percent standard and 14 overdue tickets.
- Objectives table
- Three objectives, each with a measure, a target and when it is judged.
- Support you will have
- Coaching, shadowing, a course and a daily report.
- Reviews and outcomes
- Four review dates, the three possible outcomes and the right to a support person.
- Signature block
- The team lead's name and title.
Turning a vague complaint into a target
Most performance problems start as an impression: slow, careless, not a team player. A plan built on impressions fails, because the employee cannot see what to change and a reviewer cannot judge whether it changed. Start by asking what the impression is based on, then find the figure that shows it. Slow becomes tickets resolved on first contact; careless becomes errors found in a quality audit; not a team player becomes handovers missed. Workplace advisory bodies recommend agreeing standards that are clear, measurable and achievable, and giving the support needed to reach them, which is the structure of this letter.
Weak objectives and measurable ones
Improve communication with customers is weak; update every open ticket at least every 48 hours, measured by the ticket ageing report, is measurable. Be more productive is weak; resolve 75 percent of tickets on first contact over September and October is measurable. Show more initiative is weak and usually best left out unless it can be tied to something observable, such as articles written for the knowledge base. Three objectives are plenty. More than five spreads the employee's effort thinly and makes the outcome letter hard to write.
How to adapt this document
Replace the figures with your own data for at least two months, and keep one genuine strength in the opening paragraph. Rebuild the objectives table so each row has a measure, its source, a target and a date. List only support you will actually provide, with days and times. Set reviews every two weeks and put them in both diaries before sending. Check your performance policy and any award or agreement for steps that must come before or after a plan, and use the same names for those steps in the outcomes paragraph.
What makes this document work
The gap is a number, and so is the strength
First contact resolution of 58 percent against a 75 percent standard and a 79 percent team average, plus 14 overdue tickets in August, define the problem. The same paragraph records a satisfaction score of 4.4 out of 5 in line with the team, so the plan reads as fair rather than a case being built.
Each objective has a measure and a source
The table names the report each figure comes from, the target and when it is judged: 75 percent or more, 2 or fewer overdue tickets a month, 60 percent of tickets linked to articles. Nobody can argue later about what success meant.
Outcomes are said before they happen
The closing paragraph lists the three outcomes, from closing the plan to the formal procedure that can end in dismissal, and promises an update at every review. An employee who reads that on day one cannot say the consequence came as a surprise.
Questions people ask
What is a sensible length for a PIP, 30, 60 or 90 days?
Long enough for the measures to move and for the employee to use the support, usually 30 to 90 days. Sixty days suits a role measured monthly, like this one, because it gives two full months of data. A plan too short to show change looks like a formality; one that runs for six months loses urgency and delays a decision for both sides.
What happens if an employee does not meet the plan?
The employer decides between extending it once, if progress is real, and moving to its formal performance or capability procedure, which may lead to warnings and eventually dismissal. The decision should follow the process the letter described. Write the outcome in a separate letter that records each target against the result, rather than telling the employee in passing.
Should the employee sign the PIP letter?
Asking for a signature to confirm receipt is common, but it should be clear that signing does not mean agreeing with the assessment. Some employers add a received by line; others rely on an email reply. If the employee refuses to sign, note the date the letter was given and by whom, and carry on with the plan.
Can a performance improvement plan be used during probation?
It can, but probation usually has its own review process and a shorter path to ending employment, so a full plan is less common there. Where a new employee is close to the standard, a short plan inside probation can be a fair way to decide whether to confirm, extend or end it. State which process applies so the employee knows.
What makes a PIP objective measurable?
It names the measure, where the figure comes from, the target and the period it is judged over. Keep customers updated is a wish; two or fewer tickets past the response target with no update, per month, from the service desk report, is an objective. If you cannot say where the number will come from, the objective is not ready to put in a letter.
Build your own in about a minute
The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.
Make one like thisOther document examples
Resignation withdrawal letter asking to stay on
A resignation can usually be withdrawn only if the employer agrees, so a withdrawal letter asks rather than tells. This one page letter from a laboratory technician asks to stay after the job he resigned for fell through, accepts that the decision belongs to his manager and commits to finishing a validation project.
Failed probation letter with reasons, notice and final pay
A failed probation letter ends employment during probation, gives the reasons, and sets out the notice the contract requires and the final pay. This one page letter from a hotel group ends a front office supervisor's employment in month five, tying the decision to two recorded reviews and paying a week in lieu.
Employee recognition letter that names one specific result
An employee recognition letter works when it names exactly what the person did and what difference it made, so it can sit on their file as evidence rather than a pleasantry. This one thanks a dispatcher for keeping 148 deliveries moving through a six hour routing outage, and puts the result in three numbers.
Want the steps in the builder? Read Write the plan from a description, then Add the objectives table and timeline. For everything this generator can do, see the document maker.
Sources
Written and checked by the OneCraft team. Last checked .