1. LandOffer
  2. Blog
  3. All articles
  4. Someone Else Gets Credit for Your Work: Correct the Record with Evidence

Workplace Communication

Someone Else Gets Credit for Your Work: Correct the Record with Evidence

A fictional team corrects a sole-builder attribution using specific contribution evidence, then routes a repeated reporting error to the document owner while keeping an old PDF unresolved.

10 min readLandOffer team

When someone else receives credit for your work, identify the specific attribution error, gather a small set of relevant records, and ask for a factual correction in the place where the error appeared. Separate your contribution from your colleagues’ work and from assumptions about intent. A private clarification may resolve a one-off omission; a repeated or disputed error may need the manager or document owner to review the evidence and correct the record.

This LandOffer.ai guide includes a completed contribution record, a respectful clarification, and a manager-routing example with an unresolved distribution issue. All people, documents, and replies are fictional. No real coworker was contacted, account inspected, or company record changed. The method supports an accurate account of the work; it does not guarantee recognition, a performance-rating change, a promotion, or a particular response from your employer. Primary guidance was checked October 27, 2026.

Colleagues review separate contributions to a shared project record

Define the error before deciding how to respond

“Someone got praised” and “the record wrongly names them as the sole author” are different problems. Praise for a presentation can recognize the presenter’s communication without establishing authorship of the work. A project lead can deserve credit for coordination even when they did not write the implementation. Your goal is to correct what the record says about contributions, rather than replace somebody else’s recognition with an equally incomplete account.

Write down the wording, audience, date, and artifact involved. Was your name omitted from a slide, was your implementation attributed to another person, or did an executive praise the person who happened to answer a question? If you are relying on your recollection of a spoken statement, label it as your recollection. Do not turn it into a verbatim quotation or a documented claim without supporting evidence.

SHRM’s January 2023 advice recommends asking a colleague about missing recognition with an inquisitive tone before assuming intent, and bringing an unresolved or repeated credit issue to management where appropriate. This is professional guidance, not a requirement to confront someone privately in every circumstance. Consider the relationship, the seriousness of the issue, and your employer’s reporting process.

Specify the wording to change, the replacement contribution statement, and the artifact where it belongs. “Please replace the sole-builder wording on slide 4 and preserve everyone’s roles” is reviewable. “Make sure I get the recognition I deserve” is understandable but leaves the recipient guessing about the requested action. An exact correction also helps a manager evaluate the issue without resolving a broad argument about who is more valuable.

Gather contribution evidence without claiming more than it shows

Use records you are authorized to access: a design discussion, a work item, a reviewed change, a test-plan document, or an accepted handoff. Choose the smallest set that explains the contribution. Preserve links and dates in the approved system; do not move confidential company material into personal storage merely to build a case.

A timestamp can show when a particular draft existed. It does not prove that nobody discussed the idea earlier. A change history can support an implementation contribution without proving sole ownership of the whole project. Likewise, counting commits, lines changed, messages, or meeting attendance is not a fair automatic measure of contribution. Include requirements work, testing, coordination, and other substantive roles when the evidence supports them.

The Center for Creative Leadership’s feedback guidance distinguishes the situation, observable behavior, and impact, then encourages inquiry about intent. For this task, that means describing the actual slide wording and its consequence before asking how it happened. It does not mean you must accept an explanation that leaves the attribution wrong. Intent and correction are separate questions.

Give the reviewer enough context to assess the contribution fairly. Include a genuine limitation: a shared design, a colleague’s review, or an artifact that does not establish what you initially thought. Keep relevant context even when it limits the contribution you can claim.

Completed case: implementation, validation, and presentation are different roles

Nia and Owen work at fictional Alder Systems. They helped prepare an inventory-normalization tool for an internal demonstration. Priya reviewed validation scenarios. In an October 13, 2026, project update, slide 4 says, “Owen built the inventory reconciler.” Nia sees the slide in the approved team workspace. She believes its sole-builder wording is inaccurate; she does not have evidence that Owen intended to exclude her.

Her completed contribution record is narrow enough to support a correction:

Record What the fictional artifact supports What it does not establish
October 5 mapping proposal, authored by Nia with Owen’s comments Nia drafted the normalization mapping; Owen contributed requirements comments That Nia originated every project idea or worked without input
October 6 requirements summary, maintained by Owen Owen coordinated stakeholder requirements and documented the demonstration scope That Owen wrote the implementation
October 8 reviewed change record, authored by Nia Nia implemented the mapping logic described in that change That the tool was deployed or proved effective in production
October 9 scenario review, maintained by Priya Priya reviewed the validation cases and recorded unresolved questions That every test passed or that Priya approved release
October 12 demonstration outline, maintained by Owen Owen prepared and coordinated the presentation Sole authorship of the demonstrated tool
October 13 slide 4 The update currently attributes building the reconciler to Owen The reason for that wording or everyone’s understanding of it

These are fictional written records, not a repository inspected or software executed for this article. No performance measurements, customer outcomes, or production results are supplied. Nia’s evidence supports a contribution statement, which is the task at hand.

She starts with a private message to Owen because this example has no stated threat or other reason to avoid direct contact:

In today’s project update, slide 4 says you built the inventory reconciler. The mapping proposal and implementation record identify my work on those parts, while you coordinated requirements and the demo, and Priya reviewed the validation scenarios. The current wording makes the implementation appear to be yours alone. Was it intended to describe the presenter rather than the contributors? Could we replace it with the role summary below before the next distribution?

Owen replies that he copied a presenter field into the sentence and did not mean to identify the sole implementer. Nia records that as Owen’s explanation, not independently proven intent. He agrees to correct the slide he maintains. Owen’s explanation and agreement do not establish that the slide changed; Nia still needs to read the corrected artifact.

Their agreed replacement reads:

Inventory-normalization demonstration: Nia drafted the normalization mapping and implemented the mapping logic. Owen coordinated requirements and prepared the demonstration. Priya reviewed the validation scenarios; the scenario review still contains open questions. This update does not record production deployment or release approval.

The correction credits Nia without erasing coordination or validation work. It also avoids replacing one inaccurate claim with “Nia delivered the complete solution,” which the selected evidence does not support. Priya is credited for the review she performed, not for an invented all-clear.

Correct the audience’s record, not only the private conversation

After a private acknowledgment, identify which audience-facing artifact still needs the agreed correction. Identify the artifact owner and the appropriate way to update it. That may mean editing the current slide, adding a correction to meeting notes, or asking an owner to distribute a short factual clarification. A large public accusation is not the only alternative to staying silent.

In the fictional case, Owen updates slide 4 on October 14, and Nia reads the replacement in the team workspace. Owen also gives the following clarification at the next project discussion:

One attribution correction from the earlier update: Nia drafted the mapping and implemented that part of the reconciler. I coordinated requirements and the demonstration, and Priya reviewed the scenarios. Slide 4 now reflects those roles and the remaining review questions.

The correction is brief because the audience needs an accurate work record, not the details of Nia and Owen’s private conversation. The updated slide and delivered clarification close those two specific actions within the fictional case. They do not prove that every recipient revised their impression or that the correction reached every exported copy.

Before sharing a correction, consider who actually needs it. A restricted project update should not become an excuse to circulate confidential work broadly. Ask the responsible owner to handle distribution when you lack that authority. Preserve the corrected version and date without deleting the original evidence of what was changed, subject to the organization’s records policy.

A repeated error can require a different owner

On October 20, a monthly report repeats the old sole-builder wording. Owen did not author that report; its editor, Mei, copied material from an earlier export. Nia now has evidence of a second inaccurate artifact, but repetition alone still does not establish a coordinated attempt to take credit. The immediate problem is that the authoritative correction did not reach another reporting channel.

Nia’s completed request to Mei, who is also the responsible manager, reads:

The October 20 monthly report repeats the earlier attribution that Owen built the reconciler. The corrected October 14 slide identifies Nia’s mapping and implementation, Owen’s requirements and demo work, and Priya’s scenario review. I have linked the current slide and the supporting contribution records in the approved workspace. Could you update the report’s role summary and identify how to correct the PDF already circulated? I would also like us to agree which source future summaries should use. I am asking for accurate attribution, not a judgment about anyone’s motive.

Mei checks the linked records with Nia and Owen. On October 21, she updates the report’s master document with the agreed role summary. She asks the communications owner to handle the previously distributed PDF; that owner has not yet accepted a correction date. Mei agrees to provide a status update by October 23. Nia does not record the distributed PDF as corrected merely because the master changed.

Record or decision Completed disposition in the fictional case Remaining boundary
October 13 slide Updated October 14; Nia read the corrected wording Does not fix every old export
Project discussion Owen delivered a specific role clarification Audience understanding was not measured
October 20 report master Mei updated it October 21 after reviewing contributions Published PDF remains unchanged in the case record
PDF correction request Mei asked its communications owner and accepted responsibility for a status update Owner’s correction date and actual distribution still pending
Future reporting source Mei designates the current reviewed role summary as the source for the next report Later reports still need review; recurrence is not guaranteed to stop

The manager’s role here is concrete: inspect evidence, correct the document she owns, and coordinate a request she cannot complete alone. This avoids escalating a vague complaint while leaving the actual error untouched. It also avoids treating a disputed workplace pattern as resolved after a single reassuring conversation.

A revised contribution record sits beside an older copy still awaiting correction

Choose the route according to the situation

For a first omission with a clear artifact, a private question and a proposed correction may be sufficient. If an inaccurate statement is being used in a live decision, a short factual clarification can be appropriate: state your contribution and the shared roles without arguing about motives in front of the room. Follow up on the underlying record afterward. Choose a route that fits your role, the evidence, and the meeting’s purpose.

For repeated, denied, or materially consequential misattribution, bring the specific records and attempted corrections to the appropriate manager or reporting owner. If the manager is involved, or you believe a direct approach is unsafe, ask about another authorized channel. You do not need to manufacture a confrontation to earn the right to seek support.

Acas’s guidance, written for the UK workplace context, recommends checking the organization’s policy and distinguishes informal resolution from formal routes when a problem is serious or remains unresolved. It is useful process guidance here, not a statement of US legal rights or a requirement to exhaust private conversations. Concerns involving discrimination, retaliation, threats, or formal review decisions may need a different process and case-specific advice.

Prepare the contribution record and proposed wording, ask the responsible owner for the correction, and agree how you will verify it. Track what was actually corrected and what still needs action. LandOffer.ai publishes this workplace guide; it does not investigate disputes or determine how your employer should allocate recognition.

Sources and Further Reading