What Item Should Not Be Documented On A Performance Evaluation: Complete Guide

10 min read

What if you could skip the awkward “we need to talk about your… uh, personality” part of every performance review?

Picture this: you sit down with your manager, the paper (or digital form) in front of you, and you both glide through goals, achievements, and growth plans. No cringe‑worthy sections about “office gossip” or “how often you bring donuts.”

That smooth ride isn’t a fantasy. It starts with knowing exactly what not to write down. Let’s dig into the one item that belongs nowhere on a performance evaluation—and why leaving it off can make the whole process feel a lot less like a trial and a lot more like a conversation.

It sounds simple, but the gap is usually here.


What Is a Performance Evaluation (Without the Jargon)

A performance evaluation is simply a structured conversation about how someone’s work lines up with the expectations of their role. Think of it as a roadmap: you look at where you started, where you’re now, and where you want to go Worth keeping that in mind..

In practice, the document that backs that talk usually contains sections for:

  • Goals and results
  • Core competencies or skill areas
  • Development needs
  • Future objectives

That’s it. Anything beyond those pillars tends to drift into the realm of “personal commentary,” which is precisely what we want to avoid.

The One Item That Doesn’t Belong

The single piece of information you should never document on a performance evaluation is personal, non‑job‑related opinions or observations—in other words, subjective judgments about a person’s character, demeanor, or private life that have no direct bearing on their work output Worth keeping that in mind..

Why? Because those remarks open a legal can of worms, poison morale, and derail the whole purpose of the review: improving performance, not policing personalities It's one of those things that adds up..


Why It Matters / Why People Care

It Keeps the Review Legal

Employers who slip personal opinions into evaluations risk violating anti‑discrimination laws. Imagine a manager writing, “John is too aggressive in meetings; he should calm down.” If “aggressive” is a coded reference to a protected characteristic—like race, gender, or disability—that line can become evidence in a lawsuit No workaround needed..

It Protects Employee Trust

When you read a line that feels like a personal jab, you shut down. Trust evaporates faster than a coffee left on a hot desk. Employees start to see reviews as weapons, not tools. And when trust is gone, engagement drops, turnover spikes, and the whole organization suffers But it adds up..

It Keeps the Focus on What Moves the Needle

Performance reviews are supposed to be about results, skills, and growth. Adding a “personality” checkbox distracts from measurable outcomes. The short version is: the more you focus on the job, the more you can actually help someone get better at it Small thing, real impact..


How It Works (or How to Do It)

Below is a step‑by‑step walk‑through of how to build a clean, effective evaluation that stays clear of that forbidden item.

1. Start With Concrete Data

Gather numbers, project milestones, client feedback—anything that can be verified Most people skip this — try not to. Worth knowing..

  • Example: “Delivered Project X two weeks ahead of schedule, saving the client $15,000.”
  • Example: “Achieved a 12% increase in quarterly sales, exceeding the target by 3%.”

2. Translate Data Into Competencies

Link the raw facts to the skill sets you care about.

  • “Demonstrated strong time‑management by consistently meeting tight deadlines.”
  • “Exhibited effective stakeholder communication, evident from the positive client survey scores.”

3. Highlight Strengths With Evidence

Don’t just say “great team player.” Show it.

  • “Led a cross‑functional team of five, coordinating daily stand‑ups that kept the project on track.”

4. Identify Development Areas—But Keep Them Job‑Focused

If there’s a gap, frame it around a skill, not a personality trait Worth keeping that in mind..

  • Bad: “Needs to be less negative in meetings.”
  • Good: “Would benefit from training in constructive feedback techniques to enhance collaborative discussions.”

5. Set SMART Goals

Specific, Measurable, Achievable, Relevant, Time‑bound goals keep the conversation grounded.

  • “Increase client retention rate by 5% over the next six months through proactive follow‑up calls.”

6. Document Support Resources

List the exact tools, courses, or mentorship opportunities that will help the employee meet those goals.

  • “Enroll in the ‘Advanced Negotiation’ workshop by Q3.”
  • “Pair with senior analyst for bi‑weekly data‑analysis reviews.”

7. Review and Clean Up

Before the manager signs off, scan the document for any stray personal comments. If something reads like “She’s too quiet,” replace it with a performance‑related observation or delete it entirely That alone is useful..


Common Mistakes / What Most People Get Wrong

Mistake #1: Mixing Personality With Performance

It’s easy to blur the line when a coworker’s demeanor seems to affect the team. Ask yourself, “Can I prove this with work output?The fix? ” If the answer is no, cut it Easy to understand, harder to ignore. Surprisingly effective..

Mistake #2: Using Vague Language

Phrases like “needs improvement” without context are meaningless. They also invite personal interpretation, which can drift into the forbidden territory Worth knowing..

Mistake #3: Over‑Documenting “Soft Skills”

Soft skills are important, but they belong in the same framework as hard skills—backed by examples. Even so, g. Here's the thing — don’t write “good vibe” or “friendly” unless you can tie those traits to a measurable outcome (e. , “received a 95% satisfaction score on client interactions”) Less friction, more output..

Mistake #4: Forgetting Legal Review

Many companies have a legal or HR checkpoint for evaluation templates. Skipping that step means you might unintentionally slip in prohibited language It's one of those things that adds up..

Mistake #5: Letting Bias Slip Into Comments

Even well‑meaning managers can let personal preferences color their notes. The antidote is a checklist: “Is this comment about work? Is it backed by evidence? Is it free of protected‑class references?


Practical Tips / What Actually Works

  1. Use a “Fact‑First” Template – Start each bullet with the observable action, then add the impact.
    Bad: “She’s often late to meetings.”
    Good: “Arrived 10 minutes late to three of five scheduled client calls, which delayed the agenda by an average of 12 minutes.”

  2. Keep a Living Performance Log – Encourage employees to jot down achievements weekly. When review time rolls around, the log provides a ready‑made evidence bank.

  3. Train Managers on Bias Awareness – A short workshop on “What belongs in a review” can cut the personal commentary by half.

  4. Separate “Culture Fit” From the Formal Review – If you need to discuss cultural alignment, do it in a separate conversation, not the evaluation document That's the part that actually makes a difference..

  5. take advantage of 360‑Degree Feedback Carefully – Peer comments are valuable, but they must be filtered for relevance. Only include feedback that ties directly to job performance.

  6. Set a “No‑Personal‑Opinion” Rule – Make it a line item on the evaluation checklist: “All comments must be job‑related and evidence‑based.”

  7. Use Clear Rating Scales – Numbers or descriptors (e.g., “Exceeds Expectations”) reduce the temptation to write free‑form personality notes.


FAQ

Q: Can I mention an employee’s “attitude” at all?
A: Only if you can tie it to a concrete work outcome. Instead of “attitude,” say “demonstrated a proactive approach by identifying three process improvements.”

Q: What if a manager truly believes a personal trait is hurting the team?
A: Address it in a separate coaching session, not the formal evaluation. Focus the review on observable performance metrics.

Q: Are there any exceptions for remote work settings?
A: No. Whether in the office or at home, personal opinions about “presence” or “energy” belong in a conversation, not the written review.

Q: How do I handle a situation where a peer’s comment is personal?
A: Filter it. If the peer says, “She’s always quiet,” ask for examples of how that quietness impacted a project. If none exist, discard the comment.

Q: Does this rule apply to entry‑level employees too?
A: Absolutely. Early‑career staff are the most vulnerable to vague, personality‑based feedback, so keeping it strictly performance‑focused is even more critical Easy to understand, harder to ignore..


Performance reviews don’t have to feel like a courtroom. By steering clear of personal, non‑job‑related opinions, you keep the conversation legal, constructive, and—dare I say—pleasant Easy to understand, harder to ignore..

So the next time you sit down to fill out that form, remember the golden rule: If it’s not about what they did, don’t write it down. Your employees will thank you, HR will breathe easier, and the whole process might just become something you look forward to each year.

And yeah — that's actually more nuanced than it sounds.

That’s the real win. Happy reviewing!

8. Build a “Evidence‑First” Template

A practical way to keep personal commentary out of the review is to redesign the form itself. Instead of open‑ended narrative fields, use a two‑column layout:

Performance Indicator Evidence (Date, Project, Metric)
Meets quarterly sales target $1.2 M in Q1 sales; 112 % of quota (02/12/2024)
Delivers code on schedule Completed Feature X in 3 weeks vs 4‑week estimate (03/05/2024)
Improves process efficiency Reduced onboarding time by 20 % (04/20/2024)

When reviewers are forced to fill in the evidence column, they naturally gravitate toward concrete facts. The narrative column can be used for brief, actionable recommendations—but only after the evidence has been logged. This design makes it impossible to slip in “She’s too quiet” without a supporting data point Not complicated — just consistent..

9. Conduct a “Pre‑Review” Check‑In

Before the formal evaluation period ends, schedule a 15‑minute “pre‑review” meeting. The purpose is twofold:

  1. Validate the evidence – Both manager and employee confirm that the logged achievements are accurate and complete.
  2. Identify gaps early – If a performance area is lacking, the employee gets a chance to address it before the final rating is set.

Because the conversation is anchored in the same evidence that will appear on the written review, there’s little room for off‑topic personal remarks.

10. Automate Redaction of Personal Language

If your organization uses an applicant‑tracking or performance‑management system, you can set up simple keyword filters. Words such as “friendly,” “aggressive,” “talkative,” or “introverted” can trigger a prompt for the reviewer to either replace the term with a measurable description or delete the line entirely. While automation isn’t a substitute for human judgment, it serves as a safety net that catches inadvertent bias before the document is finalized Small thing, real impact..

11. Provide a “Feedback‑Only” Channel

Sometimes managers feel compelled to share personal observations because they think the employee needs to hear them. Create a separate, informal feedback channel—like a quarterly “growth chat” or a mentorship log—where these observations can be documented and discussed. By segregating this from the official review, you preserve the integrity of the performance record while still giving employees the developmental input they need.

12. Review the Review

Finally, institute a peer‑review step for the review itself. A second manager or an HR business partner reads the completed form with a checklist that includes:

  • Are all comments tied to a specific, observable outcome?
  • Is any language subjective or personal?
  • Do rating scales align with documented evidence?

If the reviewer flags any issues, the original author revises the document before it’s signed off. This double‑check dramatically reduces the likelihood that personal opinions slip through.


Bringing It All Together

Implementing these safeguards doesn’t require a massive overhaul—just a series of incremental changes that reinforce one principle: Performance reviews are about work, not about who the person is. When you embed evidence collection, redesign forms, and create separate spaces for personal development conversations, you build a culture where feedback is clear, fair, and legally sound Easy to understand, harder to ignore..


Closing Thoughts

The temptation to sprinkle a review with personality‑based remarks is understandable; after all, people are complex, and managers often want to be helpful. Yet the cost of mixing opinion with evaluation—legal exposure, demotivated staff, and a tarnished employer brand—far outweighs any short‑term convenience. By institutionalizing evidence‑first practices, training managers, and using technology as a guardrail, you turn the performance review from a potential minefield into a strategic tool for growth But it adds up..

Remember the mantra that opened this piece: If it’s not about what they did, don’t write it down. Let that be the compass that guides every line you type, every rating you assign, and every conversation you have. When the focus stays on measurable results, you empower employees, protect your organization, and finally make the annual review something that everyone can look forward to Not complicated — just consistent..

Happy reviewing, and may your next performance cycle be the most objective—and the most productive—yet.

Just Got Posted

What's New Around Here

On a Similar Note

More from This Corner

Thank you for reading about What Item Should Not Be Documented On A Performance Evaluation: Complete Guide. We hope the information has been useful. Feel free to contact us if you have any questions. See you next time — don't forget to bookmark!
⌂ Back to Home