When an employee is not meeting expectations, violating company policies, or creating problems for customers or coworkers, you eventually reach a point where termination becomes necessary. But making the decision to terminate is only part of the process; how you document that decision can be just as important as the decision itself.
In this article, I'll outline the distinction between strong and weak documentation and demonstrate how an untrained manager can create problems when they are hasty to document what happened. For example, if a former employee challenges the termination, files for unemployment, or lodges a discrimination or other employment-related claim, the incomplete paper trail makes it difficult to contest any wrongdoing.
Strong documentation creates a clear record of what happened, which expectations were communicated, how the employee responded, in what ways the employee failed to meet those expectations, which corrective steps were taken, and why termination was justified.
As a manager, you should document the specific policy, job requirement, performance standard, or workplace rule involved to meet this first requirement.
Describe what happened, when it happened, and what evidence supports the conclusion.
Document previous coaching, warnings, training, performance improvement plans, or other corrective action by identifying the specific behavior or specific misconduct, noting when it occurred, and supporting the conclusion with evidence throughout the disciplinary process. This might include previous performance issues, written reprimands, final warnings, performance improvement plans, development plans, the more severe form of response, and the termination date after the employee failed to improve.
Give the employee an opportunity to explain the situation and document relevant information they provided as part of a fair disciplinary procedure. In certain circumstances, a disciplinary hearing may be the best course before you decide on appropriate disciplinary action.
Provide guidance on the specific misconduct under review, the possible outcomes, and any written notice required by your own policy for legal compliance. Start with less severe steps such as coaching or a written reprimand before escalating to a final warning or other disciplinary action. For performance issues, use a performance improvement plan or development plan to document specific objectives, support improvement, and note the consequences if targets are not met. More severe measures might include demotion (such as reducing an employee's title, salary, and responsibilities) or other adverse action, up to and including termination or pay cuts.
Consider whether similarly situated employees have been treated similarly for comparable conduct, taking into account the employee's history.
The goal is to create a factual record that someone unfamiliar with the situation could understand months or years later. An employee should have the opportunity to respond to the specific misconduct during the disciplinary process, which may include an investigation or disciplinary hearing in certain circumstances. The employer should then decide the best course and appropriate disciplinary action under its own policy and communicate the possible outcomes in a written notice. A fair, transparent process also supports legal compliance and helps build trust within the organization.
Weak documentation, on the other hand, lacks all the details that make documentation strong. It typically includes vague statements such as "poor attitude," "ongoing issues," or "attendance problems" that give little understanding about your employee disciplinary action to someone reviewing the case from the outside.
Here are three examples of strong vs. weak documentation for an employee who was terminated for each of these scenarios: poor performance, attendance, and misconduct.
Joe Friday repeatedly struggled to meet the performance standards required for his role as a Records Division Clerk. Despite prior coaching, warnings, and an opportunity to improve, his accuracy and productivity remained below the company's established standards, which led to performance issues from unmet job responsibilities.
Expectations Violated
Company handbook policy requires 95% accuracy and 40 entries per shift, effective January 15, 2024. Joe signed a receipt acknowledging the policy on January 22, 2024. He completed new-hire training in January 2024 and refresher training on April 8, 2025.
Final Incident
A July 15, 2026, audit covering June 1–July 14 found that Joe averaged 27 entries per shift with 78% accuracy and had misfiled 14 case numbers.
Joe reported no medical or system-related issues affecting his performance. Additional training was offered June 3, 2026, but Joe declined.
Performance and Discipline History
Joe had consistently met performance expectations in 2024. When his performance started declining, he received the following:
All acknowledgments were signed. Rework associated with the errors cost approximately $1,800.
Expectations Violated
"Joe was not meeting performance expectations."
Final Incident
"We reviewed Joe's work and he was not performing up to standards. He was warned multiple times and things did not improve, so we let him go."
Additional Information
"Joe has been struggling for a while with his employee behavior. This has been an ongoing issue."
The strong version establishes the specific standard, actual performance, prior corrective action, employee response, and business impact.
The weak version does not identify what "performance expectations" means, how Joe failed to meet them, when he was warned, or what the company did to help him improve.
The lesson: If performance is measurable, document the measurements.
Joe Friday accumulated a pattern of unexcused absences, including multiple no-call/no-shows, despite receiving progressive discipline. After receiving a final written warning that another unexcused absence could result in termination, Joe missed another scheduled shift.
Expectations Violated
Handbook attendance policy, revised 03/01/2025, states that more than three unexcused absences within a rolling 90-day period may result in termination.
Joe signed acknowledgments on 01/22/2024 and again 03/10/2025 for the updated policy.
Final Incident
On 07/14/2026, Joe incurred his fifth unexcused absence during the 04/16–07/14 rolling 90-day period:
Documentation was requested after each absence and never provided. No FMLA or ADA documentation was on file.
Performance and Discipline History
All documents were signed. Coverage overtime cost the company approximately $390.
Expectations Violated
"Joe had attendance problems and missed too much work."
Final Incident
"Joe called in again on 07/14/2026. This was the last straw. He had been warned before about his attendance."
Additional Information
"Joe was warned about attendance. He kept missing days, so we had to let him go."
The strong documentation shows exactly which policy applied, how many absences occurred, when they occurred, and which consequences had previously been communicated.
The phrase "missed too much work" does not establish how much is too much or whether the employee's absences were actually covered by the company's attendance policy.
Note how the strong documentation also addressed whether any of his absences involved protected leave or a disability accommodation, making it difficult for Joe to claim after the fact.
The lesson: Don't document "attendance problems;" document the specific attendance events and how they relate to the policy.
Joe Friday had several inappropriate interactions with members of the public. After a third documented incident involving hostile language and inappropriate conduct toward a customer, the company determined termination was warranted to protect a healthy work environment.
Expectations Violated
Handbook conduct policy, effective 08/01/2023, prohibits hostile language and public confrontations with customers or members of the community. Joe signed an acknowledgment on 08/15/2023 and completed mandatory customer service training on 08/20/2023.
Final Incident
On 07/11/2026 at approximately 10:20 a.m., Joe raised his voice and used obscenities toward civilian Maria Santos at the Records counter.
Written statements were obtained from Santos, Officer Kim (#4471), and Supervisor Walsh. Lobby video was preserved.
Joe admitted raising his voice and using obscenities.
Complaint #1 was filed the same day.
Prior Conduct Record
Expectations Violated
"Joe cussed and was rude to a civilian. Employees are expected to treat the community with respect."
Final Incident
"Joe yelled curse words at a civilian and made her cry. This is not acceptable."
Additional Information
"Joe has had issues with mistreating civilians before. He knows he's not supposed to act this way."
The weak version relies heavily on conclusions such as "rude" and "mistreating civilians." The strong version describes what happened, when it happened, who witnessed it, what evidence exists, and what the employee admitted.
That's particularly important for conduct issues, where descriptions can easily become subjective.
The lesson: Document the behavior, not merely the label you give the behavior.
A simple way to evaluate disciplinary documentation is to imagine that someone unfamiliar with the situation reads it six months later. These are key steps in a sound disciplinary process, and factual records are especially important to reduce discrimination claims involving protected characteristics, limit legal risks, and, when handled fairly and transparently, foster trust.
Could that person determine:
If the answer is no, the documentation may be too vague.
One of the most common documentation mistakes is describing the employee's personality rather than their behavior.
Statements may reflect a manager's frustration, but they don't establish what actually happened. Examples of character judgments might include:
These questions are key steps for reviewing documentation in the disciplinary process:
Rather than "Joe has a bad attitude," document the specific conduct that demonstrates the problem, including dates, circumstances, and relevant evidence.
Strong documentation does not automatically make every termination defensible, and it should describe the specific misconduct rather than character judgments. Employers should also consider whether they have applied their policies consistently.
If two employees commit substantially similar violations, but one is terminated while the other receives a warning, the employer should understand and be able to explain the difference as part of selecting the appropriate disciplinary action.
This does not mean every employee must receive identical discipline. An employee with a history of repeated violations may appropriately receive more serious discipline than someone committing a first offense, especially when the employee's history supports the distinction. But the reason for the difference should be legitimate and documented.
A useful formula for disciplinary documentation is:
Expectation + Evidence + Employee Response + History + Action = Thorough Documentation
Identify the rule. Document the facts. Record the employee's response. Establish the history. Explain the action.
Good documentation creates a clear, factual record that helps managers make consistent decisions and helps employees understand what is expected of them. Consistency in applying disciplinary action helps prevent perceived favoritism, and fair and transparent processes foster trust.
Most importantly, don't wait until termination to start documenting a problem. When performance, attendance, or conduct issues arise, document them accurately, specifically, and as they occur. For more information, please reach out to your Stratus HR rep.
Not a current Stratus HR client? Book a consultation and our team will contact you shortly.