Coworker Taking Credit for Your Work? What to Say and Do

A coworker is taking credit for my work. Where do I start?

The first urge makes sense: get angry, correct it, tell everyone how it really went. But it's better to stop first and answer a few questions privately. This isn't defending your coworker. It's a way to act precisely.

1. Is the work really mine, or did we do it together? Often several contributions overlap in reality.
2. What exactly did he say? "We prepared the solution" may be perfectly fair. "I ran the research," if he didn't, distorts a specific contribution.
3. Did he know it was your part? Sometimes people just aren't aware of how tasks were split.
4. Is this a one-off or a pattern? One episode and five episodes call for different responses.
5. What matters most to me here: recognition, future assignments, performance review, fairness?

The last question is especially useful, because your answer shapes the strategy. If visibility to your manager matters, regular updates on your results will help. If fairness with this coworker matters, you need a conversation. If your performance review is the concern, talk with your manager.

The more clearly you distinguish the parts of the work, the easier it is to restore accuracy without discounting what the other person really did. That isn't weakness or giving in. It protects your position against the reply, "You're exaggerating."

If after this check you still feel it was unfair, that feeling has grounds, and it's worth raising. If it turns out contributions were split differently than you thought, that's useful to know too, and then it's enough to clarify expectations going forward.

How do I separate facts from assumed motives?

When you're hurt, your mind fills in the picture quickly: "He did it on purpose," "He always does this," "He's trying to undermine me." Those conclusions may be right, or they may come from exhaustion and hurt feelings. For a conversation and for decisions, what you need is facts you can verify.

Write down what happened like meeting minutes, without adjectives:

• Date and context. Meeting, chat, presentation, email.
• What you did. Concrete steps and results: analysis, writing, calculation, idea.
• What the coworker did. Their contribution: formatting, presenting, coordination.
• What was said. The words, verbatim if possible.
• Who was present.
• What supports my part. Document versions, tickets, messages, approvals.

Compare two versions. First: "He sneakily stole my work." Second: "At the meeting on the 12th, he said, 'I analyzed the data.' I did the analysis; the version from the 5th is saved in the shared folder." You can build a conversation from the second. From the first, you only get a fight.

A record like this lets you prepare a precise conversation without having to prove your coworker acted maliciously. You'll probably never know their motive for sure, and you don't need to. The fact and its consequences are enough: your contribution wasn't named, and it affects your visibility.

If situations like this hit you especially hard, it may not be only about this episode. The theme of recognition and a sense of professional worth is covered in why successful women still wait for validation.

How do I keep a record of my work without breaking any rules?

Many traces of your work appear on their own: document versions, ticket history, emails, comments, approvals. The goal isn't to build a case against someone. It's to avoid losing what already exists.

What makes sense to do:

• Save work in approved company systems with clear file names and dates.
• When you finish a stage, send a short email with the result and next steps; it also documents your contribution.
• Keep approvals where a manager or client confirms acceptance.
• Jot down dates and facts of disputed episodes for yourself right after the event, while details are fresh.
• In shared documents, leave comments with your name and the date.

What not to do:

• Forward confidential documents to your personal email.
• Secretly record conversations. Recording laws vary by state, and it can backfire.
• Break access rules or company security policies.
• Collect material in a way that looks like surveillance of a colleague.

These actions can hurt you: breaking company rules can undercut your own argument. If things turn into a serious employment dispute, talk to an employment attorney about how to document.

A good habit works ahead of time: when your results regularly leave a trail in shared systems even without conflict, there are fewer disputed moments. It isn't distrust of colleagues. It's ordinary work hygiene that protects everyone involved.

It echoes the visibility theme in my piece on invisible work in the office: what isn't named or written down easily dissolves.

What can I say in the meeting without making a scene?

In a safe work setting, you can add a short, factual clarification. It doesn't accuse and doesn't ask anyone to explain their intentions. It simply restores accuracy.

Lines you can adapt:

• "Yes, in the analysis I put together, we saw that pattern. I can walk through how I checked the data."
• "Just to break it down: I handled the research, Andrew built the presentation, and we agreed on the final recommendation together."
• "One detail on this section: I wrote it, so I can take questions on it."
• "Glad the result landed well. Here's how we got there: my stage was..."

What these have in common: they're specific, calm, and useful to the discussion. You're not saying, "That's my work, not his." You're adding information that was missing.

What to avoid in public: "Actually, I did that," sarcasm, listing every accomplishment of the past few months, or sliding into personal accusations. The more specific the episode, the easier it is for others to see exactly which inaccuracy you're correcting.

If you couldn't say it in the moment, that's okay. You can come back to it: "Going back to who handled the analysis, I'd like to clarify..." Late and clear is better than never.

Feeling nervous before a line like this is normal. You're stepping out of a habit of staying quiet. It helps to prepare the sentence and say it out loud. If sitting through possible displeasure is hard for you, I write more about it in why it's so hard to tolerate someone's disapproval.

What if speaking up in the meeting is hard or unsafe?

Sometimes jumping in is risky: senior leaders are present, the format doesn't allow questions, or there are people who bruise easily. In that case you can use an ordinary follow-up email.

Here's a sample short email after a meeting, with no accusations:

Hi all, wrapping up on the project. I prepared the data analysis and conclusions, Andrew put together the presentation, and we agreed on the final recommendation together. Next steps: ___ (who, what, by when). Materials are in the shared folder: ___.

There isn't a word in it about what happened in the meeting. But now the division of parts is on record in work correspondence. It helps not only you; the team gets a clear picture of who is responsible for what.

Another option: in a project status update, task tracker, or report, note who completed which part. If your team keeps such documents, that's a natural way to do it.

If none of these suits you, there's a conversation after the meeting, covered next. You don't have to fix things within the hour. Sometimes a calm discussion the next day works better than an immediate reaction in the heat of the moment.

How do I talk to my coworker one-on-one?

If the episode repeats, address the pattern directly, without sweeping accusations. Compare two sentences.

"You keep throwing me under the bus." "In the last two meetings, my analysis was presented as your work. It's important to me that contributions are named accurately. Let's agree on how we'll present joint results."

The second gives the person something specific to respond to, plus a proposed agreement. It doesn't demand an admission of guilt, but it offers a way forward.

A simple outline:

1. Pick a calm time and a private place.
2. Describe the fact: what was said and in what situation.
3. Say how it affected you or why it matters.
4. Propose a specific agreement.
5. Listen to the response.

Responses vary: "I didn't think about it," "I meant all of us," "You're right, sorry." Or defensive ones: "You're overreacting." Don't argue about motives. Return to the agreement: "Maybe I misread it. Let's still decide how we'll talk about results going forward."

Watch what happens next, too. A one-time slip may be fixed after the talk. If the person agrees and then it happens again, you need a different level of solution. Then it helps to discuss with your manager how responsibility is divided and how contributions are made visible, relying on documents and concrete episodes, not a diagnosis of your coworker's character.

When talking to your manager, skip "he stole my idea" and try: "I want my contribution to the project to be clear. Here's what I did, here's what my colleague did. How should we reflect that?"

If speaking directly is tense for you, the principles in personal boundaries without ultimatums can help.

What if my manager is the one taking credit, or speaking up is dangerous?

A separate case arises when the manager takes the credit, or objecting could bring consequences. A direct confrontation can be risky here, and it's important not to act in the heat of the moment.

First assess the real risks: how much you depend on this job, what alternatives you have, and how objections are usually received in your organization. Then consider safer channels:

• A trusted leader at another level, or a mentor within the company.
• An employee representative, union, or ethics hotline, if you have one.
• HR, if you trust its independence.
• A consultation with an employment attorney.
• Coworkers who saw your contribution and could confirm it if it comes to that.

Internal procedures and options differ, so a universal "report it right away" isn't enough. Sometimes it's smarter to build your own visibility first: share results more often in accepted formats, get confirmations from clients and adjacent teams, leave traces in systems. Sometimes it makes sense to think about changing jobs.

If the situation involves humiliation, pressure, threats, or discrimination, it's no longer a communication question. Seek specialized support, which may include HR, an employment attorney, or an agency such as the EEOC or your state labor department. Don't stay alone with it.

If the situation keeps you tense for a long time, you lose sleep or interest in work, or you feel constant anxiety, talk to your doctor or a licensed therapist. How you feel matters on its own, not just as a reason to fix work.

How do I make credit part of the process, and what can I do today?

For future projects, it helps to define in advance who's responsible for what and how results will be presented. A clear division reduces confusion as well as protecting credit. In a final document or status update, you can briefly list each person's contribution, if that fits your team's norms. This is especially useful where one person presents the work of a whole team.

It's also worth reporting your own results in the normal rhythm of work, before any conflict. A short update on finished tasks, findings, and the next step helps your manager see what your work consists of. That isn't an obligation to promote yourself nonstop. It's part of sharing information, without which even a conscientious manager may only know what they hear in group meetings. For how to talk about your work without sounding like self-promotion, see how to talk about your work.

For a small step today, do three things:

1. Pick one episode.
2. Write a two-sentence clarification: what you did and how you propose to present the result going forward.
3. Reread it for accusations you can't back up and for needless justification.

The goal isn't to prove your whole worth. It's to restore accuracy about one work fact.

Sometimes the correction will be taken calmly, sometimes it will take a sequence of steps, and sometimes you'll discover a systemic problem in the environment. Don't promise yourself that perfect words will bring justice. But silence doesn't have to be the only way to keep professional relationships intact. You can mark authorship calmly, taking into account shared contribution, real risks, and your own right to be seen in the work you actually did.