A calm, evidence-first way to correct the record with the person, your manager, or the room — without starting a fight you cannot finish.
When a coworker presents your work as theirs, the move that works is specific and unemotional: name the deliverable, point to a record that shows your part, and ask for one concrete correction. Do it close to the event, in the smallest room that still includes the people whose opinion matters.
Most of these situations are settled in two conversations — one with the coworker, one with your manager — backed by a document, ticket history or email trail you can show rather than describe.
When to do it, and when to wait
Speak up when the credit is being attached to something that will be remembered or measured. Hold off when the only thing driving you is the last ten minutes.
- It happened in front of decision-makers. Your coworker presented [project] to a leadership review, client or all-hands and used "I" for work you did. Correct it in the room if you can do it in one sentence, or within 24 hours if you cannot.
- It is now written down. A status report, release note, project tracker, design doc, award nomination or customer email names them as the owner. Written records get copied into promotion packets and performance reviews, so they need fixing while anyone still remembers.
- It is the second time. A single vague "we" is usually sloppiness. A pattern — same person, same habit, across several deliverables — is a behaviour, and it will continue until someone names it.
- A review or promotion cycle is inside the next quarter. Credit that is uncorrected before calibration is credit you will not get back. Work backwards from your company's review dates.
- Your manager asked who did something and someone else answered. That is the cheapest moment to correct, because the question was already live.
Not yet: you are still angry, or you cannot yet point to a specific artifact — a ticket, a commit, a file version, a dated email — that shows your part. Wait until you can say what you did and show where it lives. Anger with no evidence reads as a personality clash, and that is the version your manager will remember.
Also wait if the work genuinely was shared and your real complaint is the proportion. That is still worth raising, but it is a different conversation: "I'd like the split described accurately," not "that was mine."
What to say
Keep every version short. The longer you talk, the more it sounds like a grievance and the less it sounds like a correction.
In the meeting, in real time
Spoken — correcting the record in the room
"Quick add on that — I built the [data pipeline / analysis / design] behind [project], so I can take any questions on how it works. [Name], do you want to carry on with the rollout part?"
This works because it claims the specific piece, offers something useful, and hands the floor back. Nobody has to lose.
One to one with the coworker
Spoken — private conversation
"I wanted to flag something while it's fresh. In [meeting/update] on [date], [deliverable] was described as your work. I did [specific part], and the [ticket / doc history / email from date] shows it. I'm not after a big correction — I'd like [the status update to name me / the contributors slide fixed / you to mention it to [manager]]. Can we do that this week?"
If they get defensive, do not argue about intent. Say:
Spoken — when they say it was unintentional
"That's fine, I'll take it as a mix-up. What I'd still like is [the specific correction]. Going forward, can we agree that whoever does the build presents that section?"
Email to your manager
Email — subject: Credit on [project]
Hi [manager],
Short note before our 1:1 so you have the detail.
In [meeting / report] on [date], [deliverable] was presented as [coworker]'s work. My part was [specific contribution] — [ticket number], [document link or file name], and the draft I sent you on [date].
I've spoken to [coworker] directly and [they've agreed to X / we didn't land on anything]. What I'd like from you is [my contribution recorded in the project summary / this reflected when you write my review / to present this section myself at the next readout].
Happy to keep it brief — I'd rather fix the record than make it a thing.
[Your name]
Slack or Teams, same day
Message — low-stakes nudge in a shared channel
"Adding context for anyone following along: the [component] in [project] was mine — happy to walk through the tradeoffs if it's useful. Thread here: [link]."
Use the channel version when the audience that saw the misattribution is the channel itself. Do not use it as a substitute for talking to the person.
Mistakes to avoid
| Mistake | Why it backfires |
|---|
| Saying nothing and hoping your manager noticed | Managers mostly see what is presented to them. Silence reads as agreement with the version in the room, and by review season the written record is the only version left. |
| Correcting them publicly with an edge in your voice | The room stops hearing the content and starts watching the conflict. You become the person who made the meeting awkward, which is stickier than the credit question itself. |
| Going to your manager or HR before talking to the coworker | Most employers expect a direct conversation first, and skipping it makes you look like you escalated a misunderstanding. It also hands the coworker a grievance of their own. |
| Arguing about their motives | You cannot prove intent, and they will deny it. "You stole my work" invites a fight; "the record is wrong, here is the ticket" invites a fix. |
| Relying on memory instead of artifacts | Without a dated document, ticket or email, it becomes your account against theirs, and your manager will usually resolve that by doing nothing. |
| Turning one incident into a campaign | Raising it repeatedly, in every channel, past the point where it was addressed makes the issue your reputation rather than theirs. Raise it, get the correction in writing, move on. |
The honest downside: sometimes you do everything right and nothing changes. Some managers avoid conflict; some organisations reward whoever presents last. Correcting the record protects your own account of your work, but it does not guarantee your coworker faces any consequence, and in a small team it can make the working relationship cooler for a while. Decide in advance whether you can live with that, because the alternative — saying nothing — has its own cost at review time.
If the answer is no
If the coworker denies it, your manager shrugs, or the correction never appears, shift from fixing one incident to protecting the next twelve months.
- Same week: Start documenting your own work where other people can see it. Assign tickets to yourself, put your name in document headers, send a short Friday summary to your manager. This is the single change that makes a repeat harder.
- Within two to four weeks: Ask your manager for named ownership on the next piece of work — in the project tracker, in the kickoff doc, in writing. Frame it as clarity for the team, not as a response to the incident: "Can we put owners against each workstream so handoffs are clean?"
- Within four to eight weeks: Ask to present your own work. Volunteer for the demo, the client readout, the stakeholder update. Presenting is the cheapest form of attribution and it is hard to argue with.
- Within one to two months, if it repeats: Follow the escalation route in your employee handbook — usually HR or a skip-level manager. Put it in writing, factual and dated, with the artifacts attached. What happens next depends heavily on the employer and on state employment rules, so read the handbook rather than assuming. If you think the treatment is tied to a protected characteristic, or you are worried about retaliation, that is a separate matter and worth raising with a qualified employment attorney in your state before you file anything.
- Over one review cycle, roughly three to six months: Keep a running record of your contributions — a simple dated list of what you shipped and the outcome. Bring it to your self-assessment. Even if the credit question is never formally resolved, your own documented account changes what your manager has to work with.
- Three to six months out: If the pattern continues and your manager will not act, treat it as information about the team rather than about you. Explore an internal move, talk to a manager on another team, or start a quiet external search with your record of work ready to describe. Attribution problems that leadership knows about and tolerates rarely resolve themselves.
At every stage, keep copies of your own work records somewhere you will still have access to if you change roles — within whatever your employer's policy allows for company material.
Frequently asked questions
How much should I actually ask for?
Ask for one specific, cheap correction rather than a general acknowledgement. Good asks: my name added to the contributors slide, the ticket reassigned, a line in the next status update, me presenting that section at the next readout, or my manager hearing the full account before review season. Asks that rarely work: an apology, a public retraction, or a promise about future behaviour with nothing concrete attached. If the credit affected a promotion case or a performance rating, say that directly to your manager and ask that your contribution be reflected in the written review — but keep the request about the record, not about compensation outcomes, which are decided through a separate process at most employers.
How fast do I need to say something?
In the room, within seconds, if you can do it in one friendly sentence. Otherwise, within 24 to 72 hours — long enough to cool down and gather artifacts, short enough that everyone still remembers who said what. Beyond about two weeks it becomes much harder, because people have moved on and raising it looks like you have been brooding. If you have already missed that window and a review is coming, do not reopen the specific incident; instead give your manager a written summary of your contributions across the period and let the record speak.
What if my manager is the one taking credit?
Managers routinely present team work upward, and that is normal — the problem is when your name never appears anywhere. Rather than challenging the presentation, ask for visibility you can control: request to join the meeting where the work is discussed, ask to send the readout yourself, or ask your manager directly how your contributions are being represented at the level above. If nothing changes over a couple of cycles, build relationships with your skip-level manager and peers in other teams through demos and written updates, so your work is known by people other than your manager.
How do I follow up if nothing happens after the first conversation?
Follow up once, in writing, within a week: "Checking in on the contributors line for [project] — happy to make the edit myself if that's easier." Offering to do the work removes the excuse. If there is still no movement after that second nudge, stop chasing the single incident and move to the longer-term steps: named ownership on new work, presenting your own results, and a documented record for your self-assessment. Repeated chasing of one correction costs you more credibility than the correction is worth.
Will raising this make me look difficult?
It depends entirely on how you do it. A short, factual, artifact-backed correction with a specific ask reads as professional. A general complaint about a colleague's character, raised more than once, reads as a conflict. Keep it to the deliverable, keep it brief, and close it out once you have the correction in writing. If your workplace treats any factual correction as troublemaking, that tells you something useful about whether your work will be fairly assessed there.
