What’s the one thing you should never write down on a performance evaluation?
You’re staring at a blank form, the deadline’s looming, and the HR handbook is whispering “be thorough.” Yet there’s a line that most managers skip over—because it’s the one that can backfire the hardest.
Let’s dig into that hidden trap, why it matters, and what you can actually put on the page instead Worth keeping that in mind..
What Is “The Undocumented Item” in a Performance Review
When we talk about “the item that should not be documented,” we’re not talking about a specific skill or KPI. It’s the type of comment that belongs in a hallway conversation, not on a permanent record Less friction, more output..
Think of it as the “off‑the‑record” feedback that feels urgent in the moment but can become a career‑sucking liability later. It’s the personal gripe, the vague “needs improvement” without evidence, or the subjective judgment that isn’t tied to measurable behavior.
In plain language: any observation that can’t be backed up with concrete examples, dates, or data should stay out of the written review.
The “Why” Behind This Rule
Most companies use performance evaluations as legal safeguards. If a manager writes something subjective, it can be pulled into a grievance or lawsuit. The HR playbook explicitly warns against “unsubstantiated statements Still holds up..
So the item you shouldn’t document is essentially unverified, non‑objective feedback And that's really what it comes down to..
Why It Matters / Why People Care
It Protects the Employee
Imagine you get a note that says “lacks initiative.That's why ” No project name, no date, no context. But you can’t refute it, and it sticks on your file for years. That vague line can block promotions, salary bumps, or even a new job offer The details matter here..
People argue about this. Here's where I land on it.
It Shields the Manager
Managers who put subjective judgments in writing open themselves up to accusations of bias. A single line like “doesn’t fit the team culture” can be interpreted as discrimination, even if the intent was harmless.
It Keeps the Review Process Credible
When reviews are filled with concrete, observable facts, they become a useful development tool. Vague, undocumented complaints turn the whole process into a “gotcha” exercise, and nobody trusts it.
How It Works (or How to Do It)
Below is a step‑by‑step guide to making sure your performance evaluations stay factual, fair, and future‑proof.
1. Gather Evidence First
Before you even open the evaluation form, pull together the data you’ll need Most people skip this — try not to..
- Project logs: dates, deliverables, outcomes.
- Metrics: sales numbers, bug‑fix counts, customer satisfaction scores.
- Peer feedback: documented 360‑degree comments, not just “they’re great.”
Having a folder of evidence means you won’t have to rely on memory or gut feeling when you write.
2. Translate Observations Into Behaviors
Instead of writing “John is lazy,” write “John missed the deadline for the Q2 report on May 12, delivering it three days late, which delayed the client presentation.”
Notice the shift: you’ve turned a judgment into a specific behavior that can be verified Worth knowing..
3. Use the STAR Framework
Situation – Task – Action – Result.
Every time you need to comment on a strength or a development area, structure it like this:
- Situation: The team needed a quick pivot for the new API.
- Task: Sarah was tasked with refactoring the authentication module.
- Action: She rewrote 1,200 lines of code in two days, coordinating with QA daily.
- Result: The release went live on schedule, and post‑launch bugs dropped by 30 %.
The STAR method forces you to anchor every statement in reality Most people skip this — try not to. But it adds up..
4. Separate Fact From Interpretation
Create two columns in your draft: “Observed Facts” and “Interpretation.”
- Fact: “Emily logged 45 support tickets in March, resolving 42 within SLA.”
- Interpretation (optional): “Shows strong time‑management skills.”
If you can’t back up the interpretation with another fact, leave it out of the written review. You can discuss it verbally instead That's the part that actually makes a difference. Surprisingly effective..
5. Keep the Language Neutral
Avoid loaded words like “always,” “never,” “good,” or “bad.” Stick to verbs and nouns that describe actions.
- Bad: “He never takes initiative.”
- Better: “He did not propose any new process improvements during the Q3 sprint planning.”
Neutral language reduces the chance of perceived bias Not complicated — just consistent..
6. Review With a Peer or HR
Before you hit “submit,” have a trusted colleague skim the document. Ask them: “Do any statements feel vague or unsupported?”
A fresh set of eyes catches the hidden “undocumented items” you might have missed.
Common Mistakes / What Most People Get Wrong
Mistake #1: “Soft Skills” Without Examples
Everyone loves to say “great communicator,” but if you can’t point to a presentation, a client email thread, or a facilitation note, that line is meaningless on paper.
Mistake #2: “Personal Preferences”
“Would be better if they smiled more” belongs in a coaching chat, not a formal review. Still, personal demeanor isn’t a performance metric unless it directly impacts job duties (e. And g. , a customer‑facing role with documented complaints).
Mistake #3: “Future‑Facing Vague Goals”
Writing “needs to improve leadership” without a development plan is a dead end. Pair every development area with a concrete action: “Enroll in the company’s ‘Leading Remote Teams’ workshop by Q4.”
Mistake #4: “Copy‑Paste Boilerplate”
Using generic templates verbatim can hide the fact that you didn’t actually assess the employee. Tailor each paragraph; otherwise you’re just filling space.
Mistake #5: “Over‑Documenting Minor Issues”
If an employee missed a single deadline but has a perfect record otherwise, flag it as a one‑off incident with context, not a recurring problem. Over‑documenting can inflate the perceived severity.
Practical Tips / What Actually Works
-
Start with a “What Went Well” list. Capture three to five concrete wins before you dive into development areas.
-
Use a “Data‑First” checklist. Before you write a comment, ask: “Do I have a date, metric, or source?” If the answer is no, skip it.
-
Turn every negative into a development action. “Missed deadline on X” becomes “Create a weekly milestone tracker for X project.”
-
Schedule a follow‑up conversation. The written review is a reference point; the real coaching happens in the meeting.
-
Document the conversation, not the judgment. After the meeting, add a short note: “Discussed deadline issue; agreed on tracker implementation.” This keeps the record factual.
-
put to work technology wisely. If your HR system allows attaching files, link the actual report or metric chart rather than summarizing it in text.
-
Mind the timing. Write the review within a week of the evaluation period ending while facts are fresh.
FAQ
Q: Can I mention a personal conflict in the review?
A: Only if the conflict directly affects work output and you have documented incidents (e.g., missed deadlines due to unresolved collaboration issues). Otherwise, address it privately.
Q: What if I truly don’t have data for a concern?
A: Hold off on writing it. Use the conversation to explore the issue and gather evidence before it becomes a formal record.
Q: Should I delete all “soft‑skill” comments?
A: Not at all. Soft‑skill feedback is valuable—just back it up with examples: “Led the post‑mortem meeting, facilitating input from all stakeholders.”
Q: How often should I update my evidence folder?
A: Ideally after each major project or quarterly review cycle. A running log prevents last‑minute scrambling Simple, but easy to overlook..
Q: Is it okay to use “I think” or “I feel” in the review?
A: Avoid it. Those phrases signal subjectivity. Replace them with observable facts or remove them entirely Small thing, real impact..
So there you have it—the one item you should never let slip onto the performance evaluation form: any comment that can’t be backed up with concrete, documented evidence.
Stick to facts, give clear examples, and keep the subjective stuff for the face‑to‑face chat. Your employees will thank you, your manager will thank you, and HR will thank you—because the review will finally be a tool that builds, not a weapon that wounds Took long enough..
