Capability vs conduct: choose the right route before you start

What's the difference between capability and conduct?

Capability covers skill, aptitude and health: the salesperson who works every lead and still misses target, the developer promoted beyond their current skills, the warehouse operative whose back condition now prevents heavy lifting. The defining feature is effort without result - the person is trying, and the gap remains.

Conduct covers choices: lateness without reason, refusing reasonable instructions, breaking clear rules, falsifying records, behaviour towards colleagues. The defining feature is the reverse - the result is achievable, and the person is choosing not to deliver it, or actively doing something the rules forbid.

The distinction matters because the law judges you on process, and the fair process for a can't looks nothing like the fair process for a won't. One is fundamentally about support; the other is fundamentally about accountability. You can't run both at once, and you shouldn't try.

Is it capability or conduct? A decision table

Real cases arrive as symptoms, not labels. This table maps the common ones - treat it as a starting hypothesis to test, not a verdict:

Notice how often the first step is a question, not a procedure. "Ask why" is doing the heavy lifting in that table because the answer routinely moves a case between rows - the lateness that turns out to be a caring crisis, the "attitude problem" that turns out to be undiagnosed illness.

What does a fair capability process look like?

Capability is a support process with a formal ending, not a punishment with paperwork:

• Say it clearly, early. The standard, the gap, the evidence - in a documented 1:1, not saved up for a formal meeting.
• Provide real support. Training, coaching, clearer priorities, removal of conflicting duties - whatever the gap actually needs.
• Give a reasonable period to improve, with reviews. A structured performance improvement plan with checkpoints is the standard vehicle; our template uses 2/4/8-week reviews.
• Warn honestly. The employee should know from the start that failure to improve could ultimately mean dismissal - hiding that is unfair, not kind.
• End with a fair formal stage. If the plan fails, a formal capability meeting with the right to be accompanied, a considered decision in writing, and an appeal - the same procedural spine the Acas Code expects. Capability dismissals are with notice.

What does a fair conduct process look like?

Conduct runs through the disciplinary procedure in the Acas Code of Practice: establish the facts through an investigation, tell the person in writing what's alleged with the evidence, hold a hearing without unreasonable delay where they can respond with a companion present, decide and confirm in writing, and offer an appeal to someone not previously involved. Tribunals can adjust awards by up to 25% for an unreasonable failure to follow the Code. We've written the whole route up, sized for a small company, in our small-business disciplinary guide.

How should ill-health capability be handled?

Health is capability's hardest corner, and it demands extra care. Get medical evidence before decisions - fit notes, and occupational health where the picture is unclear. Consult the employee genuinely: they usually understand their condition better than anyone in the room. And remember the Equality Act 2010: many long-term conditions meet the definition of disability, which triggers the duty to make reasonable adjustments - to the role, the hours, the targets, or the absence triggers themselves (see our guide to Bradford Factor exclusions). For mental-health absence specifically, a well-built phased return solves most cases before capability procedures are ever needed - our return-to-work guide covers that. Dismissal on ill-health grounds should be the genuine last resort, after adjustments and redeployment have actually been explored, not just mentioned.

Why does mislabelling one as the other lose tribunals?

Because unfair dismissal cases turn on procedure, and the wrong label means the right procedure never happened. March a struggling employee through a disciplinary and a tribunal sees someone punished for what they couldn't help - no support offered, no time to improve, no training: unfair, even though poor performance is a potentially fair reason. Drift genuine misconduct through months of vague performance chat and you've skipped the investigation and hearing the Code requires - and left the behaviour unaddressed for everyone watching.

The label also sets the tone in the room. People forgive being told they're not meeting a standard far more readily when the response is support rather than accusation - and tribunals notice which one the paperwork shows. From 1 January 2027, with the qualifying period down to 6 months, the cost of a mislabelled process arrives much earlier in every employment than it used to.

How CoDash keeps the route honest

Whichever route a case takes, it's won or lost on the record. CoDash keeps 1:1 notes and objectives documented against each person, PIP reviews timestamped, and ER case records in one trail - so when you have to show that the support was real or the process was fair, the evidence already exists.

Frequently asked questions