Gross misconduct is behaviour serious enough to justify dismissal without notice, decided through an investigation rather than declared by a manager.
Gross misconduct is behaviour serious enough to destroy the trust an employment relationship rests on, which allows an employer to dismiss without notice and without working through the usual warning ladder. It is the shortest route out of a contract and the one most likely to be challenged, because everything hangs on whether the conduct really was that serious.
The most common misunderstanding is treating it as a list of acts. It is not. Gross misconduct is a conclusion reached at the end of a process, not a label a manager applies at the start of one. The same act can be gross misconduct in one context and a written warning in another, and the difference is usually intent, scale, whether it was concealed, and what the company did the last time it happened to someone else.
Listing these in the employee handbook is worth doing, because it removes the argument that nobody knew. But a list in a handbook does not make the finding automatic, and a tribunal will still ask what you actually established.
Summary means without notice. It does not mean without process, and the gap between those two readings is where most employers lose. The sequence is the same one that applies to any serious allegation: establish the facts, put the specific allegation to the person in writing, hear their response, consider it honestly, then decide and give the decision with reasons.
If someone needs to be kept away from the workplace while this happens, that is suspension, and it should be neutral: paid, short, explained as a protective measure and not as a finding. A suspension that runs for two months on full pay with no communication is itself evidence that the employer was not conducting an investigation so much as building a case.
Most legal systems put a hard deadline on dismissal for cause, measured from the day the employer learned of the conduct rather than from the day it happened. In Poland the window is one month from obtaining the information, and the notice of termination has to state the reason. Ukraine applies a one-month deadline from discovery and a six-month outer limit from the act itself. In Argentina the constraint is different but just as unforgiving: the dismissal letter has to set out the grounds clearly, and no new grounds can be introduced later if the case goes to court.
The practical consequence is that delay converts a strong case into a weak one. An employer who knows about the conduct, waits, keeps the person working normally for six weeks and then dismisses has undermined its own argument that the relationship was untenable. It also means the written reason has to be right the first time, because in most jurisdictions you are stuck with what you wrote.
The first failure is inconsistency: the same conduct that ended one person's employment was handled with a conversation for someone more senior, and the file shows it. The second is investigating to confirm rather than to find out, which usually looks like never interviewing the one witness who might contradict the manager. The third is a vague charge, where the letter says loss of trust instead of naming the act, the date and the evidence. The fourth is skipping the hearing because the facts looked obvious, which invalidates the dismissal in most systems no matter how obvious they were.
There is also a quieter failure worth naming: calling something gross misconduct because the real problem is capability and the company wants to avoid a performance improvement plan. Poor performance and misconduct are different routes with different evidence, and a conduct case built on a performance problem tends to collapse under the first serious question.
A dismissal for cause is the one exit where the gap between the decision and the loss of access actually matters. In Core HR, terminating a person deactivates their account and revokes system access in the same operation, clears any connected integration tokens, and triggers removal from the Google Workspace directory where that provisioning is enabled. Unfinished onboarding tasks and in-flight workflows can be cancelled automatically at the same moment, while the offboarding workflow itself keeps running, which is exactly the split you want when the departure is immediate.
The record side is deliberately rigid. The termination form will not submit without both a type of termination and a reason from lists you control, so a conduct dismissal cannot be filed as an unexplained exit, and the Termination breakdown report groups by those values. The form also carries the last working day and, separately, the last day in the office, which is what you need when someone is walked out before their formal end date. Direct reports can be reassigned to a named person or left unassigned from the termination date, so a team is not left reporting to a deactivated account. Documents generated for the exit pull employee fields and the termination date automatically from templates, and in accounts using the Kadry compliance module the process can generate a different document depending on the termination type, so a dismissal for cause and a resignation do not come out of the same template.
From Core HR to advanced workforce analytics — see the platform saving 80 hours a month for teams just like yours. Fully tailored to your workflow.