How to Handle It When a Coworker Takes Credit for Your Work

Understanding the Situation

In a new job you have no track record, so credit travels through whoever is in the room rather than through what people already know about you. Your work usually passes up a chain — you to a teammate, teammate to your manager, manager to their boss — and your name can drop off at any link. In a three-person team, everyone knows who built what. On a 30-person team with a weekly review meeting, the senior person summarizing the work is the only name the audience hears.

The mechanics that cause it are usually dull. A draft gets shared as an attachment instead of a file with edit history, so there's no author trail. A handoff happens verbally at a desk or in a direct message that nobody else sees. Someone says "we pulled the numbers" and the room hears "I pulled the numbers." Norms differ by industry too: in agency and consulting work the person who presents to the client is often credited by default, in software the commit and ticket history make authorship visible to anyone who looks, and in sales the account owner gets the win regardless of who built the proposal.

After one incident you usually cannot tell whether it was deliberate or careless, and you do not need to. The first-incident response is the same either way — name the specific piece of work, to the specific person, and make your authorship visible on the record going forward. If it is careless, that fixes it. If it is deliberate, it puts the person on notice and gives you something concrete to point at the second time.

Step-by-Step Response

1. Within 24 hours, write down the facts. Date, the meeting or email, the exact piece of work, and what was said as closely as you can recall. Then collect the artifacts: the message where you sent the draft, the ticket assigned to you, the version history on the shared file. You are not building a case yet — you are making sure that if you need details in three weeks, you have them.
2. In the next day or two, check what was actually said. If you heard about it secondhand, ask someone who was there: "Did the forecast section come up as a team thing, or did it land as Dan's? I built that part and I'm trying to work out whether that was clear to the room." Sometimes the answer is that your name was mentioned and the person relaying it to you missed it.
3. Day two or three, speak to the coworker directly. One incident, specific, no audience, no accusation of intent. Wording is in the next section. Keep it under two minutes and end with what you want next time, not an apology demand.
4. The same week, change how your work reaches your manager. Send deliverables to your manager directly rather than only through the teammate who consolidates them, with two lines of context: "Attaching the churn analysis — I built the model, Dan reviewed the assumptions." Keep drafts in a shared file that records who edited what, rather than emailing attachments back and forth, so authorship is visible without anybody having to remember it. Put your name in the document header.
5. By the end of the first week, start a short weekly update to your manager. Three to five lines, Friday, listing what you finished and what you're on next. This is not self-promotion — it means your manager can describe your work accurately when asked, which is the specific behavior that stops credit disputes before they start.
6. If it happens a second time, raise it with your manager within a few days. Bring the two dates and the two artifacts. Ask for a change to how work is attributed, not for a verdict on the coworker.
7. If it continues past 30 days of raising it, check your handbook before escalating further. What counts as a formal complaint, who receives it and what happens next vary a lot by employer, and in some countries and US states there are additional internal procedures. Read your own policy rather than assuming the process works the way it did at your last job.

What to Say

Directly to the coworker, a day or two after

You

"Quick thing about yesterday's review — when the retention slides came up, it sounded like you'd built them. I pulled that data and wrote the summary. Can we say it's both of us next time?"

Likely response

"Oh — I didn't mean it that way, I was just answering Maria's question."

You

"Fine, I figured. Easiest fix: send it to Maria with both names on it, and I'll send you my part by Thursday so there's time."

To your manager, after the second time

You

"I want to flag something factual. The March pricing model and last week's churn deck were both mine, and both got presented as Dan's. I've talked to him once already. I'm not asking you to referee — I'd like to send my work to you directly instead of routing it through him."

Likely response

"Dan does consolidate the team's work, that's his role."

You

"Then can the deck list who did each section? That solves it without changing the process."

In the room, while it's happening

Coworker

"...so I rebuilt the query and got it down to four seconds."

You

"Happy to take the follow-ups on that one — I wrote the query, so I can explain the caching trade-off if anyone wants the detail."

That offers useful information rather than correcting someone publicly, and it puts your authorship on the record in front of the same people who heard the claim.

Frequently asked questions