Underperforming employees are team members whose output, behaviour, or results fall consistently short of what their role requires. Identifying them early, diagnosing the real cause, and responding with a clear process protects your organisation from legal exposure, payroll errors, and team morale damage. This guide walks you through every step, from first observation to resolution. See the glossary for related HR terms.
What is meant by underperforming employees?
An underperforming employee is someone whose output, quality, behaviour, or process adherence consistently falls below what their role requires. The word “consistently” matters. One missed deadline or a difficult week does not make someone an underperformer. You are looking for a pattern that persists across a meaningful period.
Operational definition and measurable threshold
Before you raise a performance issue formally, agree internally on what underperformance actually looks like in numbers for that specific role. Without that, any conversation you have is subjective and hard to defend.
A sales rep 30% below target for three consecutive quarters is a clear case. An engineer whose code causes rollbacks repeatedly within a two-month window is another. A support agent whose satisfaction scores drop significantly while complaints stack up tells a clear story. Define the threshold before the conversation, not during it.
Evidence standard and legal defensibility
If it is not written down, it did not happen. That is the practical rule in performance management. A manager’s memory of “we talked about this six months ago” will not hold up in a dispute, and it will not help you defend a payroll decision either.
Document system data with timestamps, save quality notes with context, and write up coaching conversations on the same day they happen. If the employee pushed back or had a reason, note that too. A complete picture is more defensible than a one-sided file.
If you work across multiple countries, check local rules on employee data storage before you build your evidence file. Some jurisdictions restrict how long you can retain performance records or require the employee to have access to their own file on request. Getting that right upfront avoids a compliance problem on top of a performance problem.
How should you measure and document underperforming employees?
The metrics you use need to connect directly to what the role is actually supposed to deliver, and they need to feed the same systems that calculate pay. If HR tracks one version of performance and payroll calculates incentives on another, you will have errors and disputes you cannot easily explain.
Metrics tied directly to role success criteria
Pick two or three metrics per role that reflect real output, not activity. Closed deal value per quarter for sales, units per shift for production, first contact resolution for support. Keep them consistent across similar roles so you can compare people fairly and extract the data cleanly for payroll.
Avoid metrics that are easy to game or that depend heavily on factors outside the employee’s control. If you measure calls handled but ignore queue size, your data tells the wrong story. Review your metric set at least once a year to make sure it still reflects the role as it actually runs today.
Evidence collection, timelines, and storage
Capture evidence as it happens, not when things escalate. Reconstructing a performance record three months after the fact looks exactly like what it is: an attempt to build a case backwards.
Export metrics with timestamps on a regular cycle. Log coaching conversations in the official HR record the same day, not in a personal notebook or email chain. When pay is at risk, everything needs to be in the system that feeds payroll, not scattered across inboxes. Set a reminder to review stored records for completeness every quarter so gaps surface before they become a problem.
How do you handle underperforming employees in practice?
In practice, underperformance management is as much a coordination task as it is a people task. HR, the line manager, and payroll all need to work from the same information at the same time, or the process breaks down exactly when the stakes are highest.
Payroll-sensitive recordkeeping and system integration
When underperformance affects pay (variable comp, suspension, or final pay), a mistake in your records becomes a mistake on the payslip. That creates rework, legal exposure, and employee complaints that are hard to resolve.
Reconcile your incentive eligibility rules in the payroll engine with the HR performance flags before every pay run. Log pay-impacting decisions into the HR system the moment you make them. Before final pay goes out, validate the calculation against your internal payroll guidance line by line. If your HR and payroll systems do not share a real-time integration, assign a specific person to run that check manually at each pay cycle until the integration is in place.
How do you identify the root cause and classify it correctly?
Getting the diagnosis right matters more than most managers realise. Treating a skills gap as misconduct is one of the most common and expensive mistakes in performance management. It triggers the wrong process, produces the wrong outcome, and can expose your organisation to a wrongful dismissal claim.
Distinguishing capability, conduct, and mismatch
Capability means the employee does not have the skill or knowledge to do the job at the required level. Conduct means they choose not to meet expectations. Mismatch means the role itself may no longer be the right fit, even after genuine support.
Failed assessments and incomplete training point to capability. A clear policy breach with supporting evidence points to conduct. Someone who works hard, completes every development programme, and still cannot reach the bar is likely a mismatch. Each requires a different conversation, different documentation, and different next steps.
Checking for systemic and management factors
Before you conclude it is entirely the employee’s problem, check whether the system contributed. Poor onboarding, unrealistic targets, missing tools, and inconsistent manager feedback all show up as underperformance on the employee’s record even when the root cause sits elsewhere.
Check the onboarding file and training completion data first. Then look at whether the workload matched the targets for that role. Review how often the manager gave feedback and whether that feedback was clear and consistent. If you find gaps, fix them before you escalate. Escalating without addressing contributing factors increases the risk of an unsuccessful outcome and leaves the underlying problem in place for the next employee in the role.
Decision points that affect payroll and legal exposure
Some classification decisions change what you owe the employee in pay and what process you are legally required to follow. Getting these wrong is costly.
Withholding variable pay tied to performance criteria, suspending someone with or without pay, and setting the right separation date for final pay calculations all carry direct legal and payroll consequences. Do not make these calls without payroll and legal input. A short conversation before the decision is far cheaper than correcting it afterwards.
How do you run a performance improvement plan that works?
A PIP (performance improvement plan) only works if the employee understands exactly what success looks like, when you will review it, and what help they will get. A vague PIP is worse than no PIP because it looks like process theatre rather than genuine support.
Designing a focused performance improvement plan
Keep the plan to two or three concrete, measurable targets that connect directly to the role. Set a clear end date and build in mid-point check-ins so there are no surprises. Be specific about the support you are providing: is it weekly coaching, a course, a mentor, or additional resources? Put it in writing so both sides are accountable.
A PIP that says “improve communication skills” is not a PIP. One that says “respond to all client emails within one business day, measured over a six-week period, with bi-weekly manager reviews” is something you can both work with. Specificity protects you legally and gives the employee a genuine target to aim for.
Checkpoints, documentation, and privacy standards
Write up every checkpoint the same day it happens and save it to the official employee record. If the employee disagrees with your summary, note that too. An accurate, complete record protects you whether the outcome is improvement or escalation.
Keep the file restricted to those with a genuine business need. Store everything in line with your security and data protection policies. Loose files in shared drives or email chains create compliance risk that surfaces at the worst possible moment.
Escalation to formal discipline, redeployment, or separation
If the PIP does not produce sufficient improvement, the next step depends on your classification. A capability case may point toward redeployment if a better-fit role exists. A conduct case moves into your formal disciplinary framework. A mismatch that redeployment cannot solve leads to separation.
Hold the formal disciplinary meeting with a prepared agenda and document the outcome clearly. If redeployment is on the table, run a proper role-matching review rather than a quick reassignment. Before separation, reconcile final pay, accrued leave, and any outstanding incentive adjustments. Coordinate the close-out with HR integration so nothing falls through the gap between systems.
One detail that frequently causes problems at separation is the effective date. The date HR records as the last working day, the date payroll uses for final calculations, and the date communicated to the employee need to match exactly. A mismatch of even one day can trigger incorrect statutory payments, tax complications, or a dispute over notice entitlement. Confirm the effective date in writing before any system is updated.
What operational changes reduce recurrence and improve handling?
Most organisations that struggle with underperformance management are not struggling because of the individual cases. They are struggling because the underlying systems, metrics, and manager skills are not set up to catch and handle these situations well.
System and process fixes to prevent false positives
If your automated alerts fire too often, managers stop taking them seriously. Align role success criteria with measurable fields in your core systems so alerts reflect real sustained shortfalls, not noise. Add a human review step before any alert triggers a formal action. Harmonise your incentive eligibility rules between HR and payroll so the same decision produces the same outcome in both systems.
Manager training and accountability
Most performance management failures happen at manager level, not at HR policy level. Managers avoid difficult conversations, document things inconsistently, or escalate too late because they have not been trained or held accountable for doing it well.
Give managers a documentation template they can use immediately after a coaching conversation. Run calibration sessions so rating standards stay consistent across your management team. Then treat how a manager handles underperformance as a factor in their own performance review. That changes the incentive quickly.
Monitoring, audits, and continuous improvement
Run periodic audits of underperformance cases to check whether outcomes are consistent and fair across teams and demographics. Use people analytics to spot patterns: if one team generates five times more PIP cases than comparable teams, that is more likely a management or design problem than a hiring problem.
Track PIP outcomes and time to resolution so you know whether your process is working. Build integration health checks into your routine so HR-to-payroll data flows stay clean. Use your internal interface guidance to keep systems aligned as processes evolve.
What should you focus on right now?
Pick one thing: the last underperformance case your organisation handled and ask whether it was documented well, classified correctly, and resolved at the right pace. If the answer is no to any of those, that is your starting point. Fix the template, train the manager, or close the system gap that caused the problem before the next case arrives.
If you have not reviewed your PIP template in the last twelve months, that is a good place to start. Check that your current template requires a named owner, a specific metric, a timeline, and a support commitment. If any of those four elements are optional rather than mandatory, you are relying on manager quality rather than process quality. Making them required costs nothing and makes every case easier to manage and defend.