How do I write a useful performance improvement plan?

Write a useful performance improvement plan by naming the specific work gap, the required result, the support being provided and the evidence each review will examine. Make the workload and timeline feasible, hear the employee's account and record the manager's commitments too. A document saying improve immediately leaves both people guessing about what happens tomorrow.

I would want the employee to leave the conversation able to describe an ordinary successful day. Not a personality transformation. Not a promise to care more. A clear account of the work, the help available and the standard the next review will use.

Describe the work that missed the requirement

Start with dated examples and the actual requirement. Identify what happened, the effect on the work and what remains uncertain. Replace labels such as unreliable with specific observations the employee can examine and answer.

Ask about missing information, unclear priorities, skills, tools, workload and authority. Those questions do not excuse every shortfall; they help establish what needs to change. A manager should not prescribe training when the necessary customer record is locked in the manager's inbox.

Give the employee space to explain and correct the factual account. If the evidence changes, update the account openly. Do not retain an inaccurate example merely because the plan is already formatted.

The existing standards discussion examines making expectations usable. A written improvement plan adds a defined review period, specific support and a record of how the proposed change will be assessed.

Keep the plan within the appropriate employment process

Identify the applicable organizational procedure and obtain appropriate HR or employment advice before using a formal plan. Clarify its status, review route and any stated consequences. Do not present a generic online document as a completed legal process.

The U.S. EEOC's performance guidance emphasizes clear expectations and consistently applied standards. It also addresses reasonable accommodation when disability-related needs arise during a performance discussion. A relevant request needs the proper process; a manager should not treat asking for support as punishment-worthy behavior.

Do not diagnose an employee or demand personal medical details as an improvised management exercise. Use the responsible confidential process for questions requiring it. Share performance records only with people who appropriately need them.

This article develops an operational writing example, not a dismissal decision. The appropriate response to conduct, capability, protected leave or accommodation issues depends on the actual facts and applicable requirements.

Make the objective specific and controllable

State the result, counted work, deadline source and required evidence. Use a standard related to the actual role. Decide how work blocked by someone else's missing input will be recorded and resolved.

Acas, Britain's workplace advisory body, describes improvement plans with specific objectives, a reasonable timeline and necessary support or training, discussed with the employee and recorded in writing. Those practical questions travel well; its employment procedures should not be treated as U.S. legal rules.

A speed target also needs the quality conditions that make speed useful. Closing a customer case without the required explanation can improve a dashboard while leaving the actual problem untouched.

Define the review method before collecting results. If the work varies substantially, use appropriate comparable categories and explain them. Do not quietly give one employee harder assignments and then interpret a lower raw count as a clean comparison.

An original four-week support case

Consider a wholly fictional customer-support role. A prior review found 26 assigned cases in one week. Two lacked required internal information throughout the relevant window. The manager records those as blocked work to resolve separately, leaving 24 eligible cases for this bounded timeliness measure.

Of those 24, eighteen received the required usable update within the agreed window. That is 75 percent. The other six were late. The case supplies a confirmed feasible service window and comparable case types; it does not establish a universal support-industry target.

The proposed plan covers four weeks, with a checkpoint each week. For a week with 24 comparable eligible cases, at least 90 percent must receive the update on time. The employee must also meet the specified information and record requirements on all 24.

Ninety percent of 24 is 21.6, so the smallest whole-case count meeting the timeliness target is 22. Twenty-one would be only 87.5 percent. Do not round 21.6 down and call that compliance.

Timeliness and quality remain separate tests. For this supplied example, the quality record must show the correct case reference, the supported current answer, any unresolved dependency and the next responsible contact. No employee is expected to invent an answer to satisfy the clock.

Give the manager deliverables too

Before the review begins, the manager provides the required record access, written examples, a current escalation route and a clear priority rule. The employee receives training on the actual workflow and practice with feedback.

The manager agrees to review blocked cases promptly through the named route. The employee agrees to flag missing inputs with the case reference and relevant deadline. Neither commitment should be left as an unmeasurable instruction to communicate better.

If an input is unavailable, record what happened and what the manager did about it. A blocked case does not disappear from customer obligations merely because it is outside the employee's eligible measurement set.

Keep the support delivery record beside the results. If promised training was canceled or access failed, establish that fact before interpreting the review. A plan measures performance under actual conditions, not under support that existed only on paper.

Fit the plan inside paid time

The fictional employee has forty paid hours a week over four weeks, totaling 160 hours. Complete employer cost is $30 an hour, with all ordinary payroll-related costs included, so $4,800 is separately funded for the period.

Routine work requires 140 of those hours. It includes 96 hours for the planned 24 comparable weekly cases at one paid hour each across four weeks, including checking, plus 44 hours for all other tasks and blocked-case handling.

The plan adds eight training hours, four coaching hours and four practice hours within the existing paid schedule. Those sixteen hours take total employee use to 156 hours, leaving four hours of available margin. No required homework or unpaid catch-up is assumed.

The manager separately needs four meeting hours, two preparation hours and two review hours. All eight are available after other commitments and funded at a complete $50 hourly cost, totaling $400.

A $500 separate support allocation covers that manager cost and leaves $100. The employee's training hours are already inside the $4,800 ordinary payroll; adding their cost again would duplicate it. Other business expenses and customer commitments remain separately funded in this limited staffing example.

These hours and rates are original inputs, not a wage rule or proof that another role has enough capacity. If the actual plan adds work to an already full schedule, revise the work allocation or obtain properly funded support before promising a fair opportunity to improve.

Read two checkpoints with both measures visible

At the first fictional checkpoint, 23 of 24 eligible cases receive the required update on time. Timeliness is 95.8 percent when displayed to one decimal place, above the 90 percent requirement.

However, one of the 24 cases lacks a required part of the information record. Only 23 meet the quality condition. The week therefore does not meet both supplied objectives. The timing result should be recognized accurately without hiding the remaining quality issue.

At the second checkpoint, 22 of 24 are timely, or 91.7 percent to one decimal place, and all 24 meet the quality condition. Both objectives are met for that week.

Scroll across to compare the original checkpoints. The quality gap and late cases are separate measures, not necessarily different people or cases to add together.

No results for weeks three and four are supplied. One successful week does not establish sustained completion of the four-week plan. Nor do these observations isolate whether training, clearer inputs, case mix or another factor caused the change.

Hold a review the employee can use

Bring the actual work examples, the agreed criteria and the support record. Describe what improved, what remains unresolved and what the employee says about it. Separate a missing record from a proven substantive error, and investigate the difference.

Agree the next specific action within the appropriate process. It might be practice on a particular task, resolving an access problem or continuing the current support while gathering the next week's evidence. Record who is responsible and when the action will be checked.

If work volume or circumstances change, explain how the review will remain fair and relevant. Do not rewrite a past target after seeing the result. A prospectively revised plan needs its own clear version, suitable review and communication.

Any formal consequence requires the actual organizational and legal process. A percentage in this example is not automatic permission to discipline, dismiss or overlook an accommodation question.

Leave with a usable written plan

1. Specific observed gap and the employee's account.
2. Job-related objectives, eligible work and evidence.
3. Feasible period and regular review dates.
4. Manager support, access, training and escalation commitments.
5. Paid time and capacity for both improvement work and normal obligations.
6. How changed circumstances and disputed evidence are handled.
7. Plan status, appropriate review route and clearly explained next steps.

The document should make the next conversation more precise. If the employee still cannot tell what to do differently, or the manager cannot tell whether the promised help arrived, the plan needs more work before the clock becomes its main feature.