Employee recognition software: how to choose one that gets used

The pilot goes well. Three months later the feed is a thank-you from the same eight people, finance has discovered that the vouchers were taxable, and the warehouse shift has never used it because nobody there has a work laptop.

None of that is a feature problem, and none of it appears in a demo.

This article is a buyer's guide to employee recognition software that names no products and quotes no prices. It covers what the system actually has to do, the tax question that sinks more schemes than any missing feature, the privacy line on public praise, the five reports worth more than the feature list, and the questions to ask a provider before you sign.

Recognition works best when it sits in the same place as feedback and goals rather than in an app of its own. See how New Dynamics recognition lets people thank each other for specific work where the rest of the conversation already happens.

If you are still deciding what to recognise rather than what to buy, our 50 employee recognition ideas is the better starting point, and costs nothing.

What the software has to do

Strip away the branding and there are five jobs.

Make giving recognition take under a minute. Every extra field reduces use. If a manager has to pick a value, a category, an amount and a visibility setting, they will do it once.

Put it where people already are. Recognition that requires a separate login is recognition that happens on the last Friday of the quarter. That means working inside the tools people have open, and on a phone for anyone without a desk.

Handle awards end to end, including the money. Nominations, approvals, budgets, the award itself, and a record of who received what and at what value. The last part is the one that matters at year end.

Show who is missed. The report nobody asks for in a demo and everybody needs by month three.

Respect privacy. Public praise is published information about a person, and not everyone wants it.

Anything beyond these five is decoration until the five are solid.

The tax question, before the feature list

This is the part that turns a popular scheme into an awkward conversation with finance, and it is specific to how the award is given rather than to which system you buy. The description below is the United Kingdom position and is general information rather than tax advice.

HM Revenue and Customs runs a trivial benefits exemption, and the conditions are strict. A benefit is exempt only if all of these apply: "it cost you £50 or less to provide", "it's not cash or a cash voucher", "it's not a reward for their work or performance", and "it's not in the terms of their contract".

Read the third condition again. A recognition award is, by definition, a reward for work or performance. So the exemption that employers most often assume covers their scheme is usually the one condition their scheme cannot meet, and the award becomes reportable.

The practical answer for most employers is a PAYE Settlement Agreement, which HMRC describes as an arrangement that "allows you to make one annual payment to cover all the tax and National Insurance due on minor, irregular or impracticable expenses or benefits for your employees". That keeps the tax off the individual's payslip, which matters: an award that arrives as a deduction is worse than no award.

What this means for the software choice is concrete. Ask every provider:

• Can it export every award, with recipient, date, item and value, in a format payroll can use?
• Can it enforce a per-award and per-person budget, and show the running total?
• Can it separate categories that are taxable from any that are not, rather than treating everything as one pot?
• Can it stop an award being issued once a limit is reached, rather than reporting the breach afterwards?

A system that cannot answer those four will hand you a reconciliation job every year, however good the feed looks.

Public praise is published information

A recognition wall is a stream of statements about identifiable people, visible to colleagues and sometimes beyond. The Information Commissioner's Office puts the test plainly for employers using employment records: "You must balance the benefits to you of publishing information about your workers with their reasonable expectations of privacy."

In practice, three settings carry that balance:

• Who can see a given recognition: the team, the organisation, or the recipient alone. Someone should be able to receive thanks without it being broadcast.
• What happens on exit: whether a leaver's record disappears, and whether that is what the team expects.
• How long the feed is kept, and whether anyone has ever decided that rather than inheriting the default.

Ask the provider where the data lives, who can export it, and what happens to it when the contract ends.

The five reports that matter

A feature list tells you what the software can do. These five tell you whether the scheme is working, and a system that cannot produce them is a wall of praise with no feedback loop.

1. Who has received nothing. By team, by shift, by working pattern, by location. This is the single most useful report and the one most often missing. Expect to find night shifts, part-time colleagues and back-office teams.
2. Who is giving. If recognition only flows downward from managers, you have a manager habit, not a culture. If it is concentrated in two enthusiastic givers, it will stop when they leave.
3. What is being recognised. Tie the text back to the behaviours you say matter. If every award is for "going the extra mile" at the weekend, the scheme is quietly rewarding overwork.
4. Spend against budget, per team and per head, with the taxable total visible all year rather than discovered in the spring.
5. Distribution across protected and non-protected groups. Run it quietly and regularly. A scheme that systematically misses one group is a fairness problem that looks like an engagement success.

Our post on long service recognition covers the one award type where the rules and the expectations differ.

Questions to ask a provider

Take these to the demo and ask for answers in writing.

1. Show me the payroll export, with a real month of data, not a sample screen.
2. Show me the report of people who have received nothing in ninety days.
3. What does an employee without a company device see, and how do they give recognition?
4. What are the visibility options, and what is the default for a new recognition?
5. What happens at renewal: can we export everything, in what format, and what is deleted?
6. What does implementation require from us, in hours, and who runs it?
7. How do awards work across countries, if you have staff outside the United Kingdom, since the tax treatment differs everywhere.

A provider who answers the first two quickly is used to customers who run real schemes. A provider who redirects to the feed and the badges is selling a demo.

What usually goes wrong

• Budget with no rules. Managers either spend nothing or spend it all in month one. Set a per-person cap and a rhythm before launch.
• Launching to everyone at once. A pilot in two teams, with the awkward questions answered, beats a company-wide launch with none.
• Treating low use as a training problem. If people are not using it, something is slower than the alternative. Usually that is the login, the form or the approval.
• No link to the work. Recognition with no detail reads as politeness. Our post on recognition messages covers the wording that makes it land.
• Buying a separate tool for every related job. Recognition, feedback, goals and reviews that sit in four systems produce four half-used systems.

Do you need dedicated software at all?

Often, no. Below a hundred or so people, a weekly habit in an existing channel, a named budget and a spreadsheet of awards can work well, and the tax questions are the same either way.

Dedicated software earns its cost when any of these are true: recognition has to reach people without desks, awards involve money that needs budgets and approvals, you need the distribution reports, or recognition keeps starting and stopping because it depends on individuals remembering.

If the honest answer is that the habit does not exist yet, build the habit first. Software makes an existing habit easier and does not create one.

Frequently asked questions

What is employee recognition software?

It is a system for giving, recording and sometimes rewarding recognition at work: peer and manager thanks, nominations and awards, with a record of who received what and reporting on participation. The useful ones also handle budgets, approvals and the export that payroll needs at the end of the year.

Is employee recognition taxable in the UK?

Usually yes. HMRC's trivial benefits exemption requires that the benefit is not cash or a cash voucher and is not a reward for work or performance, and a recognition award is a reward for work or performance. Most employers handle the resulting liability through a PAYE Settlement Agreement, and this is general information rather than tax advice.

What should you look for in a recognition platform?

Speed of giving, reach to people without a company device, award and budget handling with a payroll export, a report showing who has received nothing, and clear visibility settings. Those five cover the ways schemes fail. Everything else is preference.

How much does employee recognition software cost?

Pricing is per employee per month in most cases, and it varies enough that any figure quoted here would mislead you. The number that matters is the total of the licence plus the award budget plus the tax on the awards, because the last two are usually larger than the first.

Do small companies need a recognition platform?

Often not. Below about a hundred people, a regular habit in a channel people already use, a named budget and a simple record of awards achieves most of the benefit. Buy software when recognition has to reach people without desks, when awards need approvals and budgets, or when you need the participation reports.

How do you measure whether recognition is working?

Look at who has received nothing, who is giving, what is being recognised, spend against budget and distribution across groups. Volume on its own is a vanity measure: a rising number of awards concentrated in the same teams is a sign the scheme is widening a gap rather than closing it.

What happens to recognition data when someone leaves?

That depends on configuration, so decide it before launch rather than inheriting a default. The ICO expects employers to balance publishing information about workers against their reasonable expectations of privacy, which applies to a public feed as much as to a file.

Your next step: test the two reports

1. Write down the five jobs above, then score each shortlisted system out of five. Ignore the feature matrix.
2. Ask for the payroll export and the "received nothing" report in every demo, with real data.
3. Confirm your tax position for awards before launch, including whether a PAYE Settlement Agreement is needed.
4. Pilot in two teams, one of which has people without company devices, and read the participation report after six weeks.

For the habits that make any scheme work, with or without software, read and download our employee recognition guide. The guide is free to read, and the PDF uses our short download form.

Want recognition in the same place as feedback and goals rather than in a separate app? Book a New Dynamics demo and bring your current award budget. You can also email contact@new-dynamics.com.