How to document a performance problem so it holds up later

Write what a stranger could verify

"Poor attitude" tells a reader nothing and looks like a pretext. "Interrupted two colleagues in the March 4 staff meeting and left before the agenda finished, after being asked on February 18 to stay through team meetings" is a fact pattern. Dates, behaviors, prior expectations, observable consequences.

Document the conversation, not just the conclusion

The record should show what was expected, when it was communicated, what support was offered, and how the employee responded. A file containing only the final warning suggests the earlier steps never happened.

Be consistent across people

If three employees have the same attendance record and only one is written up, the documentation becomes the evidence. Before issuing corrective action, check how the same issue has been handled with others in the same role.

Make improvement plans real

• Specific, measurable expectations rather than restated job duties
• A defined period, usually 30 to 60 days
• What support the employer will provide
• Scheduled check-ins actually held and briefly recorded
• A clear statement of what happens if expectations are not met

Before a separation

Run a readiness review: the documentation trail, comparator treatment, timing against any recent complaint or protected leave, final pay logistics and the meeting script. Ten minutes of preparation changes how the next twelve months go.