Short version: "Bad attitude" is a feeling, not a fact, and it won't hold up in a performance improvement plan or an employment dispute. The fix is to document specific, observable behaviour — what happened, when, and what was expected — which also gives employees a real, coachable path to improve.

Every dealership manager has said it at some point: "They just have a bad attitude." And honestly, they're probably right. But here's the problem when it's time to document performance issues: you can't put "bad attitude" in a Performance Improvement Plan. You can't defend it in an employment dispute. And you definitely can't coach someone out of it when neither of you can agree on what it actually means.

This is one of the most common gaps we see in dealership HR across North America. A situation builds over time, frustration grows, and by the time someone decides to act, the only thing in writing is nothing at all.

Getting this right is not about being overly formal or turning your store into a legal minefield. It's about being fair to the employee, protecting the business, and actually giving people a real shot at improving before things get to a breaking point.

Why doesn't vague language hold up?

Words like "bad attitude," "not a team player," or "doesn't get along with others" feel accurate in the moment. They might even be accurate. But from a documentation standpoint, they're nearly useless.

Anyone reviewing that record later, whether it's an HR lead, a labour board, or a lawyer, is going to ask: what exactly did this person do? When? How often? "Bad attitude" is a feeling, not a fact. And feelings don't hold up when decisions are being questioned.

This is where most performance conversations fall apart. The issue exists, but it was never defined in a way that can be proven. What does hold up is specific, observable behaviour, the kind you can point to, date-stamp, and describe without editorializing.

Why does vague feedback actually make performance worse?

Vague feedback doesn't just create legal exposure. It actually makes it harder for employees to improve. If someone tells you that you have a bad attitude, you leave that conversation confused and probably defensive. You might walk away thinking you just need to smile more.

But if someone tells you that you interrupted a customer three times during their last service visit, and that you've had two survey complaints this month about customers feeling rushed, now you know exactly what to work on. The specificity isn't just for the file. It's what makes coaching actually stick.

This is something Megan Cole, VP at The Minory, explains: "If I say Megan has a bad attitude versus Megan, you dismissed that customer twice in that conversation. The second way is much more objective and much more actionable."

Feelings vs. facts: what does the difference look like?

Take the example of a service advisor getting customer complaints. The temptation is to write something like "needs to improve attitude with customers" or "be more professional." Those phrases might feel clear in the moment, but they leave far too much room for interpretation.

Here's how to translate vague observations into documentable behaviours:

• "Bad attitude" becomes: greets each customer by name within 30 seconds of arrival
• "Be more professional" becomes: no interruptions during customer explanations
• "Doing better with customers" becomes: zero dismissive remarks recorded in customer survey responses

Same underlying concern. Completely different paper trail. One is a feeling. The other is a checklist item you can either tick or you can't. If you can't clearly describe the behaviour, you can't stand behind the decision later.

What should performance documentation actually include?

The goal of any performance documentation is to describe what actually happened, when it happened, and what was said about it. That means noting:

• What was observed: the specific action or behaviour, not your read on what it meant
• When it happened: date, context, who was present
• What was said: the conversation you had with the employee, including their response
• What was expected instead: the standard they were not meeting

That last point is important. Employees can only improve what has been clearly defined. If the expectation was never set, the documentation of the gap is going to be weak.

This is something the HR4 2026 Automotive Workforce Report speaks to directly: when clear expectations are not set in the first 90 days, you are more likely to see both performance problems and early turnover. It's a pattern echoed in broader HR guidance on documenting employee performance, specificity is what makes a record usable.

How should managers document a performance conversation?

None of this requires managers to become HR specialists or spend hours on formal reports. It's about building a habit of writing things down while they're fresh. A quick note in an employee record after a conversation is enough:

"Spoke with [name] on [date] about a customer complaint received on [date]. Complaint indicated the customer felt rushed and that their questions were not answered. We discussed the specific interaction. Employee acknowledged the feedback and will focus on allowing customers to finish explaining before responding."

That's it. No legal language. No formal document. Just a record that the conversation happened, what it was about, and what the expected change looks like. Platforms like HR4 can help managers log exactly this kind of note directly into an employee's profile, so it's accessible to the right people and does not get buried in someone's email.

Why does good documentation protect everyone?

Good documentation is not about building a case against someone. Done right, it's actually the opposite. It's the proof that the employee was told what the problem was, given a clear picture of what good looks like, and supported in the process of getting there.

When a decision to terminate does eventually come up, the question is not whether the employee had problems. It's whether they were given a fair opportunity to fix them. Documentation is what shows that they were.

On the other side of that, clear documentation also helps you recognize when someone is genuinely improving. Progress that isn't recorded tends to get forgotten.

Frequently asked questions

Can you put "bad attitude" in a performance review or PIP? No. "Bad attitude" is subjective and hard to defend in a dispute. Document the specific, observable behaviouyr behind it instead — for example, interrupting a customer three times during a service visit — along with the date and context.

How do you document an employee's bad attitude? Record four things: what was observed (the specific action, not your interpretation), when it happened (date, context, who was present), what was said (the conversation and the employee's response), and what was expected instead (the standard they were not meeting).

Why does vague feedback make performance worse? Employees can only improve what is clearly defined. Telling someone they have a "bad attitude" leaves them confused and defensive. Pointing to a specific behaviour gives them something concrete to work on, which is what makes coaching stick.

‍How long should performance documentation take? A few minutes. A short note logged right after the conversation, what happened, when, what was discussed, and the expected change, is enough. It does not require formal legal language or a lengthy report.

See how HR4 helps dealerships document performance the right way

HR4's performance tools are built for dealerships specifically, so your managers can log coaching notes, track incidents, and build structured PIPs without switching between systems or losing the paper trail. Ready to see it in action? Book a demo with the HR4 team and we'll show you how it works for your rooftops.