A performance improvement plan needs that connection between the expected standard and documented examples. Show the work gap, the assistance proposed, and the evidence the review will examine. Leave room for the employee's perspective and for the arrangements that still need agreement.
The example here is fictional and focuses on preparing reports. It is a working-document exercise, not an actual personnel record or an employment decision.
Start with the same standard for each example
The supplied work standard requires every report to state its reporting period, source ID, and next owner. When a source is absent, the report must explicitly say that the source is pending.
The three supplied documents show:
| Document | Reporting period | Source ID or pending-source note | Next owner |
|---|---|---|---|
| D1 | Present | Blank | A |
| D2 | Present | Present | Present |
| D3 | Present | Blank | B |
The documented gap is specific: D1 and D3 omit the required source reference or pending-source note. D2 contains all three required fields. This evidence does not establish the writer's attitude, motivation, or reasons for the omissions.
The U.S. Office of Personnel Management's supervisor guide emphasizes observable examples, clear expectations, assistance, and review documentation. Its employment procedures address a federal context; this exercise uses only those work-document principles, with actual employer requirements left to the relevant private process. Read the OPM guide.
Turn the gap into a concrete expectation
Compare these two versions:
Vague: Be more professional and show better attention to detail.
Work-specific proposal: For the next two assigned reports, include the reporting period, source ID or explicit pending-source note, and next owner. Review each report against the same three-field checklist.
The second version tells both people what to examine. It also covers the situation where a source has not arrived; the employee is not being asked to invent an ID to satisfy a field.
“Next two assigned reports” is the exercise's proposed work sample, not a universal review period. Actual dates, assignments, and employer requirements remain to be confirmed. Avoid placing a ready-made deadline into a real plan simply because a template supplied one.
Put the assistance beside the expectation
The proposed support is a 15-minute source-inventory walkthrough, a model report, and a check-in. Its availability, date, and responsible person still need confirmation.
| Plan element | Working entry |
|---|---|
| Documented gap | D1 and D3 lack source ID or pending-source note. |
| Proposed expectation | Required fields present in the next two assigned reports. |
| Proposed assistance | Source-inventory walkthrough, model report, and check-in. |
| Employee perspective | Blank; invite the employee's explanation and support needs. |
| Review arrangements | Dates, owner, and actual requirements to confirm. |
| Review evidence | Examine assigned reports against the same checklist. |
| Result | Blank; no later reports or improvement findings supplied. |
A proposed walkthrough is not evidence that support was delivered. A filled expectation is not evidence that improvement occurred. Keep those records separate so the review can use what actually happened.
Make the conversation two-sided
Ask whether the standard was clear, whether the source inventory is accessible, and what support would help the person complete the required fields. Record their actual explanation rather than filling it in with a likely-sounding cause.
The plan can then identify any change to the proposed assistance or review arrangement. It should be clear which wording is a proposal, which facts have been documented, and which arrangements have been agreed. A checkbox in a worksheet does not establish another person's agreement or determine their performance.
Use the fictional working example
Select the standard to inspect D1, D2, and D3. Compare the vague instruction with the specific expectation, then open the assistance and review sections to see what remains unconfirmed.
Use the blank plan to practice connecting a sanitized work example, standard, expectation, assistance, perspective, and review evidence. Missing standard or example produces a visible reminder, with typing retained during validation. Confirm before resetting the form. Keep actual employee details and formal review records in the organization's private process; this public training example does not store personnel records or trigger an HR action.
Copy this prompt for the training worksheet
Create a complete self-contained HTML performance-improvement planning
training worksheet. Use only fictional/sanitized work examples.
My work standard: [observable requirement]. Documented examples:
[facts]. Proposed expectation/support/review: [details]. Employee
perspective and unconfirmed arrangements: [blank/open questions].
Include a separate fictional report-preparation case. Standard: every
report states reportingperiod, sourceID, nextowner; absent source needs
explicit pending-source note. D1 periodpresent/sourceblank/nextownerA;
D2 allthreepresent; D3 periodpresent/sourceblank/nextownerB. Gap D1/D3
omit source or pending note. Do not infer attitude, motivation, or cause.
Compare “Be more professional” with proposed nexttwo assignedreports
containing all required fields, checked against the same checklist.
Propose15minute sourceinventory walkthrough, modelreport, checkin;
availability/date/owner still to confirm. Employee perspective blank.
Actual reviewperiod/employerrequirements to confirm; no universal
deadline, federal timelines, consequences, signatures, or legal advice.
No later performance results supplied; planned assistance is not delivered
support and no checkbox certifies improvement/agreement or triggers HR.
Allow standard/evidence inspection, vague-vs-specific comparison, and
support/review-status views. Separate blank plan, named missing-standard/
example feedback, retained entries across views/validation, confirmed
reset. Explain actual personnel records use the organization's private
process. No ratings, discipline recommendations, notifications, storage,
or actual employment action. Use labeled keyboard-accessible controls,
visible focus, system fonts at least16px, readable360px layout without
horizontal scrolling, inline CSS/JavaScript, no dependencies. Complete HTML.
Revise the instruction someone has to use
Before reusing the training plan, read its expectation as though you were preparing the next report. Could you tell what to do when the source is missing? In NOS, directly revise the visible expectation to include that pending-source option. A clearer instruction gives the review a fairer, more concrete piece of work to discuss.