Performance Management: Documentation That Holds Up Later

When an employee challenges a firing, the employer's defense is usually a business reason: performance. Whether that reason holds depends less on whether the performance was actually poor than on whether the record created at the time says so, says it specifically, and matches how comparable employees were treated. A file full of "meets expectations" reviews followed by a sudden termination for chronic failure is the single most common way an otherwise defensible decision becomes a jury question.

Good documentation is not about volume. It is about writing down the specific, observable thing that happened, when it happened, what was said about it, and what the employee was told to do differently.

What a usable record actually says

The test is whether a stranger reading the note two years later can tell what happened without asking the author. Conclusions fail that test; facts pass it. "Unprofessional" tells a reader nothing. "Raised voice at a client during the 9:15 call on March 4; client emailed to complain the same afternoon" tells them everything.

• Date, time, and location of the event, not just the month
• What was observed or measured, in the words a witness would use
• The standard the conduct or output fell short of, quoted from the job description or a written goal
• What the manager said to the employee, and what the employee said back
• What specific change was requested, and by when
• Any support offered — training, tools, a schedule change, reassignment of a marginal duty
• Whether other employees with similar issues were addressed the same way

Two items are worth avoiding. First, speculation about causes — health, family, personality, age, attitude. Guessing that someone is "checked out because of what's going on at home" is an inference an employee's lawyer will read aloud. Second, medical detail. If a limitation or leave need surfaces, that belongs in a confidential file and triggers a different process, not a performance note.

The documentation lifecycle

Performance records are useful only if they form a sequence a reader can follow from expectation to consequence.

1. Set the standard. Written goals or a current description of essential duties give later notes something to measure against. Our guide to job descriptions and essential functions covers how to write that baseline so it is usable.
2. Coach in real time. The first record is usually a short, dated note of a conversation. It is not discipline; it establishes that the employee was told.
3. Escalate in writing. A formal warning restates the standard, the gap, prior conversations by date, the required change, and the consequence of no change.
4. Give a defined improvement period. Specific measurable targets, a stated length, scheduled check-ins, and named support.
5. Assess honestly at the end. Write what happened against each target. If the employee met them, say so and close the plan — reopening it without a new event undermines the whole file.
6. Decide and record the reason once. The separation reason given internally, to the employee, and to any agency should be the same reason, in the same words.

Improvement plans: useful tool, common trap

A performance improvement plan is a communication device, not a legal formality. It helps when the targets are things the employee can control and measure, the timeframe fits the work cycle, and the manager actually holds the check-ins. It hurts in three recurring situations.

The first is the pretextual plan — issued only to build a file, with targets no one intends the employee to meet. Colleagues notice, and so do fact-finders comparing it to plans given to others. The second is the abandoned plan, where check-ins never happen and the employee reasonably concludes the issue passed. The third is the plan that arrives days after an employee reports harassment, requests leave, or asks for an accommodation; timing alone can support an inference, which is why retaliation exposure deserves a separate look before any plan is issued.

Note also that in unionized and non-union workplaces alike, performance discussions can brush against protected concerted activity — an employee criticized for raising pay or staffing concerns with coworkers may be describing conduct the National Labor Relations Board treats as protected under Section 7. Separate the work-output issue from the complaint that accompanied it, and document only the former.

Consistency is the whole ballgame

Discrimination claims are usually proved by comparison, not by a smoking-gun statement. The EEOC's laws and guidance library reflects the same structure the courts use: the employer offers a reason, and the employee tries to show it is not the real one. The most effective way to show that is a coworker with the same problem and a different outcome.

Before a termination, run a short comparison. Who else has had this issue in the last two years? What happened to them? If the answers differ, is there a documented, non-protected explanation — different roles, different severity, different prior record? Age-based claims carry their own statutory framework under the ADEA's enforcement provisions, and comparator evidence drives them too. Where a performance decision overlaps with headcount reduction, the analysis shifts again toward the criteria discussed in our piece on reduction-in-force selection.

Files, access, and what employees can see

Keep performance records in the personnel file and medical or accommodation information in a separate confidential file. Limit access to people with a business need. Several states give employees a statutory right to review their personnel file, obtain copies, or attach a written rebuttal — so write every note on the assumption the employee will read it. Where wage or hour issues appear alongside performance concerns, keep the timekeeping records straight as well; the Wage and Hour Division recordkeeping rules operate independently of any performance process. What the handbook promises about reviews, warnings, and file access should match what actually happens, a theme developed in our guide to handbooks that match practice.

Quick answers

Does an employee have to sign a written warning?

No, and refusal is not misconduct in itself. The signature usually acknowledges receipt, not agreement. If the employee declines, note the date, that the document was reviewed with them, and who witnessed the conversation. Offering space for the employee's written response often produces a more useful record than a signature does, because it captures their version at the time.

Can we fire someone who is on an improvement plan for a different reason?

Yes, if the reason is real and documented. A serious safety violation or misconduct does not have to wait for a performance timeline to expire. Say plainly which conduct drove the decision rather than blending it into the performance narrative — mixed explanations that shift over time are exactly what pretext analysis looks for.

How long should performance records be kept?

Longer than most companies expect. Federal anti-discrimination recordkeeping rules require retention of personnel records for defined periods, and any record relevant to a filed charge must be preserved until the matter concludes. Because charge and lawsuit deadlines can run well past a separation, a retention schedule built around the longest applicable limitations period is safer than a fixed one-year purge.

Is a verbal warning worth anything?

Only if someone wrote it down. A dated note describing a coaching conversation is genuine evidence that the employee had notice. An unrecorded conversation becomes a swearing contest, and the employee's account is often the more specific one because they remember the day it happened.

Where this leaves you

Write notes the same week the event happens, in observable terms, referencing a written standard. Keep the escalation sequence visible and finish what you start — close plans, record outcomes, and never revise history. Before any termination, run the comparator check and the timing check: who else did this, what happened to them, and what protected activity occurred in the preceding weeks. If either check raises a flag, slow down and get advice before acting. The connected duties — leave, accommodation, retaliation, and separation documents — are collected in the Workplace Rights & HR pathway, and the EEOC publishes the federal framework these decisions are measured against.