A Coworker Took Credit for My Work: What to Say, and Who to Say It To

In the readout, the forecast model came up as "the model we built." You built it. You had walked your peer through it the week before so they could field questions, and now the VP was nodding at them, and you said nothing, because correcting a colleague in front of leadership costs more than the credit is worth. "A coworker took credit for my work" is how you will put it that evening, to someone outside the company, which is the only place it gets said.

Then most people do the thing that feels safe. They book time with their manager and open with "I wanted to flag something about Casey."

That sentence feels like reporting a fact. It gets heard as opening a case. You have turned a two-person problem into a three-person one, and you are the one who escalated it. Your manager now owns a conflict they did not have this morning, and the cheapest way to close it is to decide you are both a little bit right.

Go to the person first. Not to get an apology, and not to prove what they meant. Go to make one specific agreement about how credit gets named from here, because that agreement is the only thing that changes what happens in the next readout.

The 24 hours before you say anything

Wait a day. Not mainly to cool off, though that helps. Wait because three ordinary explanations look identical to theft from where you are sitting, and you cannot tell them apart until you check.

What were they actually asked to do? If a VP asked for a five-minute status and your peer gave it, "we" is the normal word for that. Nobody delivering a status update runs a credits roll. That version is not theft. It is a format.

What did they actually say? Reconstruct the sentences, not the feeling. "Here is what we found" is not a claim of authorship. "I built this" is. If there is a recording, a deck or a thread, read it. People remember the sting accurately and the words badly.

What did the room already know? If your name has been on the doc for six weeks and you were in every working session, one "we" did not erase you. If nobody in that room has ever seen your name near the work, the urgency is different.

Is this once, or is this the pattern? Once is an incident. Three times in a quarter is a pattern. The conversation is the same either way. The agreement at the end of it gets firmer.

Then write the trail down. One page, before you talk to anyone:

• The artifact and where it lives, with its created date and your name on it.
• The dates you shared it, and who with.
• The sentence that was said, as close to verbatim as you can get, and where.
• Who else was in the room.

This is not a case file, and you will probably never show it to anyone. It exists so your own account stays specific under pressure. Say "you have been doing this for months" without a date attached and you have handed the argument away.

The opening line

Say it in person, or on video with cameras on. One to one, within a few days.

The opening line has two jobs: name the specific thing, and leave the motive out. Motive is the part they can deny honestly. They cannot deny saying "the model we built." They can absolutely deny meaning anything by it, and once you are arguing about what was in their head, you are arguing about something neither of you can check.

The strong version is shorter, and that is most of why it works. One fact, one intention, and not a single word the other person can argue with instead of answering.

The three answers, and what to say to each

This has the same shape as most difficult conversations at work. The opening sentence decides whether the other person defends themselves or works with you. After that, it goes one of three ways.

"I did not realize"

The genuine one. You can tell because they get specific back: they name the moment, or wince at the right sentence. It is the most useful outcome available and the one most people waste, because relief feels like resolution and they leave without agreeing to anything.

Do not spend the goodwill making them feel worse. Take it and move: "I believe you. Can we agree on how we handle it next time, so neither of us has to think about it again?"

"It was a team effort"

The slippery one, because it is partly true and it sounds generous. It answers a specific point with a general truth, and general credit goes to whoever is standing in the room.

Do not argue about whether it was a team effort. Agree, then put the detail back: "It was, and I want to keep it that way. Within that, I built the model and wrote the recommendation, and those are the parts that came up as ours. I am not asking for a credits roll. I am asking that when the model comes up, my name comes with it."

Accept the frame, restore the specifics inside it. Arguing with "it was a team effort" makes you sound like someone who does not want a team.

The flat denial

"That is not what happened." Or the softer version: "I think you are reading too much into it."

Do not relitigate. You will not win an argument about a memory, and trying turns four minutes into something you both carry for a year. Say the fact once, drop the interpretation, and go to the future.

"We remember it differently, and I do not think we are going to settle that today. What I care about is how it goes next time."

Then propose the agreement anyway. If they will not accept even a neutral rule that applies to both of you, that refusal is information, and it is the first point where your manager becomes a reasonable person to talk to.

The agreement you are actually there to make

An apology closes the past. It does not change the next readout, and chasing one is why these conversations end with both people uncomfortable and nothing different. Behavior changes when there is a rule, and when the rule is specific enough that anyone can see it kept or broken.

Make it small, concrete, mutual and forward-facing. Mutual is the load-bearing part. You are proposing how the two of you present joint work, not issuing a restriction on them.

That message is the only written record you need, and its job is not evidence. It is a shared memory, so neither of you has to reconstruct what was agreed. It also does one quiet thing. If it happens again, you are no longer describing a feeling. You are describing an agreement that was made and not kept, and that is a fact a manager can act on.

Bringing your manager in, and the version where they outrank you

How to frame it as information

Three things justify telling your manager. The agreement was made and then broken. The person refused any agreement at all. Or the credit is feeding a decision being made right now: a promotion cycle, a staffing call, your review.

How you open decides whether you read as a colleague or as a complainer. If the person who took the credit is above you, the conversation is a different one: see giving feedback to your boss. A complaint asks your manager to do something about a person. Information tells them something they need to do their own job, and leaves the next move to them.

"I want to give you some context, not ask you to do anything. The forecast model in Tuesday's readout was mine. I talked to Casey about it directly and we agreed to name who did what at the top whenever either of us presents joint work. It came up the same way again on the 14th. I am telling you because you write my review, and I would rather you had this from me."

Notice what is missing. No adjective about Casey. No theory about why. No request. Three dated facts, one of which can be checked. If your manager does nothing, your name is still attached to the work in the head of the person who decides what you get next.

Avoid "always" and "constantly." One dated instance is worth more than a pattern you cannot cite.

When the person who took the credit outranks you

Same conversation, three changes.

Raise it inside a meeting you already have, not one you book. A booked meeting from someone junior reads as a problem before you open your mouth, and they arrive defended.

Frame the agreement as visibility you need rather than a rule they have to follow. "You are in rooms I am not in. When the model comes up in those rooms, it helps me if my name comes with it." That costs them nothing, which is what makes it easy to say yes to.

Ask for one small specific thing instead of a principle. "Would you be willing to name it as mine in your update to Dana this week?" A concrete yes is far easier to give than an abstract commitment, and once they have done it, they have set the precedent themselves.

If none of that moves anything, spend the energy on independent visibility instead. Send your own weekly update. Put your name on the artifact. Present the work yourself at least once, to the people who allocate the next one. A record that does not depend on someone else narrating it is much harder to take.

This does not work if the person did it on purpose and has done it before. Someone who takes credit as a habit is not going to be corrected by a level sentence in a hallway, and the useful move there is a written record and your manager, not a better conversation. We are describing the first time, which is most times.

Knowing the line is not the same as being able to say it

The whole conversation is about four minutes long, and maybe six sentences in it matter. You already know roughly what they are. That was never the hard part.

The hard part is that when you are sitting across from the person, your voice tilts up at the end, you add "I mean, it is not a big deal," and you leave with an apology and no agreement. That is the standard outcome for people who prepared carefully and had never said any of it out loud.

Rehearsing in your head does not count, because in your head Casey concedes on the second sentence. You need to have said "I built that model" to someone who answers "it was a team effort" and genuinely believes it, enough times that your next line comes out level instead of apologetic.