Office Chaos
A Coworker Takes Credit for Your Work: What to Say and Do
A coworker walks through a deck you built and describes it as their own. You can correct the impression without turning the project meeting into an argument. Identify the part you produced, offer the relevant detail, and decide afterward whether the incident needs a separate conversation.
Separate a missing mention from a false claim
Someone presenting the team’s results is not automatically claiming authorship of everything in them. Look at the actual wording and what the audience was likely to understand. “I put together this forecast” is different from “Here’s our forecast.” Either can deserve clarification if your role is being lost, but the request should fit what happened.
Write down the contribution at issue: the initial concept, the spreadsheet, the customer research or the final recommendation. Include work other people added. A useful account might read, “I built the forecasting model; Chris checked the assumptions and presented the recommendation.” That gives your manager something more concrete than a dispute over who deserves credit.
Use a short correction in the meeting
Pick a statement that lets you rejoin the discussion. These are sample scripts, not quotations from real coworkers.
| What happened | What you could say | What it achieves |
|---|---|---|
| Your model is presented without context | “I built that model using September’s numbers. I can walk through the assumptions.” | Connects your name to a specific contribution |
| A shared idea becomes one person’s achievement | “Chris and I developed that together. Chris handled the interviews; I mapped the options.” | Restores shared credit |
| An update assigns your deliverable to someone else | “One correction for the project notes: I drafted that recommendation. The version history is in the shared folder.” | Fixes the record |
| You need time to respond | “I’ll follow up with the details of my part after this call.” | Creates room for a calm follow-up |
Use the same audience as the original misunderstanding where possible. A small correction to the project group is usually more proportionate than copying a senior leader who had no involvement.
Ask for a specific change afterward
A private conversation works best when it ends with something you can check. For example: “In today’s update, you said you created the proposal. I wrote the first draft and tested the scenarios. Please add that to the recap, and I’d like to present the analysis in Thursday’s review.” If the coworker says they meant the whole team, you can acknowledge that explanation and still ask for accurate project notes. Agree on the correction itself, who will make it and when. “I’ll be more careful” is harder to follow up than a revised slide or an agreed co-presentation.
SHRM’s guidance on credit-taking also recommends checking the context, discussing the concern directly and making contributions visible before escalating where needed. It offers professional advice, not a guaranteed outcome.
Keep project evidence where it belongs
Use the tools your company permits: document history, assigned tickets, shared drafts, review comments and delivery messages. A timestamp helps establish when work happened; it does not prove that nobody else contributed. Keep a short description of your role alongside the record.
For a performance review, collect the project, your contribution, the outcome and a link to the relevant internal record. For ongoing work, use brief updates that identify owners and next steps. You do not need to turn every Slack reply into a claim of authorship.
Keep confidential files in approved systems. Don’t forward customer material or company documents to a personal account to build a case.
Bring a repeated pattern to your manager
If the correction is refused, the behavior continues or the issue affects a performance review, ask your manager to help resolve the attribution. Bring a few clear examples and explain what you have already requested. Ask for a concrete process: named owners in the project brief, a corrected review entry or a chance to present your own work.
“My contribution to these two projects is missing from the team recap. I’ve asked for it to be corrected. Can we agree on how contributions will be recorded before the next review?” makes the request clear without claiming to know the coworker’s motives.
If your manager is the person taking credit, consider another appropriate leader, HR or a trusted employee representative. Where you fear retaliation, get support before deciding whether to confront the person alone. The right route depends on the organization and the situation.
Make the next project easier to attribute
Agree up front on who develops each part, who approves it and who presents it. A project lead can own delivery while contributors retain recognition for the analysis, design or implementation they did. Credit works better when it is attached to the actual work rather than whoever happens to be on the final call.
If your responsibilities keep expanding without meaningful recognition, read about ghost growth at work. If the issue is a coworker withholding access or context, the guide to knowledge hiding addresses that different problem.
Common questions
What if I don’t have a written record?
You can still explain your contribution and ask for clarification. Be clear about what you know and what you cannot establish. Start documenting future milestones through normal project updates.
Should I stop sharing ideas?
Consider asking to stay involved in the follow-up or presentation instead. If a repeated pattern makes ordinary collaboration difficult, discuss the working arrangement with an appropriate manager.
What if the coworker apologizes and does it again?
Refer to the new incident and the change you had agreed on. Ask for a visible correction and involve your manager if the agreement is not being followed.
Find the right coworker gift
Use the relationship, budget and vibe to narrow the catalogue.
0 comments