Poor performance documentation is not a record of frustration. It is a clear, factual account of what happened, why it mattered, what expectations were communicated, and how the employee was given an opportunity to improve. Good documentation helps managers act fairly, gives employees a realistic understanding of the problem, and creates continuity if another manager or HR representative later becomes involved. The goal is not to build a case against someone. It is to create an accurate record that supports a reasonable performance conversation and measurable next steps.
How to Document Poor Employee Performance Fairly and Effectively
#1. Define the Performance Problem Clearly
Begin by identifying the specific performance issue rather than labeling the employee as careless, unmotivated, or unreliable. Personal judgments are difficult to verify and can make documentation sound biased. Focus on observable conduct, completed work, missed expectations, or measurable results.
For example, “Jordan is careless with reports” is vague. A stronger statement would be: “The sales report submitted on March 8 contained six formula errors and was missing the regional revenue summary requested in the assignment instructions.” The second version tells the reader what occurred without speculating about Jordan’s character or intentions.
A useful description answers four questions:
- What was expected?
- What actually happened?
- When did it happen?
- What was the effect on the work, team, customer, or deadline?
If the issue involves behavior rather than output, describe the behavior precisely. Instead of writing that an employee has a “bad attitude,” document that the employee interrupted a colleague three times during a client meeting after being asked to wait until the presentation ended. Specificity makes the record more useful and fair.
#2. Gather Relevant Facts and Evidence
Before documenting poor performance, collect the information needed to distinguish a pattern from an isolated incident. Review the applicable job expectations, assignment instructions, deadlines, quality standards, attendance records if relevant, and prior communications about the work. Use sources that you can reasonably verify.
Evidence may include:
- A missed project deadline and the agreed due date
- An error identified in a submitted document
- Customer or colleague feedback tied to a specific event
- A work sample that does not meet an established standard
- Records of coaching or follow-up conversations
- The employee’s explanation or response
Do not gather information indiscriminately or include unrelated complaints. A performance record should not become a collection of every annoyance associated with an employee. Include facts that help explain the particular concern and its impact.
It is also important to check whether the same standard is being applied consistently. If several employees faced the same problem but only one is being documented, consider whether there is a relevant difference in circumstances. Consistency does not require identical treatment in every situation, but it does require a defensible reason for meaningful differences.
#3. Record Dates, Expectations, and Impact
Strong documentation establishes a timeline. Record when the expectation was communicated, when the work was due, when the problem occurred, when it was discussed, and what follow-up took place. Dates help prevent confusion and show whether the employee had a reasonable opportunity to respond or improve.
For example, a useful entry might state:
On April 2, the project schedule identified April 12 as the deadline for the first draft. On April 9, the employee confirmed that the draft was on schedule. The draft was not submitted on April 12 and was received on April 16 without the required cost analysis. The delay moved the client review from April 15 to April 19.
This record is more informative than “The employee missed another deadline.” It connects the expectation to the result and explains why the issue mattered.
Document impact without exaggerating it. If a missed deadline required a colleague to work late, say so if that fact is known. If the consequence was simply that a review had to be rescheduled, record that instead of claiming the employee “damaged the client relationship.” Accurate documentation is more persuasive than dramatic wording.
#4. Discuss the Concern With the Employee
Documentation should support a conversation, not replace one. Once you have identified the concern, meet with the employee privately and explain what you observed. Give the employee an opportunity to provide context, identify obstacles, correct factual errors, or raise information you may not have known.
Use a calm structure:
- State the relevant expectation.
- Describe the observed result or behavior.
- Explain the work-related impact.
- Ask for the employee’s perspective.
- Clarify what needs to change.
A manager might say:
The report was due on Monday and needed to include the regional analysis. The version submitted on Wednesday did not contain that section, and several figures did not match the source data. This delayed the review meeting. Can you walk me through what happened?
The employee’s response does not automatically excuse the performance issue, but it may affect the appropriate next step. The problem could involve unclear instructions, competing priorities, insufficient training, missing resources, or a personal circumstance that requires referral to an appropriate internal resource. Record the relevant explanation neutrally, along with any clarification or support offered.
#5. Separate Coaching From Formal Corrective Action
Not every performance problem requires the same level of response. A first-time, low-impact mistake may call for coaching and clarification. A repeated failure after prior feedback may require a more formal written warning or performance improvement process, depending on the organization’s procedures.
Your documentation should make the nature of the conversation clear. You might record that the meeting was an informal coaching discussion, a documented performance conversation, or part of a formal corrective action process. Do not describe a conversation as a warning if the employee was not told that it was a formal warning, and do not use threatening language to make ordinary coaching sound more serious.
A practical coaching record could state:
The manager reviewed the missed deadline with the employee, clarified that draft schedules must be updated when risks arise, and asked the employee to provide a revised schedule by April 18. The employee stated that two urgent requests had affected the timeline. The manager agreed to review priority conflicts during the weekly planning meeting.
If formal action may be appropriate, follow established organizational procedures and consult HR or another responsible internal resource. Documentation should support fair process, not bypass it.
#6. Set Specific Expectations and a Review Date
A performance conversation is incomplete if it only describes what went wrong. The employee should understand what acceptable performance looks like, what action is required, and when progress will be reviewed. Vague directions such as “be more careful” or “improve communication” are difficult to follow and evaluate.
Translate the concern into observable expectations. For example:
- Submit weekly reports by noon every Friday.
- Verify all formulas against the source spreadsheet before submission.
- Notify the manager at least one business day before a deadline if a deliverable is at risk.
- Allow colleagues to finish presenting before responding during team meetings.
Set a review date that is appropriate to the seriousness and frequency of the issue. A manager may review progress after one week for a time-sensitive reporting problem or after several weeks for a broader quality concern. Document any support offered, such as training, written instructions, prioritization help, or access to a subject-matter expert.
A useful expectation might read: “For the next four weekly reports, submit the completed report by noon Friday, include all required sections, and confirm that the figures have been checked against the source data. We will review each report in the following one-on-one meeting.”
#7. Follow Up and Update the Record
Follow-up is what turns documentation into a fair performance-management process. At the review point, compare the employee’s actual performance with the expectations that were set. Record improvement as carefully as you record continuing problems. A balanced record should not preserve only negative information.
If the employee improves, document what changed and whether the expectations have been met consistently. If the problem continues, identify the new incidents, refer back to the prior discussion, and explain what further action is being considered. Avoid simply copying the original note and adding “still an issue.” Each entry should explain what happened during the new review period.
For example:
At the April 25 review, the employee submitted all four weekly reports by the agreed deadline. Three reports included the required sections and accurate figures. The April 19 report contained one calculation error, which the employee corrected the same day after it was identified. The manager will continue reviewing reports for two additional weeks before closing the coaching plan.
If expectations were not met, document that fact and consult the appropriate internal process before deciding what comes next. Do not threaten termination or impose consequences inconsistently. The record should show a reasonable progression of communication, support, evaluation, and decision-making.
Examples of Documenting Poor Employee Performance
The following examples illustrate how to convert general complaints into useful performance records. Each example identifies an expectation, describes an observable issue, and explains the practical impact.
Missed deadlines
Weak: “Taylor is always late with assignments.”
Stronger: “The inventory reconciliation was due by 3 p.m. on May 6. Taylor submitted it at 10 a.m. on May 8 without notifying the manager that the deadline was at risk. The purchasing team could not complete its scheduled review on May 7 and moved the review to May 8.”
Work quality
Weak: “Morgan’s work is sloppy.”
Stronger: “The customer mailing list submitted on May 11 contained 18 duplicate records and omitted the required postal-code field for 27 contacts. The list was returned for correction before it could be uploaded to the mailing system.”
Attendance or reliability
Weak: “Chris cannot be depended on.”
Stronger: “Chris was scheduled to open the service desk at 8 a.m. on May 14 and arrived at 8:24 a.m. without notifying the supervisor. The desk opened late, and the supervisor covered the first customer appointments.”
Communication
Weak: “Lee has poor communication skills.”
Stronger: “During the May 16 project meeting, Lee did not tell the team that the vendor had changed the delivery date. The team continued using the earlier date in its client schedule until the change was discovered on May 17.”
Workplace conduct
Weak: “Avery is disruptive.”
Stronger: “During the May 20 team meeting, Avery interrupted two colleagues while they were presenting. After the manager asked the group to allow each person to finish, Avery interrupted a third speaker. The manager discussed the conduct privately with Avery after the meeting.”
These examples avoid assumptions about motive. They also give the employee enough information to understand what needs to change.
How to Write a Performance Documentation Note
A consistent format can help managers write notes that are complete without becoming unnecessarily long. Use the same basic structure for each significant incident or review:
Date and context: Identify when and where the issue occurred, along with the relevant assignment, meeting, or responsibility.
Expected standard: State the deadline, quality requirement, conduct expectation, or role responsibility.
Observed facts: Describe what the employee did or did not do. Include measurable details where available.
Impact: Explain the practical consequence without overstating it.
Employee response: Record the explanation or relevant information the employee provided.
Manager response: Note any coaching, clarification, resources, or direction offered.
Next expectation: State what must happen next and when it will be reviewed.
A concise note might look like this:
Date: June 3
Issue: The monthly expense report was due by noon on June 2. The submitted report arrived at 4:30 p.m. and contained three unsupported expense entries.
Impact: Finance could not complete its scheduled review that afternoon.
Discussion: The employee explained that receipts were stored in a separate folder and had not been gathered before the deadline. The manager reviewed the submission checklist and asked the employee to attach receipts to each entry before submitting future reports.
Next step: The employee will submit the June report by noon on July 2 using the checklist. The manager will review compliance during the next monthly meeting.
Keep notes professional and secure according to organizational practice. Avoid recording unnecessary personal details, rumors, sarcasm, or emotional reactions. If the employee raises a sensitive issue involving health, family circumstances, harassment, discrimination, or another matter requiring specialized handling, document the fact that the concern was raised and refer it through the appropriate internal channel rather than investigating it casually in a performance note.
What to Say When Discussing the Documentation
Managers sometimes worry that written documentation will make a conversation hostile. In practice, the tone depends less on the existence of a record than on how the manager uses it. Present the document as an accurate summary of the concern and the agreed next steps, not as a surprise accusation.
You can introduce the conversation this way:
I want to review the performance concern we discussed and make sure we have an accurate record. I’ll explain what I observed, and I’d like you to add any context or corrections before we agree on the next steps.
If the employee disagrees with the record, listen carefully and separate factual disputes from differences in judgment. Check dates, instructions, and work samples where appropriate. You may revise the record if it contains an error, while still documenting the performance concern if the underlying facts remain supported.
You can respond to disagreement with measured language:
I understand that you see the situation differently. Let’s identify which facts we disagree about and check the relevant emails, deadlines, or work records. I also want to make sure your explanation is included in the documentation.
The employee does not necessarily have to agree with the manager’s assessment for the documentation to be useful. However, the employee should have a fair opportunity to understand the concern and provide a response. Follow applicable organizational procedures regarding acknowledgment, signatures, responses, and access to personnel records.
Closing Thoughts
How to document poor employee performance comes down to accuracy, fairness, and follow-through. Describe observable facts, connect them to clear expectations, explain the work-related impact, and give the employee a reasonable opportunity to respond and improve. Good documentation does not assume bad motives or exaggerate consequences. It creates a reliable record of what happened, what support was offered, and what must happen next. Before writing your next note, gather the relevant facts and ask whether another reasonable reader could understand the situation without knowing your personal opinion.