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

If a coworker just presented your work as their own, the best first move is a small one. Say one calm, factual sentence that puts your name back on the work, then follow up in writing the same day. You do not need to prove motive or win an argument. You need the record to show who did what.

This post covers how to tell what kind of credit-taking you are dealing with, what to say in the room and afterward, and how to build a record that makes your authorship hard to blur. For the mechanism behind the pattern, the Field Guide entry on credit theft and idea appropriation explains it. Here, the focus is on what you can do.

Work out which kind of credit-taking this is

Not every case of missing credit is the same, and the right response depends on which one you are in. These three groups are a practical way to sort what you see. They are working categories, not a research classification.

Opportunistic. A one-time slip. Someone summarized fast, used “I” when they meant “we,” or forgot where the idea started. The tell is that it does not repeat, and they fix it easily when it is named.

Structural. The system does not track authorship. A manager says “my team built this” and never names anyone, or leadership habitually credits the most senior person in the room. Nobody planned it, and arguing with one person changes little. The fix is to change how work gets attributed: named updates and written summaries.

Campaign. The same person, again and again, often in rooms you are not in. Your working document shows up in their slide. In the sharper version, they act as if they never saw your draft, which the Field Guide calls eavesdrop and erase. In the most extreme version, the roles get inverted so that they “led” and you “supported,” a move described in position inversion. Count the documented instances: one is a slip until proven otherwise, two is worth watching, and three within a few months from the same person is a pattern.

What to say in the room

Dana (composite scenario) built the churn analysis in a shared spreadsheet two weeks ago. In the Thursday review, a colleague presents it: “I pulled together some numbers on churn.” Dana feels her face go hot. She does not say “that was mine.” She says, “Glad the churn numbers are useful. I built that model, so I can walk through the assumptions if that helps.”

Nobody was accused. The room simply learned who owns the details.

Three lines you can adapt:

• “That builds on the draft I shared on the 3rd. Happy to take the questions on the details.”
• “Glad this is landing. I ran the analysis, so I can speak to how we got the numbers.”
• If a leader asks directly: “I did the analysis, and [name] helped present it.”

• Keep it to one sentence, and say it right away or not at all, since a correction three meetings later sounds like a grievance.
• State what you did, not what they did. "I built it" works. "You stole it" starts a fight about motive.
• Point forward: offer to explain the details, so the conversation stays about the work.

Why does a plain statement work? In three experiments by Madeline Heilman and Michelle Haynes, published in the Journal of Applied Psychology in 2005, participants read descriptions of a mixed-sex pair’s successful joint work. When it was unclear who had contributed what, the female member was rated as less competent and less influential than the male member. That devaluation was not found when the ambiguity was constrained, for example by feedback on each member’s own performance (Study 1) or by how the task was structured (Study 2). These were experiments with written descriptions, not real offices, and they studied women in mixed-sex pairs, so treat them as a pointer, not a promise. The pointer is useful, though: ambiguity about who did what is where credit was misattributed in these studies, and one clear sentence removes some of it.

Why not the accusation? Saying “you took credit” claims to know their motive, and a person who feels attacked often flips the frame and becomes the injured party. That reversal has a name in the Field Guide, DARVO. Facts about your work are harder to reverse than claims about their character.

What to say after the meeting

If the moment passed and you said nothing, that is common, and it is not too late. Two follow-ups do most of the work.

A short private conversation, within a day or two. Keep it low-key and specific: “In Thursday’s review, the churn analysis was presented without mentioning that I built it. I’d like the follow-up email to say so. Can you add that?” You are asking for one repair, not a confession. Someone who was merely careless will often agree.

A written recap to a small group. After the same meeting, send two or three lines to the people who were in the room: “Quick recap: churn analysis (built by me, draft shared on the 3rd) shows X. Next step is Y, owner Z.” It reads as ordinary project hygiene, and it puts authorship in writing without an argument.

If the person denies it, do not re-argue. Say, “Understood. I’ll keep the file history in the project notes,” and move on. The dated document does the arguing.

Build the record that makes credit hard to blur

Most of this is habit, not confrontation. The Field Guide entry on building the record yourself covers the full practice. These are the moves that matter most for credit:

• Send the draft before you present it, to your manager and one other person, with a one-line note: "Attaching the analysis I've been building for Thursday."
• Keep work in shared documents where version history shows who wrote what and when.
• Send a two-line recap within an hour of any meeting where your idea was discussed.
• Write your own updates with "I" for your work and "we" for shared work, so your own record models the precision you want from others.
• Keep a private, dated log outside company systems of what you shipped and what it moved. Two lines on Friday is enough.

Do not overdo it. Copying everyone on everything can look political and strain good-faith relationships. Match the intensity to the risk: light for a colleague who has never done this, heavier for a repeat pattern.

Why it is often about status, not only one person

If this keeps happening to you and not to the loudest person on your team, the cause may not be you. Research on how credit is assigned points to status.

A 2015 study in the Journal of Applied Psychology by Tabitha Howell, David Harrison, Elizabeth Burris and James Detert looked at 693 employees from 89 credit union units. Supervisors were more likely to credit employees who spoke up the same amount if those employees had higher status, whether that status was cued by demographic variables such as majority ethnicity and full-time hours, or by being central in the informal social network. The authors also found that even when certain groups of lower-status employees spoke up more, they could not make up for the effect of their demographic status.

A separate 2022 study in Frontiers in Psychology, using 418 matched leader and employee pairs at one large manufacturing company, found that leaders’ credit-claiming influenced employee outcomes through employee anger and perceived unfairness, and the outcomes measured were less voice behavior and lower job performance. It is one company and one questionnaire study, but it suggests leaders’ credit-claiming can have costs for organizations, not only for the person who lost the credit. A 2025 news release from the University of Toronto Scarborough on research by David Zweig and colleagues in a survey of over 1,500 workers makes a similar point: victims of what the researchers call knowledge theft reported being more protective and territorial about their work afterwards, including hiding their knowledge.

What this means for you: the goal is to remove ambiguity, so that credit does not default to the most visible or senior person. It is also a reason not to blame yourself when a good idea gets absorbed into someone else’s name.

When it is a pattern: how to escalate

Escalate on documented repetition and impact. Three dated instances, or any case where the missing credit affects a rating, a pay decision or a promotion case, is enough to take to your manager.

Frame it around outcomes: “Three times this quarter, work I did has been presented without attribution. I’d like our updates to name contributors, and I want to be sure my work is visible in review season.” That is specific and does not require anyone to admit to bad faith.

If your manager is the one taking credit, you need a second witness. The Field Guide entry on skip-level allies covers how to build relationships with people who can see your work directly before you need them. A skip-level manager who already knows what you do can correct the story without a formal complaint.

HR is usually not the first stop for a single incident. It becomes more relevant when the credit loss is tied to a protected characteristic, when you face retaliation for speaking up, or when a documented pattern has not been fixed by your manager. The post on whether to go to HR about bullying explains what HR can and cannot do, and how to document workplace bullying covers the record itself in more detail. This is general information, not legal advice. If you think the credit loss is tied to a protected characteristic or to retaliation, a local employment lawyer, union representative or advice service can tell you what applies where you live.

Where this stops being about credit

One stolen idea is a bad afternoon. A long run of them, alongside exclusion from meetings, mocking or a sudden fall in how you are described to others, is a broader pattern, and it deserves a broader response. Take it seriously without labeling anyone. This is a pattern, not a diagnosis. You cannot diagnose someone else, but you can protect your work and your record.

Sources