How to support performance — and document the process
Most performance problems don't get worse because the employee can't improve. They get worse because the manager waits too long, says the wrong things, and skips the documentation. Here's the framework that fixes all three.
Every HR professional has lived this scenario: a manager comes to you wanting to terminate an employee who has, in their words, "been a problem for months." You ask for the documentation. There is none. Or there's one vague email from six months ago. Or there are notes that say things like "bad attitude" and "not a team player" — the exact phrases that turn a defensible separation into a wrongful termination claim.
Performance management done well isn't about building a paper trail to fire someone. It's about giving employees a real chance to succeed, supporting managers through hard conversations, and creating the documentation that protects everyone if things don't work out. This framework walks you through the entire arc, from the first informal coaching conversation to a formal Performance Improvement Plan to separation — with the documentation language and escalation logic built in.
In an at-will employment state, you generally do not need documented cause to terminate. But "at-will" does not protect you from discrimination, retaliation, or wrongful termination claims — and those claims almost always come down to whether the documentation tells a consistent, objective story. The cost of doing this wrong is measured in five and six figures, plus the time and morale damage to your team.
1. Address Performance Concerns Early — and Informally
The single most common performance management mistake is waiting too long to say something. By the time the manager is frustrated enough to involve HR, the employee has often been struggling for months without clear feedback — and now feels blindsided when formal action begins.
The first stage isn't formal documentation. It's a coaching conversation: clear, specific, and timely. The goal is to name the gap, understand why it exists, and agree on what changes.
A good coaching conversation has four parts
- Specific observation — "In the last three weeks, four customer escalations have come back to your queue because the initial response missed key information." Not "your work is sloppy."
- Impact — "This is slowing down our team's response time and creating extra work for the leads."
- Inquiry — "Help me understand what's getting in the way." Listen before you problem-solve.
- Clear expectation — "Going forward, I need every initial response to include the three required elements. Let's check in next week on how it's going."
Document the coaching conversation
Even informal coaching gets a brief written record. Not a formal write-up — just a manager's note in their own file. Date, what was discussed, what was agreed to. This is the foundation everything else builds on.
"Talked to Jamie about attitude problems. Hope it improves."
"3/12: Met with Jamie re: four customer escalations in past 3 weeks tied to incomplete initial responses. Reviewed required elements. Jamie agreed to include all three on every response. Follow-up scheduled 3/19."
2. Escalate to a Written Warning When Coaching Doesn't Hold
If the same concern continues after coaching — or if the conduct is more serious from the start (attendance violations, policy breaches, significant performance gaps) — the next stage is a formal written warning. This is where HR typically gets involved as a partner to the manager.
A written warning is not a punishment. It's a formal communication that says: this is the gap, this is the expectation, this is what happens if it doesn't change. Done well, it gives the employee one more clear opportunity to course-correct.
Every written warning includes
- The specific concern — observable behaviors or outcomes, with dates and examples
- The relevant policy or standard — what expectation has not been met and where it's documented
- The prior conversations — when the concern was first raised informally and what was agreed
- The required change — specifically what the employee must do differently, by when
- The consequences — what will happen if the required change does not occur (typically: further formal action up to and including termination)
- Support being offered — training, mentoring, schedule adjustments, accommodations
- Acknowledgment — employee signature confirming receipt (not agreement — receipt)
If the employee raises a protected concern during this conversation — a medical condition, a disability, a need for accommodation, a complaint about discrimination or harassment — the performance conversation pauses. You now have parallel processes to manage, and proceeding with performance action without addressing the protected concern creates significant retaliation risk. Loop in the right partners before continuing.
3. Performance Improvement Plan (PIP) — the Formal Structure
A Performance Improvement Plan is the most formal stage of the performance management framework before separation. It is also one of the most commonly misused tools in HR — written too vaguely to be actionable, set up with goals the employee cannot realistically meet, or used as a checkbox before a termination decision that's already been made.
Used correctly, a PIP is a structured 30, 60, or 90-day plan that gives the employee a documented, fair opportunity to demonstrate sustained improvement. It is also the document that protects the organization if separation becomes necessary.
A defensible PIP has six elements
- Specific performance gaps — the exact behaviors or outcomes that fall below expectation, with current data and prior documentation referenced
- SMART goals — Specific, Measurable, Achievable, Relevant, Time-bound. "Improve performance" is not a goal. "Close 90% of assigned tickets within SLA over the next 30 days" is.
- Defined timeline — typically 30, 60, or 90 days, with the end date stated
- Scheduled check-ins — weekly is best for 30-day PIPs; biweekly for longer plans. Each check-in produces written notes.
- Resources and support — what the organization is providing to help the employee succeed: training, tools, mentoring, additional feedback
- Stated outcomes — what happens at the end of the PIP depending on results: successful completion, extension (if appropriate), or separation
Before issuing a PIP, ask yourself: could a reasonable, motivated employee actually meet these goals in this timeframe with the resources I'm providing? If the answer is no, you don't have a PIP — you have a paper trail for a separation decision that's already been made. That distinction matters legally and ethically.
4. Documenting Every Check-In
The check-in documentation throughout a PIP is what makes or breaks the case if separation becomes necessary. Each check-in note should include:
- The date of the meeting and who was present
- Progress on each goal, with specific data where measurable
- Areas where the employee has improved (this matters — performance management isn't only about what's wrong)
- Areas where concerns remain, with specific examples
- Anything the employee raised — concerns, requests, explanations
- Any adjustments made to the plan or support offered
- Next check-in date and any commitments before then
Documentation language that holds up
The most important rule of performance documentation: describe observable conduct and outcomes, not personality or motive. You cannot defensibly document that someone "has a bad attitude." You can defensibly document that "during the 3/22 team meeting, the employee rolled their eyes and stated 'this is pointless' when assigned the project, and did not contribute further to the discussion."
"Lazy. Doesn't care. Bad attitude. Not a culture fit. Unprofessional. Difficult to work with."
"Missed three of five committed deadlines this period. Did not respond to two follow-up requests from team lead. Arrived 25+ minutes late to four scheduled team meetings."
5. The Escalation Decision — When to Move From Coaching to PIP to Separation
One of the hardest judgment calls in HR is when to escalate. Move too fast and you skip steps that protect the organization. Move too slowly and you let performance problems damage the team and demoralize high performers who are watching.
Move from informal coaching to written warning when:
- The same concern has been raised informally and has not changed after a reasonable period (typically 2–4 weeks)
- The conduct is serious enough on its own to warrant formal documentation (attendance, policy violations, significant errors)
- Multiple separate concerns are emerging that, together, indicate a pattern
Move from written warning to PIP when:
- The required change identified in the written warning has not occurred
- The performance gap is significant enough to require a structured, multi-week improvement effort
- The employee or manager has explicitly asked for a more structured path forward
Move from PIP to separation when:
- The PIP timeline has concluded and the goals were not met, with documentation showing the gap is consistent with what was identified in the plan
- The employee has explicitly refused to engage with the plan or its goals
- New conduct emerges during the PIP that itself warrants separation (gross misconduct, policy violation)
The right escalation, with the right documentation, every time.
Performance Guidance inside Compass gives you coaching conversation scripts, PIP templates with SMART goal frameworks, check-in documentation language, and an escalation decision tree built for managers who don't do this every day.
See How Compass Works →6. Coaching the Manager Through the Process
Most performance management problems aren't really about the employee — they're about a manager who hasn't been trained to do this well. They avoid the conversation, soften the message until it becomes meaningless, write documentation that won't hold up, or escalate too fast because they're frustrated.
HR's job is not just to manage the process. It's to coach the manager through it. That means:
- Helping the manager rehearse the conversation before it happens — what they'll say, what the employee might say, how to respond
- Reviewing draft documentation before it's delivered — checking for vague language, motive language, or anything that sounds like a personal attack
- Sitting in on the harder conversations when the manager is new to formal performance management or when the situation is sensitive
- Debriefing after each step — what worked, what didn't, what to adjust for next time
Managers who feel supported through these conversations get better at them. Managers who are left to figure it out alone produce the documentation that turns into wrongful termination claims.
7. If Separation Becomes Necessary
If the PIP concludes without sustained improvement, separation is on the table. This is not a moment to improvise. The separation decision should be reviewed against:
Before any separation decision:
- Is the documentation complete and consistent with the framework above?
- Has the employee raised any protected concerns (medical, disability, complaint of harassment or discrimination, request for accommodation) during the process?
- How have similar performance situations been handled with other employees? Is this decision consistent?
- Are there any factors that might suggest the performance issues are tied to a protected characteristic, a leave, or a complaint?
- Has legal counsel reviewed the file if the situation is in any way ambiguous?
- Have you considered offering a severance agreement with a release in exchange for a clean separation, where appropriate?
The separation conversation itself should be brief, respectful, and clear. State the decision, summarize the basis (referencing the documented process), explain the logistics (final pay, benefits, COBRA, return of equipment), and end the conversation. This is not the time to debate the decision, soften the message into ambiguity, or share opinions about the employee personally.
The Through-Line: Documentation That Protects Everyone
The best performance documentation tells a clear, chronological, objective story. Someone reading the file should be able to see what was expected, what was observed, what was communicated to the employee, what support was offered, how the employee responded, and what the basis for each escalation decision was.
That documentation protects the employee, who has a record of what they were told and what they had a chance to address. It protects the manager, who isn't operating on memory or impression. And it protects the organization if the separation is ever challenged.
None of this is about building a case against someone. It's about being honest, in writing, about how performance has been managed — so that whatever the outcome, the process was fair, the support was real, and the record stands up.
Stop rebuilding the performance management process from scratch every time.
Coaching scripts. PIP templates. Documentation language. Escalation decision trees. State-aware guidance for separations. All inside HR Compliance Compass.
See Pricing →