When a termination is challenged, one of the first questions an attorney or agency investigator asks is simple: "Show me the documentation." Too often the answer is a glowing annual review, a few vague emails and a manager's memory. The employee says they were never told there was a problem, and on paper, they are right.
Documentation is not about building a case against someone. It is about creating an accurate, shared record of expectations, feedback and results. Done well, it helps employees improve, keeps managers honest and protects the business when a decision has to be made.
Why documentation matters
- Clarity for the employee. Written feedback removes ambiguity about what needs to change.
- Consistency across the team. Records help you treat similar issues the same way, which is the heart of avoiding discrimination claims.
- Continuity. If a manager leaves, the history does not leave with them.
- Defense. If an employee later alleges discrimination or retaliation, contemporaneous records showing a legitimate, consistent reason are your strongest evidence.
The five qualities of good documentation
| Quality | Weak example | Strong example |
|---|---|---|
| Specific | "Often late." | "Arrived after the 9:00 a.m. shift start on Sept 3, 8 and 15 (9:22, 9:40, 9:15)." |
| Objective | "Lazy and unmotivated." | "Completed 14 of the 25 tickets assigned this week; team average was 23." |
| Timely | Written months later from memory | Written the same day or within a day or two |
| Tied to expectations | "Not meeting standards." | "The role requires responding to client emails within one business day (job description, section 2)." |
| Shows communication | Private note the employee never saw | "Discussed in 1:1 on Sept 16; employee said the commute had changed; agreed on plan below." |
What to write down
A useful record of a performance conversation usually covers:
- Date, time and who was present.
- The expectation. What the employee is supposed to do, and where that standard comes from.
- What actually happened. Facts, examples, dates and numbers.
- The impact. How the issue affected customers, coworkers, deadlines or revenue.
- The employee's response. Their explanation, in a neutral summary. Record it even if you disagree.
- Next steps. What the employee will do, what support you will provide and when you will follow up.
- Consequences, if relevant. For formal warnings, what may happen if the issue continues.
A sample coaching note
Here is what a short, well-written note can look like after a one-on-one:
"Oct 2, 1:1 with Jordan (manager: Priya). Expectation: weekly status reports to the client are due by 5 p.m. Friday, per the account plan shared in July. Reports for Sept 13 and Sept 27 were sent the following Monday; the client raised the delay on Sept 30. Jordan explained that the reporting dashboard was slow on Fridays. Agreed: Jordan will start reports Thursday afternoon, and Priya will ask IT to look at the dashboard by Oct 6. We will review on Oct 16."
It is brief, factual, includes the employee's perspective and ends with clear next steps on both sides.
Language to avoid
Documents can become evidence, so write as if a judge, a jury or the employee will read them. Avoid:
- Labels and diagnoses such as "seems depressed," "unstable" or "has anger issues." Describe behavior instead.
- References to protected characteristics, including age ("not as sharp as the younger staff"), pregnancy, disability, religion, national origin or family status.
- References to protected activity as part of the problem, such as "complains too much about pay" or "took a lot of medical leave." Taking protected leave or raising concerns cannot be counted against someone.
- Exaggeration, like "always" and "never," unless literally true.
- Sarcasm or emotion. Keep the tone neutral and professional.
Levels of documentation
Not every issue needs a formal write-up. Match the documentation to the stage of the conversation.
Informal coaching notes
Short notes from one-on-ones capturing feedback given and agreed actions. These can live in a manager's file or your HR system, but they should still be factual and dated. A quick follow-up email ("Thanks for meeting today, here is a recap of what we discussed...") is an easy way to share the note with the employee.
Written warnings
A formal document describing the issue, prior conversations, expectations and consequences. The employee should receive a copy and sign to acknowledge receipt. Note if they decline to sign.
Performance improvement plans
A structured plan with measurable goals, support and a timeline, used when an issue persists despite coaching.
Performance reviews
Annual or periodic reviews should reflect reality. Inflated reviews are one of the biggest problems in later disputes; if you rated someone "meets expectations" across the board, it is hard to argue their performance was unacceptable a month later.
Where to store it
- Keep formal warnings, PIPs and reviews in the employee's personnel file.
- Keep medical information, including doctor's notes and accommodation records, in a separate confidential file.
- Store investigation files separately with restricted access.
- Know your state's rules on employee access to personnel files; several states give employees a right to inspect or copy them. See our state HR law guides for details.
- Follow a consistent retention schedule and do not destroy records once a claim is threatened.
Documentation checklist for managers
- Write it the same day or as soon as possible.
- Include specific dates, examples and measurable facts.
- Link the issue to a known expectation or policy.
- Record that you discussed it with the employee, and their response.
- State next steps and a follow-up date.
- Remove opinions, labels and any reference to protected traits or activity.
- Check that the issue is treated the same way it was for other employees.
- Share formal documents with the employee and get acknowledgment of receipt.
- File it in the right place.
Special situations
Recent complaints or leave. If the employee has recently raised a concern, requested an accommodation or taken protected leave, involve HR before escalating discipline. Documentation that suddenly appears after protected activity can look like retaliation, even when the issue is real.
Possible medical causes. If the employee mentions a health condition that may affect their work, document the conversation and start the ADA interactive process rather than treating it purely as a performance issue.
Remote employees. Rely on measurable outputs, such as deliverables, response times and project milestones, rather than impressions of "presence" or online status.
Key takeaways
- Good documentation is specific, objective, timely and tied to a clear expectation.
- Always record that the issue was communicated and how the employee responded.
- Avoid labels, emotional language and anything touching protected characteristics or activity.
- Keep reviews honest; inflated ratings undermine later decisions.
- Involve HR when timing overlaps with complaints, leave or accommodation requests.
Make documentation easier
Need a written warning or coaching memo? AskHrAI's HR document generator drafts structured templates, and the AI HR chat can help you reword notes so they stay factual and neutral.
This article is general information, not legal advice. Employment laws change and vary by state and city — confirm details with your state labor department or an employment attorney.