How to Document Employee Performance Issues Legally

Documentation is the foundation of every defensible performance management process. Without it, a manager’s legitimate concerns about underperformance become difficult to act on — and if challenged, impossible to defend. With it, the process is transparent, fair, and legally sound.

The challenge is that most managers document performance issues poorly — not because they are careless, but because no one has shown them what good documentation looks like. Here is a practical guide.

Why Documentation Matters

When a PIP is challenged — in an employment tribunal, a grievance process, or an HR investigation — the documentation is what the case rests on. The questions asked will be:

Did the manager communicate clear expectations to the employee?
Did the manager provide specific feedback when those expectations were not met?
Was the employee given a genuine opportunity to improve?
Was the process consistent with how similar situations were handled?
Was the decision to issue a PIP based on evidence, or on subjective assessment?

Good documentation answers all of these questions affirmatively. Poor documentation leaves the answer to each one uncertain.

The Principles of Good Performance Documentation

Be specific

Every piece of documentation should describe observable behaviors or measurable outcomes — not characterizations of the person. Specificity is what makes documentation useful in a PIP and defensible if challenged.

Not specific: “David consistently fails to meet expectations and does not take his responsibilities seriously.”

Specific: “On March 3, 5, and 10, David submitted client proposals after the agreed 48-hour deadline. On March 7, a client escalation was received referencing an unanswered email from March 3. These incidents were discussed in a one-on-one on March 12.”

Be contemporaneous

Document as close to the event as possible. Notes written weeks after a conversation are less reliable and less credible than those written the same day. Build the habit of a brief documentation note immediately after any significant performance-related conversation.

Be objective

Avoid adjectives that reflect opinion rather than observation. Words like “poor,” “bad,” “lazy,” “difficult,” and “unmotivated” are judgments. They invite dispute and can create perception of bias. Replace them with descriptions of what happened.

Be consistent

Apply the same documentation standard across all employees. If you document every late submission for one employee but not for others, inconsistency can become evidence of unfair treatment. The standard should be consistent regardless of the individual.

Keep it proportionate

Not every performance issue requires formal documentation. Informal notes and one-on-one follow-ups are appropriate for minor, first-time issues. Reserve formal documentation for patterns of behavior, significant incidents, or any situation where a PIP may be the next step.

What to Document Before a PIP Is Issued

The documentation trail that precedes a PIP is what demonstrates the process was fair. At minimum, you should have documented:

Prior conversations: Every coaching conversation, feedback session, or direct discussion about the performance issue should be noted — date, what was discussed, what the employee said, and what next steps were agreed. A follow-up email to the employee after each conversation creates a contemporaneous record.

Performance data: Any quantitative evidence of the performance issue — sales data, quality metrics, attendance records, error rates, client satisfaction scores. Tie the data to the relevant period and the expected standard.

Prior warnings: Records of any verbal or written warnings that have already been issued.

The employee’s responses: Document what the employee said when the issues were raised. Did they acknowledge the problem? Dispute it? Provide context that changed your assessment? This matters because it shows the employee was given an opportunity to respond.

How to Document a Performance Conversation

After any significant performance discussion, write a brief contemporaneous note that includes:

Date and setting of the conversation
Who was present
What you raised (specific, factual)
What the employee said in response
What next steps were agreed
The timeline for follow-up

Keep this in the employee’s HR file and, where appropriate, follow up with an email to the employee summarizing what was discussed. The email creates a written record that the employee received the feedback — and gives them an opportunity to correct the record if they believe something was mischaracterized.

Language That Will Not Hold Up

Avoid these categories of language in performance documentation:

Attitude and motivation language: “Jennifer has a bad attitude,” “Thomas is not motivated,” “She doesn’t care about her work.” These are inferences, not observations. Document the behavior: “In three team meetings in February, Jennifer responded to feedback with dismissive language on two occasions, noted in meeting minutes dated February 8 and February 21.”

Comparative language without evidence: “Other team members outperform David significantly.” Compare to the standard, not to individual colleagues, unless you are explicitly measuring against a team benchmark.

Vague frequency language: “He is frequently late,” “She often misses deadlines.” “Frequently” and “often” invite challenge. Replace with specific instances: “He arrived after 9:30am on six of fifteen working days in March.”

Speculative language about intent: “I believe she is doing this deliberately,” “He seems to be trying to avoid responsibility.” Document what happened, not what you think motivated it.

Storing Documentation Securely

Performance documentation should be:

Stored in a secure location accessible only to the manager and HR
Not shared with other team members or colleagues
Retained according to your organization’s data retention policy and applicable employment law in your jurisdiction
Not kept in personal email or on personal devices

In most jurisdictions, employees have the right to access documentation held about them. Assume everything you document could be seen by the employee — and write accordingly.

From Documentation to PIP

Good documentation makes writing a PIP significantly easier — and more defensible. When you have a clear record of the performance issues, the dates they occurred, the conversations that addressed them, and the evidence that improvement did not follow, the PIP becomes an accurate summary of a fair process rather than a document that needs to construct a case from scratch.

Templates Hub’s PIP Builder is designed to work alongside your documentation: the manager inputs the key facts, incidents, and prior conversations, and the builder converts them into appropriately structured PIP language — specific, factual, and legally considered.

Summary

Effective performance documentation is specific, contemporaneous, objective, and consistent. It describes what happened — behaviors and outcomes — not what the manager thinks those behaviors mean. Built up over time, it creates the foundation for a fair PIP process that is both defensible and genuinely oriented toward helping the employee improve.

How to Document Employee Performance Issues Legally and Effectively