You know the employee isn’t meeting expectations. Your gut says something needs to change. But when you sit down to put it in writing, you freeze, because how to document employee performance issues the right way feels like a test you never studied for. You’re not alone. Most leaders we work with at Soteria HR tell us that documentation is the single HR task they put off the longest, and it’s also the one that costs them the most when they skip it.
Poor documentation, or none at all, leaves your company exposed during unemployment claims, wrongful termination disputes, and EEOC complaints. On the flip side, clear and consistent records protect you legally, give employees a fair shot at improvement, and make tough conversations easier to navigate. The difference between a defensible termination and a costly lawsuit often comes down to what you wrote and when you wrote it.
This guide breaks down exactly what to document, how to phrase it objectively, and when to put pen to paper (or fingers to keyboard). We’ll walk through real-world examples, timing best practices, and the common mistakes that undermine even well-intentioned managers. Whether you’re addressing a single incident or building a case over time, you’ll leave here with a repeatable process you can start using today.
What to document and why it protects you
When you understand what belongs in a performance record, you stop second-guessing yourself mid-sentence. Every document you create serves two purposes: it gives the employee clarity about where they stand, and it gives you a defensible paper trail if the situation escalates to a termination, a discrimination claim, or an unemployment hearing. Neither purpose works if the record is vague, emotional, or missing key details. Getting this right from the start is what separates an HR process that holds up from one that falls apart under pressure.
A single well-written incident report can be the difference between winning and losing an unemployment claim or wrongful termination dispute.
The core elements every performance record needs
Knowing how to document employee performance issues starts with knowing exactly what to include. Each record should capture the who, what, when, and how of the situation without editorializing. If you leave out the date or skip the specific behavior, the document loses credibility fast. Below are the six elements every performance documentation entry should contain:
| Element | What to include |
|---|---|
| Date and time | When the incident or issue occurred, not just when you wrote it up |
| Employee name and role | Full name and current position title |
| Description of the issue | Specific, observable behavior or missed output |
| Expectations referenced | The policy, goal, or standard that was not met |
| Prior notice | Whether the employee received a warning previously |
| Manager name and signature | Who documented it and when they documented it |
Why incomplete documentation backfires
Most legal and HR problems don’t come from what managers did. They come from what managers failed to write down. If you terminate an employee but your records only show notes like "bad attitude" or "not a team player," you’ve created a serious liability. Subjective language and missing dates make your case look inconsistent, and courts, mediators, and state unemployment boards all notice that inconsistency quickly.
Your documentation also needs to reflect a pattern when one exists. A single incident note from two years ago carries little weight compared to a consistent, timestamped record of conversations, written warnings, and follow-up meetings. Think of your documentation as a timeline a stranger could read cold and understand. If that outside reader can’t tell what happened, in what order, and what you did about it, your records need more work before you take any formal action.
Step 1. Set expectations and gather facts
Before you write a single word, you need two things in place: documented expectations the employee was aware of, and a clear set of facts about what actually happened. Without both, your documentation becomes your opinion rather than a record. Skipping this step is one of the most common reasons performance records fall apart during disputes, and it’s where learning how to document employee performance issues properly actually begins.
Confirm that expectations were communicated
You can’t hold someone accountable to a standard they never received. Before documenting the issue, confirm that the employee had written access to the relevant policy, goal, or job requirement before the problem occurred. This could be their signed offer letter, a performance goal set during their last review, or your employee handbook.
If you can’t point to a document where the expectation was set, fix that first before you move forward.
If the expectation was communicated verbally, document that conversation too. Write a brief note that captures when the conversation happened, who was present, and what was discussed. A record that says "Employee was informed on March 3rd by their direct manager during a one-on-one that client emails must be answered within 24 hours" is far more useful than no record at all.
Gather the specific facts before you write
Once expectations are confirmed, collect the facts before you open a blank document. That means exact dates and measurable outputs rather than general impressions. Pull the relevant data, emails, or reports. If a deadline was missed, note which one and by how much. If a policy was violated, name the policy and describe exactly what occurred.
Use this checklist before you start writing:
- Date and time of the incident or pattern start date
- Specific behavior or missed output
- The standard or expectation it violated
- Supporting documents, emails, or reports
- Whether prior conversations or warnings exist
Step 2. Write objective notes that hold up
Once you have the facts, the way you write them down determines whether your documentation holds up or falls flat. The core rule of how to document employee performance issues is simple: describe what you observed, not what you concluded. Judges, HR investigators, and unemployment boards care about observable facts, not your interpretation of them. Every word choice matters here.
Use behavior-based language
Your notes should read like a factual report, not a character assessment. Stick to what you saw, heard, or measured. Avoid words like "lazy," "difficult," or "negative attitude" because those describe character, not conduct. Instead, name the specific action or inaction that occurred and tie it directly to a missed standard.
Replace "Employee has a bad attitude" with "Employee interrupted a client call on April 10th and raised their voice when asked to follow the escalation protocol outlined in the Customer Service Policy."
Use this template as a starting point for any incident:
Date of incident: [Date]
Employee: [Full name, title]
Documented by: [Manager name, title]
Date documented: [Date you wrote this]
Incident description:
On [date], [employee name] [specific behavior or missed output].
This did not meet [specific policy, goal, or standard], which was
communicated on [date] via [method: handbook, email, meeting, etc.].
Prior notice given: [Yes / No]
If yes, reference: [Date and format of prior notice]
Keep your language tight and factual
Avoid qualifying words like "often," "sometimes," or "usually" when describing an issue. Those words introduce doubt and make your record look uncertain. If the same problem happened four times, write "four times" and list each date. That level of specificity signals that you documented in real time, which makes your record far harder to challenge during a dispute or formal review.
Step 3. Record the employee response and plan
Documentation doesn’t stop with your account of what happened. A complete performance record includes how the employee responded during the conversation and what improvement plan you put in place together. Skipping this part is one of the most overlooked gaps in how to document employee performance issues, and it’s a gap that can seriously weaken your position if the situation escalates later.
Capture what the employee said
Write down the employee’s response as close to verbatim as possible, not your interpretation of it. If they agreed with the feedback, note that. If they pushed back, record the specific objection they raised. Your record should reflect both sides of the conversation so it reads as a fair, balanced account rather than a one-sided write-up.
A record that includes the employee’s own words is far harder to dispute than one that only reflects the manager’s perspective.
Use this format for the response section of your notes:
Employee response:
[Employee name] stated: "[Direct quote or close paraphrase of what they said]."
Employee acknowledged the issue: [Yes / No / Partially]
Employee's explanation or objection: [Summary in their words]
Document the improvement plan
After the conversation, put the agreed-upon plan in writing and make sure the employee receives a copy. A good improvement plan states exactly what needs to change, by when, and how you will measure success. Vague plans like "improve communication" are unenforceable. Specific ones like "respond to all internal emails within one business day starting May 1st" give everyone a clear target to work toward.
Include these elements in every written plan:
- The specific behavior or performance gap being addressed
- The measurable standard the employee must meet
- The deadline or review date
- The support or resources you are providing
- Consequences if the standard is not met
Step 4. Track deadlines, follow-ups, and outcomes
Writing the initial documentation is only part of the job. What happens after that first conversation determines whether your records reflect a complete, credible process or a one-time write-up that goes nowhere. When you learn how to document employee performance issues properly, you quickly realize that follow-through documentation carries as much weight as the original record. Courts and HR investigators look for evidence that you monitored progress and took consistent action, not just that you had one conversation and hoped for the best.
Build a follow-up log
Every improvement plan you create needs a corresponding tracking log that records each check-in date, what was discussed, and whether the employee met the agreed-upon milestone. Without this log, you have no proof that you followed through on your end of the plan.
A gap between your original warning and a termination, with no documented follow-ups in between, is one of the fastest ways to lose an unemployment claim.
Use this simple log format after each follow-up meeting:
Follow-Up Log Entry
Date of follow-up: [Date]
Employee: [Full name, title]
Conducted by: [Manager name]
Progress against plan:
[Describe specifically what improved, stayed the same, or got worse]
Standards met: [Yes / No / Partially]
Next review date: [Date]
Notes: [Any new incidents, commitments, or changes to the plan]
Record the final outcome
When the performance process reaches a conclusion, whether that is successful improvement, a final warning, or termination, you need a closing entry in the record. This entry should state the outcome, the date it was decided, who was involved, and what the employee was told. Tie it back to the original documentation so your full record reads as a connected timeline from the first incident to the final decision.
Close the loop and move forward
Knowing how to document employee performance issues the right way gives you more than legal protection. It gives you a fair, repeatable process that employees can trust and managers can follow consistently. When your records are complete, timestamped, and tied to measurable expectations, you stop making decisions based on gut feeling and start making them based on facts. That shift alone changes how your entire team experiences accountability.
Most managers feel relief once they build this habit. The fear of confrontation drops because the documentation does the heavy lifting. You walk into every difficult conversation with a clear record behind you, and you walk out with a clear plan in front of you. If you want support building that process inside your organization, Soteria HR works alongside growing companies to put the right systems in place before problems escalate. Schedule a consultation with our HR team to get started.
