1. LandOffer
  2. Blog
  3. All articles
  4. Nominate a Colleague for an Internal Award with Evidence That Fits the Criteria

Workplace Communication

Nominate a Colleague for an Internal Award with Evidence That Fits the Criteria

Prepare an award nomination around the actual criteria and permitted evidence. A completed fictional nomination and five worked revisions show how to describe individual contributions, credit collaborators and retain limits on impact without confusing a draft with a submitted or successful nomination.

10 min readLandOffer team

An internal award nomination is strongest when a reviewer can connect the award's actual criteria to your colleague's specific actions, their collaborators and a bounded result. Start with eligibility and the current form, then build that connection with records you are allowed to use. Enthusiasm helps explain why you care; it cannot replace missing evidence or turn the team's entire result into one person's achievement.

This LandOffer.ai guide contains a completed fictional nomination and a worked evidence revision. Every organization, person, criterion, record, observation and approval in the examples is invented. Sources were checked on October 27, 2026. We did not inspect employee information, contact supporters or submit a nomination.

One artisan holds a small mosaic panel while another points toward it, beside bowls of colored pieces, tools and a drawn design.

Confirm the category, eligibility and actual submission rules

Read the current award description and form before drafting the nomination. Check whether the category recognizes an individual or team, the eligible work period, who may nominate, any excluded roles or previous recipients, and whether the nominee must agree to publicity. Record the deadline and time zone, word limits, required endorsements, supporting evidence format and whether a submission can be edited afterward.

These requirements vary. The University of Toronto Mississauga's nomination process lists a detailed nomination with a two-page, 1,000-word maximum, a department-head endorsement in specified circumstances and a separate support letter. Its page also says submitted nominations cannot be added to. Those are its process requirements, not a universal employee-award package or a current invitation at your employer.

If an eligibility condition is unclear, ask the program owner through the approved route before collecting sensitive material or promising a colleague that you will nominate them. An excellent story can still belong in a different category or work period. A team achievement may need a team nomination rather than an individual entry with the contributors removed.

Check administrative readiness separately so a strong account of the work is not held up by a missing required endorsement or unresolved eligibility question. A polished paragraph does not establish that the nominator is authorized, the correct category was selected or every required endorsement exists. Keep unresolved process questions visible rather than quietly assuming the form will accept your interpretation.

Map each criterion to an action and a bounded effect

MIT Human Resources' nomination-writing guidance recommends selecting a fitting category, describing specific contributions, getting detailed information from collaborators and making the result understandable to reviewers. Its advice to use measurable results where possible is not permission to manufacture a percentage or invent a counterfactual saving.

For each criterion, write down the work situation, what the nominee personally did, who else contributed, the record supporting the account and the effect you can actually describe. Record the claim you must leave out because the evidence does not establish it. A completed guide may be a useful output; adoption needs different evidence, and a causal improvement in delivery needs more than either.

Separate your own observation from a colleague's account. If another person describes a useful intervention, attribute the information and check permission to include it. Do not turn a paraphrase into a quotation or imply an independent endorsement when you wrote both the nomination and the supposed support statement.

Use the award's wording to organize the case, but do not merely repeat it as praise. “Collaboration” needs an example of working with others. “Service improvement” needs a defined service and a credible change. “Developing others” needs evidence of what people could do or understand, not just a count of invitations to a training session.

Completed example: a criteria-mapped nomination

At fictional Cedar Quay Software, Tomas nominates engineer Mira for an individual Collaboration and Practical Improvement award. The invented award considers work completed from January through September 2026. Its three criteria are improving an internal work process, collaborating across functions and leaving a useful resource others can maintain. These are authored criteria, not rules from any cited institution.

In this scenario, the program owner has confirmed Mira's eligibility and Tomas's permission to nominate. A required reviewer has accepted the final factual summary, and Mira has agreed to the approved internal use of her name and work. The completed example below remains an unsent teaching artifact; no real eligibility or consent was checked.

Their evidence record contains three items:

Criterion Record and Mira's contribution Other contributors and limit
Improve a work process September 9 review notes show Mira identifying inconsistent owner information in internal handoff packets and proposing a common check Operations lead Sela defined the receiving team's requirements; this is not a claim that Mira discovered every problem
Collaborate across functions September 16 revision history records Mira integrating engineering and operations comments into the checklist and example packet Engineer Arun tested the example's technical description; Sela reviewed operational wording; reviewers' work remains credited
Leave a maintainable resource September 24 acceptance note names Sela as continuing owner, with an agreed correction route and a versioned example Ownership acceptance establishes a maintenance arrangement, not permanent adoption or guaranteed future updates

Tomas also reviews six handoff packets in the fictional September pilot. Five contain an explicit receiving owner; one does not. This is a small descriptive count from a chosen sample. There is no comparable baseline, measured time saving or proof that the checklist caused a delivery improvement.

Finished nomination narrative

I nominate Mira for the Collaboration and Practical Improvement award for turning an unclear engineering-to-operations handoff convention into a reviewed checklist, an example packet and an accepted maintenance arrangement. I worked alongside her on the September pilot and observed the engineering review. My account of the operations requirements is supported by Sela's approved review notes.

Improving the work process: During the September 9 review, Mira identified that packets used different descriptions of the receiving owner. She drafted a check that asks the sender to name the recipient and record the recipient's acceptance separately. This made the missing information explicit rather than treating a sent packet as an accepted handoff. In our six-packet pilot review, five packets named a receiving owner and one still lacked that information. We have not measured an improvement against an earlier comparable sample.

Working across functions: Mira combined engineering comments with Sela's receiving-team requirements in the September 16 revision. Arun checked the technical example, and Sela corrected language that implied operations had accepted work merely because it was sent. Mira incorporated that correction and retained an unresolved-item field. Her contribution was coordinating and revising the shared artifact; the technical and operational judgments were collaborative.

Leaving useful ownership: By September 24, the package included a checklist, a completed example and a correction route. Sela accepted ongoing ownership, and the version note identified when a changed requirement should trigger review. This is a maintained starting point for the teams, with one pilot packet still needing follow-up. It is not evidence of company-wide use or a proven reduction in incidents.

Mira merits consideration because she made the handoff expectation clearer, incorporated colleagues' corrections and arranged a continuing owner. I am nominating that specific contribution, with the collaborators and limits above, rather than attributing the entire pilot or future delivery results to her.

The narrative answers the invented criteria without claiming that Mira won, deserved a promotion or prevented a future failure. Its evidence is deliberately modest. The unresolved packet is included because omitting it would make the pilot sound more complete than the record supports.

A magnifying glass on a stand highlights an unfinished mosaic corner beside three tags showing a hand, linked circles and a key.

Replace weak praise with evidence a reviewer can understand

The second completed asset follows Tomas's initial draft through a factual review. Each replacement uses the same fictional record, so the revision cannot borrow a better outcome from a different story.

Initial wording Factual problem Completed replacement
“Mira single-handedly transformed our handoffs.” Erases Sela's requirements, Arun's technical check and reviewers' corrections “Mira coordinated the shared checklist revision; Sela defined receiving requirements and Arun checked the technical example.”
“The new process eliminated ownership confusion.” One of six reviewed pilot packets still lacked an owner “Five of six pilot packets named a receiving owner; the remaining packet needed follow-up.”
“She saved every team hours each week.” No timed observation, comparison period or company-wide coverage “The reviewed package makes owner identification and acceptance separate checks; time saving has not been measured.”
“Everyone says she is an exceptional collaborator.” Unspecified people and no attributable example “Sela's approved review notes describe the correction Mira incorporated: sending a packet does not establish receiving-team acceptance.”
“This resource will keep improving delivery indefinitely.” Future maintenance and delivery effects are unverified “Sela accepted ownership of the versioned package, with a correction route; future updates and delivery effects remain to be observed.”

This is more than exchanging adjectives for numbers. The revision changes who receives credit, how far the observation extends and which claims are withheld. The five-of-six count is useful because its denominator and limitation are clear, not because a numerical sentence is automatically stronger than a qualitative one.

Suppose a supporter also remembers that Mira helped another team during an urgent handoff. Tomas has no dated example or permission to include the details. In the authored revision, he excludes that claim and records a question about the date, specific action and permitted supporting account; it remains unverified. The deadline does not justify converting an unconfirmed memory into a verified accomplishment.

Credit collaborators without losing the individual contribution

A nomination for one person can describe collaborative work precisely. Use verbs that explain their actual part: investigated, drafted, coordinated, tested, revised or obtained an ownership decision. Then identify the partners' contributions where they matter to the result. Credit the nominee's own work while retaining the contributions necessary to explain the result.

Ask what would remain if the nominee's part were removed from the account. In Mira's case, the defensible individual contribution is coordinating a shared revision, incorporating a consequential correction and arranging the ownership record. Sela's requirements and Arun's technical review remain necessary parts of the story. The team result provides context; it is not automatically personal credit.

Avoid evaluating worth through constant availability, popularity or proximity to leaders. A colleague working approved hours or contributing quietly may have strong criterion-relevant evidence. Describe the work and its context rather than praising late-night responsiveness as a universal standard of commitment. If the award explicitly asks about exceptional contribution, explain the relevant distinction from the person's agreed responsibilities without inventing unpaid expectations.

Make the packet readable and safe for its actual reviewers

Sonoma State University's nomination guidance emphasizes concrete examples, plain language, proofreading and writing for reviewers who may not know the nominee. Use those principles without treating its support-letter advice as your employer's mandatory process.

A reviewer outside engineering may not understand an internal acronym, repository name or incident label. Explain the work problem in ordinary language before describing the technical contribution. Keep the strongest criterion-relevant example early, and let headings help the reviewer locate each part of the case.

Include only material appropriate for the award reviewers. A customer ticket, security finding, medical detail or confidential personnel note should not be pasted into a recognition form because it makes the story vivid. Use approved summaries or a permitted verification route. Redaction alone does not establish permission, particularly when a small team or distinctive event still identifies someone.

Check supporting statements independently for factual consistency and allowed use. If the process requires a separate writer, that person must provide their own account through the required route. Do not fabricate a signature, endorsement, quotation or attachment receipt. A requested letter is still pending until the required contribution actually exists.

Finish with an accurate submission state

Before submission, compare the completed form with the current criteria and evidence map. Check names, work-period dates, individual-versus-team category, word limits, required approvals and whether links or attachments are accepted. Read the rendered form for truncation and missing fields if you are authorized to use it; a local document alone cannot verify the actual portal.

In the fictional example, Tomas has a completed narrative and approved factual summaries. The nomination is still unsent. He cannot call it submitted, received, shortlisted or successful. In a real authorized process, retain the actual submission confirmation and any later correction route separately from your draft.

Retain the approved contribution summary, its evidence limits and the actual submission state separately from any later committee decision. That record supports accurate recognition without becoming a promised career outcome. Return to LandOffer.ai's workplace guides for another current-work reference, keeping gratitude, nomination status and the award decision distinct.

Sources and Further Reading