Back to insights

Employee Taking Credit for Others' Work: Correct the Record

A white line links a small open diamond to a facet in a larger divided shape; grey fragments remain disconnected.

A project reaches the leadership meeting with one person's name attached. Someone else says their work disappeared. Establish what happened, correct what you can support and be clear about what remains unresolved.

Author

Cooperly Team

Category

Manager Playbooks

Published

15 Oct 2026

An employee taking credit for someone else's work needs a specific response. Check the contribution behind the claim, hear the people involved and correct any misleading account where it mattered. Keep the question of intent separate from what you can establish about the work.

What you'll learn

  1. Establish actual contributions without treating an assignment or a final edit as the whole history.
  2. Correct an inaccurate account while keeping disputed or missing details explicit.
  3. Agree how the next update will credit the work, then check what actually happens.

Employee taking credit: check the actual claim

Ask the person raising the concern what they did, what was said about it, who received that account and what they want corrected. Locate the actual report, presentation or message. 'I presented the findings' and 'I did the analysis' describe different contributions. Check the wording before deciding what response is needed.

Speak privately with the colleague whose account is questioned too. A possible opening is: "In Monday's update, you described the analysis as your work. Another colleague says they built part of it. I want to understand what each of you contributed before correcting the account. Can you walk me through it?" This is an illustrative invitation, not a finding that anyone stole credit.

Keep the conversation grounded in observable behaviour and evidence. A confident explanation does not establish who did the work. Someone being upset does not disprove their contribution. Ask comparable questions of everyone involved, including yourself if your summary omitted someone.

Separate confirmed contributions from disputed history

  1. 01

    Identify the different contributions

    Ask who developed the idea, gathered the information, performed the analysis, checked it and prepared or presented the final output. These roles may overlap. Do not give someone sole credit just because their name appears on the final saved file.

  2. 02

    Check relevant work evidence

    Use records you are authorised to review: an existing draft, an agreed project note or the explanation behind a change. Ask about work that happened outside those records. A missing timestamp does not establish that someone contributed nothing, and a task list may no longer describe how the work was completed.

  3. 03

    State the limits of the account

    Write the contributions you can support and mark any specific point still disputed or unknown. Ask what further relevant evidence could clarify it and set a feasible time to return. Do not invent equal shares or percentages to make the disagreement appear resolved.

Consider a hypothetical customer-support report. One employee prepares the data and calculates response times. A second spots duplicate records, changes the calculation and presents the result. The presenter tells the founder, "I built the analysis." The original contributor objects.

The manager checks the drafts and hears both accounts. The evidence supports the first employee's data preparation and initial calculation, and the second employee's correction and presentation. A task sheet names the presenter as report owner; it does not erase the first contribution. Both employees claim to have suggested the original question in an unrecorded conversation. That detail remains disputed.

The manager can correct the sole-creator description without deciding who first suggested the question. The correction names the contributions the evidence supports and leaves the unresolved point open.

Correct the account where it mattered

The experiment included 662 full-time Prolific workers across four conditions, with 88% in the US and 12% in Canada. The figures compare different conditions; they are not a before-and-after measurement of the same people. Participants responded to an imagined advertising-work scenario, so the findings concern immediate reported anger, not proven repair of long-term workplace trust.

The study did not directly compare a private apology with a public correction. Correcting the affected account is a practical recommendation here: the people relying on an inaccurate description need an accurate one.

In the hypothetical report, the manager asks the presenter to correct the update to the founder: "A correction to my description of the report: my colleague prepared the data and initial calculation. I corrected the duplicate-record issue and presented the final result." The manager checks the correction. The disputed origin of the question is not reassigned to either person.

Use the channel and detail the correction requires. Amend the report's attribution if that is where the omission sits; correct the leadership update if that is where the sole-credit claim was heard. This does not require a company-wide announcement. Check with the affected contributor about the wording and who needs to receive it, without promising confidentiality you cannot maintain.

If a review, reward or development decision relied on the inaccurate account, take the corrected information to its authorised owner through the existing process. Explain what was wrong, what is now supported and what remains uncertain. Promise a review or response only if you can arrange one; do not promise a changed rating, pay decision or promotion.

When the evidence stays incomplete

If both people contributed but the record cannot establish who originated the idea, say that. Describe the contributions you can support without presenting either person's version of the origin as settled. Do not demand a forced apology for an allegation you have not established.

If the disagreement has become a wider working conflict, use the same fair conversation structure with both people. Keep any finding about the credit claim distinct from the agreement about how they will work together. A workable next step does not make their accounts of the past identical.

Check the next real update

For the next support report, the team might name who prepared the data, who checked the calculation and who presents it. Update those descriptions if the work changes hands. Ask the presenter to acknowledge the contributions in the update itself, and make the same practice part of your own summaries.

At the agreed check, look at the actual report or message with the people involved. Did it represent the work accurately? Did the earlier correction reach the relevant audience or record? Was any decision that depended on it referred to the appropriate owner? If misrepresentation continues despite a clear expectation, address the verified behaviour through the normal process.

When the deeper issue is that the same colleague handles necessary support work while someone else gets the assignment that builds their skills, review how you allocate non-promotable tasks and opportunities. Correct credit for completed work, then make the next allocation fair on its own terms.

Cooperly's Fundamentals can support a conversation about accountability and the team's expectations. They cannot establish who created an output, prove someone's intent or decide a disputed claim. Keep those decisions grounded in the relevant work and the people's accounts.