Performance Documentation: What to Write Down, When, and How to Avoid the Common Mistakes
Good performance documentation is factual, specific, timely, balanced, and shared with the employee, not just filed away. Write it down within two hours of the conversation, not two days. Record behavior and impact, never character labels. Document the good alongside the gaps, since a manager who only records problems will eventually convince themselves they have a bad team. A performance improvement plan should be the last step in a documented process, not the first time an employee hears there's a problem.
Most people managers treat documentation as a compliance chore, something to do after the fact, mostly to cover the company if a bad-performance conversation goes wrong. That framing misses what documentation actually does.
"I used to have a manager that would say, I don't trust my memory, but I do trust ink," said Ceci Caraccioli, an HR leader who has worked with global and multicultural organizations across Latin America, speaking at a recent Talentuch webinar. "There are even studies that say we remember things differently as time passes. Different people in the same event will remember it differently, just because that's how the brain and memory work."
That's the actual case for documentation: not paperwork, but protection against the unreliability of memory, for the manager and the employee both.
Why documentation matters more than it gets credit for
Ceci Caraccioli's argument rests on four points. Documentation ensures fairness and consistency in how employees are evaluated. It supports employee development, since a manager can't coach toward a gap they haven't clearly named. It matters for compliance, because HR needs established, verifiable facts when a decision gets challenged. And it survives turnover: when a manager leaves and a new one inherits the team, or when the original manager is simply on vacation, documented history is what lets the company make a fair decision without them.
"It protects everyone," Ceci Caraccioli said. "This isn't just for the manager. It's also good for the employee, because at the end of the day, the information points toward what the right decision needs to be."
The same record can drive three different decisions
A single well-documented example doesn't just support one type of conversation. It can support recognition, a promotion case, or a performance improvement conversation, depending on what the record actually contains.
Compare "you've done a good job" to something specific: "the information you provided at the beginning of the presentation was very useful, because now people understand what the company does and when to reach out." The second version is documentation-grade. The first isn't, and Ceci Caraccioli noted that recognition built on vague praise "is probably going to fall flat."
The same logic applies to promotion cases. Managers frequently walk into promotion conversations "ill-prepared," in Ceci Caraccioli's words, with only surface-level claims like "they've been crucial to the process." Without documented specifics, that claim can't hold up to scrutiny, no matter how true it is.
What to document
Not everything. Ceci Caraccioli was direct that documentation isn't about recording every interaction, it's about capturing five categories deliberately:
Category | What it actually captures |
Achievements | Specific actions, not general praise. What did the person actually do, not "they were great" |
Expectations | Goals set in writing, ideally SMART: specific enough that both sides can later agree whether they were met |
Performance gaps | Separated into metric/KPI gaps and behavioral gaps, described by what was observed, not how it was interpreted |
Coaching and support | What the manager did or said to help the person move from one performance level to another |
Key conversations and context | Salary discussions, career interest, and situational context (was the person new, untrained, or dealing with something that affected the work) |
The behavioral category deserves particular care. "Anything that has to do with behavior feels a little bit subjective," Ceci Caraccioli said. "But if we're specific about the things we've seen, and not how we're interpreting somebody's behavior, we're able to have a better conversation with that person about behaviors that are appropriate or inappropriate in the workplace."
When to document
Timing is not a minor detail, it's the difference between documentation that holds up and documentation that doesn't. Ceci Caraccioli's guidance: write it down within two hours of the conversation, not the two-day window that sounds reasonable but already erodes accuracy. This is also why she recommends structuring interviews and one-on-ones to run 45 to 50 minutes instead of a full hour, leaving 10 to 15 minutes immediately after to take notes.
"If you leave the notes for the end of the day, those notes are going to be 50% less effective than if you take them right after the conversation," she said.
Three moments call for documentation as a standing practice, not a one-off:
Every one-on-one, held regularly (more than once a month), documented, and sent to the employee so both people are working from the same record of what was said.
Every milestone, at the end of projects or defined periods, capturing what happened and how it went.
Before any formal step. A performance improvement plan should never be the starting point of a process. It's the end of one, built on documentation that already exists.
AI note-taking tools came up directly in the session: Ceci Caraccioli called them a legitimate option, but only with the agreement of everyone in the conversation, since some people are genuinely uncomfortable being recorded that way. Manual note-taking, she said, "is still a good skill to have."
The five quality rules
For documentation to be useful later, in a dispute, a promotion case, or a coaching conversation, it needs to meet five standards:
Factual. Describe what was said and done, not how it was interpreted. "They were angry" is an interpretation. "They raised their voice and said X" is a fact.
Specific. "Not punctual" isn't documentation. "Arrived after the scheduled start time three times in the last week" is.
Timely. Written as close to the event as possible, ideally within two hours.
Balanced. Recording only problems creates a distorted record, and a distorted sense that the team is worse than it is.
Shared. The employee should know what's being documented about them before it's filed, not discover it for the first time in a formal review.
Common mistakes that undermine documentation
Ceci Caraccioli named six patterns that show up repeatedly, and that quietly make documentation worthless when it matters most:
Biased language. Recording interpretation instead of observation gives the other person legitimate grounds to ask, "where is that coming from?"
Delaying and backfilling. Documentation written hours or days after the fact is measurably less reliable, not just less convenient.
Inconsistent terminology. If "meets expectations" or "against our culture" was never clearly defined, using it in documentation doesn't hold up.
Only recording problems. This skews the manager's own perception of the team and leaves employees feeling watched only for mistakes.
Vague language. Words like "improve" or "find good" mean nothing without a specific, completed sentence behind them.
Surprise documentation. If a formal review is the first time an employee hears about an issue, the documentation process failed well before that meeting happened.
Formal steps come last
One of the more practical points from the session: a performance improvement plan (PIP) should sit at the end of a documented sequence, not function as the opening move. Ceci Caraccioli's own question to managers considering a PIP is simple: how many times has informal coaching already happened, and was it documented?
The sequence, in order: informal coaching (documented, even if it happened casually in a one-on-one), then more direct documented conversations, then formal warnings, and only then a PIP. Working through that sequence often surfaces something else entirely, that the person needed more training, or that expectations were never clearly communicated in the first place, which changes the actual problem being solved.
Making documentation a habit
Documentation that only happens after something goes wrong isn't a system, it's damage control. Ceci Caraccioli's recommendation is to build a personal structure: a template for one-on-ones, a checklist of what to cover, whatever fits a manager's own style. There's no single correct format.
Two operational points matter more than the template itself. First, use the company's actual HR system (Workday, Cornerstone, or whatever the organization runs) instead of personal folders, since that's where the information needs to be when someone else has to make a decision and the original manager isn't there. Second, set a cadence for one-on-ones and keep it. Employees who can predict when these conversations happen come prepared to them, with their own examples of the work they've done.
What good documentation looks like
Ceci Caraccioli's closing checklist, distilled:
Write it down within two hours, not two days.
Describe behavior and impact. Never label character. Even positive labels ("you're my rock star") can feel like a weight rather than useful feedback.
Record the good as carefully as the gaps.
Tell the person what's being documented before it's filed.
"Documentation isn't paperwork," Ceci Caraccioli said. "It's how fairness gets proved."
Frequently asked questions
How soon after a conversation should I document it?
Within two hours if possible. Ceci Caraccioli's guidance treats the commonly cited "within a day or two" as already too slow, since memory degrades measurably in that window.
What's the difference between documenting behavior and documenting character?
Behavior documentation describes what happened: what was said, what was done, and its impact. Character documentation labels the person ("you're not a team player"). Labels invite disagreement and rarely lead to a productive conversation. Specific behavior descriptions do.
Do I need to document informal coaching, or just formal warnings?
Informal coaching needs documentation too, even a short email summarizing what was discussed after a one-on-one. Formal steps like a PIP should only happen after a documented trail of informal coaching already exists.
Should employees see what's being documented about them?
Yes. Sharing documentation, particularly from one-on-ones, gives the employee a chance to say "that's not how I meant it" or "that's not what happened," before the record becomes the basis for a formal decision.
Building a stronger team?
