1. LandOffer
  2. Blog
  3. All articles
  4. Create a Performance Improvement Plan with Observable Success Criteria

People Management

Create a Performance Improvement Plan with Observable Success Criteria

Draft an HR-reviewed performance improvement plan with observable criteria, support, eligible opportunities, fair evidence boundaries and reasoned review decisions.

10 min readLandOffer team

Create a performance improvement plan by connecting documented work gaps to observable behavior, a realistic opportunity to demonstrate it, promised support, and a defined review method. Have the draft reviewed through your employer's HR process before delivery. State what counts as success, what is excluded, who supplies support, and how mixed or insufficient evidence will be reviewed. Keep the stated success criteria separate from any later employment decision.

This LandOffer.ai guide includes a completed fictional plan, criterion rewrites, and midpoint and closing records. No real employee information, HR approval, personnel decision, or workplace result is used. The example is an editorial design, not a legally sufficient form or a universal employer procedure.

Two colleagues review a visible practical standard beside the tools and support needed to improve the work.

Confirm the process and describe the work gap

A formal PIP is different from an ordinary development goal or an employee's weekly evidence log. As the manager, you are defining a performance concern and the opportunity to address it through the organization's process. Consult the appropriate HR or employee-relations contact about suitability, required language, review, delivery, and records before issuing it.

William & Mary's supervisor guidance connects a PIP to clear acceptable behavior, measurement, a timeline, follow-up, and assistance. It requires advance HR approval in its process. Its duration rules and employee-category provisions belong to that institution; they do not establish the required period or process at another employer.

Describe the gap through specific work examples and the applicable expectation. “The receiving engineer could not identify the validation performed in two handoffs” is more useful than “you lack ownership.” Keep the evidence relevant and appropriately private. Do not infer attitude, intent, or a medical explanation from an observed work problem.

Check the expectations against the current role and explain the required work in plain language. If the underlying standard is unclear or the work opportunity is unavailable, resolve that with HR rather than making the employee responsible for guessing what a successful outcome would look like.

Turn judgment words into observable criteria

A useful criterion identifies the behavior or output, the circumstances in which it applies, the evidence to examine, and the threshold. Specify which work version and event time the reviewer will examine. Defining the denominator and exclusions lets both participants identify the same eligible work.

For example, counting completed handoffs is not enough if some were canceled, blocked by unavailable access, or assigned too late for the stated process. Define an eligible opportunity before evaluation. Record exceptions with reasons and the person reviewing them; do not quietly remove inconvenient evidence or count an unavailable task as a failure.

The University of Oregon's PIP FAQ describes specific measurable goals and a documented follow-up schedule. It also recommends HR consultation when goals are mixed or success is unclear, and employee input on proposed steps. That is guidance within its own employment framework, not a transferable rule about consequences, timing, or records.

Separate requirements from preferences. If a concise note with four required fields is acceptable, do not later mark it unsuccessful because the writing style differs from your preferred example. If quality matters, describe the content standard rather than relying on “professional,” “proactive,” or “better communication” without explanation.

Completed rewrites of vague expectations

The following rewrites belong to the fictional case used below. They are not general thresholds for engineering work.

Vague expectation Observable replacement Evidence and boundary
Show more ownership Before transferring a qualifying change, include the change purpose, validation performed and result, unresolved risk or explicit none, and receiving owner in the handoff note. Review the note version present at transfer, not a later repair. All four fields must be substantive; a placeholder does not satisfy the requirement.
Communicate risks earlier For each qualifying risk discovered before transfer, notify the manager and receiving owner through the agreed work channel before the handoff, stating impact and a requested decision or next step. Compare discovery, notification, and transfer records. A risk first discovered afterward is outside this pre-transfer criterion, though it still needs ordinary handling.
Be consistently reliable The final four qualifying handoff notes must meet the four-field criterion before transfer; each qualifying pre-transfer risk during evaluation must meet the notification criterion. Define qualifying work and excluded blockers in advance. Do not count unrelated delivery dates or code defects as hidden additional tests.

The rewrite makes evaluation more transparent, but it does not prove that the expectations are reasonable for a particular employee or role. That judgment still requires knowledge of the actual work, support, employer process, and HR review.

Check whether the employee will have enough qualifying opportunities. A four-item standard cannot be evaluated fairly from two available items by pretending the other two failed. Plan how the manager will respond if assignments, access, or dependencies prevent the intended observation.

Completed fictional plan with support and opportunities

Carmen is an engineer on a laboratory-equipment inventory application. Manager Derek has documented two prior handoffs that omitted validation results and a receiving owner despite earlier coaching. Those are invented examples of work gaps, not real personnel history. The plan concerns handoff documentation and risk communication, not Carmen's personality or medical circumstances.

In the fictional process, HR reviewer Anika reviews and approves version 1 before delivery. The learning and evaluation period is six weeks, chosen for this case. No source establishes six weeks as a required or sufficient duration.

Plan element Completed fictional agreement for the example
Scope and baseline Address the missing handoff information and pre-transfer risk communication described in the two documented examples. Keep ordinary role duties separate from these stated evaluation criteria.
Success criterion 1 In Weeks 3–6, the final four qualifying handoff notes contain the four substantive fields before transfer: purpose, validation/result, unresolved risk or none, receiving owner.
Success criterion 2 Every qualifying risk discovered before transfer in Weeks 3–6 is notified before handoff to Derek and the receiving owner, with impact and a requested decision or next step.
Qualifying opportunity A bounded change assigned with the approved note template, required work access, a named receiving owner, and sufficient time to prepare the note. Derek plans eight such changes during evaluation.
Exclusions Canceled work, unavailable required access, or externally blocked work without a transferable result is excluded from the handoff denominator. Derek records the reason and reviews disputed exclusions with Anika. Exclusion does not erase ordinary communication obligations.
Support and owners Derek supplies the template and one completed example before Week 1. Technical mentor Hugo provides two practice reviews in Weeks 1–2 and a weekly question slot. Derek removes Carmen's optional reporting cleanup to protect preparation time.
Review schedule Weekly private check-ins; a written midpoint record at the end of Week 3; a closing review at the end of Week 6 with Anika consulted on mixed or insufficient evidence.
Records and response Keep plan versions, agreed work evidence, support delivered, employee comments, exclusions, and review decisions in the approved restricted location. Carmen can identify factual disagreements and support gaps through the designated process.
Possible outcomes Meet the stated criteria and proceed under the employer's continuing expectations, or have unmet or unclear results reviewed for the appropriate next step. Further formal action may be considered under the applicable process; no employment outcome is predetermined in this example.

Derek explains the criteria privately and asks Carmen to describe the required handoff in her own words. She points out that receiving owners are sometimes assigned late. Derek takes responsibility for naming the receiver when assigning qualifying work; if that input is missing, the task is not silently scored against her.

Acknowledgment and agreement are not treated as interchangeable. The example records that Carmen received the plan and supplied comments; it does not imply that a signature proves she agrees with every statement. How acknowledgment and any disagreement are handled must follow the employer's actual process.

Record the midpoint without moving the standard

At the end of Week 3, two qualifying evaluation handoffs have occurred. Both notes contain the four fields before transfer. One identified pre-transfer risk was communicated to both required recipients with its impact and requested decision. These are fictional observations, not an actual test of the plan.

The midpoint also records a support failure. Hugo's weekly question slot was canceled once, and Derek had not supplied a replacement. Carmen says the next change includes unfamiliar validation evidence. Derek and Hugo hold the replacement question slot before that change proceeds; the midpoint record confirms delivery without adding an employee requirement.

The midpoint finding is “early evidence consistent with the criteria; final-four consistency not yet established.” Two successful notes do not satisfy a four-note closing standard. Derek retains the original criteria and continues the planned opportunities.

UC Berkeley's employee-relations guidance describes constructive feedback, assistance or reprioritization, and a PIP process with regular feedback and documentation after unsuccessful coaching. It advises consultation with HR. Its classifications and timeframes are institution-specific; the useful principle here is to document both expectations and the support actually provided.

If a criterion needs revision because it was unclear or an input was unavailable, preserve the original version, the reason, HR review, and the communicated revision. Do not change the threshold retrospectively and describe the new rule as if it had been present from the start.

Completed closing record with a mixed result

The Week 6 review reconciles the planned opportunities, actual eligible work, and observed criteria. It does not reduce the outcome to whether Derek feels more confident about Carmen.

A review record is checked beside completed work examples, with one unresolved item kept visible for a bounded next decision.
Review item Completed fictional closing record
Opportunity count Eight changes were planned. One was externally blocked without a transferable result and recorded as excluded. Seven qualifying handoffs were available for review.
Criterion 1 evidence Notes 1–5 met the four-field requirement before transfer. Note 6 omitted the validation result until after transfer. Note 7 met the requirement. The final four notes are 4–7, so the consistency criterion is not met.
Criterion 2 evidence Three qualifying pre-transfer risks occurred; all three notifications reached Derek and the receiving owner before handoff with impact and a requested next step. Criterion 2 is met.
Support and comments Template and practice reviews were delivered. The canceled mentor slot was replaced as recorded at midpoint. Carmen acknowledges the missing result in Note 6 and asks to use the same pre-transfer check on further work. No private personal explanation is invented.
Reviewed closing decision Derek and Anika record a mixed result, not successful completion and not automatic dismissal. In this fictional process they approve two additional weeks with four qualifying opportunities and the same support, prospectively extending the evaluation window through Week 8 while retaining both criteria, followed by a recorded review at the end of Week 8.

The additional observation period is a case-specific reviewed decision. It is not a promise that every employer must extend a plan or that the next review will produce a particular outcome. The final-four criterion still applies to the rolling final four qualifying notes; Note 6 remains in the record. It is not deleted to manufacture improvement.

If four further qualifying notes occur, the rolling final group at the next review will be Notes 8–11. All four must meet the original criterion before transfer; Note 6 remains part of the historical record. Derek and Anika do not assume those future notes will succeed. They preserve the same two-opportunities-per-week cadence and will review actual evidence, missing opportunities, and support before deciding the next step.

The closing communication states the mixed findings, the approved observation period, support owners, and the next review point. It avoids promising continued employment, threatening an automatic consequence, or describing a future decision as already made. Any further action remains subject to the actual employer process and qualified review.

Check the plan before delivery and after review

Before issuing a real plan, verify that the work examples are accurate, the standard is relevant, the evidence method is understandable, support has named owners, and enough opportunities exist. Ask HR to review the required process and language. Use the employee's input to identify factual errors and missing resources without turning the meeting into a debate about personality.

After each review, distinguish criterion met, criterion unmet, and evidence insufficient. Record support delivered and external constraints beside the employee's work evidence. Keep health, leave, accommodation, or other sensitive matters in their appropriate channels; do not diagnose causes or improvise policy decisions in the plan.

Save the reviewed version, eligible-work record, employee comments, support delivery, and next review owner in the approved location. Return to LandOffer.ai for related management guidance after those records are complete. A clear plan makes the standard and decision reviewable; it cannot guarantee an employment result.

Sources and Further Reading