How to Document a Performance Problem So It Holds Up Later
By John Hamilton, MS, PHRca, PHR · Reviewed for legal currency August 2026
I am not an attorney. This article is general information based on my experience as an HR professional, and it is not legal advice. For legal advice about your situation, consult a qualified attorney.
The short version
- The test is whether a jury reading your documentation would see what you saw.
- Good documentation is specific, contemporaneous, behavioral, tied to a written standard, and includes the employee’s response.
- A file full of praise followed by a sudden termination is the single most common documentation failure.
Fixing an HR mistake after the fact costs more than preventing it. Subscriptions start at $139 a month, and every plan includes a custom employee manual. Call (562) 444-8076, email service@accomplicenter.com, or come by our store at 3217 Carson St in Lakewood to sign up.
The most expensive employment decisions a small employer makes are termination decisions, and the most common reason termination decisions go wrong is bad documentation. The performance issue is usually real. The conversations with the employee usually happened. The expectations usually were communicated. None of it ends up in writing in a form that holds up later.
The “would this email convince a jury” test
Pretend the documentation you just wrote is going to be projected on a screen in front of a jury. The jury has never met you, doesn’t know your business, has no priors about the employee. They can read what you wrote, and that’s all the information they have about the situation.
Would they see what you saw. Would they understand the behavior was a problem. Would they conclude the employee knew what was expected and fell short. Would they see the company as having handled the situation in good faith.
If yes, the documentation is doing its job. If no, the documentation isn’t going to survive the moment when it gets used.
It’s the same test an arbitrator, a hearing officer, an EEOC investigator, or a state agency will apply. Could a reasonable third party read this and conclude what you concluded.
What good documentation includes
- Specifics, not generalities. “John was unprofessional with a customer” is general. “On October 15 at approximately 2 PM, John raised his voice to a customer who asked for a refund. The customer (Jane Smith, order 4721) reported that John told her the policy was clearly posted and she should have read it. John used a dismissive tone for several minutes. The customer left without resolution and posted a negative review the same evening” is specific.
- Contemporaneous, not after-the-fact. Documentation written within 24 to 48 hours of the event is contemporaneous. Documentation written six months later because someone is now considering termination is not contemporaneous. The contemporaneous version carries weight. The after-the-fact version looks like manufactured evidence.
- Behavioral, not personal. “John was rude” is a personality conclusion. “John raised his voice and used dismissive language with a customer” is a behavior. Behavior is documentable. Personality isn’t.
- Tied to the job description or written standards. The behavior or performance issue should connect to a specific expectation. “John’s customer service didn’t meet the standard in the job description, which states that customer-facing staff will treat all customers with professionalism and resolve issues constructively.” The standard is the anchor.
- Includes the employee’s response. What the employee said when the issue was raised. Did they acknowledge it. Did they dispute it. Did they offer context. Did they propose a solution. The employee’s response is part of the file.
- Includes any commitments or follow-up. What was decided in the conversation. What the employee committed to do differently. What the company committed to (training, support, etc.). What the next check-in or review will look like.
What bad documentation looks like
“Talked to John about his attitude.” No specifics, no behavior, no standard, no follow-up.
“John needs to improve.” Conclusion without evidence.
“Several customers have complained about John.” Aggregated claim without specifics.
“John has been a problem for a while.” Vague timeline, no events.
Documentation written six months after the events occurred, drafted to support a termination decision that’s already been made. The reverse-engineered file. Easy to spot. Doesn’t survive scrutiny.
Documentation that’s inconsistent with other contemporaneous records (positive performance reviews, no prior write-ups, manager praise in emails). The kind of inconsistency that destroys credibility.
The structure of a good written record
A performance documentation note should include, in some order:
Date and time of the event or conversation.
- Who was involved. The employee. The manager. Any witnesses. Any customers or other parties.
- What happened. Specific behavior, specific words if possible, specific outcomes.
- Why it’s a problem. Connection to the job description, to a written policy, to a customer or operational impact.
- What was discussed. The conversation between the manager and the employee, including the employee’s response.
- What’s expected going forward. Specific behavior, specific outcomes, specific timeframes.
- Any commitments. What the employee said they would do. What the company will provide.
- Follow-up date. When the next check-in will happen.
A documentation note in this structure runs maybe 200 to 400 words. It’s not a thesis. It’s a record.
The conversation matters as much as the document
Documentation captures a conversation. The conversation has to actually happen, and it has to be the kind of conversation that the documentation reflects.
This means: when an issue arises, talk to the employee. Don’t wait. Don’t accumulate issues silently and spring them in a termination meeting. Address each issue close to when it happens. Have the conversation. Document the conversation. Move on.
This pattern, repeated, is what builds the file that supports a termination decision when one becomes necessary. It’s also what often prevents the termination, because employees who get clear, contemporaneous feedback often correct the issue.
The praise problem
Operators who later have to fire someone often have a track record of praising that same employee in writing. Positive performance reviews. “Great job!” emails. Holiday bonuses. Promotion considerations. Then, six months after the last positive communication, a termination.
This pattern is the single biggest documentation problem I see. The praise undermines the eventual termination. A jury reading the file sees positive feedback up to a few months before the firing, with no negative documentation in between, and concludes that something other than performance must have caused the change. That something often gets identified as a protected reason.
The fix is to give honest performance feedback throughout the relationship. If performance has been mixed, the reviews should reflect that. If issues arise, they get documented when they arise, not retroactively. The file should match reality.
This doesn’t mean withholding praise. Praise good work. Document accurately. Reviews should reflect the actual performance, including the parts that need improvement. A balanced review that’s honest about strengths and weaknesses survives scrutiny in a way that all-positive-then-suddenly-fired doesn’t.
The performance improvement plan
A formal performance improvement plan (PIP) is a documentation tool that structures the response to a sustained performance issue. The PIP includes:
The specific performance gaps, with examples and standards.
The expectations going forward, with measurable goals.
The timeframe, typically 30 to 90 days.
The support the company will provide, like training, coaching, additional resources.
The check-in cadence, typically weekly or biweekly.
The consequences of not meeting the standard, typically termination.
The employee’s signature acknowledging receipt (not agreement, just receipt).
A PIP done well is a tool for either improvement (sometimes the employee turns it around) or for clean termination (the file is unambiguous). A PIP done poorly is a fig leaf the company puts on a termination decision that was already made, and juries see through this.
The test for a good PIP is whether the company actually wants the employee to succeed. If yes, the PIP is structured to help them succeed and the company invests in the support. If no (the company has decided to terminate and is going through the motions), the PIP is theater and shouldn’t be used.
What this looks like in your manual
Your handbook should have a performance management section that:
References the standards (job descriptions, policies) against which performance is measured. Describes the company’s approach to performance feedback (regular check-ins, periodic reviews). Describes the discipline structure (with “may” rather than “will” language). References the PIP as a tool for sustained issues. Confirms that documentation will be created throughout the relationship.
We include this in the custom employee manual that comes with every AccompliCenter HR subscription. The section ties to the job descriptions, the discipline policy, and the termination procedure. Plans start at $139 a month.
The skills of documenting performance well are practiced. Most managers are uncomfortable writing critical things about employees, even when the criticism is warranted. The discomfort is part of the job. The cost of not documenting is the lawsuit that the documentation would have prevented or shortened.
To subscribe, call us at (562) 444-8076, stop by our store at 3217 Carson St in Lakewood, or email service@accomplicenter.com.
See AccompliCenter HR plans →