Good performance documentation records the expectation, observable facts, employee response, support offered, and agreed follow-up. It helps an employee understand what must change and gives the next reviewer enough context to assess the decision. Avoid labels, invented quotations, and conclusions that the evidence does not support.
A manager says an employee has "a bad attitude." You ask what happened, and the room gets quiet. The label carried the frustration but lost the facts. The examples below show how to recover the actual work issue, the employee's explanation, and a next step both people can understand.
What should a manager document?
Use six fields for a routine performance conversation:
- Expectation: the required work, standard, and date it was communicated.
- Observation: what happened, when it happened, and the source of the information.
- Impact: the specific work consequence, without exaggeration.
- Employee response: their explanation, disagreement, or information that needs checking.
- Support and action: what each person will do next.
- Follow-up: when progress will be reviewed and how it will be assessed.
This is Verk Vibe's suggested working format, not a required legal form. The EEOC's guidance on performance and disability discusses clear expectations, consistently applied standards, and accommodation considerations.
Example 1: a missed deadline
The examples below are fictional teaching examples. Adapt the structure to the actual facts and relevant policies.
Weak record: "Jordan is unreliable and keeps missing deadlines. We discussed improvement."
Usable record: "The weekly inventory report was due at 2 p.m. Friday under the schedule shared Monday. The report arrived at 4:20 p.m. Jordan said the supplier file arrived late and showed the request sent Thursday. We agreed Jordan will flag missing inputs by noon Thursday. I will identify a backup supplier contact. We will review the next two weekly reports at our scheduled check-ins."
The second version gives the employee a clear action and records the manager's responsibility. It does not turn a late input into a personality judgment.
If the report's timing caused a specific consequence, document the verified consequence. Do not add a business impact simply because the form has a box for one.
Example 2: a quality problem
Weak record: "Casey is careless and needs to pay more attention."
Usable record: "Three orders in the sample reviewed Tuesday used an outdated shipping address. Casey said the saved customer record had not been updated. We checked the record and confirmed the old address was still present. Operations will correct the source record today. Casey will compare the shipping address with the approved order before release. We will review Friday's sample together."
This example changes the diagnosis. The initial complaint sounded like individual carelessness. The review found a source-data problem and a verification step that needed an owner.
A useful record can show that the system needs repair. Do not use documentation to preserve a conclusion after the evidence changes.
Example 3: behavior during a meeting
Weak record: "Morgan was disrespectful and not a team player."
Usable record: "During Tuesday's planning meeting, Morgan spoke over two colleagues before they finished presenting their proposed schedules. I asked participants to finish one at a time. Morgan said the proposed deadline was unworkable and requested time to explain the staffing constraint. We agreed to reserve a separate review of the constraint and to use the facilitator's speaking order in the next meeting."
Record both the conduct and the substance of the concern. A staffing objection may deserve review even when the meeting behavior needs coaching. Consider whether the concern involves protected activity before treating it as misconduct.
The NLRB's concerted activity guidance explains that certain employee efforts to address working conditions are protected. The factual context matters.
When should managers involve HR before proceeding?
Pause for an appropriate review when the issue involves a potential accommodation, protected leave, a discrimination concern, a recent complaint, disputed pay, or other protected activity. Managers should know the route for escalating these situations.
An employee can raise a medical-related need without using the word "accommodation." Keep medical details in the appropriate restricted process rather than in ordinary coaching notes. Ask the designated HR contact how to record the work expectation while the request is assessed.
For complaint-related situations, the EEOC's retaliation guidance makes clear that protected activity does not remove accountability for legitimate performance issues. It also does not permit punishment for raising the concern. An independent review of the proposed action can help examine the reasons and evidence.
How soon should you write the note?
Write it close enough to the event to preserve accuracy. Include the actual date written and the date of the conversation. If you document later, say so. Never backdate a note or make reconstructed detail look contemporaneous.
Share the work expectations and follow-up with the employee through an appropriate channel. Acknowledgment of receipt should not be treated as agreement with every statement. Preserve the employee's substantive response and investigate factual disagreements that matter.
Can Ai write performance documentation?
An approved tool can help organize a factual draft when its use and the data involved are authorized. The manager remains responsible for verifying every sentence. Do not ask a tool to invent examples, infer intent, supply missing quotations, or strengthen a record to justify a predetermined result.
Make documentation part of the management rhythm
The record becomes useful when the follow-up happens. Review the commitment, confirm whether the support was provided, and document what changed. A collection of notes with no follow-through is an archive of unfinished management.
A useful test: remove the employee's name from a note and ask another manager what should happen next. If they need the unwritten backstory, revise the record before relying on it for a decision.
Explore ManagerOS for a repeatable management rhythm, or read the performance management field note to connect individual conversations to an ongoing system.