Sabotaging coworkers can make ordinary work feel unusually difficult. Information goes missing, deadlines are disrupted, mistakes are attributed to the wrong person, or colleagues quietly undermine decisions after agreeing to them. Yet not every disagreement, delay, or poor result is sabotage. The practical challenge is to recognize a repeated pattern without making an accusation you cannot support. This article explains how to separate observable conduct from assumptions, protect your work, address the behavior professionally, and involve the right person when direct handling is no longer sufficient.
How to Recognize and Handle Sabotaging Coworkers
#1. Separate Sabotage From Ordinary Workplace Conflict
Start by defining the problem carefully. A coworker who disagrees with your proposal, misses an occasional deadline, or makes an honest mistake is not necessarily sabotaging you. Sabotage involves conduct that appears designed, knowingly or repeatedly, to obstruct your work, damage your credibility, or prevent a legitimate task from succeeding.
Look for patterns rather than relying on a single frustrating incident. Relevant signs may include:
- Important information being withheld while others receive it.
- Private agreements being denied or changed without explanation.
- Your work being misrepresented to managers or clients.
- Last-minute changes that create avoidable errors.
- Commitments being undermined after a decision has been made.
- Mistakes being attributed to you despite clear evidence of another person’s responsibility.
- Negative claims about your work being circulated without being raised with you directly.
Context matters. A coworker may be disorganized, overloaded, confused about responsibilities, or working from incomplete information. Before concluding that someone intends to harm you, ask what facts you can verify and whether there is another reasonable explanation.
#2. Document Observable Facts and Their Impact
If the behavior is recurring, keep a factual record. Write down the date, situation, people involved, agreed responsibility, what happened, and the effect on the work. Save relevant emails, project updates, meeting notes, and version histories according to your organization’s normal practices.
Avoid writing conclusions such as “Jordan is trying to ruin my reputation.” Instead, record something more precise: “On Tuesday, Jordan agreed to send the approved pricing sheet by noon. The sheet was not sent, and a different, outdated version was provided to the client at 3 p.m. I had not received notice of the change.” This kind of record is easier to verify and more useful if a manager later needs to assess the situation.
Documentation is not a license to monitor people obsessively or collect private information. Its purpose is to clarify a work problem. Focus on material facts, business impact, and your own responsibilities. A concise record can also reveal that several incidents were unrelated rather than part of one deliberate pattern.
#3. Protect Your Work Through Clear Processes
You can reduce the opportunity for disruption by making responsibilities, deadlines, and decisions visible. After meetings, send a short summary identifying what was agreed, who owns each task, and when each deliverable is due. Use shared project tools or approved communication channels so critical information does not exist only in private conversations.
For example, after a planning meeting, you might write:
To confirm today’s decisions: I will prepare the draft proposal by Thursday at noon. Morgan will provide the updated product specifications by Wednesday at 3 p.m. We will use the version in the shared folder for Friday’s review. Please let me know by tomorrow if I have misunderstood any part of this.
This is not about building a case against a coworker. It is about creating a reliable work process that benefits everyone. Keep access appropriate, avoid unnecessary copying of senior leaders, and do not use documentation as a public warning or embarrassment tactic. Clear records protect the team as well as the individual.
#4. Raise the Issue Privately and Specifically
When the problem is serious enough to address, speak with the coworker privately if doing so feels reasonably safe and appropriate. Use a calm description of what you observed, explain the work impact, and ask for their perspective. Do not begin by labeling them dishonest, hostile, or a saboteur.
A useful conversation might sound like this:
I want to clarify what happened with the client report. We agreed that the final version would come from the shared folder, but a different version was sent without notice. That created conflicting information and required us to correct the report. Can you help me understand what changed?
For future reports, I need us to confirm any changes in the project channel before sending them externally. If you think a different version should be used, please raise that with me first so we can resolve it.
The other person may offer a legitimate explanation, identify a process failure, or deny responsibility. Listen without abandoning the facts. If the response becomes hostile, evasive, or accusatory, do not turn the conversation into an argument. Restate the practical expectation and end the discussion professionally.
#5. Set Boundaries Around Access, Communication, and Responsibility
A boundary is a clear statement about how you will work, not a threat designed to control another person. If someone repeatedly changes your work, bypasses agreed channels, or seeks access they do not need, adjust the process within your authority.
You might require approvals in writing, limit editing permissions where appropriate, or move important decisions into shared systems. You can also clarify which tasks you own and which decisions require joint agreement. These steps should be consistent with company procedures and should not prevent legitimate collaboration.
Consider wording such as:
I’m happy to review changes to the report, but I’m not comfortable with edits being made after approval without a recorded discussion. Please send proposed changes through the project channel so we can confirm the final version together.
Boundaries should be applied consistently, including when the other person is not involved. Otherwise, they may appear personal or retaliatory. Keep communication civil, provide necessary information, and avoid withholding resources that the coworker genuinely needs to perform their role.
#6. Involve a Manager or HR With a Focused Account
If the conduct continues, affects customers or deliverables, or cannot be resolved directly, raise it with your manager or another appropriate internal resource. Present the issue as a work problem supported by specific examples. Explain what you have already tried and what outcome you need.
A useful summary might include:
- The behavior or event you observed.
- The dates, deliverables, or decisions involved.
- The measurable or practical effect on the work.
- Any relevant documentation.
- The conversation or process change you attempted.
- The assistance you are requesting.
You could say:
I’m asking for help with a recurring coordination problem. On three occasions, the approved project file was replaced or bypassed without notice, and the resulting versions were sent to stakeholders. I have attached the meeting summaries and corrected files. I discussed the process privately with Alex and proposed using the shared approval channel, but the problem has continued. I need clarification about ownership and the required approval process.
Avoid presenting speculation as fact or demanding a particular punishment. Your manager may interpret the situation differently, need to speak with others, or discover a broader process problem. If the concern involves harassment, discrimination, threats, retaliation, serious misconduct, or a significant risk to clients or employees, use the organization’s established reporting route rather than relying only on an informal conversation.
#7. Maintain Professional Conduct While the Issue Is Reviewed
Being targeted—or believing you are being targeted—can make it tempting to retaliate, warn everyone about the person, or respond with the same tactics. Those reactions can weaken your position and create a second workplace problem. Continue to communicate respectfully, meet your own commitments, and keep your records factual.
Do not confront the coworker publicly, circulate accusations, manipulate files, or deliberately exclude them from information required for their job. If you need distance, keep interactions task-focused and use established channels. Ask a manager to clarify roles rather than announcing that the coworker cannot be trusted.
Also pay attention to your own interpretation. A stressful pattern may cause every delay to look intentional. Review the facts with a trusted, appropriately placed adviser who can help you distinguish a genuine conduct problem from a strained working relationship. The goal is not to win a personal conflict. It is to restore reliable work, protect professional standards, and ensure that concerns are handled fairly.
When the Situation Requires a Different Response
Some workplace problems should not be handled as an ordinary peer disagreement. If a coworker threatens you, retaliates after you raise a concern, destroys or falsifies important records, exposes confidential information, discriminates against someone, or creates a serious safety or compliance risk, seek guidance through the appropriate internal reporting process. Depending on the organization, that may include a manager, HR, compliance, security, or another designated resource.
Do not investigate beyond your role or confront someone in a situation that feels unsafe. Preserve relevant information, describe what happened accurately, and ask what steps you should take next. You do not need to prove a coworker’s motive before reporting conduct that creates a serious workplace concern.
For less severe but persistent problems, a manager may be able to improve the situation by clarifying ownership, changing approval points, separating conflicting responsibilities, or facilitating a structured discussion. Be open to solutions that address the process even if they do not confirm your interpretation of the coworker’s intent. A fair response focuses on conduct and impact, not on assigning a damaging label.
A Practical Conversation Framework
A direct conversation is most useful when it has a narrow purpose. Do not attempt to resolve every past frustration in one meeting. Choose one or two concrete incidents, explain the impact, and identify the future behavior you need.
You can use this structure:
- Describe the event: State what happened without exaggeration.
- Explain the impact: Identify the delay, confusion, rework, risk, or reputational problem.
- Invite clarification: Give the other person an opportunity to explain.
- State the expectation: Describe the process that should apply next time.
- Confirm the next step: Agree on who will do what and how it will be recorded.
For example:
During Monday’s handoff, the customer requirements were changed after I completed the draft, but I was not notified. I had to redo the document, and the team lost time before the review. Was there a reason the change was not posted in the project channel?
Going forward, let’s record requirement changes there before either of us updates the draft. I’ll acknowledge the change and revise the document by the agreed deadline.
If the person denies the event, return to the evidence rather than escalating emotionally. If they claim you caused a problem, ask for a specific example and address it separately. If the conversation cannot remain constructive, end it and involve the appropriate manager.
Closing Thoughts
Sabotaging coworkers are best handled through careful observation, clear records, reliable processes, and proportionate escalation. The strongest response is not a dramatic accusation; it is a disciplined effort to establish what happened, protect the work, and give the other person a fair opportunity to respond. When the pattern continues or the stakes are serious, involve the right internal resource with a factual account. Stay professional throughout, because your conduct is part of the evidence others will use to assess the situation.