An employee rewards and recognition programme makes valued contributions visible and explains how they will be acknowledged. Rewards may include financial or other benefits, while recognition expresses appreciation for a specific contribution. A useful programme connects both to the organisation’s goals and treats employees fairly. Its credibility depends on clear criteria and consistent decisions more than on the size of an award ceremony.
What published research shows
A Gallup–Workhuman study reported in September 2024 followed nearly 3,500 employees from 2022 to 2024. Employees receiving high-quality recognition were 45% less likely to have changed organisations two years later. This is a relative difference observed in the study, not a 45-percentage-point reduction or a guaranteed effect of introducing an award programme. Source
Define the purpose before selecting rewards
Start with the behaviour or contribution you want to support. This might be reliable teamwork, service improvement, knowledge sharing or sustained quality. Avoid a vague objective such as making everyone more motivated without explaining what the programme will recognise or how it fits the work.
Check whether the underlying problem actually requires recognition. An award cannot compensate for unclear responsibilities, an unsafe process or an unreasonable workload. If employees lack the tools to do their jobs, address that obstacle directly. Recognition should complement sound management and appropriate employment arrangements.
Distinguish pay, incentives and appreciation
Base pay compensates the role under the relevant employment arrangements. An incentive typically links a reward to defined conditions or results. Recognition acknowledges a contribution and may be informal or formal, financial or non-financial. Explain these distinctions so employees know what is contractual, what is conditional and what is discretionary.
CIPD’s reward guidance considers the wider mix of financial and non-financial elements in the employment experience. For programme design, this means looking beyond a single prize. Development opportunities, useful feedback and meaningful appreciation may sit alongside financial rewards, but should not be presented as substitutes for obligations owed to employees.

Make the criteria observable
Describe what qualifies and what evidence is required. “Supported another team to resolve a documented handover problem” is easier to assess than “showed a great attitude.” Give examples of eligible contributions without making the examples an exhaustive list that excludes equally valuable work.
| Design choice | Question to answer | Risk to avoid |
|---|---|---|
| Individual or team recognition | Who contributed to the outcome? | Rewarding one visible person for shared work |
| Nomination route | Who can submit evidence? | Excluding less visible roles or shifts |
| Decision process | Who reviews and approves? | Unexplained preferences or conflicts of interest |
| Timing | When should recognition occur? | Appreciation arriving too late to be meaningful |
| Reward form | What is suitable for the recipient? | Assuming everyone wants public attention |
Keep the process proportionate. A short evidence-based nomination may be more practical than a lengthy application for a modest award. The design should make worthwhile contributions easier to notice, not add administrative work that discourages participation.
Build fairness into access and decisions
Consider employees whose work is important but less visible, including support functions, remote teams and different shifts. A nomination system based only on popularity may favour people with larger networks. Explain how contributions will be compared and how reviewers will address incomplete information or conflicts of interest.
For a formal award, require reviewers to declare relevant conflicts and refer the decision to an independent reviewer when needed. Record the contribution, supporting evidence, decision and brief reason. If evidence is incomplete, request clarification using the same standard for comparable nominations. Define who handles correction requests and when employees can expect a response. Set the budget and approval authority before promising rewards.
Review who receives recognition over time and investigate unexplained patterns. Equal treatment does not require identical awards for every contribution, but differences should have understandable reasons. Provide a route for questions and corrections without turning the programme into a competition that damages cooperation.
Avoid incentives that weaken the real objective
A sales award based only on revenue may overlook payment collection, unsuitable commitments or delivery capacity. A speed award may encourage shortcuts. Consider what a person could do to maximise the metric while harming the intended outcome, then adjust the criteria and safeguards.
For example, a fictional service team might recognise a well-documented improvement that reduces repeated errors while preserving quality. The review would examine the contribution and evidence, not assume that a high activity count proves value. This example is illustrative and does not describe an ATMACSS client outcome.
Make recognition specific and respectful
Explain what the person or team did and why it mattered. Generic praise repeated for everyone can feel disconnected from the work. Recognition close to the contribution often makes the connection easier to understand, but the timing should still allow the facts to be checked.
Ask about preferences where appropriate. Some employees welcome a public announcement; others prefer private thanks or a development opportunity. Avoid sharing personal information or project details that should remain restricted. Recognition should respect the recipient and the people whose work made the contribution possible.
Pilot and listen before expanding
Test the programme with a defined group and period. Explain the criteria, nomination process and review arrangements. Collect feedback from participants and people who were eligible but did not take part. Low participation may indicate confusion or lack of trust rather than lack of worthwhile contributions.
Review the effort required, consistency of decisions and whether the programme recognises the intended work. Adjust unclear criteria before extending the programme. Keep a record of the changes so employees can understand which rules applied during each period.
Evaluate the programme without claiming causation
Track participation, coverage, decision timeliness and feedback about fairness. You may also monitor relevant organisational measures, but a change in retention or performance does not prove the programme caused it. Leadership, pay, workload and labour-market conditions can change at the same time.
Define coverage before counting awards. In a fictional pilot with a fixed group of 100 eligible employees, 30 awards received by 20 different people mean recipient coverage of 20%, not 30%. Count each recipient once during the stated period and document who is eligible. Compare departments or shifts using their own eligible headcounts, while checking differences in work and opportunity to contribute. This is a diagnostic measure, not a quota or proof of fairness; a low rate should trigger questions about access, nominations and evidence rather than an automatic award.
Use the findings to improve the design rather than to produce an impressive headline. If people perceive the process as unfair, investigate that finding even when award participation is high. A programme should earn trust through its decisions, not rely on communication alone to establish credibility.
Design a practical approach with ATMACSS
Bring your current criteria, workforce structure and feedback to a discussion about Corporate Training, Coaching & Internship with ATMACSS. The performance management guide explains how clear expectations and useful feedback can support a recognition programme grounded in actual contributions.

