
When is Dismissal a Reasonable Outcome for Employee Misconduct?
A manager has an employee on a final written warning. There’s been another incident and the manager’s immediate reaction is that the employee has had enough chances. They know the business can’t keep dealing with the same problem and they’re ready to bring the employment to an end.
It’s an understandable response, especially when the earlier incidents have already taken considerable time to address. But an active final written warning doesn’t make dismissal automatic. The employer still needs to establish what happened this time and decide whether dismissal is reasonable in the circumstances.
This post is for: UK SME owners and managers in Great Britain considering dismissal following further misconduct where an employee already has a final written warning.
You’ll leave with: a practical way to assess that decision. It focuses on the judgement involved in choosing an outcome, rather than taking you through the whole disciplinary procedure or considering dismissal for poor performance.

Start with what happened this time
Imagine a maintenance business with an engineer who’s received a final written warning for repeatedly failing to complete the service records that customers and the office team rely on. The warning explained what needed to change, how long it would remain active and that further misconduct could lead to dismissal.
A few months later, another job record is missing. The operations manager is exasperated. The previous incidents caused considerable disruption and they believe the engineer has ignored a clear instruction yet again. From their perspective, dismissal seems the obvious next step.
Before reaching that decision, however, the business needs to understand the new incident on its own terms. Was the engineer expected to complete the record before leaving the site? Did they have access to the system? Was the problem a deliberate refusal, carelessness or something outside their control? A customer complaint or an incomplete record may establish that something went wrong but it doesn’t necessarily explain why.
In this example, suppose the engineer says the mobile reporting system was unavailable and they rang the office to pass on the essential information. That explanation needs checking, not accepting automatically or dismissing because of the employee’s previous record. What does the system log show? Who took the call? Was there an agreed alternative process for reporting when the system failed?
The earlier warning gives the manager a legitimate reason to take the latest concern seriously. It isn’t evidence that the latest allegation has been proved. That distinction matters because the eventual decision must be based on a fair examination of what actually happened, including the employee’s explanation.
What did the final written warning actually cover?
Once the facts of the new incident are established, the warning becomes relevant. Check that it was properly issued following a fair procedure, whether it’s still active and precisely what it covered. An active final written warning can make dismissal a possible outcome of further misconduct but its wording and the relationship between the incidents are relevant.
For our engineer, a warning about failing to complete service records is plainly relevant to another missing record. The question becomes less straightforward if the new concern is unrelated, particularly if it’s relatively minor. An employer shouldn’t treat the existence of any final warning as permission to dismiss for whatever happens next. The conduct, the warning and the employer’s rules all need to be considered together.
It’s also worth reading what the employee was actually told. Was the expected standard clear? Did the warning explain the consequences of another incident? If the requirement was vague or a new reporting system changed how the job had to be done, that may affect how reasonably the employee could have been expected to comply.
An expired warning needs particular care. It shouldn’t simply be treated as though it were still active; whether historical conduct can properly be considered depends on the circumstances and may require advice. The safer starting point is the current evidence and the status of the warning under the business’s disciplinary policy.
Hear the explanation before deciding
Managers sometimes reach this stage exhausted by the history of the problem. That makes it especially important not to allow the disciplinary hearing to become a formality. The employee must know the allegation and the possible consequences, have the relevant information and a proper opportunity to respond and be allowed to be accompanied where the statutory right applies.
In the engineer’s case, the explanation about the reporting system could change how the incident is viewed. The manager needs to establish whether the system was unavailable, whether the engineer passed on the information as claimed and what instructions applied when electronic reporting wasn’t possible. The employee should also have the opportunity to explain anything the initial investigation may have missed.
Any circumstances that might explain the behaviour or affect how seriously it should be treated need proper consideration. For this engineer, that could include whether the business had explained an alternative reporting procedure and whether previous difficulties with the system had been raised. Those circumstances won’t necessarily excuse the missing record but the manager needs to consider their relevance before deciding on an outcome.
The manager may still conclude that the engineer failed to meet a reasonable requirement. What matters is reaching that conclusion after considering the evidence and the employee’s response, rather than treating the hearing as confirmation of a decision already made.
What outcome would be justified in this case?
Once the latest incident has been examined, the manager needs to decide what it means alongside the engineer’s active final written warning. The warning is relevant but simply saying ‘they were already on a final warning’ won’t explain why dismissal is justified.
If the reporting system was working, the requirement was understood and the engineer again chose not to complete the record, the warning may carry considerable weight. If the system failed and the engineer followed the agreed alternative procedure, the manager could reasonably reach a very different conclusion. The investigation should establish which account the evidence supports before any sanction is chosen.
The manager should also consider whether another sanction would be appropriate and, if not, why. Would a further warning be likely to bring about the required change or does the latest incident show a continuing failure to follow an essential procedure despite a clear final warning? These are decisions to make on the facts, not assumptions based on how frustrating the earlier incidents have been.

Look beyond the engineer’s case before confirming the outcome
Even where the individual evidence appears clear, the business needs to consider how it has responded to similar conduct. Has another employee failed to complete an essential record in comparable circumstances and how was that handled? An active final written warning may justify a different outcome, as could differences in the seriousness of the misconduct, its consequences or any mitigating circumstances.
Consistency doesn’t mean making identical decisions in every case. Employers may have good reasons for reaching different outcomes and some individual circumstances must remain confidential. What matters is being able to explain those differences using relevant facts rather than personal impressions.
The business should also look at its own management practices. If managers have regularly allowed employees to disregard the procedure when work is busy, it may be difficult to justify taking serious disciplinary action against someone for doing something that’s previously been accepted. That doesn’t mean the requirement can’t be enforced but the employer needs to recognise any inconsistency before deciding what’s fair.
Only after weighing the individual case and the wider circumstances should the decision maker settle on an outcome. Dismissal may be a reasonable response to further misconduct following a final written warning but it isn’t inevitable. Where the facts are disputed or the outcome carries significant legal risk, it’s sensible to seek advice before confirming the decision.
Record the reasoning and communicate the decision properly
Once a manager with the authority to make the decision has reached an outcome, the written record should explain the misconduct found, the evidence relied upon, the relevance of the warning, any mitigation considered and why the chosen sanction is justified. It should be understandable to someone who wasn’t involved in the case.
A useful check before confirming dismissal
If you’re considering dismissal after further misconduct, try explaining the decision in a few sentences without relying on the phrase ‘final written warning’ as your main justification. What did the investigation establish? What did the employee say in response? Why does the combination of the latest incident and the relevant history make dismissal reasonable, rather than another outcome?
If you can’t yet answer those questions convincingly, there may be more to establish before making the decision. If you can, you’re in a stronger position to explain the outcome to the employee and demonstrate how it was reached.
Further reading
For the detailed disciplinary stages, see Handling Employee Misconduct in a UK Small Business: How to Respond Fairly
For investigating allegations, see How Thorough Does a Workplace Investigation Need to Be?
For common procedural pitfalls, see Are You Missing These Important Details in your Disciplinary Process?
Disclaimer
This article provides general information and practical guidance for employers in Great Britain. It isn’t legal advice and shouldn’t replace advice on specific employment circumstances. Different rules apply in Northern Ireland.
