The director smiles. “Brilliant work, Tom.”
Tom nods. He has just presented the analysis you spent the weekend building. Not once did he mention you. You're sitting two seats away, smiling the sort of smile that could crack a tooth.
Maybe he forgot. Maybe he thinks the slide belongs to the team. Maybe he knows exactly what he's doing. You won't settle that in the meeting. You can, however, make sure the right people understand what you contributed.
What to say when someone takes credit in a meeting
Don't open with “That's my idea” unless you want the entire discussion to become an argument about ownership. Link yourself to a specific part of the work and offer the next useful step.
“Just to add some context, I built the underlying model and tested the assumptions. Happy to take the questions on those.”
Good when you want recognition without suggesting the other person acted maliciously.
“Yes, that's the approach I suggested in Monday's review. I've put together a short plan for how we'd run it.”
You establish the history and move towards delivery.
“To clarify the split, I developed the analysis and Priya reviewed the commercial assumptions. We can both answer questions on it.”
Fairness matters. Don't take all the credit while asking someone else to share it.
Notice what's missing. No sarcasm. No “actually” delivered through gritted teeth. No attempt to humiliate your colleague in front of senior people. The point is accurate attribution.
What to do afterwards
Send a short note, ideally as part of the normal project follow-up. Mention the decision, what you delivered and what you'll own next. Make it easy for someone reviewing the project later to understand your work.
“Thanks for the discussion today. As agreed, I'll send round the revised model I developed, including the sensitivity analysis. Priya's feedback on the assumptions is incorporated. I'll also take the team through the outputs at Thursday's check-in.”
It's a project update, not a disguised accusation.
If the colleague clearly misstated the facts, you may also want a private conversation. Keep it plain: “I noticed the model was introduced as your work. I built it, and I'd like that reflected in future presentations.” Don't lecture. Make the request and listen to their response.
What if they keep doing it?
One ambiguous incident can be a misunderstanding. A repeated pattern is different. Start keeping dated records of the deliverables you created, the versions you shared and how the work was presented. Keep records in permitted company systems, without copying confidential client material into your personal email.
Then speak to your manager about the impact. Be specific about what you need, particularly if the missing credit affects a promotion, project allocation or performance review.
“On the last three projects I've built the core analysis, but that hasn't been clear in the leadership updates. I'd like us to agree how contributions are recognised going forward, especially for my review.”
This turns a vague complaint into a concrete question about assessment and fairness.
If your manager is also the person taking credit, consider another appropriate manager, HR or a trusted representative. Choose the route that fits the seriousness of the pattern and the policies available to you.
Four things that usually make it worse
- Sending an angry reply-all. The audience grows while the useful facts get lost.
- Claiming exclusive ownership of genuinely shared work. Be precise about who created, reviewed and approved each part.
- Talking about the person rather than the behaviour. Colleagues can disagree about motives; they can check documents and dates.
- Waiting six months to raise it. Specific examples become harder to remember and less useful when they're old.
What if the colleague genuinely didn't realise?
That happens. In many teams, the person presenting is speaking on behalf of several people. If they correct the record when asked, say thank you and move on. Your goal isn't to establish villains; it's to establish an accurate account of the work.
Sometimes it's worth agreeing a simple credit convention: name the analyst when the methodology is discussed, make sure the project update says who built what, and include the right people in questions they can answer.
What if you're junior and they're senior?
The status difference can make a public correction feel dangerous. Use the lightest wording that still does the job: “I worked on that analysis and can share the detail if helpful.” After the meeting, send your normal delivery recap to the appropriate team.
Also consider who can fairly corroborate the work: a project lead, reviewer or colleague who worked alongside you. Your case is stronger when it rests on visible evidence rather than on somebody taking your side.
When to take it further
If credit-taking forms part of sustained bullying, discrimination or retaliation, don't treat it merely as a public-speaking problem. Seek support through your workplace process and, if appropriate, a union representative or independent adviser. Acas explains what bullying at work can look like and where to seek help.
The sentence to remember
“I built that part of the work and can walk you through it.”
It's not especially theatrical. But it tells the truth, offers something useful and keeps you in the conversation. Much better than thinking of the perfect comeback on the bus home.