How to Handle Employee Performance Issues: An HR Guide

An employee performance issue is a persistent gap between actual work and documented standards, objectives, or quality requirements. HR should first be sure about the expectations, tools, authority and scope of role before treating it as an individual problem. HR owns process design, documentation standards, review cadence, escalation paths, and consistency across managers.

Key Takeaways

• Performance vs. conduct: Performance is about how well someone is doing their job and whether their work meets expectations. Conduct is about how they behave and whether that behavior follows company policies. Handle the two differently, with different evidence and processes.
• Diagnose the system first: Check expectations, resources, authority, priorities, feedback history, role scope, and manager assumptions before classifying an employee as underperforming.
• Equip managers: Rather than asking managers to wing it in difficult conversations, HR should give them a repeatable structure, objective documentation standards, and situation-specific language.
• Use defined timelines: Improvement windows should reflect the issue and the role's natural work cycle. An open-ended process is neither useful to the manager nor clear to the employee.

What Counts as a Performance Issue

A performance issue is a continuing gap between an employee's actual performance and the documented expectations. Examples include missing deadlines, repeating mistakes, poor quality work, or failing to complete important tasks to the standard needed. It is not about whether the manager likes the way the employee works. The important question is whether the employee is failing to meet a reasonable, established standard.

Gallup's latest U.S. data shows why the standard must exist before performance can be assessed: in the first half of 2026, only 49% of employees strongly agreed that they knew what was expected of them at work.

When It Is Not a Performance Issue

Before starting an underperformance process, HR should determine whether the gap belongs to the system rather than the employee. Check these eight conditions:

1. Undefined standards: No written baseline, measurable goal, or clear quality requirement was communicated.  

2. Resource or authority deficits: The employee lacks the tools, budget, training, headcount, or authority needed to deliver the expected result. Gallup reported that only 37% of U.S. employees strongly agreed in May 2026 that they had the materials and equipment needed to do their work correctly.  

3. Shifting priorities: Deadlines, project scope, or strategic priorities changed without corresponding changes to targets.  

4. Withheld feedback: The manager noticed the problem but waited until a formal review instead of giving the employee a chance to correct it.  

5. Unrealistic role scope: The role requires more work than one qualified employee can reasonably complete.  

6. Personal circumstances: A temporary personal or health-related circumstance is affecting output and requires the appropriate organizational support rather than an automatic performance process.  

7. Manager preference: The employee meets the documented standard but does not use the manager's preferred method or style. That is not automatically a performance gap. See: Are You a Bad Manager?.  

8. Uncommunicated role evolution: The role changed, but its expectations, description, or training were never updated.

For the standard itself, see performance expectations.

Performance Issues vs Conduct Issues

A performance issue is a capability or output gap measured against a work standard. A conduct issue is behavior that breaches a workplace rule or policy. Keeping the distinction clear determines what evidence HR collects, who leads the first conversation, and what process follows.

A missed sales target and a policy violation should not be handled through the same evidence or conversation. The former asks whether the employee can meet an established performance standard; the latter asks whether the employee followed an established rule.

Scope Boundary: This guide covers the people process, internal workflow and management enablement. It does not deal with employment law, jurisdiction specific requirements or dismissal procedure. The organization should seek the advice of qualified counsel when legal requirements or possible termination become an issue.

The Five Types and What Each One Needs

Poor performance has different causes, so HR should not give managers one generic response. Classifying the gap first makes the intervention more specific and easier to measure. Use performance gaps as a reference for measuring the distance between expected and actual performance.

The classification should guide the intervention, not become a permanent label. If evidence shows that the original diagnosis was wrong, HR should adjust the process.

Designing the Process: What HR Owns

Managers handle performance consistently when HR provides the infrastructure. This means defining criteria for what needs to be in place before a conversation, setting standards for documentation, establishing cadences for review, and determining when an issue is outside of the manager’s scope.

According to CIPD, performance management is a mix of objective setting, feedback, performance improvement, and ongoing review supported by fit-for-purpose HR processes for managers.

What HR Owns vs. What the Manager Owns

What Must Exist Before Any Conversation  

HR should verify three preconditions:

1. A documented job standard: An up-to-date description of duties and required performance.

2. Measurable performance goals or KPIs: Specific output, quality, or delivery expectations.  

3. A record of prior feedback: Evidence that the employee was told about the concern before it became a formal issue.  

This is a consistency requirement, not an exercise in building a case.

The Documentation Standard: Three Ways to Record One Incident  

Documentation should capture observable facts, dates, business impact, and relevant history. It should not rely on labels such as "lazy," "unmotivated," or "poor attitude."  

Consider a project lead who submits a client deck four hours late and includes incorrect financial figures.

Weak documentation:  

"Alex has a poor work ethic, seems unmotivated, and failed to submit the pitch deck on time due to bad time management."  

Why it doesn’t work: It labels the employee, assumes intent, and has no date, no evidence, and no measurable impact.

Moderate documentation:  

"Alex missed the deadline for the Client X presentation on Tuesday. The presentation was late and needed formatting corrections before sending."  

Why it is incomplete: It names the incident but leaves out the exact delay, the exact errors, the business impact and the history.

Strong documentation:  

"On Tuesday, September 15, Alex submitted the Client X pitch deck at 4:00 PM, four hours after the agreed 12:00 PM deadline. The account team therefore could not review the slides before the client meeting. Three financial projections also contained calculation errors and required manager revision. Similar deadline delays were discussed during one-on-one check-ins on August 12 and August 28."  

Why it works: It records dates, measurable facts, business impact, and previous feedback without adding a judgment about intent or character.  

Check-in Cadence  

Follow-up intervals should reflect the type of issue rather than a generic "check in regularly" instruction. See effective one-on-one meetings for guidance on structuring these check-ins.  

• Skill or quality gaps: Weekly reviews of work samples, errors, and technical questions.  

• Volume or pacing gaps: Biweekly reviews of completion rates, queue volume, and milestones. See meeting cadence.  

• Collaboration gaps: Monthly reviews that incorporate relevant stakeholder feedback.  

Gallup research also shows the cost of waiting for formal reviews: employees receiving weekly rather than annual feedback were 5.2 times more likely to strongly agree that they received meaningful feedback, 3.2 times more likely to say they were motivated to do outstanding work, and 2.7 times more likely to be engaged.

The Escalation Path  

HR should define where each level of the process fits:

• Level 1: Manager: Manager coaching, routine feedback, prioritization, immediate operational support.

• Level 2: HR: Ongoing gaps, disputes about the fairness of standards, or concerns needing HR process support.

• Level 3: Manager's manager: Review where the employee challenges the assessment, the manager's judgment is disputed, or a formal performance process requires additional oversight.

Equipping Managers for the Conversation  

HR should view the manager section as a toolkit it provides to managers, not general advice for managers. The toolkit should cover manager avoidance, conversation structure, language for each situation, and post-meeting documentation.

This matters because performance conversations are often delayed. SHRM reported that 61% of HR professionals said fewer than half of managers in their organizations effectively address underperformance or improvement areas among direct reports.

Unblocking Manager Avoidance  

When managers bring an underperformance issue to HR, the problem may already have existed for months. HR's first task is often to help the manager act rather than attempting to solve the employee's performance directly.  

Before the meeting, HR should help the manager:  

• Review two or three concrete examples.  

• Confirm that the expected standard is documented.  

• Check that the employee had the necessary resources and authority.  

• Rehearse the opening and the requested next steps.  

A useful external reference is Harvard Business Review's discussion of why managers often avoid corrective conversations because they anticipate defensiveness or relationship strain.  

The Conversation Structure  

Give managers a simple three-part structure:  

1. Open directly: Tell them why you are meeting and don’t spend the first few minutes softening the message up.

2. Present evidence: Use 2-3 specific examples and explain the business impact rather than reading an HR file out loud.

3. Close specifically: Set expectation immediately. Support available and date of next review.

For opening questions and meeting structure, see one-on-one meeting questions and how to run effective one-on-one meetings.  

HR expert Christopher D. Lee argues that traditional appraisals focus on past paperwork instead of forward-looking coaching conversations.

Situation-Specific Communication Guidance

Managers need language matched to the problem rather than a generic list of phrases.

See negative feedback examples for additional wording guidance.  

What the Manager Writes Down Afterwards  

After the meeting, the manager should send a structured summary to the employee and HR containing:  

1. The date, time, and attendees.  

2. The specific performance gaps and examples discussed.  

3. Agreed actions, expected outputs, and deadlines.  

4. Support, tools, or training committed by the manager.  

5. The next check-in date and cadence.  

This record supports consistency between managers and gives HR a clear basis for the next review.  

Three Situations the Standard Process Doesn't Cover

The standard process becomes less useful when the employee disputes the assessment, a former high performer suddenly drops off, or the rest of the team starts absorbing the performance gap. HR should adapt the process to each situation instead of treating every underperformer as the same case.  

The Employee Disagrees  

Employees can challenge the examples, argue the target was unrealistic, cite a change in scope or question the manager’s interpretation.

HR should double-check the pushback before automatically supporting the original assessment:

• Check if expectations changed.
• Verify that the data is accurate.
• Verify that the employee had the resources they needed If the counterclaim is not supported, go back to documented standards and evidence.

If the employee raises concerns about manager bias, HR can involve the manager's manager or use a structured review. See skip-level meetings.  

The important distinction is between disagreement that reveals a genuine process problem and disagreement that does not change the evidence. If the employee is correct about the underlying standard or circumstances, fix the process before continuing the performance intervention.  

The Former High Performer  

A sudden dip from a strong performer needs to be diagnosed before escalation. The question is what changed, not whether the current output is below standard.

HR should examine changes in role, workload, priorities, team structure, or engagement. Where appropriate, investigate signs of employee burnout or employee disengagement.  

The former high performer is still held accountable to current expectations, but the diagnosis may help clarify whether the first intervention should be workload adjustment, clearer priorities, role alignment or performance management.

The Rest of the Team  

Colleagues often notice when they are absorbing unfinished work. HR should protect the employee's confidentiality while making sure the team's workload remains manageable.  

Managers should not disclose performance details, PIP terms, or disciplinary information. They can acknowledge operational changes without discussing the individual's case. For example:  

"We're adjusting resource allocation and workflow capacity so the team can continue meeting its milestones."  

Where work is being redistributed, managers should make the new ownership clear rather than leaving high performers to absorb the gap indefinitely.  

How Long to Give an Employee to Improve

There is no single improvement period for every role. HR should set a range based on the issue, the role's natural work cycle, and what has already been tried. The process should have a defined endpoint rather than continuing indefinitely.

These are working ranges, not automatic deadlines. A role with a two-week production cycle should not be assessed like one with a quarterly delivery cycle.  

When an Employee May Need More Time  

Consider extending the window when:  

• Performance is improving consistently but has not yet reached the required benchmark.  

• Documented operational problems affected the employee's ability to deliver.  

• The employee is actively applying feedback and completing agreed training or corrective actions.  

When to Accelerate the Process  

A shorter review cycle may be appropriate when:  

• Performance continues to deteriorate despite clear feedback and support.  

• The gap is creating significant operational disruption.  

• The employee is not engaging with the agreed process.  

These decisions should remain tied to documented performance evidence rather than assumptions about attitude or intent.

When to Move to a Performance Improvement Plan

Where there is a significant performance gap after the setting of clear expectations, feedback, support and documented review, a Performance Improvement Plan is appropriate. HR should only approve the move if the organization can demonstrate that the employee understood the standard, had the resources to meet the standard, received meaningful feedback and was given a reasonable opportunity to improve.

Before moving to a PIP, HR should check the following:

• A documented history of performance concerns and feedback.  

• A clear job standard and measurable expectations.  

• Appropriate tools, resources, and support.  

• A defined improvement period and review history.  

• Manager and HR sign-off on the decision.  

This article does not explain how to write a PIP or provide a template. For that separate process, see how to write performance improvement plans and PIP examples.

Frequently Asked Questions  

What counts as a performance issue?  

A performance problem is a deviation of actual work from established job standards. If someone regularly misses deadlines, makes avoidable mistakes, delivers substandard quality or fails to meet specified output requirements, and has the necessary tools and authority to succeed, then they have a performance issue.

What is the difference between a performance issue and a conduct issue?  

Performance concerns relate to capability and output against work standards. Conduct concerns relate to behavior against organizational policies or rules. They require different evidence and processes, so HR should not automatically treat conduct as a type of performance problem.  

Who should handle a performance issue, the manager or HR?  

The manager is responsible for day-to-day feedback, expectations, coaching and performance monitoring. HR owns the process framework and documentation standards, consistency across managers and formal escalation support. Instead of just stepping in and taking over the conversation, HR should prepare the manager.

How do you tell an employee their performance is not good enough?  

State purpose clearly, use 2-3 specific examples, explain the gap against the documented standard, and set dated next steps. Don’t judge attitude or personality. End by stating a clear expectation, what support is available and when the next review will be.

How long should you give an employee to improve?  

The appropriate window depends on the role and issue. A practical starting range is 14–30 days for operational roles, 30–60 days for specialist roles, and 60–90 days for senior or strategic roles, with the review cadence matched to the work cycle.  

Should you put an underperforming employee on a PIP straight away?  

No. HR should first check the standard, tools, authority, prior feedback, and improvement opportunities. A PIP is a formal next step for persistent gaps that have not been addressed with clear expectations, feedback, support, and documented review.