How to Document Employee Performance Issues Correctly
Documentation is the single most important HR habit a manager can build, and the one most managers never develop until they need it and do not have it. A termination without documentation is a decision you cannot defend. A termination with specific, consistent, contemporaneous documentation is a decision that holds up under scrutiny in the courts.
Here is exactly what performance documentation needs to include and how to create it correctly.
The Four Elements of Defensible Documentation
1. Specificity
Documentation must describe specific, observable behaviors, not generalizations, interpretations, or character assessments. 'Employee submitted the March 15 client report four hours after the 5pm deadline, as documented in the email received at 9:07pm' is specific. 'Employee consistently misses deadlines' is a generalization that means nothing in a legal proceeding.
Every piece of documentation should answer: what specifically happened, when, and where. If you cannot answer those three questions, the documentation is not specific enough. Fight the temptation to be lazy with documentation here. It will pay off.
2. Contemporaneous timing
Write it down the same day. Documentation written the day of a conversation or incident is credible. Documentation reconstructed weeks later looks like it was created to support a decision that had already been made. Courts and agencies look at the date documentation was created relative to the events it describes, and same-day notes carry significantly more weight than retrospective summaries. It doesn’t have to be anything fancy, just get the specifics down on paper.
3. Consistency
Document for every employee, not just the ones you think might become problems. Selective documentation (only writing things down when you sense trouble) is one of the most common patterns that gets managers in trouble. If you only document performance issues for employees in certain demographic groups, the documentation pattern itself becomes evidence of discriminatory treatment. Stay away from that and be consistent from the outset.
4. Objectivity
Document what you observed, not what you concluded. 'Employee raised their voice and used profanity during the team meeting on March 10' is objective. 'Employee has anger management issues' is a conclusion. Objective documentation describes; it does not diagnose.
What to Document
Performance conversations: date, what was discussed, what was agreed, any commitments made
Missed deadlines or deliverables: specific dates, what was expected, what was delivered
Conduct issues: specific behaviors, date, time, location, any witnesses
Written warnings and disciplinary actions: formal documents with signature and date
Follow-up check-ins: whether the behavior improved, stayed the same, or worsened
Any explanation given by the employee for the behavior: document their response even if you do not accept it
How to Document: The Practical Method
You do not need a formal HR system to document performance issues correctly. A simple approach that works for most small businesses:
Create a folder on your computer or in your email for each employee
After any significant performance or conduct conversation, write a brief email to yourself with the subject line: '[Employee name] — [date] — [topic]' — and send it to your own email address
The email timestamp establishes the contemporaneous date, the content establishes the specifics
For formal written warnings, use a written warning template and keep the signed copy in the employee's personnel file
Don’t write your first written warning from scratch.
This Progressive Discipline & Written Warning template includes the exact documentation language, structure, and legal safeguards managers need when performance issues escalate beyond notes and conversations.
Stop guessing what a defensible warning should look like.
This method takes two minutes per incident and creates an organized, date-stamped record that is exactly what you need if a decision is ever challenged. And, courts place more weight on this method because it is more difficult to post-date documentation.
What Not to Include
Speculation about the employee's motives or mental state
References to protected characteristics like age, race, gender, religion, disability, or any other protected class
Your personal feelings about the employee
Promises about future decisions: 'one more incident and you're fired' creates obligations you may not want to be held to
Information shared in confidence by other employees unless directly relevant to the documented incident
The Documentation Test
Before finalizing any piece of documentation, ask: if a neutral third party like a judge, an HR investigator, or an agency auditor read this document, would they understand exactly what happened, when, and what standard was not met? If the answer is yes, the documentation is sufficient. If the answer is no, add specificity until it is. Also, ask yourself this question: if the local newspaper had the document and used it as a front-page article, would you be embarrassed by it? If so, adjust the documentation.
