How To Get Someone Fired From Their Job

What Actually Makes a Termination Stick

Most people have a fantasy version of getting someone fired. They picture drama, confrontations, dramatic emails copied to the whole company. That's not how it works in practice. The people who actually get terminated are the ones where the paper trail makes it obvious, boring, and inescapable. The ones where HR can't possibly defend keeping them because the documentation does all the talking.

I've sat on the other side of these conversations more times than I'd like to count. The ones that work are never about being right. They're about being documented. There's a huge difference and most people conflate the two.

How To Get Someone Fired From Their Job Through Proper Documentation

The process starts long before anyone mentions termination. It starts with observable behavior that violates a stated policy or consistently falls below an expected standard. You need three things simultaneously: a written policy that the person has acknowledged, a clear record of how their behavior violates that policy, and a pattern rather than an incident. A single mistake, no matter how egregious, is rarely grounds for termination unless it's a zero-tolerance item like theft or physical violence. A pattern is what makes it defensible.

The first thing you do is write it down. Not an email. A contemporaneous record. The date, the specific behavior, the policy reference, the business impact. You write it on the same day, not three days later when you're frustrated enough to embellish. I've seen performance files fall apart because someone went back and rewrote notes from memory after a conflict. The discrepancies between the original note and the "refined" version destroyed credibility entirely.

The second thing is a conversation. You tell the person directly what the problem is, you reference the specific policy, you state the expectation, and you document that conversation. This isn't a warning shot across the bow. It's creating a record that the person was put on notice. Without that, any termination looks arbitrary. With it, it looks like the logical conclusion of a process the person had every opportunity to respond to.

Where People Mess This Up

The most common mistake is focusing on personality conflicts instead of policy violations. "They're difficult to work with" doesn't terminate anyone. "They sent three separate emails copying external clients that contained confidential pricing data, which violates Section 4.2 of the Data Handling Policy that they signed during onboarding" does. Keep it concrete. Keep it in writing. Keep it tied to something that exists outside your opinion.

Another mistake is going to a manager without going through the proper escalation path. If you have a direct report who is causing problems, you document it, you address it, and if it continues, you escalate to their manager and HR together. Skipping steps creates gaps in the chain of custody for the documentation. HR will ask when the first verbal warning was given, when the written warning occurred, what remediation was offered, and if the behavior changed between each step. If you can't answer those questions with dates and names, you don't have a case yet. I learned this the hard way. A colleague of mine spent six months building a case against another team member. He had emails, he had screenshots, he had witness statements. When we went to HR, the first question they asked was whether there had been any formal written warnings filed in the system. There hadn't. Every single interaction had been informal. The file was rejected. Not because the behavior wasn't real — it absolutely was — but because HR couldn't defend a termination based on informal complaints alone. We had to start over with formal documentation, which took another four months. By then, the person had transferred departments.

The Performance Improvement Plan Route

If the issue is competence rather than misconduct, the PIP process is your primary mechanism. This is where most people fail because they treat a PIP as a formality instead of a structured process. A proper PIP has specific, measurable goals, a defined timeline, weekly check-ins with documentation, and clear consequences if the goals aren't met. I've seen too many PIPs that say things like "improve communication skills" or "be more proactive." Those are meaningless. They can't be measured. They can't be defended in an unfair termination hearing.

The goals need to be things like "respond to all customer emails within 4 business hours" or "submit all reports by the 15th of each month with zero formatting errors." Measurable, time-bound, verifiable. And you need to track progress weekly with a short written summary that both parties sign. Not to be punitive. To create the record. The counter-intuitive part here is that a well-run PIP often leads to improvement. The documentation process itself forces clarity that was missing before. People who are genuinely struggling often respond to specific, structured feedback. The ones who don't improve are the ones who were never going to, and the PIP gives you the documented basis to move forward. Win or lose, you're in a stronger position than you were before.

When Documentation Isn't Enough

There are situations where the formal process won't protect you or the organization. If the person you're trying to get rid of has strong political connections, if they're in a protected category and the organization is risk-averse, or if you're in a small company where everyone knows everyone, the paper trail might not be sufficient on its own. In those cases, the documentation becomes necessary but not sufficient. You need allies. You need people who will corroborate your claims in writing. You need a narrative that multiple independent sources can support.

I worked with someone who needed to document a senior manager's behavior. This person collected three separate written statements from direct reports, two from cross-functional colleagues, and one from a client. Each statement referenced specific incidents with dates. HR still hesitated. The turning point wasn't more documentation — it was an internal audit that independently confirmed patterns the written statements had described. Sometimes the system needs external validation to move forward. There's also the question of whether you actually want this outcome. Terminating someone is disruptive. It creates vacancies, morale issues, potential legal exposure, and sometimes retaliation. Before you invest three to six months building a case, make sure the cost is worth it and that the alternative — transferring the person, letting them go voluntarily, restructuring around them — has been genuinely considered. I've seen people burn relationships and personal energy pursuing terminations that could have been solved with a transfer or a mediated conversation. One more thing worth noting: if you're the one being targeted by someone else using this process, the same documentation principles protect you. Ask for specifics. Request copies of any written complaints. Verify that policies were communicated to you in writing. Challenge vague language. The process only works against you if you can't hold it to account.